PH_Rule_No_Response_To_Ping_Net
Enabled
Detects a device does not respond to ping - 10 out of 10 ping packets are lost - either the host is down or there is a routing problem
7
Availability
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/TA0040T1529
System Shutdown/Reboot
Adversaries may shutdown/reboot systems to interrupt access to, or aid in the destruction of, those systems.
https://attack.mitre.org/techniques/T1529Network
Any Device via Ping Monitoring
Correlation
Identify the root cause and solve the issue
If the following pattern or patterns match an ingested event within the given time window in seconds, trigger an incident.
120 seconds
If the following defined pattern/s occur within a 120 second time window.
AllPingLossNet OR SystemShutdown
This defines how two or more distinct events are related in a time-series based action. e.g. An event occurs followed by another event if the source IP, user, and messageId are the same
AllPingLossNet.hostIpAddr = SystemShutdown.reptDevIpAddr
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_DEV_MON_PING_STAT" AND hostIpAddr IN (Group@PH_SYS_DEVICE_Network)
This defines how matching events are aggregated, only events with the same matching attribute values are grouped into one unique incident ID
hostIpAddr,hostName
This is most typically a numerical constraint that defines when the rule should trigger an incident
AVG(pktLossPct) = 100 AND COUNT(*) >= 1
Operator Rank: 0 Operator Type: OR
This operator defines the logic condition relating to the prior event subpattern clause and the following event subpattern clause
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_SystemShutdown) AND reptDevIpAddr IN (Group@PH_SYS_DEVICE_Network)
This defines how matching events are aggregated, only events with the same matching attribute values are grouped into one unique incident ID
reptDevIpAddr,reptDevName
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
hostIpAddr = AllPingLossNet.hostIpAddr,
hostIpAddr = SystemShutdown.reptDevIpAddr,
hostName = AllPingLossNet.hostName,
hostName = SystemShutdown.reptDevName