Easy ReviewDOP-C02
Security and Compliance13

Network Firewall

Route VPC traffic through firewall endpoints and control packet and flow inspection.

Network Firewall needs both a routing path and an inspection policy. Stateless actions determine whether packets reach stateful domain and Suricata rules.

Firewall endpoints and routing

AWS Network Firewall filters VPC traffic that is routed through its firewall endpointsA firewall endpoint is the VPC traffic insertion point for a firewall policy.. An endpoint is the insertion point for inspection. Creating the firewall and steering packets through it are separate parts of the setup.

How it works

  1. Reserve dedicated firewall subnets in the selected Availability Zones. Keep application resources in other subnets.
  2. Create endpoints with the firewall policy. A policy selects the stateless packet rules and stateful flow inspection rules.
  3. Update route tables, which choose the next destination for packets, to insert the endpoint into the required path. In the internet-gateway example, the customer subnet sends internet traffic to the endpoint and the firewall subnet sends it to the gateway.
  4. Route the response through the same endpoint. Stateful inspectionStateful inspection evaluates packets in the context of their traffic flow. needs both directions of the flow, the related request and response packets.
  5. Configure stateful-engine logging when needed. Use Firewall Manager for centrally managed deployments across an organization.
Firewall Manager model Deployment
Distributed Firewalls and endpoints in accounts and VPCs within scope
Centralized A firewall in a single VPC
Import existing firewalls Existing firewalls governed by a Firewall Manager policy

Exam cues

  • If the question says a firewall exists but traffic bypasses it, think route tables, because the endpoint inspects traffic routed through it.
  • If the question says requests and responses take different firewall paths, think symmetric routingSymmetric routing sends both directions of a flow through the same firewall endpoint., because stateful inspection needs the same endpoint for both directions.
  • If the question says deliver firewall flow logs to a stream, think a Firehose log destination, because Network Firewall supports it directly.

Remember

  • Reserve endpoint subnets exclusively for Network Firewall.
  • An endpoint cannot inspect traffic entering or leaving its own subnet.
  • Endpoint associations support additional endpoints and VPCs within the documented zone constraints.
  • Stateful log destinations are S3, CloudWatch Logs, and Firehose; log types include flow, alert, and TLSTLS is a protocol for encrypting network connections..
  • A firewall can attach directly to a transit gateway.
  • TLS inspection decrypts, inspects and re-encrypts traffic.

Trap: Adding a firewall without changing the required routes does not put application traffic on the inspection path.

Example outbound path; return traffic uses the same endpoint
12EC2 workloadFirewall endpointInternet
  1. The customer subnet route sends internet-bound traffic to the firewall endpoint.

  2. The firewall subnet route sends inspected internet-bound traffic to the internet gateway; return routing inserts the same endpoint.

From the AWS docs (11)
  • Network Firewall filters traffic using stateless packet rules and stateful inspection of traffic flows.
  • For VPC firewalls, provide a subnet in each selected Availability Zone; reserve endpoint subnets exclusively for Network Firewall.
  • A firewall endpoint cannot filter traffic entering or leaving the subnet where the endpoint resides.
  • VPC endpoint associations allow multiple endpoints in an Availability Zone and endpoints in additional VPCs, limited to zones supported by the primary firewall VPC endpoints.
  • After creating a firewall, update VPC route tables to insert its endpoints into the traffic path, including both directions to filter incoming and outgoing traffic.
  • For the documented internet-gateway topology, customer-subnet routes point internet traffic to the firewall endpoint, gateway routes point return traffic to it, and firewall-subnet routes point internet traffic to the gateway.
  • Stateful inspection requires request and response traffic for a flow to pass through the same firewall endpoint.
  • Network Firewall can send stateful-engine flow, alert, and TLS logs to S3, CloudWatch Logs, or a Firehose delivery stream.
  • Firewall Manager supports distributed Network Firewall deployments, a centralized firewall in one VPC, and importing existing firewalls for policy management.
  • A Network Firewall can attach directly to a transit gateway as a firewall attachment, giving central inspection without provisioning firewall endpoints in an inspection VPC.
  • A TLS inspection configuration lets Network Firewall decrypt inbound and outbound TLS traffic, inspect it with stateful rules and re-encrypt it before forwarding.

