Endpoint

10/24/2016
09:05 AM
Connect Directly
Twitter
LinkedIn
Google+
RSS
E-Mail
50%
50%

Microsoft's New Patch Tuesday Model Comes With Benefits And Risks

Microsoft has transitioned its Patch Tuesday update process to a cumulative rollup model. What businesses need to know about the new patching regimen.

Microsoft as of this month officially transitioned its Patch Tuesday model to a cumulative patching process for Windows 7 and Windows 8.1 that security experts say is a more flexible and streamlined way to update vulnerable systems. But it also comes with some risks.

October 11 marked the first time Microsoft released updates via its new system, which combines security and non-security fixes into large bundles. Three distinct update bundles will roll out each month; two available to enterprise customers, and one for consumers.

On the second Tuesday of each month, otherwise known as Patch Tuesday, Microsoft will distribute two update batches.

One of these, for businesses and consumers, is released via Windows Update, Windows Server Update Services (WSUS), and the Windows Update Catalog. This is a monthly rollup of security and non-security fixes, which contains all updates for the month as well as fixes for the previous months. If a user skips a month, they will receive the patches for that month in the following month's bundle.

The second bundle contains all security patches for the specific month and excludes fixes from previous months. These security-only rollouts, intended for enterprise users, are distributed through WSUS and Windows Update Catalog.

"What Microsoft is trying to do is make things simpler for users by delivering all updates together," explains Amol Sarwate, director of vulnerability labs at Qualys. "When administrators install patches, they can just deploy one patch." This model also makes it easier to learn which fixes are included and which aren't, he adds.

On the third Tuesday, Microsoft will release a preview of non-security updates slated to arrive in the following month's rollup. This allows businesses to test updates on their systems and verify compatibility.

Sarwate explains how this new strategy is intended to streamline the update process for enterprise customers and give them the option to choose specific bundles. He advises organizations to take advantage of the opportunity to test new updates ahead of their release.

Microsoft's new update model also addresses problems businesses previously encountered when applying new security fixes.

"The main issue in the past has been that some users, mostly by mistake, didn't install all patches," explains Johannes Ullrich, dean of research at SANS Technology Institute. "This led to a very fragmented user base and increased the risk of new patches, as you couldn't be sure that all old patches were applied correctly."

Business systems are more tightly managed, he continues, and decisions are more carefully made as part of a controlled patch process. Organizations can delay patches for a particular month if they conflict with business-critical apps.

The Tradeoffs

While the change is intended to make patching simpler for enterprise users, experts agree there is still risk involved. 

"As someone who manages patching, I welcome the change," says Michael Gray, VP of tech at Thrive Networks. "The time spent researching every patch is exhaustive."

However, he continues, there is a risk of people not wanting to download these monolithic updates. What's more, the larger these bundles get, the more likely it is someone could compromise the entire package.

Ullrich acknowledges the new model will make patch application easier, but there is also risk related to availability.

"If a particular patch interferes with a particular function of the PC, either a hardware component or customer software, then the entire patch has to be delayed and it will not be advisable to just apply a partial patch," he explains. 

This further emphasizes the importance of patch testing, which may be a bit easier on the new system since there will be less variability, he continues. However, it remains to be seen how this will work out in the first few months of Microsoft's new model.

As IT managers begin to roll out these changes, they should keep standard patching best practices in mind, says Sarwate. He recommends deploying updates in waves, so if there's a need to roll back, it's only necessary for a small group of workers.

Ullrich advises corporations to apply patches as soon as Microsoft releases them. Home users should still automatically apply patches.

Related Content:

Kelly Sheridan is the Staff Editor at Dark Reading, where she focuses on cybersecurity news and analysis. She is a business technology journalist who previously reported for InformationWeek, where she covered Microsoft, and Insurance & Technology, where she covered financial ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Joe Stanganelli
50%
50%
Joe Stanganelli,
User Rank: Ninja
10/31/2016 | 5:51:48 AM
Patch Watching
The worst is downloading and installing a bunch of patches, and then finding out that one has screwed up your system -- and you have to figure out which one.

The sad thing is that "recommended" self-serving vendor patches (as opposed to genuine security updates) have made people distrustful of the entire model -- leading to people not installing important security updates and bad patch-management processes.

Incidentally, Susan Bradley keeps a neat blog on Windows updates -- and what they could do to your systems -- here: windowssecrets.com/category/patch-watch/
Crowdsourced vs. Traditional Pen Testing
Alex Haynes, Chief Information Security Officer, CDL,  3/19/2019
BEC Scammer Pleads Guilty
Dark Reading Staff 3/20/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Well, at least it isn't Mobby Dick!
Current Issue
5 Emerging Cyber Threats to Watch for in 2019
Online attackers are constantly developing new, innovative ways to break into the enterprise. This Dark Reading Tech Digest gives an in-depth look at five emerging attack trends and exploits your security team should look out for, along with helpful recommendations on how you can prevent your organization from falling victim.
Flash Poll
The State of Cyber Security Incident Response
The State of Cyber Security Incident Response
Organizations are responding to new threats with new processes for detecting and mitigating them. Here's a look at how the discipline of incident response is evolving.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2016-10743
PUBLISHED: 2019-03-23
hostapd before 2.6 does not prevent use of the low-quality PRNG that is reached by an os_random() function call.
CVE-2019-9947
PUBLISHED: 2019-03-23
An issue was discovered in urllib2 in Python 2.x through 2.7.16 and urllib in Python 3.x through 3.7.2. CRLF injection is possible if the attacker controls a url parameter, as demonstrated by the first argument to urllib.request.urlopen with \r\n (specifically in the query string or PATH_INFO) follo...
CVE-2019-9948
PUBLISHED: 2019-03-23
urllib in Python 2.x through 2.7.16 supports the local_file: scheme, which makes it easier for remote attackers to bypass protection mechanisms that blacklist file: URIs, as demonstrated by triggering a urllib.urlopen('local_file:///etc/passwd') call.
CVE-2019-9945
PUBLISHED: 2019-03-23
SoftNAS Cloud 4.2.0 and 4.2.1 allows remote command execution. The NGINX default configuration file has a check to verify the status of a user cookie. If not set, a user is redirected to the login page. An arbitrary value can be provided for this cookie to access the web interface without valid user...
CVE-2019-9942
PUBLISHED: 2019-03-23
A sandbox information disclosure exists in Twig before 1.38.0 and 2.x before 2.7.0 because, under some circumstances, it is possible to call the __toString() method on an object even if not allowed by the security policy in place.