๐ผ 1.1 Maintain current contact details | | | 1 | |
๐ผ 1.2 Ensure security contact information is registered | | | 1 | |
๐ผ 1.3 Ensure security questions are registered in the AWS account | | | | |
๐ผ 1.4 Ensure no root user account access key exists | | 1 | 1 | |
๐ผ 1.5 Ensure MFA is enabled for the "root user" account | | | 1 | |
๐ผ 1.6 Ensure hardware MFA is enabled for the "root user" account | | | 1 | |
๐ผ 1.7 Eliminate use of the root user for administrative and daily tasks | | 1 | 1 | |
๐ผ 1.8 Ensure IAM password policy requires minimum length of 14 or greater | | | 1 | |
๐ผ 1.9 Ensure IAM password policy prevents password reuse | | 1 | 1 | |
๐ผ 1.10 Ensure multi-factor authentication (MFA) is enabled for all IAM users that have a console password | | | 1 | |
๐ผ 1.11 Do not setup access keys during initial user setup for all IAM users that have a console password | | 1 | 1 | |
๐ผ 1.12 Ensure credentials unused for 90 days or greater are disabled | | | | |
๐ผ 1.13 Ensure there is only one active access key available for any single IAM user | | 1 | 1 | |
๐ผ 1.14 Ensure access keys are rotated every 90 days or less | | 1 | 1 | |
๐ผ 1.15 Ensure IAM Users Receive Permissions Only Through Groups | | 1 | 1 | |
๐ผ 1.16 Ensure IAM policies that allow full ":" administrative privileges are not attached | | 1 | 1 | |
๐ผ 1.17 Ensure a support role has been created to manage incidents with AWS Support | | | 1 | |
๐ผ 1.18 Ensure IAM instance roles are used for AWS resource access from instances | | 1 | 1 | |
๐ผ 1.19 Ensure that all the expired SSL/TLS certificates stored in AWS IAM are removed | | 1 | 1 | |
๐ผ 1.20 Ensure that S3 Buckets are configured with 'Block public access (bucket settings)' | | 1 | 1 | |
๐ผ 1.21 Ensure that IAM Access analyzer is enabled | | 1 | 1 | |
๐ผ 1.22 Ensure IAM users are managed centrally via identity federation or AWS Organizations for multi-account environments | | | 1 | |