# A cloud governance framework for security has six layers, from account structure to evidence

Facts read 16 Nov 2026. Page reviewed 16 Nov 2026.

A security-focused cloud governance framework has six layers: account structure, baseline preventive guardrails, detective controls, exceptions, a test step, and evidence. Each cloud supplies native objects for every layer. In the library, 26 of 100 entries show no native test step found on 10 Nov 2026, mostly in Google Cloud.

## Each layer answers one question and maps to a native object

The table is a summary of documentation read on 16 Nov 2026. Layers 3 and 6 are the thinnest in the library, because this site covers preventive guardrails; detective mechanisms are named only where a cloud puts them next to a preventive one.

| Layer | Question it answers | AWS | Azure | Google Cloud |
| --- | --- | --- | --- | --- |
| 1. Structure | Where does a rule attach? | Organization, OUs, accounts | Management groups, subscriptions | Organization, folders, projects |
| 2. Baseline preventive | What is never allowed? | [SCP](/mechanisms/scp/), [RCP](/mechanisms/rcp/) | [Azure Policy](/mechanisms/azure-policy/) with deny | [Organization policy](/mechanisms/org-policy/), [IAM deny](/mechanisms/iam-deny/) |
| 3. Detective | What drifted anyway? | AWS Config rules (Control Tower detective controls) | Azure Policy with audit effect | Dry-run violations in audit logs; other detective tooling not read for this page |
| 4. Exceptions | Who may break a rule, and until when? | Principal tag or ARN conditions; Control Tower exempted parameters | Policy exemptions with expiresOn | Folder or project override, tag conditions |
| 5. Test | What does the rule break? | Test OU, policy simulator for SCPs | enforcementMode DoNotEnforce | Dry-run mode |
| 6. Evidence | Can you show the rule held? | Denies logged in CloudTrail | Compliance reporting and auditing | Audit logs of dry-run and enforced violations |

## Structure comes first because it decides how many rules you need

Microsoft recommends keeping the management group hierarchy reasonably flat, ideally no more than three to four levels, and states a limit of six levels of depth. It also recommends limiting the number of Azure Policy assignments at the root management group scope. AWS documents a 10,240 character ceiling per service control policy and a cap on how many SCPs attach to a root, OU or account. Those numbers shape every later layer.

See [landing zone guardrails for AWS](/landing-zone-guardrails-aws/) and [landing zone guardrails for Azure](/landing-zone-guardrails-azure/) for the structures each provider recommends.

## The test layer is where the three clouds differ most

The library records, for each of 100 entries, the native way to test before enforcing. For 26 of them the answer is "none found on 10 Nov 2026". Twenty-three are Google Cloud entries, and all 23 are legacy managed constraints, which Google documents as outside Policy Simulator and mostly outside dry-run mode. Two are Azure entries and one is AWS.

That makes the test layer the main reason an outside tool earns a place in the framework. The [Simulation Coverage Matrix](/simulation/) shows which platforms add a test step the clouds lack, and [testing a guardrail before you apply it](/guides/testing-a-guardrail-before-you-apply-it/) walks through the native options.

## A short order of work follows from the layers

The order is this page's own recommendation. It follows the documented limits above and is not taken from a single provider's guidance.

- Fix the structure first: one baseline attachment point per cloud, and a sandbox group with a looser set.
- Add the small number of rules that must never be broken, and read the breakage recorded for each entry before attaching it.
- Put every new rule through the cloud's test step, or a platform that adds one, before it is enforced.
- Give every exception an owner and an end date in whatever field or record the cloud allows.
- Keep the log that shows denials, so that the rule can be shown to have held.

## Exceptions and evidence are the layers audits ask about

A guardrail with a hard-coded exception is a guardrail with a permanent hole. Of the three clouds, only Azure documents an expiry field on its exception object in the pages read; see [guardrail exceptions and waivers](/guardrail-exceptions-and-waivers/). For rollout order across layers, see [rolling out guardrails without breaking production](/guides/rolling-out-guardrails-without-breaking-production/).

For evidence, AWS says a prevented action "is denied and logged in CloudTrail" and the resource is logged in AWS Config (AWS Control Tower documentation, read 10 Nov 2026). Microsoft lists compliance reporting and auditing as a deployment consideration. Google documents that dry-run violations are audit logged without blocking.

## Related pages

- [Guardrail exceptions and waivers in AWS, Azure and Google](/guardrail-exceptions-and-waivers/)
- [Landing zone guardrails for AWS: the Control Tower baseline](/landing-zone-guardrails-aws/)
- [Azure landing zone guardrails: policy by management group](/landing-zone-guardrails-azure/)
- [All of them](/guides/)

## Sources

- Microsoft: Azure governance design area: https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/ready/landing-zone/design-area/governance (read 16 Nov 2026)
- Microsoft: management groups in Azure landing zones: https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/ready/landing-zone/design-area/resource-org-management-groups (read 16 Nov 2026)
- Microsoft: Azure Policy assignment structure: https://learn.microsoft.com/en-us/azure/governance/policy/concepts/assignment-structure (read 16 Nov 2026)
- Microsoft: Azure Policy exemption structure: https://learn.microsoft.com/en-us/azure/governance/policy/concepts/exemption-structure (read 16 Nov 2026)
- Google Cloud: test organization policies in dry-run mode: https://cloud.google.com/resource-manager/docs/organization-policy/dry-run-policy (read 16 Nov 2026)
- AWS Control Tower: how controls work: https://docs.aws.amazon.com/controltower/latest/userguide/how-controls-work.html (read 10 Nov 2026)
- AWS Organizations: quotas and limits: https://docs.aws.amazon.com/organizations/latest/userguide/orgs_reference_limits.html (read 10 Nov 2026)
- Microsoft: Azure Policy audit effect: https://learn.microsoft.com/en-us/azure/governance/policy/concepts/effect-audit (read 16 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://cloudgovernancetools.com/cloud-governance-framework/
