This rule ensures all EC2 instances are securely placed within a VPC.
Rule | EC2 instances should be in a VPC |
Framework | NIST Cybersecurity Framework (CSF) v1.1 |
Severity | ✔ High |
Rule Description:
The rule states that all EC2 instances should be deployed within a Virtual Private Cloud (VPC) to comply with the NIST Cybersecurity Framework (CSF) v1. The VPC provides a secure and isolated environment for EC2 instances, helping to protect sensitive data and prevent unauthorized access.
Troubleshooting Steps (if applicable):
Check if the EC2 instance is currently associated with a VPC. You can do this by selecting the instance in the AWS Management Console and inspecting the "Virtual Private Cloud (VPC)" field.
If the instance is not associated with a VPC, it needs to be migrated to a VPC. Follow the step-by-step guide below for the necessary steps.
If the instance is already associated with a VPC, ensure that the VPC is properly configured with appropriate security groups, network ACLs, and subnets according to your security requirements.
Necessary Codes (if applicable):
No specific code snippet is provided for this rule as it involves configuring the infrastructure and settings in the AWS Management Console or AWS CLI.
Step-by-Step Guide for Remediation:
Determine the desired VPC architecture: Decide whether you want to use the default VPC or create a new VPC.
Create a new VPC (if needed):
Migrate EC2 instance to the VPC:
Verify the association with the VPC:
Repeat steps 2 to 4 for any other EC2 instances that are not associated with a VPC.
Conclusion:
By ensuring that all EC2 instances are deployed within a VPC, you comply with the NIST Cybersecurity Framework (CSF) v1. This helps to establish a secure network architecture, protecting confidential data and reducing the potential attack surface.