What is HSM (Hardware Security Module)?

HSM meaning

An HSM is a computer built only for key protection. It has its own processor, random number generator and secure storage. If someone opens the case or probes it, it is designed to erase the keys. It has strict access controls, with several administrators needed for sensitive actions, and logs every operation.

What an HSM does

The main functions are:

• Generate a key pair with a certified random source.
• Store the private key so it cannot be exported in plain form.
• Sign and decrypt inside the device on request.
• Control who may use each key and write a log of every use.
• Back up keys in an encrypted form to another HSM.

FIPS 140 and Common Criteria

Buyers look for independent certification. FIPS 140-3, from NIST (replacing FIPS 140-2), defines four security levels. Level 1 is the basic requirement, Level 2 adds tamper evidence, Level 3 adds tamper response and identity-based access, and Level 4 adds protection against environmental attacks. Many signing HSMs are validated at Level 3. Common Criteria is a separate framework often cited for signing devices. Certification applies to a specific model and version, so check the certificate number.

Forms of HSM

A network appliance in a rack, a PCIe card in a server, a small USB device and a cloud service all count. Programs usually talk to them through PKCS #11 or a vendor library. A cloud HSM means the provider runs the device and you rent access to it. The USB token is a one-person version of the same idea, and a secure element is the chip-level form found in phones.

When a business needs an HSM

A single person signing a few documents rarely does. A bank signing thousands of statements a day, or an authority issuing certificates, does. If your system holds one key that can sign on behalf of many people, protect it with an HSM. Where each person holds their own key in their phone, as in the ePahichan app, the secure hardware of the phone does the same job per user.

Key ceremonies and backup

Authorities create root keys in a documented ceremony. Several trusted people attend, the room and devices are logged, and the key is split between smart cards so no single person can use it. The HSM is then stored offline. The same care applies on a smaller scale to a business signing key: decide who may use it, who can recover it and what is logged.

Backups are the awkward part. A key that can never leave the device is safe but lost if the device fails, so HSMs support encrypted backup to a second HSM of the same family. Test the recovery before you need it.

Example: a bank signing statements

A bank issues thousands of statements and wants each one signed by the bank’s own certificate. A server prepares the PDFs and sends each hash to the HSM. The HSM signs it and returns the signature, which the server inserts. The key is never in the server’s memory.

If an attacker breaks into the server, they can ask the HSM to sign things while they have access, but they cannot take the key away and use it later elsewhere. The HSM log shows what was signed and when, which helps the bank find and revoke what was signed in that window.

FIPS 140-2 certificates and the September 2026 change

NIST’s validation program said FIPS 140-2 certificates remain accepted through 21 September 2026, after which they move to the historical list. Historical modules can stay in use in existing systems, but agencies and many regulated buyers do not accept them for new purchases. As of October 2026, that date has passed.

When buying an HSM, ask for a FIPS 140-3 certificate number and check it on the NIST validated-modules list, rather than relying on a brochure.