FortiSIEM Rules

Service Staying Down: No Response to STM: Has IP

Rule ID

PH_Rule_Cont_No_Service_Response_IP

Default Status

Disabled

Description

Detects a service staying down - that is went from up to down and did not come up and is no longer responding to end user monitoring probes. This service has well known IP address.

Severity

8

Category

Availability

MITRE ATT&CK® Tactics

Application

MITRE ATT&CK® Techniques

No Technique Specified

Impacts

Application

Data Source

Any Device via STM 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.

AppDown NOT_FOLLOWED_BY AppUp

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

AppUp.hostName = AppDown.hostName AND AppUp.hostIpAddr = AppDown.hostIpAddr AND AppUp.endUserMonitorName = AppDown.endUserMonitorName

SubPattern Definitions

SubPattern Name: AppDown

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_DEV_MON_EUM_FAIL" AND hostIpAddr IS NOT NULL

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

hostName,hostIpAddr,endUserMonitorName

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

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_DEV_MON_EUM_SUCCESS"

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

hostName,hostIpAddr,endUserMonitorName

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=AppDown.hostName,
hostIpAddr=AppDown.hostIpAddr,
endUserMonitorName=AppDown.endUserMonitorName