> 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/unified-application-security-policies/view-and-manage-policy-details.md).

# View and manage policy details

Select a policy row in the table to open the policy side card. The side card displays:

* **Policy configuration summary**: Name, description, policy type, conditions, scope, triggers, and actions
* **Efficiency metrics**: Issues created (total and last seven days), PRs blocked (total and last seven days), CI pipelines blocked (total and last seven days)
* **Editor metadata**: Created by, modified by, creation date, and last modified date

**View policy-driven issues**

* Select **Open Issues** under **Efficiency** from the policy side card to redirect to the All Issues table under the Application Issues module
* Navigate to the issues table filtered by the policy name

The issues table is filtered by the issues created by the selected policy.Unified Application Security Policies create issues in the consolidated **All** AppSec Issues table. Navigate to **Modules** → **Application Security** → **Issues** → **All**.

The **All Issues** table applies the following default filters:

* **Code Scan Source**: **Branch** (except for the Malware tab)
* **Status !** = **resolved**
* **Excluded** = **No**

**Blocking policy visibility in scan tables**

To view how blocking policies surface in scan results, navigate to **Modules** → **Application Security** → **Scans**. The Pull Request Scans and CI Scans tables display blocking policy information:

| Column              | Description                                                     |
| ------------------- | --------------------------------------------------------------- |
| Blocking Policies   | Names of all policies that triggered a block action on the scan |
| Blocking Policy IDs | IDs of all policies that triggered a block action on the scan   |

Surfacing these results enables you to trace which policy blocked a specific PR or CI pipeline and navigate to the policy configuration for review or adjustment.

**Manage existing policies**

* **Edit a policy**: Select the policy row and select **Edit** from the actions menu. The policy wizard opens in edit mode with the current configuration pre-populated. Out-of-the-box (OOTB) policies have limited editability, only the status (enable/disable) and certain trigger configurations can be modified
* **Enable/Disable a policy**: Select the policy row and select **Enable** or **Disable** from the actions menu. Disabled policies stop evaluating findings. Enabling a previously disabled policy resumes evaluation during the next scan cycle
* **Duplicate a policy**: Select the policy row and select **Duplicate** from the actions menu. The wizard opens with the source policy configuration pre-populated and a new name. Duplication is available only for policies marked as clonable
* **Delete a policy**: Select the policy row and select **Delete** from the actions menu

  <div data-gb-custom-block data-tag="hint" data-style="warning" class="hint hint-warning"><h3>Caution</h3><p>Deleting a policy closes all issues created by that policy during the next periodic scan. This action cannot be undone. Consider disabling the policy instead of deleting the policy to preserve issue history.</p></div>


---

# 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/unified-application-security-policies/view-and-manage-policy-details.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.