Stateful, domain, and Suricata rules

AWS Network Firewall first checks packets independently, then can inspect them as part of a connection. Stateless means each packet is judged alone. Stateful means inspection uses the traffic flow. SuricataSuricata is an intrusion prevention engine with a rule language supported by Network Firewall. is the rule language supported by the stateful intrusion prevention engine.

How it works

  1. Evaluate stateless rules first. Their action passes, drops, or forwards the packet to stateful inspectionStateful inspection evaluates packets in the context of their traffic flow.. If none matches, apply the configured default stateless action.
  2. Forward traffic that needs domain or Suricata inspection to the stateful engine. Stateless Pass bypasses that engine.
  3. Choose domain lists for hostname matching or Suricata rule strings for explicit traffic conditions. HTTP_HOST reads the HTTP Host headerThe HTTP Host header identifies the hostname requested by an HTTP client.; TLS_SNI reads Server Name IndicationSNI is a TLS handshake field that identifies the hostname requested by a client., the hostname sent in a TLSTLS is a protocol for encrypting network connections. handshake.
Stateless action Result
Pass Permit the packet and end inspection
Drop Block the packet and end inspection
Forward to stateful rules Send the packet to flow inspection

Exam cues

  • If the question says a stateful deny is bypassed by a stateless allow, think change Pass to Forward to stateful rules, because Pass ends inspection.

Remember

  • Unmatched stateless traffic uses configured defaults; full packets and UDP fragments have separate settings.
  • TLS SNI hostname inspection does not itself decrypt HTTPS payloads.

Trap: A stateful rule cannot inspect a packet already permitted by stateless Pass. The packet must be forwarded to the stateful engine.

Stateless decisions control access to stateful inspection
inspectPassDropForwardpermitPacketStateless engineDestinationStateful engineBlocked
From the AWS docs (8)
  • Network Firewall evaluates stateless rules first and only sends packets to stateful inspection when the stateless action forwards them.
  • Stateless Pass permits the packet and ends inspection; Drop blocks it; Forward to stateful rules sends it to stateful inspection.
  • Packets that match no stateless rule use the configured default stateless action; full packets and UDP fragments have separate default settings.
  • The stateful engine inspects packets in the context of their traffic flow and supports Suricata-compatible rules for intrusion prevention.
  • Suricata-compatible rule strings define traffic match conditions and actions for the stateful engine.
  • TLS_SNI domain rules match the hostname in the TLS handshake; HTTP_HOST rules match the HTTP Host header.
  • With default action order, an Allow domain list using HTTP_HOST or TLS_SNI blocks nonmatching domains for the selected protocol; with strict order, this implicit denial does not apply.
  • Domain filtering based on HTTP Host or TLS SNI does not itself decrypt encrypted payloads; TLS inspection uses a separate TLS inspection configuration.

Rule group capacity and evaluation order

AWS Network Firewall rule groups reserve processing capacity when they are created, and stateful rules run in an order the policy chooses. Both settings shape what a firewall can hold and which rule wins, so they matter when a central firewall grows or inspects traffic for other VPCs.

How it works

  1. Size each rule group at creation. Its capacity is fixed; later rule updates cannot exceed it, and a firewall policy reserves the whole configured capacity of every group it references.
  2. To grow past that capacity, create a replacement group and point the policy at it.
  3. Choose the stateful rule order. Default action order evaluates pass, then drop, reject and alert. Strict order follows rule group priority and the order of rules inside each group.
  4. For domain list rules in a central inspection VPC, set HOME_NET to include the other VPC address ranges. By default it covers only the VPC where the firewall is deployed.

