attachment
<div dir="ltr"><div>Hi,</div><div><br></div><div>This NIST SP800-133 spec is finally being revised to align with updated NIST SP800-90A/B/C</div><div>(Entropy and RNGs) and NIST PQC standards (FIPS 203, 204, 205 and future 206 and 207).</div><div><br></div><div>Crypto Key Generation underlies a whole lot of NIST specs. They have said that SP800-133</div><div>will go to full standard in the next release in later 2026.</div><div><br></div><div>Cheers,</div><div>- Ira</div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">---------- Forwarded message ---------<br>From: <b class="gmail_sendername" dir="auto">'Hamilton Silberg' via pqc-forum</b> <span dir="auto"><<a href="mailto:pqc-forum@list.nist.gov">pqc-forum@list.nist.gov</a>></span><br>Date: Fri, Apr 17, 2026 at 9:54 AM<br>Subject: [pqc-forum] Call for comments: ipd SP 800-133r3 Recommendation for Cryptographic Key Generation<br>To: pqc-forum <<a href="mailto:pqc-forum@list.nist.gov">pqc-forum@list.nist.gov</a>><br></div><br><br>Hello all,<br><br>The initial public draft (ipd) of NIST SP 800-133r3 (Revision 3), Recommendation for Cryptographic Key Generation, is available for public comment. <br><br>Proposed changes in this revision include the following:<br>•<span style="white-space:pre-wrap"> </span>Asymmetric key-pair generation has been expanded to include methods for deriving randomness during key-pair generation.<br>•<span style="white-space:pre-wrap"> </span>Key-pair generation now has options for derivation similar to symmetric keys and new methods for “seed expansion,” which allows for the limited use of SHAKE and deterministic random bit generators (DRBGs).<br>•<span style="white-space:pre-wrap"> </span>Key-encapsulation mechanisms (KEMs) are discussed as a key-establishment option for symmetric key generation, and post-quantum cryptography (PQC) references have been added throughout (e.g., the new PQC signatures).<br>•<span style="white-space:pre-wrap"> </span>Text has been reworded to address random number generation in alignment with SP 800-90C.<br><br><br>Comments are especially requested regarding:<br>•<span style="white-space:pre-wrap"> </span>Hardware security module (HSM) design — How do these requirements align with common practice and existing systems using a root seed/secret value?<br>•<span style="white-space:pre-wrap"> </span>PQC implementations and protocols — How do these requirements fit with storing keys as seeds (e.g., for ML-KEM) and performing hybrid (i.e., combined classical and post-quantum) implementations?<br><br>The public comment period will be open through June 16, 2026.<br>See: <a href="https://csrc.nist.gov/pubs/sp/800/133/r3/ipd" target="_blank">https://csrc.nist.gov/pubs/sp/800/133/r3/ipd</a><br><br>Best,<br>-Hamilton Silberg<br>NIST PQC
<p></p>
-- <br>
You received this message because you are subscribed to the Google Groups "pqc-forum" group.<br>
To unsubscribe from this group and stop receiving emails from it, send an email to <a href="mailto:pqc-forum+unsubscribe@list.nist.gov" target="_blank">pqc-forum+unsubscribe@list.nist.gov</a>.<br>
To view this discussion visit <a href="https://groups.google.com/a/list.nist.gov/d/msgid/pqc-forum/eb4929b9-119e-4f8f-a221-04976ea72d51n%40list.nist.gov?utm_medium=email&utm_source=footer" target="_blank">https://groups.google.com/a/list.nist.gov/d/msgid/pqc-forum/eb4929b9-119e-4f8f-a221-04976ea72d51n%40list.nist.gov</a>.<br>
</div></div>