mirror of
https://github.com/mukul975/Anthropic-Cybersecurity-Skills.git
synced 2026-07-24 13:40:57 +03:00
72 lines
2.9 KiB
Markdown
72 lines
2.9 KiB
Markdown
---
|
|
name: configuring-hsm-for-key-storage
|
|
description: Hardware Security Modules (HSMs) are tamper-resistant physical devices that safeguard cryptographic keys and perform cryptographic operations in a hardened environment. Keys stored in an HSM never lea
|
|
domain: cybersecurity
|
|
subdomain: cryptography
|
|
tags: [cryptography, hsm, key-management, pkcs11, hardware-security]
|
|
version: "1.0"
|
|
author: mahipal
|
|
license: MIT
|
|
---
|
|
# Configuring HSM for Key Storage
|
|
|
|
## Overview
|
|
|
|
Hardware Security Modules (HSMs) are tamper-resistant physical devices that safeguard cryptographic keys and perform cryptographic operations in a hardened environment. Keys stored in an HSM never leave the device boundary, providing the highest level of key protection. This skill covers configuring HSMs using the PKCS#11 standard interface, including key generation, signing, encryption, and key management using both physical HSMs and SoftHSM2 for development.
|
|
|
|
## Objectives
|
|
|
|
- Configure SoftHSM2 as a development PKCS#11 provider
|
|
- Generate and manage keys inside the HSM via PKCS#11
|
|
- Perform cryptographic operations (sign, verify, encrypt, decrypt) using HSM-resident keys
|
|
- Implement HSM-backed certificate authority operations
|
|
- Configure key access policies and user authentication
|
|
- Interface with cloud HSM services (AWS CloudHSM, Azure)
|
|
|
|
## Key Concepts
|
|
|
|
### HSM Compliance Levels
|
|
|
|
| FIPS Level | Protection | Use Case |
|
|
|-----------|-----------|----------|
|
|
| FIPS 140-2 Level 1 | Software only | Development |
|
|
| FIPS 140-2 Level 2 | Tamper-evident, role-based auth | General production |
|
|
| FIPS 140-2 Level 3 | Tamper-resistant, identity-based auth | Financial, government |
|
|
| FIPS 140-2 Level 4 | Physical tamper response | Military, classified |
|
|
|
|
### PKCS#11 Architecture
|
|
|
|
```
|
|
Application --> PKCS#11 API --> HSM Provider --> Hardware HSM
|
|
|
|
|
(SoftHSM2 for dev)
|
|
```
|
|
|
|
### Key Objects in PKCS#11
|
|
|
|
| Object Type | Description | Operations |
|
|
|-------------|-------------|-----------|
|
|
| CKO_SECRET_KEY | Symmetric keys (AES) | Encrypt, Decrypt, Wrap |
|
|
| CKO_PUBLIC_KEY | Public keys (RSA, EC) | Verify, Encrypt, Wrap |
|
|
| CKO_PRIVATE_KEY | Private keys (RSA, EC) | Sign, Decrypt, Unwrap |
|
|
| CKO_CERTIFICATE | X.509 certificates | Storage, retrieval |
|
|
|
|
## Security Considerations
|
|
|
|
- Never export private keys from HSM (use CKA_EXTRACTABLE=False)
|
|
- Use separate slots/partitions for different applications
|
|
- Implement multi-person key ceremony for CA root keys
|
|
- Enable audit logging for all HSM operations
|
|
- Implement HSM backup and disaster recovery
|
|
- Use strong PINs and enable SO (Security Officer) PIN
|
|
|
|
## Validation Criteria
|
|
|
|
- [ ] SoftHSM2 initializes with token and user PIN
|
|
- [ ] AES key generates inside HSM
|
|
- [ ] RSA key pair generates inside HSM
|
|
- [ ] Encryption/decryption uses HSM-resident keys
|
|
- [ ] Signing/verification uses HSM-resident keys
|
|
- [ ] Keys cannot be exported (non-extractable)
|
|
- [ ] Key listing shows all HSM-stored objects
|