A laptop has been asking to restart all week.
The billing server hasn’t been rebooted in months.
The practice-management application is still on an old version because “the vendor says don’t update.”
Meanwhile, attackers are looking for software weaknesses they already know how to exploit.
Verizon’s 2026 Data Breach Investigations Report found vulnerability exploitation was the most common initial access vector, involved in 31% of breaches. The report’s remediation findings are a warning too: median time to patch rose from 32 days to 43 days, and organizations fully remediated only 26% of CISA Known Exploited Vulnerabilities (KEVs) in 2025.
That 43 days is a median, not a timer running on every small firm. But the message is clear: gaps between a fix becoming available and that fix being installed can give attackers time to act.
“We Click Update When It Pops Up” Isn’t a Patch Program
“It’s been asking me to restart for a week,” the receptionist says.
The office manager adds, “We’ll do it after month-end.”
And the practice-management app? “The vendor says don’t update.”
These are understandable decisions when your staff is busy and downtime is costly. But an update prompt is only one visible piece of the problem. It won’t necessarily appear for every device or application that needs attention.
Consider what might be missing from your patch routine: firmware for the firewall and Wi-Fi access points, the network-attached storage (NAS), copier, phone system, document management server, VPN appliance, browser extensions, and third-party PDF or medical imaging software. Each has its own vendor, update process, and maintenance requirements.

If nobody owns the inventory, some systems simply don’t get checked. That’s why IT asset management matters: you need to know what technology you have before you can know whether it is patched, supported, and still appropriate for your business.
A vendor warning against an update deserves attention, not an indefinite pass. Ask for the compatibility concern in writing, confirm what release the vendor supports, document any temporary risk-reduction steps, and set a date to revisit the decision. “Don’t update” should have an owner and an end date.
Attackers Don’t Need a Zero-Day
A newly discovered flaw with no available fix is called a zero-day. It gets headlines. But attackers don’t always need one.
Once a software vendor releases a security patch, the weakness it fixes may become easier to identify. Attackers can look for systems that still have the old version. In plain terms: the repair is available, but your unpatched device may still have the open door.
That gap is the defender window. The time between a vulnerability becoming known or fixable and your firm actually reducing the risk. It is not just about installing updates on laptops. It is about finding affected systems, deciding how urgent the issue is, applying the fix safely, and confirming it worked.
The urgency is not theoretical. As of mid-November 2026, CISA’s free, public Known Exploited Vulnerabilities catalog held about 1,781 entries. Some recent entries had remediation due dates only days after being added; for example, vulnerabilities added November 13 showed due dates of November 16. Those deadlines apply to federal agencies under government directives, not automatically to every private firm. But the catalog is a valuable signal: these vulnerabilities are known to be exploited in the wild.
The monthly volume can be substantial too. Tenable reported that Microsoft’s November 2026 Patch Tuesday addressed 1,093 CVEs. That does not mean your firm has 1,093 urgent tasks. It means updates need a consistent process to identify which fixes affect your systems and prioritize the ones that matter most.
What the Rules Say About Vulnerability Assessment
For certain covered financial institutions, the FTC Safeguards Rule calls for regular monitoring and testing of information-security safeguards. Under 16 CFR 314.4(d), if you do not have effective continuous monitoring or another system that detects vulnerability-creating changes on an ongoing basis, you must conduct annual penetration testing and vulnerability assessments at least every six months. The rule also addresses assessments when material changes occur and in other circumstances that may materially affect your information-security program. Separately, § 314.4(c)(7) requires procedures for change management.
For medical practices and other covered entities or business associates, the HIPAA Security Rule includes a required risk analysis and periodic evaluation, along with addressable procedures to guard against, detect, and report malicious software. See 45 CFR 164.308(a)(1)(ii)(A), (a)(5)(ii)(B), and (a)(8). HIPAA does not set one universal patching interval for every organization. Your approach should be informed by the risks to electronic protected health information and your environment.
For law firms, ABA Formal Opinion 477R discusses lawyers’ reasonable efforts to protect client information in electronic communications. It does not prescribe a patch schedule, but it underscores the need to take appropriate steps to protect confidential information.
This is general information, not legal advice. Your obligations depend on your organization, operations, and applicable rules. Consult qualified legal or compliance professionals about HIPAA compliance, FTC Safeguards, GLBA compliance, and other requirements.
Prioritize Like a Business Owner, Not a Scanner
A vulnerability scanner can produce a long list. It can’t make your business decisions for you. Start with practical risk:
- Known exploited vulnerabilities first. Check CISA’s KEV catalog and determine whether the affected product is in your environment.
- Internet-facing systems next. Prioritize devices and services reachable from outside your organization, such as VPN appliances and exposed servers.
- Systems holding sensitive data. Focus on devices and applications storing or connecting to client, patient, or financial information.
- Everything else on a planned schedule. Risk still matters, but not every routine update is an emergency.
Then keep the work moving with a calendar. Patching is a routine operating process, not a heroic weekend project after an alarming headline. Like preventive care, regular checks can help you spot problems before they turn into urgent, disruptive events.
Five Habits That Make Patching Manageable
- Name an owner and set a schedule. Someone must be accountable for reviewing updates across endpoints, servers, applications, and network equipment. They need a reliable inventory to work from.
- Give staff a heads-up about maintenance windows. Tell people when devices may restart, how long the work may take, and what to do if they are working remotely. Good business IT support should help set expectations, not surprise the team.
- Set a clear reboot expectation. Updates may not finish until a device restarts. “I’ll do it later” can quietly become weeks. Agree on a reasonable deadline and make it easy for staff to save work first.
- Deploy in stages. Test updates on a small group or test system before rolling them out to everyone. This “ring” approach can catch a compatibility issue without taking the whole firm offline.
- Track exceptions, including an end date. Record the affected device or application, why the update is deferred, who owns the decision, what risk-reducing steps are in place, and when it will be reviewed. Watch out for the “defer for 30 days” setting that gets renewed until it becomes forever.

