# Ensure Unattached Customer Managed IAM Policy Does Not Allow ':*' Administrative Privileges

- Source: https://support.icompaas.com/support/solutions/articles/a_1788890040083509-ensure-unattached-customer-managed-iam-policy-does-not-allow-administrative-privileges
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [AWS Cloud](https://support.icompaas.com/support/solutions/c_1788889426924716) › [AWS Checks](https://support.icompaas.com/support/solutions/folders/f_1788889470630116)
- Last updated: 2026-09-08
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

**Description**

Ensure that customer-managed IAM policies that are not currently attached to any user, group, or role, do not grant broad administrative privileges using a statement such as Effect: Allow, Action: '\*', Resource: '\*', or similarly broad wildcard patterns like 'service:\*'.

**Rationale**

Unattached policies with overly broad administrative permissions represent latent risk: they are not actively enforced today, but if mistakenly attached to a principal in the future, whether by an automation script, a well-intentioned but hasty administrator, or a compromised account making IAM changes, they immediately grant excessive privileges. Identifying and either tightening or removing such policies before they are attached reduces the chance of an accidental privilege escalation.

**Impact**

-   Reduces the risk of unintentional privilege escalation if a leftover overly broad policy is later attached to a principal
    
-   Encourages IAM policy hygiene and least-privilege policy design across the account
    
-   Requires reviewing whether the policy was intentionally created for a specific, tightly controlled use case before deleting or modifying it
    

**Default Value**

IAM does not restrict what policy documents can be authored or left unattached; there is no default protection against overly broad, unattached policies existing in the account.

**Pre-Requisites**

-   IAM permissions to list and review customer-managed policies (iam:ListPolicies, iam:GetPolicyVersion) and to delete or edit them (iam:DeletePolicy, iam:CreatePolicyVersion)
    

**Test Plan**

1.  Sign in to the AWS Management Console at [https://console.aws.amazon.com](https://console.aws.amazon.com/).
    
2.  Navigate to IAM > Policies.
    
3.  Filter for Customer managed policies and review each policy's Attached entities count.
    
4.  For each policy with zero attachments, open the policy and review its JSON policy document.
    
5.  Verify that no statement grants Effect: Allow with Action: '\*' and Resource: '\*' (or an equally broad wildcard) without a scoping condition.
    
6.  If an unattached policy grants overly broad administrative privileges, follow the implementation steps.
    

**Implementation Steps**

1.  Sign in to the AWS Management Console at [https://console.aws.amazon.com](https://console.aws.amazon.com/).
    
2.  Navigate to IAM > Policies and select the unattached policy with overly broad permissions.
    
3.  Determine whether the policy is still needed; if not, select Delete policy and confirm.
    
4.  If the policy is still needed for a legitimate, narrower purpose, select Edit policy and revise the statement to scope Action and Resource to only the specific services, actions, and resource ARNs required.
    
5.  Create a new policy version with the revised, least-privilege statement, and set it as the default version.
    
6.  Verify the policy document no longer contains an unscoped Action: '\*', Resource: '\*' statement.
    

**Backout Plan**

1.  Sign in to the AWS Management Console at [https://console.aws.amazon.com](https://console.aws.amazon.com/).
    
2.  Navigate to IAM > Policies and select the affected policy.
    
3.  Select Edit policy and create a new version restoring the broader Action: '\*', Resource: '\*' statement, if reverting is required.
    
4.  Set the restored version as the default version.
    

**Reference**

-   [https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html)

## Related compliance guidance

- [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Configuration checks like this one are the technical half of a SOC 2 / ISO 27001 programme — the guide shows where they fit, what else an auditor expects, and how to evidence them.
- [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): ISO 27001 Annex A.8 (technological controls) is where cloud hardening evidence lands; the guide shows how to run the ISMS around it.