💼 1.11 Do not setup access keys during initial user setup for all IAM users that have a console password - Level 1 (Manual)

• ID: /frameworks/cis-aws-v2.0.0/01/11

Description

AWS console defaults to no check boxes selected when creating a new IAM user. When creating the IAM User credentials you have to determine what type of access they require.

Programmatic access: The IAM user might need to make API calls, use the AWS CLI, or use the Tools for Windows PowerShell. In that case, create an access key (access key ID and a secret access key) for that user.

AWS Management Console access: If the user needs to access the AWS Management Console, create a password for the user.

Similar

• Sections
  • /frameworks/cis-aws-v3.0.0/01/11
  • /frameworks/cis-aws-v1.5.0/01/11
• Internal
  • ID: dec-c-e0b3f20c

Similar Sections (Take Policies From)

Section	Sub Sections	Internal Rules	Policies	Flags	Compliance
💼 CIS AWS v1.5.0 → 💼 1.11 Do not setup access keys during initial user setup for all IAM users that have a console password - Level 1 (Automated)		1	1		no data
💼 CIS AWS v3.0.0 → 💼 1.11 Do not setup access keys during initial user setup for all IAM users that have a console password - Level 1 (Manual)		1	1		no data

Similar Sections (Give Policies To)

Section	Sub Sections	Internal Rules	Policies	Flags	Compliance
💼 CIS AWS v1.5.0 → 💼 1.11 Do not setup access keys during initial user setup for all IAM users that have a console password - Level 1 (Automated)		1	1		no data
💼 CIS AWS v3.0.0 → 💼 1.11 Do not setup access keys during initial user setup for all IAM users that have a console password - Level 1 (Manual)		1	1		no data

Sub Sections

Section	Sub Sections	Internal Rules	Policies	Flags	Compliance

Policies (1)

Policy	Logic Count	Flags	Compliance
🛡️ AWS IAM User with console and programmatic access set during the initial creation🟢⚪		🟢 x2, ⚪ x1	no data

Internal Rules

Rule	Policies	Flags
✉️ dec-x-b10e98af	1