CIS Amazon Web Services Foundations Benchmark v1.2.0/Identity and Access Management/4 of 49
1.4Ensure access keys are rotated every 90 days or less
Control family: Identity and Access Management
Control description
Access keys consist of an access key ID and secret access key, which are used to sign programmatic requests that you make to AWS. AWS users need their own access keys to make programmatic calls to AWS from the AWS Command Line Interface (AWS CLI), Tools for Windows PowerShell, the AWS SDKs, or direct HTTP calls using the APIs for individual AWS services. It is recommended that all access keys be regularly rotated.
How to implement
ResponsibilityCustomerYou configure and operate this in your own cloud accounts.
Long-term access keys should be replaced at least every 90 days, so a key copied from a laptop, a script or a log stops working before long. Rotation means creating a new key, moving the program onto it, then deactivating and deleting the old one. Keys that can be replaced with roles (see 1.19) shouldn't exist at all.
Before you start
The same on every cloud, before the steps in the tabs.
- Record which program or person uses each access key, so a rotation can be planned with its owner.
Evidence
- The register of access keys and their owners
Not applicable. This benchmark covers AWS only.
On AWS the tasks rotate a key without downtime in IAM, then add the AWS Config rule that flags keys older than 90 days.
Task 1Rotate an access key without breaking its user
- Sign in to the AWS Management Console at console.aws.amazon.com and open IAM > Users.
- Open the user and choose the Security credentials tab; under Access keys, note the age of each key.
- Choose Create access key, choose the use case, then Next and Create access key, and give the new key to the owner through your secrets store.
- Once the program uses the new key, check the old key's Last used date stops moving.
- Choose Actions > Deactivate on the old key, wait a few days, then choose Actions > Delete.
- Check it: the user has one active key, created less than 90 days ago.
Task 2Keep it checked with the AWS Config rule access-keys-rotated
- Open AWS Config in the Region where you record global resources such as IAM, and choose Rules > Add rule.
- On Specify rule type, search for access-keys-rotated, select it and choose Next.
- On Configure rule, under Parameters, set maxAccessKeyAge to 90, then choose Next.
- On Review and create, check the settings and add the rule.
- Check it: once the rule has finished Evaluating..., the Rules page shows it as compliant; open the rule to see any resource that fails.
Evidence
- The access-keys-rotated rule with maxAccessKeyAge 90, showing all users compliant
- The credential report, with every active key's access_key_1_last_rotated within the last 90 days
- Security Hub CSPM control IAM.3, showing passed
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.