EvidenceSheet

SC-16 Transmission of Security and Privacy Attributes. Associate [organization-defined] with information exchanged between systems and between system components

Transmission of Security and Privacy Attributes. Associate [organization-defined] with information exchanged between systems and between system components.

5
artefacts
1
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

  • Design and configuration evidence showing attributes travel with the information across each exchange · Cloud console / configuration management

periodic reviewEvidence produced at each review

  • Evidence the receiving system interprets and honours the transmitted attributes · Document repository
  • Records of exchanges where attribute mismatch caused the transfer to be refused · Document repository

governing documentDocuments that govern the control

  • The defined security and privacy attributes required to accompany information exchanged between systems and components · Policy repository / GRC workspace
  • Integrity protection over the attributes in transit so they cannot be altered · Document repository

First move

Mostly documents and reviews. Pull the 1 system-held artefact from your Cloud console / configuration management on a schedule; put the documents under version control with an owner and review date, and log each review as a dated record with a named reviewer.

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-15 Collaborative computing devices and applications · SC-17 Public key infrastructure certificates