[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71CSGQR7ZQSS8KGX7NT3R65":3,"skill-same:01M71CSGQR7ZQSS8KGX7NT3R65":70},{"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":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":14,"repositoryHtmlUrl":46,"repositoryHomepageUrl":6,"ownerHtmlUrl":47,"ownerBlogUrl":6,"ownerDescription":48,"updatedAt":49,"install":50,"resources":63},"01M71CSGQR7ZQSS8KGX7NT3R65","compliance-iso-framework",null,"-| | Organizational (A.5) | 37 controls | Policies, roles, threat intelligence, cloud security | | People (A.","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\u002Fcompliance-iso-framework\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37],"framework","compliance","iso","compliance iso framework","security","cybersecurity","threat intelligence","cloud","cloud security","threat","intelligence","roles","controls","people","2026-11-10 10:12:30",false,"---\nname: compliance-iso-framework\ndescription: \"-| | Organizational (A.5) | 37 controls | Policies, roles, threat intelligence, cloud security | | People (A.\"\ndomain: cybersecurity\n---\n\n-|\n| Organizational (A.5) | 37 controls | Policies, roles, threat intelligence, cloud security |\n| People (A.6) | 8 controls | Screening, awareness, remote working, reporting |\n| Physical (A.7) | 14 controls | Perimeters, entry controls, equipment security |\n| Technological (A.8) | 34 controls | Access control, cryptography, logging, secure development |\n\n### New Controls in 2022 Edition\n11 new controls were added:\n1. A.5.7 - Threat Intelligence\n2. A.5.23 - Information Security for Cloud Services\n3. A.5.30 - ICT Readiness for Business Continuity\n4. A.7.4 - Physical Security Monitoring\n5. A.8.9 - Configuration Management\n6. A.8.10 - Information Deletion\n7. A.8.11 - Data Masking\n8. A.8.12 - Data Leakage Prevention\n9. A.8.16 - Monitoring Activities\n10. A.8.23 - Web Filtering\n11. A.8.28 - Secure Coding\n\n## Workflow\n\n### Phase 1: Gap Analysis and Scoping (Weeks 1-4)\n1. Define ISMS scope boundaries (locations, business units, systems)\n2. Identify interested parties and their requirements\n3. Perform gap analysis against ISO 27001:2022 requirements\n4. Document internal and external context (PESTLE, SWOT)\n5. Obtain top management commitment and allocate budget\n\n### Phase 2: Risk Assessment (Weeks 5-10)\n1. Define risk assessment methodology (asset-based, scenario-based, or hybrid)\n2. Create asset inventory covering information, people, processes, technology\n3. Identify threats and vulnerabilities for each asset\n4. Assess risk likelihood and impact using defined criteria\n5. Calculate risk levels and determine risk treatment options (mitigate, accept, transfer, avoid)\n6. Develop Risk Treatment Plan (RTP)\n\n### Phase 3: Control Selection and SoA (Weeks 11-14)\n1. Map risk treatments to Annex A controls\n2. Create Statement of Applicability (SoA) documenting:\n   - Which controls are applicable and justification\n   - Which controls are excluded and justification\n   - Implementation status of each control\n3. Design control implementation plans with owners and timelines\n\n### Phase 4: Implementation (Weeks 15-30)\n1. Develop and approve information security policy\n2. Implement selected Annex A controls\n3. Create mandatory documented procedures:\n   - Information Security Policy (A.5.1)\n   - Risk Assessment Process (Clause 6.1.2)\n   - Risk Treatment Process (Clause 6.1.3)\n   - Internal Audit Programme (Clause 9.2)\n   - Management Review Process (Clause 9.3)\n   - Corrective Action Procedure (Clause 10.1)\n4. Deploy technical controls and security tooling\n5. Conduct security awareness training for all personnel\n\n### Phase 5: Internal Audit and Management Review (Weeks 31-36)\n1. Plan and execute internal audit programme covering all clauses and applicable controls\n2. Document audit findings and nonconformities\n3. Implement corrective actions with root cause analysis\n4. Conduct management review covering:\n   - Status of previous actions\n   - Changes in internal\u002Fexternal issues\n   - Information security performance metrics\n   - Audit results and risk assessment outcomes\n   - Opportunities for improvement\n\n### Phase 6: Certification Audit (Weeks 37-42)\n1. **Stage 1 Audit**: Documentation review, readiness assessment\n2. Address Stage 1 findings\n3. **Stage 2 Audit**: On-site assessment of ISMS effectiveness\n4. Resolve any nonconformities (major NCRs require re-audit)\n5. Receive ISO 27001 certification (valid for 3 years)\n\n### Phase 7: Continual Improvement (Ongoing)\n1. Annual surveillance audits (Years 1 and 2)\n2. Recertification audit (Year 3)\n3. Regular risk reassessment and control effectiveness reviews\n4. Incident-driven improvements and lessons learned integration\n\n## Key Artifacts\n- ISMS Scope Document\n- Information Security Policy\n- Risk Assessment Methodology\n- Risk Register and Risk Treatment Plan\n- Statement of Applicability (SoA)\n- Internal Audit Reports\n- Management Review Minutes\n- Corrective Action Register\n- Metrics and KPI Dashboard\n\n## Common Pitfalls\n- Scope too broad or too narrow, leading to audit complications\n- Treating ISO 27001 as a checkbox exercise rather than embedding into business processes\n- Insufficient top management involvement and commitment\n- Failing to maintain documented evidence of control operation\n- Not performing regular risk reassessments as the threat landscape changes\n- Ignoring the 11 new controls in the 2022 edition during transition\n\n## Integration Points\n- **ISO 27002:2022**: Detailed implementation guidance for Annex A controls\n- **ISO 27005**: Information security risk management methodology\n- **ISO 27017**: Cloud security controls\n- **ISO 27018**: Protection of PII in cloud services\n- **ISO 27701**: Privacy Information Management System (PIMS) extension\n- **NIST CSF 2.0**: Cross-mapping for dual compliance\n- **SOC 2**: Overlapping trust service criteria\n\n## References\n- ISO\u002FIEC 27001:2022 Information Security Management Systems\n- ISO\u002FIEC 27002:2022 Information Security Controls\n- ISO\u002FIEC 27005:2022 Information Security Risk Management\n- ISMS.online ISO 27001 Annex A Guide: https:\u002F\u002Fwww.isms.online\u002Fiso-27001\u002Fannex-a-2022\u002F\n- IT Governance ISO 27001 Controls Guide: https:\u002F\u002Fwww.itgovernance.co.uk\u002Fblog\u002Fiso-27001-the-14-control-sets-of-annex-a-explained\n","-|\n| Organizational (A.5) | 37 controls | Policies, roles, threat intelligence, cloud security |\n| People (A.6) | 8 controls | Screening, awareness, remote working, reporting |\n| Physical (A.7) | 14 controls | Perimeters, entry controls, equipment security |\n| Technological (A.8) | 34 controls | Access control, cryptography, logging, secure development |\n\n### New Controls in 2022 Edition\n11 new controls were added:\n1. A.5.7 - Threat Intelligence\n2. A.5.23 - Information Security for Cloud Services\n3. A.5.30 - ICT Readiness for Business Continuity\n4. A.7.4 - Physical Security Monitoring\n5. A.8.9 - Configuration Management\n6. A.8.10 - Information Deletion\n7. A.8.11 - Data Masking\n8. A.8.12 - Data Leakage Prevention\n9. A.8.16 - Monitoring Activities\n10. A.8.23 - Web Filtering\n11. A.8.28 - Secure Coding\n\n## Workflow\n\n### Phase 1: Gap Analysis and Scoping (Weeks 1-4)\n1. Define ISMS scope boundaries (locations, business units, systems)\n2. Identify interested parties and their requirements\n3. Perform gap analysis against ISO 27001:2022 requirements\n4. Document internal and external context (PESTLE, SWOT)\n5. Obtain top management commitment and allocate budget\n\n### Phase 2: Risk Assessment (Weeks 5-10)\n1. Define risk assessment methodology (asset-based, scenario-based, or hybrid)\n2. Create asset inventory covering information, people, processes, technology\n3. Identify threats and vulnerabilities for each asset\n4. Assess risk likelihood and impact using defined criteria\n5. Calculate risk levels and determine risk treatment options (mitigate, accept, transfer, avoid)\n6. Develop Risk Treatment Plan (RTP)\n\n### Phase 3: Control Selection and SoA (Weeks 11-14)\n1. Map risk treatments to Annex A controls\n2. Create Statement of Applicability (SoA) documenting:\n   - Which controls are applicable and justification\n   - Which controls are excluded and justification\n   - Implementation status of each control\n3. Design control implementation plans with owners and timelines\n\n### Phase 4: Implementation (Weeks 15-30)\n1. Develop and approve information security policy\n2. Implement selected Annex A controls\n3. Create mandatory documented procedures:\n   - Information Security Policy (A.5.1)\n   - Risk Assessment Process (Clause 6.1.2)\n   - Risk Treatment Process (Clause 6.1.3)\n   - Internal Audit Programme (Clause 9.2)\n   - Management Review Process (Clause 9.3)\n   - Corrective Action Procedure (Clause 10.1)\n4. Deploy technical controls and security tooling\n5. Conduct security awareness training for all personnel\n\n### Phase 5: Internal Audit and Management Review (Weeks 31-36)\n1. Plan and execute internal audit programme covering all clauses and applicable controls\n2. Document audit findings and nonconformities\n3. Implement corrective actions with root cause analysis\n4. Conduct management review covering:\n   - Status of previous actions\n   - Changes in internal\u002Fexternal issues\n   - Information security performance metrics\n   - Audit results and risk assessment outcomes\n   - Opportunities for improvement\n\n### Phase 6: Certification Audit (Weeks 37-42)\n1. **Stage 1 Audit**: Documentation review, readiness assessment\n2. Address Stage 1 findings\n3. **Stage 2 Audit**: On-site assessment of ISMS effectiveness\n4. Resolve any nonconformities (major NCRs require re-audit)\n5. Receive ISO 27001 certification (valid for 3 years)\n\n### Phase 7: Continual Improvement (Ongoing)\n1. Annual surveillance audits (Years 1 and 2)\n2. Recertification audit (Year 3)\n3. Regular risk reassessment and control effectiveness reviews\n4. Incident-driven improvements and lessons learned integration\n\n## Key Artifacts\n- ISMS Scope Document\n- Information Security Policy\n- Risk Assessment Methodology\n- Risk Register and Risk Treatment Plan\n- Statement of Applicability (SoA)\n- Internal Audit Reports\n- Management Review Minutes\n- Corrective Action Register\n- Metrics and KPI Dashboard\n\n## Common Pitfalls\n- Scope too broad or too narrow, leading to audit complications\n- Treating ISO 27001 as a checkbox exercise rather than embedding into business processes\n- Insufficient top management involvement and commitment\n- Failing to maintain documented evidence of control operation\n- Not performing regular risk reassessments as the threat landscape changes\n- Ignoring the 11 new controls in the 2022 edition during transition\n\n## Integration Points\n- **ISO 27002:2022**: Detailed implementation guidance for Annex A controls\n- **ISO 27005**: Information security risk management methodology\n- **ISO 27017**: Cloud security controls\n- **ISO 27018**: Protection of PII in cloud services\n- **ISO 27701**: Privacy Information Management System (PIMS) extension\n- **NIST CSF 2.0**: Cross-mapping for dual compliance\n- **SOC 2**: Overlapping trust service criteria\n\n## References\n- ISO\u002FIEC 27001:2022 Information Security Management Systems\n- ISO\u002FIEC 27002:2022 Information Security Controls\n- ISO\u002FIEC 27005:2022 Information Security Risk Management\n- ISMS.online ISO 27001 Annex A Guide: https:\u002F\u002Fwww.isms.online\u002Fiso-27001\u002Fannex-a-2022\u002F\n- IT Governance ISO 27001 Controls Guide: https:\u002F\u002Fwww.itgovernance.co.uk\u002Fblog\u002Fiso-27001-the-14-control-sets-of-annex-a-explained\n",{"name":5,"domain":29,"description":7},"main","a91f1293287ffa9f4f1b8f486cd6e835a1568c84","skills\u002Fcompliance-iso-framework","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace","https:\u002F\u002Fgithub.com\u002FDCx7C5","#Python","2026-09-01 11:21:00",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add DCx7C5\u002Fai-marketplace --skill compliance-iso-framework",{"tool":56,"command":57},"bunx","bunx skills add DCx7C5\u002Fai-marketplace --skill compliance-iso-framework",{"tool":59,"command":60},"pnpm","pnpm dlx skills add DCx7C5\u002Fai-marketplace --skill compliance-iso-framework","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fcompliance-iso-framework\u002FSKILL.md",true,[64],{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"index.json","REFERENCE","参考文档",580,"https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fcompliance-iso-framework\u002Findex.json",[71,96,119,141,163,179],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":38},"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",[],[78,79,80,81,82,83,84,85,86,87,88,89,90,91,92,93,94,29,95],"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":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":38},"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",[],[103,78,104,81,105,106,107,29,108,109,110,111,112,113,83,114,115,116,117,118],"exploit","services wmi exec exploit","exec","remote","traffic","Bash","analysis","team","across","crackmapexec","native","command","lateral movement","read","lateral-movement","Impacket",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":38},"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",[],[126,127,128,129,130,131,29,108,132,109,133,134,83,116,135,136,137,138,139,140],"artifact","registry","registry artifact extract","extract","evidence-collection","artifact-analysis","collection","analyze","uncover","software","activity","digital-forensics","windows-registry","regripper","sonnet",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":147,"publishedAt":38},"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",[],[79,148,149,150,151,152,153,84,154,29,95,155,156,157,158,159,160,161,162,83],"processes token impersonate detect","token","processes","attacks","windows","escalation","techniques","privilege-escalation","seimpersonate","token-impersonation","printspoofer","exploitation","potato","impersonation","via",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":167,"categories":168,"keywords":169,"publishedAt":38},"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",[],[170,171,79,172,150,152,173,84,174,154,29,95,109,175,176,177,178,162,83,85],"thread","processes thread injection detect","injection","memory","process-injection","api","apc-injection","thread-injection","nt-api",{"skillNo":180,"name":181,"nameZh":6,"description":182,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":183,"categories":184,"keywords":185,"publishedAt":38},"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",[],[186,79,150,187,173,84,188,189,29,95,190,191,192,193,194,195,83,85,196,197],"processes hollow technique detect","tree","memory-forensics","process-hollow","peb","runpe","image","pe-header","in memory","with","mismatched","headers"]