# Issue Details: Explore
The Explore tab provides a detailed view of the issue, including its description, affected assets, risk context, and remediation guidance.
Use this tab to understand what was detected, assess impact, and take action.
| Section | What it shows | How to use |
| ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------- |
| Description | A detailed explanation of the issue, including the misconfiguration or exposure, the specific conditions that caused it (such as settings, ACLs, or policies), and the potential impact on confidentiality, integrity, and availability. | Use this section to understand the root cause of the issue and why it matters, without reviewing raw configurations. |
| Exposed active secrets | Any sensitive data detected in the affected resources, such as tokens, credentials, or encoded secrets. | If present, treat the issue as high priority, as sensitive data may already be exposed. |
| Cloud account | The cloud account where the issue was detected. | Use this to identify ownership and route remediation to the relevant team. |
| Entity severity counts | A breakdown of affected entities by severity level. | Use this to understand how widespread the issue is and whether it includes high or critical risk items. |
| Top impacted resources | The main resources affected by the issue, such as buckets, assets, or services. | Use this to prioritize investigation and remediation on the most relevant resources. |
| In cloud regions | The regions where the affected resources are deployed. | Use this for regional ownership, compliance considerations, and environment-specific handling. |
| Top context | Contextual risk signals such as public exposure, resource usage, activity, or severity indicators. | Use these signals to assess real risk and prioritize remediation based on exposure and usage. |
| Recommendation | Remediation guidance with step-by-step instructions, available through different methods such as AWS Portal, CLI, or Terraform. | Follow the steps according to your preferred workflow to resolve the issue. |
| Attack path | A visual representation of how the issue can be exploited, including relationships between resources and possible attack paths. | Use this to understand the broader impact, identify lateral movement risks, and prioritize fixes based on exploitability. |
---
# 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/explore.md?ask=
```
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.