FortiSIEM Rules

P2P traffic consuming high network bandwidth

Rule ID

PH_Rule_PolicyViolation_2

Default Status

Enabled

Description

Network IPS detected P2P traffic and the source IP is also sending/receiving excessive traffic exceeding 5MB over a 10 minute window

Severity

7

Category

Security

MITRE ATT&CK® Tactics

Policy Violation

MITRE ATT&CK® Techniques

No Technique Specified

Impacts

Application

Data Source

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

Detection

Correlation

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.

600 seconds

Trigger Conditions

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

P2P AND ExcessiveBytes

Global Constraint

This defines how two or more distinct events are related in a time-series based action. e.g. An event occurs followed by another event if the source IP, user, and messageId are the same

P2P.srcIpAddr = ExcessiveBytes.srcIpAddr

SubPattern Definitions

SubPattern Name: P2P

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

(reptDevIpAddr IN (Group@PH_SYS_DEVICE_NETWORK_IPS) OR (reptDevIpAddr IN (Group@PH_SYS_APP_NETWORK_IPS) AND eventType CONTAIN "Snort-")) AND  eventType IN (Group@PH_SYS_EVENT_P2PTraffic)

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

srcIpAddr

Aggregate Constraint

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

COUNT(*) >= 1
Operator Rank: 0 Operator Type: AND

This operator defines the logic condition relating to the prior event subpattern clause and the following event subpattern clause

SubPattern Name: ExcessiveBytes

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 IN (Group@PH_SYS_EVENT_PermitNetTraffic, Group@PH_SYS_EVENT_NetflowTraffic, Group@PH_SYS_EVENT_BiNetflowTraffic)

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

srcIpAddr

Aggregate Constraint

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

SUM(totBytes64) >= 5242880

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 = P2P.srcIpAddr