Imagine a critical vulnerability that lands on a Monday. The vendor has a fix, and your security team wants it installed today. The problem is that the system in question runs the billing platform that your finance team relies on every day and the update could break the integrations that connect it to everything else. Nobody wants to take that system offline during month-end. So the patch waits and the vulnerability stays exposed.
This is far more common than most people expect. And they would usually imagine that patching is just a button to click, but in practice, it is a decision with trade-offs. Testing takes time. Some systems have no vendor support left at all, and some flaws have no fix yet. Yet, leaving those gaps as they are, is of course, never a good answer. Waiting for a perfect fix should not mean waiting with no protection in place.
This is where virtual patching comes in.
Why patching doesn’t always happen on time
Let us go back to May 2017, when the WannaCry ransomware spread across the world within hours. Microsoft had released a fix for the underlying Windows flaw in supported versions two months prior, in March. A lot of machines still hadn’t been updated yet when the attack hit. Some simply missed it. Others were held back because the updated probably needed testing first, or because the systems were running software that no longer had standard support.
Microsoft’s response was unusual. It issued an emergency patch for Windows XP, an operating system that had already stopped receiving routine updates for years. The episode showed something useful for any business: a patch existing is not the same as a patch being applied, and the gap between the two is where attackers operate.
Many organisations won’t be able to close that gap overnight. That’s actually a normal state of affairs, and not a failure. What matters is how you manage the time in between and whether the people responsible for that time know exactly what they are protecting against. A patch sitting in a queue with no interim protection is a risk nobody has agreed to carry, even if nobody has written it down.
What virtual patching actually means
Virtual patching is a way to block attacks on a vulnerability without changing the vulnerable software itself. Security controls such as web application firewalls, intrusion prevention systems or firewall rules are configured to recognise and stop traffic that matches known exploitation attempts. The vulnerable system keeps running as it is but the door it leaves open is covered.
The Log4Shell vulnerability in the late 2021 showed how this works in practice. The flaw was in a logging library used by a huge range of applications and it was easy to exploit. Within days of it becoming public, security providers including Cloudflare and Google Cloud published firewall rules designed to block the known attack patterns for customers using their services. Businesses still had to update their softwares and many of them took weeks to do so. The rules bought them time and reduced their exposure while that work went on.
The thing is, virtual patching is not a permanent fix. It reduces the chance of exploitation but it doesn’t remove the flaw. Attackers constantly find new ways around filters so a rule that worked yesterday may need adjusting tomorrow. The underlying vulnerability still needs to be fixed and the virtual patch should be treated as a temporary measure with a clear end date.
Why penetration testing matters
Here’s the part many teams skip. Installing a firewall rule or an intrusion prevention signature feels like progress, and in many cases, it is. But the important question is whether the control actually stops an attacker. Because rules can contain typos, miss an alternative path into the same system or only cover one of several ways the flaw can be reached.
This is where penetration testing becomes valuable. An authorized tester can try the same routes an attacker would, check if the virtual patch blocks them, and look for ways around it. They can also check whether an attacker who gets past the workaround could move on to other systems. The result is evidence rather than assumption.
Security controls should be tested, not simply trusted. This principle applies just as much to temporary measures as to permanent ones. A penetration test turns “we think this is covered” into “we tried to get in and here’s what happened.” The evidence is useful in two ways. It tells the technical team if the workaround is working, plus, it gives leadership a clear picture of the risk that remains while the permanent fix is being scheduled. Either way, the decision to keep a system running with a known flaw becomes a conscious one, supported by facts.
It’s also worth testing the workaround after any change. A firewall rule that worked last month may behave differently after a configuration update, so any workaround needs to be checked again whenever the environment around it changes, however small the change seems.
A practical plan while you wait
If a vulnerability cannot be patched straight away, the first job is to understand the risk. Virtual patching only makes sense once you know what you’re protecting and why it matters to the business. Work out which systems are exposed, how important they are and how an attacker would reach them. That usually means looking at internet-facing services first, followed by the systems that hold sensitive data and then anything connected to both.
Next, put a compensating control in front of the exposed system. Here, virtual patching sits alongside segmentation rather than replacing it, and the two work best together. That might be a firewall rule, a web application firewall signature or tighter network segmentation that limits where the system can talk. Segmentation is worth a special mention because it limits the damage if an attacker does get in. Keeping a vulnerable away from the rest of the network means a single compromise doesn’t turn into a wider incident.
Then watch the system closely. Unusual traffic, unexpected logins and changes to configuration should all trigger a closer look and someone needs to be responsible for reviewing those alerts. Monitoring turns a temporary workaround into a managed risk rather than a hope.
Finally, test the controls and set a deadline. Penetration testing confirms the workaround does what you think it does. A remediation date, agreed with the business, keeps the temporary measure form becoming permanent. The best outcome is a fix that goes in on schedule with the workaround removed afterwards.
Netpluz can help you
Netpluz;s offensive security services are built around this kind of validation. Vulnerability assessment helps you find weaknesses across your systems and prioritise them, and penetration testing checks whether those weaknesses can actually be exploited, including whether the controls you’ve out in place stop an attack. Together they help you decide what to fix first and if the workaround is good enough for the time being.
If your team is holding a vulnerability that can’t be patched yet, the next step does not have to be a big project. A short conversation with our team can help you map the exposure, decide what needs testing and plan the path to a permanent fix. There is no need to have all the answers before you call. Usually, the most useful step is simply a clear list of the systems that cannot be patched yet, the reasons why, and who owns each one. That list alone tends to reveal where the biggest gaps sit.



