À La Carte Firmware Pen Testing

    Firmware Pen Testing. Done at the Silicon.

    Embedded firmware extraction, reverse engineering, secure-boot validation, and OTA update testing for medical devices. The work that proves your device's root of trust actually holds.

    The short answer

    What is firmware penetration testing?

    Firmware penetration testing examines the software that runs on a device's chips. Testers extract the firmware through debug ports, flash memory or update files, then reverse engineer it to find hard-coded secrets, weak update and boot checks, outdated components and memory-safety flaws. For an FDA submission, findings are traced to the threat model and rated for patient-harm risk.

    JTAG, SWD, UART, SPI, chip-off: whatever your device exposes.

    • JTAG / SWD / UART
    • Chip-off extraction
    • Secure boot review
    • OTA path testing
    • Free 30-min scoping call
    • Fixed-fee quote in 24 hours
    • Hardware lab in-house
    • Senior embedded reverser on every job
    • Re-test included
    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

    Fixed-fee engagement

    Firmware 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 firmware extraction, reverse engineering, debug-interface checks, secure boot, signing, rollback, and update-path security tests.
    • 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

    • Firmware images and build identifiers, device samples, debug access details, update/signing design, and explicit permission for any extraction or chip-off work.
    • 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 Most Pen Tests Never Touch the Firmware

    Application security firms test what they're equipped to test: web apps. Embedded firmware requires a hardware lab, oscilloscopes, JTAG adapters, and reverse-engineering experience that generalists don't carry.

    No Hardware Lab

    Without a soldering station, logic analyzer, and JTAG adapters, the tester can't even reach the firmware to begin testing it.

    No Binary Reversing Skill

    Reversing ARM/RISC-V/MIPS firmware in Ghidra requires a different practitioner than the one who reads OWASP Top 10 reports.

    Secure Boot Treated as a Spec

    FDA guidance recommends testing evidence, not assertion. Generic firms quote your design doc back to you instead of testing whether the chain actually holds.

    Attack surface

    What We Actually Test

    À la carte scope. We focus on the firmware layer and adjacent hardware interfaces. Pair with our BLE/RF or PHI Cloud service for full coverage.

    Hardware Interface Discovery

    • Visual + logic-analyzer port identification
    • JTAG / SWD enumeration (JTAGulator, Bus Pirate)
    • UART discovery, baud detection, console attack
    • SPI / I²C bus sniffing and injection
    • Test-point and debug-header documentation

    Firmware Extraction

    • In-circuit flash readout via SPI/QSPI
    • JTAG/SWD memory dumps
    • Chip-off extraction (BGA / TSOP / SOIC) when required
    • OTA package interception and unpacking
    • Bootloader and recovery-mode extraction

    Binary Analysis & Reverse Engineering

    • Ghidra / IDA reversing of ARM, RISC-V, Xtensa, MIPS
    • Hard-coded credential and key hunting
    • Cryptographic primitive review (custom or weak crypto)
    • Symbol recovery and function identification
    • SBOM correlation and CVE exploit verification

    Secure Boot & OTA

    • Secure-boot chain validation (ROM → BL → app)
    • Signature, hash, and rollback-protection testing
    • OTA package signing and version-pinning review
    • Downgrade-attack and partial-image scenarios
    • Recovery / factory-reset abuse paths
    How it works

    Engagement Methodology

    Three to six weeks depending on extraction difficulty and binary size.

    1. 01

      Scoping & Hardware Intake

      We review your architecture, MCU/SoC datasheet, secure-boot design, and SBOM. You ship two to three units to our lab (one for destructive extraction if chip-off is in scope).

    2. 02

      Interface Discovery & Extraction

      We document every exposed debug interface, attempt non-destructive extraction first (JTAG/SWD/UART), and only escalate to chip-off when warranted.

    3. 03

      Reverse Engineering & Exploitation

      Binary analysis in Ghidra, secret hunting, crypto review, secure-boot chain testing, and OTA path attacks. Every finding reproduced and evidenced.

    4. 04

      Reporting & Re-test for FDA Premarket Submissions

      Findings mapped to AAMI TIR57, IEC 81001-5-1, and the Feb 2026 FDA guidance. SBOM-to-finding traceability included. Re-test until you pass.

    What's included

    Reviewer-ready deliverables in one engagement

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

    • JTAG / SWD / UART debug interface testing
    • Flash extraction (in-circuit and chip-off)
    • Binary reverse engineering and crypto review
    • Secure boot, signing, and rollback validation
    • OTA update path and integrity testing
    • SBOM correlation and CVE exploit verification
    Pricing guidance

    Pricing Guidance

    Fixed-fee. Hardware testing is more variable than software. We always scope on a 30-min call before quoting.

    Standard Firmware

    Fixed fee after scoping

    Single MCU/SoC, exposed debug interfaces, well-documented SBOM. Most ARM Cortex-M and ESP32-class devices.

    • Non-destructive extraction (JTAG/SWD/UART)
    • Full binary reverse engineering
    • Secret + crypto review
    • Secure boot validation
    • One round of re-test

    Hardened / Locked

    Fixed fee after scoping

    Locked debug ports, encrypted flash, or secure-element-protected boot. Requires chip-off or side-channel exploration.

    • Chip-off extraction (1-2 destructive units)
    • Secure-element interface analysis
    • OTA path and rollback testing
    • Glitching / fault-injection where applicable
    • Two rounds of re-test

    Multi-Processor System

    Fixed fee after scoping

    Multiple processors (e.g., main MCU + radio SoC + safety co-processor), proprietary RTOS, or Linux-based platforms with custom kernel.

    • Per-processor extraction and analysis
    • Inter-processor communication review
    • Linux kernel / driver review (where applicable)
    • Dedicated senior embedded lead

    What drives the price

    • Number of processors and firmware images in scope
    • Whether debug ports are open, locked, or fused-off
    • Need for chip-off extraction (destructive) vs. in-circuit
    • Binary size and obfuscation level
    • Presence of a secure element or TPM
    • Inclusion of OTA path and rollback testing
    • RTOS vs. embedded Linux (kernel review adds scope)

    We always need 2-3 sample units. One may be destroyed if chip-off is required. Discuss in scoping.

    FAQ

    Firmware Pen 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 Firmware Penetration Testing?

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

    Embedded firmware extraction, reverse engineering, secure-boot validation, and OTA update testing for medical devices. The work that proves your device's root of trust actually holds.