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.

Vulnerabilities / Threats

1/23/2019
02:30 PM
Chetan Mundhada
Chetan Mundhada
Commentary
Connect Directly
LinkedIn
RSS
E-Mail vvv
100%
0%

The Evolution of SIEM

Expectations for these security information and event management systems have grown over the years, in ways that just aren't realistic.

The concept of security information and event management (SIEM) has its origins in the need to have a unified view of security events across multiple technologies. From antivirus software detecting malware on some endpoint to a firewall blocking suspicious traffic on an unauthorized port, SIEM gives security operations teams a central dashboard from which they could assess the "security posture" of their organizations. The dashboard serves as a kind of one-stop shop for finding and acting on security-related information, hence the name.

Over the years, expectations from these systems have grown, with marketers beginning to claim that their SIEM platforms can even be used to correlate seemingly isolated events and identify threats that individual security products would otherwise miss. Given the rising importance of cybersecurity, this technology quickly catapulted to the top of every CISO's wish list.

What followed was a rush fueled by paranoia and efficient marketing to set up SIEM-powered security operations centers. SIEM platforms evolved into multifaceted tools for monitoring, reporting, and forensic investigation. Suddenly, SIEM had become such a crucial component of cybersecurity strategy that regulations began requiring the use of such platforms in banking institutions.

SIEM, however, is hardly a panacea for all security problems. Issues like complex implementation, lack of flexibility, slow response times, and sky-high costs became seemingly necessary evils. Moreover, the torrent of alerts kept security teams under constant pressure to "close issues." It was only natural for users to notice the elephant in the room: The reality of SIEM systems had fallen far short of all the hype.

In hindsight, it seems obvious that SIEM systems were unable to deliver on their marketers' promises. They were built on a back-end technology — relational databases — that wasn't designed for use like this. The volume and variety of data generated in today's environments shows that traditional RDBMS-based SIEM systems cannot find the proverbial needle in the haystack. The volume of alerts generated cannot be investigated manually by SOC analysts. Correlation-based rules alone cannot identify the ever-increasing number of scenarios in which a cybersecurity incident can penetrate an organization.

Advancements in technologies managing unstructured data (i.e., big data), toolkits leveraging data science in machine-assisted decision-making (i.e., machine learning), and frameworks that allow multiple isolated security applications to work together (i.e., security orchestration) have given us the firepower needed to scale up the capabilities of the next generation of SIEM systems.

Security analytics and orchestration solutions available today are capable of processing large volumes of data at high speeds in a scale-as-you-grow architecture. This processing capability allows users to build models using data science. These models can identify both patterns of normal activity and outliers or potentially malicious events without writing specific rules. The systems can be integrated with other applications to exchange information and investigate the outliers identified. Orchestration can also be paired with automated threat response mechanisms, reducing human involvement.

Now, marketers have begun raising the bar on what technology alone can deliver, furthering the competition between vendors to prove technical superiority. Today's automated black-box solutions claim to leverage advanced artificial intelligence and orchestration to provide security at the click of a button. There is a sense of déjà vu with banking regulators prescribing big data-based analytics solutions to manage security operations.

What is needed is an understanding of what capabilities users should expect of the technologies they use, and how to correctly leverage them to improve security. Every IT environment is unique, so expecting software to automagically secure them all with artificial intelligence is still beyond the realm of what technology can deliver.

Technology plays a crucial role in processing large volumes of data, performing repeated tasks, making disconnected systems work together, and using complex math to identify the potentially malicious. This is already the bulk of the heavy lifting in ensuring security; what is needed further is human intelligence for correct navigation.

No doubt, this calls for a comprehensive skill set, which is evidently a scarce resource. While it might appear difficult to pull off, being blown away by marketers boasting about one-size-fits-all solutions is certainly not the best way to start.

Related Content:

Chetan Mundhada drives the Sales team for DNIF with a focus on growing the company's enterprise and channel. He brings to the position a successful track record of over 14 years in the IT infrastructure and security domain. He has a keen interest in data analytics and ... View Full Bio
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Florida Town Pays $600K to Ransomware Operators
Curtis Franklin Jr., Senior Editor at Dark Reading,  6/20/2019
Pledges to Not Pay Ransomware Hit Reality
Robert Lemos, Contributing Writer,  6/21/2019
AWS CISO Talks Risk Reduction, Development, Recruitment
Kelly Sheridan, Staff Editor, Dark Reading,  6/25/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Building and Managing an IT Security Operations Program
As cyber threats grow, many organizations are building security operations centers (SOCs) to improve their defenses. In this Tech Digest you will learn tips on how to get the most out of a SOC in your organization - and what to do if you can't afford to build one.
Flash Poll
The State of IT Operations and Cybersecurity Operations
The State of IT Operations and Cybersecurity Operations
Your enterprise's cyber risk may depend upon the relationship between the IT team and the security team. Heres some insight on what's working and what isn't in the data center.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-1619
PUBLISHED: 2019-06-27
A vulnerability in the web-based management interface of Cisco Data Center Network Manager (DCNM) could allow an unauthenticated, remote attacker to bypass authentication and execute arbitrary actions with administrative privileges on an affected device. The vulnerability is due to improper session ...
CVE-2019-1620
PUBLISHED: 2019-06-27
A vulnerability in the web-based management interface of Cisco Data Center Network Manager (DCNM) could allow an unauthenticated, remote attacker to upload arbitrary files on an affected device. The vulnerability is due to incorrect permission settings in affected DCNM software. An attacker could ex...
CVE-2019-1621
PUBLISHED: 2019-06-27
A vulnerability in the web-based management interface of Cisco Data Center Network Manager (DCNM) could allow an unauthenticated, remote attacker to gain access to sensitive files on an affected device. The vulnerability is due to incorrect permissions settings on affected DCNM software. An attacker...
CVE-2019-1622
PUBLISHED: 2019-06-27
A vulnerability in the web-based management interface of Cisco Data Center Network Manager (DCNM) could allow an unauthenticated, remote attacker to retrieve sensitive information from an affected device. The vulnerability is due to improper access controls for certain URLs on affected DCNM software...
CVE-2019-10133
PUBLISHED: 2019-06-26
A flaw was found in Moodle before 3.7, 3.6.4, 3.5.6, 3.4.9 and 3.1.18. The form to upload cohorts contained a redirect field, which was not restricted to internal URLs.