NIST SP 800-171 Rev 3
03.04 CM (Configuration Management)

NIST SP 800-171 Rev 3 03.04.12: System and Component Configuration for High-Risk Areas

Issue specifically configured systems to individuals traveling to high-risk locations; apply additional safeguards on return.

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

What else in your programme already covers this

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

  • ANSSI-HYG-33 Adopt Security Policies Dedicated to Mobile Terminals

FedRAMP High · 1 control

  • CM-2(7) Configure Systems and Components for High-Risk Areas

FedRAMP Moderate · 1 control

  • CM-2(7) Configure Systems and Components for High-Risk Areas

ISO 27001:2022 · 1 control

  • 7.9 Security of assets off-premises

ISO 27002:2022 · 1 control

  • 7.9 Security of assets off-premises

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.04 CM (Configuration Management)

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.04.12 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 7 it maps to, and the evidence behind each claim, over MCP and REST.