Endpoint

10/25/2017
10:50 AM
50%
50%

Productivity, Operations Hardest-Hit by Endpoint Attacks

Operational outcomes from infected endpoints are more common than data loss or financial effects, researchers found.

Endpoint infections are more likely to affect operational outcomes than data loss or finances, researchers report. Nearly one-third of IT and security pros say interruptions to standard business processes are the biggest effect on compromised endpoints, followed by impeding the productivity of knowledge workers (31%) and delays to other IT projects (28%).

In a new Enterprise Strategy Group (ESG) study titled "Top-of-mind Threats and Their Impact on Endpoint Security Decisions," researchers polled 300 IT and security professionals from the US (43%), Japan (21%), UK (13%), France (12%), and Germany (11%) to learn about the endpoint security threats keeping them on their toes.

Cybercriminals, phishing, and unknown malware are top security concerns. Ninety percent of respondents state they are "very concerned" or "concerned" about cybercriminals, 82% are worried about nation-state cyberespionage, 79% fear hacktivists, and 78% worry about insiders.

Email phishing attacks with a malicious attachment (55%) or link to malicious website (54%) are the most commonly used attack vectors against organizations in the past two years. Known malware is a problem, according to 35% of participants, but unknown malware is more concerning. Nearly 30% say unknown malware is the top attack form, and 44% report it's the greatest risk to their organization's endpoints, according to the report, which was commissioned by Cylance.

Read more details here.

Join Dark Reading LIVE for two days of practical cyber defense discussions. Learn from the industry’s most knowledgeable IT security experts. Check out the INsecurity agenda here.

Dark Reading's Quick Hits delivers a brief synopsis and summary of the significance of breaking news events. For more information from the original source of the news item, please follow the link provided in this article. View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
White House Cybersecurity Strategy at a Crossroads
Kelly Jackson Higgins, Executive Editor at Dark Reading,  7/17/2018
Lessons from My Strange Journey into InfoSec
Lysa Myers, Security Researcher, ESET,  7/12/2018
What's Cooking With Caleb Sima
Kelly Jackson Higgins, Executive Editor at Dark Reading,  7/12/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-14339
PUBLISHED: 2018-07-19
In Wireshark 2.6.0 to 2.6.1, 2.4.0 to 2.4.7, and 2.2.0 to 2.2.15, the MMSE dissector could go into an infinite loop. This was addressed in epan/proto.c by adding offset and length validation.
CVE-2018-14340
PUBLISHED: 2018-07-19
In Wireshark 2.6.0 to 2.6.1, 2.4.0 to 2.4.7, and 2.2.0 to 2.2.15, dissectors that support zlib decompression could crash. This was addressed in epan/tvbuff_zlib.c by rejecting negative lengths to avoid a buffer over-read.
CVE-2018-14341
PUBLISHED: 2018-07-19
In Wireshark 2.6.0 to 2.6.1, 2.4.0 to 2.4.7, and 2.2.0 to 2.2.15, the DICOM dissector could go into a large or infinite loop. This was addressed in epan/dissectors/packet-dcm.c by preventing an offset overflow.
CVE-2018-14342
PUBLISHED: 2018-07-19
In Wireshark 2.6.0 to 2.6.1, 2.4.0 to 2.4.7, and 2.2.0 to 2.2.15, the BGP protocol dissector could go into a large loop. This was addressed in epan/dissectors/packet-bgp.c by validating Path Attribute lengths.
CVE-2018-14343
PUBLISHED: 2018-07-19
In Wireshark 2.6.0 to 2.6.1, 2.4.0 to 2.4.7, and 2.2.0 to 2.2.15, the ASN.1 BER dissector could crash. This was addressed in epan/dissectors/packet-ber.c by ensuring that length values do not exceed the maximum signed integer.