Study guide

14.2 AWS Control Tower Landing Zone & Guardrail Framework

AWS Certified Security – Specialty SCS-C03

Track your progress as you read

Finished sections get a check mark.

1 Chapter 0: Getting Started with the SCS-C03 Exam

0.1 SCS-C03 Exam Format, Domains & Study Strategy

2 Chapter 1: Security Monitoring, Alerting & Threat Detection Services

1.1 Workload Monitoring & Health Check Strategies 1.2 Amazon GuardDuty Architecture & Finding Types 1.3 AWS Security Hub & Automated Conformance Assessment 1.4 Amazon Macie & Automated Data Classification

3 Chapter 2: Enterprise Logging Architecture & Analysis

2.1 Multi-Account CloudTrail & Organization Trails 2.2 Amazon Security Lake & OCSF Log Normalization 2.3 Network Telemetry: VPC Flow Logs & Route 53 Resolver Logs 2.4 Troubleshooting Security Telemetry & Log Ingestion 2.5 Analyzing, Normalizing & Correlating Security Logs

4 Chapter 3: Incident Readiness, Response Planning & Automated Runbooks

3.1 Incident Response Planning & Blast Radius Mitigation 3.2 Testing & Validating Incident Response Plans 3.3 Automated Incident Remediation with EventBridge & Step Functions 3.4 Systems Manager OpsCenter & Incident Manager Runbooks

5 Chapter 4: Digital Forensics, Evidence Preservation & Root Cause Analysis

4.1 Forensic Artifact Capture & Chain of Custody 4.2 Threat Containment & Network Quarantine Techniques 4.3 Correlating Events & Root Cause Analysis with Amazon Detective

6 Chapter 5: Edge Protection, WAF & DDoS Mitigation

5.1 CloudFront Security Headers & Origin Access Control 5.2 AWS WAF Architecture & Advanced Rule Sets 5.3 AWS Shield Advanced & DDoS Defense Architectures 5.4 Edge Integrations: Managed Rule Groups, OCSF Ingestion, IoT Policies & CORS

7 Chapter 6: Compute Workload Hardening, Vulnerability Management & GenAI Security

6.1 Golden AMIs & Container Image Hardening Pipelines 6.2 Amazon Inspector Vulnerability Management & Patch Automation 6.3 Generative AI Security: Amazon Bedrock Guardrails & Model Protection 6.4 Instance Profiles, Service Roles & Execution Roles for Compute 6.5 Secure Administrative Access: Session Manager & EC2 Instance Connect

8 Chapter 7: Network Security, Segmentation, Private Connectivity & Encryption in Transit

7.1 Layered Traffic Filtering: SGs, NACLs & AWS Network Firewall 7.2 Hybrid Connectivity Security: VPN, Direct Connect & MACsec 7.3 Zero-Trust Access & Network Access Analysis 7.4 Enforcing Encryption in Transit: ELB Security Policies, TLS & HTTPS-Only Access 7.5 Private Access: VPC Endpoints, PrivateLink, Client VPN & Verified Access 7.6 Inter-Resource Encryption in Transit: Nitro, EMR, EKS & SageMaker AI

9 Chapter 8: Enterprise Authentication, Federation & Directory Services

8.1 AWS IAM Identity Center & Enterprise IdP Integration 8.2 Amazon Cognito User Pools & Identity Pools 8.3 AWS Security Token Service (STS) & Temporary Credential Workflows 8.4 Troubleshooting Identity & Authentication Failures

10 Chapter 9: Advanced Authorization Architecture & Policy Evaluation

9.1 Complete AWS Policy Evaluation Logic & Decision Flow 9.2 Permission Boundaries & Safe Admin Delegation 9.3 Attribute-Based Access Control (ABAC) with IAM Tags

11 Chapter 10: Least Privilege, Policy Validation & External Access Auditing

10.1 IAM Roles Anywhere & Amazon Verified Permissions 10.2 Auditing External & Unused Access with IAM Access Analyzer 10.3 Analyzing Authorization Failures & Policy Simulation

12 Chapter 11: Cryptographic Services: KMS Architecture & Key Governance

