PH_Rule_Perf_9
Enabled
Detects high memory usage by a server application on the basis of 3 consecutive measurements in a 15 minute period
8
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.003
Endpoint Denial of Service: Application Exhaustion Flood
Adversaries may target resource intensive features of web applications to cause a denial of service (DoS). Specific features in web applications may be highly resource intensive. Repeated requests to those features may be able to exhaust system resources and deny access to the application or the server itself.
https://attack.mitre.org/techniques/T1499/003Server
Windows Performance Monitoring via OMI or FortiSIEM Agent, Linux via SNMP
Correlation
No remediation guidance specified
If the following pattern or patterns match an ingested event within the given time window in seconds, trigger an incident.
900 seconds
If the following defined pattern/s occur within a 900 second time window.
HighProcessMemory
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_PROC_RESOURCE_UTIL" AND hostIpAddr IN (Group@PH_SYS_DEVICE_Server)
This defines how matching events are aggregated, only events with the same matching attribute values are grouped into one unique incident ID
hostName, hostIpAddr, swProcName
This is most typically a numerical constraint that defines when the rule should trigger an incident
AVG(memUtil) >= DeviceToCMDBAttr(hostIpAddr,swProcName,ProcessMemoryUtilThreshCrit) AND COUNT(*) >= 3
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
hostName = HighProcessMemory.hostName,
hostIpAddr = HighProcessMemory.hostIpAddr,
swProcName = HighProcessMemory.swProcName,
memUtil = HighProcessMemory.AVG(memUtil)