A company uses AWS Organizations with all features enabled. The security team wants to prevent any principal in member accounts from disabling AWS CloudTrail or deleting the trail, even if they have administrator permissions in their account. The security team also wants to ensure that new accounts automatically inherit this restriction. Which combination of actions should they take?
SCPs applied at the organization root apply to all member accounts, including future ones, and can restrict actions even for account administrators. Denying cloudtrail:StopLogging and cloudtrail:DeleteTrail prevents anyone in member accounts from disabling or deleting trails. The management account is not affected by SCPs, but the requirement focuses on member accounts. This is the correct way to enforce guardrails centrally.
Why this answer
Service control policies (SCPs) are the only AWS Organizations feature that can centrally restrict actions across all member accounts, including future ones, and apply to all principals, including account administrators. By denying cloudtrail:StopLogging and cloudtrail:DeleteTrail at the root, the security team ensures no member account can tamper with CloudTrail. Other options are either detective, not inheritable, or do not apply cross-account.
Exam trap
The trap here is assuming that IAM permission boundaries or detective controls like EventBridge can enforce organization-wide preventive restrictions, when only SCPs provide that centralized, inheritable deny capability.