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 Security

4/17/2018
09:35 AM
Joe Stanganelli
Joe Stanganelli
Joe Stanganelli
50%
50%

Endpoint Security: 3 Big Obstacles to Overcome

Two recent reports highlight three major challenges in enterprise endpoint security.

In a report released last month on "next-generation endpoint security," Enterprise Security Group (ESG) analyst Jon Oltsik observed that enterprises and antivirus vendors alike find keeping up with endpoint security difficult because of the sophisticated nature, prolific volume, and exponentiating complexity of attacks.

"40% to 50% of new sophisticated malware attacks could evade endpoint AV, compromise PCs, and act as a beachhead for advanced cyber-attacks," wrote Oltsik. "CISOs realize today that, regardless of the controls they deploy, some malware will sneak through, so they need continuous monitoring and visibility of endpoint behavior."

"Continuous," however, has practical limits.

ESG found that the top endpoint-security challenge -- as indicated by approximately 25% of the 385 cybersecurity professionals surveyed for ESG's report -- was respondents' InfoSec teams taking too long dealing with too many security alerts, many of which are "false alarms." This suggests a -- ahem -- continuous trend.

In a separate ESG study last year, 36% of respondents reported that "keeping up with the volume of security alerts" was their top challenge. Little wonder that enterprise security alerts are commonly treated as so much noise. 31% admitted that their organizations ignore at least 50% of their security alerts; an additional 34% reported that their organizations ignore 26% to 50% of their security alerts.

Endpoint-security obstacle #1: insufficient automation
ESG and other pundits have concluded that proper endpoint-security management demands enhanced automation and machine-learning tools -- with the clearing out of security alerts being but one use case.

In an Industrial Internet Consortium (IIC) whitepaper on best practices in endpoint security, published in March, IIC emphasized automated protocols as a common denominator for both secure endpoint identities and secure attestations. Automation driven by public-key cryptography standards (PKCS), reported IIC, is critical to ensuring safety and certainty in the digital supply chain of certificates, firmware updates, etc. -- helping to keep at bay any malware that might otherwise slip through (sub)standard AV solutions.

Indeed, 17% of ESG study respondents identified their AV software as their top endpoint-security challenge, while 19% pointed to too many manual processes because of their lack of integrated endpoint-security automation. (It should be noted that respondents were allowed to select up to two responses.)

When it comes to malicious bots and the like, some contend that fighting AI with AI can be a losing battle. Consequently, a wholesale ban on non-whitelisted bots can help cut down on endpoint-security alerts and keep them manageable.

Nonetheless, IIC maintains that automated endpoint updates should be reliable without in-house whitelists or blacklists (typically manually input) as a matter of scalability.

"The number of attacks on industrial endpoints has grown rapidly in the last few years and has severe effects," wrote Steve Hanna, co-author of the whitepaper. "Unreliable equipment can cause safety problems, customer dissatisfaction, liability, and reduced profits."

Endpoint-security obstacle #2: legacy devices
Despite these admonitions against equipment unreliability, the authors make allowances for legacy endpoints. Still, they concede (1) that some of the most effective endpoint-security measures are embedded in hardware (typically not an option for legacy devices), and (2) that inadequately secure legacy endpoints must rely on network-security measures.

This latter point rather defeats the purpose of endpoint security. Why struggle against the most modern, most secure endpoints when there are more vulnerable legacy endpoints to be pwned?

To be fair, it is feasible to implement lower levels of trust across legacy endpoints -- but perhaps impractical. Legacy endpoints are maintained for a reason (usually involving cost). Presumably, therefore, these legacy endpoints still need levels of accessibility appropriate for more up-to-date endpoints -- despite the confidentiality and integrity risks.

Endpoint-security obstacle #3: poor security culture
This preference among enterprises -- even among InfoSec workers -- to mortgage endpoint security for agility's sake is further evident in ESG's findings:

  • Respondents' second-biggest endpoint-security challenge (23%) was that regular re-imaging of infected endpoint devices creates more work for respondents' helpdesks and "imped[es] end-user productivity."
  • 17% of respondents also complained that "imped[ed] end-user productivity" caused by endpoint-security agents slowing down endpoint processes was their organization's top endpoint-security challenge.
  • 14%, meanwhile, said that their top endpoint-security woe was lacking the budget for "the right endpoint-security products".

ESG is not alone in making such findings. Verizon Wireless , for instance, recently reported that nearly one third of surveyed mobility professionals admitted that their organizations sacrificed mobile security in favor of business agility -- at significant risk. (See: Verizon Mobility Security Index Shows Enterprises Not Doing Enough.)

More depressingly, in a world where enterprises can be split into the hacked and the unaware of being hacked, a doubtlessly overly optimistic 10% of ESG respondents reported having no endpoint-security challenges whatsoever.

Related posts:

—Joe Stanganelli, principal of Beacon Hill Law, is a Boston-based attorney, corporate-communications and data-privacy consultant, writer, and speaker. Follow him on Twitter at @JoeStanganelli.

Comment  | 
Print  | 
More Insights
Comments
Oldest First  |  Newest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 10/30/2020
'Act of War' Clause Could Nix Cyber Insurance Payouts
Robert Lemos, Contributing Writer,  10/29/2020
6 Ways Passwords Fail Basic Security Tests
Curtis Franklin Jr., Senior Editor at Dark Reading,  10/28/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
How to Measure and Reduce Cybersecurity Risk in Your Organization
In this Tech Digest, we examine the difficult practice of measuring cyber-risk that has long been an elusive target for enterprises. Download it today!
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-15703
PUBLISHED: 2020-10-31
There is no input validation on the Locale property in an apt transaction. An unprivileged user can supply a full path to a writable directory, which lets aptd read a file as root. Having a symlink in place results in an error message if the file exists, and no error otherwise. This way an unprivile...
CVE-2020-5991
PUBLISHED: 2020-10-30
NVIDIA CUDA Toolkit, all versions prior to 11.1.1, contains a vulnerability in the NVJPEG library in which an out-of-bounds read or write operation may lead to code execution, denial of service, or information disclosure.
CVE-2020-15273
PUBLISHED: 2020-10-30
baserCMS before version 4.4.1 is vulnerable to Cross-Site Scripting. The issue affects the following components: Edit feed settings, Edit widget area, Sub site new registration, New category registration. Arbitrary JavaScript may be executed by entering specific characters in the account that can ac...
CVE-2020-15276
PUBLISHED: 2020-10-30
baserCMS before version 4.4.1 is vulnerable to Cross-Site Scripting. Arbitrary JavaScript may be executed by entering a crafted nickname in blog comments. The issue affects the blog comment component. It is fixed in version 4.4.1.
CVE-2020-15277
PUBLISHED: 2020-10-30
baserCMS before version 4.4.1 is affected by Remote Code Execution (RCE). Code may be executed by logging in as a system administrator and uploading an executable script file such as a PHP file. The Edit template component is vulnerable. The issue is fixed in version 4.4.1.