> 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/ci-scans/references/reference-e-issue-category-routing.md).

# Reference E: Issue category routing

Each issue category tab presents a distinct detection type. Use this table to route a CI scan result to the owning resolution guide.

| Tab                   | Detection scope                                                                                             | First evidence to check                                                         | Resolution guide                                                       |
| --------------------- | ----------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------- | ---------------------------------------------------------------------- |
| **Vulnerabilities**   | Known CVE vulnerabilities in dependencies resolved during the build. This includes transitive dependencies. | Whether a fix version exists. Confirm the dependency resolved during the build. | Investigate, prioritize, and remediate SCA CVE issues.                 |
| **Configurations**    | IaC misconfigurations in Terraform, CloudFormation, Kubernetes, and Helm templates.                         | The resource block and attribute in the template.                               | Investigate, prioritize, and remediate IaC misconfiguration issues.    |
| **Secrets**           | Hardcoded credentials, API keys, and tokens.                                                                | The secret validation status. Rotate credentials that reach the build stage.    | Investigate, prioritize, and remediate secrets issues.                 |
| **Package Integrity** | Package operational risk and license miscompliance.                                                         | The license obligation and package operational-risk rating.                     | Investigate package operational-risk and license-miscompliance issues. |


---

# 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/ci-scans/references/reference-e-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.