Microsoft Build Engine Started by a Script Process

edit

Microsoft Build Engine Started by a Script Process

edit

An instance of MSBuild, the Microsoft Build Engine, was started by a script or the Windows command interpreter. This behavior is unusual and is sometimes used by malicious payloads.

Rule type: query

Rule indices:

  • winlogbeat-*
  • logs-endpoint.events.*
  • logs-windows.*

Severity: low

Risk score: 21

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: 7 (version history)

Added (Elastic Stack release): 7.7.0

Last modified (Elastic Stack release): 7.12.0

Rule authors: Elastic

Rule license: Elastic License v2

Potential false positives

edit

The Build Engine is commonly used by Windows developers but use by non-engineers is unusual.

Rule query

edit
event.category:process and event.type: start and
process.name:MSBuild.exe and process.parent.name:(cmd.exe or
powershell.exe or cscript.exe or wscript.exe)

Threat mapping

edit

Framework: MITRE ATT&CKTM

Rule version history

edit
Version 7 (7.12.0 release)
  • Formatting only
Version 6 (7.11.2 release)
  • Formatting only
Version 5 (7.11.0 release)
  • Formatting only
Version 4 (7.10.0 release)
  • Formatting only
Version 3 (7.9.1 release)
  • Formatting only
Version 2 (7.9.0 release)
  • Updated query, changed from:

    process.name:MSBuild.exe and process.parent.name:(cmd.exe or
    powershell.exe or cscript.exe or wscript.exe) and
    event.action:"Process Create (rule: ProcessCreate)"