Claude 24f816b6a3
Consolidate 22 sibling repos into layered organism structure
Place useful parts of the surrounding repos into sica-fondt by layer, per the
body model (Ada = membrane; brain/endocrine/capabilities/knowledge non-Ada):

- brain/        LLM reasoning + providers (dapr, hermes, MoMoA)
- capabilities/ REPRAG sidecars: hermes tools/skills, dapr tools, parallel
                dispatch, A51 channels, and the OSINT cluster
- knowledge/    LORAG corpus: 754 cyber-skills, agency personas, secure-coding,
                MITRE ATT&CK data
- reference/    defensive threat-reference (C3, shhbruh doc) + AdaYaml parser

License handling: AGPL sources (worldosint, advanced_evolution, mercury,
Reticulum) and GPL DeTTECT are SPEC-only clean-room/port descriptions — no
copyleft code copied. MIT/Apache/data parts copied as working trees.

Safety: shhbruh escape/persistence material and C3 covert-C2 kept as reference
only, not wired into the running organism. See CONSOLIDATION.md.

https://claude.ai/code/session_01UehUqEXXJJCsHoA4voCU5c
2026-06-10 06:53:01 +00:00

2.2 KiB

name description domain subdomain tags version author license nist_ai_rmf atlas_techniques nist_csf
performing-hardware-security-module-integration Integrate Hardware Security Modules (HSMs) using PKCS#11 interface for cryptographic key management, signing operations, and secure key storage with python-pkcs11, AWS CloudHSM, and YubiHSM2. cybersecurity cryptography
HSM
PKCS11
CloudHSM
YubiHSM2
key-management
cryptographic-operations
hardware-security
1.0 mahipal Apache-2.0
MEASURE-2.7
MAP-5.1
MANAGE-2.4
AML.T0070
AML.T0066
AML.T0082
PR.DS-01
PR.DS-02
PR.DS-10

Performing Hardware Security Module Integration

Overview

Hardware Security Modules (HSMs) provide tamper-resistant cryptographic key storage and operations. This skill covers integrating with HSMs via the PKCS#11 standard interface using python-pkcs11, performing key generation, signing, encryption, and verification operations, querying token and slot information, and validating HSM configuration for compliance with FIPS 140-2/3 requirements.

When to Use

  • When conducting security assessments that involve performing hardware security module integration
  • When following incident response procedures for related security events
  • When performing scheduled security testing or auditing activities
  • When validating security controls through hands-on testing

Prerequisites

  • HSM device or software HSM (SoftHSM2 for testing)
  • PKCS#11 shared library (.so/.dll) for the HSM vendor
  • Python 3.9+ with python-pkcs11
  • Token initialized with SO PIN and user PIN
  • For AWS CloudHSM: cloudhsm-pkcs11 provider configured

Steps

  1. Load PKCS#11 library and enumerate available slots and tokens
  2. Open session and authenticate with user PIN
  3. Generate RSA 2048-bit or EC P-256 key pairs on the HSM
  4. Perform signing and verification using on-device keys
  5. List all objects (keys, certificates) stored on the token
  6. Query mechanism list to verify supported algorithms
  7. Generate compliance report with key inventory and algorithm audit

Expected Output

  • JSON report listing HSM slots, tokens, stored keys, supported mechanisms, and compliance status
  • Signing test results with key metadata and algorithm details