Knowledge is Power

Sitewide Search

Search Bare Metal Cyber

Search exact control and technique identifiers, Cyber Wiki articles, framework records, playbooks, books, podcasts, Academy courses, individual lessons, and BMC Cyber Challenge activities.

Network controlIntermediate

Cloud Security Groups and Network ACLs

Security groups, firewall rules, and network access-control lists restrict traffic at resource, subnet, or network boundaries.

What it means

Different controls may be stateful or stateless and may apply at different points in the path. Effective design depends on understanding evaluation order, inheritance, and default behavior.

Why it matters

Broad or overlapping rules are a common source of cloud exposure and can remain invisible when teams focus only on perimeter firewalls.

Practical focus

  • Use least-access rules tied to workload purpose
  • Prefer references to trusted identities or groups where supported
  • Review unused, shadowed, and overly broad rules

Common mistakes

  • Opening management ports to the internet
  • Assuming a deny rule works the same across providers
  • Using one shared rule set for unrelated workloads

BMC v0.2.2 cornerstone expansion

Start analysis of Cloud Security Groups and Network ACLs with the mission or business outcome, then identify assets, identities, data, trust boundaries, dependencies, expected behavior, and credible failure or abuse cases.

Translate those observations into preventive, detective, responsive, and recovery controls. A mature explanation states not only what the concept is, but also how a practitioner demonstrates that it is working under normal, abnormal, and recovery conditions.

Evidence of effective implementation

  • Documented ownership, scope, decision criteria, and permitted exceptions.
  • Configuration or architectural evidence tied to a clear control objective.
  • Operational telemetry showing expected and unexpected behavior.
  • Testing that covers normal use, abuse cases, failure, rollback, and recovery.
  • Exceptions that are approved, time bounded, monitored, and revisited.
  • Lessons learned that result in updated designs, procedures, detections, or training.

Questions for learners

  • Which security properties and business outcomes does Cloud Security Groups and Network ACLs support?
  • What assumptions must remain true for the control or process to work safely?
  • What could an attacker, insider, failure, or design error do at each trust boundary?
  • Which evidence would prove that controls work continuously rather than only on paper?
  • How would the organization respond, restore service, and re-establish trust after failure?

Certification relevance

This subject appears in or supports the following certification bodies of knowledge:

AWS Cloud PractitionerAzure AZ-900Google Cloud Digital LeaderCompTIA Cloud+GIAC GCLDISC2 CCSP

Authoritative sources