FedRAMP Crypto-Module Rules: Comments Close 17 Nov
FedRAMP's RFC-0035, "Cryptographic Module Use Rules Updates" (published 14 October 2026), proposes revised cryptographic-module requirements for authorized cloud services. Public comment closes 17 November 2026, eight days from today.
Why It Matters
RFC-0035 proposes changes to how cloud providers must use cryptographic modules under the FedRAMP Consolidated Rules for 2026 (CR26), which govern both the 20x and Rev5 pipelines. The RFC process is the chance to shape the rule before it is finalized. Nothing changes for providers until FedRAMP issues final text.
It lands alongside other near-term FedRAMP dates. The CR26 vulnerability detection and response (VDR/VER) "Obtain & Maintain" date is 7 December 2026, and RFC-0036 on the 20x Class D cloud-hosted pilot closes for comment on 19 November. Compliance and security teams at cloud providers should treat the next two weeks as a review window.
Action Items
Read RFC-0035 — have your cryptography and FedRAMP leads review the proposed changes against the modules in your authorized boundary this week.
Comment by 17 November — submit feedback through the FedRAMP RFC process if a proposed change affects your implementation.
Check the 7 December date — confirm each 20x and Rev5 offering meets the CR26 VDR/VER Obtain & Maintain requirements.
Get the full analysis. Pro subscribers receive the complete deep dive, all 5 action items, source documents, and jurisdiction-specific compliance checklists.
Subscribe to Pro to read the rest.
Become a paying subscriber of Pro to get access to this post and other subscriber-only content.
UpgradeAlready a subscriber? Sign in
A subscription gets you:
- Deep dives of each updated regulation
- Source verification documents
- Extended jurisdiction-specific analysis
- Compliance deadline tracker
- Regulation crosswalk