Service Down: No Response to STM

Rule ID

PH_Rule_No_Service_Response

Default Status

Enabled

Description

Detects a service suddenly went down from up state and is no longer responding to synthetic transaction monitoring probes.

Severity

MITRE ATT&CK® Tactics

Impact

Impact consists of techniques that adversaries use to disrupt availability or compromise integrity by manipulating business and operational processes. Techniques used for impact can include destroying or tampering with data. In some cases, business processes can look fine, but may have been altered to benefit the adversaries’ goals. These techniques might be used by adversaries to follow through on their end goal or to provide cover for a confidentiality breach.

https://attack.mitre.org/tactics/TA0040

MITRE ATT&CK® Techniques

T1499.003

Endpoint Denial of Service: Application Exhaustion Flood

Adversaries may target resource intensive features of web applications to cause a denial of service (DoS). Specific features in web applications may be highly resource intensive. Repeated requests to those features may be able to exhaust system resources and deny access to the application or the server itself.

https://attack.mitre.org/techniques/T1499/003

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

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 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,endUserMonitorName

Aggregate Constraint

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

COUNT(*) >= 2

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

FortiSIEM Rules