A security vendor has reported that a flaw in its own firewall is being actively exploited by attackers. Whoever finds the flaw gets root access: full control of the device that lets all traffic in and out of your business. This is news about Check Point, but the lesson behind it applies to any business with a firewall, regardless of brand.
What exactly happened
Check Point reported that a vulnerability in the software of its gateway, another word for a firewall, is being actively exploited. An attacker who finds this vulnerability doesn’t need to log in first or guess a password. They immediately gain root access, the highest level of control a device can have. With that, they can inspect traffic, redirect it, erase logs, and reach other systems on the network.
Why this device is different from the rest
A firewall holds a special place in your network. It’s the device that all traffic between your business and the outside world passes through, and the device that decides what gets let in and what doesn’t. You rely on it to filter, watch, and warn.
When an attacker takes over that device itself, that trust is gone. Every other measure you’ve taken, a strong password policy, a backup, antivirus software on workstations, loses its value the moment the gate itself stands open. This isn’t a flaw like most others. It doesn’t affect one workstation or one application, but the foundation the rest of your security rests on.
What this means for your business
If you don’t use Check Point, this particular flaw isn’t your problem. The question behind it is: do you know exactly which devices in your network play this role, and who makes sure updates for those devices get applied the moment a supplier releases them?
At many businesses we talk to, a firewall was bought once, configured, and never actively followed up on again. No one structurally checks whether the supplier has issued a warning. Updates sometimes go uninstalled for months, simply because no one has been explicitly given that task.
What you can do right now
Start with an overview. Which firewalls and gateways do you have, which brand, which firmware version? Without that overview, you can’t set policy, because you don’t know what you’re deciding about.
Then record who’s responsible. Not ‘the ICT department’ in general terms, but a name, or a party you’ve agreed with that these devices get followed and updates applied within a fixed timeframe. Only once that responsibility is clearly assigned does it make sense to tighten technical measures, such as automatic updates or extra monitoring on the device.
Make sure you can also show when a device was last updated and by whom. That’s not pointless administration. It’s the difference between a feeling of security and demonstrable security, something you’ll increasingly be asked for on the way to being demonstrably ready for NIS2.
How we look at this
We never treat a firewall as a standalone product you buy once and then forget. It belongs to the network and security domain, with devices, updates, and responsibilities that belong together and get watched as a whole. First measure what’s in place and how current it is, then record policy on who does what and within what timeframe, and only after that set up the technology around it. That way, you avoid only taking action the moment the next flaw makes the news.
A few questions we’re often asked
We don’t use Check Point, should we still do something?
This specific flaw only affects Check Point devices, but the underlying question applies to any firewall brand. Check whether you know which firmware version is running on your device and when it was last updated. You can ask that question right now, regardless of brand.
How do we know if our firewall is vulnerable?
That’s described in the manufacturer’s security advisory, which states which versions are affected and from which version the issue is fixed. If you don’t know exactly which version you’re running, that itself is a sign your overview is missing.
Is automatic updating enough to prevent this kind of problem?
Automatic updating helps, but it doesn’t replace policy. You need to know which devices may update automatically, which should not without review, and who gets notified if an update fails. Without those agreements, you risk an update arriving but never actually being checked.
Who should pick this up if we don’t have our own ICT department?
Even if your ICT is outsourced, it still matters that someone within your business knows who carries that responsibility and within what timeframe updates get applied. Simply ask your current partner about it, rather than assuming it happens automatically.
Want to know which devices in your network play this role and whether the responsibility for updates is clearly assigned? We’re happy to think it through with you.