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.

Endpoint

5/31/2017
11:41 AM
Connect Directly
Twitter
LinkedIn
Google+
RSS
E-Mail
50%
50%

The Cons of a 'Silver Bullet' Approach to Endpoint Defense

Companies relying on individual security solutions won't find one is a 'silver bullet' that will provide seamless protection.

Endpoint tools often promise to be a "silver bullet" to tackle all security problems. The problem is, no single product will fix everything, and businesses are left to juggle several tools that don't work together.

"In the last 10 years, the industry is following a destructive path of 'new threat, new widget, new threat, new widget,'" says Brian Dye, McAfee's EVP of corporate products. Over time, he explains, companies amass a collection of individual security products that don't integrate and consequently spend more time on administration than on security.

McAfee is doubling down on endpoint strategy as it transitions back to a standalone business following its spinoff from Intel earlier this year. Dye says the focus is less on first-gen and next-gen point products, and more on how to build an architecture that adapts to changing threats.

Many businesses market their products in line with industry news, says Dye. Amid the fallout of WannaCry, for example, there was a rise in products promising defense against ransomware.

"Each wave of technology promises to be the answer to world hunger," he continues. "The bad guys always find a way around it." Next-gen products promise to fix security problems but don't integrate with the broader security framework, he explains.

The effectiveness of threat defense is one of the key challenges facing businesses this year, McAfee found in its 2017 Threats Predictions report. New techniques gain value throughout deployment and improve as they face real-life scenarios. The upward trend continues until the defense becomes so effective it motivates adversaries to respond.

"At this stage, attackers experiment and discover ways to evade this type of defense and develop countermeasures to reduce its value," the report states.

Different technologies perform different functions in the process of protection, detection, and correction, says Dye. Machine learning, antivirus, intrusion prevention, and enterprise detection and response (EDR) are all examples of technologies that work better together than alone.

"To make endpoint work, you need a platform," says Dye. "It needs to combine the strengths of many different technologies so you account for the weaknesses of those technologies."

When an attacker runs malware, for example, individual tools for machine learning and EDR can try to decide whether the threat is real. On their own, each might indicate "it might be a threat" and security teams may not respond. However, if the tools collaborated and all detected a potential threat, a team would be more likely to investigate and avoid a false positive.

"There's a core tradeoff in how effective security is, and how much risk you put to the user in terms of false positives," says Dye. "The key is to have the ability to stop the bad things and not stop the good things."

Large enterprises have an advantage in building this type of flexible platform, which Dye calls the "dynamic endpoint," because they have dedicated teams and the bandwidth to try new technologies that will give them a more well-rounded defense. Small and midsize businesses don't have the luxury of being able to test every vendor claim, he notes.

Dye cautions security teams about the danger of continuing the "silver bullet" approach to security instead of the flexible architecture approach.

"The danger is … you'll stay on the hamster wheel," he explains. "You'll purchase and deploy a solution with the strength of one technology, and you'll end up having to deploy another one in another year. You'll spend all your time on admin and suck resources away from what you're supposed to be doing."

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
Why Cyber-Risk Is a C-Suite Issue
Marc Wilczek, Digital Strategist & CIO Advisor,  11/12/2019
DevSecOps: The Answer to the Cloud Security Skills Gap
Lamont Orange, Chief Information Security Officer at Netskope,  11/15/2019
Attackers' Costs Increasing as Businesses Focus on Security
Robert Lemos, Contributing Writer,  11/15/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Navigating the Deluge of Security Data
In this Tech Digest, Dark Reading shares the experiences of some top security practitioners as they navigate volumes of security data. We examine some examples of how enterprises can cull this data to find the clues they need.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-19071
PUBLISHED: 2019-11-18
A memory leak in the rsi_send_beacon() function in drivers/net/wireless/rsi/rsi_91x_mgmt.c in the Linux kernel through 5.3.11 allows attackers to cause a denial of service (memory consumption) by triggering rsi_prepare_beacon() failures, aka CID-d563131ef23c.
CVE-2019-19072
PUBLISHED: 2019-11-18
A memory leak in the predicate_parse() function in kernel/trace/trace_events_filter.c in the Linux kernel through 5.3.11 allows attackers to cause a denial of service (memory consumption), aka CID-96c5c6e6a5b6.
CVE-2019-19073
PUBLISHED: 2019-11-18
Memory leaks in drivers/net/wireless/ath/ath9k/htc_hst.c in the Linux kernel through 5.3.11 allow attackers to cause a denial of service (memory consumption) by triggering wait_for_completion_timeout() failures. This affects the htc_config_pipe_credits() function, the htc_setup_complete() function, ...
CVE-2019-19074
PUBLISHED: 2019-11-18
A memory leak in the ath9k_wmi_cmd() function in drivers/net/wireless/ath/ath9k/wmi.c in the Linux kernel through 5.3.11 allows attackers to cause a denial of service (memory consumption), aka CID-728c1e2a05e4.
CVE-2019-19075
PUBLISHED: 2019-11-18
A memory leak in the ca8210_probe() function in drivers/net/ieee802154/ca8210.c in the Linux kernel before 5.3.8 allows attackers to cause a denial of service (memory consumption) by triggering ca8210_get_platform_data() failures, aka CID-6402939ec86e.