PH_Rule_Excessive_ICMP_Unreachables
Enabled
Detects an usually high frequency of ICMP destination unreachable packets between the same source and destination - this indicates routing error
6
Availability
Network
No Technique Specified
Network
FortiGate via Syslog or Netflow, Checkpoint via Syslog or Netflow, Palo Alto via Syslog or Netflow
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.
300 seconds
If the following defined pattern/s occur within a 300 second time window.
ExcessICMPUnreach
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
ipProto = 1 AND icmpType = 3 AND eventType IN (Group@PH_SYS_EVENT_PermitNetTraffic, Group@PH_SYS_EVENT_NetflowTraffic, Group@PH_SYS_EVENT_BiNetflowTraffic, Group@PH_SYS_EVENT_DenyNetTraffic) AND srcIpAddr NOT IN (Group@PH_SYS_APP_ACCELOPS,Group@PH_SYS_DEVICE_FSM)
This defines how matching events are aggregated, only events with the same matching attribute values are grouped into one unique incident ID
srcIpAddr, destIpAddr
This is most typically a numerical constraint that defines when the rule should trigger an incident
COUNT (*) >= 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
srcIpAddr = ExcessICMPUnreach.srcIpAddr,
destIpAddr =ExcessICMPUnreach.destIpAddr