The SIEM app is now a part of the Elastic Security solution. Click here to view SIEM documentation for previous releases.
« Microsoft Build Engine Started by a Script Process Microsoft Build Engine Started by an Office Application »
Elastic Docs ›Elastic Security Solution [7.9] ›Detections and Alerts (beta) ›Prebuilt rule reference

Microsoft Build Engine Started by a System Process

edit

Microsoft Build Engine Started by a System Process

edit

An instance of MSBuild, the Microsoft Build Engine, was started by Explorer or the WMI (Windows Management Instrumentation) subsystem. This behavior is unusual and is sometimes used by malicious payloads.

Rule type: query

Rule indices:

  • winlogbeat-*
  • 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
  • Windows

Version: 3 (version history)

Added (Elastic Stack release): 7.7.0

Last modified (Elastic Stack release): 7.9.1

Rule authors: Elastic

Rule license: Elastic License

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 or process_started) and
process.name:MSBuild.exe and process.parent.name:(explorer.exe or
wmiprvse.exe)

Threat mapping

edit

Framework: MITRE ATT&CKTM

Rule version history

edit
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:(explorer.exe or
wmiprvse.exe) and event.action:"Process Create (rule: ProcessCreate)"
« Microsoft Build Engine Started by a Script Process Microsoft Build Engine Started by an Office Application »