Skip to content
Skip to content
Cybersecurity

Post quantum cryptography meets the medical device: a headline that overreads its data

Summarise with

Only 6% of IoMT devices run post-quantum-capable SSH today. That is a sharp number, and a narrower one than the headline suggests. The marketing prize goes to the vendor who can tell the difference.

Quick answerPost quantum cryptography support is thin in healthcare: Forescout found 6% of IoMT and 16% of OT devices run capable SSH today. It is a protocol snapshot, so market inventory and compensating controls, not quantum-safe promises.

Audio version

Listen to this article. The full text is below.

9 min · narrated · download

Section 01

Forescout's number, and what it actually measures#

A fox learns to distrust the loudest track in the snow, because the loudest track is rarely the freshest, and it follows the scent back to the source. The loud one this week is a headline that says critical medical devices cannot support the post quantum cryptography transition. Infosecurity Magazine ran it on 6 October, and the post below shows how quickly the wording drifted on the way to a social feed.

@shah_sheikh
Critical Medical Devices Unable to Support PQC Transition: Forescout found that just 6% of Internet of Medical Things (IoMT) and 16% of medical OT are capable of supporting post quantum cryptography
6 October 2026View on X

Read the original and the claim narrows. Forescout's research says only 6% of IoMT devices and 16% of OT devices currently use SSH implementations that support post-quantum cryptography, against 50% of IT devices. That is a measurement of one protocol on one date, not a verdict that these devices cannot be upgraded. The distinction matters because a security vendor who repeats the headline will be corrected by the first informed buyer.

Post quantum cryptography support in SSH, by device class
Ladder chart of post quantum cryptography support in SSH: 6 per cent of IoMT devices, 16 per cent of OT devices and 50 per cent of IT devicesShare running post-quantum-capable SSH0102030405060IoMT devices: 6%IoMT devices6%OT devices: 16%OT devices16%IT devices: 50%IT devices50%
Ladder chart of post quantum cryptography support in SSH: 6 per cent of IoMT devices, 16 per cent of OT devices and 50 per cent of IT devices
ItemValue
IoMT devices6%
OT devices16%
IT devices50%
Share of devices in Forescout's Device Cloud dataset that currently use SSH implementations supporting post-quantum cryptography. It measures one protocol on one date, not whether a device can be upgraded.

Then the samples. The device figures come from a dataset of more than 2.5 million devices across more than 50 networks of healthcare delivery organisations, which are Forescout's own customers. A separate query of the Shodan search engine found over 5,500 exposed instances of 50 different medical information systems, and that is where the next figures come from. Of those exposed systems, only 31% support TLS 1.3, and 15% still support TLS 1.0 or 1.1. Two samples, two methods, one headline: always ask which dataset a figure belongs to.

  • 6%

    of IoMT devices run post-quantum-capable SSH today

  • 16%

    of OT devices in the same dataset

  • 31%

    of exposed healthcare systems support TLS 1.3

  • 2.5m

    devices in the underlying Device Cloud dataset

Section 02

Why harvest now decrypt later suits a device that lives for a decade#

The threat that makes this a buyer's problem rather than a physicist's is harvest now decrypt later: an adversary records encrypted traffic today and waits until a quantum computer can read it. Forescout is careful here, and so should you be. Its report says the greatest near-term concern is not that quantum attacks are already happening. The concern is that data with a long shelf life, such as a patient record, will still be sensitive when decryption becomes possible.

Healthcare is the sector where shelf life is longest, and the devices are the slowest to change. A peer-reviewed comment in npj Digital Medicine reports that once certified, devices are rarely updated to meet new cryptographic standards. The imaging association COCIR adds a hint of how long the installed base lingers, noting that medical technology more than ten years old is outdated and hard to maintain. Equipment bought now can be in a ward in 2035.

watercolour fox holding a locked strongbox and an hourglass, illustrating post quantum cryptography and the harvest now decrypt later risk
Locked today, read tomorrow: the clock that matters.

None of that excuses delay, because the migration is a long trail through the undergrowth even when the threat is distant. The one hard cost anchor we found is the US federal estimate: the White House report put the work for prioritised federal systems at approximately $7.1 billion in 2024 dollars. It covers government systems, not hospitals, so treat it as a scale marker, not a forecast for healthcare.

