Check ID:
Provider: AWS
Service:
Severity: CRITICAL
Categories:
Resource type:
iam_aws_attached_policy_no_administrative_privilegesProvider: AWS
Service:
iamSeverity: CRITICAL
Categories:
identity-accessResource type:
AwsIamPolicyWhat this check verifies
IAM AWS-managed policies attached to identities are inspected for statements that allowAction:'*' on Resource:'*'-i.e., full administrative *:* permissions
Risk
Unrestricted*:* access enables any action on any resource, risking:
- Data exfiltration (confidentiality)
- Unauthorized changes and policy tampering (integrity)
- Service deletion or shutdown (availability) Attackers can disable logging, create backdoor principals, and expand lateral movement.
Recommendation
Apply least privilege: avoid attaching AWS-managed policies that grant*:*.
- Use customer-managed, scoped policies per role
- Enforce separation of duties and permissions boundaries
- Prefer temporary, time-bound elevation for emergencies with MFA
- Regularly review access and use conditions to constrain context
Remediation
- Terraform
- Native IaC
- Dashboard steps
References
- https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AdministratorAccess.html
- https://support.icompaas.com/support/solutions/articles/62000233815-ensure-iam-roles-do-not-have-administratoraccess-policy-attached
- http://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.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 = iam_aws_attached_policy_no_administrative_privileges. 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