Revisions & Diff

Policy revisions track how controls change over time and provide side‑by‑side comparisons for review and troubleshooting.

What Is a Policy Revision?

Every time you change the code of a Compliance Engine policy, Cloudaware records a policy revision. Each revision captures:

• The version of the policy code.
• The time the change was made.
• Who made the change (subject to platform configuration).

Revisions provide an audit trail so you can answer “what changed?” when findings or behavior shift.

Reviewing and Comparing Revisions

From the policy editor you can:

• Open the Revisions view to see the history of changes.
• Use Compare mode to see two versions side by side with highlighted differences.

Compare mode is useful when:

• A change causes unexpected findings.
• You need to review a colleague’s modifications.
• Auditors ask for evidence of how a control evolved.

Cloning from a Revision

You can clone a revision into a new policy. This is helpful when:

• You want a safe copy of a control before experimenting with changes.
• You need a variant of an existing policy with different scope or thresholds.

Cloned policies can be deployed and scheduled independently while still preserving the original version.

Versioning Practices

When working with policy revisions:

• Treat changes to scope and logic as significant and review them with stakeholders.
• Use clear descriptions for changes so future reviewers understand why they were made.
• Avoid frequent, unreviewed edits to high‑impact policies; group changes into reviewed batches instead.

Revisions and diff utilities together give you a change history that supports both operational troubleshooting and formal audits.