PH_Rule_Cylance_8
Enabled
This rule detects Cylance threat changes
7
Change
Execution
Execution consists of techniques that result in adversary-controlled code running on a local or remote system. Techniques that run malicious code are often paired with techniques from all other tactics to achieve broader goals, like exploring a network or stealing data. For example, an adversary might use a remote access tool to run a PowerShell script that does Remote System Discovery.
https://attack.mitre.org/tactics/TA0002No Technique Specified
Other
Cylance Protect via Syslog
Correlation
Make sure it is an authorized change
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.
Threat_Changed
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 = "CylanceProtect-Threat-threat_changed"
This defines how matching events are aggregated, only events with the same matching attribute values are grouped into one unique incident ID
hostName,fileName,filePath,hashCode,threatScore
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
hostName = Threat_Changed.hostName,
fileName = Threat_Changed.fileName,
filePath = Threat_Changed.filePath,
hashCode = Threat_Changed.hashCode,
threatScore = Threat_Changed.threatScore