This rule ensures VPC default security group restricts all inbound and outbound traffic.
Rule | VPC default security group should not allow inbound and outbound traffic |
Framework | NIST 800-171 Revision 2 |
Severity | ✔ Medium |
Rule Description
The VPC default security group should not allow inbound and outbound traffic for NIST 800-171 Revision 2 compliance.
Description
The VPC (Virtual Private Cloud) default security group is automatically created when setting up a VPC in AWS (Amazon Web Services). It serves as a default security measure for controlling inbound and outbound traffic within the VPC. However, to comply with NIST 800-171 Revision 2, it is necessary to restrict inbound and outbound traffic for the default security group.
Troubleshooting Steps
Necessary Codes
There are no specific codes for this rule/policy. The configuration changes will be made through the AWS Management Console or AWS CLI (Command Line Interface).
Step-by-Step Guide for Remediation
Using AWS Management Console:
Using AWS CLI:
aws ec2 describe-security-groups --filters Name=vpc-id,Values=<Your_VPC_ID>
aws ec2 revoke-security-group-ingress --group-id <Your_Default_Security_Group_ID> --protocol -1 --source-security-group-name default
aws ec2 revoke-security-group-egress --group-id <Your_Default_Security_Group_ID> --protocol -1 --destination-security-group-name default
Conclusion
By following the provided troubleshooting steps and using the AWS Management Console or AWS CLI, you can ensure that the VPC default security group does not allow any inbound or outbound traffic that violates NIST 800-171 Revision 2 guidelines. This helps maintain better security and compliance for your AWS environment.