Le NIST déballe les nouvelles : Trois nouveaux algorithmes sont attendus en 2024

Alors que la feuille de route vers la production se précise, le responsable PKI de Keyfactorexplique quand et comment commencer à mettre en œuvre les nouvelles normes du NIST.  

The National Institute of Standards and Technology (NIST) has initiated the standardization process for four algorithms that were specifically designed to be resilient against quantum computer attacks. These algorithms were selected by NIST last year and are now one step closer to being accessible to organizations worldwide for integration into their encryption infrastructure. NIST recently released draft standards for three of the four chosen algorithms, while the draft standard for the fourth algorithm, FALCON, is expected to be published in about a year. Other algorithms were considered during the multi-year selection process and failed the rigorous testing processes, and did not hold up to public scrutiny.

Once completed, the new standards will provide the world with the first tools to protect sensitive information from this new threat. While current encryption algorithms are yet to be surpassed by quantum computers, experts emphasize the need for proactive planning to ensure long-term security. This is particularly important as integrating new algorithms across all computer systems can be time-consuming and span several years.

Now that the official word is out, industry and government organizations will race against PQC advancement to implement these standards. The cryptographic community has until November 22, 2023, to make comments before NIST finalizes the standard documents.

Q&A avec le directeur général de Keyfactor's PKI

Keyfactor’s Chief PKI Officer, Tomas Gustavsson, weighs in on the breaking industry news and advises organizations on when and how to start implementing NIST’s new standards.

Que signifie cette annonce du NIST pour la communauté cryptographique ?

TG: The news from NIST means the race is on. Organizations and vendors will quickly work to implement strategies for PKI replacement and data encryption (at rest and in transit) and develop additional protocols. We expect to see a myriad of advice, white papers, use cases, mandates, and more.

The uncertainty surrounding which algorithms will be used in practice has nearly disappeared. It is an important step because it allows organizations to focus on these algorithms for testing until production. The roadmap to production is becoming clearer, as there are now timelines outlining when the final standards will be available. For product vendors, it provides a path for development and interoperability testing.

OIDs (object identifiers) will not be released until the final standards, so it is not yet time to go to production, but the path forward is (almost) clear. What is still unclear is that we don’t know when FIPS certification can be performed. We will likely learn more about that once standards are published, potentially in early 2024.

En ce qui concerne la demande de retour d'information du NIST, y a-t-il des modifications à apporter aux projets de normes ?

TG: There is still uncertainty around Prehash usage of the digital signature algorithms for signing large payloads like CRLs, documents, or software using network-connected or cloud HSMs. It is mentioned in the FIPS 204 draft section 7.1 and the FIPS 205 draft section 9.4, but not with many details.

Comment Keyfactor est-il positionné face à ce changement imminent ?

TG: Keyfactor has been paving the way with testing implementation — over a year ago, Bouncy Castle was updated to support these algorithms. Keyfactor continues to be a leader in readiness and an advocate for organizations that need help with roadmapping, transitioning, and planning. Our custom PKI solutions enable organizations to prepare, no matter what step of the process they’re in. 

Le fait de posséder l'ensemble de la pile software , depuis les bibliothèques cryptographiques jusqu'à PKI et la signature numérique software , en passant par la gestion du cycle de vie, nous permet d'être parmi les premiers à prendre en charge les nouvelles normes. Notre site software peut servir de modèle à d'autres pour les tests, et les clients peuvent avoir la certitude que les solutions de Keyfactorsont prêtes pour le calcul quantique.

À un niveau élevé, quels conseils pouvez-vous donner aux organisations qui cherchent à mettre en œuvre ces normes (en particulier en ce qui concerne PKI) ?

TG: Now is the time for organizations to start taking inventory of systems for migration and identifying which are the most sensitive and most exposed. Security leaders also must look at the application ecosystem and start planning the migration— set up lab environments to test PQC PKI and prepare signature validation software for new algorithms. In short, start learning now so you can focus on the standardized algorithms and move forward. This change will come with a long learning curve for many organizations, so the time to begin the journey is today.

Un regard vers l'avenir : En savoir plus et tester dès aujourd'hui

Keyfactor EJBCA and SignServer already support issuing quantum-ready PKI certificates alongside the existing PKI within the same environment. This ensures a smooth experience with minimal disruption to your current infrastructure and environments. You can begin experimenting with the technology and gradually understand its relevance to your specific environment over time.

Bouncy Castle cryptographic APIs support all the new algorithms and many others. The latest beta release has been updated with the algorithm changes that came with the draft standards.

EJBCA prend en charge les algorithmes ML-DSA (DILITHIUM) et NL-DSA (FALCON) pour les AC racines, les AC émettrices et les entités finales. Des listes de révocation de certificats (CRL) peuvent être générées, mais certains aspects, tels que le protocole OCSP (Online Certificate Status Protocol) et d'autres protocoles, sont encore en phase de développement et seront disponibles à l'avenir. SignServer prend en charge les algorithmes ML-DSA (DILITHIUM) et SLH-DSA (SPHINCS+) pour les signatures CMS et brutes.

Check out our how-tos and videos, including:

• Mise en place d'une autorité de certification racine ML-DSA et d'une autorité de certification émettrice et émission de votre premier certificat de signature de code prêt pour le quantique avec EJBCA , puis signature de code avec ML-DSA dans SignServer 
• Délivrer des certificats hybrides prêts pour le quantique en utilisant le projet Bouncy Castle Kotlin.