EvidenceSheet

SC-46 Cross Domain Policy Enforcement. Implement a policy enforcement mechanism [organization-defined] between the physical and/or network interfaces for the connecting security domains

Cross Domain Policy Enforcement. Implement a policy enforcement mechanism [organization-defined] between the physical and/or network interfaces for the connecting security domains.

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 no path exists between the domains that bypasses the mechanism · Document repository
  • Assessment or accreditation evidence for the cross domain mechanism itself · Document repository

governing documentDocuments that govern the control

  • Identification of the connecting security domains and the interfaces between them · Document repository
  • Design documentation of the policy enforcement mechanism sited between those interfaces · Policy repository / GRC workspace
  • The policy the mechanism enforces, expressed as permitted data types, directions and transformations · 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

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 sheet

SC-45 System Time Synchronization. Synchronize system clocks within and between systems and system components · SC-47 Alternate Communications Paths. Establish [organization-defined] for system operations organizational command and control