SQL Server Excessive Full Scan

Rule ID

PH_Rule_DB_8

Default Status

Enabled

Description

Detects excessive SQL Server full scan (greater than 1000 per second)

Severity

MITRE ATT&CK® Tactics

Discovery

Discovery consists of techniques an adversary may use to gain knowledge about the system and internal network. These techniques help adversaries observe the environment and orient themselves before deciding how to act. They also allow adversaries to explore what they can control and what’s around their entry point in order to discover how it could benefit their current objective. Native operating system tools are often used toward this post-compromise information-gathering objective.

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

MITRE ATT&CK® Techniques

T1046

Network Service Scanning

Adversaries may attempt to get a listing of services running on remote hosts, including those that may be vulnerable to remote software exploitation. Methods to acquire this information include port scans and vulnerability scans using tools that are brought onto a system.

https://attack.mitre.org/techniques/T1046

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.

ExcessScan

SubPattern Definitions

SubPattern Name: ExcessScan

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(dbFullScansPerSec) > 1000

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 = ExcessScan.hostName,
 instanceName = ExcessScan.instanceName,
 dbFullScansPerSec = ExcessScan.AVG(dbFullScansPerSec)

FortiSIEM Rules