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 →
    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

    2-minute scope estimator

    What does a pen test for your device actually look like?

    Six questions mapped to the SPDF and FDA premarket guidance. Get a planning-grade scope, depth, and timeline - then a tailored proposal.

    Question 1 of 60% complete

    What is the device's submission pathway?

    Test depth

    White-box vs gray-box vs black-box

    For medical devices, both Blue Goat and the FDA recommend white-box testing. Reviewers expect testers to leverage source, firmware, and threat models, black-box alone routinely leads to deficiencies.

    CapabilityBlack-boxGray-boxWhite-box
    Source code access
    Firmware / binaries
    Threat model & architecture
    Authenticated test paths
    Deep logic + business-flow flaws
    Aligned with FDA expectations
    Scope coverage per test-day
    Yes Partial No
    References

    Why the FDA and AAMI point to white-box

    Premarket guidance and consensus standards both expect testers to leverage source code, design artifacts, and threat models, not just an external view of the device.

    • FDA Premarket Cybersecurity Guidance (Feb 3, 2026 final)

      Calls for security testing that demonstrates device resilience using design documentation, threat models, and source-level analysis, not black-box probing alone.

    • FD&C Act Section 524B (Cyber Devices)

      Requires sponsors to provide reasonable assurance that the device and related systems are cybersecure, which reviewers read as evidence-backed, white-box-informed testing.

    • AAMI TIR57: Principles for Medical Device Security - Risk Management

      Frames security testing as an output of threat modeling and architecture analysis. That is white-box by definition.

    • AAMI TIR97: Principles for Medical Device Security - Postmarket Risk Management

      Postmarket monitoring and vulnerability handling assume testers have access to internals, the same access white-box pen testing uses premarket.

    Before you scope

    Make sure you're testing the right things.

    The estimator gives you a planning number. These resources help you sharpen scope before kickoff.

    FDA cybersecurity readiness quiz

    2-minute self-assessment to score your submission against current FDA guidance.

    Read FDA cybersecurity readiness quiz

    Medical device penetration testing

    Our SPDF-aligned methodology, deliverables, and reviewer-ready report format.

    Read Medical device penetration testing

    Threat modeling services

    STRIDE-based modeling - the input that lets a pen test test the right things.

    Read Threat modeling services

    FDA premarket cybersecurity

    Full SPDF + eSTAR-ready submission package aligned to FDA guidance.

    Read FDA premarket cybersecurity

    Cost-of-delay calculator

    Quantify what every week of submission slip costs in revenue and runway.

    Read Cost-of-delay calculator

    White-box penetration testing

    Our recommended depth for medical devices - and the FDA's preference. Full source, firmware, and threat-model access for deeper findings.

    Read White-box penetration testing

    Pen testing methodology

    How we plan, execute, and report - designed for FDA reviewer scrutiny.

    Read Pen testing methodology