> 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/code-security/application-security-scans-management/manage-scans-through-the-tenant-ui/branch-periodic-scans/references/reference-c-issue-category-routing.md).

# Reference C: Issue category routing

Each issue category tab in the scan side panel presents a distinct detection type that demands a distinct investigation. Use this table to route from the scan result to the guide that owns resolution for the category.

| Tab                   | Detection scope                                                                                                          | First evidence to check                                                                                                                      | Resolution guide                                                                                                                               |
| --------------------- | ------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
| **Vulnerabilities**   | Known CVE vulnerabilities in open-source dependencies resolved by the SCA scanner, including transitive dependencies.    | Whether a fix version exists, and whether the vulnerable package is reachable from application code.                                         | Investigate, prioritize, and remediate SCA CVE issues                                                                                          |
| **Configurations**    | IaC misconfigurations in Terraform, CloudFormation, Kubernetes, and Helm templates.                                      | The specific resource block and attribute in the template, and whether the template is deployed.                                             | Investigate, prioritize, and remediate IaC misconfiguration issues                                                                             |
| **Secrets**           | Hardcoded credentials, API keys, and tokens in the working tree, and in commit history when Git History Scan is enabled. | The validation status of the secret. A validated, active credential is a containment task with a rotation deadline, not a code-cleanup task. | Investigate, prioritize, and remediate secrets issues                                                                                          |
| **Package Integrity** | Package operational risk and license miscompliance detected by the SCA scanner.                                          | The operational risk rating and the license obligation of the affected package.                                                              | Investigate, prioritize, and remediate package operational risk issues and Investigate, prioritize, and remediate license miscompliance issues |

> **Note:** Package Operational Risk issues and License Miscompliance issues do not receive Urgency classification. Prioritize Package Integrity issues by the operational risk rating, the license obligation, and the presence of associated CVE vulnerabilities.


---

# 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/code-security/application-security-scans-management/manage-scans-through-the-tenant-ui/branch-periodic-scans/references/reference-c-issue-category-routing.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.