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.

Operational Security

4/23/2018
09:35 AM
Alan
 Zeichick
Alan Zeichick
Alan Zeichick
50%
50%

It's the People: 5 Reasons Why SOC Can't Scale

There are always more security alerts and threats to respond, but the answer isn't to simply throw more money at the SOC to hire additional Tier 1 and Tier 2 security analysts.

SAN FRANCISCO -- Blame people for the SOC scalability challenge. On the other hand, don't blame your people. It's not their fault.

The security operations center (SOC) team is frequently overwhelmed, particularly the Tier 1 security analysts tasked with triage. As companies grow and add more technology -- including the Internet of Things (IoT) -- that means more alerts.

As the enterprise adds more sophisticated security tools, such as Endpoint Detection and Response (EDR), that means more alerts. And more complex alerts. You're not going to see a blinking red light that says: "You're being hacked." Or if you do see such an alert, it's not very helpful.

What's the problem? It's the people, say experts at the RSA Conference, which wrapped up last week. The SOC team -- or teams -- simply can't scale fast enough to keep up with the ever-increasing demand. Let's talk about the biggest problems challenging SOC scalability.

Reason #1: You can't afford to hire enough Tier 1 analysts
You certainly can't afford the Tier 2 analysts who respond to real -- or almost certainly real -- incidents. According to a quick glance at sites like Glassdoor and Indeed, be prepared to pay over $100,000 per month, per person. Reason #2: You can't find the analysts; there's not a huge talent pool
"We've created a growing demand for labor, and thus, we've created this labor shortage," said Malcolm Harkins, chief security and trust officer of Cylance.

There are huge numbers of open positions at all levels of information security, and that includes in-enterprise SOC team members. Sure, you could pay more, or do competitive recruiting, but go back to the previous point: You can't afford that. Perhaps a managed security service provider can afford to keep raising salaries, because an MSSP can monetize that expense. An ordinary enterprise can't, because security is an expense.

Reason #3: Team training is a never-ending journey without a happy ending
Even with the best security tools, being an analyst requires constant training on threats and techniques -- which is expensive to offer, especially for a smaller organization. And wouldn't you know it, as soon as you get a group of triage specialists or incident responders trained up nicely, off they go for a better job. Reason 4: Collaboration is tough for incident handoffs to the next analyst
Rishi Bhargava, co-founder of Demisto, pointed out that around-the-clock, follow-the-sun security, with investigations and incident response, brings its own challenges, particularly during shift changes.

"Collaboration, along with all the skill set problems, is a real problem," Bhargava said. "How do you do the handoff? How does the collaboration happen? How do you ensure that everyone has the right context to advance the investigation?"


The fundamentals of network security are being redefined -- don't get left in the dark by a DDoS attack! Join us in Austin from May 14-16 at the fifth annual Big Communications Event. There's still time to register and communications service providers get in free!

You can't send the next shift team an email explaining the status of today's incidents, he added, and hope an analyst can pick up it up at the start of his or her shift.

Reason #5: Security management can't scale either
There's alert fatigue for the Tier 1 and Tier 2 analysts, but the problems go all the way up the food chain.

"There's decision-maker dementia for the executives, who are pulled in too many different directions with competition priorities -- and they can't figure out how to scale either," said Cylance's Harkins. There are too many risks that senior analysts and management must address, contain or stop, for the good of the company.

It's not their fault
Go ahead, blame the analysts, and security managers, for not handling an ever-increasing workload, while fighting alert fatigue, knowing the next incident might be a Target-sized, or Equifax-sized, data breach. The real challenge is to find more resources, including better tools, practices and procedures, for scaling the SOC.

Because you can't simply throw more people at the problem.

Related posts:

— Alan Zeichick is principal analyst at Camden Associates, a technology consultancy in Phoenix, Arizona, specializing in enterprise networking, cybersecurity, and software development. Follow him @zeichick.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
More SolarWinds Attack Details Emerge
Kelly Jackson Higgins, Executive Editor at Dark Reading,  1/12/2021
Vulnerability Management Has a Data Problem
Tal Morgenstern, Co-Founder & Chief Product Officer, Vulcan Cyber,  1/14/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
2020: The Year in Security
Download this Tech Digest for a look at the biggest security stories that - so far - have shaped a very strange and stressful year.
Flash Poll
Assessing Cybersecurity Risk in Today's Enterprises
Assessing Cybersecurity Risk in Today's Enterprises
COVID-19 has created a new IT paradigm in the enterprise -- and a new level of cybersecurity risk. This report offers a look at how enterprises are assessing and managing cyber-risk under the new normal.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-7343
PUBLISHED: 2021-01-18
Missing Authorization vulnerability in McAfee Agent (MA) for Windows prior to 5.7.1 allows local users to block McAfee product updates by manipulating a directory used by MA for temporary files. The product would continue to function with out-of-date detection files.
CVE-2020-28476
PUBLISHED: 2021-01-18
All versions of package tornado are vulnerable to Web Cache Poisoning by using a vector called parameter cloaking. When the attacker can separate query parameters using a semicolon (;), they can cause a difference in the interpretation of the request between the proxy (running with default configura...
CVE-2020-28473
PUBLISHED: 2021-01-18
The package bottle from 0 and before 0.12.19 are vulnerable to Web Cache Poisoning by using a vector called parameter cloaking. When the attacker can separate query parameters using a semicolon (;), they can cause a difference in the interpretation of the request between the proxy (running with defa...
CVE-2021-25173
PUBLISHED: 2021-01-18
An issue was discovered in Open Design Alliance Drawings SDK before 2021.12. A memory allocation with excessive size vulnerability exists when reading malformed DGN files, which allows attackers to cause a crash, potentially enabling denial of service (crash, exit, or restart).
CVE-2021-25174
PUBLISHED: 2021-01-18
An issue was discovered in Open Design Alliance Drawings SDK before 2021.12. A memory corruption vulnerability exists when reading malformed DGN files. It can allow attackers to cause a crash, potentially enabling denial of service (Crash, Exit, or Restart).