
Guide
How to Choose and Size a Business Firewall: Features, Throughput and VPN
Choose a business firewall by what it must inspect, and size it with the datasheet figure measured under those conditions. Write the policy first: block what is not expressly permitted, as NIST SP 800-41 Rev. 1 advises. List the services you will run, such as intrusion prevention and TLS inspection, and compare models on the matching throughput, not on the headline firewall figure. Then plan IKEv2 for site-to-site VPNs, MFA for remote users, zones for internal traffic, logs kept off the device and a management interface kept off the internet.
Updated November 2026
What a next-generation firewall adds to a stateful firewall
NIST SP 800-41 Rev. 1 defines stateful inspection as packet filtering that also tracks the state of connections and blocks packets that deviate from it; its rules decide by address, port and protocol. A next-generation firewall (NGFW) also looks inside the traffic it allows. The term is a market label, not a standard, but RFC 9411, an IETF benchmarking methodology for these devices, recommends testing an NGFW with these features on: application identification, intrusion prevention (IPS), anti-virus, anti-spyware, anti-botnet, anti-evasion and TLS inspection, which decrypts sessions so the other engines can see inside them. Many products add sandboxing, which first runs unknown files in an isolated environment. Because TLS 1.3 (RFC 8446) encrypts every handshake message after the ServerHello, the server certificate included, a firewall that does not decrypt sees less of each session than with TLS 1.2. Every engine switched on consumes processing power.
How to read a firewall datasheet
- Firewall throughput: stateful filtering only, usually the largest number.
- IPS or threat-prevention throughput: with intrusion prevention on and, often, anti-malware and application control too; the name varies by vendor.
- TLS inspection throughput: often the smallest figure.
- IPsec VPN throughput, concurrent connections and new connections per second.
RFC 9411 (March 2023) shows why test conditions matter: it asks testers to enable the recommended security features and logging, document the traffic mix, sustain the load for at least 300 seconds and state in the report the OSI layer at which throughput was measured, because figures measured at different layers are not directly comparable. Ask each vendor for the conditions behind every number.
Sizing from internet speed, users and enabled services
- Start from the speed of the internet links, counting a backup link if both can run at once.
- Add the traffic the firewall will route between internal networks, such as cameras to a recorder.
- Compare the total with the figure for the services you will run: threat-prevention throughput for IPS and anti-malware, TLS-inspection throughput if traffic will be decrypted.
- Check the connection figures against users and devices, and VPN throughput against branches and remote users at the busiest hour.
- Leave headroom for the years the unit will serve.
SP 800-41 Rev. 1 recommends testing performance under realistic load before deployment and monitoring resources afterward.
VPN choices: site-to-site IPsec and remote access
Between sites, use IPsec with IKEv2. NIST SP 800-77 Rev. 1 (June 2020) says IKEv1 should not be used for new deployments, and RFC 9395 (April 2023) deprecated it. The NIST guide says 3DES, MD5, SHA-1 and Diffie-Hellman (DH) groups 2 and 5 should not be used, and calls for AES-GCM, or AES-CBC with HMAC-SHA-2, with DH group 14 or elliptic-curve group 19, 20 or 21. Hardening guidance from CISA, the NSA, the FBI and agencies of Australia, Canada and New Zealand (December 2024) recommends AES-256, SHA-384 or SHA-512 and DH group 15, 16 or 20. Where both ends support it, use the stricter of the two sets.
For remote staff, SP 800-77 Rev. 1 notes that TLS-based (SSL) VPNs usually run on port 443, which most networks let through, but, because they usually run as an application, perform significantly worse than kernel-based VPNs such as IPsec. Either way, require MFA for every user and expose only the VPN ports needed.
Segmentation: zones, VLANs and the rules between them
A firewall protects only the traffic that passes through it. SP 800-41 Rev. 1 warns that infected internal hosts can attack from within and recommends internal firewalls in front of important systems. Give each group its own VLAN and zone (staff, servers, guests, cameras, phones, network management) and apply deny by default between them: guests reach only the internet, cameras only their recorder. The same guide asks that this rule apply to IPv6 as it does to IPv4. The guide to planning a business network shows a VLAN layout, and the security camera system guide covers the camera network.
High availability, logs and subscriptions
- High availability (HA). Two identical units, one active and one on standby, share the configuration and usually the connection state; the standby takes over if the active unit fails. HA covers a failure of the active unit, not an outage of the internet service itself. SP 800-41 Rev. 1 asks that policy synchronization between firewalls be tested in several scenarios, such as with a node offline. Ask whether the standby unit needs its own subscriptions.
- Logs. The February 2025 edge-device guidance led by Canada's cyber security agency (CCCS), with CISA and the NSA among the contributing agencies, asks for centralized, off-device logging, as detailed as possible. CIS Safeguard 8.10 (Implementation Groups 2 and 3) asks for at least 90 days of audit logs; contracts or regulations may require more, so check the rule that applies to you.
- Subscriptions. Signatures, malware analysis, web filtering, cloud management and firmware support are often sold for a term. Ask what stops working when one lapses.
Configuration hygiene: hardening the firewall itself
Firewalls and VPN gateways face the internet by design, and attackers target them. Between them, the CCCS edge-device guidance and the CISA-led communications infrastructure guidance ask administrators to:
- change default credentials and require phishing-resistant MFA for administration;
- manage devices from an out-of-band management network or a dedicated administrative workstation, never from the internet;
- turn off unused features and plaintext services such as Telnet, and use only SNMP version 3 with authentication and encryption;
- patch soon after testing on a standby or test unit, and replace devices before end of life;
- apply default-deny rules in both directions and log denied traffic.
For U.S. federal civilian agencies, CISA's BOD 23-02 (June 2023) makes a version of the management rule binding: within 14 days of discovery by the agency or notification by CISA, an exposed management interface on a firewall, router or VPN concentrator must come off the internet or go behind Zero Trust access controls. Look up your firewall's vendor and product in CISA's Known Exploited Vulnerabilities catalog and patch listed flaws first.
Field notes: firewalls at hot, humid and outage-prone sites
- Heat and humidity. Compare the operating ranges on the datasheet with the temperature of the network closet on a hot afternoon with the air conditioning off.
- Second internet link of another type, such as fixed plus cellular, with automatic failover. Failover usually changes the public address, so tunnels defined by a fixed peer address need dynamic DNS or another plan.
- Power. Put the firewall, the internet modem or terminal and the core switch on the same UPS; computers on battery are of little use if the firewall goes dark.
- Saved configuration. SP 800-41 Rev. 1 advises backing up firewall policies and rule sets regularly. Keep the latest copy off the device, so a replacement unit is loaded rather than rebuilt by hand, and protect it, since it can contain VPN keys.
- Private remote management. Reach a site through a VPN into its management network or an MFA-protected vendor console, never through an administration page open to the internet. Set up and test that path before closing management access from the internet, or the site can lose remote administration.
Checklist: what to prepare before buying a firewall
- Internet links: number, type, speed, fixed or dynamic addresses.
- Sites, users, devices and remote workers over the life of the unit.
- Services to switch on, and the matching datasheet figures with their test conditions.
- Zones, and which ones may talk to each other.
- Whether a standby unit or a second link is needed.
- Where logs go and how long they are kept.
- Subscription terms and the model's end-of-support date.
- Who approves rule changes and where configuration copies are kept.
Common mistakes: buying on firewall-only throughput, a temporary “allow any” rule left in place, a management page open to the internet, remote access with a password alone, and IKEv1 kept after a migration.
Frequently Asked Questions
Is the router that comes with an internet service enough as a business firewall?
Usually not. NIST SP 800-41 Rev. 1 advises using devices as they were intended: routers are meant for routing, and complex filtering can overload their processors. A provider's router rarely offers per-zone rules, intrusion prevention or detailed logs. Use it for the connection, preferably in bridge mode, and put a dedicated firewall behind it.
Does TLS inspection cause problems?
It can. The firewall decrypts each session and re-encrypts it with its own certificate, so every company device must trust the firewall's certificate authority. Applications that pin their certificates break and need exceptions, and banking or health sites are often exempted on purpose. Rules on inspecting staff traffic vary by country and sector: check the rule that applies to you first.
How often should firewall rules be reviewed?
NIST SP 800-41 Rev. 1 sets no fixed interval, but asks for reviews at regular intervals, not only during audits or emergencies, within a formal change process. Each review examines every change since the last one, who made it and under what circumstances, and should uncover rules that are no longer needed; a comment on each rule makes that easier.
What happens when a firewall reaches end of life?
After the end-of-support date the vendor stops releasing firmware fixes, so new vulnerabilities stay open. The CCCS-led edge-device guidance asks administrators to review upcoming end-of-life dates periodically and to plan their removal or replacement before those dates. Note the date when you buy and budget for the replacement ahead of it.
Sources
- NIST SP 800-41 Rev. 1, Guidelines on Firewalls and Firewall Policy (September 2009)
- NIST SP 800-77 Rev. 1, Guide to IPsec VPNs (June 2020)
- IETF RFC 9411, Benchmarking Methodology for Network Security Device Performance (March 2023)
- IETF RFC 9395, Deprecation of the Internet Key Exchange Version 1 (IKEv1) Protocol and Obsoleted Algorithms (April 2023)
- IETF RFC 8446, The Transport Layer Security (TLS) Protocol Version 1.3 (August 2018)
- CISA, NSA, FBI, ASD's ACSC, CCCS and NCSC-NZ, Enhanced Visibility and Hardening Guidance for Communications Infrastructure (December 2024)
- Canadian Centre for Cyber Security with ASD's ACSC, NCSC-NZ, NCSC-UK, CISA and NSA, Security considerations for edge devices, ITSM.80.101 (February 2025)
- CISA, Binding Operational Directive 23-02: Mitigating the Risk from Internet-Exposed Management Interfaces (June 13, 2023)
- Center for Internet Security, CIS Controls Navigator v8.1 (Safeguard 8.10, Retain Audit Logs)
- CISA, Known Exploited Vulnerabilities Catalog
About this guide
This guide is by GlobalTech Corp. of Hormigueros, Puerto Rico, where it provides IT and cybersecurity services backed by over 25 years of experience. As a SonicWall Certified MSSP for Puerto Rico, it deploys and manages next-generation firewalls, VPN and SonicWall Capture ATP with centralized threat management. Its work reaches businesses all over Puerto Rico; in Florida it supports clients remotely and goes on site if a project demands it. The next-generation firewall service page lists what that service covers, and the page on SonicWall firewalls in Puerto Rico follows a firewall project on the island step by step. Figures and recommendations reviewed in November 2026.
More guides: Technology Guides.