OpenParable
Skip to content
← Back to skills

Cis AWS Foundations 2.19

DevOps & Security
cis-aws-foundations-2.19

Cis AWS Foundations 2.19 is an Agent Skill for devops & security published in the CyberStrikeus/CyberStrike repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Ensure IAM users are managed centrally via identity federation or AWS Organizations for multi-account environments

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/CyberStrikeus/CyberStrike/blob/HEAD/.cyberstrike/skill/CIS_benchmarks/Cloud_Providers/AWS/CIS_Amazon_Web_Services_Foundations_Benchmark_v7.0.0/cis-aws-foundations-2.19/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/cis-aws-foundations-2-19, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

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 provided through role assumption. Centralization of users can be accomplished through federation with an external identity provider or through the use of AWS Organizations. AWS IAM Identity Center (formerly AWS SSO) is the recommended approach for centralized user management in AWS Organizations.

Rationale

Centralizing IAM user management to a single identity store reduces complexity and the likelihood of access management errors. Using AWS IAM Identity Center further simplifies access management and reduces reliance on legacy per-account federation configurations.

Impact

Managing IAM users independently across multiple accounts increases the risk of inconsistent access controls, orphaned accounts, and excessive permissions.

Audit Procedure

Using AWS Console

For multi-account AWS environments with an external identity provider:

  1. Sign in to the AWS Management Console and open the IAM console at https://console.aws.amazon.com/iam
  2. Click Identity providers
  3. Verify that federation is configured appropriately

For environments using AWS IAM Identity Center (recommended):

  1. Sign in to the AWS Management Console and open the IAM console at https://console.aws.amazon.com/iam
  2. Navigate to IAM Identity Center
  3. Verify that IAM Identity Center is enabled
  4. Confirm that users and groups are centrally managed
  5. Confirm that access is assigned to accounts through IAM Identity Center

For multi-account environments without centralized identity management:

  1. Identify accounts that should not contain local IAM users
  2. Sign in to the AWS Management Console
  3. Switch role into each identified account
  4. Navigate to the IAM console
  5. Select Users
  6. Confirm that no IAM users representing individuals are present

Expected Result

Multi-account environments should have centralized identity management through either AWS IAM Identity Center or an external identity provider with federation. No local IAM users representing individuals should exist in member accounts (except for service accounts where required).

Remediation

The remediation procedure will vary based on the organization's implementation of identity federation and or AWS Organizations.

Ensure the following:

  1. IAM users are centrally managed through a single identity provider
  2. Local IAM users are removed from member accounts, except for service accounts where required
  3. Access to accounts is granted through role assumption
  4. Where possible, migrate to AWS IAM Identity Center for centralized access management
  5. Avoid legacy per-account federation configurations

Default Value

By default, AWS accounts are created and managed independently. IAM users are local to each account unless centralized management is explicitly configured. IAM Identity Center must be enabled to provide centralized access management.

CIS Controls

Controls VersionControlIG 1IG 2IG 3
v85.6 Centralize Account Management - Centralize account management through a directory or identity service.xx
v716.2 Configure Centralized Point of Authentication - Configure access for all accounts through as few centralized points of authentication as possible, including network, security, and cloud systems.xx

MITRE ATT&CK Mappings

Techniques / Sub-techniquesTacticsMitigations
T1078.004TA0001, TA0004M1018

Profile

Level 2 | Manual