Requirement

Employ FIPS-validated cryptography when used to protect the confidentiality of “Controlled Unclassified Information” (CUI).

Assessment Objectives

  • FIPS-validated cryptography is employed to protect the confidentiality of CUI

Potential Assessment Methods and Objects [NIST SP 800-171A]

Examine

  • System and communications protection policy
  • Procedures addressing cryptographic protection
  • System security plan
  • System design documentation
  • System configuration settings and associated documentation
  • Cryptographic module validation certificates
  • List of FIPS-validated cryptographic modules
  • System audit logs and records
  • Any other relevant documents or records

Interview

  • System or network administrators
  • Personnel with information security responsibilities
  • System developers
  • Personnel with responsibilities for cryptographic protection

Test

  • Mechanisms supporting or implementing cryptographic protection

Discussion [NIST SP 800-171 REV. 2]

Cryptography can be employed to support many security solutions including the protection of controlled unclassified information, the provision of digital signatures, and the enforcement of information separation when authorized individuals have the necessary clearances for such information but lack the necessary formal access approvals. Cryptography can also be used to support random number generation and hash generation. Cryptographic standards include FIPS-validated cryptography and/or NSA-approved cryptography.

Further Discussion

FIPS-validated cryptography means the cryptographic module has to have been tested and validated to meet FIPS 140-2 requirements. Simply using an approved algorithm is not sufficient - the module (software and/or hardware) used to implement the algorithm must be separately validated under FIPS 140. Accordingly, FIPS-validated cryptography is required to protect CUI when transmitted or stored outside the protected environment of the covered OSA information system (including wireless/remote access). Encryption used for other purposes, such as within applications or devices within the protected environment of the covered OSA information system, would not need to use FIPS-validated cryptography. This requirement, SC.L2-3.13.11, complements AC.L2-3.1.19, MP.L2-3.8.6, SC.L2-3.13.8, and SC.L2-3.13.16 by specifying that FIPS-validated cryptography must be used. While FIPS-validated modules and algorithms are critical for protecting CUI, in limited cases Enduring Exceptions and temporary deficiencies may apply when implementing such cryptographic mechanisms.

Examples

Example 1

You are a system administrator responsible for deploying encryption on all devices that contain CUI. You must ensure that the encryption you use on the devices is FIPS-validated cryptography [a]. An employee informs you of a need to carry a large volume of CUI offsite and asks for guidance on how to do so. You provide the user with disk encryption software that you have verified via the NIST website that uses a CMVP-validated encryption module [a]. Once the encryption software is active, the user copies the CUI data onto the drive for transport.

Potential Assessment Considerations

  • Is cryptography implemented to protect the confidentiality of CUI at rest and in transit, through the configuration of systems and applications or through the use of encryption tools [a]?

References

  1. NIST SP 800-171 Rev. 2 3.13.11

Need help putting this into practice? See our NIST SP 800-171 & CMMC compliance services or read our NIST SP 800-171 & CMMC articles.

See LakeRidge in action.

Talk with our team about your framework, your gaps, and the right plan.

Get a demo

See LakeRidge in action.

Loading the booking calendar…