A side-channel attack extracts secret data - typically cryptographic keys, PINs, or biometric templates - by measuring physical phenomena that leak from a device while it processes those secrets, rather than by breaking the cryptographic algorithm itself. Common side channels include power consumption (DPA - Differential Power Analysis), electromagnetic emissions (TEMPEST/EM-SCA), execution timing, cache access patterns, and acoustic emissions. The 2018 Meltdown/Spectre family demonstrated the relevance of cache-timing side channels even on commodity CPUs.

Why it matters

Side-channel resistance matters most for devices an attacker can physically possess (implantable programmers, home-use devices) and for any device where extracting a single device's keys would compromise an entire fleet. Commodity hardware typically lacks side-channel hardening; secure elements and dedicated crypto coprocessors include countermeasures.

Common pitfalls

•Storing per-device keys in commodity microcontroller flash with no side-channel hardening.
•Implementing cryptography in software with non-constant-time operations.
•Re-using a single signing key across an entire device fleet - one extraction compromises all.

Sources

NIST SP 800-90B Recommendation for the Entropy Sources · NIST
FDA Cybersecurity Guidance (Sept 2023) · FDA
MDCG Cybersecurity Guidance · MDCG

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.