> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/application-security/application-security-posture-management-aspm/urgency/prioritize-issues-by-urgency-levels.md).

# Prioritize issue types by Urgency level

The following table describes the urgency classification criteria for each scanner type:

| Issue Type                | Top Urgent                                                                                                                   | Urgent                                                                                 | Not Urgent                                                                                                           | Not Applicable                                                                           |
| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- |
| **Vulnerabilities**       | High EPSS score, listed in CISA KEV, deployed to production, internet-exposed, critical application, active exploit maturity | Moderate EPSS score, fixable, deployed to staging, or moderate application criticality | Low EPSS score, not reachable, not deployed, or development/testing environment with low application criticality     | No code to cloudtrace and no SCA-specific signals (EPSS, KEV, Reachability) available    |
| **Secrets**               | Valid or Privileged validation, public repository, deployed to production, critical application                              | Valid validation, private repository, or staging environment                           | Not validated (Unavailable), private repository, or development/testing environment with low application criticality | No code to cloudtrace and no secrets-specific signals (validation, visibility) available |
| **IaC Misconfigurations** | Deployed to production, internet-exposed, critical application                                                               | Deployed to staging, or moderate application criticality                               | Not deployed, or development/testing environment with low application criticality                                    | No code to cloud trace                                                                   |
| **Code Weaknesses**       | CWE Top 25 membership, deployed to production, internet-exposed, critical applications                                       | OWASP Top 10 membership, deployed to staging, or moderate application criticality      | Not deployed, or development/testing environment with low application criticality                                    | No code to cloud trace                                                                   |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/application-security/application-security-posture-management-aspm/urgency/prioritize-issues-by-urgency-levels.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.