# Issue Details: Context

The Context tab shows the contextual risk signals that influence the issue's final severity, organized into categories that describe how reachable, exploitable, and damaging the issue is.

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

Use this tab to understand why the issue was prioritized at its current severity and which real-world risk factors are driving that score. A red up-arrow (↑) next to a signal indicates that it raises severity.

| Section                                      | What it shows                                                                                                                                                                                                      | How to use                                                                                                                                                        |
| -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Severity change banner                       | A summary of the severity adjustment, including the original severity, the final issue severity, and who or what changed it (for example, **Severity changed from High to Appoxalypse by OX**).                    | Use this to quickly see how OX adjusted the severity from the default and confirm the resulting priority.                                                         |
| Context influencing the Final Issue Severity | The specific severity factor(s) that drove the final score, with an explanation of the underlying rule (for example, Severity Factor "Active Secret in Exposed Cloud Asset" always sets severity to appoxalypse).  | Use this to understand the reasoning behind the severity decision and to validate whether the factor still applies to the affected resource.                      |
| Reachable                                    | Context signals indicating whether the affected asset can be reached by an attacker, such as **Internet Exposure** or **Secret of a SaaS**.                                                                        | Use this to assess accessibility — issues that are reachable from the internet or via an external SaaS are more likely to be exploited and should be prioritized. |
| Exploitable                                  | Context signals indicating how easily the issue can be exploited, such as **Active Secret in Exposed Cloud Asset**, **Base64 Encoded Secret**, **Single Factor Authentication**, or **High Confidence Detection**. | Use this to gauge attacker effort — multiple exploitable signals raise the likelihood of successful abuse and reduce the time you have to respond.                |
| Damage                                       | Context signals indicating the potential blast radius if the issue is exploited, such as **SCM Secret**, **Sensitive Data**, or **Lateral Movement**.                                                              | Use this to estimate impact — these signals describe what an attacker could access, expose, or pivot to after a successful exploit.                               |

Expand any signal in the Reachable, Exploitable, or Damage sections to view the underlying evidence and the resources that triggered it.


---

# 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-context.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.