An international company needs to aggregate AWS Security Hub findings across all AWS Regions and multiple accounts, and build a centralized custom dashboard that correlates these findings with operational data for deeper analysis. Which combination of steps will meet these requirements? (Choose three.)

The first correct option establishes a centralized Security Hub administration using AWS Organizations, which is crucial for aggregating findings across multiple accounts and regions. Publishing events to Amazon EventBridge from all accounts and regions ensures all Security Hub findings are captured. The second correct option uses Kinesis Data Firehose to efficiently stream these findings from EventBridge to a single Amazon S3 bucket, which is a common and scalable solution for data aggregation. Kinesis Data Firehose handles buffering, compression, and encryption. The third correct option outlines a robust analytics pipeline: partitioning S3 data improves query performance, AWS Glue crawls and catalogs the data, Amazon Athena queries the data directly from S3, and Amazon QuickSight visualizes the data, enabling custom dashboards. The incorrect option suggesting publishing to CloudWatch instead of EventBridge is less flexible for routing events to other AWS services like Kinesis Data Firehose. The incorrect option using Kinesis data streams instead of Kinesis Data Firehose would require managing consumers and scaling, which Firehose automates. The incorrect option using AWS Glue DataBrew for crawling and schema building is less common for this specific use case compared to AWS Glue, and it doesn't mention partitioning, which is vital for large datasets.