Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Risk

How To Handle Patch Overload

Tips for preparing for and applying patches that come in big batches -- like Microsoft's February release

Special to Dark Reading

There are Patch Tuesdays, and then there are mega-Patch Tuesdays like this month's, when Microsoft released a record-tying number of 13 security bulletins fixing 26 vulnerabilities. Handling this heavy load of patches -- many of them requiring system shutdowns and reboots -- with minimal disruption to business and the rare risk of the patches themselves causing problems is no easy feat.

Much of it depends on how well-prepared your business is for handling the lighter, more typical patch releases. Those releases can help prepare you for the "big one," like February's cycle.

Prep work for any Patch Tuesday cycle should include careful review of the Microsoft material that precedes patch releases, says Jason Miller, security and data team manager at Shavlik Technologies.

"Researching each bulletin is key. Microsoft issues advanced notification every Thursday before Patch Tuesday," he says. "The information can give administrators an idea of what is coming, and how it will affect their business. Reviewing this information can save time and allow for planning. In addition, Microsoft has been supplying more relevant information on these notifications that aid in this effort."

And when the release is a whopper like this month's?

"Large patch days require additional resources, but the same techniques used for light days are applicable," Wolfgang Kandek, CTO of Qualys.

These resources -- available IT personnel, test platforms that match company configurations for ensuring the patch won't cause more problems than it solves, and firm understanding and coordination of the effect of reboots on business and operations -- can themselves be configured in ways that make mammoth patch releases more manageable.

This largely depends on a company's existing patch strategy. Automated patching and reporting can ease some of the burden, Miller says. "Patch maintenance windows may expand, though, as companies deal with troubleshooting any patch that may have failed to deploy or caused issues with systems and business applications," he says. "Some patch strategies require each patch to be tested against machines that have business applications. This ensures the patches will not cause widespread issues that can cripple a business. With large releases, there are delays in patching because the testing takes more time."

As with trimming patch deployment time and other strategies for increasing the efficiency and safety of patch deployments, the key is to have a solid, thorough understanding of all of affected systems and operations, deploying and installing the patches in stages that match the specific needs and peculiarities of those configurations.

Previous
1 of 2
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
News
Inside the Ransomware Campaigns Targeting Exchange Servers
Kelly Sheridan, Staff Editor, Dark Reading,  4/2/2021
Commentary
Beyond MITRE ATT&CK: The Case for a New Cyber Kill Chain
Rik Turner, Principal Analyst, Infrastructure Solutions, Omdia,  3/30/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-29370
PUBLISHED: 2021-04-13
A UXSS was discovered in the Thanos-Soft Cheetah Browser in Android 1.2.0 due to the inadequate filter of the intent scheme. This resulted in Cross-site scripting on the cheetah browser in any website.
CVE-2021-3460
PUBLISHED: 2021-04-13
The Motorola MH702x devices, prior to version 2.0.0.301, do not properly verify the server certificate during communication with the support server which could lead to the communication channel being accessible by an attacker.
CVE-2021-3462
PUBLISHED: 2021-04-13
A privilege escalation vulnerability in Lenovo Power Management Driver for Windows 10, prior to version 1.67.17.54, that could allow unauthorized access to the driver's device object.
CVE-2021-3463
PUBLISHED: 2021-04-13
A null pointer dereference vulnerability in Lenovo Power Management Driver for Windows 10, prior to version 1.67.17.54, that could cause systems to experience a blue screen error.
CVE-2021-3471
PUBLISHED: 2021-04-13
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Notes: none.