Blue Goat CyberBlue Goat CyberSMMedical Device Cybersecurity
    Start here
    Services
    • Medical Device Cybersecurity Consulting
    • FDA Premarket Cybersecurity Package
    • Medical Device Penetration Testing Services
    • FDA Deficiency Response
    • FDA Postmarket Cybersecurity
    • Medical Device Threat Modeling
    • eSTAR Cybersecurity Documentation Support
    See all services
    Products

    Blue Goat products

    • GoatWatch logoGoatWatchSBOM risk management for medical devices
    About
    Resources

    Learn

    • Blog
    • Podcast
    • Webinars
    • Talks & workshops
    • Glossary
    • FAQs

    Playbooks & Tools

    • Guides
    • Playbooks (PDF)
    • Infographics
    • Interactive Tools

    Signals & Proof

    • Goat FeedNew
    • News
    • Medical Device Security News
    • The Goat's Weekly
    • Case Studies
    • Proof / Receipts
    All resources, topic hubs, & collections →
    ⌘K
    Book Strategy SessionHow to prepare →
    1. Home
    2. Services
    3. Current page
    Blue Goat Cyber

    Full-service medical device cybersecurity. We protect patients by securing connected medical devices from design through postmarket.

    275+ FDA submissions supported, zero cybersecurity rejections · Mission: 1,000 by 2028

    SDVOSB · Service-Disabled Veteran-Owned Small Business

    We sponsor 10 community projects →

    Services

    • FDA Premarket Cybersecurity Package
    • FDA Deficiency Response
    • Medical Device Threat Modeling
    • Medical Device Penetration Testing Services
    • FDA Postmarket Cybersecurity
    • All services →
    Services
    • FDA Premarket Cybersecurity Package
    • FDA Deficiency Response
    • Medical Device Threat Modeling
    • Medical Device Penetration Testing Services
    • FDA Postmarket Cybersecurity
    • All services →

    Company

    • About
    • Core values
    • Manifesto
    • Leadership
    • Why Us
    • Partners
    • Careers
    • Press
    • Press kit
    • Contact
    • Company overviewPDF
    Company
    • About
    • Core values
    • Manifesto
    • Leadership
    • Why Us
    • Partners
    • Careers
    • Press
    • Press kit
    • Contact
    • Company overviewPDF

    Resources

    • Blog
    • Guides
    • Podcast
    • Case studies
    • Monthly Pulse newsletter
    • All resources →
    Resources
    • Blog
    • Guides
    • Podcast
    • Case studies
    • Monthly Pulse newsletter
    • All resources →

    Get in touch

    • info@bluegoatcyber.com
    • 844-939-GOAT
    • Book a strategy session →
    • 1776 N Scottsdale Rd, Unit 727
      Scottsdale, AZ 85257Serving clients worldwide

    Follow

    © 2026 Blue Goat Cyber. All rights reserved.

    • Privacy
    • Terms
    • Cookies
    • Sitemap
    • Accessibility
    • CVD

    MedTech Cybersecurity · Since 2022

    eSTAR cybersecurity documentation for medical devices

    For teams preparing a 510(k) or De Novo who need the cybersecurity attachments built or fixed.

    Blue Goat prepares the agreed cybersecurity documentation mapped to applicable eSTAR fields. The work connects threats, patient-harm risks, controls, and testing evidence. Your regulatory team reviews and submits the eSTAR. Fixed fee after scoping.

    Book an eSTAR scoping call

    275+ FDA submissions supported, zero cybersecurity rejections.

    What Blue Goat prepares

    • Threat model and cybersecurity risk assessment, traced to the manufacturer's ISO 14971 safety risk file
    • SBOM generation and enrichment with support level and end-of-support data
    • Security architecture views
    • Penetration testing as independent third-party reports. See what a Blue Goat penetration test report contains.
    • Cybersecurity labeling content and management plan input
    • Coordinated vulnerability disclosure support
    • Cybersecurity questions and supporting material for a Pre-Submission, prepared in FDA's PreSTAR template

    The statement of work identifies which documents need to be created, updated, or supported by additional security testing. Your manufacturer team retains engineering changes, risk acceptance, general software verification and validation, and QMS approval. The FDA makes the regulatory decision.

    Documentation support or the broader package?

    Discuss eSTAR documentation support when you need to prepare or update the cybersecurity attachments for your submission. Existing records and testing evidence determine what work is needed. This is not a separate regulatory pathway or a promise that every document applies to your device.

    Choose the FDA Premarket Cybersecurity Package when you need the broader documentation and security activities coordinated in one engagement. Choose Medical Device Penetration Testing when the gap is testing evidence. We agree any additional documentation or testing before work begins.

    Book an eSTAR scoping call

    What eSTAR is

    eSTAR is the FDA's electronic submission template, an interactive PDF. It is required for 510(k) and De Novo submissions to CDRH and CBER, unless exempted. The FDA publishes separate templates for non-IVD devices, IVD devices, and early requests such as Q-Submissions. The template checks for completeness, so a missing item can stop a submission from being accepted for review.

    For a new submission, use the FDA's current template where practicable. Relevant changes in an older major version may prompt additional information requests; older minor versions typically do not. After the FDA acknowledges your submission, update the original eSTAR for Additional Information or technical-screening responses rather than switching versions.

    For what changed in the current template, see the eSTAR 7.1 submission checklist.

    Before the formal submission, manufacturers can use PreSTAR, the FDA's template for Pre-Submission requests, to ask the FDA about their cybersecurity approach early. See PreSTAR vs eSTAR.

    eSTAR is voluntary for specified PMA application and supplement types. Applicable cybersecurity guidance recommendations also apply to PMA submissions.

    See the FDA eSTAR program for current templates and version instructions.

    What the cybersecurity section asks for

    Blue Goat's delivery map organizes the work. It is not a list of universally required FDA documents. Applicability depends on your device and pathway. See the FDA Premarket Cybersecurity Deliverables and eSTAR Map. The work falls into these groups:

    • Security risk management

      A security risk management report, a threat model, and a cybersecurity risk assessment. Exploitability and patient-harm severity are assessed separately, rather than using probability of an attack.

    • Software supply chain

      An SBOM, the support level and end-of-support date for each component, a vulnerability assessment, and an assessment of unresolved anomalies.

    • Security architecture and controls

      Security requirements with control coverage, and security architecture views.

    • Testing

      Static analysis, plus a penetration test plan, test cases, and test report, as scoped. The FDA's guidance lists five elements for a penetration test report: tester independence and technical expertise, scope, duration, methods, and results with findings and observations.

    • Labeling

      Cybersecurity labeling for users. A Manufacturer Disclosure Statement for Medical Device Security (MDS2) is an optional procurement disclosure, not an FDA or eSTAR requirement.

    • Management

      A cybersecurity management plan for postmarket vulnerability handling.

    • Interoperability and metrics

      An interoperability risk assessment, interoperability labeling, and measures and metrics.

    What the law requires and what the guidance recommends

    For a cyber device, section 524B(b) of the FD&C Act requires three things: a plan to monitor, identify, and address postmarket cybersecurity vulnerabilities and exploits, including coordinated vulnerability disclosure; processes that provide a reasonable assurance that the device and related systems are cybersecure; and a software bill of materials covering commercial, open-source, and off-the-shelf components.

    The FDA's February 3, 2026 premarket cybersecurity guidance describes recommended supporting documentation. The depth of that documentation scales with the device's cybersecurity risk.

    Where submissions come apart

    The documents have to agree with each other. The FDA's guidance names traceability as a documentation element. A threat in the threat model should lead to a risk, a control, a test, and a residual risk. When one link breaks, a reviewer cannot follow the chain.

    1. 1Threat
    2. 2Risk
    3. 3Control
    4. 4Test
    5. 5Residual risk

    The 510(k) penetration testing for an AI-enabled cloud SaMD case study illustrates testing scope and evidence. It is not an example of a complete eSTAR documentation engagement.

    What to bring to the scoping call

    • Submission pathway, planned submission date, and the eSTAR version in use.
    • Device architecture, intended use, and connected components.
    • Existing threat model, cybersecurity risk assessment, SBOM, and testing records, where available.
    • Known evidence gaps and any cybersecurity correspondence from the FDA.

    Identify missing inputs during the call. Agree secure document sharing before sending confidential device material.

    How an engagement runs

    1. 1

      Scoping

      A signed statement of work names the pathway, the device architecture, and the deliverable set.

    2. 2

      Risk analysis

      Asset inventory, threat model, and risk assessment.

    3. 3

      Security testing

      The applicable testing categories in the FDA's guidance, within the agreed scope.

    4. 4

      SBOM production

      Minimum elements first, then support level and end-of-support enrichment.

    5. 5

      eSTAR mapping

      Each agreed document is mapped to the applicable eSTAR cybersecurity fields so your regulatory team can attach it.

    6. 6

      Release

      Every deliverable passes an internal Blue Goat quality review before it ships.

    Fixed fee after scoping. The proposal records deliverables, assumptions, manufacturer inputs, and dates. Device access, engineering fixes, and review feedback can affect the schedule. Quote turnaround is separate from delivery time.

    Frequently asked questions

    Is eSTAR required for my submission?

    +

    eSTAR is required for 510(k) and De Novo submissions to CDRH and CBER, unless exempted. eSTAR is voluntary for specified PMA application and supplement types. Applicable cybersecurity guidance recommendations also apply to PMA submissions.

    Does eSTAR cybersecurity documentation apply to every device?

    +

    The FDA's guidance covers devices with cybersecurity considerations, including devices with software or programmable logic. It is not limited to network-connected devices. Section 524B adds requirements for cyber devices.

    Which eSTAR version should we use?

    +

    For a new submission, use the FDA's current template where practicable. Relevant changes in an older major version may prompt additional information requests; older minor versions typically do not. After the FDA acknowledges your submission, update the original eSTAR for Additional Information or technical-screening responses rather than switching versions.

    Can Blue Goat help with a Pre-Submission?

    +

    Yes. Blue Goat helps prepare the cybersecurity questions and supporting material for a Pre-Submission, using the FDA's PreSTAR template. A Pre-Submission lets you ask the FDA about your cybersecurity approach before you file. The FDA provides the feedback.

    What if the FDA asks for more information?

    +

    Blue Goat supports deficiency responses. See FDA cybersecurity deficiency response.

    Do you submit the eSTAR for us?

    +

    Your regulatory team owns, reviews, and submits the eSTAR. Blue Goat prepares the agreed cybersecurity documentation and supporting technical responses. General software verification and validation, QMS approval, and risk acceptance remain manufacturer responsibilities.

    How is the engagement priced and scheduled?

    +

    Fixed fee after scoping. Your pathway, device architecture, available evidence, and testing needs determine the work. Scope, deliverables, manufacturer inputs, and dates are agreed before work begins. A quote turnaround is not a delivery deadline.

    Discuss your eSTAR documentation scope

    Review the evidence you have, the work still needed, and your regulatory team's handoff requirements. Book a call, or send your details and we will follow up.

    Book an eSTAR scoping call

    Send an eSTAR scoping inquiry

    Tell us your pathway, planned submission date, and which cybersecurity documents you already have.

    Or skip the form - book a strategy session →

    We'll only use your details to respond. No newsletter spam.

    Fixed-fee engagement

    eSTAR cybersecurity documentation: deliverables, inputs, and exclusions

    Included work is defined in the signed proposal. These scope options are not automatic inclusions in every engagement.

    Fixed-fee deliverables

    • Agreed cybersecurity documents created or updated and mapped to applicable eSTAR 7.1 fields.
    • Evidence-gap review and traceability across the selected threats, controls, risk records, and security tests.

    Required inputs

    • Submission pathway, eSTAR version, intended use, architecture, existing threat model/SBOM/risk/test records, and regulatory correspondence.
    • Regulatory handoff requirements, engineering/quality reviewers, and authorized access if new security testing is included.

    Exclusions and separate work

    • Not every cybersecurity document or test is automatically included. The manufacturer reviews and submits the eSTAR. QMS/SOP work and ongoing monitoring are separate.
    • 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

    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.

    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.

    • Goat Feed: medical device cybersecurity alerts
    • The Goat's Weekly: Medical Device Cybersecurity News Brief

    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.

    • FDA Medical Device Threat Modeling Guide
    • eSTAR 7.1 Cybersecurity Documentation Guide
    • FDA SBOM Requirements for Medical Devices
    • CISA 2026 SBOM Checklist for Medical Devices
    • CISA vs FDA SBOM Checklist and Scoring Tool