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 | FedRAMP Moderate Revision 4 |
Severity | ✔ Medium |
Rule Description:
The default security group within a Virtual Private Cloud (VPC) should not allow any inbound or outbound traffic that is not compliant with the Federal Risk and Authorization Management Program (FedRAMP) Moderate Revision 4 requirements. This rule ensures that the default security group is configured to align with the specified security standards.
Troubleshooting Steps:
Neccessary Codes:
No specific codes are required for this rule. However, if necessary, you may need to use the AWS Command Line Interface (CLI) to modify the security group rules.
Remediation Steps:
Open the AWS Management Console and navigate to the VPC service.
Select the appropriate VPC from the list.
Click on the "Security Groups" tab.
Identify the default security group associated with the VPC.
Click on the default security group to view its details.
Review the inbound and outbound rules configured for the default security group.
Determine which rules do not comply with the FedRAMP Moderate Revision 4 requirements.
To remove an existing rule, locate the rule in the "Inbound Rules" or "Outbound Rules" section and click the "Edit" button.
Remove the rule by clicking the "x" icon next to it.
If necessary, add new inbound or outbound rules that comply with the FedRAMP Moderate Revision 4 requirements.
To add a new rule, click the "Edit" button in the corresponding section.
Click the "Add Rule" button.
Configure the new rule according to the required settings specified in FedRAMP Moderate Revision 4.
Save the changes and exit the security group configuration.
Repeat steps 8-14 for any additional rules that need to be modified or added.
Once all the necessary changes have been made, confirm that the default security group now adheres to the FedRAMP Moderate Revision 4 requirements.
CLI Command:
No specific CLI commands are required for this rule. The remediation steps can be accomplished through the AWS Management Console.