CIS Amazon Web Services Foundations Benchmark v1.2.0/Identity and Access Management/21 of 49
1.21Do not setup access keys during initial user setup for all IAM users that have a console password
Control family: Identity and Access Management
Control description
AWS console defaults the checkbox for creating access keys to enabled. This results in many access keys being generated unnecessarily. In addition to unnecessary credentials, it also generates unnecessary management work in auditing and rotating these keys.
How to implement
ResponsibilityCustomerYou configure and operate this in your own cloud accounts.
People who sign in to the console rarely need an access key, and keys created "just in case" when the user was set up end up unused, unrotated and forgotten. A key is created only when a person asks for one with a reason. Keys that were made at setup and never used are deleted.
Before you start
The same on every cloud, before the steps in the tabs.
- Write how people request an access key: who may ask, the reason needed, who approves it and how long it lasts.
- Tell administrators not to create keys when they set up a new user.
Evidence
- The access key request procedure and the requests approved in the period
Not applicable. This benchmark covers AWS only.
On AWS the tasks find console users holding keys that have never been used, then delete those keys.
Task 1Find keys created at setup and never used
- Sign in to the AWS Management Console at console.aws.amazon.com and open IAM.
- Choose Credential report and then Download Report.
- Filter the rows where password_enabled is true and access_key_1_active or access_key_2_active is true.
- Among those, flag keys whose last-used date is N/A and whose access_key_1_last_rotated matches the day the user was created.
Task 2Delete the unused keys
- In IAM > Users, open a flagged user and choose the Security credentials tab.
- Under Access keys, confirm the key's Last used column shows it has never been used.
- Choose Actions > Deactivate, then Actions > Delete, and confirm.
- Tell the user how to request a key with a reason if they ever need one.
- Check it: a new credential report shows no unused keys on console users.
Evidence
- The credential report, with no never-used key on a user who has a console password
- The written process for requesting an access key
Not applicable. This benchmark covers AWS only.
Console steps as of 5 November 2026. Not every step has been confirmed in a live console yet, and menus and labels can move between releases, so look for the nearest match if one has changed.