PH_RULE_RANSOMWARE_OUTBREAK_DETECTED
Enabled
Identifies ransomware detected on more than 10 hosts in a 30 minute window.
10
Security
Impact
Impact consists of techniques that adversaries use to disrupt availability or compromise integrity by manipulating business and operational processes. Techniques used for impact can include destroying or tampering with data. In some cases, business processes can look fine, but may have been altered to benefit the adversaries’ goals. These techniques might be used by adversaries to follow through on their end goal or to provide cover for a confidentiality breach.
https://attack.mitre.org/tactics/TA0040T1486
Data Encrypted for Impact
Adversaries may encrypt data on target systems or on large numbers of systems in a network to interrupt availability to system and network resources. They can attempt to render stored data inaccessible by encrypting files or data on local and remote drives and withholding access to a decryption key. This may be done in order to extract monetary compensation from a victim in exchange for decryption or a decryption key (ransomware) or to render data permanently inaccessible in cases where the key is not saved or transmitted.
https://attack.mitre.org/techniques/T1486Server
Windows Security Log via OMI or FortiSIEM Agent
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.
1800 seconds
If the following defined pattern/s occur within a 1800 second time window.
Filter
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 = "PH_RULE_RANSOMWARE_DETECTED"
This defines how matching events are aggregated, only events with the same matching attribute values are grouped into one unique incident ID
procName
This is most typically a numerical constraint that defines when the rule should trigger an incident
COUNT(DISTINCT hostName) >= 10
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
procName = Filter.procName