Skip to main content

Using the Security Event Graph to Drive Alert Prioritization


One of the biggest differentiators at Sift Security is our security event graph: We map security events into a graph database. We then analyze the graph structure to prioritize alerts. Specifically, we look for clusters of interrelated alerts, score the clusters, and surface the clusters to the analyst. The analyst can then investigate each cluster in order, quickly assessing the threat and resolving the alerts in bulk.  

Our algorithms do the important work of sifting through isolated alerts and separating the false alarms and low priority alerts from high priority security incidents. We identify the high priority incidents by analyzing how alerts are related to each other. Key to this approach is our security event graph. This graph is stored in a graph database, a relationship-centric database that enables rapid execution of complex queries that would be very expensive to make in a traditional RDBMS.  The graph structure enables us to rapidly traverse relationships and find interrelated alerts. We use JanusGraph, an open-source, scalable, and distributed graph database, to store, query, and analyze our security event graph. 

The clusters are scored and ranked based on a number of factors, including:
  • Number and priority of alerts
  • Number of alert sources and types
  • Number of different affected entity types
In this post, we share two examples of how our graph algorithms provide effective alert prioritization, one from a traditional SIEM use case and another from our CloudHunter product.

SIEM Alert Prioritization

In this scenario, we have ingested Windows Event, netflow, Cylance, and Cisco IronPort logs. We have alerts from:
  • Threat intelligence sources
  • Cylance Antivirus
  • Sift Security’s Entity Behavioral Analytics module
  • Sift Security’s Detection Rules module
In total, there are over 1,000 alerts affecting some 70 host and 10 users.
The graph algorithms identify one cluster of alerts that stands out above the rest.  This cluster contains 55 alerts, 44 of which are high risk.  We display a summary of the alerts, including a breakdown of the alert priority scores by entity, shown below.

Screen Shot 2017-08-01 at 11.18.22 AM.png

We also surface an interactive visualization of this cluster of alerts to help the analyst quickly assess the threat.  The visualization (below) shows the user credential “Robert” at the center of the cluster, and 3 affected hosts: ws02, ws35, and dev.  The processes shared between ws35 and ws02 are a malware exploit identified by Cylance, the processes shared between ws02 and dev are reconnaissance processes identified by our Entity Behavioral Analytics, and the IP address 202.116.65.35 is a threat intelligence hit.  Together, this cluster represents a successful malware exploit affecting 3 hosts and 2 user credentials.  
Screen Shot 2017-08-01 at 11.24.07 AM.png

CloudHunter Alert Prioritization

In the CloudHunter example, we have ingested CloudTrail logs from multiple AWS accounts.  The alerts come from two places:
  • Sift Security’s Analytics Module
  • Sift Security’s Detection Rules Module
Because this is a CloudHunter deployment, the detection rules module is preconfigured to alert on the Center for Internet Security benchmarks, and the analytics are configured for common cloud security use cases, such as identifying privilege escalation, data exfiltration, and other misuse of resources.
From thousands of individual alerts, the graph algorithms again identify a high priority cluster (below).  This cluster shows demo-contractor creating an instance from an AMI, and automated-s3-user accessing sensitive documents in s3 from that instance.  This is a situation where an insider was able to get access to data that should not have been able to by abusing the privileges they were granted. 

Screen Shot 2017-08-01 at 11.54.11 AM.png

Conclusions

The benefit of this graph-based alert prioritization approach is that these clusters of alerts may have otherwise gone unnoticed for a while, buried in a pile of other similar alerts. Our graph based alert prioritization helps reduce the mean time to remediation by enabling analysts to be more effective in their investigations.  If you’d like to try out our graph based alert prioritization techniques for yourself, consider trying CloudHunter, which can be deployed in under and hour to start identifying prioritized security incidents in your AWS cloud infrastructure.

For other posts about alert prioritization, see:

Comments

Post a Comment

Popular posts from this blog

Sift Security Tools Release for AWS Monitoring - CloudHunter

We are excited to release CloudHunter, a web service similar to AWS CloudTrail that allows customers to visually explore and investigate their AWS cloud infrastructure.  At Sift, we felt this integration would be important for 2 main reasons:
Investigating events happening in AWS directly from Amazon is painful, unless you know exactly what event you're looking for.There are not many solutions that allow customers to follow chains of events spanning across the on-premises network and AWS on a single screen. At Netflix, we spent a lot of time creating custom tools to address security concerns in our AWS infrastructure because we needed to supplement the AWS logs, and created visualizations based on that data.  The amazing suite of open source tools from Netflix are the solutions they used to resolve their own pain points.  Hosting microservices in the cloud with continuous integration and continuous deployment can be extremely efficient and robust.  However, tracking events, espec…

Sift Security and WannaCry

😢 The WannaCry ransomware attack has left security teams around the world scrambling to make sure they are protected and to assess whether they have been victimized. To protect themselves, organizations need to have visibility into which systems are vulnerable and be able to rapidly roll out patches.  To understand whether they have been targeted, they need visibility into the channels over which the ransomware is distributed.  To understand whether they have been infected, they need visibility into the endpoints.
Over the past weekend, I was bombarded with questions from current customers, potential customers, former colleagues, friends, and family.  Am I vulnerable? How do I protect myself? How do I know if I’ve been hit? What do I do if I’ve been hit? What can you do to help me?
This post focuses primarily on the last question. What can we at Sift Security do to help an organization respond to a massive ransomware attack? I break this down into four categories, visibility, analyt…

Next-Generation SIEMs

Intelligence, Speed, Simplicity, AutomationOverviewMajor network and security trends, including exponentially increasing network traffic, cloud architectures, complex attack surfaces, and advanced adversaries, have created new challenges for security operations in adapting to this changing threat landscape.
Increased Traffic, Hybrid Cloud Architectures, and Sophisticated Adversaries Are Overwhelming SOCs
The Security Operations Center is faced with alert overload, often paralyzed with too much information to filter, prioritize, and act upon. The end result is an inability to find the true risk amongst thousands of alerts every day with the largest of organizations easily facing millions of alerts per day.Incident responders are challenged at finding relevant information or seeing the relationships amongst disparate indicators of compromise that are buried within logs, causing delays in assessing, understanding, and mitigating incidents.T…