Security Hub is enabled in accounts managed by AWS Organizations.
Aggregate findings into a security operations account.
Which setting is most appropriate?
Configure Security Hub cross-account and cross-Region aggregation with a delegated administrator.
Detailed explanation
DNS records do not aggregate security findings.
DNS records do not aggregate security findings.
Security Hub can aggregate findings into the organization management or delegated administrator account.
Security Hub can aggregate findings into the organization management or delegated administrator account.
Separate emails do not provide centralized prioritization or management.
Separate emails do not provide centralized prioritization or management.
S3 lifecycle management does not aggregate Security Hub findings.
S3 lifecycle management does not aggregate Security Hub findings.
Check official documentation
Compare the following points with the official documentation.
AWS Security Hub cross-account aggregationの公式説明を確認する。
What to confirm
検出結果の集約とメール通知の違いを説明できる。
Key points
- Security Hub
- Cross-account aggregation
- Delegated administrator
Notes
- Environment: AWS公式SOA-C03試験ガイドとAWS公式ドキュメントの確認
- Confirm current AWS service behavior in the official documentation.
Foundation review
Central operations
Aggregation creates one prioritized view across the organization's accounts.
Account boundary
Findings remain associated with their source account while being managed centrally.