G2

Dinesh Reddy K.

Data Analyst

Enterprise (> 1000 emp.)

7/31/2025

"Centralized Security Insights for AWS"

4.5/5

What do you like best about AWS Security Hub?

As someone who manages multi-account AWS environments and data pipelines, I appreciate how Security Hub centralizes security and compliance findings across services like GuardDuty, Inspector, and Macie. The automated compliance checks for CIS and PCI DSS are especially useful for ensuring data governance without manual overhead. Security Hub’s integration with EventBridge also makes it easy to trigger automated responses, which aligns well with my experience building end-to-end data and ML workflows on AWS. Review collected by and hosted on G2.com.

What do you dislike about AWS Security Hub?

While the centralized view is powerful, handling a large volume of findings can be overwhelming without careful filtering or automation. Multi-region and cross-account configuration requires additional setup, which can slow initial adoption. Also, native integration with third-party SIEM tools could be more seamless, as currently, I rely on custom pipelines and Lambda functions to forward alerts for advanced analytics. Review collected by and hosted on G2.com.

What problems is AWS Security Hub solving and how is that benefiting you?

AWS Security Hub helps me centralize security and compliance monitoring across multiple AWS accounts and regions. It automatically aggregates findings from services like GuardDuty, Macie, and Inspector, which reduces the time I spend manually checking logs and alerts. This has been critical for maintaining data pipeline security, ensuring compliance with standards like CIS, and quickly identifying misconfigurations or threats that could affect AI/ML workloads. The centralized visibility and integration with automation tools like EventBridge enable faster response and more confidence in our overall cloud security posture. Review collected by and hosted on G2.com.