> 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-cloud-runtime-security/cases-and-issues/investigation-and-response/review-findings/findings-card.md). # Findings card The Findings card displays information about the selected finding. On this card you can see the following information. {% hint style="info" %} ### Note The information in this card is context specific, therefore some sections are not available for all findings. {% endhint %}

Section	Description
Header	Finding ID, name, category (such as, Vulnerability or Compliance), time created, and time updated.
Description	Reason that the finding was created.
Impact	Information about the possible impact of the finding on your system.
Asset	Name and type of the affected asset. To investigate the asset, click on the asset name to open a new tab displaying the asset card.
Detection logic	Detection rule that identified the specific security risk, configuration gap, or malicious behavior generating the finding.
Compliance	Violated compliance standards and specific framework controls associated with the finding. Click the expand icon to see a list of all standards associated with the finding and a granular breakdown of specific controls breached under each standard.
Evidence	Visualization of the finding in your environment.
Data	Normalized finding data.

--- # 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-cloud-runtime-security/cases-and-issues/investigation-and-response/review-findings/findings-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.