Data Destruction
Sub-techniques (4)
Adversaries may destroy data and files on specific systems or in large numbers on a network to interrupt availability to systems, services, and network resources. Data destruction is likely to render stored data irrecoverable by forensic techniques through overwriting files or data on local and remote drives. Common operating system file deletion commands such as del
and rm
often only remove pointers to files without wiping the contents of the files themselves, making the files recoverable by proper forensic methodology. This behavior is distinct from
Disk Content Wipe [MITRE]
and
Disk Structure Wipe [MITRE]
because individual files are destroyed rather than sections of a storage disk or the disk's logical structure.
Adversaries may attempt to overwrite files and directories with randomly generated data to make it irrecoverable. In some cases politically oriented image files have been used to overwrite data.
To maximize impact on the target organization in operations where network-wide availability interruption is the goal, malware designed for destroying data may have worm-like features to propagate across a network by leveraging additional techniques like
Valid Accounts [MITRE]
,
OS Credential Dumping [MITRE]
, and
SMB/Windows Admin Shares [MITRE]
..
In cloud environments, adversaries may leverage access to delete cloud storage, cloud storage accounts, machine images, database instances, and other infrastructure crucial to operations to damage an organization or their customers.
Detection
Use process monitoring to monitor the execution and command-line parameters of binaries that could be involved in data destruction activity, such as [SDelete](https://attack.mitre.org/software/S0195). Monitor for the creation of suspicious files as well as high unusual file modification activity. In particular, look for large quantities of file modifications in user directories and underC:\Windows\System32\
.
In cloud environments, the occurrence of anomalous high-volume deletion events, such as the DeleteDBCluster
and DeleteGlobalCluster
events in AWS, or a high quantity of data deletion events, such as DeleteBucket
, within a short period of time may indicate suspicious activity.
ID | Data Source | Data Component | Description |
---|---|---|---|
DS0030 | Instance | Instance Deletion | Monitor for unexpected deletion of an instance (ex: instance.delete within GCP Audit Logs), DeleteDBInstance in AWS) |
DS0020 | Snapshot | Snapshot Deletion | Monitor for unexpected deletion of a snapshot (ex: AWS DeleteSnapshot, DeleteDBSnapshot) |