SQL Server Excessive Page Read/Write

Rule ID

PH_Rule_DB_4

Default Status

Enabled

Description

Detects excessive SQL Server page read/write ( larger than 90 over 2 succesive readings)

Severity

MITRE ATT&CK® Tactics

Database

MITRE ATT&CK® Techniques

No Technique Specified

Impacts

Application

Data Source

MS SQL Server

Detection

Correlation

Remediation Guidance

Identify the root cause of the performance issue and allocate more resources if needed.

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.

ExcessPageRW

SubPattern Definitions

SubPattern Name: ExcessPageRW

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

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

Aggregate Constraint

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

COUNT (*) >= 2 AND (AVG(dbPageReadsPerSec) >= 90 OR AVG(dbPageWritesPerSec) >= 90)

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 = ExcessPageRW.hostName,
 instanceName = ExcessPageRW.instanceName,
 dbPageReadsPerSec = ExcessPageRW.AVG(dbPageReadsPerSec),
 dbPageWritesPerSec = ExcessPageRW.AVG(dbPageWritesPerSec)

FortiSIEM Rules