COS-08 Policies for data transmission
Document and issue data transmission policies with technical and organisational measures protecting transferred data against interception, manipulation, copying, alteration, redirection and destruction, with the protecti
4
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
- Transmission policy naming the transfer channels and tools that may be used · Policy repository / GRC workspace
- Cross-reference from classification levels to the transmission protection required · Policy repository / GRC workspace
- Instructions for exchanging data with external parties, including removable media handling · Policy repository / GRC workspace
- Guidance issued to staff who routinely move data between organisations · 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
- Policy addresses electronic mail but ignores the file transfer and collaboration tools staff actually use
- Protection applied uniformly with no regard to how the information was classified
- Redirection and destruction risks unaddressed because the policy considers only eavesdropping
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 sheetCOS-07 Documentation of the network topology · CRY-01 Policy for the use of encryption procedures and key management