Compliance Policies

Compliance policies are the core building block of Cloudaware Compliance Engine. Each policy defines a control, the assets it applies to, and how compliance is evaluated and recorded. Use policies to express requirements such as “all production S3 buckets must be encrypted,” “critical workloads must have backups,” or “IAM users must rotate keys regularly.”

Cloudaware provides:

• Benchmark policies that implement CIS and similar standards across AWS, Azure, and GCP.
• Cloudaware‑authored policies for security, reliability, operational excellence, and cost optimization.
• Custom policies that you write to enforce your own internal standards using Cloudaware’s policy language.

Refer to the guides below to explore how policies are structured, deployed, versioned, and connected to alerts and shared logic.

Policy Anatomy

Understand the main parts of a policy, including target objects, scope, evaluation logic, output statuses, and metadata.

Policy Deployment

Use this guide when you are ready to deploy policies from templates, scope them to environments or accounts, schedule evaluations, and roll out new controls safely.

Status Transitions

Understand how policy findings move between compliant, incompliant, inapplicable, and closed states over time.

Revisions & Diff

Use this guide when reviewing policy changes, comparing revisions, cloning from prior versions, or defining versioning practices.

Utility Classes

Reuse shared helper logic across policies, standardize calculations, and keep complex policy code easier to maintain.