> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xdr-5.x/detect-investigate-and-respond-to-threats/investigate-and-respond-to-cases/investigate-issues/issue-card.md). # Issue card The Issue card provides a full breakdown of an issue, helping you understand the root cause and take action through relevant evidence, remediation guidance, and response options. The issue card supports full case investigation by retaining case context. Once you have finished reviewing an issue, close the card to return to the initial case investigation. Each issue card adapts to the type of issue you’re investigating, surfacing the most relevant information and tools at every stage of the workflow. While layouts may vary, most issues share a common set of tabs designed to support triage, investigation, and resolution. ### Overview Displays a description of the issue and provides key information, including: * Assignee * Status * Time at which the issue was created and updated * Suggested automations to run on the issue. Click the automation to open to the Work Plan tab with details of the automation. * Affected Assets with links to the affected asset cards * Cases linked to the issue * Detection rule that triggered the issue and any associated policies. Click to see more details or open the rule or policy directly. * Violated compliance standards and specific framework controls associated with the issue.

License Note: Requires the Cortex Cloud Posture Management or Cortex Cloud Runtime Security add-on.

Click the expand icon to see a list of all standards associated with the issue and a granular breakdown of specific controls breached under each standard. * If an automation rule triggered an automation (Quick Action, playbook, or agentic agent) to run on the issue, the name of the last automation to run on the issue is displayed. * (For issues related to Container images) **Related Affected Assets** displays the assets that are related to the assets listed under **Affected Assets**. For example, if one of the associated assets is a container image running on a VM, the VM will be listed under this section. The Evidence section contains information to help you investigate the issue, such as the causality chain. {% hint style="info" %} **Note** This section is context-specific and shows data according to the issue context. {% endhint %} ### Resolution Displays recommended remediation actions, and pending, in progress, and completed actions. For more information, see [Resolution actions](/cortex-xdr-5.x/detect-investigate-and-respond-to-threats/investigate-and-respond-to-cases/investigate-issues/resolution-actions.md). ### Issue Information Displays a summary of the issue, such as issue details , indicators, and outstanding tasks. Some fields are informational and some can be edited. Includes the following sections (depending on the layout): * **Issue details**: A summary of the issue, such as type, severity, and when the issue occurred. You can update these fields as required. * **Command and task results**: Lists any manual commands and playbook task results. * **Work plan**: View or take action on the following: * **Playbook tasks**: When a playbook runs, any outstanding tasks appear. You can take various actions here or in the Work Plan tab. * **To-Do Tasks**: An ad-hoc item that is not attached to the Work Plan. Create tasks for users to complete as part of an investigation. These are like a To-Do list that you keep in an investigation on an ad-hoc basis, rather than the Work Plan, which follows a pre-defined process. You can view or create To-Do tasks. * **Notes:** Helps you understand specific actions taken, and allows you to view conversations between analysts to see how they arrived at a certain decision. You can see the thought process behind identifying key evidence and identifying similar cases. * **Malicious or suspicious indicators:** A list of any malicious or suspicious indicators. If you have the Threat Intel add-on, you can pivot to the Indicators page, where you can take further action on the indicator. * **Indicator handling:** Take actions on indicators from the displayed options. ### Technical Information Displays an overview of the information collected about the investigation, such as indicators, email information, URL screenshots, etc. When you run a playbook, the sections are automatically completed. ### Investigation Tools Enables you to take action on the issue, such as converting a JSON file to CSV and checking if the IP address is in CIDR. ### War Room A comprehensive collection of all investigation actions, artifacts, and collaboration. It is a chronological journal of the issue investigation. Each issue has a unique War Room. For information, see [Use the War Room in an investigation](/cortex-xdr-5.x/detect-investigate-and-respond-to-threats/investigate-and-respond-to-cases/investigate-issues/use-the-war-room-in-an-investigation.md). ### Work Plan A visual representation of the running playbook that is assigned to the issue. For more information, see [Use the Work Plan in an investigation](/cortex-xdr-5.x/detect-investigate-and-respond-to-threats/investigate-and-respond-to-cases/investigate-issues/use-the-work-plan-in-an-investigation.md). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://cortex-docs.paloaltonetworks.com/cortex-xdr-5.x/detect-investigate-and-respond-to-threats/investigate-and-respond-to-cases/investigate-issues/issue-card.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.