> 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/software-supply-chain-security/governance-and-enforcement/cicd-rules/cicd-rules-inventory.md). # CI/CD rules inventory The CI/CD rules inventory includes both out-of-the-box and custom rules. ## How to access the CI/CD rules inventory 1. Under **Modules**, select **Application Security** → **AppSec Rules (under Policy Management)**. 2. In the Filter panel, select **Scanner** → **CI/CD Security**. The following list lists the exposed AppSec Rules table properties. Additional settings are found under **Menu settings**. | Field/Property | Description | | -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Severity | The priority level assigned to findings identified by the rule | | Rule Name | The rule name | | Rule Description | A description of the rule | | Framework/Language | The framework or language that the detection rule applies to (for example, GitHub, Terraform, JavaScript) | | Labels | Labels assigned to the rule | | Policies Count | The amount of policies that include the rule. Selecting the count redirects to the AppSec Policies page, sorted by the policies associated with the rule | | Issues Count | The amount of issues detected by the rule. Selecting the count redirects to the CI/CD Risks page, sorted by the issues detected by the rule | | Scanner | CI/CD Security. This value is immutable | | Last modified | The date and time when the rule was most recently updated | | Mapped Cloud Security Rule | The specific runtime cloud security policy that correlates with this AppSec rule. This mapping enables you to trace a security issue from its definition in code to its manifestation in the live cloud environment, ensuring end-to-end visibility | --- # 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/application-security/software-supply-chain-security/governance-and-enforcement/cicd-rules/cicd-rules-inventory.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.