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.

Mastering Security Analytics
Newest First  |  Oldest First  |  Threaded View
User Rank: Apprentice
11/3/2014 | 11:22:25 AM
Re: Mastering Security Analytics
"...SIEM platforms still can't pull in all of the necessary feeds to track attacks across the typical attack life cycle, or kill chain, which often spans endpoints, network resources, databases, and so on..." - if so you've not the wrong SIEM platform or Use Cases, normally the latter.

I'm continually frustrated by working with companies who model use cases from available, and easy to get hold of, event sources rather than considering the intent, tools, techniques and procedures that the attacker will use (which is what you're trying to detect).  In these bottom-up cases, you end up modelling your defences in use cases, not what the attacker is doing.  These same companies are now shouting from the hilltop that SIEM is broken, but they're now going to invest heavily in analytics and fail again because the problem isn't the tool - it's the approach.

An efficient and effective SIEM platform should model the full extent of an attack-chain (we use 10 different stages in our methodology) and absolutely should include traditional infosec technical controls, network, database, endpoints - but also user profiles & permissions and applications.  If your SIEM can't handle these - your chosen SIEM platform - not SIEM itself - is the problem.  A good security operations capability should b eable to do everything mentioned here, with the right processes and skills to develop good attack-chain based use cases, to triage and tune rules continually, to product meaningful management information broken down by line-of-business and to report on the effectiveness of security controls across the business. 

The problem with Target, as you point out, was false positives.  Did Target have the right SLAs in place with their MSSP around false positives?  Did they have a defined process to continually refine content with the service provider to reduce false positives?  Did they select the service provide with the right service catalog and skills to effectively detect, prioritise and investigate incidents - or did they simply through the monitoring problem over the shelf at a third party who'd provide the service at the cheapest possible cost?  None of these problems are SIEM related, their process and governance related.

You should also build your rules to offer staged correlation that can capture possible indicators of compromise that can be used as the starting point for exploratory analytics - SIEM, analytics and visulation coupled with good profiling of your threats into use cases is the solution, not replacing one set of SIEM blinky lights with another set of analytics blinky lights.  

I'm coming across so many companies that haven't done the basics with regard business alignment, people and process around their SIEM platforms that are now looking to replace them with analytics platforms, and they won't do the right  business alignment, people and process there either -  business alignment, people and process is hard, buying a product isn't.
User Rank: Author
10/15/2014 | 7:28:38 AM
Re: Mastering Security Analytics
Nice article @ErickaChickowski. As you've clearly outlined throughout, there are a few pain points: volume, prioritization, and resources (both people and technology). I agree that if we continue "living in this alert-driven culture", we will never get out heads above water; regardless of how many responders are at our disposal.

I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Current Issue
Black Hat USA 2022 Attendee Report
Black Hat attendees are not sleeping well. Between concerns about attacks against cloud services, ransomware, and the growing risks to the global supply chain, these security pros have a lot to be worried about. Read our 2022 report to hear what they're concerned about now.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2022-08-12
Improper input validation on the `contains` LoopBack filter may allow for arbitrary SQL injection. When the extended filter property `contains` is permitted to be interpreted by the Postgres connector, it is possible to inject arbitrary SQL which may affect the confidentiality and integrity of data ...
PUBLISHED: 2022-08-12
undici is an HTTP/1.1 client, written from scratch for Node.js.`undici` is vulnerable to SSRF (Server-side Request Forgery) when an application takes in **user input** into the `path/pathname` option of `undici.request`. If a user specifies a URL such as `` or `//` ```js con...
PUBLISHED: 2022-08-12
BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Some links in BookWyrm may be vulnerable to tabnabbing, a form of phishing that gives attackers an opportunity to redirect a user to a malicious site. The issue was patche...
PUBLISHED: 2022-08-12
This Rails gem adds two methods to the ActiveRecord::Base class that allow you to update many records on a single database hit, using a case sql statement for it. Before version 0.1.3 `update_by_case` gem used custom sql strings, and it was not sanitized, making it vulnerable to sql injection. Upgra...
PUBLISHED: 2022-08-12
Shield is an authentication and authorization framework for CodeIgniter 4. This vulnerability may allow [SameSite Attackers](https://canitakeyoursubdomain.name/) to bypass the [CodeIgniter4 CSRF protection](https://codeigniter4.github.io/userguide/libraries/security.html) mechanism with CodeIgniter ...