Skip to main content

💼 CIS AWS v1.2.0

  • Contextual name: 💼 CIS AWS v1.2.0
  • ID: /frameworks/cis-aws-v1.2.0

Description

Empty...

Similar

  • Internal
    • ID: dec-a-4d0fbb89

Sub Sections

SectionSub SectionsInternal RulesPoliciesFlags
💼 1 Identity and Access Management22
    💼 1.1 Avoid the use of the "root" account11
    💼 1.2 Ensure multi-factor authentication (MFA) is enabled for all IAM users that have a console password1
    💼 1.3 Ensure credentials unused for 90 days or greater are disabled
    💼 1.4 Ensure access keys are rotated every 90 days or less11
    💼 1.5 Ensure IAM password policy requires at least one uppercase letter
    💼 1.6 Ensure IAM password policy require at least one lowercase letter
    💼 1.7 Ensure IAM password policy require at least one symbol
    💼 1.8 Ensure IAM password policy require at least one number
    💼 1.9 Ensure IAM password policy requires minimum length of 14 or greater1
    💼 1.10 Ensure IAM password policy prevents password reuse11
    💼 1.11 Ensure IAM password policy expires passwords within 90 days or less
    💼 1.12 Ensure no root account access key exists11
    💼 1.13 Ensure MFA is enabled for the "root" account1
    💼 1.14 Ensure hardware MFA is enabled for the "root" account1
    💼 1.15 Ensure security questions are registered in the AWS account
    💼 1.16 Ensure IAM policies are attached only to groups or roles11
    💼 1.17 Maintain current contact details1
    💼 1.18 Ensure security contact information is registered1
    💼 1.19 Ensure IAM instance roles are used for AWS resource access from instances11
    💼 1.20 Ensure a support role has been created to manage incidents with AWS Support1
    💼 1.21 Do not setup access keys during initial user setup for all IAM users that have a console password11
    💼 1.22 Ensure IAM policies that allow full ":" administrative privileges are not created11
💼 2 Logging9
    💼 2.1 Ensure CloudTrail is enabled in all regions11
    💼 2.2 Ensure CloudTrail log file validation is enabled11
    💼 2.3 Ensure the S3 bucket used to store CloudTrail logs is not publicly accessible
    💼 2.4 Ensure CloudTrail trails are integrated with CloudWatch Logs
    💼 2.5 Ensure AWS Config is enabled in all regions1
    💼 2.6 Ensure S3 bucket access logging is enabled on the CloudTrail S3 bucket1
    💼 2.7 Ensure CloudTrail logs are encrypted at rest using KMS CMKs1
    💼 2.8 Ensure rotation for customer created CMKs is enabled11
    💼 2.9 Ensure VPC flow logging is enabled in all VPCs11
💼 3 Monitoring14
    💼 3.1 Ensure a log metric filter and alarm exist for unauthorized API calls1
    💼 3.2 Ensure a log metric filter and alarm exist for Management Console sign-in without MFA1
    💼 3.3 Ensure a log metric filter and alarm exist for usage of 'root' account1
    💼 3.4 Ensure a log metric filter and alarm exist for IAM policy changes1
    💼 3.5 Ensure a log metric filter and alarm exist for CloudTrail configuration changes1
    💼 3.6 Ensure a log metric filter and alarm exist for AWS Management Console authentication failures1
    💼 3.7 Ensure a log metric filter and alarm exist for disabling or scheduled deletion of customer created CMKs1
    💼 3.8 Ensure a log metric filter and alarm exist for S3 bucket policy changes1
    💼 3.9 Ensure a log metric filter and alarm exist for AWS Config configuration changes1
    💼 3.10 Ensure a log metric filter and alarm exist for security group changes1
    💼 3.11 Ensure a log metric filter and alarm exist for changes to Network Access Control Lists (NACL)1
    💼 3.12 Ensure a log metric filter and alarm exist for changes to network gateways1
    💼 3.13 Ensure a log metric filter and alarm exist for route table changes1
    💼 3.14 Ensure a log metric filter and alarm exist for VPC changes1
💼 4 Networking4
    💼 4.1 Ensure no security groups allow ingress from 0.0.0.0/0 to port 22
    💼 4.2 Ensure no security groups allow ingress from 0.0.0.0/0 to port 3389
    💼 4.3 Ensure the default security group of every VPC restricts all traffic1
    💼 4.4 Ensure routing tables for VPC peering are "least access"1