An e-learning platform operates a multi-account AWS environment managed under AWS Organizations. The security team needs a solution to centralize the monitoring of security alerts and threat detections from Amazon GuardDuty, Amazon Macie, and AWS IAM Access Analyzer across all accounts. Additionally, they must continuously assess their resource configurations against the AWS Foundational Security Best Practices standard. Which solution will meet these requirements with the least operational overhead?
- Enable AWS Security Hub in a designated security administrator account, integrate it with AWS Organizations to aggregate findings across all member accounts, and enable the AWS Foundational Security Best Practices standard.Answer
- BEnable AWS Shield Advanced in the centralized security account to aggregate security events, resource vulnerability reports, and IAM access logs from all member accounts into a single dashboard.
- CConfigure stateless Network ACLs in the centralized transit VPC to monitor and aggregate configuration security compliance findings and API call anomalies from all member accounts.
- DConfigure a centralized AWS WAF Web ACL to monitor configuration changes and automatically inspect API call payloads to block unauthorized IAM configuration changes.
Answer
Enable AWS Security Hub in a designated security administrator account, integrate it with AWS Organizations to aggregate findings across all member accounts, and enable the AWS Foundational Security Best Practices standard.
The correct solution uses AWS Security Hub, which is designed to centralize and prioritize security findings from multiple AWS services (such as GuardDuty, Macie, and IAM Access Analyzer) across all accounts in an organization. It also runs automated compliance checks against standards like AWS Foundational Security Best Practices, minimizing operational overhead.
Step-by-Step Solution
Key Concept
Centralized security monitoring and compliance tracking using AWS Security Hub and AWS Organizations.