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.

Application Security

5/4/2020
09:00 AM
Kelly Sheridan
Kelly Sheridan
Slideshows
Connect Directly
Twitter
LinkedIn
RSS
E-Mail
50%
50%

7 Tips for Security Pros Patching in a Pandemic

The shift to remote work has worsened patch management challenges and created new ones. Security pros share insights and best practices.
Previous
1 of 8
Next

Patch management has historically been a challenge for IT and security teams, which are under pressure to create strong programs and deploy fixes as they're released. Now their challenges are intensified as a global shift to remote work forces companies to rethink patching strategies.

"It's a massive challenge all of a sudden," says Stephen Boyer, co-founder and CTO at BitSight. Businesses accustomed to protecting 2,000 employees across three to four offices now have to secure the same workers in 2,000 home offices. People are working on personal devices, with home routers they don't properly configure, on networks the corporation cannot manage.

Data shows home networks pose a higher security risk than enterprise networks, he continues. BitSight research shows 45% of remote office networks have observed malware, compared with 13% of corporate networks. And more industries are enforcing work-from-home policies: 84% of traffic in the US education sector shifted off-network during the fourth week of March, data shows, along with 63% of government/policies sector traffic and 35% of finance sector traffic.

"People are working on networks that aren't managed and controlled by the corporation anymore," Boyer explains. Those who do have corporate devices use them in workspaces that are "drastically different" than the environments inside a corporation. The change has been a jolt to IT and security teams, which didn't expect this level of remote work for several years and now face unprecedented challenges in buying, configuring, deploying, and patching machines.

The process of buying assets is typically a long one that is researched, vetted, planned, and executed, says Richard Melick, senior technical product manager at Automox. Laptops and desktops would arrive, and then be configured and deployed. "We skip all that now," he says. "Now it's, 'Get them a laptop so they can get back to work.'" This need to continue working remotely has created a technologically diverse environment that most IT and security pros are not used to, and the need for different configurations on different endpoints puts new pressure on teams.

"You don't necessarily have as much control as you used to," says Jon Clay, director of global threat communications at Trend Micro. The proliferation of devices across thousands of home offices has exacerbated existing patch management challenges and created new ones. Some traditional patching advice still applies in these times, and some tips are even more important.

Here, experts in vulnerability and patch management share their advice for IT and security pros struggling to patch properly throughout the pandemic. Read on to learn their tips, and feel free to share your own in the Comments section.

 

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
 

Recommended Reading:

Previous
1 of 8
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
More SolarWinds Attack Details Emerge
Kelly Jackson Higgins, Executive Editor at Dark Reading,  1/12/2021
Vulnerability Management Has a Data Problem
Tal Morgenstern, Co-Founder & Chief Product Officer, Vulcan Cyber,  1/14/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
2020: The Year in Security
Download this Tech Digest for a look at the biggest security stories that - so far - have shaped a very strange and stressful year.
Flash Poll
Assessing Cybersecurity Risk in Today's Enterprises
Assessing Cybersecurity Risk in Today's Enterprises
COVID-19 has created a new IT paradigm in the enterprise -- and a new level of cybersecurity risk. This report offers a look at how enterprises are assessing and managing cyber-risk under the new normal.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-36192
PUBLISHED: 2021-01-18
An issue was discovered in the Source Integration plugin before 2.4.1 for MantisBT. An attacker can gain access to the Summary field of private Issues (either marked as Private, or part of a private Project), if they are attached to an existing Changeset. The information is visible on the view.php p...
CVE-2020-36193
PUBLISHED: 2021-01-18
Tar.php in Archive_Tar through 1.4.11 allows write operations with Directory Traversal due to inadequate checking of symbolic links, a related issue to CVE-2020-28948.
CVE-2020-7343
PUBLISHED: 2021-01-18
Missing Authorization vulnerability in McAfee Agent (MA) for Windows prior to 5.7.1 allows local users to block McAfee product updates by manipulating a directory used by MA for temporary files. The product would continue to function with out-of-date detection files.
CVE-2020-28476
PUBLISHED: 2021-01-18
All versions of package tornado are vulnerable to Web Cache Poisoning by using a vector called parameter cloaking. When the attacker can separate query parameters using a semicolon (;), they can cause a difference in the interpretation of the request between the proxy (running with default configura...
CVE-2020-28473
PUBLISHED: 2021-01-18
The package bottle from 0 and before 0.12.19 are vulnerable to Web Cache Poisoning by using a vector called parameter cloaking. When the attacker can separate query parameters using a semicolon (;), they can cause a difference in the interpretation of the request between the proxy (running with defa...