Skip to main content
CMU-CSO-UVMAll frameworksImplementation guide coming soon

Using Validated Cryptographic Modules

Cryptographic Module Use (CMU) · Cloud Service Provider Responsibilities

FedRAMP release 2026.10.13.01Rule last changed Checked against FedRAMP/rules

Applies to: Providers
Who this applies to
Providers
Service class
Varies: A, B, C, D
Force
Varies by class
Timeframe
No fixed timeframe

Reviewed implementation guidance for CMU-CSO-UVM is not published yet. The official source below remains complete and authoritative.

Official FedRAMP source

Verbatim from FedRAMP/rules

This requirement varies by FedRAMP Certification class. Each class has its own statement:

Class A

MAY
Providers with Class A Certifications MAY use cryptographic modules or update streams of cryptographic modules with active validations under the NIST Cryptographic Module Validation Program when using cryptographic services to protect federal customer data.

Class B

MAY
Providers with Class B Certifications MAY use cryptographic modules or update streams of cryptographic modules with active validations under the NIST Cryptographic Module Validation Program when using cryptographic services to protect federal customer data.

Class C

SHOULD
Providers with Class C Certifications SHOULD use cryptographic modules or update streams of cryptographic modules with active validations under the NIST Cryptographic Module Validation Program when using cryptographic services to protect federal customer data.

Class D

MUST
Providers with Class D Certifications MUST use cryptographic modules or update streams of cryptographic modules with active validations under the NIST Cryptographic Module Validation Program when using cryptographic services to protect federal customer data.

Defined terms in this requirement

NIST 800-53 crosswalk

ac-18, au-9.3, ia-7, sc-28.1, sc-8.1

Operationalize this rule

Boundera turns FedRAMP 20x requirements like CMU-CSO-UVM into assigned evidence, remediation work, and validation workflows.

See it on your cloud

Notes

  • Cryptographic modules include specific algorithms by definition; if an update stream of a cryptographic module adds new algorithms that were not previously validated then those algorithms can not be considered within the scope of update stream usage under these rules as they are new algorithms within the module that have never been validated.

Change history

  • 2026-10-13Updated control mappings: added ac-18, au-9.3, ia-7, sc-28.1, sc-8.1.
  • 2026-10-05Added a note clarifying that new algorithms in update streams of modules are not included in the scope of updates to validated cryptographic modules.
  • 2026-06-24Official launch of the FedRAMP Consolidated Rules for 2026.

Content provenance

Official requirement text is sourced from FedRAMP/rules . Boundera implementation guidance has not been fully reviewed for this item.