Section 03

The post quantum cryptography deadlines a device maker can date#

Some dates are real and some are rumours, so here are the ones with a document behind them. NIST published its first post-quantum standards in August 2024, and says of the key-encapsulation standard that ML-KEM is believed to be secure even against an adversary with a quantum computer, with a matching statement in the signature standard. NIST's transition draft, still a draft as of today, sets the line for older algorithms: 112 bits of security strength deprecated after 2030, disallowed after 2035.

Outside the US, the UK's National Cyber Security Centre asks organisations to carry out a full discovery exercise by 2028 and to complete migration of all systems, services and products by 2035. The EU's coordinated roadmap, from the NIS Cooperation Group, says that by 2035 the transition should be completed for as many systems as practically feasible.

The dated milestones for post quantum cryptography, 2026 to 2035
The dated milestones for post quantum cryptography, 2026 to 2035Timeline of post quantum cryptography milestones: NCSC discovery by 2028, a scenario of quantum risk from 2029, NIST deprecation after 2030, NCSC priority migration by 2031, and 2035 for NCSC completion and NIST disallowance2026-10-07: Forescout analysis published07 Oct 26Forescout analysis published2028-12-31: NCSC: discovery done31 Dec 28NCSC: discovery done2029-06-30: Forescout scenario: earliest risk30 Jun 29Forescout scenario: earliest risk2030-12-31: NIST: older algorithms deprecated31 Dec 30NIST: older algorithms deprecated2031-12-31: NCSC: priority migration31 Dec 31NCSC: priority migration2035-12-31: NCSC and NIST: end point31 Dec 35NCSC and NIST: end point
Timeline of post quantum cryptography milestones: NCSC discovery by 2028, a scenario of quantum risk from 2029, NIST deprecation after 2030, NCSC priority migration by 2031, and 2035 for NCSC completion and NIST disallowance
ItemValue
2026-10-07Forescout analysis published
2028-12-31NCSC: discovery done
2029-06-30Forescout scenario: earliest risk
2030-12-31NIST: older algorithms deprecated
2031-12-31NCSC: priority migration
2035-12-31NCSC and NIST: end point
Dates from the NCSC guidance, NIST's draft IR 8547 and the EU coordinated roadmap linked in this section. The 2029 quantum date is Forescout's planning scenario, not a published deadline.

Regulators for devices have not yet put a post-quantum date on the box. The FDA's final cybersecurity guidance, dated February 2026, gives recommendations on device design, labelling and premarket documentation, and section 524B of the Food, Drug and Cosmetic Act requires a plan to monitor, identify and address postmarket cybersecurity vulnerabilities and a software bill of materials. In Europe, MDCG 2019-16 asks that manufacturers demonstrate state of the art, and we found no post-quantum wording in it. A 2025 gap analysis found that both guidance documents have unclear scope and thematic gaps.

In the US, even the privacy rule is moving slowly: the proposed HIPAA Security Rule notes that experts anticipate that quantum computing will adversely affect digital communications, yet the HIPAA Journal reports a final rule postponed until July 2027.

Section 04

Medical device security claims that stay true#

Now the marketing question, which is where folkfox earns its keep. Every security vendor selling into hospitals will start saying quantum-safe in the next year, and most of them will be saying more than the product can prove. Forescout names the reason itself: low-agility environments include regulated medical devices where changing a cipher can mean recertification or new hardware. A claim of readiness that ignores that is an invitation to be quoted back.

A folkfox editorial framework, not a regulatory standard: the evidence column is what a sceptical hospital buyer or regulator could ask to see.
ClaimRiskWhat you must be able to show
Quantum-safeHighEvery algorithm, protocol and dependency in scope has been tested; almost never provable
Supports NIST-standardised algorithmsMediumNamed algorithms and versions, per product release
Crypto-agileMediumHow an algorithm is replaced, and whether that triggers recertification
Inventory of cryptographic dependenciesLowA dated discovery report for a named estate
Compensating controls in front of legacy devicesLowThe gateway or segmentation design and its tested limits
  • Quantum-safeHighEvery algorithm, protocol and dependency in scope has been tested; almost never provable
  • Supports NIST-standardised algorithmsMediumNamed algorithms and versions, per product release
  • Crypto-agileMediumHow an algorithm is replaced, and whether that triggers recertification
  • Inventory of cryptographic dependenciesLowA dated discovery report for a named estate
  • Compensating controls in front of legacy devicesLowThe gateway or segmentation design and its tested limits

