Hardware-enforced Separation and Policy Enforcement
LOW MODERATE HIGHRequirements NIST SOURCE
Implement hardware-enforced separation and policy enforcement mechanisms between [security domains].
Discussion (NIST Supplemental Guidance)
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.
Implementation Guidance
Original engineering commentary written for this explorer — not NIST source text and not authoritative guidance.
No engineering interpretation has been authored for SC-49 yet. This section is architected to receive it — see the Requirements and Assessment sections above for the authoritative NIST source content in the meantime.
Assessment
Assessment Objectives
- security domains requiring hardware-enforced separation and policy enforcement mechanisms are defined;
- hardware-enforced separation and policy enforcement mechanisms are implemented between <SC-49_ODP security domains>.
Examine
[SELECT FROM: 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
[SELECT FROM: System/network administrators; organizational personnel with information security responsibilities; organizational personnel installing, configuring, and/or maintaining the system].
Test
[SELECT FROM: Mechanisms supporting and/or implementing hardware-enforced security domain separation and policy enforcement].
STIGs & CCIs
No STIG checks or CCI mappings are currently loaded for SC-49. This section is architected to display, per product: STIG ID, Finding ID, Severity, Title, Description, Check, Fix, CCI, and NIST control mapping — but nothing is populated here until a real DISA STIG/CCI dataset is ingested.
Learn more about STIG/CCI integration →Evidence
Categorized from the SP 800-53A "Examine"/"Test" artifact list above by keyword — not an authoritative NIST evidence list.
Policy
- System and communications protection policy
- procedures addressing cross-domain policy enforcement
- system security plan
Configuration
- system design documentation
- system configuration settings and associated documentation
Testing
- Mechanisms supporting and/or implementing hardware-enforced security domain separation and policy enforcement
Other Records
- system audit records
- other relevant documents or records