Open Standards Merge to Harden Device Security

A new open-source bridge allows devices to use hardware security chips for authentication, reducing reliance on software-only protections.
Two major industry bodies have released a joint open-source implementation that connects device authentication protocols with hardware security modules. This move aims to make it easier for manufacturers to build systems where trust is established through physical chips rather than just software code. The integration provides a standardized way for devices to verify their own integrity before communicating with other components.
The collaboration involves the Trusted Computing Group (TCG) and the DMTF, which have worked since 2021 to align their respective technologies. By combining the Security Protocol and Data Model (SPDM) with Trusted Platform Module (TPM) standards, developers now have a clearer path to creating interoperable security solutions. This approach is particularly relevant for the expanding ecosystem of connected devices that require robust identity verification.
Hardware roots of trust
The core of this update is the addition of a TPM backend to the DMTF’s libspdm library. This allows SPDM implementations to utilize keys protected within the hardware chip. According to GN technics/hardware (en-US), this means private keys never need to be exposed to the main system memory during operations. Instead, sensitive cryptographic tasks are performed inside the secure enclave of the TPM, significantly lowering the risk of key extraction by malicious software.
The integration also leverages Platform Configuration Registers (PCRs) stored in the TPM. These registers hold measurements of the system’s state at various boot stages. By using these hardware-verified measurements, devices can prove that their software environment has not been tampered with. This creates a stronger foundation for trust, as the verification is tied to immutable hardware records rather than volatile software states.
Practical applications for developers
The new implementation supports four specific security workflows. These include retrieving certificate chains from non-volatile storage, signing challenge responses with hardware-resident keys, and providing measurement data for attestation. It also facilitates signing operations during key exchange processes. These features allow developers to build systems where every component can be verified against a known good state, enhancing the overall security posture of complex device architectures.
A significant trade-off in adopting such hardware-backed security is the added complexity in development and testing. However, the DMTF has mitigated this barrier by providing a reference environment called spdm-emu. This tool uses a software-based TPM (swtpm) to simulate hardware behavior. Developers can thus test and validate their SPDM and TPM integrations without needing physical hardware, making the technology more accessible for early-stage development and validation.
Industry alignment and reach
Leaders from both organizations emphasize that this work is about accessibility and interoperability. Joe Pennisi, President of TCG, noted that providing accessible reference code helps implementers understand how these technologies complement each other. Jeff Hilland, President of DMTF, added that the open-source nature of the project allows for broader exploration and validation. This joint effort signals a shift toward standardizing how hardware and software security layers interact.
The TCG reports that its technologies are already incorporated into more than one billion devices. This widespread adoption suggests that the new integration could have a substantial impact on the security landscape for IoT and enterprise hardware. By standardizing the interface between protocols and hardware, the industry reduces fragmentation and makes it easier for security features to work across different vendors and platforms.






