Counsel for the
frontier of computation

PracticePost-Quantum Cryptography

Counsel for the post-quantum transition.

From patent rights to customer commitments.

Contact
The post-quantum transition, algorithm by algorithmRSA and ECDH key establishment is replaced by ML-KEM, FIPS 203. RSA and ECDSA signatures are replaced by ML-DSA, FIPS 204, and SLH-DSA, FIPS 205. The three standards were published in August 2024, and CNSA 2.0 is required in new national security system products from January 1, 2027.IN USE TODAYSTANDARDIZED REPLACEMENTSRSA, ECDHkey establishmentRSA, ECDSAsignaturesML-KEMFIPS 203ML-DSAFIPS 204SLH-DSAFIPS 205Aug 2024FIPS 203, 204, 205publishedJan 1, 2027CNSA 2.0 required in newnational security system products

Post-quantum cryptography has moved from a research competition to a set of dated requirements. NIST has published its first standards, federal policy has fixed deadlines for replacing quantum-vulnerable algorithms, and customers are writing those deadlines into contracts. CipherLaw advises the companies that build, sell, and invest in this technology on what they own, what they may use, and what they have promised.

Our lawyers work alongside researchers in cryptography and quantum information. We read the specification and the implementation before we advise, and we support that work with PQScope, research tooling we built to connect post-quantum research, standards activity, implementations, and patent disclosures.

The requirements now have dates. Suppliers to U.S. National Security Systems must provide CNSA 2.0 algorithms in new products from January 1, 2027. Federal agencies must move their most sensitive systems to post-quantum key establishment by the end of 2030. Each date reaches private companies through procurement terms and customer contracts.

The exposure has already begun. Encrypted data captured today can be stored and decrypted once a capable quantum computer exists. A confidentiality obligation that runs for ten years is at risk from this “harvest now, decrypt later” problem before any deadline arrives.

Companies are making claims they must be able to support. “Quantum-safe,” “PQC-ready,” and “crypto-agile” appear in product literature, questionnaire responses, and deal documents. Each is a representation, and each will be tested against the implementation actually supplied.

The rights are not fully settled. Royalty-free licenses cover certain patent portfolios relevant to ML-KEM. They do not cover every design choice in a product. Hardware acceleration, side-channel countermeasures, hybrid constructions, and protocol integrations each raise their own questions.

The dates that drive decisions

Who is affected Requirement Date
Suppliers to National Security Systems CNSA 2.0 algorithms in all new products and services January 1, 2027
Vendors seeking NIAP evaluation Products must meet CNSA 2.0 for every cryptographic function to enter evaluation January 1, 2028
Federal high value assets and high impact systems Post-quantum key establishment December 31, 2030
National Security Systems Equipment that cannot be updated to CNSA 2.0 phased out December 31, 2030
Federal high value assets and high impact systems Post-quantum digital signatures December 31, 2031
National Security Systems CNSA 2.0 mandated for all protocol use December 31, 2031
Users of NIST standards Quantum-vulnerable public-key algorithms deprecated, then disallowed After 2030, then after 2035

No single deadline governs every organization. Our research sets out which requirement applies to whom: PQC migration deadlines and readiness evidence for the civilian schedule, and CNSA 2.0 requirements, timeline, and compliance for National Security Systems and their suppliers.

Where we advise

Patents on post-quantum inventions

The algorithms are standardized. The patentable advances are in how they are implemented: faster arithmetic in hardware, defenses against side-channel attacks, protocol designs that carry larger keys, and mechanisms for replacing one algorithm with another. We identify those advances while the engineering is underway and draft claims around the technical contribution.

The appellate record is nearly empty. The Patent Trial and Appeal Board has ruled on a quantum-resistant construction once, and the applicant won. Our analysis of that decision and what it means for a post-quantum portfolio explains how to build a prosecution record for a field with almost no precedent. Our software and AI patent practice handles the filings.

Implementation and licensing rights

Before a product ships, we assess which third-party patent claims and license terms bear on the design the team has actually chosen. The published licenses are the starting point, and the analysis continues through every feature they do not reach. Our standards and IP strategy practice conducts these freedom-to-operate reviews and advises on design changes or licenses where risk appears.

Standards contributions

Publishing a paper, releasing code, submitting a proposal, and filing a patent application are connected decisions. We advise research groups and product teams on the disclosure and licensing commitments each standards body requires, and on how to protect an invention without impeding adoption of the standard it supports.

Compliance and customer commitments

We determine which post-quantum requirements bind a company, review the migration dates and readiness statements it is asked to give, and test them against the product version and the supplier commitments behind it. Our PQC compliance practice covers procurement responses, flow-down terms, security representations, and the contract language that allocates migration risk.

Investment and acquisition diligence

A target that describes itself as quantum-safe, or that depends on cryptography with a short remaining life, presents a diligence question with a price attached. We assess the claims, the migration exposure, and the patent position as part of our IP due diligence work for investors and acquirers.

Who we work with

  • Product teams shipping a post-quantum implementation, who need to know what they can patent and which rights they need.
  • Suppliers asked by a customer to commit to a migration date or to certify a product as compliant.
  • Research organizations preparing a standards submission or deciding when to publish and when to file.
  • Investors and acquirers evaluating a company whose value depends on cryptographic claims.
  • General counsel who need to know which post-quantum requirements apply to the business and what to do first.

The research behind the advice

Our advice rests on technical work we do ourselves.

  • Practice lead Jim Denaro developed the foundational patents on functional encryption and attribute-based encryption and prosecuted them into a portfolio that was later purchased. He previously served as in-house IP counsel at a cybersecurity company.
  • Technical advisor Joseph Carolan is a researcher in quantum information whose work addresses the security of cryptographic constructions against quantum adversaries, including the sponge construction underlying SHA-3.
  • PQScope gives each engagement a source-linked record of the research, standards proposals, implementations, and patent disclosures that bear on the question.

More about the team.

Selected research:

Contact CipherLaw about a post-quantum implementation, a standards contribution, a compliance commitment, or a transaction.

Clients often bring us in when

  • a product is adopting the new algorithms
  • a customer wants a migration commitment
  • a deal turns on cryptographic claims
Contact