PH_Rule_Perf_212
Enabled
Detects that interface utilization of a network device has reached a critical level (utilization greater than 50% based on 2 successive readings in a 10 minute interval. IPS devices are excluded since being a sniffing interface, they have high utilization under normal circumstances.
9
Performance
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/TA0040T1498.001
Network Denial of Service: Direct Network Flood
Adversaries may attempt to cause a denial of service (DoS) by directly sending a high-volume of network traffic to a target. Almost any network protocol may be used for flooding. Stateless protocols such as UDP or ICMP are commonly used but stateful protocols such as TCP can be used as well. Botnets are commonly used to conduct network flooding attacks against networks and services. Large botnets can generate a significant amount of traffic from systems spread across the global Internet. In some of the worst cases for distributed DoS (DDoS), so many systems are used to generate the flood that each one only needs to send out a small amount of traffic to produce enough volume to saturate the target network. In such circumstances, distinguishing DDoS traffic from legitimate clients becomes exceedingly difficult.
https://attack.mitre.org/techniques/T1498/001Network
Any Device via SNMP
Correlation
Identify the root cause of the performance issue and allocate more resources if needed.
If the following pattern or patterns match an ingested event within the given time window in seconds, trigger an incident.
600 seconds
If the following defined pattern/s occur within a 600 second time window.
IntfUtilCrit
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 ("PH_DEV_MON_NET_INTF_UTIL","PH_DEV_MON_FORTIGATE_INTF_UTIL","PH_DEV_MON_FORTIAP_INTF_UTIL") AND hostIpAddr IN (Group@PH_SYS_DEVICE_Network) AND hostIpAddr NOT IN (Group@PH_SYS_DEVICE_NETWORK_IPS) AND intfName NOT IN ("lo","Null0")
This defines how matching events are aggregated, only events with the same matching attribute values are grouped into one unique incident ID
hostIpAddr,hostName,intfName
This is most typically a numerical constraint that defines when the rule should trigger an incident
(AVG(inIntfUtil) > DeviceToCMDBAttr(hostIpAddr,intfName,NetIntfUtilThreshCrit) OR AVG(outIntfUtil) > DeviceToCMDBAttr(hostIpAddr,intfName,NetIntfUtilThreshCrit)) AND COUNT(*) >= 2
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 = IntfUtilCrit.hostIpAddr,
hostName = IntfUtilCrit.hostName,
intfName = IntfUtilCrit.intfName,
inIntfUtil = IntfUtilCrit.AVG(inIntfUtil),
outIntfUtil = IntfUtilCrit.AVG(outIntfUtil)