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.
Free. Save your status, tasks and notes.
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
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.
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.
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).
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
- 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.
- 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.
- 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/IEC 27001: 1 mapping
This control partially meets A.8.7.
ISM-1672 requires a specific malware protection configuration: enabling antivirus scanning for Microsoft Office macros. Annex A 8.7 requires organisations to implement protection against malware more generally, supported by appropriate user awareness. ISM-1672 is a concrete technical subset of the broader malware protection expectations in Annex A 8.7.
ASD Essential Eight: 6 mappings
This control is equivalent to E8-RM-ML1.3.
ISM-1672 requires Microsoft Office macro antivirus scanning to be enabled. E8-RM-ML1.3 specifies the same configuration outcome: enabling antivirus scanning for Microsoft Office macros. Both controls are aligned in scope and intent, and implementing either would largely satisfy the other.
This control partially overlaps E8-AH-ML2.3.
ISM-1672 requires Microsoft Office macro antivirus scanning to be enabled to detect malicious macro-enabled content. E8-AH-ML2.3 reduces macro-borne risk by blocking Microsoft Office from creating executable content, which targets a common malware delivery chain that macro malware may use after execution. The controls intersect in mitigating macro-enabled malware, but one is detection-oriented (scanning) and the other is prevention-oriented (blocking executable creation).
This control partially overlaps E8-RM-ML1.2.
ISM-1672 requires Microsoft Office macro antivirus scanning to be enabled to detect malicious macro content. E8-RM-ML1.2 blocks macros in files originating from the internet, reducing exposure to common phishing and drive-by macro payloads that scanning would otherwise need to detect. The overlap is macro malware mitigation, but E8-RM-ML1.2 is a source-based execution block whereas ISM-1672 is a scanning/detection setting that can apply more broadly.
- E8-RM-ML3.1Restrict Office macros to sandboxes, Trusted Locations or trusted publishersPartially overlaps
This control partially overlaps E8-RM-ML3.1.
ISM-1672 requires Microsoft Office macro antivirus scanning to be enabled to identify malicious macros at runtime or on access. E8-RM-ML3.1 restricts macro execution to sandboxed environments, Trusted Locations, or digitally signed macros from trusted publishers, thereby controlling where and when macros can run. Both reduce macro malware risk, but E8-RM-ML3.1 focuses on execution trust boundaries while ISM-1672 focuses on malware detection via scanning.
This control depends on E8-RM-ML1.4.
ISM-1672 requires Microsoft Office macro antivirus scanning to be enabled as a protective configuration. E8-RM-ML1.4 ensures users cannot change Microsoft Office macro security settings, which helps preserve the enabled scanning state and prevents user-driven weakening of macro protections. E8-RM-ML1.4 is about configuration enforcement, while ISM-1672 is the specific setting to be enforced.
This control depends on E8-RM-ML3.2.
E8-RM-ML3.2 requires macros to be checked to ensure they are free of malicious code before being signed or trusted via Trusted Locations. ISM-1672 supports this by enabling antivirus scanning for Office macros, which is a key technical mechanism that can be used during the checking step. ISM-1672 is about configuring a detection capability, while E8-RM-ML3.2 is about the governance/assurance decision to only sign or trust macros after verification.
Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.




