Employ physical isolation techniques, logical isolation techniques, or both across organizational systems and system components, so that CUI is separated into security domains behind managed interfaces, the attack surface is reduced and adversary movement between components is impeded.
This control maps to 15 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.
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.
NIST SP 800-172 3.13.4e is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of NIST SP 800-172 your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 24 of 35 NIST SP 800-172 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. 5 were rejected on the NIST SP 800-53 Rev 5 pair alone.
The graph holds this control, the 15 it maps to, and the evidence behind each claim, over MCP and REST.