Control: 1.21 Ensure IAM users are managed centrally via identity federation or AWS Organizations for multi-account environments
Description
In multi-account environments, IAM user centralization facilitates greater user control. User access beyond the initial account is then provide via role assumption. Centralization of users can be accomplished through federation with an external identity provider or through the use of AWS Organizations.
Centralizing IAM user management to a single identity provider, reduces complexity and thus less access management errors.
Remediation
From Console
Perform the following action to check:
For multi-account AWS environments with an external identity provider
- Determine the master account for identity federation or IAM user management.
- Sign into the AWS console and open the IAM Dashboard.
- In the left navigation pane, choose Identity providers.
- Verify the configuration.
For all accounts that should not have local users present. For each account
- Determine all accounts that should not have local users present
- Sign into the AWS console and open the IAM Dashboard.
- Switch role into each identified account.
- Click Users.
- Confirm that no IAM users representing individuals are present.
For multi-account AWS environments implementing AWS Organizations without an external identity provider
- Determine all accounts that should not have local users present.
- Sign into the AWS console and open the IAM Dashboard.
- Switch role into each identified account.
- Click Users.
- Confirm that no IAM users representing individuals are present.
Note: The remediation procedure might vary based on the individual organization's implementation of identity federation and/or AWS Organizations with the acceptance criteria that no non-service IAM users, and non-root accounts, are present outside the account providing centralized IAM user management.
Usage
Run the control in your terminal:
powerpipe control run aws_compliance.control.cis_v150_1_21
Snapshot and share results via Turbot Pipes:
powerpipe loginpowerpipe control run aws_compliance.control.cis_v150_1_21 --share
SQL
This control uses a named query:
manual_control