CyberKit

Security Groups and NACLs

Also called Cloud firewall rules, Network ACLs.

Virtual firewall rules that filter traffic to cloud workloads and subnets.

What it is

Cloud-native network controls where security groups act as stateful filters around instances and network access control lists act as stateless filters at the subnet boundary. Together they define what traffic can reach a workload.

Why it matters

Overly permissive rules are a common cause of exposure and lateral reach, and the rule history is valuable evidence when reconstructing how an attacker entered or moved.

In practice

An investigator finds a security group changed to allow remote access from any address minutes before the unauthorized login.

What to look for

  • Rules allowing 0.0.0.0/0 to admin ports such as SSH and RDP.
  • Overly broad port ranges or allow-all rules added during troubleshooting.
  • Security groups attached to resources that no longer exist or need them.

Common mistake

Forgetting that rules stack. A tight group can be undone by another group on the same resource.

Use it in CyberKit

In the field

Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.

  • Amazon GuardDuty Cloud service

    AWS threat detection that analyzes CloudTrail, VPC flow logs and DNS logs.

  • Microsoft Defender for Cloud Commercial

    Posture and threat protection for Azure, AWS and Google Cloud.

  • Wiz Commercial

    Maps cloud resources, identities and exposures into one graph of risk.

  • Prowler Open source

    An open source tool that checks cloud accounts against benchmarks such as CIS.

Read next

Sources