Q-Day: A Present-Day FDA Compliance Gap

By Christian Espinosa, Founder & CEO, Blue Goat Cyber

Last week I sat on a neurotech panel and made a point that landed harder than I expected: the implants we're putting in patients today are designed to last 10 to 20 years, but the cryptography protecting them won't. The CNN piece on Q-Day that's been making the rounds frames quantum computing as a looming cybersecurity crisis, and it is. But for medical devices, the framing is wrong. This isn't a future problem we have time to plan for. It is a lifecycle risk that manufacturers should assess; the guidance does not make every classical-cryptography device currently noncompliant.

Why this matters

The stakes are high: patient safety and regulatory compliance. Medical devices, especially long-lived implants, face a unique threat from quantum computing. Cryptography considered secure today (e.g., RSA, ECC) will likely be vulnerable to cryptographically relevant quantum computers within the operational lifespan of many currently implanted devices. The potential for "harvest now, decrypt later" attacks, where encrypted patient data is exfiltrated today and decrypted years later with quantum computers, poses a severe risk to patient privacy and trust.

The FDA's 'Cybersecurity in Medical Devices' Final Guidance, dated February 3, 2026, recommends cryptography "expected to be considered cryptographically strong throughout the service life of the device." This guidance, alongside standards like IEC 81001-5-1 and AAMI SW96, creates a lifecycle planning concern for devices with a 10-20 year service life that do not account for post-quantum cryptographic transitions. Failure to address this could lead to significant regulatory hurdles, market access delays, and post-market cybersecurity vulnerabilities.

Official sources: FDA, Cybersecurity in Medical Devices: Quality Management System Considerations and Content of Premarket Submissions (February 2026); FDA eSTAR Program; FDA Cybersecurity in Medical Devices FAQs (Section 524B).

The FDA Recommends Lifecycle Cryptographic Strength

Here's the language that matters. The FDA's February 2026 Premarket Cybersecurity Guidance tells manufacturers to use cryptography "expected to be considered cryptographically strong throughout the service life of the device." Read that sentence with a pacemaker in mind. Or a neurostimulator. Or an implantable cardioverter-defibrillator. Or an insulin pump. These devices stay in patients for a decade or two. The crypto running on most of them today - RSA and elliptic curve - will not survive that window once a cryptographically relevant quantum computer arrives. The FDA recommends lifecycle cryptographic strength, not a universal PQC migration deadline.

I review premarket submissions for a living, and I can tell you what I'm not seeing. I'm not seeing threat models that include a quantum adversary. I'm not seeing cryptographic agility designed into the device architecture. I'm not seeing migration plans for post-quantum cryptography in the Secure Product Development Framework documentation. The FDA guidance also says manufacturers should not implement deprecated algorithms, and that anything in "legacy use" status needs to be discussed with the agency at pre-submission. Once NIST formally deprecates RSA and ECC for the post-quantum era - and that timeline is shortening - every device shipping with classical-only crypto is going to be in that conversation whether the manufacturer wants to be or not.

Harvest Now, Decrypt Later - But the Patient Is Still Wearing the Device

The "harvest now, decrypt later" risk lands harder for medical devices than for almost any other sector. If an attacker captures biosignals from an implant today - cardiac rhythms, neural telemetry, continuous glucose data - that data stays sensitive for the patient's entire life. And the device transmitting it is still in their body when quantum decryption becomes practical.

The data outlives the crypto. The hardware outlives the crypto.

For a banking transaction, the exposure window closes when the account closes. For a neural implant, it doesn't close until the patient does. That's the asymmetry MedTech leaders need to internalize.

The Tools to Fix This Already Exist

The good news is the tools to fix this already exist. NIST finalized the first post-quantum cryptography standards in August 2024: ML-KEM for key encapsulation, ML-DSA and SLH-DSA for digital signatures. These are not research-grade. They're production-ready, and hybrid schemes that pair classical and post-quantum crypto are deployable today.

For the algorithm-by-algorithm detail, the flash and bandwidth costs on constrained hardware, and the published migration deadlines, see our guide to post-quantum cryptography for medical devices.

The path forward for medical device manufacturers is not "go build a quantum-proof device from scratch." It's three concrete steps that can be implemented now.

1. Design for cryptographic agility

See also: 8 FDA Cybersecurity Documentation Gaps to Review, FDA IDE Cybersecurity Requirements: 2026, and SBOM Diffing and CVE Correlation: A Practical Workflow Supporting Section 524B Duties.

New devices entering premarket today should be architected so that cryptographic algorithms can be swapped without replacing the device. That means modular crypto libraries, sufficient compute and memory headroom, and a secure update mechanism enough to push a PQC migration over the air. The FDA's guidance recommends secure update capabilities and lifecycle cryptographic planning. Quantum just raises the stakes.

2. Assess hybrid classical+PQC schemes based on device risk and service life

Hybrid approaches give you classical security against today's threats and post-quantum security against harvest-now-decrypt-later attacks. This is what cloud providers, browsers, and messaging platforms are already doing. There's no reason medical device manufacturers should be behind that curve.

3. Document a PQC migration plan in your SPDF

When the FDA asks how your device will remain cryptographically strong over its service life - and they will ask - you need an answer that isn't "we'll figure it out." A documented migration plan, with milestones tied to NIST's deprecation timeline, is what a defensible submission looks like.

This Isn't Theoretical Anymore

None of this is theoretical. The standards are published. The FDA guidance is signed. The threat model is real, and for the devices we're putting in patients today, the timeline is shorter than the device's own warranty card.

Quantum risk warrants planning now, but the FDA has not imposed a universal PQC migration requirement. The work to close that gap starts now, in the next premarket submission, not in the next decade.

How Blue Goat approaches this

Blue Goat Cyber helps medical device manufacturers work through the changing cybersecurity environment, including the challenges posed by Q-Day. Our methodology centers on integrating forward-looking security directly into the product lifecycle. We specialize in developing Secure Product Development Frameworks (SPDFs) that incorporate cryptographic agility and PQC migration strategies, ensuring devices remain compliant and secure throughout their long service lives.

Our team of experts, including CISSP and OSCP-certified professionals with ex-military red team experience, provides actionable guidance for threat modeling, architectural reviews, and secure code development. We assist in designing hybrid classical+PQC solutions and validating their implementation. If the FDA raises a cybersecurity question, we answer it at no extra cost until the cybersecurity portion is closed. Learn more about our services at Medical Device Penetration Testing.

Faq