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.

Attacks/Breaches

3/14/2018
03:13 PM
Connect Directly
Twitter
LinkedIn
Google+
RSS
E-Mail
50%
50%

77% of Businesses Lack Proper Incident Response Plans

New research shows security leaders have false confidence in their ability to respond to security incidents.

Your incident response plan probably isn't as strong as you think it is, according to a new pool of research showing a broad gap between the perceived strength of incident response plans and their true effectiveness.

In "The Third Annual Study on the Cyber Resilient Organization," Ponemon researchers surveyed more than 2,848 IT and IT security pros from around the world. They learned businesses continue to struggle to respond to security incidents, primarily because they lack formal incident response plans and sufficient budgets.

Nearly half (48%) of respondents rate their "cyber resilience" as high or very high, an increase from 32% one year prior. Researchers define cyber resilience as "the alignment of prevention, detection and response capabilities to manage, mitigate and move on from cyber attacks."

However, 77% of respondents admit they don't have a formal incident response plan applied consistently across their organization. Nearly half say their plan is informal or nonexistent.

"There's a bit of a discrepancy," says Ted Julian, vice president of product management at IBM Resilient. "Respondents are saying they're feeling more confident about their cyber resilience, yet when you look at the details of the components that would create good cyber resiliency, they didn't score nearly as well."

These components include skilled talent, information governance practices, formal incident response plan across the business, technologies addressing the severity and volume of attacks, sufficient funding, senior management support, and visibility into data and applications.

The top reason cited for improved cyber resiliency was hiring skilled personnel (61%), followed by better information governance (60%), and visibility into data assets and applications (57%).

Yet hiring continues to be an obstacle: the inability to hire and retain skilled personnel was the second-most common barrier to cyber resilience, reported 56% of respondents. Seventy-nine percent said the importance of having skilled security pros in an incident response plan was "high" or "very high," and 77% rated the difficulty in hiring and retaining them as very high.

Part of the reason is incident response experts need a broad range of skills. They have to know a little bit of everything: endpoint, network, operating system, the ins and outs of malware.

"It's notoriously difficult, both to keep these people and to find them," he says. "People with incident response skills are in extremely high demand … it's a diverse, hard-to-find skill set that exacerbates this talent crunch."

The largest barrier to cyber resiliency was lack of investment in new cybersecurity technologies including artificial intelligence and machine learning (60%). Julian explains how tools leveraging AI can help with "alert fatigue" so analysts can focus on more complex tasks. Some key components of incident reponse plans -- checking the EDR platform, deploying URL monitoring -- can all be automated, he says.

Incident Response Isn't One-Size-Fits-All

Some will have an incident response plan that's really thin, and it's hard to say it does anything particularly well, says Julian. Others will try to overcompensate by including every possible scenario in one plan, in which case their strategy is unwieldy.

Different incidents require different responses. What will you do if there's a DDoS attack? A ransomware attack? What happens in the case of a stolen laptop? Creating a separate plan for each distinct type of incident is critical.

You also must factor in everyone involved. A common mistake, especially in organizations with less mature plans, is neglecting to include third parties. If an incident occurs at a company that handles your customers' data, you need a process to respond appropriately.

Julian emphasizes the importance of practicing plans once they've been developed. Fire drills and tabletop exercises, during which team members go through the motions to understand their roles and responsibilities, will prove critical in the chaos following a data breach.

Related Content:

Interop ITX 2018

Join Dark Reading LIVE for two cybersecurity summits at Interop ITX. Learn from the industry’s most knowledgeable IT security experts. Early Bird Rates Expire March 16. Use Promo Code 200KS to Save an Extra $200. Check out the security track here.

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
AI Is Everywhere, but Don't Ignore the Basics
Howie Xu, Vice President of AI and Machine Learning at Zscaler,  9/10/2019
Fed Kaspersky Ban Made Permanent by New Rules
Dark Reading Staff 9/11/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
7 Threats & Disruptive Forces Changing the Face of Cybersecurity
This Dark Reading Tech Digest gives an in-depth look at the biggest emerging threats and disruptive forces that are changing the face of cybersecurity today.
Flash Poll
The State of IT Operations and Cybersecurity Operations
The State of IT Operations and Cybersecurity Operations
Your enterprise's cyber risk may depend upon the relationship between the IT team and the security team. Heres some insight on what's working and what isn't in the data center.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-4147
PUBLISHED: 2019-09-16
IBM Sterling File Gateway 2.2.0.0 through 6.0.1.0 is vulnerable to SQL injection. A remote attacker could send specially-crafted SQL statements, which could allow the attacker to view, add, modify or delete information in the back-end database. IBM X-Force ID: 158413.
CVE-2019-5481
PUBLISHED: 2019-09-16
Double-free vulnerability in the FTP-kerberos code in cURL 7.52.0 to 7.65.3.
CVE-2019-5482
PUBLISHED: 2019-09-16
Heap buffer overflow in the TFTP protocol handler in cURL 7.19.4 to 7.65.3.
CVE-2019-15741
PUBLISHED: 2019-09-16
An issue was discovered in GitLab Omnibus 7.4 through 12.2.1. An unsafe interaction with logrotate could result in a privilege escalation
CVE-2019-16370
PUBLISHED: 2019-09-16
The PGP signing plugin in Gradle before 6.0 relies on the SHA-1 algorithm, which might allow an attacker to replace an artifact with a different one that has the same SHA-1 message digest, a related issue to CVE-2005-4900.