A company uses multiple AWS security services — GuardDuty, Inspector, Macie, and IAM Access Analyzer — across multiple accounts. The security team needs a single console to view, prioritise, and manage all security findings from these services and third-party tools. Which AWS service provides this aggregated view?
Security Hub aggregates findings from GuardDuty, Inspector, Macie, IAM Access Analyzer, Firewall Manager, and third-party tools into a unified dashboard. It uses the AWS Security Finding Format (ASFF) to normalise findings and allows centralised management across accounts.
Why this answer
AWS Security Hub is the correct service because it provides a single, consolidated view of security alerts and compliance status across multiple AWS accounts and services, including GuardDuty, Inspector, Macie, and IAM Access Analyzer. It aggregates findings from these native services and third-party tools into a standardized format using the AWS Security Finding Format (ASFF), enabling centralized prioritization and management. This directly addresses the requirement for a unified console to view, prioritize, and manage all security findings.
Exam trap
The trap here is that candidates often confuse AWS Security Hub with Amazon GuardDuty or AWS Config, mistakenly thinking that GuardDuty's threat detection or Config's compliance checks already provide a consolidated view, when in fact Security Hub is the dedicated aggregation service that ingests findings from multiple sources.
How to eliminate wrong answers
Option A is wrong because Amazon GuardDuty is a threat detection service that monitors for malicious activity using VPC Flow Logs, DNS logs, and CloudTrail events, but it does not aggregate findings from other security services or third-party tools; it only generates its own findings. Option B is wrong because Amazon CloudWatch is a monitoring and observability service for metrics, logs, and alarms, not a security findings aggregator; it lacks the standardized security finding format (ASFF) and cross-service consolidation capabilities of Security Hub. Option D is wrong because AWS Config is a resource inventory and compliance auditing service that evaluates resource configurations against rules, but it does not ingest or aggregate security findings from GuardDuty, Inspector, Macie, or third-party tools; it focuses on configuration compliance, not security alert management.