$title =

When to Upgrade Your Business Firewall: Signs to Look For

;

$content = [

Upgrade your business firewall when it can no longer reliably do its job. That means the vendor has ended support or security updates, it can't inspect modern encrypted traffic or keep up with your internet speed, it lacks features your business now needs (remote-access VPN, intrusion prevention, cloud and application controls), it's hard to manage or log, or you've had incidents or compliance gaps it can't address. If two or more of these apply, plan a replacement. If the device is end-of-life, treat it as urgent. The steps below walk through each check in order, with commands you can run today and the standards each check maps to.

1. Check whether your firewall is end-of-life or out of support

Start with the model number and serial number on the label or in the admin console. Then look up the vendor's end-of-sale, end-of-support, and end-of-life dates. Vendors publish these on lifecycle pages, and the date that matters most is end of security updates. Once it passes, every new vulnerability stays open on a device that sits at the edge of your network.

This is not a theoretical risk. Verizon's 2025 Data Breach Investigations Report found that exploitation of vulnerabilities was the initial access vector in about 20% of breaches, and that edge devices and VPNs made up roughly 22% of the targets of those exploits, up from about 3% the year before. The same report found that only about half of those edge-device vulnerabilities were fully remediated, with a median of around 32 days. CISA's Known Exploited Vulnerabilities (KEV) catalog lists many firewall and VPN flaws, such as CVE-2022-42475 in FortiOS SSL-VPN and CVE-2024-3400 in Palo Alto Networks PAN-OS GlobalProtect (CVSS 10.0). A device past end of support will never receive the fix for the next one.

Example: a small office running a firewall bought in 2017 that reached end of support in 2022 has been running without patches for years. Check the model's vendor advisories against the KEV catalog, because an unpatched firewall is often the easiest way in.

Lifecycle review is also a formal requirement in some frameworks. PCI DSS v4.0.1 Requirement 12.3.4 asks organizations to review the hardware and software technologies they use at least every 12 months, including whether vendors still provide security fixes and plans for end-of-life. CIS Controls v8 Safeguard 12.1 calls for keeping network infrastructure up to date.

  • Record model, serial number, purchase date, and current firmware version in a simple asset sheet.
  • Find the vendor's end-of-sale and end-of-support dates for that exact model.
  • If support has ended, mark the replacement as urgent. If it ends within 12 months, schedule it in this budget cycle.
  • Check whether your subscription licenses (threat signatures, web filtering) are still active, since an expired license can leave a supported device with stale protection.
  • Search your model and firmware version in the CISA KEV catalog and the vendor's security advisory page.

2. Confirm the firmware is current and still receiving security patches

A supported model can still be dangerously behind if nobody has applied updates. PCI DSS v4.0.1 Requirement 6.3.3 expects critical and high-severity security patches to be installed within one month of release, which is a reasonable benchmark even if you aren't in scope. Log in and compare the running version against the latest release. On a Linux-based firewall such as pfSense or OPNsense, or a Linux appliance, you can check from the shell:

# pfSense / FreeBSD-based
pfSense-upgrade -c
uname -a

# OPNsense
opnsense-version
opnsense-update -c

# Debian/Ubuntu-based firewall (iptables/nftables host)
apt update && apt list --upgradable 2>/dev/null | head -20

For commercial appliances (Fortinet, SonicWall, Sophos, WatchGuard, Cisco Meraki), the version appears on the dashboard. Compare it to the vendor's security advisories (for example Fortinet PSIRT, Cisco Security Advisories, or SonicWall PSIRT). If critical advisories list your version as affected and no fixed release exists for your hardware, the device has effectively aged out.

3. Review performance during peak hours

Look at CPU, memory, and session counts during your busiest hour, usually mid-morning or during backups. Sustained CPU above 80%, memory near its limit, or session tables filling up are signs the hardware is undersized. Staff will describe the symptoms as slow video calls, dropped VPN sessions, or pages that hang.

Example: a 40-person office upgraded from a 100 Mbps to a 1 Gbps fiber connection, but the firewall's rated throughput with security features on is only 150 Mbps. The firewall, not the ISP, is now the bottleneck. You can confirm this with a test from a wired PC, once with the firewall in the path and once with a direct connection if you can safely arrange it.

# Run from a wired client on the LAN, against a test server you control
iperf3 -c 192.168.1.50 -t 30 -P 4

# Sample output (illustrative)
[SUM]   0.00-30.00  sec   545 MBytes   152 Mbits/sec   sender
[SUM]   0.00-30.00  sec   543 MBytes   152 Mbits/sec   receiver

# Check load on a FreeBSD/Linux-based firewall during the test
top -b -n 1 | head -5
# CPU: 97.2% user ... <-- device is saturated

If throughput is far below your internet plan, or CPU pins at the top while the test runs, the device is too small for your current connection.

4. Test whether it inspects encrypted traffic without crippling throughput

Most web traffic is now HTTPS. Google's Transparency Report shows that well over 90% of page loads in Chrome use HTTPS in most regions. A firewall that can't inspect it can't see malware downloads, command-and-control callbacks, or risky categories hidden inside encrypted sessions. Many older devices can do TLS inspection on paper but drop to a fraction of their rated speed when it's turned on.

Check the vendor's datasheet for two numbers: firewall throughput (the large, headline figure) and threat protection or TLS inspection throughput (the realistic one). For instance, Fortinet's FortiGate 40F datasheet lists 5 Gbps of firewall throughput but well under 1 Gbps with IPS and threat protection enabled (confirm the current figures on the datasheet for your model). Gaps of 5x or more between the headline number and the protected number are normal across vendors. Compare the realistic figure to your actual peak bandwidth.

  • Enable TLS inspection for a pilot group of two or three users and rerun the iperf3 or a speed test.
  • Watch CPU while they browse and download. A jump from 20% to 90% means the hardware can't handle it.
  • Confirm the device supports TLS 1.3. NIST SP 800-52 Rev. 2 required US federal servers to support it by January 2024, and older firmware may not handle it.

5. Compare its features to what the business needs now

The firewall you bought for a single office may not fit a team that now works from home, uses cloud apps, and has a second location. List what you need today and check whether the device does each item natively.

  • Remote-access VPN or zero-trust access with multi-factor authentication for remote staff.
  • Site-to-site VPN for a branch office or cloud network (for example an IPsec tunnel to AWS Site-to-Site VPN or an Azure VPN Gateway).
  • Intrusion prevention (IPS) with regularly updated signatures.
  • Web and DNS filtering by category.
  • Application control, so you can allow Microsoft 365 and block unsanctioned file-sharing or remote-control tools.
  • Support for modern authentication, such as SAML or integration with Entra ID or Google Workspace.

If you're running a separate box or paid add-on for each of these, consolidating onto a current next-generation firewall can reduce both cost and the number of things that can fail.

6. Audit your rules, logs, and alerts

A firewall is only as good as its configuration, and old ones accumulate clutter. NIST SP 800-41 Rev. 1 (Guidelines on Firewalls and Firewall Policy) recommends a default-deny posture and periodic rule review, and PCI DSS v4.0.1 Requirement 1.2.7 requires reviewing network security control configurations at least every six months. Export the rule set and look for rules that are too broad, unused, or undocumented. Rules such as 'allow any to any' or ports opened years ago for a vendor who no longer works with you are common findings.

# Linux/nftables firewall: list the ruleset with counters
sudo nft list ruleset | less

# iptables: show rules with hit counts, find rules that never match
sudo iptables -L -n -v --line-numbers

# Example output showing a risky, unused rule
num   pkts bytes target  prot opt in  out source     destination
14       0     0 ACCEPT  tcp  --  *   *   0.0.0.0/0  0.0.0.0/0   tcp dpt:3389

In that output, rule 14 allows RDP (port 3389) from anywhere and has zero hits. It should be removed, since CISA's #StopRansomware Guide lists internet-exposed RDP among the most common ransomware entry points. On commercial appliances, use the built-in rule hit count or policy analyzer to find the same patterns.

Then check logging. Can you search for a specific IP from last month? Do logs go to a central place such as a syslog server or SIEM, or do they roll over after a few days on the device? NIST SP 800-92 (Guide to Computer Security Log Management) covers centralizing and retaining logs. If you can't answer 'who connected to what and when' during an incident, the logging is inadequate. A device so hard to manage that nobody dares change a rule is also a sign it's time to move on.

7. Check for security incidents or near-misses the firewall failed to stop

Review the last 12 months. Look for malware that got through, phishing that led to a compromised account, unexpected outbound connections, brute-force attempts that succeeded, or a ransomware scare. Ask whether the firewall detected anything, or whether you learned about it from an antivirus alert, a customer, or a bank.

Example: if endpoint protection flagged a machine beaconing to a known malicious domain and the firewall's logs show the connection was allowed with no alert, the firewall lacks working DNS or threat-intelligence filtering. One such miss is a data point. Repeated misses are a pattern that points to replacement. The cost of ignoring the pattern is high: IBM's 2025 Cost of a Data Breach report put the global average breach at about $4.44 million.

8. Verify it meets compliance and cyber insurance requirements

Frameworks and contracts often require supported, patched network security devices, logging with retention, and network segmentation. PCI DSS, HIPAA (the Security Rule's audit controls at 45 CFR 164.312(b) and risk analysis at 164.308(a)(1)), and cyber insurance questionnaires all ask about this in some form. Insurers commonly ask whether your perimeter devices are vendor-supported and whether multi-factor authentication protects remote access. An end-of-life firewall can cause a failed audit, a higher premium, or a denied claim.

  • Pull your latest insurance application and compliance checklist and answer each network-security question honestly for the current device.
  • Confirm logs are retained for the period your framework requires (for example, PCI DSS v4.0.1 Requirement 10.5.1 requires at least 12 months of audit log history, with the most recent 3 months immediately available).
  • Check that you can segment sensitive systems, such as a payment terminal VLAN, from the general network (PCI DSS Requirement 1.4 covers controls between trusted and untrusted networks).

9. Weigh repair or reconfiguration cost against replacement cost

Not every problem needs new hardware. Cleaning up rules, updating firmware, renewing a license, or adding a log server may fix some issues for little money. But if the device is end-of-life, undersized, or lacks features you need, spending on it is paying for a stopgap.

Example comparison for a 25-person office (illustrative figures based on typical small-business list pricing):

  • Keep the 2018 firewall: $0 hardware, about $600 per year for a renewed subscription (if still offered), plus about $1,500 in consulting to clean up rules. Still no vendor patches, no real TLS inspection, and 150 Mbps real throughput on a 500 Mbps connection.
  • Replace with a current small-business next-generation firewall: roughly $800 to $1,800 for hardware, $400 to $900 per year for a security subscription, and about $1,000 to $2,000 for installation and migration. Supported for 5 or more years, with throughput that matches the connection.

Prices vary by vendor and region, so get two or three quotes. Count the cost of one hour of downtime for your business, then compare the replacement to a breach at even a fraction of the IBM average above, and the replacement usually looks small.

10. Decide on an upgrade and plan the replacement and migration

Count how many of the signs above apply. If two or more do, plan a replacement. If the device is end-of-life, do it now. Then plan the migration so it doesn't interrupt work.

  • Size the new device from real numbers: peak bandwidth, number of users and devices, and the inspection throughput you need, with 30 to 50 percent headroom for growth.
  • Export and back up the current configuration, then document every rule, port forward, VPN tunnel, and DHCP reservation.
  • Remove rules you no longer need instead of copying them over.
  • Stage the new firewall and test it with a few devices before cutover.
  • Schedule the switch for an evening or weekend, and keep the old firewall available for a rollback for at least a week.
  • After cutover, verify VPN, email, cloud apps, and any phone system, and check that logs are flowing to your central store.
  • Turn on automatic security updates, set a calendar reminder for the new device's end-of-support date, and review the rule set every six months.

Basic post-migration checks from a client machine confirm the essentials are working:

# Confirm outbound connectivity and DNS
ping -c 3 1.1.1.1
nslookup microsoft.com

# Confirm a blocked category is actually blocked (should fail or show a block page)
curl -I https://known-blocked-test-site.example

# Confirm RDP is NOT reachable from outside (run from an external network)
nmap -Pn -p 3389 203.0.113.10
# Expected: 3389/tcp filtered

Checking these ten items once a year takes an afternoon. It also lines up with the annual technology review in PCI DSS 12.3.4 and the six-month rule review in 1.2.7, and it tells you whether the device is still protecting the business or only giving the impression that it is.

Sources and further reading

  • Verizon, 2025 Data Breach Investigations Report (vulnerability exploitation and edge-device findings).
  • CISA, Known Exploited Vulnerabilities (KEV) Catalog, including CVE-2022-42475 (FortiOS) and CVE-2024-3400 (PAN-OS).
  • CISA, #StopRansomware Guide (RDP and remote-access exposure).
  • NIST SP 800-41 Rev. 1, Guidelines on Firewalls and Firewall Policy.
  • NIST SP 800-52 Rev. 2, Guidelines for the Selection, Configuration, and Use of TLS Implementations.
  • NIST SP 800-92, Guide to Computer Security Log Management.
  • PCI Security Standards Council, PCI DSS v4.0.1: Requirements 1.2.7, 1.4, 6.3.3, 10.5.1, and 12.3.4.
  • HHS, HIPAA Security Rule, 45 CFR 164.308 and 164.312.
  • Center for Internet Security, CIS Controls v8, Safeguard 12.1.
  • IBM, Cost of a Data Breach Report 2025.
  • Google Transparency Report, HTTPS encryption on the web.
  • Vendor datasheets and security advisory pages (Fortinet PSIRT, Cisco Security Advisories, SonicWall PSIRT) for your specific model.

];

$date =

;

$category =

;

$author =

;

$next =

;