Alert Feature Overview

Introduction

Threat Stack is a behavior based anomaly detection platform, based on telemetry delivered into the platform from various sources, including your host and your infrastructure.

What is an Alert?

Alerts are behavior anomalies elevated from the stream of raw telemetry by rule filters. Alerts contain two main components:

  • The alert title
  • The contributing events
Term Definition
Contributing Events The raw telemetry that caused the anomaly to happen.
Alert Title The name and substitutions (dynamic content) that adds context to the alert.

The substitution fields should match the aggregation fields selected for the alert. The aggregation fields define the uniqueness of the alerts. See the Life Cycle of an Alert article for additional information on aggregations.

2_alert_and_details.png

Where Do I Find Alerts in the Threat Stack Application?

In the left navigation bar, select the Alerts tab. The Alerts page displays the following information:

  • Alert Trends over time in the form of a histogram
  • Alerts sorted by severity, type, active or dismissed
  • Alert information table including filter rule and ruleset details

AlertsPage.png

On the Alerts page you have the option to:

  • Select an alert to review its alert details
  • Suppress an alert
  • Dismiss an alert (if you dismiss an alert it displays in the Dismissed Alerts tab)

Important

If a rule that triggered an alert is deleted, a generic icon (Placeholder_icon.png) displays on the Alerts page instead of the icon associated with the triggered rule.

Why Would an Alert Trigger?

Alerts trigger when Threat Stack detects a behavior anomaly deemed inappropriate based on the rules you enabled or created. Rules require a filter to match behaviors against raw telemetry.

Term Definition
Telemetry Events and behavior anomalies.
Rules Behaviors that you want to catch from the raw telemetry stream.

Rule Filter Example

Behavior to Catch Rule Filter
Privilege escalations command =“sudo”
User access Event_type =“login"

If a rule displays alerts for behavior you consider baseline or normal, you can create a suppression filter to have it no longer report that behavior. The content should match the aggregation fields selected for the alert. The aggregation fields define the uniqueness of the alerts. See the How do I Suppress an Alert? article.

Threat Stack includes three levels of elevation of behaviors to indicate the severity of the alert:

  • Severity 1 (Sev 1): It is the highest elevation of behaviors.
    • Recommended for behaviors and scenarios that should wake you up in the middle of the night. Only used for behavior anomalies where an action and remediation runbook exists.
  • Severity 2 (Sev 2): It is the second highest elevation of behaviors.
    • Recommended for behaviors you want to monitor and review with stakeholders to improve over time.
  • Severity 3 (Sev 3): It is the third highest elevation of behaviors.
    • Recommended for behaviors that companies log for compliance or forensics purposes.

Severity_levels.png

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request