Cloud governance, in its security sense, is a set of rules the cloud itself enforces on every account
Facts read 16 Nov 2026. Page reviewed 16 Nov 2026.
Cloud governance for security is the practice of setting rules once, high in the account hierarchy, so AWS, Azure or Google Cloud applies them to every account beneath. This site covers the preventive layer: 100 documented guardrails, read 16 Nov 2026. Cost governance and posture reporting are separate subjects.
Cloud security governance sets limits at the top and lets the cloud apply them
The definition used on this site is narrow. Cloud governance is the set of policies attached at the top of an account hierarchy, such as an AWS organization root, an Azure management group or a Google Cloud organization, that limit what the accounts below can do. The cloud evaluates them on every request, so no team has to remember them.
Microsoft frames the same idea as a replacement for review meetings. Its Cloud Adoption Framework says Azure Policy "replaces such reviews with automated guardrails and adherence audits" (Microsoft documentation, read 16 Nov 2026). AWS says its Organizations service lets you apply policies for governance across accounts, and calls accounts natural boundaries for permission and security.
This site covers the guardrail layer, which is one of three jobs governance is asked to do
People who search for cloud governance usually mean one of three jobs: spending limits, a report of what is misconfigured, or rules that stop a bad change. This site covers the third. Cost governance is out of scope, and a report of misconfigurations is a different tool category than the policies that prevent them.
The library holds 100 entries: 40 for AWS, 30 for Azure and 30 for Google Cloud. The largest risk classes are AI services with 19 entries, identity and privilege with 14 and encryption and keys with 13. Each entry names what it blocks and what it breaks, with the source of both.
| Cloud | Where the rule is attached | Rule objects in the library |
|---|---|---|
| AWS | Organization root, OU or account | SCP, RCP, declarative policy, permissions boundary |
| Azure | Management group, subscription or resource group | Azure Policy, deny assignment, resource lock |
| Google Cloud | Organization, folder or project | Organization policy, IAM deny, principal access boundary, VPC Service Controls |
Governance is judged by what it stops, what it breaks and how fast it can be changed
A program is only as good as its three properties. It must stop the thing it names. It must break little else, and it must say what it breaks. And a rule must be changeable without a week of testing, which is why the ranking on this site weights safe enforcement and one change per class of risk at 30 each. The method publishes all seven weights.
A single account is not governed by this definition, because there is nothing above it to attach a rule to. The case starts at two accounts: one holding the rule, one receiving it.
A governance rule is a denial with a cost, so the cost is part of the definition
A guardrail answers a request with a denial. That is its value and its risk. The glossary defines a guardrail as a policy that sets limits without granting any permission. A rule that blocks the wrong request stops legitimate work, which is why every library entry lists the breakage as well as the benefit.
Take Deny member accounts leaving the organization. It has no exception condition, so it applies to every user, role and root user in the affected member accounts. AWS documents that service control policies do not affect the management account. Governance in this sense is writing such a rule, knowing where it stops, and testing it before it ships.
The next steps are a framework, a rollout plan and a choice of tools
For the layers a program needs, read a cloud governance framework for security. For the spread of rules across three clouds, read multi cloud governance. For how platforms are ranked on getting a rule into production safely, read the method.
Related pages
Sources
- Microsoft: Azure governance design area, read 16 Nov 2026
- AWS Organizations: what is AWS Organizations, read 16 Nov 2026
- AWS Organizations: service control policies, read 16 Nov 2026
- Google Cloud: resource hierarchy, read 16 Nov 2026
Last reviewed 16 Nov 2026.