The honest rungs sell well, and they sit snugly in the hedgerow of what buyers already ask: what do we have, and what can we do about the part we cannot change? Forescout's own advice is to plan for PQC gateways and secure remote access in front of legacy systems, which is exactly the sort of concrete, checkable offer that a marketing page can state without flinching.

For a vendor, the content strategy follows from the claims ladder. Write the explainer on harvest now decrypt later for the chief information security officer, the inventory checklist for the biomedical engineer and the procurement language for the buyer, and keep the three voices distinct. Our cybersecurity marketing work and healthcare marketing work meet at exactly this point: regulated audience, evidence-led claims, long sales cycle. Related patterns appear in our piece on AI medical devices and the claim a regulator can quote back and in the ENISA threat landscape analysis.

Five moves for a healthcare security vendor
Name the dataset

Attach a source, a sample and a date to every statistic, including your own.

Retire the word safe

Replace quantum-safe with a claim you can show: named algorithms, a dated inventory or a tested gateway design.

Separate the audiences

Write one page for the security leader, one for the device engineer and one for procurement.

Offer the discovery step

Position the cryptographic inventory as the first deliverable, since the NCSC asks for discovery by 2028.

Date your content

Put the as-of date in the prose, because this field's claims go stale in a quarter.

None of this requires a shield, a padlock or a drumbeat of fear, and none of it needs a quarry of scare statistics. It requires the patience of a fox at a shuttered window: listen first, learn what is actually in the house, and speak only once you can say it plainly. The buyers in this field have heard every alarm, and they trust the vendor who sounds like an engineer.

Questions

Frequently asked questions#

What is cybersecurity in medical devices?

It is the practice of keeping connected medical devices secure across design, manufacture and use: protecting their data and functions, managing vulnerabilities after sale and documenting this for regulators. In the US, section 524B requires a postmarket plan and a software bill of materials.

What is post quantum cryptography?

Post quantum cryptography means encryption and signature algorithms designed to resist attack by quantum computers. NIST published its first standards, including ML-KEM and ML-DSA, in August 2024, and describes both as believed to be secure even against adversaries with a quantum computer.

What does harvest now decrypt later mean for hospitals?

It means an attacker records encrypted traffic or data today and decrypts it once a capable quantum computer exists. Hospitals hold data that stays sensitive for decades, so long-lived records and long-lived devices are the exposed pairing. Forescout says the near-term concern is future decryption, not attacks happening now.

What did Forescout actually find about IoMT security?

Forescout found only 6% of IoMT devices and 16% of OT devices in its dataset currently use SSH implementations supporting post-quantum cryptography, against 50% of IT devices. It measures one protocol on one date, not whether devices can be upgraded.

How should vendors market healthcare cybersecurity and PQC readiness?

Avoid the unprovable phrase quantum-safe. Claim what you can show: named NIST algorithms and versions, a dated cryptographic inventory, how algorithm changes are made and whether they trigger recertification, and tested compensating controls. Attach a source, sample and date to every statistic.

When do UK and EU timelines require post-quantum migration?

The UK NCSC asks for discovery by 2028, priority migration by 2031 and completion by 2035. The EU coordinated roadmap says that by 2035 the transition should be completed for as many systems as practically feasible. Both are guidance rather than device-specific law.

Keep reading

Read more on this topic#

Selling security into hospitals and want claims that hold?

folkfox writes evidence-led content for regulated security vendors: sourced statistics, claims ladders and pages a hospital buyer will trust.

Want folkfox in your Google results and AI answers? Set folkfox as a preferred source.

The den

Where to?

Pricing

Choose a section. Enter opens it, Escape continues reading.

Cookie preferences

folkfox uses data the way we use strategy: only when it earns its place.