PH_Rule_Flow_205
Enabled
Detects invalid TCP/UDP traffic with port number 0 (more than 10 in 3 minutes)
9
Security
Command And Control
T1571
Non-Standard Port
Adversaries may communicate using a protocol and port paring that are typically not associated. For example, HTTPS over port 8088 or port 587, as opposed to the traditional port 443. Adversaries may make changes to the standard port used by a protocol to bypass filtering or muddle analysis/parsing of network data.
https://attack.mitre.org/techniques/T1571Network
FortiGate via Syslog or Netflow,Checkpoint via Syslog or Netflow, Palo Alto via Syslog or Netflow
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.
180 seconds
If the following defined pattern/s occur within a 180 second time window.
InvalidTCPUDP
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
(ipProto = 17 OR ipProto = 6) AND destIpPort = 0 AND eventType IN (Group@PH_SYS_EVENT_PermitNetTraffic, Group@PH_SYS_EVENT_NetflowTraffic, Group@PH_SYS_EVENT_BiNetflowTraffic)
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(*) > 10
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 = InvalidTCPUDP.srcIpAddr,
incidentCount = InvalidTCPUDP.COUNT(*)