11.1 AWS KMS Architecture, Key Policies & Key Types 11.2 KMS Grants, Encryption Context & Multi-Region Keys 11.3 Imported Key Material (BYOK) & CloudHSM Key Stores

13 Chapter 12: Secrets Management, Sensitive Data Masking & PKI

12.1 AWS Secrets Manager & Systems Manager Parameter Store 12.2 Sensitive Data Masking in Telemetry & Messaging 12.3 AWS Certificate Manager (ACM) & Private CA Architecture

14 Chapter 13: Storage Encryption, Integrity, Lifecycle & Backup Protection

13.1 S3 Encryption Modes & S3 Bucket Keys 13.2 Data Integrity Protection: Object Lock, Vault Lock & Code Signing 13.3 Secure Data Lifecycle, Cross-Account Replication & Backup Vault Lock 13.4 Lifecycle, Backup & Secure Replication Beyond S3: EFS, FSx, DLM, DataSync & Air-Gapped Vaults

15 Chapter 14: Multi-Account Architecture, Organizations & Control Tower Governance

14.1 AWS Organizations Structure, Hierarchy & Resource Control 14.2 AWS Control Tower Landing Zone & Guardrail Framework 14.3 Delegated Administrator Architecture & Root User Governance 14.4 Centralized Resource Sharing with RAM & Service Catalog

16 Chapter 15: Compliance Automation, Infrastructure as Code Security & Auditing

15.1 Infrastructure as Code Security & Multi-Account Deployment 15.2 AWS Config, Conformance Packs & Automated Remediation 15.3 Audit Evidence Collection & Well-Architected Security Reviews

14.2 AWS Control Tower Landing Zone & Guardrail Framework

Key Takeaways Explain This Topic AI

AWS Control Tower orchestrates AWS Organizations, IAM Identity Center, AWS Config, and AWS CloudTrail to deploy an automated, multi-account landing zone with dedicated Log Archive and Audit accounts.

Control Tower controls are categorized by behavior into Preventive (enforced synchronously via Organizations SCPs), Detective (monitored asynchronously via AWS Config and Security Hub), and Proactive (evaluated pre-provisioning via AWS CloudFormation Hooks).

