Encrypting Files with WinRar or 7z

  1[metadata]
  2creation_date = "2020/12/04"
  3integration = ["endpoint", "windows"]
  4maturity = "production"
  5updated_date = "2024/05/21"
  6
  7[rule]
  8author = ["Elastic"]
  9description = """
 10Identifies use of WinRar or 7z to create an encrypted files. Adversaries will often compress and encrypt data in
 11preparation for exfiltration.
 12"""
 13from = "now-9m"
 14index = ["logs-endpoint.events.process-*", "winlogbeat-*", "logs-windows.*", "endgame-*"]
 15language = "eql"
 16license = "Elastic License v2"
 17name = "Encrypting Files with WinRar or 7z"
 18note = """## Triage and analysis
 19
 20### Investigating Encrypting Files with WinRar or 7z
 21
 22Attackers may compress and/or encrypt data collected before exfiltration. Compressing the data can help obfuscate the collected data and minimize the amount of data sent over the network. Encryption can be used to hide information that is being exfiltrated from detection or make exfiltration less apparent upon inspection by a defender.
 23
 24These steps are usually done in preparation for exfiltration, meaning the attack may be in its final stages.
 25
 26#### Possible investigation steps
 27
 28- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 29- Retrieve the encrypted file.
 30- Investigate other alerts associated with the user/host during the past 48 hours.
 31- Check if the password used in the encryption was included in the command line.
 32- Decrypt the `.rar`/`.zip` and check if the information is sensitive.
 33- If the password is not available, and the format is `.zip` or the option used in WinRAR is not the `-hp`, list the file names included in the encrypted file.
 34- Investigate if the file was transferred to an attacker-controlled server.
 35
 36### False positive analysis
 37
 38- Backup software can use these utilities. Check the `process.parent.executable` and `process.parent.command_line` fields to determine what triggered the encryption.
 39
 40### Response and remediation
 41
 42- Initiate the incident response process based on the outcome of the triage.
 43- Prioritize cases that involve personally identifiable information (PII) or other classified data.
 44- Isolate the involved hosts to prevent further post-compromise behavior.
 45- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
 46- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 47- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
 48- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 49"""
 50references = ["https://www.welivesecurity.com/2020/12/02/turla-crutch-keeping-back-door-open/"]
 51risk_score = 47
 52rule_id = "45d273fb-1dca-457d-9855-bcb302180c21"
 53setup = """## Setup
 54
 55If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
 56events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
 57Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
 58`event.ingested` to @timestamp.
 59For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 60"""
 61severity = "medium"
 62tags = [
 63    "Domain: Endpoint",
 64    "OS: Windows",
 65    "Use Case: Threat Detection",
 66    "Tactic: Collection",
 67    "Resources: Investigation Guide",
 68    "Data Source: Elastic Endgame",
 69    "Data Source: Elastic Defend",
 70]
 71timestamp_override = "event.ingested"
 72type = "eql"
 73
 74query = '''
 75process where host.os.type == "windows" and event.type == "start" and
 76(
 77  (
 78    (
 79      process.name:"rar.exe" or ?process.code_signature.subject_name == "win.rar GmbH" or
 80      ?process.pe.original_file_name == "Command line RAR"
 81    ) and
 82    process.args == "a" and process.args : ("-hp*", "-p*", "/hp*", "/p*")
 83  ) or
 84  (
 85    ?process.pe.original_file_name in ("7z.exe", "7za.exe") and
 86    process.args == "a" and process.args : "-p*"
 87  )
 88) and
 89  not process.parent.executable : (
 90        "C:\\Program Files\\*.exe",
 91        "C:\\Program Files (x86)\\*.exe",
 92        "?:\\ManageEngine\\*\\jre\\bin\\java.exe",
 93        "?:\\Nox\\bin\\Nox.exe"
 94      )
 95'''
 96
 97
 98[[rule.threat]]
 99framework = "MITRE ATT&CK"
100[[rule.threat.technique]]
101id = "T1005"
102name = "Data from Local System"
103reference = "https://attack.mitre.org/techniques/T1005/"
104
105[[rule.threat.technique]]
106id = "T1560"
107name = "Archive Collected Data"
108reference = "https://attack.mitre.org/techniques/T1560/"
109[[rule.threat.technique.subtechnique]]
110id = "T1560.001"
111name = "Archive via Utility"
112reference = "https://attack.mitre.org/techniques/T1560/001/"
113
114
115
116[rule.threat.tactic]
117id = "TA0009"
118name = "Collection"
119reference = "https://attack.mitre.org/tactics/TA0009/"