🛡️ Essential 8 Guide

Implementation guidance for Australian Essential Eight controls in Microsoft environments - ISM controls with PSPF mappings

About
HOME ← ISM-1659
ISM-1668 →

Microsoft Office is blocked from creating child processes.

Property Value
ISM Control ISM-1667
Revision 0
Updated Sep-21
Guideline Not provided
Section User application hardening
Topic Hardening user application configurations
Essential Eight ML2, ML3
PSPF Levels NC, OS, P, S, TS

Summary

This control blocks all Office applications from creating child processes, reducing the attack surface by preventing Office from spawning subprocesses that could be abused for code execution or malware propagation12. Implementation is achieved by importing the ASR policy for Office child process blocking into Intune, as documented in the ACSC Windows Hardening Guidelines1.

The specific ASR rule is Block all Office applications from creating child processes (GUID: D4F940AB-401B-4EFC-AADC-AD5F3C50688A). This rule blocks any child process spawned by Word, Excel, PowerPoint, OneNote, Access, or other Office applications — including PowerShell, cmd, and any external executable launched from an Office document. It complements ISM-1668 (Block Office from creating executable content), which acts at an earlier stage by preventing payload files being written to disk.

[!NOTE] Enable both ISM-1667 (child process) and ISM-1668 (executable content) rules for defence-in-depth: the executable content rule blocks payload creation; the child process rule blocks post-creation execution.

Justification

Not provided in source documentation.

Design Decision

[!NOTE] The Block all Office applications from creating child processes ASR rule will be enabled via Intune configuration profiles. This will block Office applications from creating child processes.

Prerequisites

Implementation Steps

Enable ASR rule to block Office apps from creating child processes via Intune

  1. Navigate to Graph Explorer and authenticate.1
  2. Copy the JSON in the ACSC Windows Hardening Guidelines-Attack Surface Reduction.json policy and paste it in the request body. The policy contains the specific ASR rule: Block all Office applications from creating child processes (D4F940AB-401B-4EFC-AADC-AD5F3C50688A). This ASR policy configures each of the ASR rules recommended by the ACSC in audit mode. ASR rules should be tested for compatibility issues in any environment before enforcement.1
  3. (Optional) modify the name value if necessary.1
  4. Alternatively, configure the rule directly in Intune via Endpoint security → Attack surface reduction → Create policy. Set Block all Office applications from creating child processes to Audit first, then Block after validation.
  5. For direct OMA-URI deployment, use:
    • OMA-URI: ./Vendor/MSFT/Policy/Config/Defender/AttackSurfaceReductionRules
    • Data type: String
    • Value (audit mode): D4F940AB-401B-4EFC-AADC-AD5F3C50688A=2
    • Change =2 to =1 to switch to Block mode after audit validation.
  6. Monitor audit events: Event ID 1122 (audit) and 1121 (block) in Microsoft-Windows-Windows Defender/Operational. In Microsoft 365 Defender Advanced Hunting, filter on ActionType = AsrOfficeChildProcessAudited or AsrOfficeChildProcessBlocked.

[!NOTE] This implementation imports the ASR policy in audit mode to validate compatibility before enforcement.1

HOME ← ISM-1659
ISM-1668 →