Articles

Firewall policy and ACLs: two different answers about the same packet

A firewall policy sets intent; an ACL is the mechanism that carries it onto the device.

Reading: 5 minNetworking

Article cover: Firewall policy and ACLs: two different answers about the same packet

A firewall policy and an access control list (ACL) meet the same packet and give two different answers. The policy answers should traffic of this kind cross here at all — the organisation’s statement of intent, written from a risk analysis and the information security policy. The ACL answers does this packet match a statement on this device, and what does it say to do — one mechanism that carries intent onto the wire. Read one as the other and two mistakes appear: a rule list that is valid yet enforces the wrong policy, and a policy sentence no packet-level list can express.

The two layers, and which way the intent flows

The policy sits above the ruleset and is its source. NIST defines it as what “dictates how firewalls should handle network traffic for specific IP addresses and address ranges, protocols, applications, and content types (e.g., active content) based on the organization’s information security policies”. The policy is a human decision; the ruleset is the form a device can evaluate. Intent flows downward — from the security policy, through the firewall policy, into rules, and onto each packet.

organisational security policy
        + risk analysis
              |
              v
      firewall policy            intent: what may cross, and why
              |
          expressed as
              v
      ruleset / ACL              mechanism: statements a device evaluates
              |
          applied per packet by
              v
      the enforcing device       per-packet decision: match, then act

Two questions about one packet

At an enforcing device a packet meets a matching question: does it match a statement here, and what does that statement instruct? The mechanism answers it thousands of times a second.

The policy asks a slower question: should communication of this kind exist between these two zones? A person answers it once. NIST puts intent first — before the policy is written, “some form of risk analysis should be performed to develop a list of the types of traffic needed by the organization and categorize how they must be secured” — and sets deny by default: firewalls “should block all inbound and outbound traffic that has not been expressly permitted by the firewall policy”.

The mechanics of an individual list — order, matching, actions, default — are a sibling subject, not developed here.

Terms

  • Firewall policy — the documented statement of how the firewalls should handle traffic for given addresses, protocols, applications and content types, grounded in the information security policy.
  • Ruleset — the ruleset that “describes how the firewall acts”; the expression of the policy a device evaluates.
  • ACL (access control list) — the packet-filtering mechanism a routing device uses to permit or deny traffic by address, protocol or port. One way to express part of a policy, not a policy.
  • Stateless and stateful — a stateless filter keeps no memory of flows; a stateful engine “keeps track of each connection in a state table”.
  • Policy decision point (PDP) and policy enforcement point (PEP) — the component that decides access and the one that enforces it.
  • Deny by default — the policy default that blocks everything not expressly permitted.

How intent becomes a ruleset

  1. Perform the risk analysis: the traffic the organisation needs, and how each kind must be secured.
  2. Write the policy: what may cross which boundary, and the default. Document it in the system security plan.
  3. Choose the mechanism that can express that part — a stateless list, a stateful engine, an application filter; different mechanisms enforce different subsets of the same policy.
  4. Translate the policy into rules: “These rulesets should implement the organization’s firewall policy as documented in the system security plan”.
  5. Apply the rules where the traffic is decided and enforced.
  6. Review and log; policy and rulesets change with the organisation and belong to change management.

Where the two answers diverge

Take one policy sentence: the internet may reach the public web tier on its service ports; the database tier may be reached only from the application tier. On a router this becomes a packet-filtering list; on a stateful firewall part of it becomes connection state. The same words map onto different mechanisms, because the policy never named one.

Invert it: a list of rules can be individually valid and still fail the policy, because the policy is not stored in the ruleset. The rules tell you what the device does, not what the organisation decided. Validity of a rule is not compliance with the policy.

Limits and the common mistake

  • The list is not the policy. A review that reads only the ruleset checks the implementation; it cannot judge the intent.
  • Not every policy fits a packet list. Packet filtering “does not see the identities of the users who are communicating in the traffic”; identity, application and content policy need a mechanism with more context.
  • The mechanism bounds the answer. A stateless filter cannot associate separate requests within one session; a stateful engine can.
  • The policy is only as sound as its risk analysis.
  • Security note. A policy that exists only as a ruleset is undocumented and unverifiable. Deny by default is the safer start, and policy and rulesets belong to change management with periodic review.

Level and prerequisites

L3 — integration and technical control. It fixes the boundary between a policy and the mechanism that enforces it, not how a device is configured. Prerequisites: the L1 vocabulary of protocols, ports and packet forwarding, and the L2 sheets on switching, VLANs and static routing. The ACL mechanics are the sibling L3 subject.

Where to go next

References

  • NIST — Guidelines on Firewalls and Firewall Policy (Special Publication 800-41 Revision 1, September 2009) — the definition of a firewall policy and its basis in a risk analysis (lines 1127–1131); the deny-by-default default (lines 1138–1143); the packet filter as the basic firewall feature, the ruleset that governs it, and the router’s access control list as the pure packet-filtering example (lines 412, 418–421); stateful inspection and the state table (line 494); packet filtering that cannot see user identity (line 1414); the ruleset that “describes how the firewall acts” and its obligation to implement the documented policy (lines 1684–1685, 1691–1692).
  • NIST — Guide to a Secure Enterprise Network Landscape (Special Publication 800-215, November 2022) — https://doi.org/10.6028/NIST.SP.800-215 — the policy decision point and the policy enforcement point as separate roles (lines 1110–1115); firewalls at different positions enforcing granular access-control policy (lines 687–693); firewall rules that “block or allow communication with each group or segment” (lines 1192–1193).
Nodrius Field Kit — cover

Get the Nodrius Field Kit

Enter your email and we'll send you the complete Field Kit: eight technical resources in one download.

Your email address is sent to Nodrius and used to deliver the Field Kit to you by email. Marketing messages are separate and optional: the checkbox does not affect your download, and you are only added to our updates list if you tick it. Privacy Policy.

Privacy & cookies

This site does not use cookies, analytics or tracking, and it does not profile you. There is nothing technical to switch off, so Accept and Reject change nothing about how the site works: either choice lets you browse everything normally.

The only difference is what your browser remembers: two entries in local storage — your choice here, so this notice is not shown again, and a marker that the Field Kit offer has already been made — so the offer is presented once and not on every page. They contain no identifier, they are not shared with anyone, and the site sets no cookie for either.

What we do with your data
How your email address is used when you ask for a Resource, how long it is kept and which rights you have — in the Privacy Policy.
What the site stores in your browser
Two entries in local storage — your choice on this notice and whether the Field Kit offer has been shown — and no cookies, no session storage, no third-party content: in the Cookie Policy.