# Finding Details

To view extended information for a single finding, click "view" next to a monitor result. This will open that finding's details:

<figure><img src="/files/2zdfyiAEzfqElwIxNG8P" alt="Finding details page showing attack path visualization, actions for Assign, Ignore, and Review fix, and risk details for an AWS IAM policy" width="563"><figcaption></figcaption></figure>

### Actions

#### Assign

If you've integrated P0 with Jira, you can assign findings for resolution. By default the assignee is manually assigned by you. If you've configured P0 for automatic assignment, assignees will be determined by the configured resource owner for the target scope in which the finding was discovered.

The created Jira ticket contains the finding description, finding context, and, if available, the resolution commands.

#### Ignore

To ignore a finding, click the "Ignore" button on that finding's details. The finding will no longer appear in your results, unless you select "Ignored" in the results views.

#### Review fix

For P0-provided monitors, P0 provides cloud shell commands that will resolve the finding. For example, for the "Unused Privileged Access" finding, P0 will provide commands to replace the vulnerable entitlement with a least-privilege entitlement.

<figure><img src="/files/RjndgWnpG66UvxOQCynO" alt="Remediation commands showing a least-privilege IAM policy replacement for an overly permissive AmazonEC2FullAccess policy" width="375"><figcaption></figcaption></figure>

#### Add notes

You can add notes, including business justifications, to findings by typing notes on the finding's details page.

### Attack path

P0 displays a graphical representation of the findings attack path: How an actor holding the identity can gain risky access to your system.

The attack path view has the same capabilities as the [Access Inventory](/inventory/access-inventory.md#graph-visualization) in the Access Inventory.

### Detailed information

The remainder of this page shows detailed information for the finding, and explains why this finding matched the monitor's search. For an explanation of this information, see [Result Details](/inventory/result-details.md).


---

# Agent Instructions: 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:

```
GET https://docs.p0.dev/posture/finding-details.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.