Web3 Learning

What Is a Hardware Security Module (HSM)?

By Safeheron Team

A hardware security module (HSM) is a physical computing device dedicated to safeguarding and managing cryptographic keys and performing cryptographic operations internally. The US National Institute of Standards and Technology (NIST), in SP 800-57 Part 2, defines it as “a physical computing device that safeguards and manages cryptographic keys and provides cryptographic processing”, and notes that an HSM is or contains a cryptographic module.

NIST gives a more specific description in SP 1800-16: an HSM safeguards and manages digital keys and other secrets in a tamper-evident and intrusion-resistant way, while also providing cryptographic processing.

How Does an HSM Protect Keys?

An HSM keeps both the storage and the use of keys inside a protected physical device. Applications ask the device to perform cryptographic operations instead of extracting the key and computing on their own. This is why NIST describes an HSM as a device that “safeguards and manages keys and provides cryptographic processing”.

At the physical level, NIST SP 1800-16 emphasizes that HSMs are tamper-evident and intrusion-resistant. For modules at higher security levels, FIPS 140-2 also requires tamper response circuitry: as soon as it detects that the enclosure has been opened or a maintenance access interface has been accessed, it immediately zeroizes all plaintext secret keys, private keys and critical security parameters.

At the access control level, cryptographic module standards require authentication of varying strength depending on the security level, from role-based to identity-based authentication, so that only authorized operators can invoke key-related services. The FIPS 140-3 security requirements also cover areas such as self-tests, sensitive security parameter management and life-cycle assurance.

What Do the FIPS 140-3 Security Levels Mean?

FIPS 140-3 is the US federal government’s standard for security requirements for cryptographic modules. Published on March 22, 2019, it supersedes FIPS 140-2. It provides four increasing, qualitative security levels intended to cover a range of applications and deployment environments, and its detailed testing requirements reference the international standard ISO/IEC 19790.

The basic logic of the four levels was already set out clearly in FIPS 140-2, with each level adding requirements on top of the one below it. The table below summarizes, based on the FIPS 140-2 descriptions, what each level adds in physical security and authentication.

Security LevelPhysical SecurityAuthentication
Level 1Production-grade components; no specific physical security mechanisms requiredNot required
Level 2Adds tamper-evidence requirements, such as coatings, seals or pick-resistant locksAt least role-based authentication
Level 3Adds tamper detection and response, immediately zeroizing plaintext keys when the enclosure is openedIdentity-based authentication
Level 4Provides a complete envelope of protection around the module and adds environmental failure protection or testingIdentity-based authentication

Whether a module actually meets a given level is confirmed by the Cryptographic Module Validation Program (CMVP). The CMVP is run jointly by NIST and the Canadian Centre for Cyber Security, with testing carried out by accredited independent laboratories. The CMVP has accepted FIPS 140-3 validation submissions since September 22, 2020; according to its announcement, FIPS 140-2 modules move to the historical list after September 21, 2026, and can then be used only in existing systems.

What Do Businesses Typically Use HSMs For?

Businesses mainly use HSMs to manage the entire key life cycle and to perform cryptographic operations inside the device. NIST SP 800-57 Part 2 lists the HSM as one of the key management components used to generate, establish, distribute, store, register, suspend, revoke and destroy cryptographic keys and their metadata.

A typical use case is protecting TLS server private keys. NIST SP 1800-16 recommends that, for mission-critical systems, TLS private keys be stored in an HSM. It also notes that reusing the existing key pair when renewing a certificate is recommended only when the private key is kept in an HSM validated to FIPS 140-2 Level 2 or above.

HSMs are often discussed together with key management services, and the difference between HSM and KMS is a question businesses frequently need to clarify when choosing a solution.

What Are the Limitations of HSMs in Crypto Asset Custody?

The HSM security model protects the complete key within a single hardware boundary. With crypto assets, however, a private key used to sign can move assets directly, so who can invoke that key becomes the critical question. The threshold approach proposed in NIST IR 8214 has multiple components perform cryptographic operations together, so that security goals such as key confidentiality are maintained even if f out of n components are compromised.

In NIST IR 8214C, published in January 2026, NIST further explains that threshold schemes compute operations such as signing, encryption and decryption, and key generation in a distributed way, with the private key distributed across multiple parties through secret sharing. This is the foundation of multi-party computation (MPC) wallets, and the difference between MPC and HSM comes down to whether trust is concentrated in one device or distributed across multiple parties.

Deployment scale is also a practical consideration. NIST SP 1800-16 notes that because so many TLS servers require private keys, many organizations do not use HSMs to protect them. Hardware isolation has not lost its value as a result: a trusted execution environment (TEE) can likewise provide isolation for key shares at the processor level and be combined with MPC.

Conclusion

An HSM is a hardware device dedicated to protecting keys, and FIPS 140-3 and the CMVP provide a public, unified standard for assessing its security. For crypto asset institutions, MPC custody distributes the private key as shares across multiple parties and uses hardware isolation to protect each share, combining the strengths of both technologies.

Safeheron combines its proprietary MPC with Intel SGX hardware isolation (TEE) technology to build a security architecture that defends against both internal and external threats, fully protecting private key shares, the policy engine and customer data. Safeheron’s MPC Wallet-as-a-Service provides businesses with MPC key management and a policy engine.

Want to know how MPC and TEE work together to protect your digital assets?

Contact Safeheron’s Sales Team to Book a 1:1 Demo

Share

Looking for a secure way to manage digital assets?

Talk to our experts and find the right solution for your business.

Request a Demo