Amazon Inspector v2 is not enabled
- Severity
- Medium
- Service
- Vulnerability management
- Check ID
- INSPECTOR_NOT_ENABLED
What this check finds
Amazon Inspector v2 is not scanning this account for software vulnerabilities in EC2 instances, ECR container images, or Lambda functions. Without it, known CVEs in running workloads are invisible.
Passing looks like: Amazon Inspector enabled.
How to fix it
Enable Inspector v2.
AWS CLI
aws inspector2 enable --resource-types EC2 ECR LAMBDA
Names in capitals are placeholders for your own resource. Review a command before you run it.
AWS console
Inspector → Get started → Enable Inspector. Activate via AWS Organizations for all member 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 |
|---|---|
| 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