Question 1

Is associate_public_ip_address enforced for SOC 2?

Accepted Answer

Yes, Manage access to the AWS Cloud by ensuring AWS Elastic Compute Cloud (AWS EC2) instances cannot be publicly accessed.

Question 2

Is ebs_optimized enforced for SOC 2?

Accepted Answer

Yes, An optimized instance in AWS Elastic Block Store (AWS EBS) provides additional, dedicated capacity for AWS EBS I/O operations.

Question 3

Is ebs_volumes enforced for SOC 2?

Accepted Answer

Yes, Because sensitive data can exist and to help protect data at rest, ensure encryption is enabled for your AWS Elastic Block Store (AWS EBS) volumes.

Question 4

Is metadata_options enforced for SOC 2?

Accepted Answer

Yes, Ensure the Instance Metadata Service Version 2 (IMDSv2) method is enabled to help protect access and control of AWS Elastic Compute Cloud (AWS EC2) instance metadata.

Question 5

Is monitoring enforced for SOC 2?

Accepted Answer

Yes, Enable this rule to help improve AWS Elastic Compute Cloud (AWS EC2) instance monitoring on the AWS EC2 console, which displays monitoring graphs with a 1-minute period for the instance.

Question 6

Is security_group_ingress_rules enforced for SOC 2?

Accepted Answer

Yes, This control checks whether the VPC security groups allow ingress from 0.0.0.0/0 or ::/0 to cassandra ports 7199 or 9160 or 8888. This control passes when none of the rules in a security group allow ingress traffic from 0.0.0.0/0 from ports 7199 or 9160 or 8888.

Question 7

Is subnet_id enforced for SOC 2?

Accepted Answer

Yes, Deploy AWS Elastic Compute Cloud (AWS EC2) instances within an AWS Virtual Private Cloud (AWS VPC) to enable secure communication between an instance and other services within the amazon VPC, without requiring an internet gateway, NAT device, or VPN connection.

AWS EC2 Instance Terraform module

Terraform Module Source