FortiSIEM Rules

ES Coordinator Node Staying Down

Rule ID

PH_Rule_Avail_69

Default Status

Enabled

Description

Detects that an ES Coordinator node stays down - that is didn't come up within 5 minutes of going down

Severity

9

Category

Availability

MITRE ATT&CK® Tactics

Network

MITRE ATT&CK® Techniques

No Technique Specified

Impacts

Network

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.

300 seconds

Trigger Conditions

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

CODown NOT_FOLLOWED_BY COUp

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

CODown.destName = COUp.destName

SubPattern Definitions

SubPattern Name: CODown

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 = "PH_DATA_CLUSTER_COORDINATOR_DOWN"

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

destName

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: NOT_FOLLOWED_BY

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

SubPattern Name: COUp

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 = "PH_DATA_CLUSTER_COORDINATOR_UP"

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

destName

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

 hostName = CODown.destName