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 Cloud Posture Management or Cortex Cloud Runtime Security with Application Security add-on.