EvidenceSheet
NIST SP 800-53 Rev 5 · SC - System and Communications Protection

SC-1 Policy and procedures for system and communications protection

Requires a system and communications protection policy with supporting procedures to be developed, approved, disseminated to defined personnel, owned by a named official, and reviewed and updated on a defined frequency a

5
artefacts
0
held by a system
0
at each review
hard
to go live
Policy repository / GRC workspace
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

none for this control

governing documentDocuments that govern the control

  • Approved system and communications protection policy with scope, approver and date · Policy repository / GRC workspace
  • Evidence the system and communications protection policy reached the personnel or roles it defines · Policy repository / GRC workspace
  • Written designation of the official accountable for the system and communications protection policy and procedures · Policy repository / GRC workspace
  • Procedures covering boundary protection, cryptography and transmission protection · Policy repository / GRC workspace
  • Review record for the system and communications protection policy and procedures against the defined frequency and triggering events · 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

SA-24 Design For Cyber Resiliency. Design organizational systems, system components, or system services to achieve cyber resiliency by: Defining the following cyber resiliency goals: [organization-defined]. Defining the following cyber resiliency objectives: [organization-defined]. Defining the following · SC-2 Separation of system and user functionality