PH_Rule_IPS_ADV_9
Enabled
Detects replay exploits
7
Security
Credential Access
Credential Access consists of techniques for stealing credentials like account names and passwords. Techniques used to get credentials include keylogging or credential dumping. Using legitimate credentials can give adversaries access to systems, make them harder to detect, and provide the opportunity to create more accounts to help achieve their goals.
https://attack.mitre.org/tactics/TA0006T1557.002
Man-in-the-Middle: ARP Cache Poisoning
Adversaries may poison Address Resolution Protocol (ARP) caches to position themselves between the communication of two or more networked devices. This activity may be used to enable follow-on behaviors such as Network Sniffing or Transmitted Data Manipulation. An adversary may passively wait for an ARP request to poison the ARP cache of the requesting device. The adversary may reply with their MAC address, thus deceiving the victim by making them believe that they are communicating with the intended networked device. For the adversary to poison the ARP cache, their reply must be faster than the one made by the legitimate IP address owner. Adversaries may also send a gratuitous ARP reply that maliciously announces the ownership of a particular IP address to all the devices in the local network segment. Adversaries may use ARP cache poisoning as a means to man-in-the-middle (MiTM) network traffic. This activity may be used to collect and/or relay data such as credentials, especially those sent over an insecure, unencrypted protocol.
https://attack.mitre.org/techniques/T1557/002Network
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.
300 seconds
If the following defined pattern/s occur within a 300 second time window.
IPS
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
reptDevIpAddr IN (Group@PH_SYS_DEVICE_NETWORK_IPS) AND eventType IN (Group@PH_SYS_EVENT_ReplayExploit)
This defines how matching events are aggregated, only events with the same matching attribute values are grouped into one unique incident ID
srcIpAddr,destIpAddr,eventType,ipsSignatureId
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
srcIpAddr = IPS.srcIpAddr,
destIpAddr = IPS.destIpAddr,
compEventType = IPS.eventType,
ipsSignatureId = IPS.ipsSignatureId