Data Encrypted for Impact T1486
Tactic: Impact
Adversaries may encrypt data on target systems or on large numbers of systems in a network to interrupt availability to system and network resources. They can attempt to render stored data inaccessible by encrypting files or data on local and remote drives and withholding access to a decryption key. This may be done in order to extract monetary compensation from a victim in exchange for decryption or a decryption key (ransomware) or to render data permanently inaccessible in cases where the key is not saved or transmitted.
Events covered
12 catalog events are tagged with this technique by at least one rule.
| Provider | Event | Title |
|---|---|---|
| Sysmon | Event ID 1 | Process creation |
| Sysmon | Event ID 3 | Network connection |
| Sysmon | Event ID 5 | Process terminated |
| Sysmon | Event ID 7 | Image loaded |
| Sysmon | Event ID 11 | FileCreate |
| Security-Auditing | Event ID 4656 | A handle to an object was requested. |
| Security-Auditing | Event ID 4663 | An attempt was made to access an object. |
| Security-Auditing | Event ID 4688 | A new process has been created. |
| Security-Auditing | Event ID 5145 | A network share object was checked to see whether client can be granted desired access. |
| Defender-DeviceFileEvents | FileCreated | File created |
| PowerShell | Event ID 4103 | Payload Context: ContextInfo User Data: UserData. |
| PowerShell | Event ID 4104 | Creating Scriptblock text (MessageNumber of MessageTotal). |
Authoring guide
Patterns shared across the 75 rules above: which fields they filter on, what specific values they look for, and what they exclude. The catalog normalizes field names across vendors so Sigma's Image, Elastic's process.name, and Splunk's process_name collapse into one row. Each rule contributes at most once per row.
Fields filtered most (83 distinct)
The fields most rules look at when detecting this technique. The How column shows the operators authors use (eq, wildcard, regex_match, match) and how often each appears. Sample values are concrete examples to start from, not an exhaustive list.
Top indicator values (376 distinct)
Specific (field, operator, value) combinations the rules check for, ranked by how many rules under this technique use each one. The Corpus reach column counts how many rules across the entire catalog (any technique) check the same combination. High numbers point to widely-used indicators that are likely noisy on their own; combine them with another condition for useful signal. Blank means the combination is specific to rules under this technique. Click a value to expand the rules under this technique that use it.
Exclusions (94 distinct)
Field/operator/value combinations excluded by rules under this technique (top-level not() clauses), sorted by how many rules exclude each. These are the false-positive paths the community has learned to filter out. A new rule that ignores the high-count entries here will likely fire on the same noisy paths. Click a value to expand the rules under this technique that exclude it.
Rules under this technique
Every rule in the catalog tagged with this technique, grouped by vendor. Click a rule title for its full predicates, exclusions, and indicators.
Sigma 19 rules
- Antivirus Ransomware Detection
- AWS EC2 Disable EBS Encryption
- AWS KMS Imported Key Material Usage
- BitLocker feature activation on multiple hosts (native)
- BitLocker feature configuration (Reg via command)
- BitLocker server feature activation (PowerShell)
- BlueSky Ransomware Artefacts
- FunkLocker Ransomware File Creation
- Load Of RstrtMgr.DLL By A Suspicious Process
- Load Of RstrtMgr.DLL By An Uncommon Process
- LockerGoga Ransomware Activity
- macOS Encryption Tool Usage
- Microsoft 365 - Potential Ransomware Activity
- Portable Gpg.EXE Execution
- Potential Conti Ransomware Activity
- Renamed Gpg.EXE Execution
- Suspicious Creation TXT File in User Desktop
- Suspicious Reg Add BitLocker
- WannaCry Ransomware Activity
Elastic 14 rules
- AWS S3 Object Encryption Using External KMS Key
- Deprecated - M365 Security Compliance Potential Ransomware Activity
- Excessive AWS S3 Object Encryption with SSE-C
- Potential AWS S3 Bucket Ransomware Note Uploaded
- Potential Linux Ransomware Note Creation Detected
- Potential Ransomware Behavior - Note Files by System
- Potential Ransomware Note File Dropped via SMB
- PowerShell Script with Encryption/Decryption Capabilities
- Ransomware - Detected - Elastic Defend
- Ransomware - Prevented - Elastic Defend
- Suspicious Data Encryption via OpenSSL Utility
- Suspicious File Renamed via SMB
- Suspicious Renaming of ESXI Files
- Unusual AWS S3 Object Encryption with SSE-C
Splunk 10 rules
- ASL AWS Detect Users creating keys with encrypt policy without MFA
- AWS Detect Users creating keys with encrypt policy without MFA
- AWS Detect Users with KMS keys performing encryption S3
- High Process Termination Frequency
- Ransomware Notes bulk creation
- Ryuk Test Files Detected
- Samsam Test File Write
- Windows .Key File Creation in Root Directory
- Windows BitLocker Suspicious Command Usage
- Windows DiskCryptor Usage
Kusto 18 rules
- Acronis - Multiple Endpoints Infected by Ransomware
- AV detections related to Dev-0530 actors
- AV detections related to Europium actors
- AV detections related to Hive Ransomware
- AV detections related to Zinc actors
- AWSCloudTrail - S3 bucket suspicious ransomware activity
- AWSCloudTrail - Suspicious overly permissive KMS key policy created
- Cisco SE - Ransomware Activity
- Dev-0270 Registry IOC - September 2022
- Dev-0530 File Extension Rename
- Ransom Protect Detected a Ransomware Attack
- Ransom Protect User Blocked
- Ransomware Attack Detected
- Ransomware Client Blocked
- SSG_Security_Incidents
- Trend Micro CAS - Ransomware infection
- Trend Micro CAS - Ransomware outbreak
- Votiro - File Blocked in Email
Panther 14 rules
- AppOmni Alert Passthrough
- AWS EC2 EBS Encryption Disabled
- AWS S3 Object Copied to External Account Bucket
- AWS S3 Object Exfiltration FOLLOWED BY Object Deletion
- Azure Storage Blob CPK Encryption Detected
- Azure Storage Blob Upload FOLLOWED BY CPK Encryption Error
- GCP Cloud Storage Buckets Modified Or Deleted
- GCP GCS Bulk Object Rewrite Operation
- GCP GCS Ransom Note Upload
- GCP KMS Bulk Encryption by GCS Service Account
- GCP KMS Key Granted to GCS Service Account
- GCP KMS Key Version Disabled or Destroyed
- S3 Object Encrypted with External KMS Key
- Slack Potentially Malicious File Shared