> 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/application-security-rules/rules-inventory.md). # Rules inventory The AppSec rules inventory includes both out-of-the-box (OOTB) and custom rules. You can view and manage these rules via the UI or programmatically. **UI workflow** To access Cortex Cloud Application Security rules in the tenant, under **Modules** select **Application Security** → **AppSec Rules (under Policy Management)**. The Cortex Cloud Application Security rules inventory includes both out-of-the-box and custom rules. The following list describes rules fields/properties displayed in the inventory table. By default, rules are displayed according to severity and then alphabetically. Details are provided for properties that require explanation. You can enable or disable rules by checking the box next to the rule name in the table. | Attribute/Property | Description | | -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Rule Name | The rule name | | Rule Description | A description of the rule | | Severity | The severity level assigned to findings identified by the rule | | Scanner | The type of Application Security scanner configured to detect violations of this rule | | Policies Count | The amount of policies that included the rule in its configuration | | Last modified | The date and time when the rule was most recently updated | | Labels | Labels assigned to the rule | | Framework/Language | The framework or language that the detection rule applies to (for example, GitHub, Terraform, JavaScript) | | Issues Count | The amount of issues generated from findings detected by the rule. Select the value to navigate directly to the dedicated Issues page for the corresponding scan type, Filtered by the issues detected by the rule | | Mapped Cloud Security Rule | The corresponding Cloud Security Posture Management (CSPM) rule ID that is linked to this Application Security rule. This mapping enables unified policy enforcement and ensures consistent security governance from code to cloud | **How to search for Cortex Cloud Application Security rules** Use filters to find specific rules or categories. Example 3. Examples * To filter rules relating to Secrets, select **filter icon** → **Scanner (from the Select field)** → **Secrets (from the Value field)**. * To view custom rules only, select **Mode** from the **Select field**, **not equals** as the operator, and **Out-of -the-box** as the value * Sort rules according to their attributes, such as issue severity, to prioritize remediation efforts **API workflow** Use the **List rules** and **Get rule by ID** API operations when you need to conduct programmatic audits of your detection coverage at scale. The API allows you to automatically filter rules by scanner, severity, category, or compliance standard. This is recommended when you need to export rule inventories to generate compliance reporting and audit evidence. Additionally, you can use the **Get AppSec rule labels** operation to programmatically fetch all distinct labels currently applied across your inventory, making it easier to audit your organizational tagging strategy. For information on endpoint details, refer to [API documentation for AppSec rules](https://docs-cortex.paloaltonetworks.com/r/Cortex-Cloud-Platform-APIs/Rules?tocId=3PQghuZNXt_W1txFRRaU6w). --- # 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/application-security-rules/rules-inventory.md?ask=&goal= ``` `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.