> 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/cortex-xdr-5.x/reference-and-developer-docs/role-based-access-control/cloud-security-and-posture-management-permissions/application-security-permissions/application-security-issues-permissions.md).
# Application Security - Issues permissions
Configure permissions for Application Security issues.
Issues display security findings discovered across your code repositories, container images, and CI/CD pipelines. To view Issues, go to **Modules** → **Application Security** → **Issues**, and select one of the issues, such as IaC Misconfigurations, vulnerabilities, and Secrets.
| Permission | Description | Roles Example |
| ---------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| None | No access to Application Security Issues. | SOC Tier-1 Analyst: Focus on issue triage and initial case response. Application Security findings are not part of their primary workflow. |
| View | Read-only access to all issue categories. Users can browse, filter, search, and export issues. They can view issue details and findings. They cannot change issue status, assign issues, create exclusions, or trigger remediation. | - SOC Tier-2 and 3 Analysts: SOC Tier-2 analysts may need to investigate code-related cases or correlate AppSec findings with security issues.
- Threat Hunter: Needs to correlate code-level findings with threat intelligence and attack patterns.
|
| View/Edit | Full access to manage and remediate issues. Includes all View capabilities plus: change issue status, assign issues, create exclusions, trigger remediation, perform bulk operations, and add comments. | Security Engineer: Responsible for triaging, assigning, and remediating AppSec issues. |
**Required and recommended permissions**
Consider adding the following permissions:
| Permission | Permission Level | Reason |
| -------------- | ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Query Center | View or View/Edit | - View: Recommended. Run XQL queries on issue data for advanced investigation.
- View/Edit: Recommended. Execute custom queries against AppSec issue datasets.
|
| Cases & Issues | View or View/Edit | - View: Recommended. Link AppSec issues to incident cases for correlation.
- View/Edit: Recommended. Create incident cases directly from AppSec issues.
|
| Dashboards | Enabled | View AppSec issue summary widgets on dashboards. |
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://cortex-docs.paloaltonetworks.com/cortex-xdr-5.x/reference-and-developer-docs/role-based-access-control/cloud-security-and-posture-management-permissions/application-security-permissions/application-security-issues-permissions.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.