The DoD Post-Quantum Encryption RFI Asks for an Overlay Its Own Strategy Says Cannot Replace Migration

What the DoD Post-Quantum Encryption RFI Asks For, and Who It Excludes

Sell cryptographic software into defense programs, and the DoD post-quantum encryption RFI is a capture event with a 30-day clock. It also carries an architectural filter. That filter is the most consequential term in the document. The Department of War, the renamed Department of Defense, issued the request as a special notice on Aug. 27, 2026, rather than as a formal request for information. It seeks commercially available, software-only cryptographic solutions to protect its programs of record. Responses close Sept. 27, 2026 at noon Eastern. The notice sits under the Department of Defense, sub-tier Washington Headquarters Services. The contracting shop is the Acquisition Directorate at 1155 Defense Pentagon. This is market research, not a solicitation. No dollar figure, no contract vehicle and no incumbent attach to it. The Department wants interim data protection that advances its post-quantum migration, and that phrase is where the opportunity lives.

Three details in the record do more work than the requirement text:

• The notice type is a special notice, not a formal sources-sought or presolicitation. No conversion timeline is published or implied.
• The NAICS code, product service code and set-aside fields are all blank. The blank classification fields leave the vendor pool and eventual acquisition structure undefined.
• The issuing office is Washington Headquarters Services, not a component command. The requirement sits at enterprise level rather than inside one program.

Why the buyer is asking at all

The strategy’s own foreword says nearly every deployed military asset will be affected in some way by this migration. Where the fix means replacing cryptography, it reaches into fielded equipment. That equipment sits inside systems with controlled baselines and multi-year recertification cycles. The Department needs cover for the years before that work finishes.

The Hardware Exclusion Works as a Vendor Filter

The published description asks for solutions that are software-only. The fuller requirement, as reported, bars any solution needing existing hardware replaced, modified or augmented. It names chips, cryptographic cards, radios and hardware security modules. Read as a filter, that language narrows who can respond credibly.

The Department’s own strategy names three ways to migrate a system. The notice rules out the one that normally applies to cryptographic hardware.

That leaves a narrow band: the product must change the cryptography without changing the system under it. Vendors who depend on a certified hardware module, a new radio waveform or a key management appliance fall outside it. No amount of response-writing moves them back in.

• Hardware security module vendors cannot respond without contradicting the stated constraint.
• Vendors on the high assurance path are on a different track. That path depends on National Security Agency certification and the agency’s key management infrastructure.
• Systems integrator and advisory firms have no product to submit. They still gain a customer conversation from the signal.

The Contradiction a Winning Response Has to Resolve

One sentence in the Department’s Post Quantum Cryptography Strategy sits directly across from this notice. A software overlay that wraps unmodified systems is close to what the strategy rejects.

The two documents reconcile on one word: instead. The strategy bars an overlay substituted for migration. The notice asks for interim protection that advances migration. Pitch a product as a way to skip the 2030 and 2031 dates, and the response argues against the buyer’s own policy. Position the same product as cover during migration, with a defined handoff to the full upgrade, and the response argues from the policy rather than against it. The migration handoff should therefore be explicit at the beginning of any response, before the capability discussion.

Three further rules in the same strategy narrow the target. Each is testable against your product today.

1. Confidentiality alone does not qualify. Solutions lacking post-quantum authentication are not treated as fully post-quantum. An overlay that encrypts traffic but authenticates with classical algorithms fails.
2. Symmetric key establishment, agreement and distribution protocols do not count as quantum resistant. Neither do cryptographic pre-shared keys, outside high assurance devices provisioned through the National Security Agency. Solutions built on them are set for phase-out no later than Dec. 31, 2030.
3. Quantum key distribution and quantum networking are excluded outright. They may not serve as security for confidentiality, authentication, key distribution or randomness.

For National Security Systems, the binding standard behind all of this is CNSA 2.0, the Commercial National Security Algorithm Suite the strategy requires those systems to support. The notice adds three more asks. It wants Department-approved multifactor authentication. It wants unknown parties kept out. It wants full Department control and sovereignty over data and cryptographic keys. Key sovereignty is the quiet self-selector for FedRAMP-pursuing SaaS vendors whose key custody sits with the vendor rather than the customer.

How to Test Your Product Against the Notice Before Sept. 27

Four architectural properties decide whether a response is credible: hardware independence, customer-held keys, post-quantum authentication, and no reliance on pre-shared keys. Each maps to a stated ask in the notice or to a rule in the governing strategy. Test them against your own architecture documents and key custody model, not your marketing copy.

