Our Firewall Was Hacked and What a Business Does Before Anything Else
Your firewall was the thing that got hacked. What owners should ask, why the update is not the answer, and how to protect your servers and backups.
Most business owners have never logged in to their firewall, and they should not have to. It is the box, or the cloud service, that sits between your office and the internet and decides what gets in. It is also usually the thing that lets your staff connect from home through a VPN, short for virtual private network, which is the secure tunnel that makes a laptop at a kitchen table behave as if it were sitting in the office. Nobody thinks about it until the day someone says it was the thing that got hacked.
That day arrived for a lot of businesses in November 2026. On November 6, SonicWall disclosed a flaw in the remote access feature of its newer firewalls that lets someone holding a stolen password skip the second login step entirely, and the federal Cybersecurity and Infrastructure Security Agency, known as CISA, added it to its list of flaws already being used in real attacks the same day. A week later, Check Point confirmed that attackers had taken full control of its firewalls at what the company called "a couple of dozen customers," hidden a purpose-built back door inside them, and in some cases used the firewall as a launch point to wipe the servers behind it. CISA gave federal agencies three days to fix that one.
This post is for the owner, office manager or controller in McKinney, Allen, Plano or anywhere else in North Texas who has just heard "our firewall" and "compromised" in the same sentence. It covers what you need to decide in the first day, and why "we installed the update" is not enough this time.
Why a Hacked Firewall Is a Different Kind of Problem
When a single laptop gets infected, you have one problem on one machine. When the firewall gets taken over, the problem is the device that every other device trusts. Everything your business sends to the internet passes through it. Every remote employee signs in through it. It often holds the passwords for the VPN, the accounts your IT team uses to manage it, and connection details for other systems inside the office.
There is a second reason that matters even more to you as an owner. The firewall keeps the record of who came and went. When something goes wrong, the first thing an investigator normally asks for is that record, the firewall logs, which are the running list of connections the device allowed or blocked. In the Check Point attacks, the back door the attackers installed could edit those logs. In plain terms, the people you are investigating may have rewritten the visitor book before you opened it.
That changes how a business has to respond. You cannot simply ask the firewall whether it was broken into, because a firewall controlled by an attacker will tell you whatever the attacker wants. Every important answer has to come from somewhere else.
It helps to understand that the two November incidents look very different from your side of the desk, because they leave different evidence and call for different first steps.
The SonicWall flaw is quiet. MFA, short for multi-factor authentication, is the second step after a password, usually a code or a phone prompt, that is supposed to stop a criminal who has only stolen the password. Many SonicWall firewalls quietly accept more than one way of logging in, often a leftover from before the company set up its current sign-in system. This flaw lets someone with a valid password come in through one of those older paths and never see the second step. The result is not a crash or an alarm. It is an ordinary-looking remote login from what appears to be one of your employees. Stolen passwords are bought and sold constantly, which is why we watch for staff credentials through dark web monitoring, but the business point is simpler. If MFA was the control your insurance application promised, this flaw quietly took it away.
The Check Point attack is loud, at least at the end. Attackers broke in through the remote access web page on the firewall, using a pair of flaws in the PHP software that runs that page. We wrote about those PHP flaws in late October, and Check Point says the probing started roughly a week after fixes for them became available. From that foothold, the attackers used a second flaw to gain complete control of the firewall, planted a hidden back door designed specifically for Check Point devices, and used the firewall itself to map the network behind it. On some victims, they then moved to the servers that run all of the company's other servers and ran a program that overwrote every file with zeros.
Different shapes, same lesson for an owner. The device that was supposed to stand guard became the way in, and the evidence you would normally rely on cannot be trusted on its own.
The First Calls to Make Today
If your firewall is a SonicWall or a Check Point, or you do not know what brand it is, the first call is to whoever runs your IT, whether that is one person on staff or an outside company. Ask it as a business question, and ask for answers in writing with dates.
Start with what brand and model of firewall you have, and whether the remote access feature is turned on. For Check Point, the specific question is whether the Mobile Access portal is switched on and who on the internet can reach it, and whether the fix Check Point published under advisory sk1000362 has been applied to every Check Point device you own, along with the earlier PHP fixes. For SonicWall, the question is whether the firewall is on the fixed version, and whether remote logins can still come in through any path other than your main company sign-in.
Then ask the question that matters most. Has anyone looked for signs that the attacker was already inside before the fix went on, and where did they look? A good answer mentions specific checks and specific dates. A vague answer, or "the logs look clean," is not good enough for the reason described above. If you are not sure whether your remote access page is even visible from the internet, an outside vulnerability scan of your public addresses will tell you in plain terms what the world can see.
Finally, decide who is in charge. If an outside IT company runs your firewall and you also bring in an incident response team, someone has to own each step, and that needs to be agreed before anyone starts unplugging things. That split of duties is exactly what a co-managed IT arrangement is meant to settle in advance. We wrote about the same question for a different tool in our post on a hacked remote management tool, and the principle carries over: one owner per step, written down.
Why "We Installed the Update" Does Not Close the Case
An update, which the industry calls a patch, fixes the flaw. It does not remove anything an attacker installed before the fix went on. In the Check Point case, the attackers chose a back door that survives backups and snapshots of the device, so restoring the firewall's own saved settings can bring the back door right back with them. We covered the general version of this problem in what to check after you install a security update. Firewalls are the sharpest example of it.
So the useful question is not "are we patched." It is "were we exposed and unpatched at any point, and for how long?" Our advisory on the Check Point attacks recommends treating any firewall that had its remote access portal open to the internet, and unpatched at any time after late October, as potentially compromised. For SonicWall, the honest window to review is at least the last 30 days of remote logins.
Here is what that looks like in a real office. Picture a 30-person distributor in Allen whose IT company applied the firewall fix on a Friday. Everyone relaxes. The following Wednesday, the accounting system is unreachable and the file server will not start. The update was not wrong. It arrived after someone had already moved in, and nobody went looking. The cost of that week is not the firewall. It is two or three days of no invoicing, no shipping and no payroll processing while the business waits to find out what is left.
Checking From Outside the Firewall
Because the firewall's own record may have been altered, the evidence has to come from systems the attacker did not control. That is the core of a digital forensics review, which is a structured investigation that preserves evidence first and then works out what happened, in an order that will stand up to an insurer or a lawyer later.
For a business owner, the practical requirement is this. Before anyone wipes, rebuilds or "cleans" the firewall, make sure a copy of its current state and its logs is preserved, and make sure records from other places are gathered too. That can include connection records from your internet provider's equipment, sign-in records from your company email and identity system, and the logs on the servers behind the firewall. For SonicWall, the telling check is simple to describe. Every remote login on the firewall should have a matching MFA approval in your sign-in system at the same moment. A login with no matching approval is the one to chase.
For Check Point, the investigator will look for specific traces Check Point published, including a hidden program disguised under a harmless-sounding system name, unexpected files on the remote access web page, and connections to a known attacker address. You do not need to know those details. You need to know that someone is checking for them, using records the attacker could not edit.
This step costs time on day one and saves money for months afterward. A preserved timeline is what lets you answer the questions your insurer, your clients and possibly your attorney will ask: when did they get in, what could they reach, and was any customer information exposed.
When the Attack Reaches the Servers Behind It
The part of the Check Point story that should worry every owner is the wipe. Most small and midsize businesses no longer run one physical server per job. They run one or two powerful machines, called hypervisors, which are computers whose whole purpose is to host many virtual servers at once. Your accounting system, file shares and line-of-business software may all live on the same box. In the Check Point attacks, the intruders used the firewall to reach those hypervisors by signing in with the behind-the-scenes account that the virtualization management software uses, then ran a program that overwrote the files with zeros and deleted them.
When a hypervisor is wiped, you do not lose one system. You lose everything that ran on top of it at the same moment. The only real answer is a copy of your data the attacker could not reach. That means backups that are either kept offline or stored so they cannot be changed or deleted for a set period, which the industry calls immutable. It also means backups that have actually been restored in a test, not just reported as "successful" by a nightly email.
Ask your IT provider two questions this week, whether or not you think you were hit. Could someone who controlled our firewall reach the management side of our servers? And if every server in our building were wiped tonight, how long would it take to be invoicing again, and has that ever been tested? Those answers decide whether a firewall breach is a bad week or a business-ending month.
If They Find Something, Rebuild Instead of Clean
If the review finds evidence of a break-in, the instinct is to remove the bad files and get back to work. With this kind of back door, that instinct is expensive. The safe path for a compromised firewall is to rebuild it from known good software rather than try to clean it, because an implant that survives backups and snapshots is very good at still being there three weeks later.
Rebuilding also means replacing every secret the firewall knew. That includes the VPN passwords and keys, the administrator passwords for the firewall and its management console, and the service account the attackers used to reach your servers. For a SonicWall, it means resetting passwords for everyone who can use remote access, starting with anyone whose password has shown up in breach data, and turning off the older login paths so the main company sign-in is the only way in. It is tedious work, and it touches every remote employee, so plan the communication to staff before you start.
This is also the point where the business side takes over. Talk to your insurance carrier early, because many policies have notice requirements and preferred response firms. Keep a simple written timeline of what you learned and when. If the review shows customer information was reachable, Texas notification rules may apply. None of those conversations go well without the preserved evidence from the step before.
Getting Help From a Team in McKinney
Innovation Network Design is headquartered in McKinney and works with businesses across Collin County and North Texas. When a firewall is in question, our first job is to preserve the evidence, check from outside the device, and give you a plain answer about what was reachable, while your IT provider keeps the lights on. If you are not sure whether your firewall was exposed, or you want a second opinion on what your provider has told you, call us at 512-518-4408 or reach us through our contact page. If nothing is on fire today, a free security assessment is a calm way to find out what your firewall and backups would do on a bad day.
Frequently Asked Questions
How do I know if my business firewall was hacked?
You usually cannot tell from the firewall alone, because an attacker with control of it can edit its logs. The reliable check compares the firewall's records with records from other systems, such as your email sign-in history and your internet provider's equipment. Ask your IT provider whether that comparison has been done and for what dates.
Our IT provider installed the firewall update. Are we safe now?
The update closes the flaw, but it does not remove anything an attacker installed before it went on. In the Check Point attacks, the back door survives backups and snapshots of the device. If your firewall was exposed and unpatched at any point after late October, it should be checked for signs of a break-in.
Can a hacked firewall lead to ransomware or wiped servers?
Yes. In the November 2026 Check Point attacks, intruders used the firewall to map the network behind it, then reached the servers that host other servers and ran a program that overwrote files with zeros. That is why offline or unchangeable backups that have been tested are the most important protection after a firewall breach.
Should we replace a hacked firewall or just clean it?
Rebuild it from known good software, and replace every password and key it stored. Check Point describes the back door used in these attacks as one that persists through backups and snapshots, so cleaning it in place is a gamble. Preserve a copy of the device and its logs first, so the investigation still has evidence to work with.
Happening right now?
Business email taken over, or a payment sent to the wrong account?
Call us now. The first hours matter most: your bank may still be able to recall the payment, and whoever is in the mailbox keeps access until it is locked down. We handle the lockout and help trace the payment.
Not an emergency? Get a free security assessment instead.
Mark Sullivan
Innovation Network Design
With nearly a decade in cybersecurity and IT infrastructure, our team delivers expert insights to help businesses in McKinney, Dallas, and across DFW make informed security decisions. Have a question? Get in touch.
Ready to Secure Your Business?
Get a free security assessment and find out where your organization stands.