Our Solution
After doing a deep analysis on client's compliance requirements, SecureKloud suggested the usage of AWS Config and AWS OpsWorks to ensure continuous compliance and Center for Internet Security (CIS) benchmark are maintained across the client infrastructure.
AWS Config provides a detailed view of the resources associated with the AWS account, including how they are configured, how they are related to one another, and how the configurations and their relationships have changed over time.
AWS OpsWorks for Chef Automate provides a fully managed Chef server and suite of automation tools to automate testing for compliance and security and a user interface to give visibility into the nodes. The Chef server gives a full stack automation by handling operational tasks such as software and operating system configurations, package installations, database setups, and more.
SecureKloud helped Idols, Inc to reduce the investment on time and manpower to ensure continuous compliance by configuring AWS Config rules and AWS OpsWorks for Chef Automate. Following are the config rules that ensures continuous compliance in the environment.
- Untagged EC2 resources: Checks whether the resources have at least one tag attached to it
- IAM password policy enabled: Checks whether the account password policy for IAM users meets the specified requirements
- Cloud Trail enabled: Checks whether AWS CloudTrail is enabled in the AWS account
- Approved AMIs by Ids: Checks whether running instances are using specified AMIs
- Unattached Volumes: Checks whether EBS volumes are attached to EC2 instances
- Unattached EIPs: Checks whether all EIP addresses allocated to a VPC are attached to EC2 instances or in-use ENIs
- Unattached ENIs: Checks whether all ENIs created within the VPC are attached to EC2 instances
- MFA for IAM Users: Checks whether the IAM users in the AWS account require multi-factor authentication for console sign-in
- EC2 instances within a VPC:Checks whether the EC2 instances belong to a virtual private cloud (VPC)
- S3 Bucket Public Read/Write restricted: Checks that all the S3 buckets in the AWS account do not allow public read/write access
- Disallow unrestricted incoming SSH traffic: Checks whether security groups that are in use disallow unrestricted incoming SSH traffic
- DB instance Backup enabled: Checks whether RDS DB instances have backups enabled
- Instances launched with approved Instance types: Checks whether all the EC2 instances in the AWS account are of the approved instance types
- IAM User Policy Check: Checks that none of the IAM users have policies attached