Compliance assessment
All listed controls, with their descriptions from CIS Amazon Web Services Foundations Benchmark v1.2.0
Identity and Access Management22
1.1Avoid the use of the "root" account1.2Ensure multi-factor authentication (MFA) is enabled for all IAM users that have a console password1.3Ensure credentials unused for 90 days or greater are disabled1.4Ensure access keys are rotated every 90 days or less1.5Ensure IAM password policy requires at least one uppercase letter1.6Ensure IAM password policy require at least one lowercase letter1.7Ensure IAM password policy require at least one symbol1.8Ensure IAM password policy require at least one number1.9Ensure IAM password policy requires minimum length of 14 or greater1.10Ensure IAM password policy prevents password reuse1.11Ensure IAM password policy expires passwords within 90 days or less1.12Ensure no root account access key exists1.13Ensure MFA is enabled for the "root" account1.14Ensure hardware MFA is enabled for the "root" account1.15Ensure security questions are registered in the AWS account1.16Ensure IAM policies are attached only to groups or roles1.17Maintain current contact details1.18Ensure security contact information is registered1.19Ensure IAM instance roles are used for AWS resource access from instances1.20Ensure a support role has been created to manage incidents with AWS Support1.21Do not setup access keys during initial user setup for all IAM users that have a console password1.22Ensure IAM policies that allow full "*:*" administrative privileges are not created
Logging9
2.1Ensure CloudTrail is enabled in all regions2.2Ensure CloudTrail log file validation is enabled2.3Ensure the S3 bucket used to store CloudTrail logs is not publicly accessible2.4Ensure CloudTrail trails are integrated with CloudWatch Logs2.5Ensure AWS Config is enabled in all regions2.6Ensure S3 bucket access logging is enabled on the CloudTrail S3 bucket2.7Ensure CloudTrail logs are encrypted at rest using KMS CMKs2.8Ensure rotation for customer created CMKs is enabled2.9Ensure VPC flow logging is enabled in all VPCs
Monitoring14
3.1Ensure a log metric filter and alarm exist for unauthorized API calls3.2Ensure a log metric filter and alarm exist for Management Console sign-in without MFA3.3Ensure a log metric filter and alarm exist for usage of "root" account3.4Ensure a log metric filter and alarm exist for IAM policy changes3.5Ensure a log metric filter and alarm exist for CloudTrail configuration changes3.6Ensure a log metric filter and alarm exist for AWS Management Console authentication failures3.7Ensure a log metric filter and alarm exist for disabling or scheduled deletion of customer created CMKs3.8Ensure a log metric filter and alarm exist for S3 bucket policy changes3.9Ensure a log metric filter and alarm exist for AWS Config configuration changes3.10Ensure a log metric filter and alarm exist for security group changes3.11Ensure a log metric filter and alarm exist for changes to Network Access Control Lists (NACL)3.12Ensure a log metric filter and alarm exist for changes to network gateways3.13Ensure a log metric filter and alarm exist for route table changes3.14Ensure a log metric filter and alarm exist for VPC changes