Skip to content
User application hardening
Essential EightE8-AH-ML2.2

Essential Eight AH-ML2.2 Block Microsoft Office from creating child processes

What it says

Microsoft Office is blocked from creating child processes.

Quoted as published. Everything else on this page is written by Control Stack.

In plain English

Microsoft Office, including its email client, must be blocked from starting other programs (child processes), so a malicious document cannot use Office to launch them.

Microsoft Office must be blocked from creating child processes. A child process is a program started by another program, such as a command prompt launched from Office by a document's macro or exploit. The block must cover every Office application, including the email client, on every device that runs Office. Blocked means the attempt fails, not that it is only logged or that the user can override it. E8-AH-ML2.8 sets the same block for PDF software at Maturity Level Two.

Why it matters

Malicious documents and macros commonly start a command shell or script host through Office to download and run further malware. Blocking Office from creating child processes removes that step, even when a user opens the document and enables its content.

How to implement

  1. Run the blocking rules in audit mode on a pilot group first.

    On Windows, use the endpoint protection rules that block Office applications, and separately the Office email client, from creating child processes. Review the audit events for add-ins, macros or integrations that legitimately start other programs.

  2. Change what the audit finds instead of excluding it.

    Update, replace or remove add-ins and macros that start other programs. An exclusion leaves Office able to start that program, so any exclusion is a gap against this requirement until it is removed.

  3. Switch the rules to block on every device running Office.

    Apply them through Group Policy or device management to all workstations and servers with Office, including remote desktop hosts. Use block, not audit or warn, since warn lets the user allow the program. If another product replaces the built-in Windows antivirus, use its equivalent rule.

  4. Test with a document that tries to start a program.

    Signed in as a user allowed to run macros (E8-RM-ML1.1 limits who can), open a test document whose macro tries to start a command prompt, in each main Office application. Confirm nothing starts and the device records the block.

Keep it running

Watch block events for business tools that break, and fix the tool rather than add an exclusion. Recheck when endpoint protection changes or new devices are built, since a rule can be missed or left in audit.

Evidence and audit

  1. Check 1 of 3What an auditor asks for

    Ask for

    Office licence activation records or a software inventory, compared with the devices reporting the blocking rules.

    Look at

    Devices running Office, including servers and remote desktop hosts, that are missing from the report or not set to block.

    Good evidence

    Every device running Office reports the rules for Office applications and the email client set to block, with none missing.

  2. Check 2 of 3What an auditor asks for

    Ask for

    The exclusions configured for the blocking rules.

    Look at

    Whether any exclusion lets Office start a program.

    Good evidence

    No exclusion lets Office start any program; one recorded as an approved exception still counts as a gap.

  3. Check 3 of 3What an auditor asks for

    Ask for

    A demonstration with a test document whose macro tries to start a program, run by a user allowed to run macros.

    Look at

    Whether the program starts in each main Office application, and whether the device records the block.

    Good evidence

    The program starts in no Office application tested, and each attempt appears in the device's block events.

Mappings

Closest match in ASD Information Security Manual: ISM-1601, Implement Microsoft Attack Surface Reduction rules, which asks for the same thing.

ASD ISM

ASD Information Security Manual: 11 mappings

ASD Essentials

ASD Essentials for enterprise IT: 1 mapping

Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.