Exam cues

  • If the question says a rule group has run out of capacity, think a replacement group, because capacity cannot be raised in place.
  • If the question says rules must run in an exact sequence, think strict order, because default order groups rules by action.
  • If the question says domain filtering misses traffic from spoke VPCs, think HOME_NET, because its default is the firewall’s own VPC range.

Remember

  • Rule group capacity: fixed at creation, fully reserved by each referencing policy.
  • Default stateful order: pass, drop, reject, alert.
  • HOME_NET default: the deployment VPC range.

Trap: Editing rules cannot push a rule group past the capacity chosen at creation. Plan headroom or replace the group.

From the AWS docs (4)
  • Rule-group capacity is fixed at creation and cannot be changed or exceeded by later rule updates.
  • A firewall policy reserves the entire configured capacity of a referenced rule group.
  • By default domain inspection HOME_NET is the deployment VPC address range; centralized inspection of other VPC ranges requires including those ranges in HOME_NET.
  • Default stateful action order is pass, drop, reject, then alert; strict order follows rule-group priority and the order of rules within each group.

Flashcards

tap to flip
Answer

·

All 13 cards as a list

What does AWS Network Firewall inspect, and where are its VPC endpoints placed?

It applies stateless packet rules and stateful flow inspection. Place endpoints in dedicated firewall subnets in the selected Availability Zones.

A team creates an AWS Network Firewall but application traffic is not inspected. What must it check?

Check VPC route tables. Insert firewall endpoints into the required traffic path and route both directions through the same endpoint for stateful inspection.

An application shares the AWS Network Firewall endpoint subnet and its traffic bypasses inspection. Why?

A firewall endpoint cannot inspect traffic entering or leaving its own subnet. Move the application to a separate subnet and route its traffic through the endpoint.

How should a team route traffic for stateful inspection by AWS Network Firewall?

Route both directions of each traffic flow through the same firewall endpoint.

Which Firewall Manager management models are available for AWS Network Firewall across an organization?

Distributed deployment, centralized deployment in one VPC, and importing existing firewalls.

A company routes VPC traffic through AWS Transit Gateway and wants central AWS Network Firewall inspection without building an inspection VPC. What fits?

A transit gateway-attached firewall.

AWS Network Firewall stateful rules must inspect HTTPS payloads. What is required?

A TLS inspection configuration, which decrypts, inspects and re-encrypts the traffic.

Outbound HTTP and HTTPS traffic from private subnets must use only approved domains. Which AWS Network Firewall rules fit?

Use stateful domain-list rules with HTTP_HOST and TLS_SNI, route traffic through endpoints, and forward it from stateless to stateful inspection. Account for the domain Allow behavior of the chosen rule order.

AWS Network Firewall has a stateless Pass rule and a stateful domain deny rule. Why can matching traffic bypass the domain block?

Stateless Pass ends inspection. Use Forward to stateful rules for traffic that must reach the stateful domain rule.

Does an AWS Network Firewall TLS_SNI domain rule decrypt HTTPS request bodies?

No. It matches the hostname in the TLS handshake. Payload decryption requires a separate TLS inspection configuration.

An AWS Network Firewall rule group needs more capacity after creation. Can the team raise its capacity in place?

No. Capacity is fixed at creation. Create a replacement rule group with sufficient capacity and update the policy reference.

A central AWS Network Firewall inspects other VPCs, but their traffic misses domain-list filtering. Which variable should the team review?

HOME_NET. Include the other VPC address ranges; its default covers only the deployment VPC.

What changes when AWS Network Firewall uses strict order for stateful rules?

Groups follow configured priority and rules follow their listed order, rather than the default pass, drop, reject, alert action order.

You finished every topic of DOP-C02!

Your badge turned gold. Next step: book the exam on AWS. Once you pass, add yourself to Who passed.

Share

Share that you finished this certification

I finished every topic of AWS Certified DevOps Engineer - Professional (DOP-C02) on Easy Review. Come study too!