SC-49 Hardware-enforced Separation and Policy Enforcement. Implement hardware-enforced separation and policy enforcement mechanisms between [organization-defined]
Hardware-enforced Separation and Policy Enforcement. Implement hardware-enforced separation and policy enforcement mechanisms between [organization-defined].
5
artefacts
0
held by a system
2
at each review
hard
to go live
Document repository
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- Evidence the enforcement is in hardware and cannot be reconfigured by software running in either domain · Document repository
- Assessment or test results confirming separation holds under fault and attack conditions · Source control / CI pipeline
governing documentDocuments that govern the control
- Identification of the domains or components required to be separated · Document repository
- Documentation of the hardware mechanism enforcing the separation, such as physical separation, hardware memory protection or dedicated devices · Policy repository / GRC workspace
- Policy enforced at the boundary and the interfaces permitted to cross it · Policy repository / GRC workspace
First move
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
Common gaps auditors find
- Virtualisation presented as hardware enforced separation when the hypervisor is software the domains share
- Hardware separation at the data path while a shared management processor spans both domains
- Separation asserted from product marketing with no assessment specific to this deployment
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheetSC-48 Sensor Relocation. Relocate [organization-defined] to [organization-defined] under the following conditions or circumstances: [organization-defined] · SC-50 Software-enforced Separation and Policy Enforcement. Implement software-enforced separation and policy enforcement mechanisms between [organization-defined]