FDA Postmarket Cybersecurity for Digital Therapeutics
Postmarket cybersecurity for digital therapeutics: SBOM monitoring, vulnerability disclosure, field updates, and manufacturer-reviewed risk decisions.
Aligned to FDA's February 3, 2026 premarket cybersecurity guidance.
Postmarket cybersecurity for prescription digital therapeutics and their mobile and web services starts with the deployed system, not just the submission-time SBOM. Mobile releases and backend changes can reach patients on different schedules. Postmarket records need to connect each supported app version to its APIs and therapeutic content. For devices and submissions within Section 524B scope, the statute requires a plan to monitor, identify, and address postmarket vulnerabilities, including coordinated vulnerability disclosure procedures. FDA guidance recommendations and statutory duties are documented separately.
Blue Goat reviews the component inventory against supported field configurations, monitors vulnerability sources, and documents applicability and exploitability evidence for manufacturer review. We can set up or operate coordinated vulnerability disclosure intake and connect technical review to your change-control process. Field-update planning records affected versions, deployment constraints, recovery steps, and customer communications. The scope follows the interfaces your product actually uses.
The response plan needs supported-version rules and a route for patients who cannot install an update immediately. Triage must distinguish data disclosure, interrupted access, and changes to the therapeutic content or prescribed workflow. An advisory or CVSS 4.0 score alone does not establish clinical harm. Your team supplies device-specific safety evidence and approves risk acceptance, VEX statements when used, remediation, and regulatory reporting decisions.
Layers we exercise in this engagement
The digital therapeutics system, from the outermost cloud and clinician surfaces down to the device itself. Highlighted layers are exercised by this fda postmarket cybersecurity.
- 01Prescriber portal Tested
- 02Backend APIs Tested
- 03Patient app Tested
- 04Therapeutic content Tested
- 05Vulnerability intake (CVD) Tested
Layers shown outermost (top) to innermost (bottom). Dashed rows are part of the surrounding system but out of scope for this view.
FDA Postmarket Cybersecurity engagement, end to end
Four phases, fixed fee, scoped to digital therapeutics architecture from kickoff onward.
- 01
Deployed-system scope
Confirm supported software versions, connected components, deployment constraints, and manufacturer owners.
- 02
Monitoring and technical review
Review vulnerability sources against deployed components. Record applicability and exploitability evidence for manufacturer approval.
- 03
Coordinated vulnerability disclosure
Set up or operate intake, triage, and disclosure procedures connected to your change-control process.
- 04
Field response and records
Document remediation options, update and recovery plans, affected configurations, and communications. The manufacturer approves risk, clinical, and reporting decisions.
What we see in Digital Therapeutics fda postmarket cybersecurity
The patterns we hit in this segment, this service, again and again.
Deployed component inventory can be incomplete
An app-store release can leave older patients on dependencies that are no longer monitored.
Field-update coverage can be unclear
The response plan needs supported-version rules and a route for patients who cannot install an update immediately.
Vulnerability triage can miss the clinical context
Triage must distinguish data disclosure, interrupted access, and changes to the therapeutic content or prescribed workflow.
Disclosure intake can be disconnected from change control
A report can remain in a support inbox without an assigned technical owner, affected-version record, or documented manufacturer decision. We review that handoff and the evidence retained for closure.
Standard FDA Postmarket Cybersecurity deliverables
The same deliverables the parent FDA Postmarket Cybersecurity service ships with - tuned to your digital therapeutics architecture.
- Versioned SBOM monitoring and human-reviewed vulnerability applicability records.
- Coordinated vulnerability disclosure procedures, intake, and communication drafts as scoped.
- Device-specific exploitability assessment using manufacturer-supplied patient-harm context.
- Patch-planning recommendations and targeted security retesting when selected.
- Bounded incident support, response playbooks, and tabletop exercises by agreement.
- Cybersecurity record updates for manufacturer review. Your team owns fixes, risk acceptance, release, and reporting decisions.
What lands in your eSTAR submission
Documents structured for the cybersecurity attachments of your submission - no reformatting on your side.
- Versioned SBOM monitoring and human-reviewed vulnerability applicability records.
- Coordinated vulnerability disclosure procedures, intake, and communication drafts as scoped.
- Device-specific exploitability assessment using manufacturer-supplied patient-harm context.
- Patch-planning recommendations and targeted security retesting when selected.
- Bounded incident support, response playbooks, and tabletop exercises by agreement.
Standards that apply
The Digital Therapeutics baseline, plus the call-outs that matter for fda postmarket cybersecurity in this segment.
Segment-specific call-outs
Section 524B + FDA postmarket cybersecurity guidance
We assess statutory applicability separately from guidance recommendations. The postmarket plan records monitoring, disclosure, and remediation procedures for the device in scope.
AAMI TIR97 + ISO/IEC 29147 and 30111
References for postmarket security risk management and coordinated vulnerability disclosure. The manufacturer retains clinical assessment, risk acceptance, and reporting decisions.
What's not in scope
We scope tightly on purpose. These items are either out-of-scope by design or belong in a separate engagement - we'll tell you up front, not after kickoff.
- Manufacturer risk acceptance, clinical decisions, or regulatory reporting decisions
- Automatic VEX conclusions without device-specific evidence and manufacturer approval
- Clinical validation or general software testing
- Firmware implementation or penetration testing unless separately scoped
FDA Postmarket Cybersecurity for Digital Therapeutics - FAQs
The questions buyers in this segment actually ask before scoping a fda postmarket cybersecurity engagement.
Go deeper on Digital Therapeutics and postmarket
A practical, ungated buyer's guide for medical device manufacturers evaluating cybersecurity partners, what goes wrong, why it costs you, and what to demand from your next engagement. Aligned to the FDA February 2026 premarket guidance.
A practical, ungated guide to the threat modeling gaps that trigger FDA cybersecurity questions in 510(k), De Novo, and PMA submissions - and exactly how to close them before reviewers find them.
The most common cybersecurity deficiencies in 510(k), De Novo, and PMA submissions, what triggers each one and how to fix it before you file. Aligned to the FDA February 2026 final guidance and Section 524B.
Medical device remote access security needs named users, bounded privileges, session records, and clinical safeguards. Review service and remote testing paths.
Cybersecurity for small hospitals starts with device inventories, safe remote access, downtime plans, and manufacturer evidence. Separate HHS and FDA roles.
FDA MDDT for cybersecurity: what the qualified MITRE CVSS rubric is, how medical device makers use it to score vulnerabilities, and where its limits are.
Other engagements for Digital Therapeutics
Teams in this segment commonly bundle these alongside fda postmarket cybersecurity.
Keep going
Cybersecurity alerts and guides
Goat's Weekly alerts
Medical device advisories and safety communications, with links to original sources. An alert is a reason to assess applicability, not proof that your device is affected.
Threat modeling, eSTAR 7.1, and SBOM evidence
Connect threats to controls and test evidence. Compare the CISA 2026 SBOM fields with the NTIA 2021 baseline the FDA still cites, plus its support fields. Guidance recommendations remain separate from statutory duties.
Postmarket scope
What is in a postmarket engagement?
Included work is defined in the signed proposal. These scope options are not automatic inclusions in every engagement.
Fixed-fee deliverables
- Vulnerability monitoring against the SBOMs and marketed device versions agreed in scope.
- Triage records that document affected versions, available exploit evidence, existing controls, and the basis for a device-specific assessment.
- Coordinated vulnerability disclosure process support, with named contacts and communication responsibilities.
- Patch-planning support and updates to postmarket cybersecurity records as the device changes. Engineering implementation and release testing remain manufacturer work unless separately scoped.
Required inputs
- A current SBOM for each marketed device version.
- Your postmarket cybersecurity plan, support dates, update process, and complaint-handling and disclosure contacts.
- A named manufacturer owner for clinical severity, risk acceptance, regulatory reporting, customer communications, and release decisions.
Exclusions and separate work
- Penetration testing, tabletop exercises, new submission packages, and major documentation rebuilds are included only by explicit agreement. Monitoring is not a promise to detect every vulnerability.
- General software verification and validation, clinical performance testing, and full QMS implementation or certification are outside Blue Goat's product cybersecurity scope.
- The manufacturer retains engineering changes, clinical-risk evaluation, risk acceptance, release approval, and regulatory submission decisions. No regulatory outcome is promised.
Pricing and scope changes
Fixed fee, quoted after scoping. Tabletop exercises can be included, priced by scope and on-site requirements. Risk acceptance remains a documented manufacturer decision. A written fixed-fee quote after scoping. The proposal names deliverables, versions, assumptions, required inputs, exclusions, and agreed dates. Additional work requires a separately agreed scope change. Missing inputs, access restrictions, manufacturer fixes, and review feedback can affect delivery.
Scope a FDA Postmarket Cybersecurity engagement for your digital therapeutics program.
A 30-minute discovery call with Christian Espinosa, Founder and CEO, and Kristy Kennedy, VP of Sales.
