> 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/xsiam-api/unified-rules/unified-rules-overview.md). # Unified Rules overview The Unified Rules APIs let you manage linked Cloud Security and AppSec rule pairs through a single unified endpoint. Each unified rule consists of two linked rules: * A **Cloud Security rule** that detects misconfigurations in deployed cloud infrastructure at runtime. * A linked **AppSec IaC rule** that detects the same misconfiguration in Infrastructure as Code (IaC) before deployment. Managing both rules as a single unit lets you enforce a security control consistently across the software development lifecycle — from code, to build, to runtime. ## Primary identifier The **AppSec rule ID** is the primary identifier for all unified rule operations. It is returned as the top-level `id` field in list, create, and get responses, and is used as the `ruleId` path parameter for get, update, and delete operations. ## Atomic create and delete Creating a unified rule is an atomic operation: the Cloud Security rule is created first, then the AppSec rule is created with the Cloud Security rule ID automatically injected to link the two. If the AppSec rule creation fails, the Cloud Security rule is automatically rolled back to prevent orphaned rules. Deleting a unified rule removes both rules. If one deletion succeeds and the other fails, the AppSec rule is always deleted first, followed by the linked Cloud Security rule. If the AppSec rule is deleted successfully but the subsequent Cloud Security rule deletion fails, the endpoint returns a `207 Multi-Status` response with per-rule status details, and the Cloud Security rule may be left orphaned. There is no scenario where the Cloud Security rule is deleted but the AppSec rule deletion fails. ## Required license Cortex XSIAM Premium. In Cortex XSIAM Enterprise and Cortex NG SIEM, requires the Cortex Cloud Posture Management add-on. Some APIs also require the AppSec add-on. --- # 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/xsiam-api/unified-rules/unified-rules-overview.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.