A hardware security module (HSM) protects cryptographic keys, the secrets behind data encryption, digital signatures, website certificates, and login tokens. When a key leaks, every protection that depends on it can no longer be trusted.
In 2023, the hacking group Storm-0558 forged authentication tokens with a Microsoft consumer account signing key it obtained, then accessed email accounts at 22 organizations, including government agencies. The US Cyber Safety Review Board said Microsoft insufficiently protected its consumer account key material and advised isolated key storage, with technologies such as dedicated HSMs where feasible.
This article explains what an HSM is, how it works, its types, its functions, and its benefits for company security.
What Is a Hardware Security Module (HSM)?
A hardware security module (HSM) is a dedicated hardware device that stores and uses cryptographic keys inside a physical boundary built to resist tampering. Applications only send data to the HSM and receive the result, so the keys never move to a regular server.
On a regular server, keys sit in files or in application memory, so anyone who takes control of the server can copy them. An HSM generates keys inside the device and never lets them leave in plaintext.
Key Components of an HSM
An HSM has four main components:
- A dedicated cryptographic processor that runs encryption, decryption, and digital signatures inside the device.
- Protected memory that stores the keys.
- A hardware-based random number generator that creates keys no one can guess.
- A casing with sensors that detect tampering attempts.
How a Hardware Security Module Works
An HSM works by running every operation that uses a key inside the device itself, so applications receive only the results and never hold the keys. The process has five steps:
- An administrator initializes the HSM and sets who may manage it, usually with smart cards and PINs.
- The HSM generates a key inside the device with its hardware random number generator and stores it in protected memory.
- An application authenticates to the HSM through a standard interface, then sends the data that needs to be encrypted or signed.
- The HSM runs the operation inside the device and returns only the result, such as encrypted data or a digital signature.
- The HSM records every request in an audit log, and key backups leave the device only in encrypted form.
Enterprise-grade HSMs also commonly enforce separation of duties, so sensitive actions such as deleting a key or changing an access policy need approval from more than one administrator.
Types of Hardware Security Modules
You can group HSMs by form factor (network, PCIe card, USB, or cloud) and by purpose (general-purpose or payment). General-purpose HSMs handle encryption and signing, while payment HSMs are built specifically to process PINs and card data.
| Type | Form | Best for |
|---|---|---|
| Network HSM | A device in a data center rack that serves servers and applications over the network | A shared key service for all applications, public key infrastructure (PKI), and high-volume digital signing |
| PCIe card HSM | A card installed in a PCI Express slot on a single server | A single application that needs fast response times |
| USB HSM | A portable device plugged into a computer | Development, testing, and keys that are rarely used |
| Cloud HSM | An HSM service rented from a cloud provider | Companies that do not want to manage physical devices or need to secure cloud application keys |
For companies outside the payments sector, the realistic choices are network HSMs or cloud HSMs, while PCIe cards and USB devices serve more specialized needs.
For payment HSMs, the applicable standard is PCI PTS HSM from the PCI Security Standards Council. Version 5.0, published in May 2026, expands the requirements for multi-tenant HSMs, which are shared by more than one customer.
HSM Functions and Use Cases in Companies
An HSM’s main function is to guard the keys that a system’s trust depends on, so companies deploy it mostly for services with high-value keys. The six examples below show how companies use it:
- A certificate authority, the issuer of digital certificates, keeps its signing key in an HSM, because a leak of that key would make every certificate it issued untrustworthy.
- An identity provider in a single sign-on (SSO) system signs user identity statements (SAML assertions and OpenID Connect tokens) with a private key. If that private key lives in an HSM, an attacker cannot take it elsewhere to sign forged tokens.
- A software publisher keeps its code signing key in an HSM so that the key cannot be copied from the build server and used to sign malicious software.
- Web servers and load balancers store the private key of their TLS certificate in an HSM, so stolen server files do not expose the key behind HTTPS connections.
- Databases and cloud storage use an HSM-held master key to protect the keys behind data encryption, and cloud services often let customers bring their own key.
- Payment service providers use payment HSMs to verify PINs and issue cards, because the keys involved determine the security of every transaction.
Each of the six examples hinges on a single key whose leak would undermine trust in every system that depends on it. Keys like these are the ones most worth moving to an HSM first, while ordinary application keys are often managed well enough by a key management service (KMS).
Benefits of a Hardware Security Module for Company Security
An HSM offers three benefits for a company, namely keys that cannot be copied after a server breach, resistance to physical tampering, and easier-to-audit compliance evidence.
1. Keys Cannot Be Copied Even If a Server Is Breached
Malware or an attacker on an application server can only ask the HSM to run operations, not take the keys. Even a server administrator cannot take a key marked non-exportable out of the device, which also reduces the insider threat.
2. Resistance to Physical Tampering
Sensors inside the HSM casing detect attempts to open or damage the device. In high-end HSMs, detection triggers key erasure (zeroization), so a stolen device is useless to an attacker.
3. Compliance Evidence That Is Easier to Audit
Enterprise-grade HSMs typically carry independent certification, such as validation under FIPS 140-3, the security standard for cryptographic modules from NIST (the US National Institute of Standards and Technology). That certification and the HSM’s access logs can show auditors that keys are managed with tested controls.
Conclusion
An HSM is a hardware device that stores and uses cryptographic keys inside a sealed physical boundary, so applications get the results without ever holding the keys. Its value is greatest for keys whose leak would break trust in other systems, such as certificate authority keys and login token signing keys.
You can start this week by listing your company’s signing keys and master encryption keys, then flagging the ones still stored as files or on regular servers. That list shows which keys should move to an HSM first.
Ready to Manage Digital Identities as a Business Security Strategy?
Request a demo today and discover how IAM solutions centralize user logins through Single Sign-On (SSO), automate employee onboarding, and protect company data from unauthorized access without disrupting productivity with repeated logins.
FAQ
No, because an HSM is most relevant to certificate authorities, payment service providers, and other companies that manage high-value keys or must meet certification requirements. General encryption needs are often met by a cloud provider’s KMS.
The cost depends on the form factor, performance, certification level, and deployment model, so no single price applies to every case. A cloud HSM replaces the device purchase with a subscription or usage fee, but the company usually remains responsible for its own key access policy.
Keys inside an HSM are hard to steal because they never leave in plaintext, but an attacker who controls an authorized application or account can still misuse the HSM. To reduce that risk, limit which accounts can request operations and update the firmware (the HSM’s built-in software) as the vendor advises.
Keys can be restored from an encrypted backup or from another HSM in the same cluster (a group of HSMs with synchronized keys) if the backup was made beforehand. Without a backup, keys created as non-exportable are lost with the device, and the data they encrypted can no longer be decrypted.
