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.

Analytics

9/27/2010
06:21 PM
100%
0%

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."

Previous
1 of 2
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
News
Inside the Ransomware Campaigns Targeting Exchange Servers
Kelly Sheridan, Staff Editor, Dark Reading,  4/2/2021
Commentary
Beyond MITRE ATT&CK: The Case for a New Cyber Kill Chain
Rik Turner, Principal Analyst, Infrastructure Solutions, Omdia,  3/30/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
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
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
CVE-2015-20001
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.2.0, BinaryHeap is not panic-safe. The binary heap is left in an inconsistent state when the comparison of generic elements inside sift_up or sift_down_range panics. This bug leads to a drop of zeroed memory as an arbitrary type, which can result in a memory ...
CVE-2020-36317
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.49.0, String::retain() function has a panic safety problem. It allows creation of a non-UTF-8 Rust string when the provided closure panics. This bug could result in a memory safety violation when other string APIs assume that UTF-8 encoding is used on the sam...
CVE-2020-36318
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.49.0, VecDeque::make_contiguous has a bug that pops the same element more than once under certain condition. This bug could result in a use-after-free or double free.
CVE-2021-28875
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.50.0, read_to_end() does not validate the return value from Read in an unsafe context. This bug could lead to a buffer overflow.
CVE-2021-28876
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.52.0, the Zip implementation has a panic safety issue. It calls __iterator_get_unchecked() more than once for the same index when the underlying iterator panics (in certain conditions). This bug could lead to a memory safety violation due to an unmet safety r...