• Hardware independence: The product must operate without changing chips, cryptographic cards, radios or hardware security modules.
• Customer key custody: The customer must retain sole custody of decryption keys.
• Post-quantum authentication: The solution must provide post-quantum authentication rather than only post-quantum confidentiality.
• No prohibited key-management dependency: The solution cannot rely on the excluded pre-shared-key or symmetric key-distribution approaches.
• Write the sentence that separates your product from a substitute for migration. Name the handoff point to a full upgrade.
• For a federal chief information security officer, inventory which programs of record carry cryptography you cannot replace in software.
• For a managed security provider, identify which client programs need this class of overlay, and which product partners clear the rules above.

Competitive Landscape for Software-Only Post-Quantum Products

The respondent pool for the DoD post-quantum encryption RFI is undisclosed. A special notice generates no award record to rebuild one from. The nearby category is documented. QuSecure markets its QuProtect product as software-only crypto-agility, offering post-quantum protection with no new hardware and no replacement of what already runs. The positioning tracks the notice’s own language closely. QuSecure holds six Small Business Innovation Research awards from 2020 to 2024, split between the Army and the Air Force across Phase I and Phase II. Those are service appropriations and service contracting shops. They form a separate acquisition environment from this notice. Prior performance there carries no standing with the Acquisition Directorate running it. Keyfactor and ISARA sit in the same category on the certificate and crypto-agility management side.

Large integrators are not absent. They are positioned differently. A hardware-independent product is what the constraint asks for, so an integrator’s likeliest route here is a software-native partner rather than a direct response. For a small business or mid-market defense firm, that asymmetry is the opening. On this requirement as written, the constraint rewards architecture rather than scale. If your product clears the four properties above, name your own product in a response rather than wait to be pulled in as someone else’s component.

Post-Quantum Requirements Are Headed for CMMC, Without a Compliance Date Yet

The notice asks product vendors for a response. Its consequences reach three groups, and only one has a filing deadline:

• A software vendor with a hardware-independent product should respond by Sept. 27. Address the constraint and the proxy distinction head-on, ahead of capability claims. Shaping happens now, before any requirement is written.
• A federal chief information officer or security officer should treat the notice as an early read on what an interim bridge will look like. Start the hardware-constrained inventory the strategy already requires.
• A DIB prime or DIB sub with no cryptography product still has a stake. The strategy points DIB compliance toward post-quantum requirements inside the Cybersecurity Maturity Model Certification.

That last point is where I would put planning weight. The strategy also commits to updating external certificate authorities to use post-quantum certificates. Both commitments reach Zero Trust and access control platforms across the DIB. That would turn a Department migration into a contractor obligation, once a rule attaches a compliance date. Today no FAR or DFARS clause requires post-quantum cryptography of contractors. The existing flowdown requires FIPS-validated cryptography for covered defense information. The increment here is algorithm replacement inside controls you already run, not a new control family.

Watch for the Department’s own rulemaking attaching post-quantum requirements to CMMC. Watch for a solicitation or industry day following this notice. Either turns a shaping posture into an active pursuit. A close with no follow-on action within two to three quarters puts it back on the watch list.

FAQ

Who owns the budget for this requirement?

No budget owner is identified. The notice carries no dollar figure, no appropriation line and no program element. That is normal for market research, which is why this stays a shaping opportunity rather than a pursuit.

Which contracting shop would run a follow-on competition?

The Washington Headquarters Services Acquisition Directorate issued the notice. That points to an enterprise-level buy rather than a component or program-office action. A follow-on could still move to a component command or to a consortium-based instrument.

Does responding create an advantage in a later competition?

Responding shapes requirements, which carries real value. The notice itself creates no preference and no relationship. Broad eligibility language says who may respond, not who will be favored later.

Will this become a CMMC requirement for defense contractors?

The governing strategy commits the Department to updating CMMC to include post-quantum cryptography requirements. No rulemaking with a compliance date exists yet. The obligation is directional, not enforceable.

What would invalidate the vendor-filter thesis?

A follow-on solicitation that reopens hardware modification would break the vendor-filter thesis. So would one that routes the requirement to the high assurance track instead of the commercial solutions track. So would the notice closing with no acquisition action.

What are the next observable events?

The Sept. 27 response deadline and the Oct. 12 inactive date come first. After that, watch for any industry day or draft solicitation the Department announces, and for the first post-quantum language in certification rulemaking.