IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.
« Unusual Persistence via Services Registry Unusual Process Execution Path - Alternate Data Stream »
Elastic Docs ›Elastic Security Solution [7.11] ›Detections and Alerts ›Prebuilt rule reference

Unusual Process Execution - Temp

edit

Unusual Process Execution - Temp

edit

Identifies processes running in a temporary folder. This is sometimes done by adversaries to hide malware.

Rule type: query

Rule indices:

  • auditbeat-*
  • 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
  • Linux
  • Threat Detection

Version: 6 (version history)

Added (Elastic Stack release): 7.6.0

Last modified (Elastic Stack release): 7.11.2

Rule authors: Elastic

Rule license: Elastic License

Potential false positives

edit

Build systems, like Jenkins, may start processes in the /tmp directory. These can be exempted by name or by username.

Rule query

edit
event.category:process and event.type:(start or process_started) and
process.working_directory:/tmp

Rule version history

edit
Version 6 (7.11.2 release)
  • Formatting only
Version 5 (7.10.0 release)
  • Formatting only
Version 4 (7.9.1 release)
  • Formatting only
Version 3 (7.9.0 release)

  • Updated query, changed from:

    process.working_directory:/tmp and event.action:executed
Version 2 (7.7.0 release)

  • Updated query, changed from:

    process.working_directory: /tmp and event.action:executed
« Unusual Persistence via Services Registry Unusual Process Execution Path - Alternate Data Stream »