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
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 and Disk Structure Wipe 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, OS Credential Dumping, and SMB/Windows Admin Shares..
In cloud environments, adversaries may leverage access to delete cloud storage, cloud storage accounts, machine images, and other infrastructure crucial to operations to damage an organization or their customers.
HermeticWiper can recursively wipe folders and files in
Consider implementing IT disaster recovery plans that contain procedures for taking regular data backups that can be used to restore organizational data. Ensure backups are stored off system and is protected from common methods adversaries may use to gain access and destroy the backups to prevent recovery.
|ID||Data Source||Data Component||Detects|
|DS0010||Cloud Storage||Cloud Storage Deletion||
Monitor for unexpected deletion of a cloud storage infrastructure, such as the
Monitor executed commands and arguments for binaries that could be involved in data destruction activity, such as SDelete.
Monitor for unexpected deletion to a file (ex: Sysmon EID 23)
Monitor for changes made to a large quantity of files for unexpected modifications in user directories and under C:\Windows\System32.
Monitor for unexpected deletion of a virtual machine image (ex: Azure Compute Service Images DELETE)
Monitor for unexpected deletion of an instance (ex: instance.delete within GCP Audit Logs)
Monitor for newly executed processes of binaries that could be involved in data destruction activity, such as SDelete.
Monitor for unexpected deletion of a snapshot (ex: AWS delete-snapshot)
Monitor for unexpected deletion of a cloud volume (ex: AWS delete-volume)