Secure Update Infrastructure for Medical Devices

Published June 5, 2026

Why this matters

The FDA's Cybersecurity in Medical Devices: Quality Management System Considerations and Content of Premarket Submissions (Feb 3, 2026 final guidance) made cybersecurity documentation a gating criterion for clearance under Section 524B of the FD&C Act. Reviewers now apply this guidance to secure update infrastructure for medical devices the same way they apply software lifecycle expectations from IEC 62304 and security risk-management expectations from AAMI TIR57 and ANSI/AAMI SW96:2023.

Gaps in this area are the single most common driver of first-cycle cybersecurity Additional Information (AI) requests. The FDA's FY2025 MDUFA Performance Report lists cybersecurity among the subject-matter expert areas that may be involved in reviewing a device submission, alongside sterility, biocompatibility and software. Treating it as a checklist exercise rather than a design-controlled engineering artifact is what creates the gap.

Why the update path is the highest-value target

Every other control on the device assumes the firmware it is running is the firmware you shipped. Break that assumption and the rest does not matter.

• One compromise, fleet-wide RCE. A signed-but-malicious image, or an unsigned image accepted by a weak verifier, propagates to every device that polls the update server. The blast radius is the entire installed base, not one device.
• Persistence that survives every other control. Antivirus, EDR, network segmentation, MFA on the clinical workstation - none of them touch the firmware loaded at boot. Compromise the update channel and you survive reboots, factory resets, and incident response.
• Bypasses every downstream control. Secure boot, SBOM-based vulnerability monitoring, runtime integrity checks, and pen-test-derived hardening all assume the device boots the code you signed. If the update path delivers attacker code that is also signed (because the signing key leaked, or the verifier is wrong), those controls validate the wrong artifact.
• The patch path is the malware path. The same channel you use to push security fixes is what an attacker uses to push their payload. If you have not isolated and hardened it, your defense and offense share infrastructure.

This is why reviewers under Section 524B treat updates as a design-input topic rather than a postmarket nicety - and why the same posture should drive your internal engineering priorities.

What the FDA expects in the submission

The Feb 3, 2026 final guidance Cybersecurity in Medical Devices: Quality Management System Considerations and Content of Premarket Submissions does not include a section titled "Update Infrastructure," but the requirements are spread across the package and reviewers ask for all of it.

• Architecture view of the update path. Diagram the manifest source, signing infrastructure, distribution server, transport, update agent, storage banks, and verification points. The same architecture view requirement that covers the device's clinical data flow applies to its update flow.
• Threat model entries that cover the channel end-to-end. Each step gets STRIDE entries: spoofing (fake update server), tampering (modified manifest), repudiation (no audit trail of who signed), information disclosure (leaking signing key, leaking installed-version telemetry), denial of service (force the device into a broken bank), elevation of privilege (update agent compromised → root). See our threat modeling guide.
• Controls traceability. Every threat-model entry maps to a control (signed manifest, anti-downgrade counter, mTLS, HSM-backed signing) and every control maps back to a verification activity in the SPDF.
• Pen-test evidence against the real update infrastructure. A pen test that scopes "the device" but ignores the update server, the signing infrastructure, and the on-device update agent is incomplete. Reviewers increasingly call this out as a deficiency - see 510(k) cybersecurity deficiencies that trigger FDA holds.
• Postmarket patch SLA. The vulnerability management plan must state how fast critical vulnerabilities reach the field. "Within a reasonable time" does not survive review; "critical CVSS within 30 days, high within 60, with VEX published in parallel" does. See SBOM vulnerability management and VEX mistakes that trigger FDA deficiencies.

Reference architecture

The defensible pattern is the same whether you ship one SKU or a hundred. The pieces:

• Signed update manifests. A manifest enumerates the artifact, version, target SKU, and hash. The manifest itself is signed; the artifact hash is in the signed payload, not alongside it. Verify the manifest signature, then verify the artifact matches the hash.
• Dual-bank A/B partitioning. Two firmware banks. The device runs from one; updates land in the other. On successful boot and self-test, the new bank is marked active. On failure, the bootloader falls back to the previous bank. The therapy loop never sees a half-installed update.
• Rollback protection + anti-downgrade counter. A monotonically increasing counter (stored in fused or write-once memory, or in a TPM/SE counter) is incremented on every accepted update. The bootloader refuses any image whose counter is lower than the current one. This blocks attackers from forcing the device back to a known-vulnerable version.
• Hardware root of trust. The signing public key (or the hash of it) is anchored in immutable storage - eFuse, OTP, or a secure element. The boot ROM verifies the bootloader, which verifies the application, which verifies the update agent. No link in the chain trusts on first use.
• Isolated update agent. A small, single-purpose process - no shell, no general-purpose network stack beyond what it needs, no write access to anything except the inactive bank. Ideally a separate UID, separate cgroup, separate seccomp/AppArmor profile.
• Segmented update server. A dedicated host (or namespace) that serves only update artifacts. No shared credentials with telemetry, fleet management, or clinical data stores. Read-only artifact storage with a separate signing host that publishes into it.
• mTLS to a dedicated endpoint. Each device has its own client certificate, provisioned at manufacture and rotated on a schedule. The update server validates the client cert; the device validates the server cert against a pinned issuer. Public-PKI-only or token-only auth is not enough on a device that will live in the field for a decade.

Isolation patterns that hold up

• Separate VLAN or edge gateway. The update endpoint reachable from the device sits on its own segment. The customer's IT can apply the same segmentation in their network using your published port/protocol list (which already lives in your cybersecurity labeling).
• No shared credentials with telemetry or clinical data. Compromising the telemetry pipeline should never grant write access to the update channel. Different keys, different identities, different audit trails.
• Least-privilege service accounts. The update agent owns its own bank and nothing else. The update server's signing host has no inbound network and no SSH from the production fleet network.
• HSM-backed signing. Production signing keys live in a FIPS 140-2 Level 3 (or higher) HSM. The key never leaves the HSM. Signing is a brokered operation with audit logging and dual-control approval for new build promotion.
• Air-gapped signing ceremony. Initial key generation is performed on a clean host with no network, with multiple-party attestation, recorded in a ceremony document the QMS retains. Key recovery, if applicable, uses Shamir splits held by separate custodians.
• Per-environment, per-SKU separation. Development, staging, and production use different signing keys. SKUs that have meaningfully different threat models or service lives get separate roots. A single key for "everything we ever ship" is a single point of catastrophic failure.

TUF and Uptane: when they fit, when they are overkill

TUF (The Update Framework) defines roles (root, targets, snapshot, timestamp) that separate concerns and limit blast radius if any single key is compromised. Uptane is the TUF adaptation for vehicles - and increasingly for any high-assurance embedded fleet. Both are appropriate for medical devices when:

• Heterogeneous fleet with multiple suppliers signing components. TUF's role separation lets you delegate signing of an OS image to one party, an ML model to another, and a config bundle to a third without giving any of them root authority.
• Long device service life with foreseeable key rotation. TUF's root key rotation flow is built for exactly this.
• Multi-tenant update server or shared infrastructure. TUF's snapshot/timestamp roles defend against freeze and mix-and-match attacks that a hand-rolled server probably doesn't address.
• A regulatory environment that will eventually demand it. Automotive went this way; MedTech is on the same trajectory for higher-risk classes.

They are usually overkill when you ship a single product, sign every artifact yourself, control the update server end-to-end, and have a clear and short key-rotation playbook. In that case a careful custom implementation that delivers the same guarantees (signed manifests, anti-downgrade, root-of-trust, dual-bank, isolated agent) is defensible - but document why you chose it over TUF in the security risk file so the reviewer does not have to ask.

Common pen-test findings in update infrastructure

See also: 510(k) Cleared, No Postmarket Cybersecurity: Legal?, FDA PCCP Beyond AI: Cybersecurity & Firmware Uses, and Does FDA 524B Apply to Legacy Medical Devices?.

These are the findings that recur across medical device penetration tests when the update channel is in scope:

• Unsigned images, or signature verification with a bypass. A bootloader that "validates the signature" by checking only that a signature is present. A verifier that hashes the wrong bytes. A verifier called after the image has already been mapped executable.
• Trust on first use. The device accepts whatever key the first update server presents and pins it. An attacker on the first power-on network controls the device for life.
• One signing key across every SKU and every environment. A breach of any non-production system grants production signing authority. We have seen this pattern in firms that otherwise have strong AppSec posture.
• HTTP fallback. TLS is required by config; falls back to HTTP on any TLS error. An on-path attacker forces the fallback by sending a TLS alert.
• No rollback protection. The device accepts any signed image, including a signed older image with a known unpatched vulnerability. Anti-downgrade counter is missing or stored in writable flash.
• Update agent running as root with full network access. A single bug in the parser becomes full device compromise plus arbitrary network egress.
• Update server with shared admin creds. The on-call engineer who manages telemetry can also sign and push updates. No dual control, no audit trail.
• Signing host accessible from the build cluster. A CI/CD compromise becomes a signing-key compromise becomes a fleet compromise.

Each of these maps to a specific control in the reference architecture. The fixes are not exotic - they are operational discipline applied to a system most teams treat as plumbing.

Postmarket: disclose, patch, VEX, deploy - with SLAs

The postmarket cybersecurity management plan in your submission already committed you to specific timelines. The update infrastructure is what lets you keep that commitment.

1. Disclose. A researcher (or internal monitoring) reports a vulnerability. The CVD program triages within the SLA committed in the plan. See our VDP/CVD workflows guide.
2. Patch. Engineering produces a fix, regression tests it, and re-runs the relevant security tests. The fix lands in the next build, signed in the HSM, with an incremented anti-downgrade counter.
3. VEX. Publish a VEX statement describing the affected components (linked to the SBOM), the status (fixed in version X), and any compensating controls customers should apply in the meantime.
4. Deploy. Push through the update infrastructure with the committed SLA - critical within 30 days, high within 60, communicated to operating organizations as required by Section 524B(b)(1).

The same infrastructure that lets you deploy a feature lets you deploy a security fix. The teams that treat updates as plumbing miss every SLA in their own postmarket plan; the teams that treat updates as a safety subsystem hit them.

How Blue Goat Cyber helps

We design and pen-test secure update infrastructure as part of medical device penetration testing and FDA premarket cybersecurity services, including signing infrastructure review, update-agent code review, and end-to-end fleet-side attack scenarios. The deliverable is an architecture view, threat model entries, and pen-test evidence reviewers can read straight into an eSTAR Section 14 - and a postmarket patch SLA you can actually hit.

FAQ

Does Section 524B require dual-bank A/B updates specifically?

No. The statute requires the device to be designed so updates and patches can be made available. Dual-bank A/B is the most common architecture that satisfies that requirement reliably without taking the device offline for the install window. Other architectures (in-place updates with bootloader recovery, package-based updates on a Linux device with snapshot rollback) are acceptable if they deliver the same safety guarantees - documented in the threat model and verified in pen testing.

Where does the postmarket patch SLA live in the submission?

In the postmarket cybersecurity management plan, which Section 524B(b)(1) requires explicitly. The plan should state monitoring sources, triage cadence, severity thresholds, patch-availability SLAs by severity, and customer-notification mechanism. Vague SLAs ("as soon as practicable") are flagged in deficiency letters.

How do we pen-test the update infrastructure without disrupting the production fleet?

A representative staging environment with the same signing keys (lower-privilege equivalents), update server, and a small fleet of test devices. The pen test exercises the manifest signing, transport, agent behavior, rollback, and downgrade defenses against that environment. Findings are remediated and verified before any change to production.

What if our update server is operated by the customer (on-prem hospital deployment)?

Then the device-side defenses carry the entire weight: client-side certificate validation, signed-manifest verification independent of transport, anti-downgrade counter enforced in the bootloader, and a pinned trust anchor that the customer's IT cannot relax. Document the deployment model explicitly so reviewers see that the on-prem variant is not a hole in the trust model.

Should signing keys be rotated on a schedule, or only on compromise?

Both. Plan for routine rotation that exercises the recovery path (typically every 1-3 years for intermediate keys, longer for root) and have an out-of-cycle rotation playbook for compromise. The first time you rotate a key should not be in the middle of an incident.

Related reading

• FDA Section 524B Cybersecurity Requirements Explained
• SBOM Vulnerability Management for Medical Devices
• VEX Mistakes That Trigger FDA Deficiencies
• FDA Cybersecurity Deficiency Response Checklist
• A Step-by-Step Guide to Threat Modeling Connected and Implantable Medical Devices
• Postmarket Cybersecurity Readiness Plan

More on this topic

• Section 524B(b)(2): Medical Device