AWS Security Hub is not enabled in this region
- Severity
- Low
- Service
- Security Hub
- Check ID
- SECURITYHUB_NOT_ENABLED
What this check finds
Security Hub aggregates findings from GuardDuty, Inspector, Macie, Config, and third-party tools into a single prioritised view. Without it, security findings are siloed across services and harder to triage and track.
Passing looks like: AWS Security Hub enabled.
How to fix it
Enable Security Hub in each active region.
AWS CLI
aws securityhub enable-security-hub --enable-default-standards
Names in capitals are placeholders for your own resource. Review a command before you run it.
AWS console
Security Hub → Get started → Enable Security Hub. Enable via AWS Organizations to automatically enrol all accounts.
Compliance controls it is evidence for
A failing result counts against these controls in KloudLytics; a passing one is evidence towards them. How compliance mapping works
| Framework | Controls |
|---|---|
| CIS AWS Foundations Benchmark v5.0.0 |
|
| PCI-DSS v4.0.1 |
|
| HIPAA Security Rule |
|
| SOC 2 — Trust Services Criteria |
|
| NIST SP 800-53 Rev5 (Moderate) |
|
| NIST Cybersecurity Framework 2.0 |
|
| ISO/IEC 27001:2022 Annex A |
|
Checked on every scan
KloudLytics runs this check each time it scans a connected AWS account, through a read-only role, and lists every affected resource with its region. On Pro and Business a fix is written for the specific resource rather than the general case above. The exact access it needs