The SIEM app is now a part of the Elastic Security solution. Click here to view the current documentation.
IMPORTANT: No additional bug fixes or documentation updates will be released for this version.
« Microsoft Build Engine Started by a System Process Microsoft Build Engine Using an Alternate Name »
Elastic Docs ›SIEM Guide [7.8] ›Detections (beta) ›Prebuilt rule reference

Microsoft Build Engine Started by an Office Application

edit

Microsoft Build Engine Started by an Office Application

edit

An instance of MSBuild, the Microsoft Build Engine, was started by Excel or Word. This is unusual behavior for the Build Engine and could have been caused by an Excel or Word document executing a malicious script payload.

Rule type: query

Rule indices:

  • winlogbeat-*

Severity: high

Risk score: 73

Runs every: 5 minutes

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

Maximum signals per execution: 100

References:

Tags:

  • Elastic
  • Windows

Version: 1

Added (Elastic Stack release): 7.7.0

Potential false positives

edit

The Build Engine is commonly used by Windows developers but use by non-engineers is unusual. It is quite unusual for this program to be started by an Office application like Word or Excel.

Rule query

edit
process.name:MSBuild.exe and process.parent.name:(eqnedt32.exe or
excel.exe or fltldr.exe or msaccess.exe or mspub.exe or outlook.exe or
powerpnt.exe or winword.exe) and event.action: "Process Create (rule:
ProcessCreate)"

Threat mapping

edit

Framework: MITRE ATT&CKTM

« Microsoft Build Engine Started by a System Process Microsoft Build Engine Using an Alternate Name »