SaMD Penetration Testing

    SaMD Penetration TestingCloud, API, Web and Mobile, Ready for FDA Review.

    Your SaMD has no circuit board, so the attack surface is the cloud, the APIs, the apps and the identity system. We test all of it as one engagement, scoped from your threat model, and deliver a report built for an FDA premarket submission.

    The short answer

    What is SaMD penetration testing?

    SaMD penetration testing checks software-only medical devices the way an attacker would: the cloud backend, APIs, web portals, mobile apps and the identity system that ties them together. Because connected SaMD counts as a cyber device under Section 524B, the FDA's premarket guidance recommends penetration testing as part of the cybersecurity testing evidence. We scope the test from your threat model, rate findings with CVSS and patient-harm impact, and trace each one back to your risk file.

    275+ FDA submissions supported, zero cybersecurity rejections. Mostly manual, expert-led testing.

    • Cloud + IAM
    • API authorization
    • Web + mobile apps
    • Threat-model traceability
    • Retests until uncontrolled risks are closed
    • Free 30-min call
    • No obligation
    • Senior expert, not a sales rep
    • Fixed-fee quote in 24 hours
    • NDA available on request
    Trusted by leading MedTech manufacturers since 2022 · See client outcomes and awards
    Christian Espinosa, Founder & CEO

    Reviewed by Christian Espinosa, MBA · Founder & CEO

    Last reviewed October 2026

    Fixed-fee engagement

    SaMD penetration testing: 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 cloud, IAM, tenant-isolation, API, web, and mobile attack-path testing for software as a medical device.
    • A Penetration Test Plan, Test Cases, and Test Report for the agreed attack surface and product versions.
    • Documented findings, reproduction evidence, and remediation recommendations. Clean test cases and agreed retest evidence. Device tests trace to documented threats. They distinguish security impact from manufacturer-supplied patient-harm context.

    Required inputs

    • Versioned applications, API specifications, cloud boundary, role/tenant test accounts, and authorized staging access.
    • Written authorization, rules of engagement, in-scope targets and versions, test windows, and an escalation contact.
    • Test accounts, environment access, architecture and data-flow information, and known access restrictions. Device work also needs intended use, available threat model, and ISO 14971 hazard context.

    Exclusions and separate work

    • Unlisted targets, production disruption, destructive hardware work, and third-party systems without authorization are excluded. Additional interfaces require agreement.
    • SBOM generation, SAST, threat-model creation, and architecture views are separate unless explicitly bundled. A targeted test is not whole-device coverage.
    • 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.

    FDA guidance: Cybersecurity Testing, Section C

    Cybersecurity testing beyond standard software V&V

    The FDA recommends cybersecurity testing in a security context, beyond standard software verification and validation. Security testing documentation and associated reports or assessments should be included in the premarket submission. Penetration testing is one part of this evidence, not a substitute for every testing activity.

    The manufacturer retains design verification and validation procedures under ISO 13485 Subclauses 7.3.6 and 7.3.7, design input and output review, fixes, risk acceptance, and release decisions. Blue Goat provides scoped cybersecurity testing and evidence, not general software V&V or software validation services.

    Security requirements and boundaries

    The FDA recommends evidence that each security design input was implemented successfully, plus boundary analysis and the rationale for boundary assumptions. Our agreed test cases connect applicable security requirements, threats, expected secure behavior, and actual results. Exclusions and untested requirements remain visible.

    Threat-mitigation effectiveness

    Testing evidence should address risk controls represented in the Global System, Multi-Patient Harm, Updatability and Patchability, and Security Use Case security architecture views. The threat model and Threat Table are separate deliverables, linked to controls and test evidence. Review security-policy enforcement and, as appropriate, maximum-traffic performance, stability, and reliability. The proposal identifies included checks and other manufacturer evidence needed.

    Vulnerability testing and analysis

    Section C references ANSI/ISA 62443-4-1 and recommends considering the following testing and analysis evidence:

    • Abuse or misuse cases, malformed and unexpected inputs, robustness, and fuzz testing.
    • Attack surface analysis and vulnerability chaining.
    • Closed-box known-vulnerability scanning.
    • Software composition analysis of binary executable files.
    • Static and dynamic code analysis, including hardcoded, default, easily guessed, or easily compromised credentials.

    This is a guidance evidence checklist, not a promise that every method is included in standalone penetration testing. SAST, binary software composition analysis, SBOM work, and threat-model creation or rework are separate unless explicitly bundled. Other methods depend on agreed access, interfaces, risks, and scope. Automated scan output alone is not a penetration test.

    Penetration-test evidence

    Adversarial tests focus on discovering and exploiting product vulnerabilities to identify and characterize security-related issues. The FDA recommends providing penetration-test reports that include:

    • Independence and technical expertise of testers.
    • Scope of testing.
    • Duration of testing.
    • Testing methods employed.
    • Test results, findings, and observations.

    Our Test Plan, Test Cases, and Test Report connect scope, methods, requirements, threats, findings, clean results, limitations, and retests. Documented evidence does not establish regulatory acceptance or replace manufacturer review.

    Source: Cybersecurity in Medical Devices: Quality Management System Considerations and Content of Premarket Submissions, February 3, 2026, Section C. Guidance recommendations are distinct from Section 524B statutory duties.

    Why a generic web app pen test falls short for SaMD

    An IT pen test can find the same bugs. It rarely produces evidence an FDA reviewer can use.

    No link to the threat model

    FDA guidance recommends that testing trace to the threats and controls you documented. A report that never mentions your threat model leaves the reviewer to connect the dots, and they usually ask instead.

    Threat model gap assessment

    CVSS alone is not patient-harm risk

    A medium CVSS finding that lets one clinic see another clinic's results matters more than a critical finding with no path to a patient. Findings need a patient-harm rating that feeds your ISO 14971 file.

    Pieces tested separately

    When the cloud, the mobile app and the web portal are tested by different vendors, nobody tests the paths between them. That is often where tenant isolation and token handling break.

    Attack surface

    What we test in a SaMD engagement

    Scope comes from your threat model and architecture views, so the report matches what you describe in the submission.

    Cloud & Identity

    • IAM least-privilege review (AWS / Azure / GCP)
    • Key management and storage exposure
    • Tenant isolation between customers and sites
    • Secrets in code, config and CI/CD

    APIs

    • Object- and function-level authorization (BOLA / BFLA)
    • Token lifecycle, refresh and revocation
    • Input handling, injection and SSRF
    • Rate limits and mass assignment

    Web & Mobile Apps

    • Login, session and role boundaries (OWASP ASVS)
    • iOS and Android data storage and transport (OWASP MASVS)
    • Patient data exposure in the UI, logs and exports
    • Update and configuration integrity

    AI/ML Models (when present)

    • Model and training-data access controls
    • Tampering with model updates
    • Adversarial input handling where in scope
    How it works

    How a SaMD pen test runs

    1. 01

      Scoping call

      We review your architecture, threat model and hazard analysis, agree on the environment and test windows, and send a fixed-fee quote. If the threat model or hazard analysis is missing or thin, we start there.

    2. 02

      Kickoff and intake

      A project manager runs the engagement over Slack and secure file sharing. You provide test accounts, API docs and read-only cloud access where possible.

    3. 03

      Testing

      Manual, white-box testing of the cloud, APIs and apps, using synthetic accounts and data. We never pull real patient data.

    4. 04

      Report and retests

      A report for FDA premarket submissions with CVSS and patient-harm ratings traced to your threat model, then retests until uncontrolled risks are closed.

    What's included

    Reviewer-ready deliverables in one engagement

    Every engagement ships with documented artifacts, traceable, complete, and aligned with current guidance.

    • Cloud backend, IAM and tenant isolation testing
    • API authorization testing (OWASP API Top 10)
    • Web and mobile app testing (OWASP ASVS / MASVS)
    • Report for FDA premarket submissions with threat-model traceability and retests
    Pricing guidance

    Pricing Guidance

    Fixed-fee. Cloud scope scales with surface area, not just lines of code.

    Single-Cloud, Single-Tenant

    Fixed fee after scoping

    One cloud (AWS or Azure or GCP), single-tenant deployment, modest API surface, no IoT broker or limited MQTT scope.

    • API authZ matrix (up to ~30 endpoints)
    • IAM + KMS + storage configuration review
    • PHI data-flow trace
    • HIPAA technical-safeguard validation
    • One round of re-test

    Multi-Tenant SaaS

    Fixed fee after scoping

    Most connected-device platforms: multi-tenant, device-to-cloud channel, ~50-150 API endpoints, IoT Core / IoT Hub in scope.

    • Full tenant-isolation matrix
    • Device-channel + MQTT topic ACL testing
    • Cross-tenant PHI exposure probing
    • IaC review (Terraform / CDK / Bicep) where available
    • Two rounds of re-test

    Multi-Cloud / Enterprise

    Fixed fee after scoping

    Multi-cloud or hybrid deployments, enterprise IDP federation, complex data-residency requirements, or high-volume IoT fleets.

    • Per-cloud configuration audit
    • Federated identity + SSO boundary testing
    • Data-residency and cross-region PHI flow review
    • Dedicated senior cloud + healthcare lead

    What drives the price

    • Number of clouds in scope (AWS / Azure / GCP)
    • Number of API endpoints and microservices
    • Multi-tenancy model (shared schema, schema-per-tenant, account-per-tenant)
    • Device-channel protocol (HTTPS, MQTT, AMQP, custom)
    • Test environment (production with safeguards vs. staging clone)
    • Whether infrastructure-as-code is available for review
    • PHI volume and data-residency constraints

    Production testing is supported with PHI-safe test accounts and rate-limit coordination. We never exfiltrate real PHI.

    FAQ

    SaMD Penetration Testing FAQs

    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.

    Ready to start SaMD Penetration Testing?

    SaMD Penetration Testing - scoped, fixed-fee, built for FDA premarket submissions.

    Your SaMD has no circuit board, so the attack surface is the cloud, the APIs, the apps and the identity system. We test all of it as one engagement, scoped from your threat model, and deliver a report built for an FDA premarket submission.