Blog · Postmarket

    Medical Device Security Advisor: After FDA Clearance

    What a medical device security advisor does after FDA clearance: keeping the threat model and SBOM current, rating vulnerabilities, and answering hospitals.

    Security engineer and product manager reviewing a wearable medical device and a software component list on a laptop
    On this page
    Christian Espinosa, Founder & CEO at Blue Goat Cyber

    By Christian Espinosa, MBA

    Founder & CEO · Blue Goat Cyber

    Published:

    Key Takeaways

    • [Postmarket cybersecurity](/services/fda-postmarket-cybersecurity-services "FDA postmarket cybersecurity services") is a legal duty for cyber devices under Section 524B, not an optional extra.
    • The [threat model](/services/medical-device-threat-modeling "FDA-aligned threat modeling services"), SBOM, and security risk file go stale with every release unless someone owns them.
    • New vulnerabilities need a patient-harm rating, not just a CVSS score, before you decide how to respond.
    • Hospital security questionnaires are easier and faster when the answers come from current files.
    • A medical device security advisor works on the product, not your company's IT, and is not a CISO.
    • Current files make the next 510(k), De Novo, PMA, or PCCP change start from accurate evidence.
    Direct Answer

    After FDA clearance, a medical device security advisor keeps your cybersecurity evidence true to the device you actually ship. They update the threat model and SBOM when software changes, rate new vulnerabilities for patient harm, decide which fixes need a customer notice, answer hospital security questionnaires, and flag when a change may need a new submission. It is ongoing postmarket cybersecurity work, done by someone who already knows your device.

    Reviewed October 14, 2026

    Clearance feels like the finish line. For cybersecurity, it is closer to the start. The documents you filed describe the device on the day you submitted it, and every release, new component, and newly published vulnerability makes them less accurate.

    The law expects you to keep up. Section 524B of the FD&C Act requires makers of cyber devices to monitor and address vulnerabilities after launch and to provide updates and patches. The FDA's December 2016 final guidance, Postmarket Management of Cybersecurity in Medical Devices, is still the agency's dedicated postmarket guidance.

    Most device companies do not have a full-time product security lead to own this. A medical device security advisor fills that gap on a retainer, and this post explains what that work looks like week to week.

    Why This Matters

    Section 524B took effect on March 29, 2023. For any cyber device, it requires a plan to monitor, identify, and address postmarket vulnerabilities, a process to provide updates and patches, and a software bill of materials. Those duties do not end when the clearance letter arrives.

    The FDA's postmarket expectations are set out in the December 28, 2016 final guidance, Postmarket Management of Cybersecurity in Medical Devices. It asks manufacturers to judge whether a vulnerability poses an uncontrolled or controlled risk to patients and to respond accordingly. The February 3, 2026 premarket guidance, Cybersecurity in Medical Devices: Quality System Considerations and Content of Premarket Submissions, adds that the plans you file should describe how you will actually run this work.

    Hospitals add their own pressure. Many ask for an MDS2 form, an SBOM, and answers to long security questionnaires before they buy or renew.

    The standards behind this work include ANSI/AAMI SW96:2023 and AAMI TIR57 for security risk management, IEC 81001-5-1 for the secure product lifecycle, and ISO 14971 for patient safety risk. Keeping all of them aligned after launch is where most teams fall behind.

    Official sources: FDA, Cybersecurity in Medical Devices: Quality Management System Considerations and Content of Premarket Submissions (February 2026); CISA Software Bill of Materials resources; HHS HIPAA for Professionals; CISA Cybersecurity Advisories (including ICS medical advisories).

    What changes after clearance?

    The device keeps changing, and so does the world around it. Engineering ships fixes and features, third-party libraries publish new versions, and researchers find new weaknesses in components you already use.

    Each of those events can make your filed evidence wrong. The threat model may miss a new interface. The SBOM may list an old version. The risk file may rate a threat that is now easier to exploit.

    Key requirement

    Under Section 524B, a cyber device maker must have a plan to monitor, identify, and address postmarket cybersecurity vulnerabilities, and must provide updates and patches.

    What does the advisor do each week?

    The advisor spends the retainer on whatever matters most that week. The most common work falls into four groups.

    AreaTypical work
    Files kept currentUpdate the threat model, SBOM, and security risk file when the design or components change
    VulnerabilitiesReview new CVEs in your components, rate patient harm, and recommend patch and notice decisions
    QuestionsAnswer FDA, Notified Body, hospital, and customer security questions
    Next submissionDraft security content for new submissions and PCCP changes, and scope testing

    You get a short written summary each week of what was done and what comes next. That record is useful evidence on its own when the FDA or an auditor asks how you run postmarket cybersecurity.

    How are new vulnerabilities handled?

    Every relevant vulnerability gets a patient-harm rating before anyone decides what to do. A high CVSS score on a component nobody can reach may matter less than a medium score on the Bluetooth stack.

    The advisor checks whether the vulnerable code is present and reachable, ties the threat to a hazard in your ISO 14971 file, and recommends a response. That might be a routine patch, a faster fix with a customer notice, or a documented decision that no action is needed. If outside researchers report an issue, the advisor helps run coordinated disclosure.

    How does the advisor help with hospitals?

    See also: CISA KEV Catalog: Prioritize Device Risk, Hospital Security Questions for AI Medical Devices: Answers, and SBOM for SaMD and Cloud Components: FDA Guide.

    Hospital security reviews go faster when the answers already exist. The advisor answers questionnaires and keeps the MDS2 form and SBOM current, using the same evidence you gave the FDA.

    That consistency matters. When a hospital's answers and your FDA file disagree, the review stalls while someone works out which one is right. See passing hospital security reviews for the wider process.

    When does a change need a new submission?

    Some changes can be documented in a letter to file, and others need a new 510(k). The advisor reviews each planned change for its security impact and flags when it may cross that line, so your regulatory team can decide early.

    A Predetermined Change Control Plan can cover some planned changes in advance. The advisor makes sure each change in the plan carries its security analysis and tests. See letter to file vs new 510(k) for cybersecurity changes for the decision in detail.

    Advisor, project, or full-time hire?

    Each option fits a different need. Projects suit one clear deliverable, a full-time hire suits large portfolios, and an advisor suits steady work that needs senior judgment but not 40 hours a week.

    OptionBest forTrade-off
    One-time projectA pen test, threat model, or submission packageStarts cold each time
    Advisory retainerOngoing postmarket work and questionsWeekly time, not full time
    Full-time hireLarge device portfoliosHard to find, slower to start

    Need ongoing help after clearance? Our medical device security advisory puts a senior advisor on your team every week.

    How Blue Goat Cyber Approaches This

    Blue Goat Cyber works only on medical device cybersecurity and has supported 275+ devices. Our MedTech Cybersecurity Advisory is a monthly retainer, starting at $5,000 a month, with a named senior advisor who learns your device and stays with it.

    Onboarding starts with your threat model, SBOM, risk file, and open questions. From there, the advisor joins your Slack and meetings, works the most important items each week, and sends a short written summary. Larger work, such as a penetration test, a full premarket package, or a deficiency response, is scoped separately as a fixed-fee project, so the retainer stays free for weekly work.

    The focus is the product: the device, its apps, and its cloud service. We do not run corporate IT security, and the service is not a CISO. If the FDA raises cybersecurity deficiencies after our submission, we resolve them at no additional cost.

    Related reading: SBOM for SaMD and Cloud Components: What the FDA Expects in 2026.

    Frequently Asked Questions

    What does a medical device security advisor do after FDA clearance?

    They keep your cybersecurity evidence accurate as the device changes. That includes updating the threat model and SBOM after releases, rating new vulnerabilities for patient harm, recommending patch and customer-notice decisions, answering hospital security questionnaires, and flagging changes that may need a new submission. The work is weekly and ongoing, done by someone who already knows your device.

    Is a medical device security advisory the same as a CISO?

    No. A CISO protects a company's own networks, laptops, and email. A medical device security advisory protects the product: the device, its apps, and its cloud service, plus the evidence the FDA and hospitals expect for them. Many device companies need product security help long before they need, or can afford, a corporate security leader.

    Do we still need postmarket cybersecurity work if the device is already cleared?

    Yes. This is a common misconception. Section 524B requires makers of cyber devices to monitor and address vulnerabilities and to provide updates and patches after launch. Clearance confirms your plans; it does not finish the work. New vulnerabilities in your components appear every month, and the FDA expects you to respond to them.

    How much does a medical device security advisory cost?

    Blue Goat Cyber's MedTech Cybersecurity Advisory starts at $5,000 a month, billed as a fixed monthly retainer. Penetration tests, full premarket packages, and deficiency responses are scoped separately as fixed-fee projects. The retainer covers weekly advisory work, file upkeep, vulnerability review, and answers to FDA and hospital questions.

    Can an advisor help with our next submission?

    Yes. Because the files stay current, the cybersecurity part of a new 510(k), De Novo, PMA, or PCCP change starts from accurate documents instead of a rebuild. The advisor drafts the security content and scopes any testing you need. That usually shortens preparation and reduces the chance of cybersecurity questions from the FDA.

    CTA

    Want a senior device security advisor on your team every week after clearance? Book a free discovery call and we will review your device, files, and open questions, then confirm whether the retainer fits. If the FDA raises cybersecurity deficiencies after our submission, we resolve them at no additional cost. Book a discovery call.

    About the author

    Christian Espinosa, Founder & CEO at Blue Goat Cyber

    Christian Espinosa, MBA · Founder & CEO, Blue Goat Cyber

    U.S. Air Force Academy graduate and veteran with 30+ years in cybersecurity. Founded Alpine Security in 2014 (acquired 2020), then Blue Goat Cyber in 2022. Has supported 275+ medical devices, with no cybersecurity-related rejections to date. Author of three books including The Smartest Person in the Room. Ironman triathlete and mountaineer.

    Read more about ChristianLinkedIn

    Sources & references

    Primary sources cited in this article. Links open in a new tab.

    1. FDA, Cybersecurity in Medical Devices: Quality Management System Considerations and Content of Premarket Submissions (February 2026)- U.S. FDA
    2. CISA Software Bill of Materials resources- CISA
    3. HHS HIPAA for Professionals- hhs.gov
    4. CISA Cybersecurity Advisories (including ICS medical advisories)- CISA

    Where your device stands

    Find your stage in the FDA cybersecurity journey

    Answer one question about where your device is today. You get your stage, the next action to take, and the support that fits it.

    Find where my device stands

    Free readiness check

    How ready is your cybersecurity package for FDA review?

    Seven questions mapped to the FDA's February 3, 2026 premarket cybersecurity guidance. You get a score, a gap list by area, and the fastest next move. Takes about three minutes.

    Ready when you are

    Get FDA cleared without the cybersecurity headaches.

    30-minute strategy session. No cost, no commitment - just answers from people who've shipped 275+ devices supported.