Study guide
14.3 Delegated Administrator Architecture & Root User Governance
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.3 Delegated Administrator Architecture & Root User Governance
Key Takeaways Explain This Topic AI
The Delegated Administrator model isolates day-to-day security management from the Management account, designating dedicated Security Tooling and Audit accounts to manage services such as Security Hub, GuardDuty, Macie, Inspector, and IAM Access Analyzer.
AWS Firewall Manager requires AWS Organizations with all features, a designated Firewall Manager administrator account (a delegated member account is recommended), and AWS Config recording in the member accounts and Regions it protects.
Management account root credentials cannot be restricted by SCPs and must be secured by eliminating long-term access keys, enforcing FIDO2 hardware MFA, and storing complex vault credentials under dual-custody protocols.
Member account root users are subject to SCPs; with IAM centralized root access, the management account or IAM delegated administrator can delete member root credentials and run privileged tasks through short sts:AssumeRoot sessions.
Automated incident response architectures intercept root user API calls via Amazon CloudTrail, Amazon EventBridge rule patterns matching userIdentity.type = 'Root', and Amazon SNS notifications to alert security teams immediately upon root execution.
Last updated: September 2026
14.3 Delegated Administrator Architecture & Root User Governance
A cardinal rule of enterprise cloud security is the separation of administrative duties . The AWS Organizations Management account holds ultimate authority over organizational structure, consolidated billing, and account membership. Granting security operations personnel day-to-day access to the Management account introduces catastrophic blast radius risks: a single compromised credential or operational error could sever organization-wide networking, detach governance policies, or alter billing relationships.
AWS resolves this challenge through the Delegated Administrator framework, allowing organizations to assign operational management of individual AWS security services to dedicated member accounts. Concurrently, strict Root User Governance guarantees that emergency credentials remain hardened, audited, and strictly confined to authorized break-glass scenarios.
The Delegated Administrator Model & Blast Radius Isolation
The Delegated Administrator model decouples organizational ownership from day-to-day security operations. The Management account retains sole authority to designate which member account administers each service, but operational engineering and monitoring take place entirely within dedicated security accounts.
Loading diagram...
Dedicated Account Separation
AWS architectural best practices mandate two dedicated security-related accounts in the Core OU:
Security Tooling Account (Delegated Administrator) : The active operational account used by the SecOps team. It hosts the delegated administrator roles for automated threat detection, vulnerability scanning, data classification, and centralized firewall management.
Log Archive Account : The passive repository account. It holds the read-only, air-gapped S3 buckets receiving CloudTrail logs, AWS Config history, and VPC Flow Logs. Security analysts have read-only access to investigate forensic data without possessing permissions to modify logging infrastructure.
Service-by-Service Delegated Administration
Each major AWS security service supports delegated administration, enabling centralized policy deployment and finding aggregation across all accounts and regions.
Service Delegated Admin Capabilities Key Administrative Features
AWS Security Hub Centralized CSPM & findings dashboard. Aggregates findings from GuardDuty, Macie, Inspector, IAM Access Analyzer, and third-party tools across all accounts and regions. Enables security standards (CIS Benchmark, PCI DSS, AWS Foundational Security Best Practices). Automatically enables Security Hub in new accounts.
Amazon GuardDuty Intelligent threat detection engine. Automatically enables GuardDuty in existing and newly created member accounts. Manages threat intelligence sets (custom IP feeds) and trusted IP lists. Centrally administers S3 protection, EKS runtime monitoring, RDS login activity, Lambda network profiling, and EBS malware protection.
Amazon Macie Sensitive data discovery & DLP. Centrally evaluates sensitive data posture across all Amazon S3 buckets in the organization. Defines and executes scheduled discovery jobs across member accounts. Configures custom data identifiers (regex and keyword criteria for proprietary data types).
Amazon Inspector Automated vulnerability management. Centrally manages automated, continuous vulnerability assessments for Amazon EC2 instances, Amazon ECR container images, and AWS Lambda functions. Automatically enables scanning in new accounts and aggregates Common Vulnerabilities and Exposures (CVE) findings.
IAM Access Analyzer Identity governance & unused access. Configures an organization-level External Access Analyzer to identify resources (S3, IAM roles, KMS, SQS, Secrets Manager) shared outside the AWS Organization. Configures an Unused Access Analyzer to flag unused IAM roles, access keys, and excessive permissions across member accounts.
AWS Firewall Manager Centralized network security policy enforcement. Centrally configures and deploys AWS WAF WebACLs, AWS Shield Advanced protections, VPC Security Group baselines, and AWS Network Firewall rules across all accounts, VPCs, and ALBs.
AWS Firewall Manager Prerequisites & Policy Enforcement
AWS Firewall Manager is a frequent focus on the AWS Certified Security – Specialty exam because it has strict, mandatory prerequisites that must be satisfied before any policy can be created:
Organizations All Features : The organization must be configured with All Features enabled (Consolidated Billing only is insufficient).
Designated Delegated Administrator : The Management account must designate a member account (typically the Security Tooling account) as the Firewall Manager administrator via the Organizations or Firewall Manager console.
AWS Config Active Everywhere : AWS Config must be enabled and actively recording all resources across all member accounts and in all regions where Firewall Manager policies will apply. Firewall Manager relies directly on AWS Config to discover resources, evaluate compliance, and execute remediation actions.
Loading diagram...
If AWS Config is disabled in even one member account or region, Firewall Manager cannot evaluate or protect resources in that scope.
Root User Governance & Hardening
The AWS account root user has unrestricted, irrevocable access to all resources and APIs within an account. Root user credentials bypass all IAM permission boundaries and cannot be restricted by IAM policies within that account.
Management Account Root User Hardening
Because the Management account root user is also immune to Service Control Policies , its compromise represents the ultimate organizational catastrophe. Strict hardening mandates:
Zero Long-Term Access Keys : Never create access keys for the root user. If root access keys exist, delete them immediately. Programmatic API access must be restricted to IAM roles.
Hardware Multi-Factor Authentication (FIDO2) : Protect the root user with physical, hardware-based MFA devices (such as FIDO2 WebAuthn security keys or hardware TOTP tokens). Register multiple hardware security keys to ensure backup redundancy.
Physical Vaulting & Dual-Custody : The complex, randomly generated root password and physical hardware tokens must be stored in separate, geographically distributed physical safes requiring dual-custody authorization (two distinct keyholders must be present to access the credentials).
No Routine Operational Usage : The root user must never be used for day-to-day administrative tasks. All administrative activities must be performed by federated identities assuming privileged IAM roles.
Member Account Root User Protection via SCPs
Unlike the Management account, member account root users are fully subject to Service Control Policies . Organizations can neutralize member account root user access using an explicit Deny SCP attached at the organization root: {
- "Version": "2012-10-17",
- "Statement": [
- {
- "Sid": "DenyMemberAccountRootExecution",
- "Effect": "Deny",
- "Action": "*",
- "Resource": "*",
- "Condition": {
- "StringLike": {
- "aws:PrincipalArn": [
- "arn:aws:iam::*:root"
- ]
- }
- }
- }
- ]
- }
Exam Tip : The condition "StringLike": {"aws:PrincipalArn": ["arn:aws:iam::*:root"]} matches the root user identity of member accounts. Attaching this SCP prevents anyone from logging in as a member account root user and performing API actions, effectively shutting down root account exploitation across member accounts.
Centralized Root Access for Member Accounts (IAM)
Organizations no longer need to store root passwords and MFA devices for hundreds of member accounts. Centralized root access is an IAM feature (not IAM Identity Center). After you enable trusted access for IAM in Organizations and turn on root credentials management and privileged root actions in member accounts :
The management account, or a member account designated as the IAM delegated administrator, can delete member accounts' root credentials (password, access keys, signing certificates, MFA); new accounts are created without root credentials.
For the few tasks that require root, such as unlocking an S3 bucket or SQS queue policy that denies everyone, an administrator calls sts:AssumeRoot with a task policy (for example S3UnlockBucketPolicy ). The session is short-lived (15 minutes at most), scoped to that task, and logged in CloudTrail.
Break-Glass Emergency Protocols
A Break-Glass Procedure is a documented, auditable protocol for gaining emergency administrative access during catastrophic events, such as when corporate identity federation fails, the single sign-on (SSO) directory is unreachable, or administrative IAM roles have been corrupted.
Loading diagram...
Architectural Requirements for Break-Glass Access
Dual-Custody Retrieval : Accessing emergency credentials requires two authorized individuals (e.g., CISO and Lead Architect), each holding one half of the password or separate keys to the physical safe.
Time-Bound Sessions : Emergency roles must enforce a maximum session duration (e.g., 1 hour) using temporary security credentials.
Isolated Identity : Maintain a dedicated emergency IAM role within member accounts that trusts a dedicated break-glass role in the Security Tooling account, avoiding reliance on corporate Active Directory or Okta pipelines.
High-Priority Immediate Alerting : Any invocation of emergency credentials must trigger instantaneous, high-priority alerts to the entire security leadership team.
Real-Time Root Activity Detection & Alerting
Because root user access represents extreme privilege, every root login or API invocation must trigger real-time detection and alerting.
EventBridge Real-Time Root Detection Rule
Amazon EventBridge evaluates AWS CloudTrail management events in near real time. The following event pattern captures any API call executed by a root user across the organization: {
- "detail-type": [
- "AWS API Call via CloudTrail",
- "AWS Console Sign In via CloudTrail"
- ],
- "detail": {
- "userIdentity": {
- "type": ["Root"]
- }
- }
- }
When matched, EventBridge immediately routes the payload to an Amazon SNS topic connected to PagerDuty or SOC analyst endpoints and invokes an AWS Lambda function to capture forensic context or lock down unauthorized sessions.
CloudWatch Metric Filter on CloudTrail Logs
For defense-in-depth, security teams also deploy an Amazon CloudWatch Logs Metric Filter on the centralized CloudTrail log group: { $.userIdentity.type = "Root" && $.userIdentity.invokedBy NOT EXISTS && $.eventType != "AwsServiceEvent" }
This filter increments a CloudWatch metric whenever a real human or external script executes an API call using root credentials, excluding automated internal AWS service tasks. A CloudWatch alarm set to threshold > 0 triggers immediate incident response.
Specialty Exam Traps & Architectural Pitfalls
Attempting to Manage Security Services from the Management Account : Delegating administration to a dedicated member account is an AWS core security standard. Running Security Hub or GuardDuty directly from the Management account violates the principle of least privilege and increases organizational blast radius.
Overlooking AWS Config as a Firewall Manager Blocker : You cannot successfully deploy AWS Firewall Manager policies if AWS Config is not recording resources in the target accounts and regions. If an exam scenario asks why Firewall Manager fails to apply security group policies in a member account, verify whether AWS Config is running.
Assuming SCPs Protect the Management Account Root User : SCPs have zero effect on the Management account root user. The only defenses are eliminating access keys, hardware MFA, vaulting, and continuous CloudTrail/EventBridge monitoring.
Failing to Automate Detective Protection in New Accounts : Delegated administrators for GuardDuty and Security Hub provide an Auto-Enable setting. If auto-enable is not turned on, new accounts vended through Account Factory will remain unprotected until manually enrolled.