SC.L2-3.13.11 CUI Encryption
Use FIPS validated cryptography wherever cryptography is relied on to protect the confidentiality of CUI.
3
artefacts
1
held by a system
1
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
- Configuration evidence showing validated modules and approved modes in use · Cloud console / configuration management
periodic reviewEvidence produced at each review
- Evidence non validated cryptography is not relied on for CUI · Document repository
governing documentDocuments that govern the control
- Inventory of cryptographic modules protecting CUI with validation certificate references · 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
- Cryptography strong but not FIPS validated
- Validated module present but operated outside its approved mode
- Certificate references stale or covering a different version
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.10 Key Management · SC.L2-3.13.12 Collaborative Device Control