[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AE4Z2KEBERWMSGAAGDK5XF":3,"skill-same:01M6AE4Z2KEBERWMSGAAGDK5XF":122},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":63,"commitSha":64,"skillDirectory":65,"forksCount":66,"repositoryHtmlUrl":67,"repositoryHomepageUrl":68,"ownerHtmlUrl":69,"ownerBlogUrl":70,"ownerDescription":71,"updatedAt":72,"install":73,"resources":86},"01M6AE4Z2KEBERWMSGAAGDK5XF","configuring-hsm-for-key-storage",null,"Configures Hardware Security Modules for cryptographic key storage using the PKCS#11 standard interface, covering key generation, signing, encryption, and key management on physical HSMs and SoftHSM2 for development. Use when protecting cryptographic keys so they never leave a hardened device boundary, or when building and testing PKCS#11-based key management workflows.","mukul975\u002FAnthropic-Cybersecurity-Skills","mukul975","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F42860185?v=4","01M6ADEQR8T5M4EEG6C67BQCWF","Mahipal","01M6ADJPMYWG1E5GM1FWBE3128",35925,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fconfiguring-hsm-for-key-storage\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"storage","configuring hsm for key storage","testing","hardware security","security","cybersecurity","workflows","pr","development","encryption","cryptography","hsm","key-management","pkcs11","hardware-security","2026-11-10 10:12:30",false,"---\nname: configuring-hsm-for-key-storage\ndescription: Configures Hardware Security Modules for cryptographic key storage\n  using the PKCS#11 standard interface, covering key generation, signing, encryption,\n  and key management on physical HSMs and SoftHSM2 for development. Use when protecting\n  cryptographic keys so they never leave a hardened device boundary, or when building\n  and testing PKCS#11-based key management workflows.\ndomain: cybersecurity\nsubdomain: cryptography\ntags:\n- cryptography\n- hsm\n- key-management\n- pkcs11\n- hardware-security\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_ai_rmf:\n- MEASURE-2.7\n- MAP-5.1\n- MANAGE-2.4\natlas_techniques:\n- AML.T0070\n- AML.T0066\n- AML.T0082\nnist_csf:\n- PR.DS-01\n- PR.DS-02\n- PR.DS-10\nmitre_attack:\n- T1552.004\n- T1555\n- T1078\n---\n# Configuring HSM for Key Storage\n\n## Overview\n\nHardware 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.\n\n\n## When to Use\n\n- When deploying or configuring configuring hsm for key storage capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n\n- Familiarity with cryptography concepts and tools\n- Access to a test or lab environment for safe execution\n- Python 3.8+ with required dependencies installed\n- Appropriate authorization for any testing activities\n\n## Objectives\n\n- Configure SoftHSM2 as a development PKCS#11 provider\n- Generate and manage keys inside the HSM via PKCS#11\n- Perform cryptographic operations (sign, verify, encrypt, decrypt) using HSM-resident keys\n- Implement HSM-backed certificate authority operations\n- Configure key access policies and user authentication\n- Interface with cloud HSM services (AWS CloudHSM, Azure)\n\n## Key Concepts\n\n### HSM Compliance Levels\n\n| FIPS Level | Protection | Use Case |\n|-----------|-----------|----------|\n| FIPS 140-2 Level 1 | Software only | Development |\n| FIPS 140-2 Level 2 | Tamper-evident, role-based auth | General production |\n| FIPS 140-2 Level 3 | Tamper-resistant, identity-based auth | Financial, government |\n| FIPS 140-2 Level 4 | Physical tamper response | Military, classified |\n\n### PKCS#11 Architecture\n\n```\nApplication --> PKCS#11 API --> HSM Provider --> Hardware HSM\n                                    |\n                              (SoftHSM2 for dev)\n```\n\n### Key Objects in PKCS#11\n\n| Object Type | Description | Operations |\n|-------------|-------------|-----------|\n| CKO_SECRET_KEY | Symmetric keys (AES) | Encrypt, Decrypt, Wrap |\n| CKO_PUBLIC_KEY | Public keys (RSA, EC) | Verify, Encrypt, Wrap |\n| CKO_PRIVATE_KEY | Private keys (RSA, EC) | Sign, Decrypt, Unwrap |\n| CKO_CERTIFICATE | X.509 certificates | Storage, retrieval |\n\n## Security Considerations\n\n- Never export private keys from HSM (use CKA_EXTRACTABLE=False)\n- Use separate slots\u002Fpartitions for different applications\n- Implement multi-person key ceremony for CA root keys\n- Enable audit logging for all HSM operations\n- Implement HSM backup and disaster recovery\n- Use strong PINs and enable SO (Security Officer) PIN\n\n## Validation Criteria\n\n- [ ] SoftHSM2 initializes with token and user PIN\n- [ ] AES key generates inside HSM\n- [ ] RSA key pair generates inside HSM\n- [ ] Encryption\u002Fdecryption uses HSM-resident keys\n- [ ] Signing\u002Fverification uses HSM-resident keys\n- [ ] Keys cannot be exported (non-extractable)\n- [ ] Key listing shows all HSM-stored objects\n","# Configuring HSM for Key Storage\n\n## Overview\n\nHardware 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.\n\n\n## When to Use\n\n- When deploying or configuring configuring hsm for key storage capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n\n- Familiarity with cryptography concepts and tools\n- Access to a test or lab environment for safe execution\n- Python 3.8+ with required dependencies installed\n- Appropriate authorization for any testing activities\n\n## Objectives\n\n- Configure SoftHSM2 as a development PKCS#11 provider\n- Generate and manage keys inside the HSM via PKCS#11\n- Perform cryptographic operations (sign, verify, encrypt, decrypt) using HSM-resident keys\n- Implement HSM-backed certificate authority operations\n- Configure key access policies and user authentication\n- Interface with cloud HSM services (AWS CloudHSM, Azure)\n\n## Key Concepts\n\n### HSM Compliance Levels\n\n| FIPS Level | Protection | Use Case |\n|-----------|-----------|----------|\n| FIPS 140-2 Level 1 | Software only | Development |\n| FIPS 140-2 Level 2 | Tamper-evident, role-based auth | General production |\n| FIPS 140-2 Level 3 | Tamper-resistant, identity-based auth | Financial, government |\n| FIPS 140-2 Level 4 | Physical tamper response | Military, classified |\n\n### PKCS#11 Architecture\n\n```\nApplication --> PKCS#11 API --> HSM Provider --> Hardware HSM\n                                    |\n                              (SoftHSM2 for dev)\n```\n\n### Key Objects in PKCS#11\n\n| Object Type | Description | Operations |\n|-------------|-------------|-----------|\n| CKO_SECRET_KEY | Symmetric keys (AES) | Encrypt, Decrypt, Wrap |\n| CKO_PUBLIC_KEY | Public keys (RSA, EC) | Verify, Encrypt, Wrap |\n| CKO_PRIVATE_KEY | Private keys (RSA, EC) | Sign, Decrypt, Unwrap |\n| CKO_CERTIFICATE | X.509 certificates | Storage, retrieval |\n\n## Security Considerations\n\n- Never export private keys from HSM (use CKA_EXTRACTABLE=False)\n- Use separate slots\u002Fpartitions for different applications\n- Implement multi-person key ceremony for CA root keys\n- Enable audit logging for all HSM operations\n- Implement HSM backup and disaster recovery\n- Use strong PINs and enable SO (Security Officer) PIN\n\n## Validation Criteria\n\n- [ ] SoftHSM2 initializes with token and user PIN\n- [ ] AES key generates inside HSM\n- [ ] RSA key pair generates inside HSM\n- [ ] Encryption\u002Fdecryption uses HSM-resident keys\n- [ ] Signing\u002Fverification uses HSM-resident keys\n- [ ] Keys cannot be exported (non-extractable)\n- [ ] Key listing shows all HSM-stored objects\n",{"name":5,"tags":44,"author":45,"domain":29,"license":15,"version":46,"nist_csf":47,"subdomain":34,"description":7,"nist_ai_rmf":51,"mitre_attack":55,"atlas_techniques":59},[34,35,36,37,38],"mahipal","1.0",[48,49,50],"PR.DS-01","PR.DS-02","PR.DS-10",[52,53,54],"MEASURE-2.7","MAP-5.1","MANAGE-2.4",[56,57,58],"T1552.004","T1555","T1078",[60,61,62],"AML.T0070","AML.T0066","AML.T0082","main","54a798831d2266a3ca61ce68a7acb80b81160d57","skills\u002Fconfiguring-hsm-for-key-storage",4384,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills","https:\u002F\u002Fmahipal.engineer\u002FAnthropic-Cybersecurity-Skills\u002F","https:\u002F\u002Fgithub.com\u002Fmukul975","Mahipal.engineer","🔐 Cybersecurity | 💻 Dev | 📷 Street Photographer\r\n🎓 MSc | 📚 Research & AI Security","2026-08-31 12:32:44",{"source":8,"skillName":5,"commands":74,"prompt":84,"zipAvailable":85},[75,78,81],{"tool":76,"command":77},"npx","npx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill configuring-hsm-for-key-storage",{"tool":79,"command":80},"bunx","bunx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill configuring-hsm-for-key-storage",{"tool":82,"command":83},"pnpm","pnpm dlx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill configuring-hsm-for-key-storage","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fconfiguring-hsm-for-key-storage\u002FSKILL.md",true,[87,93,98,104,108,112,118],{"path":88,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":91,"sourceHtmlUrl":92},"assets\u002Ftemplate.md","ASSET","资产文件",1254,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fconfiguring-hsm-for-key-storage\u002Fassets\u002Ftemplate.md",{"path":94,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":96,"sourceHtmlUrl":97},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fconfiguring-hsm-for-key-storage\u002FLICENSE",{"path":99,"resourceType":100,"resourceTypeDesc":101,"sizeBytes":102,"sourceHtmlUrl":103},"references\u002Fapi-reference.md","REFERENCE","参考文档",1807,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fconfiguring-hsm-for-key-storage\u002Freferences\u002Fapi-reference.md",{"path":105,"resourceType":100,"resourceTypeDesc":101,"sizeBytes":106,"sourceHtmlUrl":107},"references\u002Fstandards.md",1611,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fconfiguring-hsm-for-key-storage\u002Freferences\u002Fstandards.md",{"path":109,"resourceType":100,"resourceTypeDesc":101,"sizeBytes":110,"sourceHtmlUrl":111},"references\u002Fworkflows.md",1586,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fconfiguring-hsm-for-key-storage\u002Freferences\u002Fworkflows.md",{"path":113,"resourceType":114,"resourceTypeDesc":115,"sizeBytes":116,"sourceHtmlUrl":117},"scripts\u002Fagent.py","SCRIPT","脚本",4940,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fconfiguring-hsm-for-key-storage\u002Fscripts\u002Fagent.py",{"path":119,"resourceType":114,"resourceTypeDesc":115,"sizeBytes":120,"sourceHtmlUrl":121},"scripts\u002Fprocess.py",13002,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fconfiguring-hsm-for-key-storage\u002Fscripts\u002Fprocess.py",[123,150,174,199,225,252],{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":132,"publishedAt":39},"01M6AGDM3HJXTKXX15ZZ0ZVCJ3","verifying-build-provenance-with-slsa-sigstore","Verifies artifact signatures and SLSA provenance using Sigstore's cosign (verify, verify-attestation, verify-blob-attestation) and slsa-verifier (verify-artifact), enforcing keyless OIDC builder identity and source repo against SLSA Build levels. Use in CI\u002FCD before deploying artifacts, when consuming third-party attestations, establishing a SLSA Build L3 pipeline, or confirming provenance during incident response or admission control.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fverifying-build-provenance-with-slsa-sigstore\u002FSKILL.md",[129],{"categoryNo":130,"categoryName":131,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[133,134,135,136,28,29,137,138,31,139,140,141,142,143,144,145,146,147,148,149],"sigstore","provenance","slsa","verifying build provenance with slsa sigstore","incident response","identity","code","artifacts","ci","supply-chain","pipeline","supply-chain-security","t1195","attestation","code-signing","cosign","keyless",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":157,"publishedAt":39},"01M6AGDGBPWYVZ2F11GFKJ4HZ9","validating-tpm-measured-boot-attestation","Verifies TPM 2.0 measured-boot integrity and remote attestation with tpm2-tools -- reading PCRs (tpm2_pcrread), replaying the boot event log, generating and checking signed quotes (tpm2_quote\u002Ftpm2_checkquote), and sealing secrets to a PCR policy. Use to confirm a system booted trusted firmware\u002Fkernel for Zero Trust device posture, detect boot-chain tampering via PCR drift, or build a golden-value baseline for fleet attestation.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fvalidating-tpm-measured-boot-attestation\u002FSKILL.md",[156],{"categoryNo":130,"categoryName":131,"taxonomyType":21,"taxonomyTypeDesc":22},[158,146,159,160,28,161,29,31,162,163,164,165,166,167,168,169,170,171,172,173],"boot","TPM","validating tpm measured boot attestation","policy","verification","ZeRO","firmware","Tools","measured-boot","PCR","integrity","secrets","remote-attestation","tpm2-tools","integrity-verification","trusted-computing",{"skillNo":175,"name":176,"nameZh":6,"description":177,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":178,"categories":179,"keywords":182,"publishedAt":39},"01M6AGDCW0Y4FXZ3362GT1941M","validating-backup-integrity-for-recovery","Validates backup integrity through cryptographic hash verification, automated restore testing, corruption detection, and recoverability checks to confirm backups are reliable for disaster recovery and ransomware response. Use before relying on backups for recovery, when building post-backup validation pipelines, auditing backup infrastructure for compliance, or checking immutable\u002Fair-gapped backups for silent corruption or tampering.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fvalidating-backup-integrity-for-recovery\u002FSKILL.md",[180,181],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":130,"categoryName":131,"taxonomyType":21,"taxonomyTypeDesc":22},[168,183,184,185,26,29,186,187,162,188,189,190,191,192,193,194,195,196,197,198],"backup","recovery","validating backup integrity for recovery","infrastructure","validation","compliance","hash-verification","incident-response","ransomware","cryptocurrency","detection","t1078","t1490","immutable","disaster-recovery","restore-testing",{"skillNo":200,"name":201,"nameZh":6,"description":202,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":203,"categories":204,"keywords":206,"publishedAt":39},"01M6AGD9GBG2KZ336AE763J3WH","triaging-windows-with-kape","Runs KAPE (Kroll Artifact Parser and Extractor) to collect targeted forensic artifacts (registry hives, $MFT, event logs, prefetch, browser data) via Targets and parse them with Modules wrapping Eric Zimmerman's EZ Tools (PECmd, MFTECmd, RECmd). Use during early incident containment\u002Ftriage when full disk imaging is impractical but a defensible, parseable Windows artifact set is needed quickly, including at-scale remote collection.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ftriaging-windows-with-kape\u002FSKILL.md",[205],{"categoryNo":130,"categoryName":131,"taxonomyType":21,"taxonomyTypeDesc":22},[207,208,209,29,210,211,212,213,214,215,216,217,218,219,220,221,165,222,223,224],"windows","kape","triaging windows with kape","registry","browser","logs","windows-forensics","dfir","mft","mftecmd","data","prefetch","eric-zimmerman","digital-forensics","SET","collection","pecmd","artifact-collection",{"skillNo":226,"name":227,"nameZh":6,"description":228,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":229,"categories":230,"keywords":232,"publishedAt":39},"01M6AGD5PW5J4EVZM958WD74ZQ","triaging-vulnerabilities-with-ssvc-framework","Triages and prioritizes vulnerabilities with CISA's Stakeholder-Specific Vulnerability Categorization (SSVC) decision tree, weighing exploitation status (via the CISA KEV catalog and FIRST EPSS API), technical impact, automatability, and mission prevalence to output Track\u002FTrack*\u002FAttend\u002FAct decisions. Use when prioritizing vulnerability scan results (OpenVAS, Nessus, Qualys) for remediation planning beyond raw CVSS scores.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ftriaging-vulnerabilities-with-ssvc-framework\u002FSKILL.md",[231],{"categoryNo":130,"categoryName":131,"taxonomyType":21,"taxonomyTypeDesc":22},[233,234,235,29,236,237,238,239,240,241,242,243,244,245,246,247,248,249,250,251],"vulnerabilities","framework","triaging vulnerabilities with ssvc framework","status","planning","CISA","vulnerability-management","risk-management","nessus","qualys","openvas","cvss","remediation","risk","vulnerability","api","prioritization","ssvc","decision-tree",{"skillNo":253,"name":254,"nameZh":6,"description":255,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":256,"categories":257,"keywords":259,"publishedAt":39},"01M6AGD24TTQQM4CXG69E3B9TJ","triaging-security-incident","Performs initial triage of security incidents using the NIST SP 800-61r3 and SANS PICERL frameworks, classifying incident type, assigning priority by business impact, and routing to the appropriate response team. Use when a SIEM\u002FEDR alert needs human classification, concurrent alerts must be prioritized, or a user report or threat-intel IOC match requires initial incident categorization.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ftriaging-security-incident\u002FSKILL.md",[258],{"categoryNo":130,"categoryName":131,"taxonomyType":21,"taxonomyTypeDesc":22},[28,260,29,261,262,263,264,265,266,267,268,194,269,195,270,271,272,273,274,275],"triaging security incident","siem","file","ioc","soc","NIST-800-61","NIST","severity","edr","execution","analysis","classification","severity-classification","incident-triage","SANS-PICERL","SOC-operations"]