Check ID:
Provider: AWS
Service:
Severity: LOW
Categories:
Resource type:
accessanalyzer_enabled_without_findingsProvider: AWS
Service:
accessanalyzerSeverity: LOW
Categories:
identity-access, trust-boundaries, internet-exposedResource type:
OtherWhat this check verifies
IAM Access Analyzer analyzers are inActive state and currently report zero Active findings within their scope of monitored resources.
Risk
UnresolvedActive findings indicate unintended external or internal access paths.
- Confidentiality: public/cross-account reads of data (buckets, snapshots, secrets)
- Integrity: rogue role assumption or KMS use enabling policy/data changes
- Lateral movement across accounts
Recommendation
Enable IAM Access Analyzer in all relevant Regions and org/account scopes. Triage everyActive finding:
- Remove unintended access by tightening resource and trust policies
- Enforce least privilege and separation of duties
- Archive only validated, intended access
- Continuously monitor and automate reviews
Remediation
- Terraform
- Native IaC
- Dashboard steps
References
- https://docs.aws.amazon.com/IAM/latest/UserGuide/access-analyzer-findings-remediate.html
- https://docs.aws.amazon.com/IAM/latest/UserGuide/access-analyzer-findings-view.html
- https://aws.amazon.com/iam/access-analyzer/
- https://docs.aws.amazon.com/IAM/latest/UserGuide/access-analyzer-getting-started.html
- https://docs.aws.amazon.com/IAM/latest/UserGuide/access-analyzer-concepts.html
- https://docs.aws.amazon.com/IAM/latest/UserGuide/access-analyzer-dashboard.html
- https://docs.aws.amazon.com/IAM/latest/UserGuide/access-analyzer-findings.html
- https://aws.amazon.com/blogs/security/automate-resolution-for-iam-access-analyzer-cross-account-access-findings-on-iam-roles/
- https://docs.aws.amazon.com/IAM/latest/UserGuide/what-is-access-analyzer.html
- https://www.trendmicro.com/trendaivisiononecloudriskmanagement/knowledge-base/aws/AccessAnalyzer/findings.html
Where this check fires
This check runs on every scheduled scan against your AWS account. Findings appear at Cloud Security → Findings filterable byCheck ID = accessanalyzer_enabled_without_findings. To re-evaluate after a fix, hit Run now on the account’s schedule under Cloud Security → Schedules — the next scan re-checks this control and marks the finding fixed or keeps it persistent.
← Back to AWS checks