Response playbooks, investigation guides, and Atomic Red Team tests are Pro-only. Upgrade to unlock the full detection package for THREAT-Impact-ProductionDatabaseRecordTampering.

Upgrade to Pro
THREAT-Impact-ProductionDatabaseRecordTampering

Stored Data Manipulation — Unauthorized Bulk Modification of Production Database Records

Impact Last updated:

Unlike destruction or encryption, stored data manipulation (T1565.001) is a stealthy Impact objective: the adversary alters records in place — falsifying financial transactions, backdating timestamps, adjusting inventory or pricing data, or planting false log entries — specifically so the tampering is not immediately obvious and can influence downstream business decisions, financial reporting, or an investigation. Because the goal is integrity compromise rather than availability loss, the data remains accessible and the application keeps functioning normally, which means traditional outage-based monitoring never fires. The most reliable detection surface is the database's own audit log: a spike in UPDATE/DELETE statement volume from a single principal against production tables, especially when that principal is a service account not normally used for ad hoc interactive queries, or when the activity occurs outside any tracked change-management window. A second useful signal is direct execution of interactive query tools (ssms.exe, azuredatastudio.exe, mysql.exe, psql.exe) by a service account that should only ever connect programmatically — a strong indicator that stolen service-account credentials are being used for manual, off-process data tampering rather than application logic performing routine writes.

What is THREAT-Impact-ProductionDatabaseRecordTampering Stored Data Manipulation — Unauthorized Bulk Modification of Production Database Records?

Stored Data Manipulation — Unauthorized Bulk Modification of Production Database Records (THREAT-Impact-ProductionDatabaseRecordTampering) maps to the Impact tactic — the adversary is trying to manipulate, interrupt, or destroy your systems and data in MITRE ATT&CK.

This page provides production-ready detection logic for Stored Data Manipulation — Unauthorized Bulk Modification of Production Database Records, covering the data sources and telemetry it touches: Azure SQL Database Auditing (AzureDiagnostics, category SQLSecurityAuditEvents), Microsoft Defender for Endpoint (DeviceProcessEvents), On-prem SQL Server Audit / Extended Events (equivalent fields for non-Azure deployments). The queries below are rated high severity at medium confidence, and ship for 7 SIEM platforms — KQL, SPL, Elastic, QRadar, Sumo, YARA-L, LogScale.

MITRE ATT&CK

Tactic
Impact
Microsoft Sentinel / Defender
kusto
// THREAT: Stored data manipulation - anomalous bulk UPDATE/DELETE volume + service-account interactive tooling (T1565.001)
// Requires Azure SQL Database Auditing ingested into AzureDiagnostics (category SQLSecurityAuditEvents)
let LookbackWindow = 1h;
let BulkWriteThreshold = 100; // UPDATE/DELETE statements from one principal in the window
let KnownServiceAccounts = dynamic(["svc_appserver", "svc_etl", "svc_reporting"]); // populate with legitimate application/ETL service principals
// Signal 1: bulk UPDATE/DELETE volume spike from a single principal against production tables
let BulkWriteSpike = AzureDiagnostics
| where Category == "SQLSecurityAuditEvents"
| where TimeGenerated > ago(LookbackWindow)
| where action_name_s in ("UPDATE", "DELETE", "BATCH UPDATE", "BATCH DELETE")
| summarize WriteCount=count(), TablesTouched=make_set(object_name_s, 20) by server_principal_name_s, database_name_s, bin(TimeGenerated, 15m)
| where WriteCount >= BulkWriteThreshold
| extend Indicator = "BulkUpdateDeleteVolumeSpike"
| extend RiskScore = iff(server_principal_name_s !in~ (KnownServiceAccounts), 90, 70)
| project TimeGenerated, server_principal_name_s, database_name_s, WriteCount, TablesTouched, Indicator, RiskScore;
// Signal 2: service account launching an interactive DB query tool (indicates manual, off-process access)
let ServiceAccountInteractiveTool = DeviceProcessEvents
| where Timestamp > ago(LookbackWindow)
| where FileName in~ ("ssms.exe", "azuredatastudio.exe", "mysql.exe", "psql.exe", "dbeaver.exe")
| where AccountName in~ (KnownServiceAccounts)
| extend Indicator = "ServiceAccountLaunchedInteractiveQueryTool"
| extend RiskScore = 85
| project Timestamp, DeviceName, AccountName, FileName, ProcessCommandLine, Indicator, RiskScore;
union BulkWriteSpike, ServiceAccountInteractiveTool
| sort by RiskScore desc, TimeGenerated desc

Two-signal detection for stored data manipulation. Signal 1 aggregates Azure SQL Database audit events (SQLSecurityAuditEvents) by principal and database in 15-minute bins, flagging any principal issuing 100+ UPDATE/DELETE/BATCH statements — a volume anomaly inconsistent with normal application write patterns — with elevated risk when the principal is not on the known-service-account allowlist. Signal 2 flags a known service account launching an interactive database query GUI/CLI tool, which application service accounts have no legitimate reason to do, indicating the credential is being used manually rather than by its owning application.

high severity medium confidence

Data Sources

Azure SQL Database Auditing (AzureDiagnostics, category SQLSecurityAuditEvents) Microsoft Defender for Endpoint (DeviceProcessEvents) On-prem SQL Server Audit / Extended Events (equivalent fields for non-Azure deployments)

Required Tables

AzureDiagnostics DeviceProcessEvents

False Positives

  • Legitimate bulk data operations: month-end batch jobs, data migrations, ETL reprocessing, or scheduled cleanup jobs — exclude known batch-job service principals and their documented execution windows
  • Database administrators using SSMS/Azure Data Studio for legitimate maintenance under their own named account rather than a service account (this detection specifically targets service-account use of interactive tools, not DBA activity under personal accounts)
  • Application deployment/migration tooling that legitimately runs large schema or data updates during a release window
  • Reporting or analytics service accounts with unusually high but legitimate read-heavy query volume (this detection targets write volume, not reads, to minimize this overlap)

Sigma rule & cross-platform mapping

The detection logic for Stored Data Manipulation — Unauthorized Bulk Modification of Production Database Records (THREAT-Impact-ProductionDatabaseRecordTampering) above is provided in a vendor-neutral form so you can deploy it on any SIEM. The same logic is shipped here as native KQL (Microsoft Sentinel / Defender), SPL (Splunk), Elastic (Elastic Security (EQL)), QRadar (IBM QRadar (AQL)), Sumo (Sumo Logic CSE), YARA-L (Google Chronicle / SecOps), LogScale (CrowdStrike LogScale (CQL)) queries. In Sigma terms, this detection targets the following logsource:

logsource:
  category: process_creation
  product: windows

Browse the community-maintained Sigma rules for this technique:


Testing Methodology

Validate this detection against 2 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.

  1. Test 1Simulate Bulk UPDATE Volume Spike

    Expected signal: Azure SQL/SQL Server audit log shows 120 UPDATE statements from the svc_test principal against TestTable within a 15-minute window.

  2. Test 2Simulate Service Account Launching Interactive Query Tool

    Expected signal: DeviceProcessEvents shows ssms.exe launched with AccountName=svc_appserver.

Unlock playbooks & atomic tests with Pro

Get the full detection package for THREAT-Impact-ProductionDatabaseRecordTampering — response playbook and atomic red team tests, plus investigation guidance and hunting queries.

df00tech Pro — £29/user/month

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections

Tactic Hub

Detection Variants (1)

Different telemetry and tradecraft for the same technique — pick the one that matches the data you collect.