lacework-global-71
1.21 Ensure IAM users are managed centrally via identity federation or AWS Organizations for multi-account environments (Manual)
Profile Applicability
• Level 2
Description
In multi-account environments, IAM user centralization facilitates greater user control. User access beyond the initial account is then provided via role assumption. Centralization of users can be accomplished through federation with an external identity provider or through the use of AWS Organizations.
Rationale
Centralizing IAM user management to a single identity store reduces complexity and thus the likelihood of access management errors.
Audit
For multi-account AWS environments with an external identity provider...
- Determine the master account for identity federation or IAM user management
- Login to that account through the AWS Management Console
- Click
Services
- Click
IAM
- Click
Identity providers
- Verify the configuration
Then..., determine all accounts that should not have local users present. For each account...
- Determine all accounts that should not have local users present
- Log into the AWS Management Console
- Switch role into each identified account
- Click
Services
- Click
IAM
- 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
- Log into the AWS Management Console
- Switch role into each identified account
- Click
Services
- Click
IAM
- Click
Users
- Confirm that no IAM users representing individuals are present
Remediation
The remediation procedure will 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.