Compliancemanzill.com
CIS Amazon Web Services Foundations Benchmark v1.2.0

CIS Amazon Web Services Foundations Benchmark v1.2.0/Networking/48 of 49

4.3Ensure the default security group of every VPC restricts all traffic

Control family: Networking

Control description

A VPC comes with a default security group whose initial settings deny all inbound traffic, allow all outbound traffic, and allow all traffic between instances assigned to the security group. If you don't specify a security group when you launch an instance, the instance is automatically assigned to this default security group. Security groups provide stateful filtering of ingress/egress network traffic to AWS resources. It is recommended that the default security group restrict all traffic.

The default VPC in every region should have its default security group updated to comply. Any newly created VPCs will automatically contain a default security group that will need remediation to comply with this recommendation.

**NOTE:** When implementing this recommendation, VPC flow logging is invaluable in determining the least privilege port access required by systems to work properly because it can log all packet acceptances and rejections occurring under the current security groups. This dramatically reduces the primary barrier to least privilege engineering - discovering the minimum ports required by systems in the environment. Even if the VPC flow logging recommendation in this benchmark is not adopted as a permanent security measure, it should be used during any period of discovery and engineering for least privileged security groups.

How to implement

ResponsibilityCustomerYou configure and operate this in your own cloud accounts.

Every VPC comes with a default security group, and anything launched without a group chosen lands in it. Emptying it of all rules means a forgotten instance is cut off rather than quietly connected, and it pushes teams to create groups that say what each workload needs. Flow logs (2.9) show what traffic those groups must allow.

Before you start

The same on every cloud, before the steps in the tabs.

  • Agree that every workload gets its own security group, designed from flow log data, and that the default group stays empty.
  • Plan the move off the default group with each workload owner, so nothing loses connectivity unexpectedly.

Evidence

  • The security group standard and the migration plan per workload

On AWS the tasks move resources off the default group, remove all its rules in every VPC, and add the AWS Config rule that checks it stays empty.

Task 1Move resources off the default security group

  1. Sign in to the AWS Management Console at console.aws.amazon.com and open EC2 > Network Interfaces.
  2. Search for interfaces whose security group is named default, in each Region.
  3. For each one, create a purpose-built security group with only the ports the flow logs show are needed.
  4. Open the instance or service that owns the interface and change its security groups to the new group, removing default.
  5. Check it: searching Network Interfaces for the default group returns nothing.

Task 2Remove every rule from the default security groups

  1. Open VPC > Security groups and filter on the group name default.
  2. Select a default group, open the Inbound rules tab and choose Edit inbound rules.
  3. Choose Delete on every rule and choose Save rules.
  4. Do the same on the Outbound rules tab.
  5. Repeat for the default group of every VPC in every Region, including VPCs created later.
  6. Check it: each default group shows no inbound and no outbound rules.

Task 3Keep it checked with the AWS Config rule vpc-default-security-group-closed

  1. Open AWS Config in each Region and choose Rules > Add rule.
  2. On Specify rule type, search for vpc-default-security-group-closed, select it and choose Next.
  3. On Configure rule, keep the name, then choose Next.
  4. On Review and create, check the settings and add the rule.
  5. Check it: once the rule has finished Evaluating..., every default security group shows as compliant.

Evidence

  • The vpc-default-security-group-closed rule in each Region, showing compliant
  • Security Hub CSPM control EC2.2, showing passed
  • A search of EC2 > Network Interfaces showing nothing still attached to a default group

Console steps as of 5 November 2026. Not every step has been confirmed in a live console yet, and menus and labels can move between releases, so look for the nearest match if one has changed.