FortiSIEM Rules

Heavy UDP Port Scan: Single Host

Rule ID


Default Status



Detects excessive UDP connections from the same source to many distinct ports on the same destination in a short period of time







Discovery consists of techniques an adversary may use to gain knowledge about the system and internal network. These techniques help adversaries observe the environment and orient themselves before deciding how to act. They also allow adversaries to explore what they can control and what’s around their entry point in order to discover how it could benefit their current objective. Native operating system tools are often used toward this post-compromise information-gathering objective.

MITRE ATT&CK® Techniques


Network Service Scanning

Adversaries may attempt to get a listing of services running on remote hosts, including those that may be vulnerable to remote software exploitation. Methods to acquire this information include port scans and vulnerability scans using tools that are brought onto a system.



Data Source

FortiGate via Syslog or Netflow,Checkpoint via Syslog or Netflow, Palo Alto via Syslog or Netflow



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.

120 seconds

Trigger Conditions

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


SubPattern Definitions

SubPattern Name: Filter1

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

ipProto = 17 AND srcIpPort >= 1024 AND  eventType IN (Group@PH_SYS_EVENT_PermitNetTraffic, Group@PH_SYS_EVENT_NetflowTraffic, Group@PH_SYS_EVENT_BiNetflowTraffic) AND srcIpAddr NOT IN (Group@PH_SYS_APP_ACCELOPS,Group@PH_SYS_DEVICE_FSM) AND srcIpAddr IN (Group@PH_SYS_NETWORK_ENTERPRISE_INTERNAL_NET)

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 (DISTINCT destIpPort) >= 20

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 = Filter1.srcIpAddr,
 destIpAddr = Filter1.destIpAddr,
 incidentCount = Filter1.COUNT (DISTINCT destIpPort)