[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AF77SRXQYZE6SGEPYY3PA7":3,"skill-same:01M6AF77SRXQYZE6SGEPYY3PA7":135},{"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":28,"publishedAt":45,"linkOnly":46,"markdownContent":47,"markdownBody":48,"frontMatter":49,"refName":64,"commitSha":65,"skillDirectory":66,"forksCount":67,"repositoryHtmlUrl":68,"repositoryHomepageUrl":69,"ownerHtmlUrl":70,"ownerBlogUrl":71,"ownerDescription":72,"updatedAt":73,"install":74,"resources":87},"01M6AF77SRXQYZE6SGEPYY3PA7","implementing-iso-27001-information-security-management",null,"Guides implementation of an ISO\u002FIEC 27001:2022 Information Security Management System (ISMS) end to end: gap analysis and scoping, risk assessment methodology, Annex A control selection, Statement of Applicability (SoA) creation, and continuous improvement. Use when scoping a new ISMS, preparing for ISO 27001 certification or audit, or selecting and documenting Annex A controls for a compliance program.","mukul975\u002FAnthropic-Cybersecurity-Skills","mukul975","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F42860185?v=4","01M6ADEQR8T5M4EEG6C67BQCWF","Mahipal","01M6ADJPMYWG1E5GM1FWBE3128",35990,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-iso-27001-information-security-management\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44],"security","implementing iso 27001 information security management","cybersecurity","governance","risk assessment","pr","assessment","audit","compliance","methodology","risk-management","t1078","risk","iso27001","isms","certification","2026-11-10 10:12:30",false,"---\nname: implementing-iso-27001-information-security-management\ndescription: >-\n  Guides implementation of an ISO\u002FIEC 27001:2022 Information Security Management\n  System (ISMS) end to end: gap analysis and scoping, risk assessment methodology,\n  Annex A control selection, Statement of Applicability (SoA) creation, and\n  continuous improvement. Use when scoping a new ISMS, preparing for ISO 27001\n  certification or audit, or selecting and documenting Annex A controls for a\n  compliance program.\ndomain: cybersecurity\nsubdomain: compliance-governance\ntags:\n- compliance\n- governance\n- iso27001\n- isms\n- risk-management\n- certification\nnist_csf:\n- GV.OC-01\n- GV.RM-01\n- GV.PO-01\n- ID.RA-01\n- PR.DS-01\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nmitre_attack:\n- T1078\n- T1530\n- T1685.002\n---\n# Implementing ISO 27001 Information Security Management\n\n## Overview\nISO\u002FIEC 27001:2022 is the international standard for establishing, implementing, maintaining, and continually improving an Information Security Management System (ISMS). This skill covers the complete lifecycle from scoping through certification, including Annex A control selection, risk assessment methodology, Statement of Applicability (SoA) creation, and continuous improvement processes.\n\n\n## When to Use\n\n- When deploying or configuring implementing iso 27001 information security management 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- Understanding of information security principles and risk management concepts\n- Familiarity with organizational governance structures and business processes\n- Knowledge of IT infrastructure, network architecture, and data flows\n- Access to ISO\u002FIEC 27001:2022 and ISO\u002FIEC 27002:2022 standards documents\n\n## Core Concepts\n\n### ISMS Clauses (4-10)\nThe management system requirements define **what** must be done:\n- **Clause 4 - Context of the Organization**: Define scope, interested parties, and internal\u002Fexternal issues\n- **Clause 5 - Leadership**: Top management commitment, information security policy, roles and responsibilities\n- **Clause 6 - Planning**: Risk assessment process, risk treatment plan, information security objectives\n- **Clause 7 - Support**: Resources, competence, awareness, communication, documented information\n- **Clause 8 - Operation**: Operational planning, risk assessment execution, risk treatment implementation\n- **Clause 9 - Performance Evaluation**: Monitoring, measurement, internal audit, management review\n- **Clause 10 - Improvement**: Nonconformities, corrective actions, continual improvement\n\n### Annex A Controls (2022 Edition)\nThe 2022 revision restructured 93 controls into four categories:\n\n| Category | Controls | Examples |\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","# Implementing ISO 27001 Information Security Management\n\n## Overview\nISO\u002FIEC 27001:2022 is the international standard for establishing, implementing, maintaining, and continually improving an Information Security Management System (ISMS). This skill covers the complete lifecycle from scoping through certification, including Annex A control selection, risk assessment methodology, Statement of Applicability (SoA) creation, and continuous improvement processes.\n\n\n## When to Use\n\n- When deploying or configuring implementing iso 27001 information security management 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- Understanding of information security principles and risk management concepts\n- Familiarity with organizational governance structures and business processes\n- Knowledge of IT infrastructure, network architecture, and data flows\n- Access to ISO\u002FIEC 27001:2022 and ISO\u002FIEC 27002:2022 standards documents\n\n## Core Concepts\n\n### ISMS Clauses (4-10)\nThe management system requirements define **what** must be done:\n- **Clause 4 - Context of the Organization**: Define scope, interested parties, and internal\u002Fexternal issues\n- **Clause 5 - Leadership**: Top management commitment, information security policy, roles and responsibilities\n- **Clause 6 - Planning**: Risk assessment process, risk treatment plan, information security objectives\n- **Clause 7 - Support**: Resources, competence, awareness, communication, documented information\n- **Clause 8 - Operation**: Operational planning, risk assessment execution, risk treatment implementation\n- **Clause 9 - Performance Evaluation**: Monitoring, measurement, internal audit, management review\n- **Clause 10 - Improvement**: Nonconformities, corrective actions, continual improvement\n\n### Annex A Controls (2022 Edition)\nThe 2022 revision restructured 93 controls into four categories:\n\n| Category | Controls | Examples |\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,"tags":50,"author":51,"domain":31,"license":15,"version":52,"nist_csf":53,"subdomain":59,"description":7,"mitre_attack":60},[37,32,42,43,39,44],"mahipal","1.0",[54,55,56,57,58],"GV.OC-01","GV.RM-01","GV.PO-01","ID.RA-01","PR.DS-01","compliance-governance",[61,62,63],"T1078","T1530","T1685.002","main","54a798831d2266a3ca61ce68a7acb80b81160d57","skills\u002Fimplementing-iso-27001-information-security-management",4395,"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":75,"prompt":85,"zipAvailable":86},[76,79,82],{"tool":77,"command":78},"npx","npx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill implementing-iso-27001-information-security-management",{"tool":80,"command":81},"bunx","bunx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill implementing-iso-27001-information-security-management",{"tool":83,"command":84},"pnpm","pnpm dlx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill implementing-iso-27001-information-security-management","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-iso-27001-information-security-management\u002FSKILL.md",true,[88,94,100,105,109,113,117,121,125,131],{"path":89,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":92,"sourceHtmlUrl":93},"agents\u002Fopenai.yaml","REFERENCE","参考文档",135,"https:\u002F\u002Fgithub.com\u002Ffderuiter\u002FQRCraftly-web\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftriage\u002Fagents\u002Fopenai.yaml",{"path":95,"resourceType":96,"resourceTypeDesc":97,"sizeBytes":98,"sourceHtmlUrl":99},"assets\u002Ftemplate.md","ASSET","资产文件",11715,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-iso-27001-information-security-management\u002Fassets\u002Ftemplate.md",{"path":101,"resourceType":101,"resourceTypeDesc":102,"sizeBytes":103,"sourceHtmlUrl":104},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-iso-27001-information-security-management\u002FLICENSE",{"path":106,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":107,"sourceHtmlUrl":108},"references\u002FAGENT-BRIEF.md",7942,"https:\u002F\u002Fgithub.com\u002Ffderuiter\u002FQRCraftly-web\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftriage\u002Freferences\u002FAGENT-BRIEF.md",{"path":110,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":111,"sourceHtmlUrl":112},"references\u002Fapi-reference.md",1571,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-iso-27001-information-security-management\u002Freferences\u002Fapi-reference.md",{"path":114,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":115,"sourceHtmlUrl":116},"references\u002FOUT-OF-SCOPE.md",4667,"https:\u002F\u002Fgithub.com\u002Ffderuiter\u002FQRCraftly-web\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftriage\u002Freferences\u002FOUT-OF-SCOPE.md",{"path":118,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":119,"sourceHtmlUrl":120},"references\u002Fstandards.md",7496,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-iso-27001-information-security-management\u002Freferences\u002Fstandards.md",{"path":122,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":123,"sourceHtmlUrl":124},"references\u002Fworkflows.md",6666,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-iso-27001-information-security-management\u002Freferences\u002Fworkflows.md",{"path":126,"resourceType":127,"resourceTypeDesc":128,"sizeBytes":129,"sourceHtmlUrl":130},"scripts\u002Fagent.py","SCRIPT","脚本",8356,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-iso-27001-information-security-management\u002Fscripts\u002Fagent.py",{"path":132,"resourceType":127,"resourceTypeDesc":128,"sizeBytes":133,"sourceHtmlUrl":134},"scripts\u002Fprocess.py",32518,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-iso-27001-information-security-management\u002Fscripts\u002Fprocess.py",[136,161,185,211,237,262],{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":143,"publishedAt":45},"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",[142],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[144,145,146,147,29,31,148,149,34,150,151,152,153,154,155,156,157,158,159,160],"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":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":168,"publishedAt":45},"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",[167],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[169,157,170,171,29,172,31,34,173,174,175,176,177,178,179,180,181,182,183,184],"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":186,"name":187,"nameZh":6,"description":188,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":189,"categories":190,"keywords":195,"publishedAt":45},"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",[191,194],{"categoryNo":192,"categoryName":193,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[179,196,197,198,199,31,200,201,173,37,202,203,204,205,206,40,207,208,209,210],"backup","recovery","validating backup integrity for recovery","testing","infrastructure","validation","hash-verification","incident-response","ransomware","cryptocurrency","detection","t1490","immutable","disaster-recovery","restore-testing",{"skillNo":212,"name":213,"nameZh":6,"description":214,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":215,"categories":216,"keywords":218,"publishedAt":45},"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",[217],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[219,220,221,31,222,223,224,225,226,227,228,229,230,231,232,233,176,234,235,236],"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":238,"name":239,"nameZh":6,"description":240,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":241,"categories":242,"keywords":244,"publishedAt":45},"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",[243],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[245,246,247,31,248,249,250,251,39,252,253,254,255,256,41,257,258,259,260,261],"vulnerabilities","framework","triaging vulnerabilities with ssvc framework","status","planning","CISA","vulnerability-management","nessus","qualys","openvas","cvss","remediation","vulnerability","api","prioritization","ssvc","decision-tree",{"skillNo":263,"name":264,"nameZh":6,"description":265,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":266,"categories":267,"keywords":269,"publishedAt":45},"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",[268],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[29,270,31,271,272,273,274,275,276,277,278,40,279,207,280,281,282,283,284,285],"triaging security incident","siem","file","ioc","soc","NIST-800-61","NIST","severity","edr","execution","analysis","classification","severity-classification","incident-triage","SANS-PICERL","SOC-operations"]