ASD Strategies to Mitigate Cyber Security Incidents
Preventing Malware Delivery and Execution

ASD Strategies to Mitigate Cyber Security Incidents ASD37-03: Configure Microsoft Office macro settings (Essential)

Configure Microsoft Office macro settings to block macros from the internet, and only allow vetted macros either in Trusted Locations with limited write access or digitally signed with a trusted certificate.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 29 controls across 15 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

ACSC Essential Eight · 3 controls

  • E8-MACRO-ML1 Configure Microsoft Office Macro Settings (ML1)
  • E8-MACRO-ML2 Configure Microsoft Office Macro Settings (ML2)
  • E8-MACRO-ML3 Configure Microsoft Office Macro Settings (ML3)

FedRAMP High · 3 controls

FedRAMP Moderate · 3 controls

NIST SP 800-53 Rev 5 · 3 controls

Azure Security Benchmark · 2 controls

  • ASBv3-AM-5 Use only approved applications in virtual machine
  • ES-2 Use modern anti-malware software

CIS Controls v8 · 2 controls

  • CIS-2.7 Allowlist Authorized Scripts
  • CIS-9.6 Block Unnecessary File Types

CMMC 2.0 · 2 controls

ISO 27002:2022 · 2 controls

  • 8.7 Protection against malware
  • 8.9 Configuration management

NIST Cybersecurity Framework 2.0 · 2 controls

NIST SP 800-171 Rev 3 · 2 controls

ASIC Cyber Resilience Good Practices · 1 control

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 1 control

ISO 27001:2022 · 1 control

  • 8.7 Protection against malware

PCI DSS 4.0 · 1 control

  • 2.2.6 2.2.6 System security parameters configured against misuse

SOC 2 · 1 control

  • SOC2-CC6.8 CC6.8 Preventing and detecting unauthorised or malicious software

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in Preventing Malware Delivery and Execution

You are reading one control. How much of ASD Strategies to Mitigate Cyber Security Incidents have you already done?

ASD Strategies to Mitigate Cyber Security Incidents ASD37-03 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of ASD Strategies to Mitigate Cyber Security Incidents your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 32 of 37 ASD Strategies to Mitigate Cyber Security Incidents controls already carry evidence.

If you hold NIST SP 800-53 Rev 586.5% covered · 5 gapsIf you hold FedRAMP Moderate83.8% covered · 6 gapsIf you hold ISO 27001:202278.4% covered · 8 gapsIf you hold ISO 27002:202278.4% covered · 8 gapsIf you hold CMMC 2.075.7% covered · 9 gapsIf you hold NIST SP 800-171 Rev 370.3% covered · 11 gaps

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 0 were rejected on the NIST SP 800-53 Rev 5 pair alone.

See the released pairs, $299 eachBrowse the graph free

Query this from an agent

The graph holds this control, the 29 it maps to, and the evidence behind each claim, over MCP and REST.

MCP endpointAll ASD Strategies to Mitigate Cyber Security Incidents controls