> 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/view-urgency-in-the-tenant.md).

# Review Application Security posture and remediate issues by Urgency

Use this workflow to review Application Security posture, prioritize issues by Urgency, and investigate issue details.

{% stepper %}
{% step %}

### Review Application Security posture

On the **AppSec Dashboard**, use the **Open Issues by Urgency and Scan Type** widget to review your application security posture. This widget highlights where open Urgent and Top Urgent issues are concentrated across four issue types: Vulnerabilities, IaC Misconfigurations, Secrets, and Code Weaknesses.

As the only view that visualizes urgency levels as posture data, it displays urgency by scanner type. For deeper context, individual metrics—such as Internet Exposed, CISA KEV, EPSS, and Is Deployed—are available in the issue side panel.
{% endstep %}

{% step %}

### Drill down to issues prioritized by Urgency

Use one of these paths to open issues prioritized by Urgency. The AppSec Dashboard filters results by specific Urgency levels (such as Top Urgent or Urgent) for a single scan type (such as Vulnerabilities). The ASPM Command Center displays issues by Urgency level across all scan types combined.

{% tabs %}
{% tab title="AppSec Dashboard" %}
Combine Urgency and scanner-type filters to focus triage on one issue type.

1. Locate the **Open Issues by Urgency and Scan type** widget.
2. Identify the scanner type with the highest concentration of **Top Urgent** and **Urgent** issues.
3. Select the relevant **Top Urgent** or **Urgent** segment. For example, select **Urgent** on the **Vulnerabilities** column.

**Result:** The issues table filters to the selected Urgency level and scanner type. Selecting **Urgent** on **Vulnerabilities** shows Urgent vulnerability issues only.
{% endtab %}

{% tab title="ASPM Command Center" %}
The Command Center does not display Urgency posture. It routes to issues prioritized by Urgency using a hidden filter.

1. Open the **ASPM Command Center** dashboard.
2. Optionally scope results with the **Application** filter and time range control.
3. Select the issues funnel to open the aggregation view.
4. On the **Prioritized** stage, select **View Prioritized Issues**.
5. Select **Currently open** or **All**.

**Result:** The issues table opens in a new browser tab with **Top Urgent** and **Urgent** issues across all scanner types. **Currently open** further filters results to **New** and **In Progress** issues.
{% endtab %}
{% endtabs %}
{% endstep %}

{% step %}

### Investigate issues in the side panel

Select an issue to open its side panel. Use the side panel to understand the **Urgency Details** and investigate issue context.

Confirm the Urgency badge, contributing metrics, and calculation freshness. A stale indicator appears when the calculation is over 12 hours older than the issue update.

If Urgency is Not Applicable, the engine retries during the next periodic scan. Review [Urgency metrics](/application-security/application-security-posture-management-aspm/urgency/urgency-metrics.md) for each metric's meaning.
{% endstep %}

{% step %}

### Remediate the issue

Find remediation in the dedicated **Remediation** section at the bottom of **Overview**, or in the dedicated **Resolution** tab (Recommended).
{% endstep %}
{% endstepper %}

### Issue-type references

Use these issue-type guides for detailed investigation and remediation steps:

* [Investigate and remediate CVE vulnerability issues](/application-security/code-security/code-security-scanners/software-composition-analysis-sca-scanners/software-composition-analysis-sca-vulnerability-issues/investigate-and-remediate-cve-vulnerability-issues.md)
* [Investigate and remediate secrets issues](/application-security/code-security/code-security-scanners/secrets-scans/investigate-and-remediate-secrets-issues.md)
* [Investigate and remediate IaC misconfiguration issues](/application-security/code-security/code-security-scanners/infrastructure-as-code-iac-misconfiguration-scanner/investigate-and-remediate-iac-misconfiguration-issues.md)
* [Investigate and remediate code weakness issues](/application-security/application-security-posture-management-aspm/manage-code-weakness-issues/investigate-and-remediate-code-weakness-issues.md)


---

# 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/view-urgency-in-the-tenant.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.