August 30, 2011 By John Burnham 4 min read

How Do Security Intelligence Solutions Differ from First-Gen SIEM Products?

This is part 2 of an ongoing series of posts that answer “Six Things You Always Wanted to Know About Security Intelligence but Were Afraid to Ask.”

Now that we have a good understanding of Security Intelligence, let’s draw a clear picture of how modern Security Intelligence solutions evolved – and differ – from first-generation SIEM products.  SIEM has become a widely deployed technology over the last 5+ years, and for good reason.  But due to scale limitations and lack of visibility, legacy SIEM products can no longer go toe-to-toe with the advanced targeted threats (AKA, advanced persistent threats) making headlines today.

Log Management and Security Information and Event Management (SIEM) products are a standard element of the IT security landscape today.  Large and small organizations in private and public sectors have widely adopted the solutions, and Gartner has published its SIEM Magic Quadrant report for a number of years.  (Reportedly it’s one of Gartner’s most popular MQ reports across all IT disciplines.)  The popularity of SIEM owes to its value:  sophisticated monitoring and reporting on diverse network activity, enabling the identification of potential security risks and ensuring compliance with regulatory and policy requirements.

But first-generation SIEM products are now obsolete. Yes, obsolete. Here’s where they lag Security Intelligence solutions:

  • No network activity monitoring. In the past, event logs from devices, applications and servers gave you a rough idea of what was happening on your network.  Today, that’s just a starting point.  Security Intelligence now requires real-time visibility into the flows, user activity, social media usage, mobile access and application content traversing your network – something first-gen SIEM can’t offer.  Is that conversation using port 80 really web traffic, or is it a hidden botnet IRC communication?  Have intruders compromised a user account and used it to post sensitive information to social media sites?  Are your employees committing fraud or transmitting sensitive intellectual property inappropriately?  Without integrating network behavior analysis / anomaly detection into SIEM, you won’t know until it’s too late.
  • Not architected to scale. First-gen SIEM products did a passable job of collecting and correlating event logs for moderate size organizations.  But add in flow data, perform a few simultaneous searches, or deploy in a very large enterprise, and first-gen SIEM’s choke.  The reason is simple: they’re not architected to scale.  They depend on external relational databases, which struggle to support the volume of I/O operations involved in demanding scenarios.  Security Intelligence solutions are built from the ground up with purpose-built databases, so they can collect and correlate massive volumes of data in real time, and still respond nimbly to ad hoc searches.
  • No pre-exploit security awareness. The Security Intelligence timeline doesn’t begin at the point of exploit or breach.  That’s just when the clock starts ticking on your detection and remediation activities.  Modern Security Intelligence solutions inherently differ from first-generation SIEM products by integrating pre-exploit risk and vulnerability management capabilities, as one example.  This allows you to identify, prioritize and reduce risks associated with misconfigured devices and unpatched vulnerabilities.  In this way you actually reduce the number of breaches, as well as detect and remediate the ones that occur.
  • Reliance on signature-based detection. The game has changed.  You can’t sit back, update your malware signatures, and expect to protect your network.  First-gen SIEM offerings relied too much on the assumption of a finite and familiar set of threats.  This approach fails when the threat vectors grow exponentially more diverse by the day.
  • Too slow to deploy, too expensive to staff. When first-gen SIEMs hit the market, early adopters were willing to spend plenty of time and money to get them up and running.  Connectors and rules needed to be written, users needed to be trained and so on.  Once in production, their staffing requirements could also be significant.  They spit out too many false positives, thus requiring the addition of staff to investigate volumes of incidents.  Modern Security Intelligence solutions use a broader set of data (event, flow, asset, topology, vulnerability, configuration, etc.) and advanced automation to cut through the noise and reduce – not expand – security staffing requirements.  One organization, for example, reduced ongoing security staff time requirements by 88% with Security Intelligence:

In sum, Security Intelligence solutions have made first-generation SIEM point products obsolete, and now help organizations protect against more challenging and diverse threats, with far less effort.  They expand the scope of analysis to identify and prioritize risks before the point of exploit, and detect and resolve breaches faster through user activity and content visibility.  They also scale to far greater volumes of data at radically reduced storage costs.  And they are deployable and manageable with less manual work, satisfying stringent budget and ROI parameters.

Or in the words of one of our other customers, a leading provider of photonics-based solutions:

“We recently had an incident where someone was trying to port scan one of our email servers. Our previous system would not have seen this intrusion. Because of QRadar, we quickly – in a matter of minutes – located the individual computer and shut down the activity before any further damage could be done. The ability to locate and analyze information quickly – almost instantaneously – and in a fashion we could not do before has saved us incredible amounts of time.”

Stay tuned for the next post in this series, where we’ll look in depth at the question of how much staffing and expertise is needed to use Security Intelligence solutions

More from Risk Management

Are we getting better at quantifying risk management?

4 min read - As cyber threats grow more sophisticated and pervasive, the need for effective risk management has never been greater. The challenge lies not only in defining risk mitigation strategy but also in quantifying risk in ways that resonate with business leaders. The ability to translate complex technical risks into understandable and actionable business terms has become a crucial component of securing the necessary resources for cybersecurity programs.What approach do companies use today for cyber risk quantification? And how has cyber risk…

Cybersecurity Awareness Month: Cybersecurity awareness for developers

3 min read - It's the 21st annual Cybersecurity Awareness Month, and we’re covering many different angles to help organizations manage their cybersecurity challenges. In this mini-series of articles, we’re focusing on specific job roles outside of cybersecurity and how their teams approach security.For developers, cybersecurity has historically been a love-hate issue. The common school of thought is that coders are frustrated with having to tailor their work to fit within cybersecurity rules. However, many companies are embracing a security-first approach, and some developers…

Spooky action: Phantom domains create hijackable hyperlinks

4 min read - According to a recent paper published at the 2024 Web Conference, so-called "phantom domains" make it possible for malicious actors to hijack hyperlinks and exploit users' trust in familiar websites.The research defines phantom domains as active links to dot-com domains that have never been registered.Here's what enterprises need to know about how phantom domains emerge, the potential risks they represent and what they can do to disrupt phantom attacks. There are two common types of phantom domains: Errors and placeholders.Domain errorsErrors…

Topic updates

Get email updates and stay ahead of the latest threats to the security landscape, thought leadership and research.
Subscribe today