Skip to main content

Effective Management of Security Incidents





















You'll be excited to hear that we released an additional tab under the Risks view of our product, to enable Incident Management. The Incidents tab surfaces the highest fidelity alerts that should be prioritized in terms of investigations and/or proactive hunting and enables management of those incidents.

Screen Shot 2017-11-14 at 3.20.23 PM.png


Here's what you need to know about this new tab:

What are the Key features?

  • Visualization - dashboards and tables summarizing incidents
  • Creation - create/edit incidents, manually or automatically
  • Notification - set up notification options (Ticketing, Slack, Email, etc.)
  • Workflow - assign & change status of incidents
  • Investigations - investigate incidents, pivot to alerts, search, or the graph canvas

What dashboards are available?

  • View Incidents by status and priority
  • View trending metrics, such as # of open incidents over time
  • Filterable table with time, description, priority, status, affected entities, and more

How are Incidents created?

  • Incidents can be created manually from one or more individual alerts
  • Alert clusters, which are chains of interrelated alerts, automatically create incidents by default
  • Rules and anomalies can be configured to create incidents (for example, create an incident for all critical Wildfire alerts)

What notification options are available?

  • Out of the box notification options include Email, Slack, ServiceNow
  • Users can add their own integrations or request additional integrations

What workflow is enabled?

  • Users can sort incidents by time and priority
  • Users can assign incidents to users of Sift Security
  • Users can change the stage of incidents (e.g. Analysis, Remediate, Closed)
  • Users can provide feedback on the incident (e.g. False Positive)

What investigations and remediation capabilities are possible?

  • Users can see all the alerts that constitute an Incident
  • Users can see the raw details in Search
  • Users can investigate the Incident using the Graph Canvas, visualizing the alerts and context
  • Users can select from out of the box integrations to take action
  • Users can add custom integrations to facilitate remediation


For further reading, check out docs.siftsecurity.com, and learn more about how to take advantage of these new incident management capabilities.







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…

Data Exfiltration from AWS S3 Buckets

You will have no doubt heard by now about the recent Booz Allen Hamilton breach that took place on Amazon Web Services – in short, a shocking collection of 60,000 government sensitive files were left on a public S3 bucket (file storage in Amazon Web Services) for all to see. We are all probably too overwhelmed to care, given all the recent breaches we have been hearing about in the news. But with this breach it was different, it involved a trusted and appointed contractor whose job it was to follow security policies, put in place to avoid such incidents. So was this incident accidental or malicious? More, later about the tools we can use to tell the difference between the two. First, lets recap what happened.The IncidentAccording to Gizmodo, the 28GB of data that was leaked not only contained sensitive information on recent government projects, but at least a half dozen unencrypted passwords belonging to government contractors with Top Secret Clearance – meaning anyone who got their h…

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 interr…