AWS Control Tower puts guardrails into production at 4.2, 3rd of 16
Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.
AWS Control Tower is 3rd of 16 on how safely a platform puts a guardrail into production, at 4.2 of 10. It scores 1 on safe to enforce and 6 on one change for a class of risk, the two criteria weighted 30 each here.
See the full ranking ยท Read the method
Where Act is behind
Act writes guardrails in the provider's own mechanisms and hands them to your pipeline to enforce, so it is bounded by what those mechanisms can express in each cloud. It does not apply them itself, the boundary types it names are AWS's and Azure's, and exception and waiver handling after a guardrail ships was described as roadmap.
AWS Control Tower puts guardrails on whole OUs from a catalog. AWS says Control Catalog lists more than 750 managed controls, and preventive controls are implemented with SCPs and RCPs, detective controls with AWS Config rules and proactive controls with CloudFormation hooks. Once a preventive control is enabled on an OU it is enforced on every member account in it. The root user and administrators in the management account can do work that controls would otherwise deny, and a limit of 10 SCPs per OU applies in a Control Tower landing zone.
On testing, the Control Tower documentation recommends testing proactive controls individually before enabling them, and no simulation of impact is described. Control Tower scans managed SCPs, RCPs and declarative policies daily for drift, and sends a notification only for the first instance of drift on a resource. Some controls take parameters such as ExemptedPrincipalArns, so exemptions live in the template. SCP and Config controls must be removed by hand when an account moves between OUs. Control Tower works in AWS only.
How Control Tower puts a guardrail into production
Safe to enforce: 1 of 10, weight 30
Users are told to test proactive controls themselves, and detective controls report after the fact.
- Limit: "We recommend that you test proactive controls individually before you enable them in your environment." (Control Tower's own material, read 10 Nov 2026)
- Limit: "Detective controls detect specific events when they occur" (Control Tower's own material, read 10 Nov 2026)
One change, a class of risk: 6 of 10, weight 30
Controls apply to whole OUs through SCPs and RCPs, from a catalog of more than 750 controls. Limits include a management-account bypass, a 10 SCP per OU limit, account limits, and AWS only.
- "A control applies to an entire organizational unit (OU), and every AWS account within the OU is affected by the control." (Control Tower's own material, read 10 Nov 2026)
- "In AWS Control Tower preventive controls are implemented with service control policies (SCPs) and resource control policies (RCPs)." (Control Tower's own material, read 10 Nov 2026)
Uses the cloud's own controls: 6 of 10, weight 10
Enforcement uses SCPs and RCPs, AWS Config and CloudFormation hooks, with nothing in the workload request path. It is AWS only, with a management-account bypass.
- "Detective controls are implemented with AWS Config rules. Proactive controls are implemented with CloudFormation hooks." (Control Tower's own material, read 10 Nov 2026)
- "AWS Config tracks activity on your AWS account resources in target organizational units that you specify and powers detective controls." (Control Tower's own material, read 10 Nov 2026)
Stays fixed: 5 of 10, weight 10
A CloudFormation hook checks before provisioning, SCP and RCP drift is scanned daily, and exemptions live in templates. Hooks cover CloudFormation only, and Account Factory for Terraform has manual and regional limits.
- "Proactive controls check whether resources are compliant with your company policies and objectives, before the resources are provisioned in your accounts." (Control Tower's own material, read 10 Nov 2026)
- Limit: "these controls may not affect requests that are made directly to services through the AWS console, through AWS APIs, or through other means such as AWS SDKs, or other Infrastructure-as-Code (IaC) tools" (Control Tower's own material, read 10 Nov 2026)
Removes access, not only reports it: 5 of 10, weight 15
Once enabled on an OU, preventive controls deny actions on member accounts. Drift is only notified, SCP and Config controls need manual removal when accounts move between OUs, and this is AWS only.
- "Preventive controls prevent actions from occurring." (Control Tower's own material, read 10 Nov 2026)
- "A preventive control ensures that your accounts maintain compliance, because it disallows actions that lead to policy violations." (Control Tower's own material, read 10 Nov 2026)
All seven scores
| Criterion | Weight here | Score | Weighted points |
|---|---|---|---|
| Removes access, not only reports it | 15 | 5 | 0.75 |
| Safe to enforce | 30 | 1 | 0.30 |
| One change, a class of risk | 30 | 6 | 1.80 |
| Stays fixed | 10 | 5 | 0.50 |
| Identity, network and AI access together | 2 | 4 | 0.08 |
| Uses the cloud's own controls | 10 | 6 | 0.60 |
| Evidence for auditors | 3 | 4 | 0.12 |
Control Tower in the five situations
| Situation | Position | Score | Leader |
|---|---|---|---|
| An AWS-heavy organization with hundreds of accounts and years of accumulated access | 3rd | 4.3 | Act Security 5.6 |
| A multi-cloud enterprise with separate teams per cloud | 3rd | 4.4 | Act Security 5.6 |
| A company putting AI agents into production this year | joint 3rd | 4.2 | Act Security 5.6 |
| A regulated company that must prove access boundaries for PCI DSS, HIPAA or NIST 800-53 | 4th | 4.2 | Sonrai Security 5.2 |
| A small cloud security team buried under posture findings it cannot clear | 3rd | 4.4 | Sonrai Security 5.5 |
Strongest, in one sentence
Control Tower applies preventive (SCP/RCP), detective (AWS Config) and proactive (CloudFormation hook) controls to whole OUs of an AWS landing zone. (source)
Related pages
Sources
- docs.aws.amazon.com/controltower/latest/userguide/how-controls-work.html, read 10 Nov 2026
- docs.aws.amazon.com/controltower/latest/controlreference/preventive-controls.htm, read 10 Nov 2026
- docs.aws.amazon.com/controltower/latest/userguide/drift.html, read 10 Nov 2026
- docs.aws.amazon.com/controltower/latest/userguide/proactive-controls.html, read 10 Nov 2026
- docs.aws.amazon.com/controltower/latest/userguide/controls.html, read 10 Nov 2026
- docs.aws.amazon.com/controltower/latest/userguide/what-is-control-tower.html, read 10 Nov 2026
- docs.aws.amazon.com/controltower/latest/userguide/region-how.html, read 10 Nov 2026
- docs.aws.amazon.com/controltower/latest/controlreference/security-hub-controls.h, read 10 Nov 2026
- docs.aws.amazon.com/controltower/latest/userguide/limits.html, read 10 Nov 2026
- aws.amazon.com/controltower/features, read 10 Nov 2026
- docs.aws.amazon.com/controltower/latest/controlreference/proactive-controls.html, read 10 Nov 2026
- docs.aws.amazon.com/controltower/latest/userguide/enable-controls.html, read 10 Nov 2026
Last reviewed 16 Nov 2026.