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.


06:21 PM

Five Reasons SIEM Deployments Fail

Security information and event management deployments are often plagued by ease-of-use, scalability, and even organizational problems

Even as the security information and event management (SIEM) market grows, SIEM has picked up a bit of a bad rap among many IT executives for failing to live up to the hype. Many organizations, however, buy into SIEM with unrealistic expectations, believing it will offer them a quick-fix security panacea that automates security detection and protection. The truth is, SIEM is a tool like any other and requires expertise and sleeves-rolled-up work to offer true value.

This expectations gap can result in some serious deployment disappointment. Here are some of the biggest contributing factors to SIEM's spotty success rate:

1. SIEM is hard to use.
The nut of it really comes down to the fact that SIEM is not an easy technology to use. Part of that rests squarely at the feet of SIEM vendors, who still have not done enough to simplify their products -- particularly for small and midsize enterprises, says Mike Rothman, analyst and president of Securosis.

"I think that we need to see more of a set of deployment models [that] make it easier for folks that aren't necessarily experts on this stuff to use it. In order for this market to continue to grow and to continue to drive value to customers, it has to be easier to use, and it has to be much more applicable to the midmarket customer," Rothman says. "Right now the technology is still way too complicated for that."

At the same time, Rothman says organizations are not sufficiently "skilling up" their security workers to squeeze value out of their SIEM investments -- particularly when it comes to figuring out what to do once their SIEM's correlation engine alerts them to a problem.

"Ultimately someone still has to figure out on-site what the hell happened, and that's where you still have a skills gap, which is not just gathering the information, not just analyzing the information, [not just] figuring out when something has gone amiss, but then figuring out how to deal with it from a remediation standpoint," Rothman says. "That's not an indictment of the SIEM market per se; it just still shows the skills gap that we have, certainly within the midmarket type of context in terms of these folks doing whatever needs to be done once they figure out something's broken."

2. Log management lacks standardization.
In order to truly automate the collection of data from different devices and automate the parsing of all that data, organizations need standardization within their logged events, says Scott Crawford, analyst for Enterprise Management Associates.

"This is one of the biggest issues of event management," Crawford says. "A whole range of point products can produce a very wide variety of ways to characterize events."

Crawford says ArcSight has tried to help the field with its common event format, but its position as a vendor has made this effort lack the credibility needed to unify the market. He believes the best shot at the moment is with Mitre's initiative to launch the Common Event Expression -- similar to its successful Common Vulnerability Expression (CVE) for vulnerability management -- on which Mitre has been working in baby steps for the past few years and released an architectural overview earlier in the year.

3. IT can't rise above organizational power struggles.
"One of the key challenges our customers face is really getting all parts of the company to work together to actually make the connections to get the right scope of monitoring," says Joe Gottlieb, president and CEO of SenSage. "And the things you want to monitor sit in different places within the organization and are controlled by different parts of the organization."

As the old phrase goes, "garbage in, garbage out." If organizations cannot get all of the security and event data together that would help put together a picture of a specific incident, then the strongest correlation engine in the world won't do them a much good.

"We all know that has always been one of the most interesting topics in IT: the organizational factions and constituencies and sort of keeping up with all that," Gottlieb says. "That's typically something you have to address to make SIEM work well."

1 of 2
Comment  | 
Print  | 
More Insights
Newest First  |  Oldest First  |  Threaded View
Ransomware Is Not the Problem
Adam Shostack, Consultant, Entrepreneur, Technologist, Game Designer,  6/9/2021
How Can I Test the Security of My Home-Office Employees' Routers?
John Bock, Senior Research Scientist,  6/7/2021
New Ransomware Group Claiming Connection to REvil Gang Surfaces
Jai Vijayan, Contributing Writer,  6/10/2021
Register for Dark Reading Newsletters
White Papers
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: Google's new See No Evil policy......
Current Issue
The State of Cybersecurity Incident Response
In this report learn how enterprises are building their incident response teams and processes, how they research potential compromises, how they respond to new breaches, and what tools and processes they use to remediate problems and improve their cyber defenses for the future.
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2021-06-18
RIOT-OS 2021.01 before commit 44741ff99f7a71df45420635b238b9c22093647a contains a buffer overflow which could allow attackers to obtain sensitive information.
PUBLISHED: 2021-06-18
SerenityOS contains a buffer overflow in the set_range test in TestBitmap which could allow attackers to obtain sensitive information.
PUBLISHED: 2021-06-18
SerenityOS in test-crypto.cpp contains a stack buffer overflow which could allow attackers to obtain sensitive information.
PUBLISHED: 2021-06-18
SerenityOS before commit 3844e8569689dd476064a0759d704bc64fb3ca2c contains a directory traversal vulnerability in tar/unzip that may lead to command execution or privilege escalation.
PUBLISHED: 2021-06-18
RIOT-OS 2021.01 before commit 85da504d2dc30188b89f44c3276fc5a25b31251f contains a buffer overflow which could allow attackers to obtain sensitive information.