Firewall Guide: Choose, Configure, and Test a Firewall

A firewall is a policy enforcement point. Start with the traffic and trust boundary you need to control, then choose the narrowest rule that solves the problem and verify the result.

Start with how a firewall evaluates traffic when the boundary or stateful behavior is still unclear.

When a policy already exists, use the firewall testing workflow to verify the intended allow and deny outcomes.

A firewall boundary allowing an approved packet path while stopping an unrelated connection

Choose a firewall by trust boundary

Match the control to the boundary that actually sees the traffic. A host firewall, router, and managed gateway solve different parts of the same path.

Starting recommendations for Firewall Guide: Choose, Configure, and Test a Firewall
SituationRecommended starting pointReason
One computerUse the operating system firewallApplication-aware rules are usually easier to maintain than open ports.
Home networkUse the router firewall plus device firewallsThe router controls the boundary while each device protects itself on local networks.
Small officeUse a managed gateway and host firewallsLogging, segmentation, backups, and a documented rule owner matter more than a long feature list.

Guides in this section

Use the mechanism guide for first principles, the software and hardware guides for selection, the testing guide for planned verification, and the troubleshooting guide when real traffic fails or bypasses policy.

How Firewalls Work

Learn how stateful, application, host, and network firewalls make traffic decisions and where their protection ends.

Updated October 31, 2026

A practical firewall workflow

Firewall work becomes easier to review when it follows the lifecycle of a rule rather than a product feature list.

Define the boundary

Identify which networks, devices, applications, or users have different trust. A firewall placed at the wrong boundary cannot observe or control the communication you care about.

Write the intended traffic

Describe source, destination, direction, protocol, service, owner, and purpose before opening a console. This turns a vague request into a rule another person can review.

Test and maintain

Verify one allowed case and one blocked case, preserve the evidence, and set a review date. Remove the rule when the service or owner disappears.

Before you make a change

  • Inventory trust boundaries and active services.
  • Prefer supported built-in controls before adding complexity.
  • Keep rules narrow, named, owned, and reviewable.
  • Preserve configuration backups and a rollback path.
  • Recheck policy after network, application, or firmware changes.

Questions about this section

Where should a home firewall be located?

Use the router or gateway at the internet boundary and host firewalls on computers. Each layer sees a different part of the communication path.

What is the first sign of a weak firewall policy?

Rules without an owner, purpose, or expiry are difficult to justify and are likely to outlive the service they were created for.

How firewall guidance stays current

Firewall recommendations are reviewed against NIST policy guidance, current platform documentation, and the operational evidence a reader can verify. Unsupported product-review URLs are consolidated into current selection criteria instead of retaining expired rankings.

Review our methods