SC.L2-3.13.11 CUI Encryption
Use FIPS validated cryptography wherever cryptography is relied on to protect the confidentiality of CUI.
Source: CMMC 2.0, SC.L2-3.13.11. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open CMMC 2.0 in the compliance library.
These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.
system holds itEvidence a system already holds
- Inventory of cryptographic modules protecting CUI with validation certificate references · Policy repository / GRC workspace
- 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
none for this control
First move
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