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.

Vulnerabilities / Threats

11/9/2011
09:23 AM
50%
50%

Why Patches Don't Stop Most Attacks

Verizon's annual breach report shows few attacks exploit patchable vulnerabilities. Do you need to re-evaluate your security policies?

A fundamental component of most, if not all, IT security programs is the timely patching of vulnerabilities in critical systems.

Yet security experts are taking a new look at the strategy as data on breaches continues to show that very few attacks compromise systems using a vulnerability that could have been patched. In 2010, for example, only five vulnerabilities were exploited by attackers in the 381 breaches investigated by Verizon, according to the company's Data Breach Investigations Report (DBIR). Instead, most attackers exploited misconfigurations or gained credentials for otherwise secure systems.

The data suggests the focus of corporate IT on patching could cause managers to miss other important strategies to minimize risk, said Wade Baker, director of risk intelligence for Verizon.

"In general, the security industry is far more vulnerability-minded than we are threat-minded or focused on impact," he said. "Threat, vulnerability, and impact are the components of risk, but most of our time is spent on vulnerabilities."

The data from Verizon's report underscores that patching, while a necessary component of any vulnerability management program, is not sufficient. It's a meme that other security professionals have echoed, as well: Josh Corman, Akamai's director of security intelligence, has cited the research as a reason for companies to consider other strategies to reduce their vulnerabilities to attack and the impact of breaches.

The security experts are, however, not telling businesses to toss out their vulnerability management strategies and patch processes. Companies should just make sure they are balancing their priorities, Baker said. For example, if a company patches its systems once per quarter, then pushing for faster patches is less important that ensuring that patches are applied to all systems.

Read the rest of this article on Dark Reading.
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 8/10/2020
Pen Testers Who Got Arrested Doing Their Jobs Tell All
Kelly Jackson Higgins, Executive Editor at Dark Reading,  8/5/2020
Researcher Finds New Office Macro Attacks for MacOS
Curtis Franklin Jr., Senior Editor at Dark Reading,  8/7/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Special Report: Computing's New Normal, a Dark Reading Perspective
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
The Changing Face of Threat Intelligence
The Changing Face of Threat Intelligence
This special report takes a look at how enterprises are using threat intelligence, as well as emerging best practices for integrating threat intel into security operations and incident response. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-13295
PUBLISHED: 2020-08-10
For GitLab Runner before 13.0.12, 13.1.6, 13.2.3, by replacing dockerd with a malicious server, the Shared Runner is susceptible to SSRF.
CVE-2020-6070
PUBLISHED: 2020-08-10
An exploitable code execution vulnerability exists in the file system checking functionality of fsck.f2fs 1.12.0. A specially crafted f2fs file can cause a logic flaw and out-of-bounds heap operations, resulting in code execution. An attacker can provide a malicious file to trigger this vulnerabilit...
CVE-2020-6145
PUBLISHED: 2020-08-10
An SQL injection vulnerability exists in the frappe.desk.reportview.get functionality of ERPNext 11.1.38. A specially crafted HTTP request can cause an SQL injection. An attacker can make an authenticated HTTP request to trigger this vulnerability.
CVE-2020-8224
PUBLISHED: 2020-08-10
A code injection in Nextcloud Desktop Client 2.6.4 allowed to load arbitrary code when placing a malicious OpenSSL config into a fixed directory.
CVE-2020-8229
PUBLISHED: 2020-08-10
A memory leak in the OCUtil.dll library used by Nextcloud Desktop Client 2.6.4 can lead to a DoS against the host system.