Microsoft Build Engine Using an Alternate Name

edit

An instance of MSBuild, the Microsoft Build Engine, was started after being renamed. This is uncommon behavior and may indicate an attempt to run MSBuild unnoticed or undetected.

Rule type: query

Rule indices:

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

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

Added (Elastic Stack release): 7.7.0

Last modified (Elastic Stack release): 7.10.0

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.pe.original_file_name:MSBuild.exe or
winlog.event_data.OriginalFileName:MSBuild.exe) and not process.name:
MSBuild.exe

Threat mapping

edit

Framework: MITRE ATT&CKTM

Rule version history

edit
Version 4 (7.10.0 release)
  • Updated query, changed from:

    event.category:process and event.type:(start or process_started) and
    (pe.original_file_name:MSBuild.exe or
    winlog.event_data.OriginalFileName:MSBuild.exe) and not process.name:
    MSBuild.exe
Version 3 (7.9.1 release)
  • Formatting only
Version 2 (7.9.0 release)
  • Updated query, changed from:

    (pe.original_file_name:MSBuild.exe or
    winlog.event_data.OriginalFileName: MSBuild.exe) and not process.name:
    MSBuild.exe and event.action: "Process Create (rule: ProcessCreate)"