MedTech Terms
    The authoritative reference
    All terms
    CybersecurityConnected & Cyber-Physical DevicesHRoT

    Hardware Root of Trust

    Hardware-enforced trust anchor for selected security functions, subject to implementation and threat assumptions.

    Reviewed by Christian Espinosa, Founder, Blue Goat CyberLast reviewed June 20, 2026

    Definition

    A hardware root of trust anchors selected security functions in hardware-enforced mechanisms and trusted code or key material. Implementations can use ROM-based boot logic, TPMs or secure elements. TrustZone supplies isolation mechanisms but is not by itself a guarantee of immutable code, protected keys or physical tamper resistance. Roots of trust have explicit threat assumptions and may contain exploitable implementation flaws.
    What the regulation says
    FDA February 2026 guidance recommends risk-appropriate cryptographic and security controls. Any claimed mandatory hardware key-storage provisions in IEC 81001-5-1, AAMI SW96 or HSCC JSP require verified original passages.

    What this means in practice

    Select root-of-trust and key-protection mechanisms through device-specific risk analysis. FDA expects appropriate cybersecurity architecture and key-management evidence, but does not universally require every device to contain a TPM or secure element. Software key storage has limitations that should be evaluated, not treated as automatic regulatory failure.

    Examples

    • Illustrative: When a new patient monitoring system powers on, its initial boot code is cryptographically verified by an immutable module embedded in the hardware, preventing malicious firmware from loading.
    • Illustrative: A drug delivery device uses its integrated secure element to generate and protect cryptographic keys, ensuring that only authenticated software can access sensitive patient data or control mechanisms.
    • Illustrative: A device supplies a hardware-backed attestation signed by a protected key. The relying party evaluates freshness, measurements and trust anchors; the report is not an unconditional integrity guarantee.
    Common pitfalls
    • •Calling a software-only secure key store a 'root of trust', without hardware tamper resistance, it isn't.
    • •Provisioning the same root keys across many devices in manufacturing, per-device unique keys are required for credible device identity.
    • •Ignoring supply-chain attestation of the secure element itself, a compromised secure element undermines every claim above it.

    Frequently asked questions

    Hardware-enforced roots of trust may use immutable boot logic or protected keys. TrustZone alone is not a complete implementation, and physical tamper resistance varies. A software-only key store should not be represented as hardware protection.

    Related terms

    Grouped by theme
    Cited by

    Where this term appears across MedTech Terms.

    Latest in MedTech

    Sources

    5 sources

    Sources support the definition or relevant regulatory context, not necessarily every claim on this page. Each is graded against our source-tier hierarchy so you can see what rests on binding law versus commentary.

    Official-source claim check:

    Roots of trust anchor protection, detection and recovery; assurance depends on implementation and threat assumptions.

    Partial review: verified corrections are applied, but this is not a full accuracy certification. The last full review date is unchanged.

    Remaining verification limits
    • Secondary regulatory, standards-clause, market-prevalence or procurement claims were not fully substantiated by accessible original text.
    Tier 2Regulator guidance and consensus· 5
    Link health: 3 verified 2 unchecked· last checked 2026-06-20
    NIST·2Trusted Computing Group·1FDA·2
    1. 1
      NIST SP 800-193: Platform Firmware Resiliency
      Tier 2 Verified
      NISTcsrc.nist.gov
    2. 2
      TPM 2.0 Library Specification
      Tier 2 Verified
      Trusted Computing Grouptrustedcomputinggroup.org
    3. 3
      FDA - Cybersecurity for Medical Devices
      Tier 2 Verified
      FDAfda.gov
    4. 4
      NIST SP 800-193
      Tier 2 Unchecked
      NISTnvlpubs.nist.gov
    5. 5
      FDA final guidance, February 3, 2026
      Tier 2 Unchecked
      FDAfda.gov

    Inline markers like [1] jump to the matching reference above.