PH_Rule_IPSLA_2
Enabled
Detects IPSLA HTTP failures or response time more than 50msec or more than 3 failures in 10 minutes
7
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/TA0040T1499.002
Endpoint Denial of Service: Service Exhaustion Flood
Adversaries may target the different network services provided by systems to conduct a DoS. Adversaries often target DNS and web services, however others have been targeted as well. One example of this type of attack is known as a simple HTTP flood, where an adversary sends a large number of HTTP requests to a web server to overwhelm it and/or an application that runs on top of it. Another variation, known as a SSL renegotiation attack, the adversary establishes a SSL/TLS connection and then proceeds to make a series of renegotiation requests. Because the cryptographic renegotiation has a meaningful cost in computation cycles, this can cause an impact to the availability of the service when done in volume.
https://attack.mitre.org/techniques/T1499/002Network
Cisco IOS IPSLA Monitoring via SNMP
Correlation
Identify the root cause of the network laatency issue. May be caused by L3 routing or L2 bridging configuration issues.
If the following pattern or patterns match an ingested event within the given time window in seconds, trigger an incident.
600 secondsIf the following defined pattern/s occur within a 600 second time window.
HighRespTime OR DropThis 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
HighRespTime.reptDevName = Drop.reptDevName AND HighRespTime.srcIpAddr = Drop.srcIpAddr AND HighRespTime.srcName = Drop.srcName AND HighRespTime.destIpAddr = Drop.destIpAddrThis 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_IPSLA_HTTP_MET"This defines how matching events are aggregated, only events with the same matching attribute values are grouped into one unique incident ID
reptDevName,srcIpAddr,srcName,destIpAddrThis is most typically a numerical constraint that defines when the rule should trigger an incident
AVG(httpResponseTimeMs) > 50 AND COUNT(*) >= 3Operator Rank: 0 Operator Type: ORThis 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 = "PH_DEV_MON_IPSLA_HTTP_MET" AND httpStatusCode != 1This defines how matching events are aggregated, only events with the same matching attribute values are grouped into one unique incident ID
reptDevName,srcIpAddr,srcName,destIpAddrThis is most typically a numerical constraint that defines when the rule should trigger an incident
COUNT(*) >= 3This 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
destName = HighRespTime.reptDevName,
srcIpAddr = HighRespTime.srcIpAddr,
srcName = HighRespTime.srcName,
destIpAddr = HighRespTime.destIpAddr