Database DDL changes

Rule ID

PH_Rule_Change_20

Default Status

Enabled

Description

Detects database DDL changes

Severity

MITRE ATT&CK® Tactics

Audit

MITRE ATT&CK® Techniques

No Technique Specified

Impacts

Application

Data Source

Oracle Database Server via JDBC, Microsoft SQL Server via JDBC, IBM DB2 via JDBC

Detection

Correlation

Remediation Guidance

Make sure it is an authorized change

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.

DBChange

SubPattern Definitions

SubPattern Name: DBChange

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 IN (Group@PH_SYS_EVENT_DatabaseChange)  AND eventType NOT CONTAIN "user"

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

reptDevName,reptDevIpAddr,eventType

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 = DBChange.reptDevName,
 hostIpAddr = DBChange.reptDevIpAddr,
 compEventType = DBChange.eventType

FortiSIEM Rules