[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71CXPCSW12ZJQW3G53STG4Q":3,"skill-same:01M71CXPCSW12ZJQW3G53STG4Q":92},{"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":18,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":65,"commitSha":66,"skillDirectory":67,"forksCount":14,"repositoryHtmlUrl":68,"repositoryHomepageUrl":6,"ownerHtmlUrl":69,"ownerBlogUrl":6,"ownerDescription":70,"updatedAt":71,"install":72,"resources":85},"01M71CXPCSW12ZJQW3G53STG4Q","hardware-hsm-configure",null,"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","DCx7C5\u002Fai-marketplace","DCx7C5","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F42419559?v=4","01M71C01G2AZV3NTNGWAWSHJPP","DC","01M71C01GQW6G50S2BYMS7PP3E",0,"MIT","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fcrypto\u002Fhardware\u002Fhsm\u002Fconfigure\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"configure","hardware hsm configure","hardware","hsm","read","keys","operations","Bash","aml","cybersecurity","map","environment","manage","devices","hardware-security","pkcs11","pr","key-management","never","modules","2026-11-10 10:12:30",false,"---\nname: hardware-hsm-configure\ndescription: 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\ndomain: cybersecurity\nsubdomain: cryptography\ntags:\n- cryptography\n- hsm\n- key-management\n- pkcs11\n- hardware-security\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\nmodel: sonnet\nmaxTurns: 20\ntools: [Read, Bash, Glob, Grep]\ncapec: []\n---\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,"capec":46,"model":47,"tools":48,"domain":28,"maxTurns":52,"nist_csf":53,"subdomain":45,"description":7,"nist_ai_rmf":57,"atlas_techniques":61},[45,22,36,34,33],"cryptography",[],"sonnet",[49,26,50,51],"Read","Glob","Grep",20,[54,55,56],"PR.DS-01","PR.DS-02","PR.DS-10",[58,59,60],"MEASURE-2.7","MAP-5.1","MANAGE-2.4",[62,63,64],"AML.T0070","AML.T0066","AML.T0082","main","a91f1293287ffa9f4f1b8f486cd6e835a1568c84","skills\u002Fcrypto\u002Fhardware\u002Fhsm\u002Fconfigure","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace","https:\u002F\u002Fgithub.com\u002FDCx7C5","#Python","2026-09-01 11:21:00",{"source":8,"skillName":5,"commands":73,"prompt":83,"zipAvailable":84},[74,77,80],{"tool":75,"command":76},"npx","npx skills add DCx7C5\u002Fai-marketplace --skill hardware-hsm-configure",{"tool":78,"command":79},"bunx","bunx skills add DCx7C5\u002Fai-marketplace --skill hardware-hsm-configure",{"tool":81,"command":82},"pnpm","pnpm dlx skills add DCx7C5\u002Fai-marketplace --skill hardware-hsm-configure","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fcrypto\u002Fhardware\u002Fhsm\u002Fconfigure\u002FSKILL.md",true,[86],{"path":87,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":90,"sourceHtmlUrl":91},"index.json","REFERENCE","参考文档",679,"https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fcrypto\u002Fhardware\u002Fhsm\u002Fconfigure\u002Findex.json",[93,118,139,160,182,198],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":39},"01M71HAPZ01KQ30RKTB0FFSQ05","services-wmi-persistence-detect","Detect WMI event subscription persistence by enumerating ActiveScriptEventConsumer, CommandLineEventConsumer, and permanent subscriptions in the WMI repository.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fservices\u002Fwmi\u002Fpersistence\u002Fdetect\u002FSKILL.md",[],[100,101,102,103,104,105,106,107,108,109,110,111,112,113,114,115,116,28,117],"services","detect","services wmi persistence detect","wmi","persistence","de","cm","process","activescript","event","subscriptions","commandline-consumer","repository","subscription","event-subscription","t1546.003","forensics","process-forensics",{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":39},"01M71HAK6JTTTS229T17WJMMCG","services-wmi-exec-exploit","Perform lateral movement across Windows networks using WMI-based remote execution techniques including Impacket wmiexec.py, CrackMapExec, and native WMI commands for stealthy post-exploitation during red team engagements.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fservices\u002Fwmi\u002Fexec\u002Fexploit\u002FSKILL.md",[],[125,100,126,103,127,128,129,28,26,130,131,132,133,134,105,135,136,23,137,138],"exploit","services wmi exec exploit","exec","remote","traffic","analysis","team","across","crackmapexec","native","command","lateral movement","lateral-movement","Impacket",{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":145,"publishedAt":39},"01M71HAG6MHKNQV8KDZKMT4886","registry-artifact-extract","Extract and analyze Windows Registry hives to uncover user activity, installed software, autostart entries, and evidence of system compromise.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fregistry\u002Fartifact\u002Fextract\u002FSKILL.md",[],[146,147,148,149,150,151,28,26,152,130,153,154,105,23,155,156,157,158,159,47],"artifact","registry","registry artifact extract","extract","evidence-collection","artifact-analysis","collection","analyze","uncover","software","activity","digital-forensics","windows-registry","regripper",{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":164,"categories":165,"keywords":166,"publishedAt":39},"01M71HACR4A8XTWTTSXK4124AA","processes-token-impersonate-detect","Detect Windows token impersonation and privilege abuse including SeImpersonatePrivilege exploitation via Potato attacks and token stealing techniques.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fprocesses\u002Ftoken\u002Fimpersonate\u002Fdetect\u002FSKILL.md",[],[101,167,168,169,170,171,172,106,173,28,117,174,175,176,177,178,179,180,181,105],"processes token impersonate detect","token","processes","attacks","windows","escalation","techniques","privilege-escalation","seimpersonate","token-impersonation","printspoofer","exploitation","potato","impersonation","via",{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":188,"publishedAt":39},"01M71HAABSB4Z6QFSXEG00R4RK","processes-thread-injection-detect","Detect Windows thread injection techniques including CreateRemoteThread, QueueUserAPC, NtCreateThreadEx, and thread hijacking via process memory analysis.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fprocesses\u002Fthread\u002Finjection\u002Fdetect\u002FSKILL.md",[],[189,190,101,191,169,171,192,106,193,173,28,117,130,194,195,196,197,181,105,107],"thread","processes thread injection detect","injection","memory","process-injection","api","apc-injection","thread-injection","nt-api",{"skillNo":199,"name":200,"nameZh":6,"description":201,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":202,"categories":203,"keywords":204,"publishedAt":39},"01M71HA7H311V5G14WMX58HQSS","processes-hollow-technique-detect","Detect process hollowing (RunPE) by identifying processes with mismatched image paths between PEB and VAD tree, or unmapped PE headers in memory.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fprocesses\u002Fhollow\u002Ftechnique\u002Fdetect\u002FSKILL.md",[],[205,101,169,206,192,106,207,208,28,117,209,210,211,212,213,214,105,107,215,216],"processes hollow technique detect","tree","memory-forensics","process-hollow","peb","runpe","image","pe-header","in memory","with","mismatched","headers"]