Skip to content
FedRAMP Rules Hub
JSON — GET /api/obligations

Keyboard shortcuts

Go

  • Scope — the control cataloggm
  • Plan — your last certification classgp
  • Collect — the recipe indexgc
  • The control you are workinggw
  • Startgh

Move

  • Next rowj
  • Previous rowk
  • Previous in this run[
  • Next in this run]
  • Filter this page's list/
  • Search everything⌘K

Act

  • Copy this page's permalinky
  • Toggle dark moded
  • This sheet?

Rows are whatever the current page lists — controls on Scope, recipes on Plan and Collect.

Control index

CMU-CSO-UVMUsing Validated Cryptographic Modules

JSON — GET /api/obligationsMD — /requirement/cmu-cso-uvm.md — this page as markdown, for pasting into an agent
allvaries by class: a, b, c, d

The statement for this requirement varies by certification class — see the per-class deadlines below.

Who it binds

Providers

Controls whose FedRAMP guidance points at CMU (1)

Their guidance names the Cryptographic Module Use rules as a whole, not this requirement — so this is where to read from, not a mapping to this clause. Controls no KSI reaches have no page and are not listed.

SC-13

Which certifications it binds

Certification type
20x · Rev5
Path
Program · Agency

Evidence this requirement demands

  • List of cryptographic modules including whether these modules are validated under the NIST Cryptographic Module Validation Program or are update streams of such modules.class a
  • List of cryptographic modules including whether these modules are validated under the NIST Cryptographic Module Validation Program or are update streams of such modules.class b
  • List of cryptographic modules including whether these modules are validated under the NIST Cryptographic Module Validation Program or are update streams of such modules.class c
  • List of cryptographic modules including whether these modules are validated under the NIST Cryptographic Module Validation Program or are update streams of such modules.class d
5 default artifacts owed by every FRR requirement
  • Explanation of how the rule is followed, or an explanation of the reason and resulting risk to customers for not following the rule.
  • Verification that the implementation is appropriate for the rule, or that the reason for not implementing is accepted by a senior official.
  • Validation that the implementation is in place and working as intended, or that the reason for not implementing is accepted by a senior official.
  • Independent verification.
  • Independent validation.

Group all, subset CSO of Cryptographic Module Use. See all obligations on /obligations or the full evidence plan on /evidence.