# Issue Details: Dev Explore
The Dev Explore tab provides developer-focused remediation guidance and validation details for the detected issue, including step-by-step fix instructions, secret validation, SLA tracking, and detection history.
| Section | What it shows | How to use |
| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Recommendation | Step-by-step remediation guidance specific to the detected issue, covering rotation, removal of the secret from the affected resource, cleanup of downstream copies and caches, and recommended secret-storage practices. A **Start AI Assistant** option is available for guided support. | Follow the listed steps in order to resolve the issue. Launch the AI Assistant if you want help executing or scripting the steps. |
| SLA | The remaining time (or overage, shown in red) to remediate the issue based on its severity policy. | Use this to prioritize work — items past SLA should be addressed first. |
| Detections | The number of times the same issue has been detected. | Use this to gauge recurrence. Repeated detections may indicate a systemic problem, an incomplete fix, or a process gap. |
| Past Actions | A history of previous actions taken on the issue, such as remediation attempts, status changes, or assignments. | Review prior work to avoid duplicate effort and understand what has already been tried. |
| Description | A technical explanation of the finding, including what was detected and where, with background on the affected resource or credential type and why it matters. | Use this to confirm the nature and scope of the finding before taking action. |
| Validation | Live verification details: current status (e.g., **Active!**), the method OX used to validate the finding (e.g., OX via API call), and the potential impact (e.g., potential compromise of system). | Use this to confirm the issue is real and exploitable. An **Active** status means the secret or exposure is still valid and must be remediated immediately. |
| Secret Details | Identifying metadata about the detected secret, such as the associated login or account and the secret type (for example, User or Service). | Use this to identify the owner and scope of the secret so you can coordinate revocation with the right team. |
---
# 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-dev-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.