IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.
« Process Injection by the Microsoft Build Engine Program Files Directory Masquerading »
Elastic Docs ›Elastic Security Solution [7.16] ›Detections and alerts ›Prebuilt rule reference

Process Termination followed by Deletion

edit

Process Termination followed by Deletion

edit

Identifies a process termination event quickly followed by the deletion of its executable file. Malware tools and other non-native files dropped or created on a system by an adversary may leave traces to indicate to what occurred. Removal of these files can occur during an intrusion, or as part of a post-intrusion process to minimize the adversary’s footprint.

Rule type: eql

Rule indices:

  • logs-endpoint.events.*

Severity: medium

Risk score: 47

Runs every: 5 minutes

Searches indices from: now-9m (Date Math format, see also Additional look-back time)

Maximum alerts per execution: 100

Tags:

  • Elastic
  • Host
  • Windows
  • Threat Detection
  • Defense Evasion

Version: 3 (version history)

Added (Elastic Stack release): 7.11.0

Last modified (Elastic Stack release): 7.16.0

Rule authors: Elastic

Rule license: Elastic License v2

Rule query

edit
sequence by host.id with maxspan=5s [process where event.type ==
"end" and process.code_signature.trusted == false and not
process.executable : ("C:\\Windows\\SoftwareDistribution\\*.exe",
"C:\\Windows\\WinSxS\\*.exe") ] by process.executable [file
where event.type == "deletion" and file.extension : ("exe", "scr",
"com")] by file.path

Threat mapping

edit

Framework: MITRE ATT&CKTM

Rule version history

edit
Version 3 (7.16.0 release)
  • Formatting only
Version 2 (7.12.0 release)
  • Formatting only
« Process Injection by the Microsoft Build Engine Program Files Directory Masquerading »