Pick the interfaces your device actually exposes - from Wi-Fi and BLE to NFC, RFID, USB-OTG, JTAG, and CAN. Review example threats, possible test activities, and evidence prompts. These are not confirmed findings, required tests, or a complete device assessment.
Reviewed by
Christian Espinosa
Founder & CEO, Blue Goat Cyber
Interfaces the device actually exposes
Include service-only ports, paired accessories, and anything physically present even if disabled in software.
Wireless
Wired / physical
Cloud / app
Update / service
What you'll see after you submit
Common misconceptions
Myth: If it's just NFC for pairing, it doesn't need a threat model entry.
Reality: Assess actual NFC data flows, privileges, and trust boundaries. Configuration integrity and pairing controls depend on the implementation.
Myth: RFID is a logistics concern, not a cybersecurity concern.
Reality: Assess RFID roles, trust boundaries, and abuse cases. Patient harm depends on a device-specific clinical consequence, not the interface name.
Myth: A USB-C port that 'only charges' has no attack surface.
Reality: Inspect wiring, USB controllers, negotiated roles, and enforcement controls. A charge-only connector does not automatically provide a data path; verify the actual implementation.
References & further reading
Tracked signals that change what reviewers expect. Items move on as new ones land.
Add asset-level threats + ISO 14971 linkage.
Read Threat Model StarterTurn this profile into an effort estimate.
Read Pen Test Scope EstimatorRun the test against every interface on this profile.
Read Medical device penetration testingGet the evidence into the submission cleanly.
Read FDA premarket cybersecurity