ID | Technique | Tactic |
---|---|---|
T1190 | Exploit Public-Facing Application | Initial Access |
T1210 | Exploitation of Remote Services | Lateral Movement |
T1027 | Obfuscated Files or Information | Defense Evasion |
T1204 | User Execution | Execution |
Detection: Cisco Secure Firewall - Lumma Stealer Activity
Description
This analytic detects Lumma Stealer activity using Cisco Secure Firewall Intrusion Events. It leverages Cisco Secure Firewall Threat Defense IntrusionEvent logs to identify cases where four of the following Snort signature IDs 64793, 64794, 64797, 64798, 64799, 64800, 64801, 62709, 64167, 64168, 64169, 64796, 62710, 62711, 62712, 62713, 62714, 62715, 62716, 62717, 64812, 64810, 64811 occurs in the span of 15 minutes from the same host. If confirmed malicious, this behavior is highly indicative of a successful infection of Lumma Stealer.
Search
1`cisco_secure_firewall` EventType=IntrusionEvent signature_id IN (64793, 64794, 64797, 64798, 64799, 64800, 64801, 62709, 64167, 64168, 64169, 64796, 62710, 62711, 62712, 62713, 62714, 62715, 62716, 62717, 64812, 64810, 64811)
2
3| bin _time span=15m
4
5| fillnull
6
7| stats dc(signature_id) as unique_signature_count
8 values(signature_id) as signature_id
9 values(signature) as signature
10 values(class_desc) as class_desc
11 values(MitreAttackGroups) as MitreAttackGroups
12 values(InlineResult) as InlineResult
13 values(InlineResultReason) as InlineResultReason
14 values(dest_ip) as dest_ip
15 values(dest_port) as dest_port
16 values(rule) as rule
17 values(transport) as transport
18 values(app) as app
19 min(_time) as firstTime
20 max(_time) as lastTime
21 by src_ip
22
23| where unique_signature_count >= 3
24
25| `security_content_ctime(firstTime)`
26
27| `security_content_ctime(lastTime)`
28
29| `cisco_secure_firewall___lumma_stealer_activity_filter`
Data Source
Name | Platform | Sourcetype | Source |
---|---|---|---|
Cisco Secure Firewall Threat Defense Intrusion Event | N/A | 'cisco:sfw:estreamer' |
'not_applicable' |
Macros Used
Name | Value |
---|---|
cisco_secure_firewall | sourcetype="cisco:sfw:estreamer" |
cisco_secure_firewall___lumma_stealer_activity_filter | search * |
cisco_secure_firewall___lumma_stealer_activity_filter
is an empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
Annotations
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 Notable | Yes |
Rule Title | %name% |
Rule Description | %description% |
Notable Event Fields | user, dest |
Creates Risk Event | True |
Implementation
This search requires Cisco Secure Firewall Threat Defense Logs, which
includes the IntrusionEvent EventType. This search uses an input macro named cisco_secure_firewall
.
We strongly recommend that you specify your environment-specific configurations
(index, source, sourcetype, etc.) for Cisco Secure Firewall Threat Defense logs. Replace the macro definition
with configurations for your Splunk environment. The search also uses a post-filter
macro designed to filter out known false positives.
The logs are to be ingested using the Splunk Add-on for Cisco Security Cloud (https://splunkbase.splunk.com/app/7404).
The intrusion access policy must also be configured.
Known False Positives
False positives should be very unlikely.
Associated Analytic Story
Risk Based Analytics (RBA)
Risk Message:
Lumma Stealer Activity on host $dest_ip$ origniating from $src_ip$
Risk Object | Risk Object Type | Risk Score | Threat Objects |
---|---|---|---|
dest_ip | system | 25 | src_ip, signature |
References
Detection Testing
Test Type | Status | Dataset | Source | Sourcetype |
---|---|---|---|---|
Validation | ✅ Passing | N/A | N/A | N/A |
Unit | ✅ Passing | Dataset | not_applicable |
cisco:sfw:estreamer |
Integration | ✅ Passing | Dataset | not_applicable |
cisco:sfw:estreamer |
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: 1