A city enables Amazon GuardDuty, Amazon Inspector, and Amazon Macie and wants one place to aggregate and prioritize those security findings. Which service provides that posture aggregation?
Select an answer to reveal the explanation.
Short Explanation
Security Hub is the citywide blotter that rolls GuardDuty, Inspector, and Macie tickets into one prioritized view. Polly narration, Artifact paperwork, or Lightsail spreadsheet clerks are not that aggregation service.
Full Explanation
When a city enables Amazon GuardDuty, Amazon Inspector, and Amazon Macie and wants one place to aggregate and prioritize those security findings, AWS Security Hub is the posture aggregation service. Security Hub ingests and normalizes findings from those integrations (and others), supports standards-based checks, and provides multi-account visibility so municipal security teams can triage from a single blotter rather than three consoles.
Amazon Polly narrating each raw finding as the sole aggregation strategy fails because text-to-speech does not correlate, deduplicate, or prioritize findings across accounts. AWS Artifact agreements alone replacing continuous finding aggregation fails conceptually: Artifact provides compliance reports and agreements, not a live findings bus from GuardDuty/Inspector/Macie. Dedicating Amazon Lightsail instances to manually copy findings into spreadsheets fails because manual transcription does not scale and introduces delay and human error.
Exam caveat: Security Hub aggregation requires enabling the integrated products and appropriate member-account configuration—an empty hub means integrations were never turned on, not that the environment is clean. Operational check: enable Security Hub with delegated administration, confirm GuardDuty/Inspector/Macie findings appear, set severity-based insights or EventBridge routing to ticketing, and review unresolved high/critical findings in the weekly security operations meeting.