833-847-3280
Schedule a Call

Securing the Unpatchable in Your Network

A man is sitting in front of an unpatchable printer with "hacked" being printed out, and on the computer screen.

The recent disclosure of a critical vulnerability affecting millions of Brother printers, one that cannot be patched, has sparked serious concern among IT and security professionals. It’s a stark reminder that not every security flaw can be resolved through a software update or firmware fix.

For organizations relying on legacy or embedded systems, unpatchable vulnerabilities are not a theoretical concern. They are a persistent reality.

So, what do you do when you can’t patch? The answer lies in a multi-layered approach that combines technical, procedural, and strategic controls to contain and mitigate the risk.

 

Know What You’re Dealing With: Asset Inventory and Risk Profiling

The first step is understanding exactly what you’re dealing with. Organizations must have a clear, up-to-date inventory of all devices on the network, including peripherals like printers, scanners, and network-connected IoT devices. Too often, these devices fall through the cracks of traditional IT asset management, creating blind spots for security teams.

Once identified, each device should be assessed for its function, exposure, and risk profile. Devices that connect to sensitive systems or handle confidential data demand greater scrutiny than those with limited access.

 

Containment Through Segmentation

Once the vulnerable devices are identified, the next priority is to implement network segmentation. By isolating these endpoints from the broader network, typically by assigning them to a dedicated VLAN or subnet, organizations can dramatically reduce the risk of lateral movement should a compromise occur.

Communications to and from the device should be tightly controlled through firewalls and access control lists. Only the necessary protocols and ports should be open, and only to explicitly defined endpoints such as a print server or a few authorized clients.

 

Strengthen Devices with Compensating Controls

Even with isolation, compensating controls must be put in place. Many modern printers and embedded devices offer basic security features that are often disabled by default. Enabling authentication for users who wish to print, enforcing secure release mechanisms that require user presence, and disabling unnecessary services or ports can all reduce the attack surface.

For sensitive environments, restricting printing functionality entirely to virtual machines or print servers that serve as choke points can be an effective approach.

 

Monitor Like It Matters

Monitoring becomes especially critical when vulnerabilities cannot be patched. Print devices should not be treated as second-class citizens when it comes to logging and visibility. Network and device-level logs should be forwarded to a centralized SIEM, where anomalous behavior, such as unusually high volumes of print jobs, unexpected restarts, or communication with unfamiliar IP addresses, can trigger alerts and investigations.

These logs also serve as an invaluable resource during incident response, helping to identify the scope and origin of any compromise.

 

Operational Security: Physical and Administrative Safeguards

Operational controls also play a crucial role. Physical access to these devices should be strictly limited, particularly in public or semi-public areas where tampering is a potential concern.

Administrators should also routinely purge stored documents, cached credentials, and other sensitive data from these devices.

Firmware should be kept up to date, even if a patch for the vulnerability in question is not available, as other improvements may close related security gaps.

 

When to Retire: Strategic Risk Management

At a strategic level, organizations must face the question of risk tolerance. In many cases, the best long-term response to an unpatchable vulnerability is to retire and replace the affected device. This is especially true for devices no longer supported by the manufacturer, which are unlikely to receive any future security updates. While budget and operational constraints may limit immediate action, a phased replacement plan tied to lifecycle management can prevent future exposure.

 

Build Awareness: Train Your People

Lastly, communication and training are vital. Users must understand that peripherals, such as printers, are not immune to attack and should be treated as part of the broader security ecosystem. Policies around device usage, data handling, and reporting unusual activity must be reinforced regularly.

 

Final Thoughts: A Layered Defense is the Best Patch

Unpatchable vulnerabilities are not the end of the world, but they are a wake-up call. They challenge us to think beyond patches and adopt a more holistic security model, one that combines visibility, control, and risk-based decision-making. In the face of threats that can’t be fixed with a single update, our best defense is layered, deliberate, and proactive.

 

Take Control Before the Threat Takes Over

Unpatchable doesn’t mean unmanageable, but it does demand a proactive approach. If your organization is struggling with legacy systems, embedded devices, or other unpatchable vulnerabilities, now is the time to act. At MainNerve, we help organizations build resilient, layered defenses tailored to their risk landscape. From network segmentation to custom penetration testing and security strategy, we’ll help you secure what can’t be patched. Contact us today for a free consultation and take the first step toward a stronger, smarter defense.

Latest Posts

A transparent image used for creating empty spaces in columns
“We’re secure because nobody knows about our systems.” “We use non-standard ports so attackers can’t find our services.” “We don’t publish our architecture, so nobody knows how to attack us.” This is security through obscurity; the idea that hiding something makes it secure. And it’s…
A transparent image used for creating empty spaces in columns
 You can’t “fix” web application security and call it done. Security isn’t a project with a start and end date. It’s not something you achieve once and move on from, or a checkbox you mark complete. Web application vulnerabilities aren’t a problem you solve…
A transparent image used for creating empty spaces in columns
Your firewall is important, but it’s just not enough. For years, the security model was simple: build a strong perimeter around your network. Put up a firewall, lock down the border, and keep the bad guys outside. Everything inside the perimeter was trusted, and everything…
A transparent image used for creating empty spaces in columns
Sarah walked into the conference room already skeptical. As CFO of a mid-sized manufacturing company, she’d approved the $6,000 penetration test because the CISO insisted it was necessary for their cyber insurance renewal. Fine. But now she was being pulled into a “findings debrief” that…
A transparent image used for creating empty spaces in columns
Small business cybersecurity advice usually sounds like this: “Implement a comprehensive security program with layered defenses, regular risk assessments, security awareness training, incident response planning, and continuous monitoring.” Great. That’ll take six months, cost $50,000, and require expertise you don’t have. Meanwhile, attackers are targeting…
A transparent image used for creating empty spaces in columns
Most small and medium-sized businesses don’t have a Chief Information Security Officer. They can’t justify the $150K-$250K salary for a full-time security executive when they’re a 10 or 50-person company still figuring out basic growth. But cybersecurity risk doesn’t care about your company’s size. Ransomware…
contact

Our Team

This field is for validation purposes and should be left unchanged.
Name(Required)
On Load
Where? .serviceMM
What? Mega Menu: Services