This document has been developed to discuss approaches that can be applied by organisations to secure systems against malicious macros while balancing both their business and security requirements.

The names and locations of Group Policy settings used in this document are taken from Microsoft Office 2016 and are equally applicable to Microsoft Office 365 ProPlus and Microsoft Office 2019. Some differences however may exist for earlier versions than Microsoft Office 2016.

An increasing number of attempts to compromise organisations using malicious macros have been observed. In particular, adversaries have been observed using social engineering techniques to entice users into executing malicious macros in Microsoft Office files. The purpose of these malicious macros can range from cybercrime to more sophisticated exploitation attempts.

By understanding the business requirements for the use of macros, and applying the recommendations in this document, organisations can effectively manage the risk of allowing macros in their environments.

Microsoft Office files can contain embedded code (known as a macro) written in the Visual Basic for Applications (VBA) programming language.

A macro can contain a series of commands that can be coded or recorded, and replayed at a later time to automate repetitive tasks. Macros are powerful tools that can be easily created by novice users to greatly improve their productivity. However, an adversary can also create macros to perform a variety of malicious activities, such as assisting in the compromise of workstations in order to exfiltrate or deny access to sensitive information.

Microsoft Office has both trusted document and trusted location functions. Once trusted documents or trusted locations are defined, macros in trusted documents or macros in Microsoft Office files in trusted locations automatically execute when the files are opened. While the use of trusted documents is discouraged, trusted locations when implemented in a controlled manner can allow organisations to appropriately balance both their business and security requirements.

Microsoft Office applications allow developers to include information about themselves by digitally signing their macros. The signing certificate that is used to create a signed macro confirms that the macro originated from the signatory, while the signature itself confirms that the macro has not been altered. Digital signing certificates can be self-generated by users, obtained from a commercial Certificate Authority or obtained from an organisation’s security administrator if they operate their own Certificate Authority.

To manage the use of macros within an organisation, all macros created by users or third parties should be reviewed by an independent party to the developer and assessed to be safe before being approved for use within the organisation.

When assessing whether macros are safe or not, assessors should ask themselves the following questions:

• Is there a business requirement for a particular macro?
• Has the macro been developed or provided by a trusted party?
• Has the macro been validated by a trustworthy and technically skilled party?

The following table displays the security benefit, business impact and implementation difficulty of different approaches to managing macros in Microsoft Office files.

If organisations do not have a business requirement for macro use, support for their use should be disabled across the Microsoft Office suite.

To prevent users or an adversary from bypassing macro security controls, all support for trusted documents and trusted locations should be disabled.

To ensure users cannot knowingly or unintentionally alter macro security controls via a Microsoft Office application’s Trust Center interface, organisations should apply macro security controls using Group Policy settings.

If organisations have a business requirement for macro use, approved macros in Microsoft Office files in trusted locations can be allowed to execute. However, only specific Microsoft Office applications for which there is a business requirement for macro use should be allowed to execute approved macros. All other Microsoft Office applications should have support for macros disabled.

To prevent users or an adversary from bypassing macro security controls, support for trusted documents should be disabled while trusted locations should prevent all users, except for approved users, from adding or modifying macros in Microsoft Office files in these locations. Using an appropriately secured network path as a trusted location can assist in the centralised management and control of macros in Microsoft Office files.

To ensure users cannot knowingly or unintentionally alter macro security controls via a Microsoft Office application’s Trust Center interface, organisations should apply macro security controls using Group Policy settings.

If organisations have a business requirement for macro use, only macros digitally signed by trusted publishers can be allowed to execute. However, only specific Microsoft Office applications for which there is a business requirement for macro use should be allowed to execute digitally signed macros. All other Microsoft Office applications should have support for macros disabled.

To prevent users or an adversary from bypassing macro security controls, support for trusted documents and trusted locations should be disabled.

To further reduce the likelihood of an adversary signing a malicious macro and it being executed by users, the ability to enable macros signed by an untrusted publisher, or add additional trusted publishers, should be disabled for users. This includes via the trust bar, backstage view, Internet Options control panel and the use of certificate management tools.

Organisations should take care to sufficient test this approach before implementation to ensure that there are no unintended consequences of implementing the above restrictions on Microsoft Office and certificate management functionality within their environment.

To ensure users cannot knowingly or unintentionally alter macro security controls via a Microsoft Office application’s Trust Center interface, organisations should apply macro security controls using Group Policy settings.

If organisations have a business requirement for macro use, they should manage the use of macros in their environment using one of the recommended approaches discussed below. Relying on users to make correct security decisions one hundred percent of the time is not a realistic expectation considering the sophistication of many spear phishing attempts. As such, allowing users to decide which macros to enable on a case-by-case basis presents a significant risk and should not be implemented.

If organisations have a business requirement for macro use, they should manage the use of macros in their environment using one of the recommended approaches discussed below. Allowing unrestricting execution of all macros presents a serious risk and should never be implemented.

To protect themselves against malicious macros, organisations should implement one of the following recommended approaches:

• all macros are disabled
• only macros from trusted locations are enabled
• only macros digitally signed by trusted publishers are enabled.

In addition to implementing one of the recommended approaches above, organisations should:

• implement application control to mitigate a malicious macro running unapproved applications
• implement email and web content filtering to inspect incoming Microsoft Office files for macros, and block or quarantine them as appropriate
• implement macro execution logging to verify only approved macros are used (e.g. by logging the execution of known file extensions such as dotm, docm, xlsm, pptm and ppsm)
• ensure users assigned to assessing the safety of macros have appropriate VBA training.