FortiSIEM Online Event Successfully Purged

Rule ID

PH_Rule_Avail_PH_12B

Default Status

Enabled

Description

Detects that FortiSIEM successfully purged online event. This is normal operation when online database gets full and new events need to be accommodated

Severity

MITRE ATT&CK® Tactics

FortiSIEM

MITRE ATT&CK® Techniques

No Technique Specified

Impacts

Internal

Data Source

FortiSIEM Self Monitoring

Detection

Correlation

Remediation Guidance

Identify the root cause and solve the issue

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.

AOPurge

SubPattern Definitions

SubPattern Name: AOPurge

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

phEventCategory = 3 AND eventType IN ("PH_SYSTEM_DISK_PURGING_FINISHED","PH_ES_HOT_STORAGE_PURGING_FINISHED","PH_ES_WARM_STORAGE_PURGING_FINISHED","PH_ES_COLD_STORAGE_PURGING_FINISHED", "PH_ES_ARCHIVE_STORAGE_PURGING_FINISHED") AND totBytes64 > 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

eventType

Aggregate Constraint

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

COUNT (*) >= 1 AND AVG(totBytes64) > 0

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

 compEventType = AOPurge.eventType,
 totBytes64 = AOPurge.AVG(totBytes64)

FortiSIEM Rules