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.

Risk

9/6/2018
01:00 PM
Connect Directly
Twitter
RSS
E-Mail
100%
0%

The SOC Gets a Makeover

Today's security operations center is all about reducing the number of alerts with emerging technologies - and enhancing old-school human collaboration. Here's how some real-world SOCs are evolving.

(Continued from Page 1)

Some SOC operators are looking to cut head count as much as possible. One approach is to completely automate Tier 1 tasks, incorporating them into orchestration and automation platforms, for instance. "You cut the number of people," says one CISO from a large company who requested anonymity. Tier 2 analysts become more of the skilled first responder who can move and adapt, and Tier 3 can tackle more proactive threat hunting and IR.

"So you bring in more skilled people," the CISO says, who can be trained to perform more advanced tasks like penetration testing, and operate with a smaller team.

Tier Mashup
At managed security services provider MKACyber's SOC in Fairfax, Va., data and detection are organized by use cases and attack types that can help guide junior analysts through the SOC process. Mischel Kwon, founder and CEO of MKACyber, says the goal is to operate less as a tiered operation and more as a collaborative one. The analysts have "gates" that lead them step-by-step through the process and release them to the next step, for example, she says.

So when a phishing email generates an alert, for instance, the process flow guides them through a review to confirm whether or not the alert is actually an incident. "They then upload all of the artifacts, and a [senior] analyst reviews their work and approves it for the next level."

By integrating the approvals process and IR actions, analysts of all levels work together, she says.

Kwon predicts SOCs will be more cloud-based in the next five to 10 years. "I'm hoping there's a change for the future with more integration of vulnerability management and remediation in the SOC" as well, she says.

Data-handling in the SOC also will evolve. "In the next few years, I see us doing different types of handling data ... getting more into tagging and more data science-type research as opposed to the SIEM [approach]," Kwon says. "I see us moving away from the SIEM model."

Related Content:

 

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.

Kelly Jackson Higgins is the Executive Editor of Dark Reading. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise ... View Full Bio
 

Recommended Reading:

Previous
2 of 2
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Why Vulnerable Code Is Shipped Knowingly
Chris Eng, Chief Research Officer, Veracode,  11/30/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-21270
PUBLISHED: 2020-12-03
Versions less than 0.0.6 of the Node.js stringstream module are vulnerable to an out-of-bounds read because of allocation of uninitialized buffers when a number is passed in the input stream (when using Node.js 4.x).
CVE-2020-26248
PUBLISHED: 2020-12-03
In the PrestaShop module "productcomments" before version 4.2.1, an attacker can use a Blind SQL injection to retrieve data or stop the MySQL service. The problem is fixed in 4.2.1 of the module.
CVE-2020-29529
PUBLISHED: 2020-12-03
HashiCorp go-slug before 0.5.0 does not address attempts at directory traversal involving ../ and symlinks.
CVE-2020-29534
PUBLISHED: 2020-12-03
An issue was discovered in the Linux kernel before 5.9.3. io_uring takes a non-refcounted reference to the files_struct of the process that submitted a request, causing execve() to incorrectly optimize unshare_fd(), aka CID-0f2122045b94.
CVE-2020-17527
PUBLISHED: 2020-12-03
While investigating bug 64830 it was discovered that Apache Tomcat 10.0.0-M1 to 10.0.0-M9, 9.0.0-M1 to 9.0.39 and 8.5.0 to 8.5.59 could re-use an HTTP request header value from the previous stream received on an HTTP/2 connection for the request associated with the subsequent stream. While this woul...