PH_Rule_TH_ES_WINDOWS_2
Disabled
Detects attempts to resolve SUNBURST Domain which indicates communication attempts to SUNBURST command and Control Servers
9
Security
Command And Control
T1568.001
Dynamic Resolution: Fast Flux DNS
Adversaries may use Fast Flux DNS to hide a command and control channel behind an array of rapidly changing IP addresses linked to a single domain resolution. This technique uses a fully qualified domain name, with multiple IP addresses assigned to it which are swapped with high frequency, using a combination of round robin IP addressing and short Time-To-Live (TTL) for a DNS resource record.
https://attack.mitre.org/techniques/T1568/001Network
Cisco Umbrella via AWS_S3,Cisco Umbrella via HTTPS_ADVANCED (Umbrella API), Windows DNS via FortiSIEM Agent, Windows Sysmon via FortiSIEM Agent, BIND DNS via Syslog, FortiGate via Syslog, FortiProxy via Syslog
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.
Sunburst
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
( eventType IN (Group@PH_SYS_EVENT_CommonDNSTraffic) OR ( destName IS NOT NULL AND eventType REGEXP "FortiGate-|FortiSandbox-|FortiMail-" )) AND destName REGEXP "(.*\.)?(avsvmcloud\.com|databasegalore\.com|deftsecurity\.com|digitalcollege\.org|freescanonline\.com|highdatabase\.com|incomeupdate\.com|panhardware\.com|thedoccloud\.com|virtualdataserver\.com|websitetheme\.com|zupertech\.com)"
This defines how matching events are aggregated, only events with the same matching attribute values are grouped into one unique incident ID
srcIpAddr
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 = Sunburst.srcIpAddr