Hardware Security Module
Also called HSM.
A tamper-resistant device that generates and guards cryptographic keys.
What it is
A dedicated, tamper-resistant hardware device that generates, stores, and uses cryptographic keys so the keys never leave it in plaintext. Cryptographic operations happen inside the module's protected boundary.
Why it matters
HSMs anchor the trust of CAs, payment systems, and code-signing pipelines by keeping private keys out of reach even on a compromised host. Their use (or absence) is a key factor in how recoverable a stolen key actually is.
In practice
A certificate authority performing all signing inside an HSM so its root private key never exists in server memory.
What to look for
- Keys marked non-exportable in the HSM.
- Admin and crypto officer roles split between people.
- Unexpected signing or decrypt operations in HSM logs.
Common mistake
Assuming the HSM protects against misuse. It keeps the key safe but will still sign whatever an authorized caller sends.
Practice it nearby
CyberKit has no tool for this term itself. These are the closest places to practice it.
In the field
Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.
-
OpenSSL Open source
The command line toolkit for inspecting certificates, keys and TLS connections.
-
HashiCorp Vault Source available
Manages secrets and encryption keys, and can encrypt data as a service.
-
AWS Key Management Service Cloud service
AWS's managed service for creating and controlling encryption keys.
Read next
- Public Key Infrastructure: The system of authorities and certificates that binds keys to identities.
- Tokenization: Replacing sensitive data with a non-sensitive surrogate value.
- Full-Disk Encryption: Encrypting an entire volume so it is unreadable without the key.