Attacks/Breaches

5/31/2017
12:00 AM
Dark Reading
Dark Reading
Products and Releases
50%
50%

Security Teams Overwhelmed by Rising Volume of Attacks

New Research Finds "Time Sink" Security Investigation Threatens Effective Security Operations

SAN FRANCISCO – Splunk, provider of the leading software platform for real-time Operational Intelligence, today announced the results of new research from IDC that shows organizations are constantly under attack and struggling to keep up. The research finds most organizations run time-consuming security investigations and often fail to effectively protect themselves. Read the full IDC InfoBrief, "Investigation or Exasperation? The State of Security Operations," sponsored by Splunk.

Findings from a survey of 600 senior security professionals across the U.S. and Europe highlight that less than half (47 percent) of security teams gather enough information about those incidents to enable appropriate or decisive action. Firms experience an average of 40 actionable incidents per week, but only a quarter (27 percent) think they are coping comfortably with this workload, and a third (33 percent) describe themselves as “struggling” or “constantly firefighting.” More than half (53 percent) of respondents claimed the biggest limitation to improving security capabilities was that resources are too busy on routine operations and incident investigation.

"The amount of time companies are spending on analyzing and assessing incidents is a huge problem," said Duncan Brown, associate vice president, security practice, IDC. "The highest-paid, most skilled staff are being tied up, impacting the cost and efficiency of security operations. This is exacerbated when considered alongside the security skills shortage, which has most impact in high-value areas like incident investigation and response. Organizations must ensure that they are using their data effectively to gain key insights quickly to determine cause and minimize impact."

"It’s time to change how we approach incident response," said Haiyan Song, senior vice president, security markets, Splunk. "As attacks become more advanced, frequent, and take advantage of IT complexity, we must become proactive in our approach to security – how else will we know we have been breached? As demonstrated by the swift, global spread of WannaCry, it has never been more important for organizations to proactively monitor, analyze and investigate to verify whether there are real threats, then prioritize and remediate the most critical. By taking an analytics-driven approach, and increasingly automating when possible, security teams can shorten investigation cycles, respond quickly and appropriately in the event of a compromise, free up resources to focus on more strategic initiatives and ultimately improve security posture."

Other findings from the study include:

  • Everyone’s under attack. 62% of firms are being attacked at least weekly, with 30% attacked daily and 10% hourly or continuously. 45% are experiencing a rise in the number of security threats.
  • The volume of incidents is challenging. Organizations experience an average of 40 actionable security alerts per week, with this number rising to 77 for finance and 124 for telco.
  • Most firms only surface a breach to the board at the last possible moment. Asked when they report a security incident to the board, the top triggers were sensitive data breach (66%), compromised customer data (57%), and a mandated notification to a regulator (52%). Only 35% of firms have breach reporting to the board built into their defined incident response processes.

To find out how you compare to your peers when it comes to incident response, visit IDC's Security Response Readiness Assessment.

Methodology

IDC surveyed 600 global organizations with over 500 employees in the U.S., U.K., Germany, France, Sweden and the Netherlands.

The full IDC InfoBrief can be downloaded here.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Meet 'Bro': The Best-Kept Secret of Network Security
Greg Bell, CEO, Corelight,  6/14/2018
Containerized Apps: An 8-Point Security Checklist
Jai Vijayan, Freelance writer,  6/14/2018
Four Faces of Fraud: Identity, 'Fake' Identity, Ransomware & Digital
David Shefter, Chief Technology Officer at Ziften Technologies,  6/14/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-0291
PUBLISHED: 2018-06-20
A vulnerability in the Simple Network Management Protocol (SNMP) input packet processor of Cisco NX-OS Software could allow an authenticated, remote attacker to cause the SNMP application on an affected device to restart unexpectedly. The vulnerability is due to improper validation of SNMP protocol ...
CVE-2018-0292
PUBLISHED: 2018-06-20
A vulnerability in the Internet Group Management Protocol (IGMP) Snooping feature of Cisco NX-OS Software could allow an unauthenticated, adjacent attacker to execute arbitrary code and gain full control of an affected system. The attacker could also cause an affected system to reload, resulting in ...
CVE-2018-0293
PUBLISHED: 2018-06-20
A vulnerability in role-based access control (RBAC) for Cisco NX-OS Software could allow an authenticated, remote attacker to execute CLI commands that should be restricted for a nonadministrative user. The attacker would have to possess valid user credentials for the device. The vulnerability is du...
CVE-2018-0294
PUBLISHED: 2018-06-20
A vulnerability in the write-erase feature of Cisco FXOS Software and Cisco NX-OS Software could allow an authenticated, local attacker to configure an unauthorized administrator account for an affected device. The vulnerability exists because the affected software does not properly delete sensitive...
CVE-2018-0295
PUBLISHED: 2018-06-20
A vulnerability in the Border Gateway Protocol (BGP) implementation of Cisco NX-OS Software could allow an unauthenticated, remote attacker to cause a denial of service (DoS) condition due to the device unexpectedly reloading. The vulnerability is due to incomplete input validation of the BGP update...