# Issue Details

The issue details page provides a single, complete view of a detected issue, its identity, severity, ownership, supporting evidence, and the actions you can take to resolve or dismiss it.

<figure><img src="/files/SYZw6grRzE0dzCn1NmRt" alt="" width="563"><figcaption></figcaption></figure>

The page contains the following parts:

* [Issue header](#issue-header)
* [Explore](/scan-and-analyze-with-ox/analyzing-scan-results/active-issues-new/explore.md)
* [Dev Explore](/scan-and-analyze-with-ox/analyzing-scan-results/active-issues-new/issue-details-dev-explore.md)
* [Context](/scan-and-analyze-with-ox/analyzing-scan-results/active-issues-new/issue-details-context.md)
* [Sensitive Data](/scan-and-analyze-with-ox/analyzing-scan-results/active-issues-new/issue-details-sensitive-data.md)
* [Artifacts and Artifact Files](/scan-and-analyze-with-ox/analyzing-scan-results/active-issues-new/issue-details-artifacts-and-artifact-files.md)
* [Commits](/scan-and-analyze-with-ox/analyzing-scan-results/active-issues-new/issue-details-commits.md)
* [Extra Info](/scan-and-analyze-with-ox/analyzing-scan-results/active-issues-new/issue-details-extra-info.md)
* [Issue actions](/scan-and-analyze-with-ox/analyzing-scan-results/active-issues-new/issue-details-extra-info.md)

## Issue Header

The issue header provides a quick summary of the issue, including its type, severity, detection source, and ownership context.

<figure><img src="/files/YH80a4ntmz6OlBA4o290" alt="" width="553"><figcaption></figcaption></figure>

You can use this section to immediately understand what the issue is and how critical it is.

Example: `S3 · Publicly Accessible · AWS · Internet Exposed · Bucket Has Data`

Each part represents a different aspect of the issue:

<table><thead><tr><th width="234">Element</th><th>Description</th></tr></thead><tbody><tr><td>S3</td><td>The affected service or asset type.</td></tr><tr><td>Publicly Accessible</td><td>The core issue or misconfiguration detected.</td></tr><tr><td>AWS</td><td>The cloud provider where the issue exists.</td></tr><tr><td>Internet Exposed</td><td>Indicates that the resource is accessible from the public internet.</td></tr><tr><td>Bucket Has Data</td><td>Provides additional context about the resource state, increasing the risk level.</td></tr></tbody></table>

This structure helps you quickly understand what the issue is, where it exists, and why it is risky.

| Field                 | Description                                                                                                   |
| --------------------- | ------------------------------------------------------------------------------------------------------------- |
| Severity              | Indicates the risk level of the issue (for example, Apocalypse). Higher severity requires faster remediation. |
| Trend indicator       | Shows whether the issue severity or risk trend is increasing or decreasing.                                   |
| Context type          | Indicates the context category of the issue (for example, Cloud Context).                                     |
| Owner                 | The details f the issue owner.                                                                                |
| Application / Project | The application or project associated with the issue.                                                         |

## Issue actions

The action bar allows you to take immediate action on an issue directly from the Issue details page.

<figure><img src="/files/19kF3vmyNZzLTVVJCjT5" alt="" width="563"><figcaption></figcaption></figure>

Use these actions to manage the issue lifecycle, collaborate with your team, and trigger remediation workflows.

| Action                                                                                                                                | Description                                                                                           |
| ------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- |
| [Exclude](/exclusions-and-sla/scope-policy-and-sla-compliance/exclusions.md)                                                          | Excludes the issue from active tracking. Use this when the issue is not relevant or accepted as risk. |
| [Report false positive issue](/scan-and-analyze-with-ox/analyzing-scan-results/active-issues-new/reporting-false-positive-actions.md) | Marks the issue as a false positive.                                                                  |
| [Add comments](/ticketing-and-messaging/ticket-management/jira/page-1.md)                                                             | Adds a comment to the issue for collaboration or documentation.                                       |
| [Send a message to Slack](/ticketing-and-messaging/messaging/slack.md)                                                                | Sends the issue details to a configured Slack channel.                                                |
| [More options](#additional-actions)                                                                                                   | Opens additional actions for advanced issue management.                                               |
| [Create ticket](/ticketing-and-messaging/ticket-management.md)                                                                        | Creates a ticket in your configured ticketing system for remediation tracking.                        |

### Additional actions

The **More options** menu provides additional actions:

<table><thead><tr><th width="287.3333740234375">Action</th><th>Description</th></tr></thead><tbody><tr><td>Copy link to issue</td><td>Copies a direct link to the issue.</td></tr><tr><td>Start ChatGPT</td><td>Opens ChatGPT with context about the issue.</td></tr><tr><td>View Code Fix</td><td>Displays suggested remediation in code form, when available.</td></tr><tr><td>Jira actions</td><td>Opens Jira-related actions for the issue.</td></tr><tr><td>Snooze issue</td><td>Temporarily hides the issue until a selected time.</td></tr><tr><td>Make app irrelevant</td><td>Marks the related application as irrelevant for this issue.</td></tr><tr><td>Disable policy</td><td>Disables the policy that generated the issue.</td></tr><tr><td><a href="/pages/ugSbiaOeShMgmmg7GtqX">View/Edit policy</a></td><td>Opens the policy configuration.</td></tr><tr><td>Change severity</td><td>Updates the severity level of the issue.</td></tr><tr><td><a href="/pages/3gdvizTG1WqGImq3xqei">Change issue owner</a></td><td>Assigns or updates the issue owner.</td></tr><tr><td><a href="/pages/wLXEWJFQM747HQ346kBm">SLA actions</a></td><td>Opens SLA-related actions for the issue.</td></tr></tbody></table>


---

# 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.ox.security/scan-and-analyze-with-ox/analyzing-scan-results/active-issues-new/issue-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.