CIS Control 1
22 articles
- 1.22 Restrict Access to AWSCloudShellFullAccess (Manual)
- 1.21 Ensure IAM Users Are Managed Centrally via Identity Federation or AWS Organizations in Multi-Account Environments (Manual)
- 1.11 Do Not Create Access Keys During Initial Setup for IAM Users with a Console Password (Manual)
- 1.1 Maintain Current Contact Details (Manual)
- 1.2 Ensure Security Contact Information is Registered (Manual)
- 1.5 Ensure MFA is Enabled for the 'Root' User Account (Automated)
- 1.7 Eliminate Use of the 'Root' User for Administrative and Daily Tasks (Manual)
- 1.10 Ensure Multi-Factor Authentication (MFA) is Enabled for All IAM Users with a Console Password (Automated)
- 1.12 Ensure Credentials Unused for 45 Days or More Are Disabled (Automated)
- 1.13 Ensure There Is Only One Active Access Key for Any Single IAM User (Automated)
- 1.15 Ensure IAM Users Receive Permissions Only Through Groups (Automated)
- 1.16 Ensure IAM Policies with Full ":" Administrative Privileges Are Not Attached (Automated)
- 1.20 Ensure That IAM Access Analyzer Is Enabled for All Regions (Automated)
- 1.3 Ensure Security Questions Are Registered in the AWS Account (Manual)
- 1.4 Ensure No 'Root' User Account Access Key Exists (Automated)
- 1.6 Ensure Hardware MFA is Enabled for the 'Root' User Account (Manual)
- 1.8 Ensure IAM Password Policy Requires Minimum Length of 14 or Greater (Automated)
- 1.9 Ensure IAM Password Policy Prevents Password Reuse (Automated)
- 1.14 Ensure Access Keys are Rotated Every 90 Days or Less (Automated)
- 1.17 Ensure a Support Role Has Been Created to Manage Incidents with AWS Support (Automated)
- 1.18 Ensure IAM Instance Roles Are Used for AWS Resource Access from Instances (Automated)
- 1.19 Ensure That All Expired SSL/TLS Certificates Stored in AWS IAM Are Removed (Automated)