Control Tower controls have three guidance levels: Mandatory (always on and can't be removed, such as disallowing changes to AWS Config and CloudTrail set up by Control Tower), Strongly Recommended, and Elective.

Account Factory leverages AWS Service Catalog to automate standardized, compliant account vending with pre-configured networking, IAM baselines, and optional extension via Account Factory for Terraform (AFT) or Customizations for Control Tower (CfCT).

Governance drift occurs when resources Control Tower manages are changed outside it, such as an enrolled account moved between OUs or a managed SCP detached; remediation is re-registering the OU, updating the account, or resetting the landing zone.

Last updated: September 2026

14.2 AWS Control Tower Landing Zone & Guardrail Framework

Establishing a secure, production-ready multi-account foundation requires coordinating multiple foundational services, directory integrations, and compliance mechanisms. Manually wiring together AWS Organizations, IAM Identity Center, AWS Config, and CloudTrail across dozens of accounts introduces human error and operational drift. AWS Control Tower provides an automated service wrapper that provisions and manages a compliant multi-account Landing Zone according to AWS best practices.

Landing Zone Architecture & Core Baseline

A Control Tower Landing Zone automatically configures an orchestrated organizational hierarchy with specialized core accounts, centralized identity access, and pre-configured audit trails.

Loading diagram...

Foundational Accounts in the Core OU

Control Tower sets up two foundational member accounts within a Core (or Foundational) Organizational Unit:

Log Archive Account : Functions as the central immutable clearinghouse for organizational telemetry. It contains dedicated Amazon S3 buckets that aggregate multi-Region CloudTrail logs and AWS Config configuration history from every account in the organization. S3 Object Lock, strict bucket policies, and cross-account access restrictions prevent any single account administrator from tampering with historical audit evidence.

Audit Account (Security Tooling Account) : Serves as the operational hub for security operations center (SOC) analysts and compliance auditors. Control Tower automatically configures cross-account IAM roles granting read-only and remediation access into all member accounts from this account. It is the designated primary target for Delegated Administration of centralized security services.

Account Factory: Standardized Automated Account Vending

Account proliferation without automated governance creates security blind spots. Account Factory is the built-in account vending mechanism in AWS Control Tower. It standardizes account creation, network baselines, and security configurations across the enterprise.

How Account Factory Operates

Account Factory is delivered as an AWS Service Catalog product in the Management account:

Self-Service Vending : Authorized teams invoke the Account Factory product via the AWS Service Catalog console, API, or automated CI/CD pipelines.

Network Baselines : Account Factory automatically provisions a standardized VPC topology, specifies authorized CIDR blocks, creates public and private subnets, configures internet connectivity, and disables default VPCs across selected regions.

Identity Integration : Automatically integrates the new account with IAM Identity Center , mapping administrative and developer permission sets to federated directory groups.

Baseline Enrollment : Enrolls the account directly into the specified Organizational Unit, instantly inheriting all active guardrails and monitoring rules.

Extending Account Factory: CfCT and AFT

For enterprise infrastructure-as-code (IaC) governance, AWS provides two architectural extensions:

Customizations for AWS Control Tower (CfCT) : Uses AWS CodePipeline, AWS CodeCommit, and CloudFormation StackSets to deploy custom security baselines (such as custom IAM roles, default KMS keys, and endpoint monitors) across member accounts whenever a new account is vended or an OU is modified.

Account Factory for Terraform (AFT) : Enables platform engineering teams to define account vending and customization pipelines using Terraform. AFT provisions a dedicated pipeline architecture featuring an AFT management account, Git-driven workflow repositories, and DynamoDB state tracking.

Control Classifications: Guidance Levels

In AWS Control Tower, governance rules are formally termed Controls (formerly referred to as Guardrails). Control Tower classifies controls into three guidance categories:

Guidance Level Behavior & Enforcement Example Enterprise Rules

Mandatory Controls Automatically enabled when the Landing Zone is created. Cannot be disabled or bypassed. Enforces foundational organizational integrity. Disallow configuration changes to AWS Config and CloudTrail set up by Control Tower; Disallow deletion of the Log Archive and changes to its encryption and logging; Disallow changes to IAM roles, Lambda functions, and CloudWatch resources set up by Control Tower; Detect the public read setting of the Log Archive bucket.

Strongly Recommended Controls Based on enterprise security best practices and compliance standards (such as the CIS AWS Foundations Benchmark). Enabled by default or selectively applied to OUs. Detect whether public read access to Amazon S3 buckets is allowed; Detect whether MFA is enabled for the root user; Detect whether Amazon EBS volumes are encrypted; Disallow creation of access keys for the root user.

Elective Controls Optional, enterprise-specific guardrails. Security architects selectively activate elective controls based on specific compliance frameworks (NIST SP 800-53, PCI DSS). Disallow non-approved AWS regions; Disallow creation of internet gateways in workload subnets; Enforce specific customer managed KMS keys for S3 encryption.

Implementation Mechanisms: Preventive, Detective & Proactive

Control Tower implements governance controls through three distinct technical mechanisms across the resource lifecycle:

Loading diagram...

Comprehensive Mechanism Comparison

Attribute Preventive Controls Detective Controls Proactive Controls

Underlying Technology AWS Organizations Service Control Policies (SCPs) AWS Config Rules & AWS Security Hub Controls AWS CloudFormation Hooks

Enforcement Point Synchronous at AWS API execution. Asynchronous post-provisioning continuous monitoring. Pre-provisioning during CloudFormation stack creation or update.

Action on Non-Compliance Rejects the API call with an AccessDenied error; resource is never created. Records resource as NON_COMPLIANT in dashboards; optionally triggers automated remediation. Fails the CloudFormation hook check; stack deployment is aborted before resource provisioning starts.

Blast Radius Mitigation Maximum; prevents prohibited configurations from ever existing. Moderate; resource exists in a non-compliant state until detected and remediated. High; blocks non-compliant infrastructure-as-code templates in deployment pipelines.

Limitations Does not evaluate resource-level configuration attributes (e.g., checking if an existing volume is unencrypted). Does not apply to the Management account. Remediation lag (window of vulnerability between creation and detection). Only inspects resources provisioned via AWS CloudFormation; direct console or CLI API calls bypass hooks.

Proactive Governance via CloudFormation Hooks

A critical architectural innovation in modern landing zones is the adoption of Proactive Controls . In traditional environments, a developer might deploy an unencrypted Amazon S3 bucket via CloudFormation. A detective AWS Config rule evaluates the resource minutes later, flags it as non-compliant, and triggers a remediation Lambda function to encrypt the bucket or delete it. During that intervening window, unencrypted data may have already been written, creating a compliance breach.

CloudFormation Hooks intercept stack creation and update events in the deployment engine:

When a stack operation begins, CloudFormation invokes registered proactive hooks at the preCreate or preUpdate lifecycle points.

The hook evaluates the target resource configurations against defined compliance policies (such as verifying that BucketEncryption is enabled on AWS::S3::Bucket ).

If the configuration violates the policy, the hook returns a FAILURE status with a descriptive error message, causing CloudFormation to abort the stack operation and roll back before any cloud resource is instantiated.

Exam Tip : For the exam, recognize the lifecycle timing: Proactive controls stop non-compliant CloudFormation deployments before resources exist; Preventive controls block unauthorized API calls at execution time; Detective controls flag non-compliant resources after they are provisioned.

Managing Governance Drift & Baseline Re-Registration

Governance Drift occurs when the actual state of accounts, OUs, or guardrails within the organization diverges from the baseline configured by AWS Control Tower. Drift introduces hidden security exposures and audit non-compliance.

Common Sources of Drift

Manual Policy Alteration : An administrator with Management account access directly edits or detaches a Control Tower SCP in the AWS Organizations console.

Moved or Removed Member Account : An enrolled account is moved to another OU, or removed from the organization, in the Organizations console instead of through Control Tower.

Deleted Control Tower Resources : A Control Tower role, OU (such as the Security OU), or control is deleted or changed from outside Control Tower. (Member-account users can't simply turn off the Config recorder, because mandatory controls deny changes to Control Tower's AWS Config and CloudTrail settings.)

Landing Zone Version Lag : AWS releases updates to the Control Tower baseline that have not been applied to existing accounts.

Detecting and Remediating Drift

Console Visibility : Control Tower continuously audits organizational state and flags drifted components with a status of Drifted in the Landing Zone dashboard.

Re-registering an OU : When drift occurs at the OU level (for example, if member accounts within an OU lack mandatory SCPs or baseline roles), the administrator executes Re-register OU in the Control Tower console. This action reapplies all baseline configurations, provisions missing StackSets, and attaches mandatory guardrails across all accounts in that OU.

Updating the Account or Landing Zone : A moved account is fixed by updating it in Account Factory (or re-registering its OU). Landing-zone-level drift, such as a deleted Security OU account or role, is fixed with Reset or a landing zone update , which is also how you adopt new landing zone versions.

Specialty Exam Traps & Architectural Pitfalls

Relying Solely on Preventive Controls for Compliance Audits : Preventive controls (SCPs) prevent unauthorized API actions, but they cannot report on the compliance posture of existing resources created before the SCP was attached. True compliance requires Detective controls (AWS Config) to audit historical and current resource state.

Assuming Proactive Controls Block Direct AWS CLI Calls : CloudFormation Hooks only evaluate infrastructure deployed via AWS CloudFormation. If a developer uses the AWS CLI to execute aws s3api create-bucket , the proactive hook is completely bypassed. To block direct manual resource creation, organizations must enforce Preventive controls (SCPs) that restrict direct provisioning permissions.

Resolving Drift by Deleting Accounts : When Control Tower reports an account or OU as drifted, never delete or disassociate the account. The standard, non-destructive resolution is to use the Re-register OU or Enroll Account action in the Control Tower console.

Preventive Guardrail Immunity in the Management Account : Control Tower preventive guardrails (SCPs) do not apply to the Management account. If a workload is mistakenly deployed into the Management account, it will operate completely unconstrained by Control Tower preventive guardrails.

Loading diagram... Control Tower Multi-Account Governance & Control Lifecycle