Risk

11/14/2018
11:15 AM
50%
50%

Can Businesses Stand Up to Cybercrime? Only 61% Say Yes

While 96% of US organizations say business resilience should be core to company strategy, only 61% say it actually is.

New data points to a gap between how businesses value resilience and how they implement it, Tanium researchers report.

As part of The Resilience Gap study, Tanium polled 1,000 US business decision makers to learn more about their ability to defend against cybercrime. Nearly all (96%) believe making technology resilient to business disruptions should be core to their broader strategy. However, only 61% report that resiliency is actually in place.

There remain several barriers to achieving business resilience, researchers found, specifically between internal organizational structures and access to technology and talent. More than one-third (36%) say growing complexity is to blame; 20% blame siloed business divisions. One-third say the problem is with hackers becoming more sophisticated than internal IT teams, and 17% claim their company doesn't have the right skills to accurately detect breaches in real time.

Companies need to assign responsibility for business resilience, report researchers, who explain that one of the reasons it remains unachievable is because of growing internal confusion on where the responsibility lies. But who should handle it? Some respondents say the CIO or head of IT should take charge, 33% say all employees should be responsible, and 10% say the CEO.

Poor business resilience comes with financial consequences. Thirty-two percent say they could not — or don't know if they could — calculate the impact of a breach when considering lost revenue and productivity. Eleven percent report they don't know if they could calculate response cost; 10% don't know if they could calculate the impact of lost or exposed data.

Read more details here.

 

Black Hat Europe returns to London Dec. 3-6, 2018, with hands-on technical Trainings, cutting-edge Briefings, Arsenal open-source tool demonstrations, top-tier security solutions, and service providers in the Business Hall. Click for information on the conference and to register.

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
'PowerSnitch' Hacks Androids via Power Banks
Kelly Jackson Higgins, Executive Editor at Dark Reading,  12/8/2018
How Well Is Your Organization Investing Its Cybersecurity Dollars?
Jack Jones, Chairman, FAIR Institute,  12/11/2018
Starwood Breach Reaction Focuses on 4-Year Dwell
Curtis Franklin Jr., Senior Editor at Dark Reading,  12/5/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
10 Best Practices That Could Reshape Your IT Security Department
This Dark Reading Tech Digest, explores ten best practices that could reshape IT security departments.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-15328
PUBLISHED: 2018-12-12
On BIG-IP 14.0.x, 13.x, 12.x, and 11.x, Enterprise Manager 3.1.1, BIG-IQ 6.x, 5.x, and 4.x, and iWorkflow 2.x, the passphrases for SNMPv3 users and trap destinations that are used for authentication and privacy are not handled by the BIG-IP system Secure Vault feature; they are written in the clear ...
CVE-2018-17949
PUBLISHED: 2018-12-12
Cross site scripting vulnerability in iManager prior to 3.1 SP2.
CVE-2018-17950
PUBLISHED: 2018-12-12
Incorrect enforcement of authorization checks in eDirectory prior to 9.1 SP2
CVE-2018-17952
PUBLISHED: 2018-12-12
Cross site scripting vulnerability in eDirectory prior to 9.1 SP2
CVE-2018-16867
PUBLISHED: 2018-12-12
A flaw was found in qemu Media Transfer Protocol (MTP) before version 3.1.0. A path traversal in the in usb_mtp_write_data function in hw/usb/dev-mtp.c due to an improper filename sanitization. When the guest device is mounted in read-write mode, this allows to read/write arbitrary files which may l...