Centralize Security Hub findings via delegated admin, EventBridge to Firehose/S3, and Athena/QuickSight
Short answer
BDE Delegated admin + EventBridge, Firehose to a single S3 bucket, and Athena/QuickSight for the correlated dashboard.
Question
Key Takeaways
Security Hub delegated administration aggregates findings org-wide; EventBridge is the correct event bus (not CloudWatch). Firehose (not Data Streams) is the managed delivery stream that persists findings to S3 without building consumer apps. Athena over the S3 data lake plus QuickSight provides the search/visualization layer the analytics requirement needs.
The company needs Security Hub findings combined across all accounts and Regions and visualized on a custom dashboard with operational data. The solution: designate a Security Hub delegated administrator in the organization and publish findings to EventBridge; in each Region, an EventBridge rule sends findings to a Kinesis Data Firehose delivery stream that lands them in a single S3 bucket; Athena queries that bucket and QuickSight builds the correlated dashboard. CloudWatch (A) and Kinesis Data Streams (C) are the wrong delivery primitives.
Common mistake: Choosing CloudWatch publishing (A) instead of EventBridge, or Kinesis Data Streams (C) instead of Firehose—Data Streams needs a custom consumer to land data in S3, while Firehose delivers to S3 natively. Both A and C use the wrong transport for a managed S3 lake.
Expert Analysis
Why the Answer Is Correct
B establishes the delegated administrator and EventBridge publishing so findings from all accounts/Regions flow through one bus. D uses per-Region EventBridge rules to Firehose delivery streams that consolidate findings into a single S3 bucket—the managed path to a data lake. E uses Glue/Athena to query the S3 data and QuickSight to build the correlated dashboard, meeting the analytics and visualization requirement. Together they cover aggregation, storage, and insight.
Why the Other Options Are Wrong
A publishes to CloudWatch, which is not the finding-distribution mechanism Security Hub uses for cross-account analytics. C uses Kinesis Data Streams, which would require a custom consumer to write to S3; Firehose (D) does this natively. The B/D/E combination is the documented, lowest-effort pipeline.
Community Comment Notes
Commenters concluded B/D/(F) referencing the AWS architecture blog for visualizing Security Hub findings with analytics/BI tools; in this five-option set the analytics step is E (Glue/Athena/QuickSight). A and C are explicitly rejected for using CloudWatch and Data Streams instead of EventBridge and Firehose. The correct trio is B, D, E.
Official Reference
- https://docs.aws.amazon.com/securityhub/latest/userguide/designate-orgs-admin-account.html
- https://docs.aws.amazon.com/firehose/latest/dev/what-is-this-service.html
- https://docs.aws.amazon.com/athena/latest/ug/what-is.html
These links open the official vendor documentation in a new tab.
Discussion 6 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 6
-
ion_gee 👍 2Not A, do not need cloud watch. Not C, Kinesis Data firehose(Now Amazon Data Firehose) is what we need here, not Kinesis Data Streams. Not E . Rather use Athena to query S3 See Ref https://aws.amazon.com/blogs/architecture/visualize-aws-security-hub-findings-using-analytics-and-business-intelligence-tools/
-
MikeRach 👍 1BDF The steps are literally provided in this Doc https://aws.amazon.com/blogs/architecture/visualize-aws-security-hub-findings-using-analytics-and-business-intelligence-tools/
-
sarcactus 👍 1BDF Also agree with previous comment.
-
nublit 👍 1BDF are the best options
-
awssecuritynewbie 👍 1BDF for sure,
Show 1 more comment
-
ale_brd_111 👍 1BDF probably
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.