NIST SP 800-171 Rev 3
03.13 SC (System and Communications Protection)

NIST SP 800-171 Rev 3 03.13.13: Mobile Code

Define acceptable and unacceptable mobile code and mobile code technologies; authorize, monitor, and control use of mobile code.

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

What else in your programme already covers this

This control maps to 20 controls across 16 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 · 2 controls

  • E8-MACRO-ML1 Configure Microsoft Office Macro Settings (ML1)
  • E8-MACRO-ML3 Configure Microsoft Office Macro Settings (ML3)
  • ASD37-03 Configure Microsoft Office macro settings (Essential)
  • ASD37-04 User application hardening (Essential)

CIS Controls v8 · 2 controls

  • CIS-2.7 Allowlist Authorized Scripts
  • CIS-9.4 Restrict Unnecessary or Unauthorized Browser and Email Client Extensions

ISO 27001:2022 · 2 controls

  • 8.23 Web filtering
  • 8.7 Protection against malware

CMMC 2.0 · 1 control

FedRAMP High · 1 control

FedRAMP Moderate · 1 control

HIPAA Security Rule · 1 control

PCI DSS 4.0 · 1 control

  • 6.4.3 6.4.3 Payment page script management

SOC 2 · 1 control

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

UK Cyber Essentials · 1 control

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 03.13 SC (System and Communications Protection)

You are reading one control. How much of NIST SP 800-171 Rev 3 have you already done?

NIST SP 800-171 Rev 3 03.13.13 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of NIST SP 800-171 Rev 3 your existing evidence covers. Hold PCI DSS 4.0 and 69 of 97 NIST SP 800-171 Rev 3 controls already carry evidence.

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 PCI DSS 4.0 pair alone.

Query this from an agent

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