Skip to content
System hardening
ASD ISMISM-1672

ASD ISM 1672 Enable antivirus scanning for Office macros

What it says

Microsoft Office macro antivirus scanning is enabled.

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

In plain English

Turn on Microsoft Office's antivirus scanning of macros, so the antivirus product checks macros, including what they do as they run.

Microsoft Office macro antivirus scanning must be enabled. This covers the scan of encrypted macros before they load, and Office's runtime scan: as a macro runs, Office passes its activity to the installed antivirus product through the Windows Antimalware Scan Interface (AMSI), a standard link between applications and antivirus. Antivirus on the workstation (ISM-1417) does not by itself meet this control, and scanning does not replace the check ISM-1890 requires before macros are signed or placed in Trusted Locations.

Why it matters

Malicious macros are often disguised so that scanning the file reveals nothing. Scanning what the macro does as it runs lets the antivirus product judge the behaviour, and Office closes the session if the product finds the macro malicious.

How to implement

  1. Confirm the antivirus product works with macro scanning.

    Office passes macro activity to whichever product is registered as an AMSI provider, so check your vendor's documentation and confirm the product is running on each device with Office (ISM-1417). Without a registered provider there is nothing for Office to scan with.

  2. Set 'Macro Runtime Scan Scope' to 'Enable for all documents'.

    Without this, the Office policy can leave out files in Trusted Locations, trusted documents and macros signed by a trusted publisher. ASD recommends this value. Heavy macros may run more slowly, so test them first.

  3. Set encrypted macro scanning by policy.

    In Excel, PowerPoint and Word, set the 'Scan encrypted macros' policies to Enabled with 'Scan encrypted macros (default)', so encrypted files are not skipped and people cannot change it (ISM-1489).

  4. Cover Office where this interface does not exist.

    AMSI is a Windows interface. On other operating systems, ask your antivirus vendor how macros are scanned and test it, or disable macros there. Anything left uncovered is a known shortfall.

Keep it running

Recheck after changing antivirus product, because the new product must also register as an AMSI provider. Treat a macro detection as malicious code and handle it under ISM-0917.

Evidence and audit

  1. Check 1 of 3What an auditor asks for

    Ask for

    The 'Macro Runtime Scan Scope' and 'Scan encrypted macros' policy states from endpoint management for every user, compared with Office install records from licensing or a software inventory scan.

    Look at

    Whether both policies reach everyone with Office, and their values.

    Good evidence

    Everyone on either list has 'Macro Runtime Scan Scope' set to 'Enable for all documents', the value ASD recommends, and 'Scan encrypted macros (default)' for Excel, PowerPoint and Word. Nobody has either policy disabled or not applied.

  2. Check 2 of 3What an auditor asks for

    Ask for

    The antivirus product's status on workstations picked from the inventory scan, with its vendor's documentation of AMSI support.

    Look at

    Whether the product is running on each workstation and registers as an AMSI provider.

    Good evidence

    A product that registers as an AMSI provider is running on every sampled workstation.

  3. Check 3 of 3What an auditor asks for

    Ask for

    A live test on a sampled workstation, using a harmless test macro your antivirus vendor or security team has confirmed should trigger a detection, with macros permitted for the test account.

    Look at

    Whether the macro is halted, and what the antivirus logs.

    Good evidence

    Office halts the macro and the antivirus log shows a detection for it.

Mappings

Closest match in ASD Essential Eight: E8-RM-ML1.3, Enable antivirus scanning for Microsoft Office macros, which asks for the same thing.

ISO 27001

ISO/IEC 27001: 1 mapping

  • A.8.7Protection against malwarePartially meets
Essential Eight

ASD Essential Eight: 6 mappings

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