[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AFAQX1AJHV51SZ4Z35CX9Z":3,"skill-same:01M6AFAQX1AJHV51SZ4Z35CX9Z":124},{"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":34,"publishedAt":50,"linkOnly":51,"markdownContent":52,"markdownBody":53,"frontMatter":54,"refName":69,"commitSha":70,"skillDirectory":71,"forksCount":72,"repositoryHtmlUrl":73,"repositoryHomepageUrl":74,"ownerHtmlUrl":75,"ownerBlogUrl":76,"ownerDescription":77,"updatedAt":78,"install":79,"resources":92},"01M6AFAQX1AJHV51SZ4Z35CX9Z","implementing-pci-dss-compliance-controls",null,"Implements PCI DSS 4.0.1's 12 requirements across 6 control objectives for organizations that store, process, or transmit cardholder data, including the customized validation approach, enhanced authentication, and continuous monitoring controls introduced by the 51 requirements mandatory since March 2025. Use when scoping a cardholder data environment, building PCI DSS 4.0.1 compliance controls, or preparing for a PCI assessment.","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-pci-dss-compliance-controls\u002FSKILL.md",[18,23,26,31],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",{"categoryNo":32,"categoryName":33,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000037","律师与法务",[35,36,37,38,39,40,41,42,43,44,45,46,47,48,49],"compliance","implementing pci dss compliance controls","security","cybersecurity","governance","pr","assessment","authentication","validation","monitoring","data","t1078","pci-dss","payment-security","cardholder-data","2026-11-10 10:12:30",false,"---\nname: implementing-pci-dss-compliance-controls\ndescription: Implements PCI DSS 4.0.1's 12 requirements across 6 control objectives\n  for organizations that store, process, or transmit cardholder data, including the\n  customized validation approach, enhanced authentication, and continuous monitoring\n  controls introduced by the 51 requirements mandatory since March 2025. Use when\n  scoping a cardholder data environment, building PCI DSS 4.0.1 compliance controls,\n  or preparing for a PCI assessment.\ndomain: cybersecurity\nsubdomain: compliance-governance\ntags:\n- compliance\n- governance\n- pci-dss\n- payment-security\n- cardholder-data\nnist_csf:\n- GV.PO-01\n- PR.DS-01\n- PR.AA-01\n- DE.CM-01\n- ID.RA-01\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nmitre_attack:\n- T1078\n- T1530\n- T1685.002\n---\n# Implementing PCI DSS Compliance Controls\n\n## Overview\nPCI DSS 4.0.1 establishes 12 requirements across 6 control objectives for organizations that store, process, or transmit cardholder data. With PCI DSS 3.2.1 retiring April 2024 and 51 new requirements becoming mandatory March 31, 2025, this skill covers implementing all requirements including the new customized validation approach, enhanced authentication, and continuous monitoring controls.\n\n\n## When to Use\n\n- When deploying or configuring implementing pci dss compliance controls 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 payment card processing flows and cardholder data environment (CDE)\n- Knowledge of network segmentation and security architecture\n- Access to cardholder data environment for scoping\n- Understanding of PCI compliance validation levels (merchant levels 1-4, service provider levels 1-2)\n\n## Core Concepts\n\n### 12 PCI DSS Requirements by Control Objective\n\n**Build and Maintain a Secure Network and Systems**\n1. Install and maintain network security controls (firewalls, NSCs)\n2. Apply secure configurations to all system components\n\n**Protect Account Data**\n3. Protect stored account data (encryption, tokenization, truncation)\n4. Protect cardholder data with strong cryptography during transmission\n\n**Maintain a Vulnerability Management Program**\n5. Protect all systems and networks from malicious software\n6. Develop and maintain secure systems and software\n\n**Implement Strong Access Control Measures**\n7. Restrict access to system components and cardholder data by business need to know\n8. Identify users and authenticate access to system components\n9. Restrict physical access to cardholder data\n\n**Regularly Monitor and Test Networks**\n10. Log and monitor all access to system components and cardholder data\n11. Test security of systems and networks regularly\n\n**Maintain an Information Security Policy**\n12. Support information security with organizational policies and programs\n\n### Key PCI DSS 4.0 Changes\n- **Customized Approach**: Alternative to defined approach, allowing custom control design with objective-based validation\n- **MFA for all CDE access**: Extended beyond admin to all access to cardholder data (Req 8.4.2)\n- **Targeted Risk Analysis**: Organizations perform their own risk analysis for flexible requirements\n- **Authenticated Vulnerability Scanning**: Internal scans must use authenticated scanning (Req 11.3.1.1)\n- **Anti-phishing mechanisms**: Technical controls to detect and protect against phishing (Req 5.4.1)\n- **Automated log review**: Automated mechanisms for review of audit logs (Req 10.4.1.1)\n\n## Workflow\n\n### Phase 1: Scoping and Assessment (Weeks 1-4)\n1. Identify all cardholder data flows (card present, card not present, storage)\n2. Define Cardholder Data Environment (CDE) boundaries\n3. Validate network segmentation effectiveness\n4. Determine compliance validation level\n5. Conduct PCI DSS gap assessment against all 12 requirements\n\n### Phase 2: Network and System Security (Weeks 5-12)\n1. Deploy and configure network security controls (Req 1)\n2. Implement network segmentation to minimize CDE scope\n3. Harden system configurations using CIS Benchmarks (Req 2)\n4. Implement WAF for public-facing web applications (Req 6.4.1)\n5. Deploy anti-malware on all in-scope systems (Req 5)\n\n### Phase 3: Data Protection (Weeks 13-20)\n1. Implement encryption for stored cardholder data (Req 3)\n2. Deploy tokenization where possible to reduce scope\n3. Enforce TLS 1.2+ for all cardholder data transmission (Req 4)\n4. Implement key management procedures\n5. Deploy data discovery tools to locate unencrypted cardholder data\n\n### Phase 4: Access Controls (Weeks 21-28)\n1. Implement RBAC based on business need to know (Req 7)\n2. Deploy MFA for all access to CDE (Req 8)\n3. Implement unique user IDs for all users\n4. Enforce password policies meeting PCI DSS 4.0 requirements\n5. Implement physical access controls for CDE facilities (Req 9)\n\n### Phase 5: Monitoring and Testing (Weeks 29-36)\n1. Deploy centralized logging for all CDE components (Req 10)\n2. Implement automated log review mechanisms\n3. Conduct internal and external vulnerability scans (Req 11)\n4. Perform penetration testing (internal and external)\n5. Implement file integrity monitoring (FIM) for critical files\n\n### Phase 6: Policy and Governance (Weeks 37-42)\n1. Develop comprehensive information security policy (Req 12)\n2. Implement security awareness training including anti-phishing\n3. Establish incident response plan specific to cardholder data\n4. Conduct targeted risk analyses for flexible requirements\n5. Document and validate all controls for assessment\n\n## Key Artifacts\n- CDE Scope Documentation and Network Diagrams\n- Self-Assessment Questionnaire (SAQ) or Report on Compliance (ROC)\n- Attestation of Compliance (AOC)\n- Quarterly ASV Scan Reports\n- Annual Penetration Test Report\n- Risk Assessment Documentation\n- Security Policies and Procedures\n\n## Common Pitfalls\n- Scope creep due to inadequate network segmentation\n- Storing prohibited data (CVV, full track data) after authorization\n- Missing the March 2025 deadline for new mandatory requirements\n- Treating PCI DSS as annual compliance rather than continuous security\n- Not including cloud and container environments in CDE scope\n\n## References\n- PCI DSS v4.0.1: https:\u002F\u002Fwww.pcisecuritystandards.org\u002Fdocument_library\u002F\n- PCI SSC Quick Reference Guide\n- PCI DSS 4.0 Summary of Changes\n- UpGuard PCI DSS 4.0 Guide: https:\u002F\u002Fwww.upguard.com\u002Fblog\u002Fpci-compliance\n","# Implementing PCI DSS Compliance Controls\n\n## Overview\nPCI DSS 4.0.1 establishes 12 requirements across 6 control objectives for organizations that store, process, or transmit cardholder data. With PCI DSS 3.2.1 retiring April 2024 and 51 new requirements becoming mandatory March 31, 2025, this skill covers implementing all requirements including the new customized validation approach, enhanced authentication, and continuous monitoring controls.\n\n\n## When to Use\n\n- When deploying or configuring implementing pci dss compliance controls 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 payment card processing flows and cardholder data environment (CDE)\n- Knowledge of network segmentation and security architecture\n- Access to cardholder data environment for scoping\n- Understanding of PCI compliance validation levels (merchant levels 1-4, service provider levels 1-2)\n\n## Core Concepts\n\n### 12 PCI DSS Requirements by Control Objective\n\n**Build and Maintain a Secure Network and Systems**\n1. Install and maintain network security controls (firewalls, NSCs)\n2. Apply secure configurations to all system components\n\n**Protect Account Data**\n3. Protect stored account data (encryption, tokenization, truncation)\n4. Protect cardholder data with strong cryptography during transmission\n\n**Maintain a Vulnerability Management Program**\n5. Protect all systems and networks from malicious software\n6. Develop and maintain secure systems and software\n\n**Implement Strong Access Control Measures**\n7. Restrict access to system components and cardholder data by business need to know\n8. Identify users and authenticate access to system components\n9. Restrict physical access to cardholder data\n\n**Regularly Monitor and Test Networks**\n10. Log and monitor all access to system components and cardholder data\n11. Test security of systems and networks regularly\n\n**Maintain an Information Security Policy**\n12. Support information security with organizational policies and programs\n\n### Key PCI DSS 4.0 Changes\n- **Customized Approach**: Alternative to defined approach, allowing custom control design with objective-based validation\n- **MFA for all CDE access**: Extended beyond admin to all access to cardholder data (Req 8.4.2)\n- **Targeted Risk Analysis**: Organizations perform their own risk analysis for flexible requirements\n- **Authenticated Vulnerability Scanning**: Internal scans must use authenticated scanning (Req 11.3.1.1)\n- **Anti-phishing mechanisms**: Technical controls to detect and protect against phishing (Req 5.4.1)\n- **Automated log review**: Automated mechanisms for review of audit logs (Req 10.4.1.1)\n\n## Workflow\n\n### Phase 1: Scoping and Assessment (Weeks 1-4)\n1. Identify all cardholder data flows (card present, card not present, storage)\n2. Define Cardholder Data Environment (CDE) boundaries\n3. Validate network segmentation effectiveness\n4. Determine compliance validation level\n5. Conduct PCI DSS gap assessment against all 12 requirements\n\n### Phase 2: Network and System Security (Weeks 5-12)\n1. Deploy and configure network security controls (Req 1)\n2. Implement network segmentation to minimize CDE scope\n3. Harden system configurations using CIS Benchmarks (Req 2)\n4. Implement WAF for public-facing web applications (Req 6.4.1)\n5. Deploy anti-malware on all in-scope systems (Req 5)\n\n### Phase 3: Data Protection (Weeks 13-20)\n1. Implement encryption for stored cardholder data (Req 3)\n2. Deploy tokenization where possible to reduce scope\n3. Enforce TLS 1.2+ for all cardholder data transmission (Req 4)\n4. Implement key management procedures\n5. Deploy data discovery tools to locate unencrypted cardholder data\n\n### Phase 4: Access Controls (Weeks 21-28)\n1. Implement RBAC based on business need to know (Req 7)\n2. Deploy MFA for all access to CDE (Req 8)\n3. Implement unique user IDs for all users\n4. Enforce password policies meeting PCI DSS 4.0 requirements\n5. Implement physical access controls for CDE facilities (Req 9)\n\n### Phase 5: Monitoring and Testing (Weeks 29-36)\n1. Deploy centralized logging for all CDE components (Req 10)\n2. Implement automated log review mechanisms\n3. Conduct internal and external vulnerability scans (Req 11)\n4. Perform penetration testing (internal and external)\n5. Implement file integrity monitoring (FIM) for critical files\n\n### Phase 6: Policy and Governance (Weeks 37-42)\n1. Develop comprehensive information security policy (Req 12)\n2. Implement security awareness training including anti-phishing\n3. Establish incident response plan specific to cardholder data\n4. Conduct targeted risk analyses for flexible requirements\n5. Document and validate all controls for assessment\n\n## Key Artifacts\n- CDE Scope Documentation and Network Diagrams\n- Self-Assessment Questionnaire (SAQ) or Report on Compliance (ROC)\n- Attestation of Compliance (AOC)\n- Quarterly ASV Scan Reports\n- Annual Penetration Test Report\n- Risk Assessment Documentation\n- Security Policies and Procedures\n\n## Common Pitfalls\n- Scope creep due to inadequate network segmentation\n- Storing prohibited data (CVV, full track data) after authorization\n- Missing the March 2025 deadline for new mandatory requirements\n- Treating PCI DSS as annual compliance rather than continuous security\n- Not including cloud and container environments in CDE scope\n\n## References\n- PCI DSS v4.0.1: https:\u002F\u002Fwww.pcisecuritystandards.org\u002Fdocument_library\u002F\n- PCI SSC Quick Reference Guide\n- PCI DSS 4.0 Summary of Changes\n- UpGuard PCI DSS 4.0 Guide: https:\u002F\u002Fwww.upguard.com\u002Fblog\u002Fpci-compliance\n",{"name":5,"tags":55,"author":56,"domain":38,"license":15,"version":57,"nist_csf":58,"subdomain":64,"description":7,"mitre_attack":65},[35,39,47,48,49],"mahipal","1.0",[59,60,61,62,63],"GV.PO-01","PR.DS-01","PR.AA-01","DE.CM-01","ID.RA-01","compliance-governance",[66,67,68],"T1078","T1530","T1685.002","main","54a798831d2266a3ca61ce68a7acb80b81160d57","skills\u002Fimplementing-pci-dss-compliance-controls",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":80,"prompt":90,"zipAvailable":91},[81,84,87],{"tool":82,"command":83},"npx","npx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill implementing-pci-dss-compliance-controls",{"tool":85,"command":86},"bunx","bunx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill implementing-pci-dss-compliance-controls",{"tool":88,"command":89},"pnpm","pnpm dlx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill implementing-pci-dss-compliance-controls","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-pci-dss-compliance-controls\u002FSKILL.md",true,[93,99,104,110,114,118],{"path":94,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":97,"sourceHtmlUrl":98},"assets\u002Ftemplate.md","ASSET","资产文件",4286,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-pci-dss-compliance-controls\u002Fassets\u002Ftemplate.md",{"path":100,"resourceType":100,"resourceTypeDesc":101,"sizeBytes":102,"sourceHtmlUrl":103},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-pci-dss-compliance-controls\u002FLICENSE",{"path":105,"resourceType":106,"resourceTypeDesc":107,"sizeBytes":108,"sourceHtmlUrl":109},"references\u002Fapi-reference.md","REFERENCE","参考文档",6459,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-pci-dss-compliance-controls\u002Freferences\u002Fapi-reference.md",{"path":111,"resourceType":106,"resourceTypeDesc":107,"sizeBytes":112,"sourceHtmlUrl":113},"references\u002Fstandards.md",1087,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-pci-dss-compliance-controls\u002Freferences\u002Fstandards.md",{"path":115,"resourceType":106,"resourceTypeDesc":107,"sizeBytes":116,"sourceHtmlUrl":117},"references\u002Fworkflows.md",1643,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-pci-dss-compliance-controls\u002Freferences\u002Fworkflows.md",{"path":119,"resourceType":120,"resourceTypeDesc":121,"sizeBytes":122,"sourceHtmlUrl":123},"scripts\u002Fagent.py","SCRIPT","脚本",12331,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-pci-dss-compliance-controls\u002Fscripts\u002Fagent.py",[125,150,174,197,222,249],{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":132,"publishedAt":50},"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",[131],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[133,134,135,136,37,38,137,138,40,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":50},"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":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[158,146,159,160,37,161,38,40,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":50},"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":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[168,183,184,185,186,38,187,43,162,35,188,189,190,191,192,46,193,194,195,196],"backup","recovery","validating backup integrity for recovery","testing","infrastructure","hash-verification","incident-response","ransomware","cryptocurrency","detection","t1490","immutable","disaster-recovery","restore-testing",{"skillNo":198,"name":199,"nameZh":6,"description":200,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":201,"categories":202,"keywords":204,"publishedAt":50},"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",[203],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[205,206,207,38,208,209,210,211,212,213,214,45,215,216,217,218,165,219,220,221],"windows","kape","triaging windows with kape","registry","browser","logs","windows-forensics","dfir","mft","mftecmd","prefetch","eric-zimmerman","digital-forensics","SET","collection","pecmd","artifact-collection",{"skillNo":223,"name":224,"nameZh":6,"description":225,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":226,"categories":227,"keywords":229,"publishedAt":50},"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",[228],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[230,231,232,38,233,234,235,236,237,238,239,240,241,242,243,244,245,246,247,248],"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":250,"name":251,"nameZh":6,"description":252,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":253,"categories":254,"keywords":256,"publishedAt":50},"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",[255],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[37,257,38,258,259,260,261,262,263,264,265,46,266,193,267,268,269,270,271,272],"triaging security incident","siem","file","ioc","soc","NIST-800-61","NIST","severity","edr","execution","analysis","classification","severity-classification","incident-triage","SANS-PICERL","SOC-operations"]