Ensure IAM policies do not use NotResource with Allow effect
Using NotResource with Allow grants permissions on all resources except those listed. This can inadvertently grant access to sensitive resources.
Security Impact
Access may be granted to sensitive resources that weren't explicitly excluded from the NotResource list.
How to Remediate
Replace NotResource statements with explicit Resource statements that specify only the required resources.
Affected Resources
Compliance Frameworks
How TigerGate Helps
TigerGate continuously monitors your AWS environment to detect and alert on this misconfiguration. Here's what our platform does for this specific check:
- Continuous Scanning
Automatically scans all Identity and Access Management (IAM) resources across your AWS accounts every hour
- Instant Alerts
Get notified via Slack, email, or webhooks when this misconfiguration is detected
- One-Click Remediation
Fix this issue directly from the TigerGate dashboard with our guided remediation
- Compliance Evidence
Automatically collect audit evidence for SOC 2, NIST 800-53 compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-iam-24
- Service
- Identity and Access Management (IAM)
- Category
- Permissions Management
- Severity
- MEDIUM
Automate This Check
TigerGate automatically scans your AWS environment for this and 575+ other security checks.
Start Free TrialRelated Identity and Access Management (IAM) Checks
View all checksAvoid the use of root account
Ensure MFA is enabled for the root account
Ensure hardware MFA is enabled for the root account
Ensure no root account access keys exist
Ensure IAM password policy requires at least one uppercase letter