Skip to main content

💼 CIS AWS v1.2.0

  • ID: /frameworks/cis-aws-v1.2.0

Stats​

not available

Description​

Empty...

Similar​

  • Internal
    • ID: dec-a-4d0fbb89

Sub Sections​

SectionSub SectionsInternal RulesPoliciesFlagsCompliance
💼 1 Identity and Access Management22815no data
 💼 1.1 Avoid the use of the "root" account11no data
 💼 1.2 Ensure multi-factor authentication (MFA) is enabled for all IAM users that have a console password1no data
 💼 1.3 Ensure credentials unused for 90 days or greater are disabledno data
 💼 1.4 Ensure access keys are rotated every 90 days or less11no data
 💼 1.5 Ensure IAM password policy requires at least one uppercase letterno data
 💼 1.6 Ensure IAM password policy require at least one lowercase letternullno data
 💼 1.7 Ensure IAM password policy require at least one symbolno data
 💼 1.8 Ensure IAM password policy require at least one numberno data
 💼 1.9 Ensure IAM password policy requires minimum length of 14 or greater1no data
 💼 1.10 Ensure IAM password policy prevents password reuse11no data
 💼 1.11 Ensure IAM password policy expires passwords within 90 days or lessno data
 💼 1.12 Ensure no root account access key exists11no data
 💼 1.13 Ensure MFA is enabled for the "root" account1no data
 💼 1.14 Ensure hardware MFA is enabled for the "root" account1no data
 💼 1.15 Ensure security questions are registered in the AWS accountno data
 💼 1.16 Ensure IAM policies are attached only to groups or roles11no data
 💼 1.17 Maintain current contact details1no data
 💼 1.18 Ensure security contact information is registered1no data
 💼 1.19 Ensure IAM instance roles are used for AWS resource access from instances11no data
 💼 1.20 Ensure a support role has been created to manage incidents with AWS Support1no data
 💼 1.21 Do not setup access keys during initial user setup for all IAM users that have a console password11no data
 💼 1.22 Ensure IAM policies that allow full ":" administrative privileges are not created11no data
💼 2 Logging937no data
 💼 2.1 Ensure CloudTrail is enabled in all regions1no data
 💼 2.2 Ensure CloudTrail log file validation is enabled11no data
 💼 2.3 Ensure the S3 bucket used to store CloudTrail logs is not publicly accessibleno data
 💼 2.4 Ensure CloudTrail trails are integrated with CloudWatch Logsno data
 💼 2.5 Ensure AWS Config is enabled in all regions1no data
 💼 2.6 Ensure S3 bucket access logging is enabled on the CloudTrail S3 bucket1no data
 💼 2.7 Ensure CloudTrail logs are encrypted at rest using KMS CMKs1no data
 💼 2.8 Ensure rotation for customer created CMKs is enabled11no data
 💼 2.9 Ensure VPC flow logging is enabled in all VPCs11no data
💼 3 Monitoring1414no data
 💼 3.1 Ensure a log metric filter and alarm exist for unauthorized API calls1no data
 💼 3.2 Ensure a log metric filter and alarm exist for Management Console sign-in without MFA1no data
 💼 3.3 Ensure a log metric filter and alarm exist for usage of 'root' account1no data
 💼 3.4 Ensure a log metric filter and alarm exist for IAM policy changes1no data
 💼 3.5 Ensure a log metric filter and alarm exist for CloudTrail configuration changes1no data
 💼 3.6 Ensure a log metric filter and alarm exist for AWS Management Console authentication failures1no data
 💼 3.7 Ensure a log metric filter and alarm exist for disabling or scheduled deletion of customer created CMKs1no data
 💼 3.8 Ensure a log metric filter and alarm exist for S3 bucket policy changes1no data
 💼 3.9 Ensure a log metric filter and alarm exist for AWS Config configuration changes1no data
 💼 3.10 Ensure a log metric filter and alarm exist for security group changes1no data
 💼 3.11 Ensure a log metric filter and alarm exist for changes to Network Access Control Lists (NACL)1no data
 💼 3.12 Ensure a log metric filter and alarm exist for changes to network gateways1no data
 💼 3.13 Ensure a log metric filter and alarm exist for route table changes1no data
 💼 3.14 Ensure a log metric filter and alarm exist for VPC changes1no data
💼 4 Networking42no data
 💼 4.1 Ensure no security groups allow ingress from 0.0.0.0/0 to port 22no data
 💼 4.2 Ensure no security groups allow ingress from 0.0.0.0/0 to port 3389no data
 💼 4.3 Ensure the default security group of every VPC restricts all traffic1no data
 💼 4.4 Ensure routing tables for VPC peering are "least access"1no data