---
title: An end-of-support firewall is still on your internet edge (e.g. SonicWall Gen 6): shrink its exposure, check it for compromise, and replace it | ctxsec
url: https://ctxsec.com/playbooks/end-of-support-edge-firewall-still-in-service-response
---

[← Playbooks](/playbooks)

# An end-of-support firewall is still on your internet edge (e.g. SonicWall Gen 6): shrink its exposure, check it for compromise, and replace it

For teams that still run edge firewalls or VPN appliances that no longer get security fixes. Built from SonicWall's Nov 18, 2026 advisory retiring Gen 6/6.5, which says no patches will ship even for Critical flaws and that internet-facing units are expected to be targeted.

For: Network / firewall admins, SOC, IT leadership

[1. Find every unsupported unit](#s1)[2. Cut the attack surface now](#s2)[3. Check it hasn't already been used](#s3)[4. Replace and record the risk](#s4)

1.

Step 1 of 4

__

### Find every unsupported unit

Spares, branch boxes and virtual firewalls are the ones that get missed.

   - Pull model and firmware from your asset inventory, vendor cloud portal and SNMP/config backups; compare against the vendor's end-of-support table
   - Include virtual appliances (e.g. SonicWall NSv 10-1600) and DR/standby units
   - Rank by exposure: WAN management on, SSL VPN on, public IPs

2.

Step 2 of 4

__

### Cut the attack surface now

You can't patch it, so reduce what's reachable.

   - Disable HTTPS/SSH management on WAN interfaces; manage only from an internal jump host
   - Turn off SSL VPN or move remote access to a supported device; if VPN must stay, enforce MFA and remove stale local accounts
   - Restrict any remaining exposed services to known source IPs

3.

Step 3 of 4

__

### Check it hasn't already been used

Edge devices are a common first foothold for ransomware crews.

   - Review admin and VPN login history for unknown users, new local accounts and logins from unexpected countries
   - Diff the running config against a known-good backup: new NAT/port forwards, address objects, admin users or SNMP communities
   - Rotate admin, VPN, LDAP/RADIUS bind and any shared secrets stored on the device; hunt internally for activity from the firewall's inside IP

4.

Step 4 of 4

__

### Replace and record the risk

Make the decision visible until the box is gone.

   - Order replacements for internet-facing units first and set a decommission date
   - Record a formal risk acceptance with an owner for anything that must stay temporarily
   - Subscribe to the vendor's advisories: a fix for supported models tells attackers what to try on unsupported ones

Original content by ctxsec. Printable checklist: use your browser's print view.
