Hardcoded credentials are authentication secrets - passwords, API keys, private keys, service tokens - embedded directly in firmware, binaries, or source code distributed across every unit of a device family. Because the secret is identical on every device, a single firmware extraction or source leak compromises the entire fleet. Hardcoded credentials have driven multiple high-profile FDA safety communications (Hospira infusion pumps, St. Jude implantables, GE imaging consoles) and remain a top finding in MedTech penetration tests.

Why it matters

Eliminating hardcoded credentials means every device must provision its own unique key material at manufacture (often via a hardware secure element), or pull a unique credential from an authenticated bootstrap service on first boot. Service accounts that need credentials should rotate them through a secrets manager rather than embedding static values.

Common pitfalls

•Burning the same SSH or web-admin password into every shipped device.
•Embedding cloud API keys in mobile companion apps - they can be extracted by anyone with the app binary.
•Using a 'default password that the user must change' that, in practice, no one changes.

Sources

CWE-798 Use of Hard-coded Credentials · MITRE
FDA Cybersecurity Guidance (Sept 2023) · FDA
CISA - Healthcare and Public Health Sector · CISA

Open full page

Select term B to compare.

Why compare MedTech terms side by side?

MedTech terminology is full of pairs that look interchangeable but carry very different regulatory, clinical, and commercial consequences. Picking the wrong framework, pathway, or standard early in a project can add months to a submission, invalidate clinical evidence, or trigger an audit finding. Side-by-side comparison is the fastest way to surface those differences before they become costly mistakes.

Each comparison on this page pulls from the same vendor-neutral, sourced definitions used throughout the MedTech Terms glossary. You see the one-line summary, the formal definition, why it matters in practice, common pitfalls, and the primary sources (FDA guidance, EU MDR/IVDR articles, ISO/IEC standards, MDCG documents, IMDRF principles) that back each entry. That makes the comparison defensible in regulatory strategy memos, design reviews, and submission narratives.

Common comparison patterns

Regulatory pathway choice - 510(k) vs PMA, 510(k) vs De Novo, Abbreviated vs Special 510(k).
Quality systems - QSR vs ISO 13485, QMSR vs QSR.
Software classification - SaMD vs SiMD, Locked vs adaptive AI.
EU frameworks - MDR vs IVDR, CE Mark vs UKCA.
Cybersecurity artifacts - SPDX vs CycloneDX SBOM, CVE vs CVSS.
Post-market actions - Recall vs field action, Removal vs correction.

How to use this tool

Pick term A and term B from the dropdowns, or click a preset above. The URL updates with both slugs so you can bookmark or share the exact comparison with a colleague, a notified body reviewer, or your regulatory consultant. Click Open full page on either side for the complete entry, including FAQs, related terms, and the full citation list. If you are not sure which term to start with, browse the Categories view or the A-Z index.

MedTech Terms is a vendor-neutral community resource sponsored by Blue Goat Cyber. Definitions are written for educational use and are not legal or regulatory advice.