{"catalog":{"description":"AWS Enterprise Accelerator - Compliance: Quick Start Standardized Architecture for CIS Amazon Web Services Foundations BenchmarkSecurity Requirements Reference, v1.2.0, 05-23-2018 This document describes the CIS Amazon Web Services Foundations Security Requirements that are directly addressed by this AWS Quick Start package. Additional information about this benchmark can be found at https://benchmarks.cisecurity.org/en-us/?route=downloads.form.awsfoundations.110 It is important to note that the Description of AWS Implementation details and Additional Guidance in this document are not exhaustive, and must be reviewed, evaluated, assessed, and approved by the customer organization, and layered with other security features that address all of the in-scope systems and applications for a holistic solution to meet overall security requirements. The controls are a combination of AWS Config Rules (both AWS-managed and custom), Amazon CloudWatch rules, and Amazon CloudWatch alarms. Please note that these resources will incur costs in your account; please refer to the pricing model for each service. The following preconditions must be met before the stack can be launched. This Quickstart does provide customers with an option of configuring AWS CloudTrail and AWS Config. Customers can choose to do so or choose to configure these services themselves. Precondition 1: AWS Config must be turned on in the region where this template will be run. This is needed for Config Rules. Precondition 2: AWS CloudTrail must be turned on and must be delivering logs to CloudWatch Logs. This is needed for CloudWatch metrics and alarms. Precondition 3: AWS Lambda must be supported in the region where this template will be launched. See this page for AWS services region support: https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/","uuid":"59fdaecc-6a00-47a6-9af1-308467b7b08f","datePublished":"2018-05-23T04:00:00","version":"1.0.0","master":false,"url":"https://www.cisecurity.org/benchmark/amazon_web_services/","abstract":"Securing Amazon Web Services - an objective, consensus-driven security guideline for the AWS cloud providers.","defaultName":"cis-aws","title":"Standardized Architecture for CIS AWS Foundations Benchmark, Version 1.2","lastRevisionDate":"2024-01-26","regulationDatePublished":"2022-08-12","keywords":"CIS; AWS; Benchmarks; Security Controls;","securityControls":[{"id":25011,"description":"This control is implemented using the AWS CloudWatch Alarm and  custom Log Metric Filter defined for control 3.3 which  reports if the root account is being used. ","references":"Responsibility: Customer","tenantsId":1,"uuid":"cd2f64f6-fddf-4bea-b6d4-0a844a8c321a","family":"Identity and Access Management","subControls":"","weight":0,"isPublic":true,"enhancements":"","controlType":"Stand-Alone","title":"1.1 Avoid the use of the \"root\" account (Scored)","relatedControls":"","catalogueID":140,"assessmentPlan":"We recommend that Root accounts should not be used and that the credentials not be shared with anyone else. As a best practice, customers should leverage IAM Groups, Roles and Users to grant access to specific AWS resources. Refer to IAM Best Practices at  the following link:\r\nhttp://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html","practiceLevel":"","mappings":"","controlId":"1.1"},{"id":25012,"description":"This control is implemented as a Config rule backed by a custom lambda function. The config rule reports back the compliance status of IAM users against this control. The Config rule DOES NOT enforce this control by enabling MFA for any of the IAM users.","references":"Responsibility: Shared (Config Rule and Customer)","tenantsId":1,"uuid":"56acac65-32db-4d9f-823f-4b3fe933284c","family":"Identity and Access Management","subControls":"","weight":0,"isPublic":true,"enhancements":"","controlType":"Stand-Alone","title":"1.2 Ensure multi-factor authentication (MFA) is enabled for all IAM users that have a password (Scored)","relatedControls":"","catalogueID":140,"assessmentPlan":"For extra security, we recommend that customers enable multi-factor authentication (MFA) for  IAM users based on the compliance reported by the config rule.\r\nRefer to IAM Best Practices at the following link:\r\nhttp://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html\r\n\r\nIf the Config rule reports NonCompliance, ensure that IAM Users with a password have MFA enabled. For remediation, refer to control 1.2 in the document  https://d0.awsstatic.com/whitepapers/compliance/AWS_CIS_Foundations_Benchmark.pdf","practiceLevel":"","mappings":"","controlId":"1.2"},{"id":25013,"description":"This control is implemented as a Config rule backed by a custom lambda function. The config rule reports back the compliance status of IAM users credentials against this control. The Config rule  DOES NOT enforce this control by disabling credentials.","references":"Responsibility: Shared (Config Rule and Customer)","tenantsId":1,"uuid":"4eb9cebd-f59f-4a11-bf92-a25d35d14b2d","family":"Identity and Access Management","subControls":"","weight":0,"isPublic":true,"enhancements":"","controlType":"Stand-Alone","title":"1.3 Ensure credentials unused for 90 days or greater are disabled (Scored)","relatedControls":"","catalogueID":140,"assessmentPlan":"We recommend that unused credentials be disabled by customers based on the Compliance reported by the Config rule.\r\nRefer to IAM Best Practices at the following link:\r\nhttp://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html\r\n\r\nIf the Config rule reports NonCompliance, ensure that credentials unused for 90 days or greater are disabled. For remediation, refer to control 1.3 in the document  https://d0.awsstatic.com/whitepapers/compliance/AWS_CIS_Foundations_Benchmark.pdf","practiceLevel":"","mappings":"","controlId":"1.3"},{"id":25014,"description":"This control is implemented as a Config rule backed by a custom lambda function. The config rule reports back the compliance status of IAM users with active access keys against this control. The Config rule  DOES NOT enforce this control by rotating the access keys.","references":"Responsibility: Shared (Config Rule and Customer)","tenantsId":1,"uuid":"683a15ad-2279-4737-b1c0-c877a1f9330d","family":"Identity and Access Management","subControls":"","weight":0,"isPublic":true,"enhancements":"","controlType":"Stand-Alone","title":"1.4 Ensure access keys are rotated every 90 days or less (Scored)","relatedControls":"","catalogueID":140,"assessmentPlan":"We recommend that access keys  be rotated by customers based on the Compliance reported by the Config rule. Refer to IAM Best Practices at\r\nhttp://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html\r\n\r\nIf the Config rule reports NonCompliance, ensure that Access keys are rotated every 90 days or less. For remediation, refer to control 1.4 in the document  https://d0.awsstatic.com/whitepapers/compliance/AWS_CIS_Foundations_Benchmark.pdf","practiceLevel":"","mappings":"","controlId":"1.4"},{"id":25015,"description":"The Quick Start creates an AWS Managed Config Rule to check the compliance status of the policy password against these specific CIS controls. The Config rule  does not enforce any security controls.","references":"Responsibility: Shared (Config Rule and Customer)","tenantsId":1,"uuid":"893764be-fd8b-4db2-b875-a9dc8217c769","family":"Identity and Access Management","subControls":"","weight":0,"isPublic":true,"enhancements":"","controlType":"Stand-Alone","title":"1.5 Ensure IAM password policy requires at least one uppercase letter (Scored)","relatedControls":"","catalogueID":140,"assessmentPlan":"We recommend that a strong password policy be set for IAM users.\r\nRefer to IAM Best Practices at the following link:\r\nhttp://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html\r\n\r\nIf the Config rule reports NonCompliance, ensure that the password policy meets the controls requirements. For remediation, refer to controls 1.5 through 1.11 in the document  https://d0.awsstatic.com/whitepapers/compliance/AWS_CIS_Foundations_Benchmark.pdf","practiceLevel":"","mappings":"","controlId":"1.5"},{"id":25016,"description":"The Quick Start creates an AWS Managed Config Rule to check the compliance status of the policy password against these specific CIS controls. The Config rule  does not enforce any security controls.","references":"Responsibility: Shared (Config Rule and Customer)","tenantsId":1,"uuid":"97571b84-744a-4431-9a2c-55c541be5fef","family":"Identity and Access Management","subControls":"","weight":0,"isPublic":true,"enhancements":"","controlType":"Stand-Alone","title":"1.6 Ensure IAM password policy require at least one lowercase letter (Scored)","relatedControls":"","catalogueID":140,"assessmentPlan":"We recommend that a strong password policy be set for IAM users.\r\nRefer to IAM Best Practices at the following link:\r\nhttp://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html\r\n\r\nIf the Config rule reports NonCompliance, ensure that the password policy meets the controls requirements. For remediation, refer to controls 1.5 through 1.11 in the document  https://d0.awsstatic.com/whitepapers/compliance/AWS_CIS_Foundations_Benchmark.pdf","practiceLevel":"","mappings":"","controlId":"1.6"},{"id":25017,"description":"The Quick Start creates an AWS Managed Config Rule to check the compliance status of the policy password against these specific CIS controls. The Config rule  does not enforce any security controls.","references":"Responsibility: Shared (Config Rule and Customer)","tenantsId":1,"uuid":"8f9a6675-ad24-4f50-9fe5-115a85aded72","family":"Identity and Access Management","subControls":"","weight":0,"isPublic":true,"enhancements":"","controlType":"Stand-Alone","title":"1.7 Ensure IAM password policy require at least one symbol (Scored)","relatedControls":"","catalogueID":140,"assessmentPlan":"We recommend that a strong password policy be set for IAM users.\r\nRefer to IAM Best Practices at the following link:\r\nhttp://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html\r\n\r\nIf the Config rule reports NonCompliance, ensure that the password policy meets the controls requirements. For remediation, refer to controls 1.5 through 1.11 in the document  https://d0.awsstatic.com/whitepapers/compliance/AWS_CIS_Foundations_Benchmark.pdf","practiceLevel":"","mappings":"","controlId":"1.7"},{"id":25018,"description":"The Quick Start creates an AWS Managed Config Rule to check the compliance status of the policy password against these specific CIS controls. The Config rule  does not enforce any security controls.","references":"Responsibility: Shared (Config Rule and Customer)","tenantsId":1,"uuid":"c997b934-05ea-4860-b0db-8e7dfafc9413","family":"Identity and Access Management","subControls":"","weight":0,"isPublic":true,"enhancements":"","controlType":"Stand-Alone","title":"1.8 Ensure IAM password policy require at least one number (Scored)","relatedControls":"","catalogueID":140,"assessmentPlan":"We recommend that a strong password policy be set for IAM users.\r\nRefer to IAM Best Practices at the following link:\r\nhttp://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html\r\n\r\nIf the Config rule reports NonCompliance, ensure that the password policy meets the controls requirements. For remediation, refer to controls 1.5 through 1.11 in the document  https://d0.awsstatic.com/whitepapers/compliance/AWS_CIS_Foundations_Benchmark.pdf","practiceLevel":"","mappings":"","controlId":"1.8"},{"id":25019,"description":"The Quick Start creates an AWS Managed Config Rule to check the compliance status of the policy password against these specific CIS controls. The Config rule  does not enforce any security controls.","references":"Responsibility: Shared (Config Rule and Customer)","tenantsId":1,"uuid":"bfcb15a0-7955-4552-b635-6d27f9e90ca6","family":"Identity and Access Management","subControls":"","weight":0,"isPublic":true,"enhancements":"","controlType":"Stand-Alone","title":"1.9 Ensure IAM password policy requires minimum length of 14 or greater (Scored)","relatedControls":"","catalogueID":140,"assessmentPlan":"We recommend that a strong password policy be set for IAM users.\r\nRefer to IAM Best Practices at the following link:\r\nhttp://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html\r\n\r\nIf the Config rule reports NonCompliance, ensure that the password policy meets the controls requirements. For remediation, refer to controls 1.5 through 1.11 in the document  https://d0.awsstatic.com/whitepapers/compliance/AWS_CIS_Foundations_Benchmark.pdf","practiceLevel":"","mappings":"","controlId":"1.9"},{"id":25020,"description":"The Quick Start creates an AWS Managed Config Rule to check the compliance status of the policy password against these specific CIS controls. The Config rule  does not enforce any security controls.","references":"Responsibility: Shared (Config Rule and Customer)","tenantsId":1,"uuid":"dcda07b7-bedd-4bc9-8b45-2647f7454d3a","family":"Identity and Access Management","subControls":"","weight":0,"isPublic":true,"enhancements":"","controlType":"Stand-Alone","title":"1.10 Ensure IAM password policy prevents password reuse (Scored)","relatedControls":"","catalogueID":140,"assessmentPlan":"We recommend that a strong password policy be set for IAM users.\r\nRefer to IAM Best Practices at the following link:\r\nhttp://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html\r\n\r\nIf the Config rule reports NonCompliance, ensure that the password policy meets the controls requirements. For remediation, refer to controls 1.5 through 1.11 in the document  https://d0.awsstatic.com/whitepapers/compliance/AWS_CIS_Foundations_Benchmark.pdf","practiceLevel":"","mappings":"","controlId":"1.10"},{"id":25021,"description":"The Quick Start creates an AWS Managed Config Rule to check the compliance status of the policy password against these specific CIS controls. The Config rule  does not enforce any security controls.","references":"Responsibility: Shared (Config Rule and Customer)","tenantsId":1,"uuid":"170336f8-d128-47dc-b12d-01e5def0c2fe","family":"Identity and Access Management","subControls":"","weight":0,"isPublic":true,"enhancements":"","controlType":"Stand-Alone","title":"1.11 Ensure IAM password policy expires passwords within 90 days or less (Scored)","relatedControls":"","catalogueID":140,"assessmentPlan":"We recommend that a strong password policy be set for IAM users.\r\nRefer to IAM Best Practices at the following link:\r\nhttp://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html\r\n\r\nIf the Config rule reports NonCompliance, ensure that the password policy meets the controls requirements. For remediation, refer to controls 1.5 through 1.11 in the document  https://d0.awsstatic.com/whitepapers/compliance/AWS_CIS_Foundations_Benchmark.pdf","practiceLevel":"","mappings":"","controlId":"1.11"},{"id":25022,"description":"This control is implemented as a Config rule backed by a custom lambda function. The config rule reports back the compliance status of root account access keys and MFA settings for root account. The Config rule  DOES NOT enforce this control by changing any root account information.","references":"Responsibility: Shared (Config Rule and Customer)","tenantsId":1,"uuid":"e606fac4-b58b-4b09-ab37-111e17c6ee61","family":"Identity and Access Management","subControls":"","weight":0,"isPublic":true,"enhancements":"","controlType":"Stand-Alone","title":"1.12 Ensure no root account access key exists (Scored)","relatedControls":"","catalogueID":140,"assessmentPlan":"We recommend you that create an IAM user for yourself that has administrative privileges and avoid generating Access Keys for the root account.\r\nRefer to IAM Best Practices at the following link:\r\nhttp://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html\r\n\r\nIf the Config rule reports NonCompliance, ensure that no root account access key exists. For remediation, refer to control 1.12 in the document  https://d0.awsstatic.com/whitepapers/compliance/AWS_CIS_Foundations_Benchmark.pdf","practiceLevel":"","mappings":"","controlId":"1.12"},{"id":25023,"description":"This control is implemented as a Config rule backed by a custom lambda function. The config rule reports back the compliance status of root account access keys and MFA settings for root account. The Config rule  DOES NOT enforce this control by changing any root account information.","references":"Responsibility: Shared (Config Rule and Customer)","tenantsId":1,"uuid":"67f45a17-8c6d-47d3-af09-155af9714fa0","family":"Identity and Access Management","subControls":"","weight":0,"isPublic":true,"enhancements":"","controlType":"Stand-Alone","title":"1.13 Ensure  MFA is enabled for the \"root\" account (Scored)","relatedControls":"","catalogueID":140,"assessmentPlan":"We recommend that MFA be enabled for the root account\r\nRefer to IAM Best Practices at the following link:\r\nhttp://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html\r\n\r\nIf the Config rule reports NonCompliance, ensure MFA is enabled for root account. For remediation, refer to control 1.13 in the document  https://d0.awsstatic.com/whitepapers/compliance/AWS_CIS_Foundations_Benchmark.pdf","practiceLevel":"","mappings":"","controlId":"1.13"},{"id":25024,"description":"This control is implemented as a Config rule backed by a custom lambda function. The config rule reports back the compliance status of root account access keys and MFA settings for root account. The Config rule  DOES NOT enforce this control by changing any root account information.","references":"Responsibility: Shared (Config Rule and Customer)","tenantsId":1,"uuid":"8c1a55ca-e94e-4774-9124-036a5f1ccf16","family":"Identity and Access Management","subControls":"","weight":0,"isPublic":true,"enhancements":"","controlType":"Stand-Alone","title":"1.14 Ensure hardware MFA is enabled for the \"root\" account (Scored)","relatedControls":"","catalogueID":140,"assessmentPlan":"We recommend that MFA be enabled for the root account\r\nRefer to IAM Best Practices at the following link:\r\nhttp://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html\r\n\r\nIf the Config rule reports NonCompliance, ensure hardware MFA is enabled for root account. For remediation, refer to control 1.14 in the document  https://d0.awsstatic.com/whitepapers/compliance/AWS_CIS_Foundations_Benchmark.pdf","practiceLevel":"","mappings":"","controlId":"1.14"},{"id":25025,"description":"The Quick start does not provide any implementation for this control due to the lack of APIs to automate this.","references":"Responsibility: Customer","tenantsId":1,"uuid":"ec3fcff2-781e-4bfb-88fa-85ac48a8429e","family":"Identity and Access Management","subControls":"","weight":0,"isPublic":true,"enhancements":"","controlType":"Stand-Alone","title":"1.15 Ensure security questions are registered in the AWS account (Not Scored)","relatedControls":"","catalogueID":140,"assessmentPlan":"Security Questions are highly recommended to be setup to help you recover root login access, if lost. For remediation, refer to control 1.15 in the document  https://d0.awsstatic.com/whitepapers/compliance/AWS_CIS_Foundations_Benchmark.pdf","practiceLevel":"","mappings":"","controlId":"1.15"},{"id":25026,"description":"This control is implemented as a Config rule backed by a custom lambda function. The config rule reports back the compliance status of IAM policies attached only to IAM Groups or Roles. The Config rule  DOES NOT enforce this control by attaching IAM policies to either IAM Groups or Roles","references":"Responsibility: Shared (Config Rule and Customer)","tenantsId":1,"uuid":"ff773de3-ec12-4d22-9529-1750d290c1f7","family":"Identity and Access Management","subControls":"","weight":0,"isPublic":true,"enhancements":"","controlType":"Stand-Alone","title":"1.16 Ensure IAM policies are attached only to groups or roles (Scored)","relatedControls":"","catalogueID":140,"assessmentPlan":"We recommend that you assign IAM Policies to either IAM Groups or IAM Roles to reduce the complexity of access management as the number of users grow.\r\nIf the Config rule reports NonCompliance, ensure IAM policies are attached only to Groups or Roles. For remediation, refer to control 1.16 in the document  https://d0.awsstatic.com/whitepapers/compliance/AWS_CIS_Foundations_Benchmark.pdf","practiceLevel":"","mappings":"","controlId":"1.16"},{"id":25027,"description":"The Quick start does not provide any implementation for this control due to the lack of APIs to automate this.","references":"Responsibility: Customer","tenantsId":1,"uuid":"693d81d5-bd2b-45a4-b1c4-9a772be74a0b","family":"Identity and Access Management","subControls":"","weight":0,"isPublic":true,"enhancements":"","controlType":"Stand-Alone","title":"1.17 Maintain Current contact details (Not Scored)","relatedControls":"","catalogueID":140,"assessmentPlan":"We recommend that current contact details be maintained. AWS Uses this contact the account owner when prohibitive or suspicious activities are observed within an account.\r\nFor remediation, refer to control 1.17 in the document  https://d0.awsstatic.com/whitepapers/compliance/AWS_CIS_Foundations_Benchmark.pdf","practiceLevel":"","mappings":"","controlId":"1.17"},{"id":25028,"description":"The Quick start does not provide any implementation for this control due to the lack of APIs to automate this.","references":"Responsibility: Customer","tenantsId":1,"uuid":"d7628889-8ecb-46c3-a967-d611d20f875f","family":"Identity and Access Management","subControls":"","weight":0,"isPublic":true,"enhancements":"","controlType":"Stand-Alone","title":"1.18 Ensure Security contact information is registered (Not Scored)","relatedControls":"","catalogueID":140,"assessmentPlan":"We recommend that the Security contact information be kept current. Specifying security-specific contact information will help ensure that security advisories sent by AWS reach the team in your organization that is best equipped to respond to them.\r\n\r\nFor remediation, refer to control 1.18 in the document  https://d0.awsstatic.com/whitepapers/compliance/AWS_CIS_Foundations_Benchmark.pdf","practiceLevel":"","mappings":"","controlId":"1.18"},{"id":25029,"description":"This control is implemented as a Config rule backed by a custom lambda function. The config rule reports back the compliance status of EC2 Instances which do not have an Instance Profile attached to them. The Config rule DOES NOT enforce this control by attaching Instance profiles to EC2 Instances.","references":"Responsibility: Shared (Config Rule and Customer)","tenantsId":1,"uuid":"f333bebe-1669-4033-84e1-cf96278d058e","family":"Identity and Access Management","subControls":"","weight":0,"isPublic":true,"enhancements":"","controlType":"Stand-Alone","title":"1.19 Ensure IAM instance roles are used for AWS resource access from instances (Not Scored)","relatedControls":"","catalogueID":140,"assessmentPlan":"We recommend that IAM Roles be attached to an EC2 Instance to provide temporary credentials for the applications running on the EC2 Instances\r\nRefer to IAM Best Practices at the following link:\r\nhttp://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html\r\n\r\nIf the Config rule reports NonCompliance, ensure IAM Instance roles are used for EC2 Instances. For remediation, refer to control 1.19 in the document  https://d0.awsstatic.com/whitepapers/compliance/AWS_CIS_Foundations_Benchmark.pdf\r\n\r\nNote: IAM Roles can be atached to running Instances. See this documentation \r\nhttps://aws.amazon.com/blogs/security/new-attach-an-aws-iam-role-to-an-existing-amazon-ec2-instance-by-using-the-aws-cli/?sc_channel=sm&sc_campaign=rolesforrunninginstances&sc_publisher=tw&sc_medium=social&sc_content=read-post&sc_country=global&sc_geo=global&sc_category=ec2&sc_outcome=launch\r\n","practiceLevel":"","mappings":"","controlId":"1.19"},{"id":25030,"description":"This control is implemented as a Config rule backed by a custom lambda function. The config rule reports back the compliance status on whether a Support role exists or not. The Config rule  DOES NOT enforce this control by creating a Support role.When the \"AWSSupportAccess\" managed policy is not assigned to any IAM User, Role or Group the config rule will not list any resources.When the \"AWSSupportAccess\" managed policy is assigned to any IAM User, Role or Group the config rule will list the resources as being compliant.","references":"Responsibility: Shared (Config Rule and Customer)","tenantsId":1,"uuid":"bd9db844-666b-47e7-9b83-589ac33af3bf","family":"Identity and Access Management","subControls":"","weight":0,"isPublic":true,"enhancements":"","controlType":"Stand-Alone","title":"1.20 Ensure a support role has been created to manage incidents with AWS Support (Scored)","relatedControls":"","catalogueID":140,"assessmentPlan":"It is recommended that customers create an IAM Role to allow authorized users to manage incidents with AWS Support.\r\n\r\nIf the Config rule reports NonCompliance, ensure that atleast 1 IAM Role,User,Group has the AWSSupportAccess policy assigned to it. For remediation, refer to control 1.20 in the document  https://d0.awsstatic.com/whitepapers/compliance/AWS_CIS_Foundations_Benchmark.pdf","practiceLevel":"","mappings":"","controlId":"1.20"},{"id":25031,"description":"The Quick start does not provide any implementation for this control.","references":"Responsibility: Customer","tenantsId":1,"uuid":"bb42224a-2b64-4a4b-8677-9d7718681145","family":"Identity and Access Management","subControls":"","weight":0,"isPublic":true,"enhancements":"","controlType":"Stand-Alone","title":"1.21 Do not setup access keys during initial user setup for all IAM users that have a console password (Not Scored)","relatedControls":"","catalogueID":140,"assessmentPlan":"It is recommended that additional steps be taken by their user upon profile creation to understand the intent of usage and storage of keys.\r\n\r\nFor remediation, refer to control 1.21 in the document  https://d0.awsstatic.com/whitepapers/compliance/AWS_CIS_Foundations_Benchmark.pdf","practiceLevel":"","mappings":"","controlId":"1.21"},{"id":25032,"description":"This control is implemented as a Config rule backed by a custom lambda function. The config rule reports back the compliance status on IAM Policies allowing Admin privileges. The Config rule  DOES NOT enforce this control by deleting such Policies.","references":"Responsibility: Shared (Config Rule and Customer)","tenantsId":1,"uuid":"7c40e824-e0ce-4c0d-9492-3f61f8360b83","family":"Identity and Access Management","subControls":"","weight":0,"isPublic":true,"enhancements":"","controlType":"Stand-Alone","title":"1.22 Ensure IAM policies that allow full \"*:*\" administrative privileges are not created (Scored)","relatedControls":"","catalogueID":140,"assessmentPlan":"It is recommended that IAM policies do not allow full administrative privileges and that the policies follow the principle of least previlige.\r\n\r\nIf the Config rule reports NonCompliance, ensure that IAM Policies provide least previlige access to AWS resources. For remediation, refer to control 1.22 in the document  https://d0.awsstatic.com/whitepapers/compliance/AWS_CIS_Foundations_Benchmark.pdf","practiceLevel":"","mappings":"","controlId":"1.22"},{"id":25033,"description":"This quickstart provides customers an option to automatically configure CloudTrail in the AWS region where this Quick Start is being run. Cloudtrail is not enabled in all regions. This is because CloudTrail Logs need to be delivered to CloudWatch Logs within each region.\r\n \r\nThis control is also implemented as a Config rule backed by a custom lambda function. The config rule reports back the compliance status on whether CloudTrail is enabled in all regions. The Config rule  DOES NOT enforce this control by enabling CloudTrail in all regions.","references":"Responsibility: Shared (Cloudformation template, Config rule and Customer)","tenantsId":1,"uuid":"d6ab135b-cd50-4514-9e58-babb0f90938c","family":"Logging","subControls":"","weight":0,"isPublic":true,"enhancements":"","controlType":"Stand-Alone","title":"2.1 Ensure CloudTrail is enabled in all regions (Scored)","relatedControls":"","catalogueID":140,"assessmentPlan":"This quickstart provides customers an option to automatically configure CloudTrail in the AWS region where this Quick Start is being run. AWS accounts which do not have Cloudtrail configured, should choose this option for the CIS Cloudformation template to execute successfully. \r\n\r\nIf the Config rule reports NonCompliance, customers can choose to enable Cloudtrail in all regions and configure CloudWatch log delivery. For remediation, refer to control 2.1 in the document  https://d0.awsstatic.com/whitepapers/compliance/AWS_CIS_Foundations_Benchmark.pdf\r\n","practiceLevel":"","mappings":"","controlId":"2.1"},{"id":25034,"description":"This quickstart enables Cloudtrail log file validation when customers choose the to automatically configure CloudTrail via the template. \r\n\r\nThis control is also implemented as a Config rule backed by a custom lambda function. The config rule reports back the compliance status on whether CloudTrail log file validation is enabled. The Config rule DOES NOT enforce this control by enabling CloudTrail log file validation.","references":"Responsibility: Shared (Cloudformation template, Config rule and Customer)","tenantsId":1,"uuid":"ad74961a-8c3a-4a2d-9112-2cf80ed80d5c","family":"Logging","subControls":"","weight":0,"isPublic":true,"enhancements":"","controlType":"Stand-Alone","title":"2.2 Ensure CloudTrail log file validation is enabled (Scored)","relatedControls":"","catalogueID":140,"assessmentPlan":"\r\nIf the Config rule reports NonCompliance, ensure Cloudtrail log file validation is enabled. For remediation, refer to control 2.2 in the document  https://d0.awsstatic.com/whitepapers/compliance/AWS_CIS_Foundations_Benchmark.pdf\r\n","practiceLevel":"","mappings":"","controlId":"2.2"},{"id":25035,"description":"This quickstart ensures that S3 Bucket for Cloudtrail is not publicly accessible when customers choose to automatically configure Cloudtrail via the template.\r\n\r\nThis control is also implemented as a Config rule backed by a custom lambda function. The config rule reports back the compliance status on whether CloudTrail log file S3 Bucket is publicly accessible. The Config rule  DOES NOT enforce this control by changing S3 Bucket ACLs.","references":"Responsibility: Shared (Cloudformation template, Config rule and Customer)","tenantsId":1,"uuid":"82d31107-4311-42e9-a158-da4e29b04232","family":"Logging","subControls":"","weight":0,"isPublic":true,"enhancements":"","controlType":"Stand-Alone","title":"2.3 Ensure the S3 bucket used to store CloudTrail logs is not publicly accessible (Scored)","relatedControls":"","catalogueID":140,"assessmentPlan":"\r\n\r\nIf the Config rule reports NonCompliance, ensure S3 Bucket configured for Cloudtrail to log to is not publicly accessible . For remediation, refer to control 2.3 in the document  https://d0.awsstatic.com/whitepapers/compliance/AWS_CIS_Foundations_Benchmark.pdf\r\n","practiceLevel":"","mappings":"","controlId":"2.3"},{"id":25036,"description":"This quickstart ensures that Cloudtrail trails are integrated with CloudWatch Logs when customers choose to automatically configure Cloudtrail via the template.\r\n\r\nThis control is also implemented as a Config rule backed by a custom lambda function. The config rule reports back the compliance status on whether CloudTrail logs are integrated with CloudWatch logs. The Config rule  DOES NOT enforce this control by configuring CloudTrail to deliver logs to CloudWatch Logs.","references":"Responsibility: Shared (Cloudformation template, Config rule and Customer)","tenantsId":1,"uuid":"a9b057a1-abd4-4fc8-bbf1-b0b678f18bcc","family":"Logging","subControls":"","weight":0,"isPublic":true,"enhancements":"","controlType":"Stand-Alone","title":"2.4 Ensure CloudTrail trails are integrated with CloudWatch Logs (Scored)","relatedControls":"","catalogueID":140,"assessmentPlan":"\r\nIf the Config rule reports NonCompliance, ensure that Cloudtrail trails are integrated with Cloudwatch logs. For remediation, refer to control 2.4 in the document  https://d0.awsstatic.com/whitepapers/compliance/AWS_CIS_Foundations_Benchmark.pdf\r\n","practiceLevel":"","mappings":"","controlId":"2.4"},{"id":25037,"description":"This quickstart provides customers an option to automatically configure Config at a regional level via the template.","references":"Responsibility: Shared (Cloudformation Template and Customer)","tenantsId":1,"uuid":"5d4f2d38-7fb8-40a5-98b3-c4524de386e3","family":"Logging","subControls":"","weight":0,"isPublic":true,"enhancements":"","controlType":"Stand-Alone","title":"2.5 Ensure AWS Config is enabled in all regions (Scored)","relatedControls":"","catalogueID":140,"assessmentPlan":"This quickstart provides customers an option to automatically configure AWS Config at a regional level. Customer AWS accounts which do not have Config configured, should choose this option for the CIS Cloudformation template to execute successfully. \r\n\r\nFor manual remediation, refer to control 2.5 in the document  https://d0.awsstatic.com/whitepapers/compliance/AWS_CIS_Foundations_Benchmark.pdf\r\n","practiceLevel":"","mappings":"","controlId":"2.5"},{"id":25038,"description":"This quickstart ensures that S3 bucket access logging is enabled on the Cloudtrail S3 bucket when customers choose to automatically configure Cloudtrail via the template.\r\n\r\nThis control is also implemented as a Config rule backed by a custom lambda function. The config rule reports back the compliance status on whether all S3 Buckets have logging enabled. The Config rule  DOES NOT enforce this control by configuring logging on any S3 bucket.","references":"Responsibility: Shared (Cloudformation template, Config rule and Customer)","tenantsId":1,"uuid":"140fe1a1-5b73-4a2b-9003-0d3f824d06ae","family":"Logging","subControls":"","weight":0,"isPublic":true,"enhancements":"","controlType":"Stand-Alone","title":"2.6 Ensure S3 bucket access logging is enabled on the CloudTrail S3 bucket (Scored)","relatedControls":"","catalogueID":140,"assessmentPlan":"It is recommended that Logging be enabled for all S3 Buckets. Configuring logs to be placed in a separate bucket allows access to log information which can be useful in security and incident response workflows. \r\n\r\nIf the Config rule reports NonCompliance, enable Cloudtrail S3 bucket access logging. For remediation, refer to control 2.6 in the document  https://d0.awsstatic.com/whitepapers/compliance/AWS_CIS_Foundations_Benchmark.pdf","practiceLevel":"","mappings":"","controlId":"2.6"},{"id":25039,"description":"This quickstart ensures that Cloudtrail logs are encrypted at rest using KMS CMKs when customers choose to automatically configure Cloudtrail via the template.\r\n\r\nThis control is also implemented as a Config rule backed by a custom lambda function. The config rule reports back the compliance status on whether CloudTrail logs are encrypted . The Config rule  DOES NOT enforce this control by enabling CloudTrail log file validation.","references":"Responsibility: Shared (Cloudformation template, Config rule and Customer)","tenantsId":1,"uuid":"220900af-28d4-4f87-8e05-2c63938ba5e5","family":"Logging","subControls":"","weight":0,"isPublic":true,"enhancements":"","controlType":"Stand-Alone","title":"2.7 Ensure CloudTrail logs are encrypted at rest using KMS CMKs (Scored)","relatedControls":"","catalogueID":140,"assessmentPlan":"Configuring CloudTrail to use SSE-KMS provides additional confidentiality controls on log data as a given user must have S3 read permission on the corresponding log bucket and must be granted decrypt permission by the CMK policy.\r\n\r\nIf the Config rule reports NonCompliance, ensure Cloudtrail logs are encrypted at rest using KMS CMKs. For remediation, refer to control 2.7 in the document  https://d0.awsstatic.com/whitepapers/compliance/AWS_CIS_Foundations_Benchmark.pdf","practiceLevel":"","mappings":"","controlId":"2.7"},{"id":25040,"description":"This control is implemented as a Config Rule backed by a custom Lambda function. The Config Rule reports back the compliance status on whether the rotation for any CMKs is enabled. The Config rule  DOES NOT enforce this control by enabling CMKs rotation.","references":"Responsibility: Shared (Config rule and Customer)","tenantsId":1,"uuid":"86ca381f-6088-4196-af84-42899428de71","family":"Logging","subControls":"","weight":0,"isPublic":true,"enhancements":"","controlType":"Stand-Alone","title":"2.8 Ensure rotation for customer created CMKs is enabled (Scored)","relatedControls":"","catalogueID":140,"assessmentPlan":"It is recommended to rotate encryption keys to reduce the potential impact of a compromised key as data encrypted with a new key cannot be accessed with a previous key that may have been exposed.\r\n\r\nIf the Config rule reports NonCompliance, ensure rotation of customer created CMKs are enabled. For remediation, refer to control 2.8 in the document  https://d0.awsstatic.com/whitepapers/compliance/AWS_CIS_Foundations_Benchmark.pdf","practiceLevel":"","mappings":"","controlId":"2.8"},{"id":25041,"description":"This control is implemented as a Config rule backed by a custom lambda function. The config rule reports back the compliance status on whether VPC Flow Logging is enabled. The Config rule  DOES NOT enforce this control by enabling VPC Flow Logging.","references":"Responsibility: Shared (Config rule and Customer)","tenantsId":1,"uuid":"f9d7953b-3444-42c6-bec4-5c6c5aa1f5e9","family":"Logging","subControls":"","weight":0,"isPublic":true,"enhancements":"","controlType":"Stand-Alone","title":"2.9 Ensure VPC flow logging is enabled in all VPCs (Scored) ","relatedControls":"","catalogueID":140,"assessmentPlan":"It is recommended to have VPC Flow Logs enabled to provide visibility into network traffic that traverses the VPC and to detect anomalous traffic or insight during security workflows.\r\n\r\nIf the Config rule reports NonCompliance, ensure VPC Flow logging is enabled in all VPCs. For remediation, refer to control 2.9 in the document  https://d0.awsstatic.com/whitepapers/compliance/AWS_CIS_Foundations_Benchmark.pdf","practiceLevel":"","mappings":"","controlId":"2.9"},{"id":25042,"description":"The Quick Start creates an AWS CloudWatch Alarm and a custom Log Metric Filter to report on multiple unauthorized action or login attempts.","references":"Responsibility: Shared (CloudWatch Alarm and Customer)","tenantsId":1,"uuid":"72a3c9da-2c65-4c5e-bf00-277c6dfaf3af","family":"Monitoring","subControls":"","weight":0,"isPublic":true,"enhancements":"","controlType":"Stand-Alone","title":"3.1 Ensure a log metric filter and alarm exist for unauthorized API calls (Scored)","relatedControls":"","catalogueID":140,"assessmentPlan":"It is recommended that customers monitor unauthorized API calls which will help reveal application errors and may reduce time to detect malicious activity.","practiceLevel":"","mappings":"","controlId":"3.1"},{"id":25043,"description":"The Quick Start creates an AWS CloudWatch Alarm and a custom Log Metric Filter to report on Management Console logins without MFA. ","references":"Responsibility: Shared (CloudWatch Alarm and Customer)","tenantsId":1,"uuid":"fd12ac05-ab55-402d-950f-5c6f7aa31c22","family":"Monitoring","subControls":"","weight":0,"isPublic":true,"enhancements":"","controlType":"Stand-Alone","title":"3.2 Ensure a log metric filter and alarm exist for Management Console sign-in without MFA (Scored)","relatedControls":"","catalogueID":140,"assessmentPlan":"It is recommended that customers monitor for single-factor console logins. This will increase visibility into accounts that are not protected by MFA.","practiceLevel":"","mappings":"","controlId":"3.2"},{"id":25044,"description":"The Quick Start creates an AWS CloudWatch Alarm and a custom Log Metric Filter to report if the root account is used. ","references":"Responsibility: Shared (CloudWatch Alarm and Customer)","tenantsId":1,"uuid":"dc7dfa60-0d9f-4060-87d4-f0330a76121f","family":"Monitoring","subControls":"","weight":0,"isPublic":true,"enhancements":"","controlType":"Stand-Alone","title":"3.3 Ensure a log metric filter and alarm exist for usage of \"root\" account  (Scored) ","relatedControls":"","catalogueID":140,"assessmentPlan":"It is recommended that customers monitor for root account logins which will provide visibility into the use of a fully privileged account and an opportunity to reduce the use of it.","practiceLevel":"","mappings":"","controlId":"3.3"},{"id":25045,"description":"The Quick Start creates an AWS CloudWatch Rule that matches incoming CloudWatch Events for IAM policy changes and publishes the changes to an SNS topic. ","references":"Responsibility: Shared (CloudWatch Rule and Customer)","tenantsId":1,"uuid":"e7dfc5fb-861f-40b5-8760-cee99490cfe7","family":"Monitoring","subControls":"","weight":0,"isPublic":true,"enhancements":"","controlType":"Stand-Alone","title":"3.4 Ensure a log metric filter and alarm exist for IAM policy changes (Scored) ","relatedControls":"","catalogueID":140,"assessmentPlan":"It is recommended that customers monitor changes to IAM policies which will help ensure authentication and authorization controls remain intact.","practiceLevel":"","mappings":"","controlId":"3.4"},{"id":25046,"description":"The Quick Start creates an AWS CloudWatch Rule that matches incoming CloudWatch Events for CloudTrail changes and publishes the changes to an SNS topic.","references":"Responsibility: Shared (CloudWatch Rule and Customer)","tenantsId":1,"uuid":"090251d9-10e7-4570-8e8b-13105fe9d5b0","family":"Monitoring","subControls":"","weight":0,"isPublic":true,"enhancements":"","controlType":"Stand-Alone","title":"3.5 Ensure a log metric filter and alarm exist for CloudTrail configuration changes (Scored) ","relatedControls":"","catalogueID":140,"assessmentPlan":"It is recommended that customers monitor changes to CloudTrail's configuration which will help ensure sustained visibility to activities performed in the AWS account.","practiceLevel":"","mappings":"","controlId":"3.5"},{"id":25047,"description":"The Quick Start creates an AWS CloudWatch Alarm and a custom Log Metric Filter to report if there are multiple management console logins failures. ","references":"Responsibility: Shared (CloudWatch Alarm and Customer)","tenantsId":1,"uuid":"cea9161d-1dbf-494d-8683-8dadc6289c82","family":"Monitoring","subControls":"","weight":0,"isPublic":true,"enhancements":"","controlType":"Stand-Alone","title":"3.6 Ensure a log metric filter and alarm exist for AWS Management Console authentication failures (Scored) ","relatedControls":"","catalogueID":140,"assessmentPlan":"It is recommended that customers monitor failed console logins. This may decrease lead time to detect an attempt to brute force a credential, which may provide an indicator, such as source IP, that can be used in other event correlation.","practiceLevel":"","mappings":"","controlId":"3.6"},{"id":25048,"description":"The Quick Start creates an AWS CloudWatch Alarm and a custom Log Metric Filter to report if customer created CMKs get disabled or scheduled for deletion. ","references":"Responsibility: Shared (CloudWatch Alarm and Customer)","tenantsId":1,"uuid":"54feaeb9-342a-408a-bba2-bf92726a5a55","family":"Monitoring","subControls":"","weight":0,"isPublic":true,"enhancements":"","controlType":"Stand-Alone","title":"3.7 Ensure a log metric filter and alarm exist for disabling or scheduled deletion of customer created CMKs (Scored) ","relatedControls":"","catalogueID":140,"assessmentPlan":"It is recommended that customers monitor deletion or disabling of CMKs. Data encrypted with disabled or deleted keys will no longer be accessible.","practiceLevel":"","mappings":"","controlId":"3.7"},{"id":25049,"description":"The Quick Start creates an AWS CloudWatch Rule that matches incoming CloudWatch Events for S3 bucket policy changes and publishes the changes to an SNS topic. ","references":"Responsibility: Shared (CloudWatch Rule and Customer)","tenantsId":1,"uuid":"f1080a90-24c6-4461-bf0a-5e8ad245d5af","family":"Monitoring","subControls":"","weight":0,"isPublic":true,"enhancements":"","controlType":"Stand-Alone","title":"3.8 Ensure a log metric filter and alarm exist for S3 bucket policy changes (Scored) ","relatedControls":"","catalogueID":140,"assessmentPlan":"It is recommended that customers monitor changes to S3 bucket policies to reduce time to detect and correct permissive policies on sensitive S3 buckets.","practiceLevel":"","mappings":"","controlId":"3.8"},{"id":25050,"description":"The Quick Start creates an AWS CloudWatch Rule that matches incoming CloudWatch Events for Config changes and publishes the changes to an SNS topic. ","references":"Responsibility: Shared (CloudWatch Rule and Customer)","tenantsId":1,"uuid":"839bbeb0-071c-418c-a56e-09428a125927","family":"Monitoring","subControls":"","weight":0,"isPublic":true,"enhancements":"","controlType":"Stand-Alone","title":"3.9 Ensure a log metric filter and alarm exist for AWS Config configuration changes (Scored) ","relatedControls":"","catalogueID":140,"assessmentPlan":"It is recommended that customers monitor changes to AWS Config configuration which will help ensure sustained visibility of configuration items within the AWS account.","practiceLevel":"","mappings":"","controlId":"3.9"},{"id":25051,"description":"The Quick Start creates an AWS CloudWatch Rule that matches incoming CloudWatch Events for security groups changes and publishes the changes to an SNS topic. ","references":"Responsibility: Shared (CloudWatch Rule and Customer)","tenantsId":1,"uuid":"dacbd0ac-5526-4405-a54a-831ca81e9f1b","family":"Monitoring","subControls":"","weight":0,"isPublic":true,"enhancements":"","controlType":"Stand-Alone","title":"3.10 Ensure a log metric filter and alarm exist for security group changes (Scored) ","relatedControls":"","catalogueID":140,"assessmentPlan":"It is recommended that customers monitor changes to security group which will help ensure that resources and services are not unintentionally exposed.","practiceLevel":"","mappings":"","controlId":"3.10"},{"id":25052,"description":"The Quick Start creates an AWS CloudWatch Rule that matches incoming CloudWatch Events for network access control lists changes and publishes the changes to an SNS topic.","references":"Responsibility: Shared (CloudWatch Rule and Customer)","tenantsId":1,"uuid":"5930afee-e603-4417-b662-c3b1341b25da","family":"Monitoring","subControls":"","weight":0,"isPublic":true,"enhancements":"","controlType":"Stand-Alone","title":"3.11 Ensure a log metric filter and alarm exist for changes to Network Access Control Lists (NACL) (Scored) ","relatedControls":"","catalogueID":140,"assessmentPlan":"It is recommended that customers monitor changes to NACLs to help ensure that AWS resources and services are not unintentionally exposed.","practiceLevel":"","mappings":"","controlId":"3.11"},{"id":25053,"description":"The Quick Start creates an AWS CloudWatch Rule that matches incoming CloudWatch Events for network gateways, route tables and VPC changes and publishes the changes to an SNS topic. ","references":"Responsibility: Shared (CloudWatch Rule and Customer)","tenantsId":1,"uuid":"ffc5ae60-3eb8-4963-a9d3-b98eb7aa103b","family":"Monitoring","subControls":"","weight":0,"isPublic":true,"enhancements":"","controlType":"Stand-Alone","title":"3.12 Ensure a log metric filter and alarm exist for changes to network gateways (Scored) ","relatedControls":"","catalogueID":140,"assessmentPlan":"It is recommended that customers monitor changes to network gateways which will help ensure that all ingress/egress traffic traverses the VPC border via a controlled path.\r\nMonitoring changes to route tables will help ensure that all VPC traffic flows through an expected path.Monitoring changes to VPC configuration will help ensure that all VPCs remain intact.","practiceLevel":"","mappings":"","controlId":"3.12"},{"id":25054,"description":"The Quick Start creates an AWS CloudWatch Rule that matches incoming CloudWatch Events for network gateways, route tables and VPC changes and publishes the changes to an SNS topic. ","references":"Responsibility: Shared (CloudWatch Rule and Customer)","tenantsId":1,"uuid":"d02b7acf-5f67-4c27-a2bc-b610e7d1e2cf","family":"Monitoring","subControls":"","weight":0,"isPublic":true,"enhancements":"","controlType":"Stand-Alone","title":"3.13 Ensure a log metric filter and alarm exist for route table changes (Scored) ","relatedControls":"","catalogueID":140,"assessmentPlan":"It is recommended that customers monitor changes to network gateways which will help ensure that all ingress/egress traffic traverses the VPC border via a controlled path. Monitoring changes to route tables will help ensure that all VPC traffic flows through an expected path.Monitoring changes to VPC configuration will help ensure that all VPCs remain intact.","practiceLevel":"","mappings":"","controlId":"3.13"},{"id":25055,"description":"The Quick Start creates an AWS CloudWatch Rule that matches incoming CloudWatch Events for network gateways, route tables and VPC changes and publishes the changes to an SNS topic. ","references":"Responsibility: Shared (CloudWatch Rule and Customer)","tenantsId":1,"uuid":"00cf7f04-6c77-4281-8950-697faa8bfcb0","family":"Monitoring","subControls":"","weight":0,"isPublic":true,"enhancements":"","controlType":"Stand-Alone","title":"3.14 Ensure a log metric filter and alarm exist for VPC changes (Scored) ","relatedControls":"","catalogueID":140,"assessmentPlan":"It is recommended that customers monitor changes to network gateways which will help ensure that all ingress/egress traffic traverses the VPC border via a controlled path.  Monitoring changes to route tables will help ensure that all VPC traffic flows through an expected path.Monitoring changes to VPC configuration will help ensure that all VPCs remain intact.","practiceLevel":"","mappings":"","controlId":"3.14"},{"id":25056,"description":"This control is implemented as an AWS Managed Config Rule to report back the compliance status on whether security groups allow ingress from 0.0.0.0/0 to port 22. The Config rule  DOES NOT enforce this control by restricting security groups ingress traffic from 0.0.0.0/0 to port 22.","references":"Responsibility: Shared (Config rule and Customer)","tenantsId":1,"uuid":"5840eae8-850c-4506-b4ac-306c17e26785","family":"Networking","subControls":"","weight":0,"isPublic":true,"enhancements":"","controlType":"Stand-Alone","title":"4.1 Ensure no security groups allow ingress from 0.0.0.0/0 to port 22 (Scored) ","relatedControls":"","catalogueID":140,"assessmentPlan":"It is recommended that customers remove unfettered connectivity to remote console services, such as SSH, reduces a server's exposure to risk.\r\n\r\nIf the Config rule reports NonCompliance, ensure no security groups allow Ingress from 0.0.0.0/0 to port 22. For remediation, refer to control 4.1 in the document  https://d0.awsstatic.com/whitepapers/compliance/AWS_CIS_Foundations_Benchmark.pdf","practiceLevel":"","mappings":"","controlId":"4.1"},{"id":25057,"description":"This control is implemented as an AWS Managed Config Rule to report back the compliance status on whether security groups allow ingress from 0.0.0.0/0 to port 3389. The Config rule  DOES NOT enforce this control by restricting security groups ingress traffic from 0.0.0.0/0 to port 3389.","references":"Responsibility: Shared (Config rule and Customer)","tenantsId":1,"uuid":"43638344-597b-4d20-a48a-54818591543a","family":"Networking","subControls":"","weight":0,"isPublic":true,"enhancements":"","controlType":"Stand-Alone","title":"4.2 Ensure no security groups allow ingress from 0.0.0.0/0 to port 3389 (Scored) ","relatedControls":"","catalogueID":140,"assessmentPlan":"It is recommended that customers remove unfettered connectivity to remote console services, such as RDP, reduces a server's exposure to risk.\r\n\r\nIf the Config rule reports NonCompliance, ensure no security groups allow Ingress from 0.0.0.0/0 to port 3389. For remediation, refer to control 4.2 in the document  https://d0.awsstatic.com/whitepapers/compliance/AWS_CIS_Foundations_Benchmark.pdf","practiceLevel":"","mappings":"","controlId":"4.2"},{"id":25058,"description":"This control is implemented as a Config rule backed by a custom lambda function. The config rule reports back the compliance status on whether the default security groups restrict all traffic. The Config rule  DOES NOT enforce this control by configuring the default security groups.","references":"Responsibility: Shared (Config rule and Customer)","tenantsId":1,"uuid":"7ec7607e-191d-48a5-97f7-8f5223ae3233","family":"Networking","subControls":"","weight":0,"isPublic":true,"enhancements":"","controlType":"Stand-Alone","title":"4.3 Ensure the default security group of every VPC restricts all traffic (Scored) ","relatedControls":"","catalogueID":140,"assessmentPlan":"It is recommended to configure all VPC default security groups to restrict all traffic. This will encourage least privilege security group development and mindful placement of AWS resources into security groups which will in-turn reduce the exposure of those resources.\r\n\r\nIf the Config rule reports NonCompliance, ensure that the default security group of every VPC restricts all traffic. For remediation, refer to control 4.3 in the document  https://d0.awsstatic.com/whitepapers/compliance/AWS_CIS_Foundations_Benchmark.pdf","practiceLevel":"","mappings":"","controlId":"4.3"},{"id":25059,"description":"This control is implemented as a Config rule backed by a custom lambda function. The config rule reports back the compliance status on whether the VPC routing tables are configured with \"least access\". The Config rule  DOES NOT enforce this control by configuring routing tables for VPC peering.","references":"Responsibility: Shared (Config rule and Customer)","tenantsId":1,"uuid":"4139b0a5-ee5a-4513-bf75-6821c27bb7bd","family":"Networking","subControls":"","weight":0,"isPublic":true,"enhancements":"","controlType":"Stand-Alone","title":"4.4 Ensure routing tables for VPC peering are \"least access\" (Not Scored)","relatedControls":"","catalogueID":140,"assessmentPlan":"Being highly selective in peering routing tables is a very effective way of minimizing the impact of breach as resources outside of these routes are inaccessible to the peered VPC.\r\n\r\nIf the Config rule reports NonCompliance, ensure that the routing tables for VPC peering are \"least access\". For remediation, refer to control 4.4 in the document  https://d0.awsstatic.com/whitepapers/compliance/AWS_CIS_Foundations_Benchmark.pdf","practiceLevel":"","mappings":"","controlId":"4.4"}]}}