EvidenceSheet
NIST SP 800-171 Rev 3 · 03.13 SC (System and Communications Protection)

03.13.11 Cryptographic Protection

Implement FIPS-validated or NSA-approved cryptography for protecting the confidentiality of CUI.

Source: NIST SP 800-171 Rev 3, 03.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 NIST SP 800-171 Rev 3 in the compliance library.

3
artefacts
0
held by a system
2
at each review
hard
to go live
Document repository
where the evidence lives
teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

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

none for this control

periodic reviewEvidence produced at each review

  • FIPS 140-2/3 validation certificates · Document repository
  • FIPS mode evidence · Document repository

governing documentDocuments that govern the control

  • Cryptographic module inventory · Policy repository / GRC workspace

First move

No system holds this evidence for you: it is people and documents. Reminders and routing to the owner still save time. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date.

Common gaps auditors find

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 sheet

03.13.10 Cryptographic Key Establishment and Management · 03.13.12 Collaborative Computing Devices and Applications