PH_RULE_ICS_Execution_through_API
Enabled
An ICS monitoring system has detected an event containing MITRE ICS Technique ID T0871 - Execution through API. Adversaries may attempt to leverage Application Program Interfaces (APIs) used for communication between control software and the hardware.
8
Security
Execution ICS
Network
Dragos Platform via Syslog and Nozomi SCADA Guardian/CMC via NOZOMI_API
Correlation
Investigate the source, and determine if the event was legitimate.
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.
mitre_ics_event
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 CONTAIN "FortiDeceptor-" OR eventType CONTAIN "Dragos-" OR eventType CONTAIN "Nozomi-") AND attackTechniqueId REGEXP "^(T\d+,)*T0871(,T\d+)*$"
This defines how matching events are aggregated, only events with the same matching attribute values are grouped into one unique incident ID
srcIpAddr,destIpAddr,eventType
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
compEventType=mitre_ics_event.eventType,
srcIpAddr=mitre_ics_event.srcIpAddr,
destIpAddr=mitre_ics_event.destIpAddr,
incidentCount=mitre_ics_event.COUNT(*)