03.13.11 Cryptographic Protection
Implement FIPS-validated or NSA-approved cryptography for protecting the confidentiality of CUI.
3
artefacts
0
held by a system
1
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
none for this control
periodic reviewEvidence produced at each review
- FIPS mode evidence · Document repository
governing documentDocuments that govern the control
- FIPS 140-2/3 validation certificates · Document repository
- Cryptographic module inventory · 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
- non-FIPS algorithms used
- FIPS mode not enabled on OS
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 sheet03.13.10 Cryptographic Key Establishment and Management · 03.13.12 Collaborative Computing Devices and Applications