FortiSIEM Rules

High Severity Outbound Permitted IPS Exploit

Rule ID


Default Status



Detects a high severity IPS exploit detected by IPS - - from internal networks permitted to external network







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.

MITRE ATT&CK® Techniques

No Technique Specified



Data Source

FortiGate via Syslog, FortiProxy via Syslog, Checkpoint IPS-1 via LEA/Syslog, PaloAlto PAN-OS via Syslog



Remediation Guidance

No remediation guidance specified

Time Window

If the following pattern or patterns match an ingested event within the given time window in seconds, trigger an incident.

300 seconds

Trigger Conditions

If the following defined pattern/s occur within a 300 second time window.


SubPattern Definitions

SubPattern Name: NonCiscoIPSHighSev

This is the named definition of the event query, this is important if multiple subpatterns are defined to distinguish them.

SubPattern Query

This is the query logic that matches incoming events

(eventType CONTAIN "Checkpoint-ips" OR eventType CONTAIN "Cisco_IPS" OR
	  eventType CONTAIN "Corero-SmartWall" OR eventType CONTAIN "FortiGate-ips" OR
	  eventType CONTAIN "Juniper_IDP" OR eventType CONTAIN "McAfee-Intrushield" OR
	  eventType CONTAIN "Sophos-UTM-Intrusion" OR eventType CONTAIN "Forcepoint-NGFW-" OR
	  eventType CONTAIN "Snort-") AND eventSeverity >= 8 AND
          srcIpAddr IN (Group@PH_SYS_NETWORK_ENTERPRISE_INTERNAL_NET) AND eventAction = 0

Group by Attributes

This defines how matching events are aggregated, only events with the same matching attribute values are grouped into one unique incident ID


Aggregate Constraint

This is most typically a numerical constraint that defines when the rule should trigger an incident

COUNT(*) >= 1

Incident Attribute Mapping

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 = NonCiscoIPSHighSev.srcIpAddr,
 compEventType = NonCiscoIPSHighSev.eventType,
 attackName = NonCiscoIPSHighSev.attackName,
 destIpAddr = NonCiscoIPSHighSev.destIpAddr,
 ipsSignatureId = NonCiscoIPSHighSev.ipsSignatureId,
 incidentCount = NonCiscoIPSHighSev.COUNT(*)