PH_RULE_DARKSIDE_Traffic_DetectedOutbound
Enabled
Detects if outbound traffic to known malicious IPs associated with DarkSide occurred.
9
Security
Exfiltration
Exfiltration consists of techniques that adversaries may use to steal data from your network. Once they’ve collected data, adversaries often package it to avoid detection while removing it. This can include compression and encryption. Techniques for getting data out of a target network typically include transferring it over their command and control channel or an alternate channel and may also include putting size limits on the transmission.
https://attack.mitre.org/tactics/TA0010T1041
Exfiltration Over C2 Channel
Adversaries may steal data by exfiltrating it over an existing command and control channel. Stolen data is encoded into the normal communications channel using the same protocol as command and control communications.
https://attack.mitre.org/techniques/T1041Network
FortiGate via Syslog or Netflow, Cisco IOS via Syslog or Netflow, Checkpoint via Syslog or Netflow, Palo Alto via Syslog or Netflow
Correlation
Check if the source is patched for the CVE associated with the event. If yes then remove the host from the network and patch immediately. If host is not scanned then determine if the host is running the affected version of the application. If yes then patch immediately, else it is likely a false positive.
If the following pattern or patterns match an ingested event within the given time window in seconds, trigger an incident.
300 seconds
If the following defined pattern/s occur within a 300 second time window.
darkside
This is the named definition of the event query, this is important if multiple subpatterns are defined to distinguish them.
This is the query logic that matches incoming events
destIpAddr IN (176.123.2.216,51.210.138.71,185.105.109.19,192.3.141.157,213.252.247.18,23.95.85.176,159.65.225.72,80.209.241.4,46.166.128.144,108.62.118.232,185.203.116.7,185.203.117.159,104.21.69.79,172.67.206.76,185.203.116.28,198.54.117.197,198.54.117.199,185.243.214.107,45.61.138.171,45.84.0.127,88.85.66.195,139.45.195.28,139.45.195.93,139.45.196.12,139.45.196.74,146.185.16.146,173.192.200.70,173.237.15.140,173.237.15.156,185.225.208.133,193.124.201.171,88.85.66.196,88.85.66.201,88.85.82.153,88.85.82.189,89.19.36.48,139.45.195.149) AND eventType IN (Group@PH_SYS_EVENT_PermitNetTraffic, Group@PH_SYS_EVENT_NetflowTraffic, Group@PH_SYS_EVENT_BiNetflowTraffic,Group@PH_SYS_EVENT_DenyNetTraffic) AND srcIpAddr IN (Group@PH_SYS_NETWORK_ENTERPRISE_INTERNAL_NET)
This defines how matching events are aggregated, only events with the same matching attribute values are grouped into one unique incident ID
srcIpAddr,destIpAddr
This is most typically a numerical constraint that defines when the rule should trigger an incident
COUNT(*) >= 1
This section defines which fields in matching raw events should be mapped to the incident attributes in the resulting incident.
The available raw event attributes to map are limited to the group by attributes and the aggregate event constraint fields for each subpattern
srcIpAddr=darkside.srcIpAddr,
destIpAddr=darkside.destIpAddr