Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
A Trusted Platform Module is a tamper-resistant chip that generates and stores keys, measures the boot process, and lets a machine prove its own state to a remote verifier.

What Is a Trusted Platform Module?
A Trusted Platform Module is a dedicated cryptographic processor built into almost every business computer sold in the past decade. Its purpose is to hold secrets that software cannot be trusted to hold: private keys that never leave the chip, measurements of what the machine loaded at boot, and attestations that a remote system can check. The specification is maintained by the Trusted Computing Group and published as ISO/IEC 11889.
Most people meet it as a Windows 11 requirement. Its actual value is that it anchors disk encryption, device identity, and boot integrity in hardware rather than in a configuration file.
TPM 1.2 was fixed to RSA-2048 and SHA-1, which is why it is now obsolete. TPM 2.0 is algorithm-agile: it supports SHA-256, elliptic curve keys, and multiple key hierarchies with separate authorisation policies. Implementations vary in assurance. A discrete TPM is a separate chip on the motherboard. An integrated TPM sits inside another controller. A firmware TPM runs inside the CPU’s trusted execution environment—Intel PTT or AMD fTPM—which is cheaper and far more common in laptops, but shares its fate with the processor’s security boundary. Virtual TPMs give the same interface to cloud and hypervisor guests.
On Windows, BitLocker seals the volume master key to the TPM so an encrypted disk removed from the machine is unreadable. Credential Guard stores derived domain credentials in virtualisation-based security backed by the chip, blocking many pass-the-hash techniques. Windows Hello binds biometric unlock to hardware, and device attestation lets conditional access policies distinguish a managed laptop from an unmanaged one. Microsoft made TPM 2.0 mandatory for Windows 11 in 2021, and with Windows 10 support ending on 14 October 2025 the requirement has driven a large UK hardware refresh cycle.
On Linux, systemd-cryptenroll binds LUKS volumes to PCR values, the Integrity Measurement Architecture extends measurement into user space, and Keylime provides continuous remote attestation. Server estates use TPM-backed SSH and machine certificates so that credentials cannot be copied off a host.
Require a PIN or passphrase alongside TPM-only unlock on any laptop that leaves the building—the NCSC’s device security guidance recommends pre-boot authentication for exactly this reason, and secure configuration is one of the five Cyber Essentials controls. Enable Secure Boot so the measurements mean something, keep TPM firmware in your patch cycle, and escrow BitLocker recovery keys in Active Directory or Entra ID rather than in a spreadsheet. Clear the TPM when a device changes owner. Finally, decide which PCRs you seal to: binding to too many means a routine firmware update locks users out, while binding to too few weakens the guarantee.
Our Infrastructure and Architecture Review Services cover endpoint encryption and attestation design across a managed estate.
No, but without one the volume master key must come from a USB startup key or a passphrase the user types each boot. A TPM allows transparent unlock while still binding the key to that specific machine and boot configuration. The strongest common setup is TPM plus a PIN, which keeps the hardware binding and defeats bus sniffing and evil maid attacks.
It is adequate for most organisations and avoids the physical bus between chip and CPU entirely, which closes the sniffing attack. The trade-off is that it shares the processor’s trusted execution environment, so a flaw there affects the TPM too. For high-assurance work with a credible physical threat, a discrete certified chip is still preferred.
A TPM is a low-cost chip soldered to one machine, protecting that machine’s identity, boot state, and disk key. A hardware security module is a separate certified appliance built for throughput, protecting organisational keys such as certificate authority roots or payment keys for many clients. They serve different scopes and are not interchangeable.
The headline attacks need physical access to probe the bus or glitch the chip. Remote risk comes from firmware vulnerabilities such as the 2023 reference implementation flaws, and from timing side channels like TPM-Fail that a local unprivileged process can exploit. Keep TPM firmware patched through your vendor update channel, which many organisations overlook entirely.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.