More Info:

Empty groups should be cleaned up and should not linger around.

Risk Level

Informational

Address

Security

Compliance Standards

CBP

This rule identifies IAM roles that do not require multi-factor authentication (MFA) or external ID for assumed roles. Roles without MFA or external ID can pose security risks, as they may allow unauthorized access or increase the attack surface for potential breaches. Enforcing MFA and external ID requirements adds an additional layer of security to IAM roles and helps prevent unauthorized access.

Triage and Remediation

How to Prevent

To prevent the misconfiguration of having groups without users in AWS IAM using the AWS Management Console, follow these steps:

  1. Regularly Review IAM Groups:

    • Navigate to the IAM Dashboard in the AWS Management Console.
    • Click on “Groups” in the left-hand navigation pane.
    • Regularly review the list of IAM groups to identify any groups that do not have any users assigned to them.
  2. Implement Group Usage Policies:

    • Establish and enforce policies within your organization that require IAM groups to have at least one user or role assigned to them.
    • Ensure that any new group created has a clear purpose and assigned users or roles.
  3. Automate Group Monitoring:

    • Set up AWS Config rules to monitor IAM groups and detect groups without users.
    • Use the AWS Config rule “iam-group-has-users-check” to automatically check for groups without users and flag them for review.
  4. Scheduled Audits:

    • Schedule regular audits (e.g., monthly or quarterly) to review IAM groups and ensure compliance with your group usage policies.
    • Document the audit process and findings to maintain a record of compliance and actions taken.

By following these steps, you can proactively prevent the misconfiguration of having groups without users in AWS IAM.

Additional Reading: