The National Institute of Standards and Technology (NIST) announced on November 19, 2026, that it will revise Special Publication (SP) 800-52 Rev. 2, its guidelines for selecting, configuring and using Transport Layer Security (TLS) implementations. The current version calls for TLS 1.2 on government TLS servers and clients and for TLS 1.3 support by January 1, 2024.
Why NIST is revising it
SP 800-52 Rev. 2 was published in August 2019. In May 2026, NIST's Crypto Publication Review Board asked the public to comment on it. NIST says it had expected to revise the publication when it opened the review, and that the comments it received were consistent with that plan. A planning note now on the publication page says NIST will next develop a draft of SP 800-52 Rev. 3 and post it for public comment. NIST will not ask for more comments before that draft is out.
What NIST plans to change
According to the announcement, the planned policy changes include:
- NIST will recommend that servers "may" support TLS 1.2, rather than "should" support it.
- TLS 1.0 and TLS 1.1 will not generally be allowed.
- The Cryptographic Module Validation Program (CMVP) will set a timeline after which including TLS 1.2 in a module will need a strong justification, and including TLS 1.0 or 1.1 in non-governmental servers will need an exceptional one.
NIST also lists other planned updates: alignment with RFC 9846 for TLS 1.3, deprecating or disallowing TLS 1.2 cipher suites that use SHA-1, DSA, static key exchange or RSA key exchange, more detail on TLS 1.3 algorithms negotiated in extensions, post-quantum algorithms, a 128-bit minimum security level, and requiring AEAD modes for symmetric encryption and authentication. Certificate profiles, session resumption and early data, certificate revocation, supported extensions and references are also on the list.
What it means for practitioners
Rev. 2 remains the current version, and NIST has not yet released a draft revision. NIST points readers to its CSRC news and publications pages to follow the draft. Our suggestion, not NIST's: teams that manage servers or appliances can start listing where TLS 1.0, TLS 1.1 or older TLS 1.2 cipher suites are still enabled.
This kind of configuration work often falls to a security engineer or a system administrator. To see which certifications fit those roles, try the certification path planner.
