Detection: Crowdstrike Multiple LOW Severity Alerts

Updated Date: 2024-09-30 ID: 5c2c02d8-bee7-4f5c-9dea-e3e1012daddb Author: Teoderick Contreras, Splunk Type: Anomaly Product: Splunk Enterprise Security

Description

The following analytic detects multiple CrowdStrike LOW severity alerts, indicating a series of minor suspicious activities or policy violations. These alerts are not immediately critical but should be reviewed to prevent potential threats. They often highlight unusual behavior or low-level risks that, if left unchecked, could escalate into more significant security issues. Regular monitoring and analysis of these alerts are essential for maintaining robust security.

Search

1`crowdstrike_stream` tag=alert event.SeverityName= LOW 
2| rename event.EndpointIp as src_ip, event.EndpointName as src_host, event.UserName as user, event.IncidentDescription as description, event.IncidentType as type, event.NumbersOfAlerts as count_alerts, event.SeverityName as severity 
3| stats dc(type) as type_count, values(user) as users, values(description) as descriptions, values(type) as types, values(severity) count min(_time) as firstTime max(_time) as lastTime by src_ip src_host 
4| where type_count >= 3 
5| `security_content_ctime(firstTime)` 
6| `security_content_ctime(lastTime)` 
7| `crowdstrike_multiple_low_severity_alerts_filter`

Data Source

No data sources specified for this detection.

Macros Used

Name	Value
crowdstrike_stream	`sourcetype="CrowdStrike:Event:Streams:JSON"`
crowdstrike_multiple_low_severity_alerts_filter	`search *`

crowdstrike_multiple_low_severity_alerts_filter is an empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.

Annotations

- MITRE ATT&CK

+ Kill Chain Phases

+ NIST

+ CIS

- Threat Actors

ID	Technique	Tactic
T1110	Brute Force	Credential Access

KillChainPhase.EXPLOITAITON

NistCategory.DE_AE

Cis18Value.CIS_10

APT28

APT38

APT39

APT41

Agrius

DarkVishnya

Dragonfly

Ember Bear

FIN5

Fox Kitten

HEXANE

OilRig

Turla

Default Configuration

This detection is configured by default in Splunk Enterprise Security to run with the following settings:

Setting	Value
Disabled	true
Cron Schedule	`0 * * * *`
Earliest Time	`-70m@m`
Latest Time	`-10m@m`
Schedule Window	`auto`
Creates Risk Event	True

This configuration file applies to all detections of type anomaly. These detections will use Risk Based Alerting.

Implementation

To implement CrowdStrike stream JSON logs, use the Falcon Streaming API. Set up an API client, authenticate with your CrowdStrike credentials, and subscribe to the "CrowdStrike:Event:Streams:JSON" event stream. Process and store the JSON logs as needed, integrating them into your logging or SIEM system for monitoring and analysis.

Known False Positives

unknown

Associated Analytic Story

Compromised Windows Host

Risk Based Analytics (RBA)

Risk Message	Risk Score	Impact	Confidence
Several LOW severity alerts found in $src_host$	49	70	70

The Risk Score is calculated by the following formula: Risk Score = (Impact * Confidence/100). Initial Confidence and Impact is set by the analytic author.

References

https://www.crowdstrike.com/wp-content/uploads/2022/12/CrowdStrike-Falcon-Event-Streams-Add-on-Guide-v3.pdf

Detection Testing

Test Type	Status	Dataset	Source	Sourcetype
Validation	✅ Passing	N/A	N/A	N/A
Unit	✅ Passing	Dataset	`CrowdStrike:Event:Streams`	`CrowdStrike:Event:Streams:JSON`
Integration	✅ Passing	Dataset	`CrowdStrike:Event:Streams`	`CrowdStrike:Event:Streams:JSON`

Replay any dataset to Splunk Enterprise by using our replay.py tool or the UI. Alternatively you can replay a dataset into a Splunk Attack Range

Source: GitHub | Version: 2