Hardware Security Module
What is Hardware Security Module?
A dedicated cryptographic processor that provides secure generation, storage, and management of digital keys and performs encryption operations in a tamper-resistant device.
Terms that appear alongside hardware security module
Each of these is named in at least one of the same controls as hardware security module. The number is how many controls name both.
- encryption 5 shared controls
- fips 4 shared controls
- key management 4 shared controls
- tls 3 shared controls
- hardware security module hsm 3 shared controls
- audit 3 shared controls
- authentication 3 shared controls
- encryption at rest 3 shared controls
Frameworks that govern hardware security module
What the standards actually require on hardware security module
Requirements naming hardware security module across 6 standards, quoted from the control text.
Private keys for Microsoft AD CS CA servers are protected by a hardware security module.
ISM-1957 · HSM protection of CA private keys →Security Dimension 3 Non-Repudiation per X.805 Clause 6.3: Non-repudiation stops a person or entity from credibly denying that it carried out a given action on data, by keeping evidence of network-related actions available (for example evidence of an obligatio...
X805-Dim3-Non-Repudiation-Proof-Origin-Delivery-Sender-Receiver-Denial-Prevention · ITU-T X.805 Security Dimension 3 - Non-Repudiation + Proof of Origin + Proof of Delivery + Sender + Receiver Denial Prevention + Digital Signatures + Timestamping + Audit Logs + Forensic Evidence + Court-Admissible Records →OMB, with NIST, CISA and GSA, requires FCEB agencies to follow best practices on the protection and management of hardware security modules, trusted execution environments or other isolation technologies for the access tokens and cryptographic keys that cloud...
us-executive-order-14144-strengthening-and-promoting-innovation-in-the-nations-cybersecurity::4(g)(iii) · Sec. 4(g)(iii) Follow best practice for HSMs and isolation protecting cloud keys →Where the institution administers its own keys, policies cover how keys are securely generated, distributed, used, stored, renewed, revoked, recovered and destroyed.
adgm-fsra-information-technology-risk-management-guidance-ver01-201124::13.2 · Manage cryptographic keys securely through their lifecycle: generation in secure modules, protected storage and transport, purpose and expiry controls, revocation and destruction, inventory, rotation, compromise response, third-party oversight and logging →Data stored on the cloud, data in transit and the channel used to access them are encrypted at a level proportionate to the materiality of the assets, the deployment model and the risks, with encryption keys stored separately from virtual images and data.
bank-of-mauritius-guideline-on-use-of-cloud-services-2022::7.2.viii · Encrypt data at rest and in transit and manage encryption keys under institution control →Stored and transferred data and their backups, above all sensitive data, are protected by adequate encryption controls: detailed, periodically reviewed policies and procedures govern encryption keys through creation, storage, use, expiry, renewal and archiving...
central-bank-of-jordan-cloud-computing-guideline-2018::2.7.2 · Encrypt data at rest, in transit and in backups under controlled key management →Questions people ask about hardware security module
What is Hardware Security Module?
Why is Hardware Security Module important for compliance?
Which compliance frameworks address Hardware Security Module?
Where can I learn more about Hardware Security Module?
See how Hardware Security Module applies across compliance frameworks
Our platform maps 1,305 frameworks with 315K cross-framework control mappings. Explore how this concept is addressed across standards.