<  Back to rules search

Access keys are not created for IAM user during initial set up



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.


Requiring the additional steps be taken by the user for programmatic access after their profile has been created will give a stronger indication of intent that access keys are necessary for their work and once the access key is established on an account that the keys may be in use somewhere in the organization.

Note: Even if it is known the user will need access keys, require them to create the keys themselves or put in a support ticket to have them created as a separate step from user creation.


See the CIS AWS Foundations Benchmark controls docs for console remediation steps.



Default value



  1. https://docs.aws.amazon.com/cli/latest/reference/iam/delete-access-key.html
  2. https://docs.aws.amazon.com/IAM/latest/UserGuide/id_users_create.html

Additional Information: Credential report does not appear to contain “Key Creation Date”

CIS controls

Version 7, 16 - Account Monitoring and Control