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
How Enterprises Are Assessing Cybersecurity Risk in Today's Environment
The adoption of cloud services spurred by the COVID-19 pandemic has resulted in pressure on cyber-risk professionals to focus on vulnerabilities and new exposures that stem from pandemic-driven changes. Many cybersecurity pros expect fundamental, long-term changes to their organization's computing and data security due to the shift to more remote work and accelerated cloud adoption. Download this report from Dark Reading to learn more about their challenges and concerns.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2022-01-28
A local privilege escalation vulnerability was found on polkit's pkexec utility. The pkexec application is a setuid tool designed to allow unprivileged users to run commands as privileged users according predefined policies. The current version of pkexec doesn't handle the calling parameters count c...
PUBLISHED: 2022-01-28
An incorrect default permission vulnerability exists in the cgiserver.cgi cgi_check_ability functionality of reolink RLC-410W v3.0.0.136_20121102. All the Get APIs that are not included in cgi_check_ability are already executable by any logged-in users. An attacker can send an HTTP request to trigge...
PUBLISHED: 2022-01-28
A firmware update vulnerability exists in the 'factory' binary of reolink RLC-410W v3.0.0.136_20121102. A specially-crafted series of network requests can lead to arbitrary firmware update. An attacker can send a sequence of requests to trigger this vulnerability.
PUBLISHED: 2022-01-28
A denial of service vulnerability exists in the cgiserver.cgi API command parser functionality of Reolink RLC-410W v3.0.0.136_20121102. A specially-crafted series of HTTP requests can lead to denial of service. An attacker can send an HTTP request to trigger this vulnerability.
PUBLISHED: 2022-01-28
Missing DLLs, if replaced by an insider, could allow an attacker to achieve local privilege escalation on the DeltaV Distributed Control System Controllers and Workstations (All versions) when some DeltaV services are started.