If a vendor requires a delay, keep the decision visible and revisit it. If a patch causes a problem, document the impact and adjust the rollout. The aim is controlled change, not updates at any cost, and not permanent postponement.
What Evidence Should You Ask For?
An IT audit or IT assessment should be able to give you more than “everything looks fine.” Ask for a monthly patch-status report showing:
- The percentage of managed devices that are current.
- Known-missing patches, with an owner and target date for each.
- The dates of the latest firmware checks for firewalls, access points, and other network equipment.
- The date and scope of the latest vulnerability assessment.
- Any approved exceptions and when they are due for review.
These records can help you understand progress and identify issues before they become emergencies. They may also help when insurers, auditors, or regulators ask how your firm tracks updates and assesses vulnerabilities. Your reporting should reflect what was checked, what remains open, and what decision was made, not just what a dashboard happens to count.
Managing Patches In-House vs. With a Provider
Handling updates internally can work if you have the time, tools, inventory, and coverage. A knowledgeable generalist may understand your systems and know which applications are sensitive to change.
The trade-offs are real: one person may have limited visibility after hours, no separate test ring, and no coverage during a vacation. Update work can also compete with helpdesk requests and daily operations. Training staff and maintaining dedicated tools take time and budget.
A managed services provider can bring automation, defined deployment routines, network support, and documented reporting. For a small law firm, medical practice, or accounting firm, outsourced IT can provide access to a broader process and economies of scale without hiring a full internal team. A provider can also align patching with endpoint security, ransomware protection, cloud services, and your wider cybersecurity program.
But a provider does not remove the need for a maintenance window, business sign-off, or clear ownership of exceptions. Your staff still needs to know when work is planned, and your leadership still needs to make decisions about business impact. Managed services should make that process clearer, not invisible.
Patching is one part of a broader security posture, alongside other controls such as privileged access. If that topic is also on your list, see our related article on standing privileged access in law firms, medical practices, and accounting firms.

Questions for Whoever Runs Your IT
Take this checklist to your internal team or provider:
- Do we have a current inventory of endpoints, servers, applications, and network equipment?
- Who owns patching, and what is the regular schedule?
- How do you identify vulnerabilities listed in CISA’s KEV catalog?
- How do you prioritize internet-facing systems and systems holding sensitive data?
- How are updates tested and deployed in stages?
- What is our process for reboots and staff communication?
- Which updates are deferred, who approved each deferral, and when does it expire?
- When was our last vulnerability assessment, and can we review the findings and remediation status?
Final Word
The goal is not to eliminate every update prompt by Friday. It is to establish a predictable rhythm: know what you own, prioritize the real risks, apply updates safely, and document what remains open.
If your firm can’t answer who owns patching, when firmware was last checked, or how old its vulnerability assessment is, start with a clear baseline. A PC of Mind provides IT services and cybersecurity services for professional firms. Contact our team to discuss a practical IT assessment and a patch-management process built around your operations.