PH_Rule_ADV_21
Enabled
Detects a likely succesful IPS detected exploit (e.g. Buffer overflow, Privilege escalation) optionally preceded by a Reconnaissance and followed by outbound connections and/or excessive scanning
9
Security
Execution
Execution consists of techniques that result in adversary-controlled code running on a local or remote system. Techniques that run malicious code are often paired with techniques from all other tactics to achieve broader goals, like exploring a network or stealing data. For example, an adversary might use a remote access tool to run a PowerShell script that does Remote System Discovery.
https://attack.mitre.org/tactics/TA0002No Technique Specified
Server
FortiGate via Syslog, FortiProxy via Syslog, Checkpoint IPS-1 via LEA/Syslog, PaloAlto PAN-OS via Syslog
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.
600 seconds
If the following defined pattern/s occur within a 600 second time window.
Exploit FOLLOWED_BY Outbound OR Deny
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
Exploit.destIpAddr = Outbound.srcIpAddr AND Exploit.destIpAddr = Deny.srcIpAddr
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_RULE_SYSTEM_EXPLOIT_IPS"
This defines how matching events are aggregated, only events with the same matching attribute values are grouped into one unique incident ID
destIpAddr,eventType,ipsSignatureId
This is most typically a numerical constraint that defines when the rule should trigger an incident
COUNT(*) >= 1
Operator Rank: 1 Operator Type: FOLLOWED_BY
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
destIpAddr NOT IN (Group@PH_SYS_NETWORK_ENTERPRISE_INTERNAL_NET) AND
reptDevIpAddr IN (Group@PH_SYS_DEVICE_FIREWALL) AND destIpPort IN (21,23,80,443)
This defines how matching events are aggregated, only events with the same matching attribute values are grouped into one unique incident ID
srcIpAddr
This is most typically a numerical constraint that defines when the rule should trigger an incident
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 = "PH_RULE_EXCESS_DENY_SRC"
This defines how matching events are aggregated, only events with the same matching attribute values are grouped into one unique incident ID
srcIpAddr
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
destIpAddr = Exploit.destIpAddr,
compEventType = Exploit.eventType,
ipsSignatureId = Exploit.ipsSignatureId