SC-49 Hardware-enforced Separation and Policy Enforcement
Guidance: nonePolicy clause: noneWhat these mean
sc49ctl| Baselines | Implementation level | Enhancements |
|---|---|---|
| Not in a baseline | Organization | None |
Related controls: AC-4, SA-8, SC-50
Control statement
Section titled “Control statement”Implement hardware-enforced separation and policy enforcement mechanisms between [Assignment: organization-defined security domains].
NIST discussion
System owners may require additional strength of mechanism and robustness to ensure domain separation and policy enforcement for specific types of threats and environments of operation. Hardware-enforced separation and policy enforcement provide greater strength of mechanism than software-enforced separation and policy enforcement.
Assessment objectives (SP 800-53A)
Section titled “Assessment objectives (SP 800-53A)”Objectives and methods for SC-49
Determine if hardware-enforced separation and policy enforcement mechanisms are implemented between [Assignment: organization-defined security domains].
Examine: System and communications protection policy; procedures addressing cross-domain policy enforcement; system design documentation; system configuration settings and associated documentation; system audit records; system security plan; other relevant documents or records.
Interview: System/network administrators; organizational personnel with information security responsibilities; organizational personnel installing, configuring, and/or maintaining the system.
Test: Mechanisms supporting and/or implementing hardware-enforced security domain separation and policy enforcement.
Independent guidance, not an official NIST publication. Control text is from NIST SP 800-53 Rev. 5 and SP 800-53A (public domain). Original content is licensed CC BY 4.0; program templates and the downloadable kit are dedicated to the public domain under CC0 1.0.