A security engineer needs to centralize GuardDuty findings for a multi-account organization. The goal is to ensure that all current and future accounts in the 'Production' OU have GuardDuty enabled automatically and report to the security account. What is the most efficient way to achieve this?
Trap 1: Designate the security account as the GuardDuty delegated…
GuardDuty delegated administration allows the security account to manage member accounts. Auto-enablement ensures that new accounts added to the organization are automatically protected without manual intervention, reducing the risk of coverage gaps. This approach centralizes finding management and billing while maintaining regional compliance and operational efficiency.
Trap 2: Enable GuardDuty manually in each account and use an S3 bucket in…
Standalone GuardDuty enablement requires manual setup in every account, which is operationally intensive and prone to human error. It fails to leverage AWS Organizations for governance, making it difficult to ensure that every new account is correctly configured for threat detection across the entire enterprise environment.
Trap 3: Use an IAM role in the master account to invite each member account…
Invitation-based GuardDuty management is a legacy method that preceded Organizations integration. While it allows for member-master relationships, it does not support automatic enablement for new accounts. This leads to higher administrative overhead and the potential for new accounts to remain unprotected for significant periods.
- A
Designate the security account as the GuardDuty delegated administrator and enable 'Auto-enable' for the organization.
Why it fails: GuardDuty delegated administration allows the security account to manage member accounts. Auto-enablement ensures that new accounts added to the organization are automatically protected without manual intervention, reducing the risk of coverage gaps. This approach centralizes finding management and billing while maintaining regional compliance and operational efficiency.
- B
Enable GuardDuty manually in each account and use an S3 bucket in the security account as a finding export destination.
Why it fails: Standalone GuardDuty enablement requires manual setup in every account, which is operationally intensive and prone to human error. It fails to leverage AWS Organizations for governance, making it difficult to ensure that every new account is correctly configured for threat detection across the entire enterprise environment.
- C
Use an IAM role in the master account to invite each member account to a GuardDuty master-member relationship.
Why it fails: Invitation-based GuardDuty management is a legacy method that preceded Organizations integration. While it allows for member-master relationships, it does not support automatic enablement for new accounts. This leads to higher administrative overhead and the potential for new accounts to remain unprotected for significant periods.
- D
Deploy a CloudFormation StackSet to all accounts in the Production OU that enables GuardDuty and sets a custom publishing frequency.
CloudFormation StackSets can deploy GuardDuty, but they do not provide the native management features of delegated administration. StackSets require continuous maintenance to ensure they target the correct OUs and do not offer the same seamless integration for aggregating findings into the security account console.