SC.L2-3.13.8 Data in Transit
Apply cryptographic protection to prevent unauthorized disclosure of CUI during transmission, unless alternative physical safeguards protect it instead.
3
artefacts
1
held by a system
0
at each review
moderate
to go live
Cloud console / configuration management
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Transmission encryption configuration for CUI bearing paths · Cloud console / configuration management
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Inventory of CUI transmission paths, internal and external · Policy repository / GRC workspace
- Documented alternative physical safeguards where used · Policy repository / GRC workspace
First move
Start with the 1 of 3 artefacts that already live in a system (Cloud console / configuration management); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- External transmission encrypted while internal paths are clear
- Email carrying CUI sent without protection
- Alternative safeguards asserted without documentation
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.L2-3.13.7 Split Tunneling · SC.L2-3.13.9 Connections Termination