PH_Rule_IPS_15
Enabled
Detects high severity website defacement attack
9
Security
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/TA0040T1491.001
Defacement: Internal Defacement
An adversary may deface systems internal to an organization in an attempt to intimidate or mislead users. This may take the form of modifications to internal websites, or directly to user systems with the replacement of the desktop wallpaper. Since internally defacing systems exposes an adversary's presence, it often takes place after other intrusion goals have been accomplished.
https://attack.mitre.org/techniques/T1491/001T1491.002
Defacement: External Defacement
An adversary may deface systems external to an organization in an attempt to deliver messaging, intimidate, or otherwise mislead an organization or users. Externally-facing websites are a common victim of defacement; often targeted by adversary and hacktivist groups in order to push a political message or spread propaganda. Website defacement may also be used as setup, or a precursor, for future attacks such as Drive-by Compromise.
https://attack.mitre.org/techniques/T1491/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.
WebDefacement
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 (Group@PH_SYS_EVENT_WebsiteDefacementAttack)
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 = WebDefacement.srcIpAddr,
destIpAddr = WebDefacement.destIpAddr,
compEventType = WebDefacement.eventType,
ipsSignatureId = WebDefacement.ipsSignatureId