[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AF596EKKGDMTW578WB4CGD":3,"skill-same:01M6AF596EKKGDMTW578WB4CGD":140},{"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":31,"publishedAt":48,"linkOnly":49,"markdownContent":50,"markdownBody":51,"frontMatter":52,"refName":77,"commitSha":78,"skillDirectory":79,"forksCount":80,"repositoryHtmlUrl":81,"repositoryHomepageUrl":82,"ownerHtmlUrl":83,"ownerBlogUrl":84,"ownerDescription":85,"updatedAt":86,"install":87,"resources":100},"01M6AF596EKKGDMTW578WB4CGD","implementing-gdpr-data-protection-controls",null,"Implements GDPR (EU 2016\u002F679) technical and organizational measures — privacy by design\u002Fdefault, DPIAs, data subject rights management, 72-hour breach notification, and cross-border transfer mechanisms (SCCs, BCRs, adequacy). Use when designing or auditing GDPR controls, building a DPIA, handling data subject access\u002Ferasure requests, or assessing cross-border data transfers.","mukul975\u002FAnthropic-Cybersecurity-Skills","mukul975","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F42860185?v=4","01M6ADEQR8T5M4EEG6C67BQCWF","Mahipal","01M6ADJPMYWG1E5GM1FWBE3128",35884,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-gdpr-data-protection-controls\u002FSKILL.md",[18,23,28],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",{"categoryNo":29,"categoryName":30,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000037","律师与法务",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47],"data protection","gdpr","data","implementing gdpr data protection controls","design","cybersecurity","governance","pr","privacy by design","transfer","compliance","privacy","data-protection","dpia","eu-regulation","t1078","2026-11-10 10:12:30",false,"---\nname: implementing-gdpr-data-protection-controls\ndescription: Implements GDPR (EU 2016\u002F679) technical and organizational measures — privacy by design\u002Fdefault, DPIAs, data subject rights management, 72-hour breach notification, and cross-border transfer mechanisms (SCCs, BCRs, adequacy). Use when designing or auditing GDPR controls, building a DPIA, handling data subject access\u002Ferasure requests, or assessing cross-border data transfers.\ndomain: cybersecurity\nsubdomain: compliance-governance\ntags:\n- compliance\n- governance\n- gdpr\n- privacy\n- data-protection\n- eu-regulation\nnist_csf:\n- GV.OC-02\n- GV.PO-01\n- PR.DS-01\n- PR.AA-01\n- ID.AM-02\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_ai_rmf:\n- MEASURE-2.7\n- MAP-5.1\n- MANAGE-2.4\n- MEASURE-2.8\n- MEASURE-2.9\natlas_techniques:\n- AML.T0070\n- AML.T0066\n- AML.T0082\nmitre_attack:\n- T1078\n- T1530\n- T1685.002\n---\n# Implementing GDPR Data Protection Controls\n\n## Overview\nThe General Data Protection Regulation (EU) 2016\u002F679 (GDPR) is the EU's comprehensive data protection law governing the collection, processing, storage, and transfer of personal data. This skill covers implementing the technical and organizational measures required by GDPR, including data protection by design and by default, Data Protection Impact Assessments (DPIAs), data subject rights management, breach notification procedures, and cross-border data transfer mechanisms.\n\n\n## When to Use\n\n- When deploying or configuring implementing gdpr data protection 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 EU data protection law and its territorial scope\n- Knowledge of personal data processing activities within the organization\n- Familiarity with data architecture, databases, and application systems\n- Understanding of data flows including cross-border transfers\n\n## Core Concepts\n\n### Key GDPR Articles for Technical Controls\n\n| Article | Requirement |\n|---------|-------------|\n| Art. 5 | Principles: lawfulness, purpose limitation, data minimization, accuracy, storage limitation, integrity and confidentiality, accountability |\n| Art. 6 | Lawful basis for processing (consent, contract, legal obligation, vital interests, public task, legitimate interest) |\n| Art. 25 | Data protection by design and by default |\n| Art. 28 | Processor obligations and contractual requirements |\n| Art. 30 | Records of processing activities (ROPA) |\n| Art. 32 | Security of processing (technical and organizational measures) |\n| Art. 33 | Breach notification to supervisory authority (72 hours) |\n| Art. 34 | Communication of breach to data subjects |\n| Art. 35 | Data Protection Impact Assessment (DPIA) |\n| Art. 37-39 | Data Protection Officer (DPO) appointment and role |\n| Art. 44-49 | Cross-border data transfers (adequacy, SCCs, BCRs) |\n\n### Article 32 Security Measures\nThe regulation requires organizations to implement measures appropriate to the risk:\n- **Pseudonymization** and encryption of personal data\n- **Confidentiality, integrity, availability, and resilience** of processing systems\n- **Ability to restore** availability and access to personal data in a timely manner\n- **Regular testing** and evaluation of technical and organizational measures\n\n### Data Subject Rights (Articles 12-22)\n| Right | Article | Description |\n|-------|---------|-------------|\n| Right to be informed | 13-14 | Transparent information about processing |\n| Right of access | 15 | Obtain copy of personal data |\n| Right to rectification | 16 | Correct inaccurate data |\n| Right to erasure | 17 | \"Right to be forgotten\" |\n| Right to restrict processing | 18 | Limit processing of data |\n| Right to data portability | 20 | Receive data in machine-readable format |\n| Right to object | 21 | Object to processing (especially direct marketing) |\n| Automated decision-making | 22 | Not be subject to solely automated decisions |\n\n## Workflow\n\n### Phase 1: Data Mapping and Assessment (Weeks 1-6)\n1. Create comprehensive data inventory:\n   - What personal data is collected\n   - From whom (data subjects)\n   - Why (purposes and lawful bases)\n   - Where it's stored (systems, locations, countries)\n   - Who has access (internal and external)\n   - How long it's retained\n   - What security measures protect it\n2. Document Records of Processing Activities (ROPA) per Article 30\n3. Identify lawful basis for each processing activity\n4. Map cross-border data transfers and transfer mechanisms\n5. Identify processing activities requiring DPIA\n\n### Phase 2: Gap Analysis and Risk Assessment (Weeks 7-10)\n1. Assess current state against GDPR requirements\n2. Perform DPIAs for high-risk processing activities\n3. Identify security gaps in Article 32 compliance\n4. Evaluate data retention compliance\n5. Assess data subject rights request handling capabilities\n\n### Phase 3: Technical Controls Implementation (Weeks 11-24)\n1. **Encryption**:\n   - Data at rest: AES-256 for databases, file systems, backups\n   - Data in transit: TLS 1.2+ for all personal data transfers\n   - Key management: secure key storage and rotation procedures\n2. **Pseudonymization**:\n   - Implement tokenization for sensitive identifiers\n   - Separate pseudonymization keys from data stores\n3. **Access Controls**:\n   - Role-based access control (RBAC) for personal data\n   - Principle of least privilege\n   - MFA for systems processing personal data\n   - Regular access reviews\n4. **Data Minimization**:\n   - Implement data collection limits at application layer\n   - Default privacy settings (data protection by default)\n   - Automated data retention enforcement\n5. **Erasure and Portability**:\n   - Build data deletion workflows across all systems\n   - Implement data export in machine-readable formats (JSON, CSV)\n   - Cascade deletion to backups and archives\n6. **Consent Management**:\n   - Implement granular consent collection mechanisms\n   - Consent withdrawal functionality\n   - Consent audit trail and versioning\n7. **Breach Detection**:\n   - SIEM for personal data access monitoring\n   - Data loss prevention (DLP) controls\n   - Anomalous access detection\n\n### Phase 4: Organizational Controls (Weeks 11-24)\n1. Appoint Data Protection Officer (DPO) if required\n2. Develop data protection policies and procedures\n3. Create breach notification procedures (72-hour timeline)\n4. Establish data subject request (DSR) handling procedures\n5. Implement vendor management with Data Processing Agreements (DPAs)\n6. Deploy privacy awareness training for all staff\n7. Create data protection by design guidance for development teams\n\n### Phase 5: Documentation and Compliance Evidence (Weeks 25-30)\n1. Finalize ROPA documentation\n2. Document all DPIAs and outcomes\n3. Create data protection policies\n4. Document technical and organizational measures\n5. Establish privacy notice and consent records\n6. Create international transfer documentation (SCCs, TIAs)\n\n### Phase 6: Ongoing Compliance (Continuous)\n1. Regular DPIA reviews for new processing activities\n2. Annual data mapping refresh\n3. Periodic security measure testing (Art. 32 requirement)\n4. Data subject request tracking and SLA monitoring\n5. Breach response readiness testing\n6. Training refresh and awareness campaigns\n\n## Key Artifacts\n- Records of Processing Activities (ROPA)\n- Data Protection Impact Assessments (DPIAs)\n- Data Processing Agreements (DPAs)\n- Privacy Notices and Consent Records\n- Breach Response Procedures and Register\n- Data Subject Request Handling Procedures\n- International Data Transfer Mechanisms (SCCs, BCRs)\n- Technical and Organizational Measures Documentation\n\n## Common Pitfalls\n- Treating GDPR as only a legal\u002Fcompliance exercise without technical implementation\n- Incomplete data mapping missing shadow IT or legacy systems\n- Failing to maintain consent audit trails\n- Not testing 72-hour breach notification capability\n- Ignoring cross-border transfer requirements for cloud services\n- Over-reliance on consent as lawful basis when legitimate interest applies\n\n## References\n- GDPR Official Text: https:\u002F\u002Fgdpr-info.eu\u002F\n- European Data Protection Board (EDPB) Guidelines\n- ICO (UK) GDPR Guidance: https:\u002F\u002Fico.org.uk\u002Ffor-organisations\u002Fguide-to-data-protection\u002Fguide-to-the-general-data-protection-regulation-gdpr\u002F\n- CNIL (France) GDPR Compliance Toolkit\n- Article 29 Working Party Guidelines on DPIAs\n","# Implementing GDPR Data Protection Controls\n\n## Overview\nThe General Data Protection Regulation (EU) 2016\u002F679 (GDPR) is the EU's comprehensive data protection law governing the collection, processing, storage, and transfer of personal data. This skill covers implementing the technical and organizational measures required by GDPR, including data protection by design and by default, Data Protection Impact Assessments (DPIAs), data subject rights management, breach notification procedures, and cross-border data transfer mechanisms.\n\n\n## When to Use\n\n- When deploying or configuring implementing gdpr data protection 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 EU data protection law and its territorial scope\n- Knowledge of personal data processing activities within the organization\n- Familiarity with data architecture, databases, and application systems\n- Understanding of data flows including cross-border transfers\n\n## Core Concepts\n\n### Key GDPR Articles for Technical Controls\n\n| Article | Requirement |\n|---------|-------------|\n| Art. 5 | Principles: lawfulness, purpose limitation, data minimization, accuracy, storage limitation, integrity and confidentiality, accountability |\n| Art. 6 | Lawful basis for processing (consent, contract, legal obligation, vital interests, public task, legitimate interest) |\n| Art. 25 | Data protection by design and by default |\n| Art. 28 | Processor obligations and contractual requirements |\n| Art. 30 | Records of processing activities (ROPA) |\n| Art. 32 | Security of processing (technical and organizational measures) |\n| Art. 33 | Breach notification to supervisory authority (72 hours) |\n| Art. 34 | Communication of breach to data subjects |\n| Art. 35 | Data Protection Impact Assessment (DPIA) |\n| Art. 37-39 | Data Protection Officer (DPO) appointment and role |\n| Art. 44-49 | Cross-border data transfers (adequacy, SCCs, BCRs) |\n\n### Article 32 Security Measures\nThe regulation requires organizations to implement measures appropriate to the risk:\n- **Pseudonymization** and encryption of personal data\n- **Confidentiality, integrity, availability, and resilience** of processing systems\n- **Ability to restore** availability and access to personal data in a timely manner\n- **Regular testing** and evaluation of technical and organizational measures\n\n### Data Subject Rights (Articles 12-22)\n| Right | Article | Description |\n|-------|---------|-------------|\n| Right to be informed | 13-14 | Transparent information about processing |\n| Right of access | 15 | Obtain copy of personal data |\n| Right to rectification | 16 | Correct inaccurate data |\n| Right to erasure | 17 | \"Right to be forgotten\" |\n| Right to restrict processing | 18 | Limit processing of data |\n| Right to data portability | 20 | Receive data in machine-readable format |\n| Right to object | 21 | Object to processing (especially direct marketing) |\n| Automated decision-making | 22 | Not be subject to solely automated decisions |\n\n## Workflow\n\n### Phase 1: Data Mapping and Assessment (Weeks 1-6)\n1. Create comprehensive data inventory:\n   - What personal data is collected\n   - From whom (data subjects)\n   - Why (purposes and lawful bases)\n   - Where it's stored (systems, locations, countries)\n   - Who has access (internal and external)\n   - How long it's retained\n   - What security measures protect it\n2. Document Records of Processing Activities (ROPA) per Article 30\n3. Identify lawful basis for each processing activity\n4. Map cross-border data transfers and transfer mechanisms\n5. Identify processing activities requiring DPIA\n\n### Phase 2: Gap Analysis and Risk Assessment (Weeks 7-10)\n1. Assess current state against GDPR requirements\n2. Perform DPIAs for high-risk processing activities\n3. Identify security gaps in Article 32 compliance\n4. Evaluate data retention compliance\n5. Assess data subject rights request handling capabilities\n\n### Phase 3: Technical Controls Implementation (Weeks 11-24)\n1. **Encryption**:\n   - Data at rest: AES-256 for databases, file systems, backups\n   - Data in transit: TLS 1.2+ for all personal data transfers\n   - Key management: secure key storage and rotation procedures\n2. **Pseudonymization**:\n   - Implement tokenization for sensitive identifiers\n   - Separate pseudonymization keys from data stores\n3. **Access Controls**:\n   - Role-based access control (RBAC) for personal data\n   - Principle of least privilege\n   - MFA for systems processing personal data\n   - Regular access reviews\n4. **Data Minimization**:\n   - Implement data collection limits at application layer\n   - Default privacy settings (data protection by default)\n   - Automated data retention enforcement\n5. **Erasure and Portability**:\n   - Build data deletion workflows across all systems\n   - Implement data export in machine-readable formats (JSON, CSV)\n   - Cascade deletion to backups and archives\n6. **Consent Management**:\n   - Implement granular consent collection mechanisms\n   - Consent withdrawal functionality\n   - Consent audit trail and versioning\n7. **Breach Detection**:\n   - SIEM for personal data access monitoring\n   - Data loss prevention (DLP) controls\n   - Anomalous access detection\n\n### Phase 4: Organizational Controls (Weeks 11-24)\n1. Appoint Data Protection Officer (DPO) if required\n2. Develop data protection policies and procedures\n3. Create breach notification procedures (72-hour timeline)\n4. Establish data subject request (DSR) handling procedures\n5. Implement vendor management with Data Processing Agreements (DPAs)\n6. Deploy privacy awareness training for all staff\n7. Create data protection by design guidance for development teams\n\n### Phase 5: Documentation and Compliance Evidence (Weeks 25-30)\n1. Finalize ROPA documentation\n2. Document all DPIAs and outcomes\n3. Create data protection policies\n4. Document technical and organizational measures\n5. Establish privacy notice and consent records\n6. Create international transfer documentation (SCCs, TIAs)\n\n### Phase 6: Ongoing Compliance (Continuous)\n1. Regular DPIA reviews for new processing activities\n2. Annual data mapping refresh\n3. Periodic security measure testing (Art. 32 requirement)\n4. Data subject request tracking and SLA monitoring\n5. Breach response readiness testing\n6. Training refresh and awareness campaigns\n\n## Key Artifacts\n- Records of Processing Activities (ROPA)\n- Data Protection Impact Assessments (DPIAs)\n- Data Processing Agreements (DPAs)\n- Privacy Notices and Consent Records\n- Breach Response Procedures and Register\n- Data Subject Request Handling Procedures\n- International Data Transfer Mechanisms (SCCs, BCRs)\n- Technical and Organizational Measures Documentation\n\n## Common Pitfalls\n- Treating GDPR as only a legal\u002Fcompliance exercise without technical implementation\n- Incomplete data mapping missing shadow IT or legacy systems\n- Failing to maintain consent audit trails\n- Not testing 72-hour breach notification capability\n- Ignoring cross-border transfer requirements for cloud services\n- Over-reliance on consent as lawful basis when legitimate interest applies\n\n## References\n- GDPR Official Text: https:\u002F\u002Fgdpr-info.eu\u002F\n- European Data Protection Board (EDPB) Guidelines\n- ICO (UK) GDPR Guidance: https:\u002F\u002Fico.org.uk\u002Ffor-organisations\u002Fguide-to-data-protection\u002Fguide-to-the-general-data-protection-regulation-gdpr\u002F\n- CNIL (France) GDPR Compliance Toolkit\n- Article 29 Working Party Guidelines on DPIAs\n",{"name":5,"tags":53,"author":54,"domain":37,"license":15,"version":55,"nist_csf":56,"subdomain":62,"description":7,"nist_ai_rmf":63,"mitre_attack":69,"atlas_techniques":73},[42,38,33,43,44,46],"mahipal","1.0",[57,58,59,60,61],"GV.OC-02","GV.PO-01","PR.DS-01","PR.AA-01","ID.AM-02","compliance-governance",[64,65,66,67,68],"MEASURE-2.7","MAP-5.1","MANAGE-2.4","MEASURE-2.8","MEASURE-2.9",[70,71,72],"T1078","T1530","T1685.002",[74,75,76],"AML.T0070","AML.T0066","AML.T0082","main","54a798831d2266a3ca61ce68a7acb80b81160d57","skills\u002Fimplementing-gdpr-data-protection-controls",4379,"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":88,"prompt":98,"zipAvailable":99},[89,92,95],{"tool":90,"command":91},"npx","npx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill implementing-gdpr-data-protection-controls",{"tool":93,"command":94},"bunx","bunx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill implementing-gdpr-data-protection-controls",{"tool":96,"command":97},"pnpm","pnpm dlx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill implementing-gdpr-data-protection-controls","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-gdpr-data-protection-controls\u002FSKILL.md",true,[101,107,113,118,122,126,130,136],{"path":102,"resourceType":103,"resourceTypeDesc":104,"sizeBytes":105,"sourceHtmlUrl":106},"agents\u002Fopenai.yaml","REFERENCE","参考文档",113,"https:\u002F\u002Fgithub.com\u002Ffderuiter\u002FQRCraftly-web\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgrilling\u002Fagents\u002Fopenai.yaml",{"path":108,"resourceType":109,"resourceTypeDesc":110,"sizeBytes":111,"sourceHtmlUrl":112},"assets\u002Ftemplate.md","ASSET","资产文件",6211,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-gdpr-data-protection-controls\u002Fassets\u002Ftemplate.md",{"path":114,"resourceType":114,"resourceTypeDesc":115,"sizeBytes":116,"sourceHtmlUrl":117},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-gdpr-data-protection-controls\u002FLICENSE",{"path":119,"resourceType":103,"resourceTypeDesc":104,"sizeBytes":120,"sourceHtmlUrl":121},"references\u002Fapi-reference.md",2171,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-gdpr-data-protection-controls\u002Freferences\u002Fapi-reference.md",{"path":123,"resourceType":103,"resourceTypeDesc":104,"sizeBytes":124,"sourceHtmlUrl":125},"references\u002Fstandards.md",5488,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-gdpr-data-protection-controls\u002Freferences\u002Fstandards.md",{"path":127,"resourceType":103,"resourceTypeDesc":104,"sizeBytes":128,"sourceHtmlUrl":129},"references\u002Fworkflows.md",7130,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-gdpr-data-protection-controls\u002Freferences\u002Fworkflows.md",{"path":131,"resourceType":132,"resourceTypeDesc":133,"sizeBytes":134,"sourceHtmlUrl":135},"scripts\u002Fagent.py","SCRIPT","脚本",9355,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-gdpr-data-protection-controls\u002Fscripts\u002Fagent.py",{"path":137,"resourceType":132,"resourceTypeDesc":133,"sizeBytes":138,"sourceHtmlUrl":139},"scripts\u002Fprocess.py",22121,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-gdpr-data-protection-controls\u002Fscripts\u002Fprocess.py",[141,167,191,217,242,269],{"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":148,"publishedAt":48},"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",[147],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[149,150,151,152,153,37,154,155,39,156,157,158,159,160,161,162,163,164,165,166],"sigstore","provenance","slsa","verifying build provenance with slsa sigstore","security","incident response","identity","code","artifacts","ci","supply-chain","pipeline","supply-chain-security","t1195","attestation","code-signing","cosign","keyless",{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":171,"categories":172,"keywords":174,"publishedAt":48},"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",[173],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[175,163,176,177,153,178,37,39,179,180,181,182,183,184,185,186,187,188,189,190],"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":192,"name":193,"nameZh":6,"description":194,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":195,"categories":196,"keywords":201,"publishedAt":48},"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",[197,200],{"categoryNo":198,"categoryName":199,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[185,202,203,204,205,37,206,207,179,42,208,209,210,211,212,47,213,214,215,216],"backup","recovery","validating backup integrity for recovery","testing","infrastructure","validation","hash-verification","incident-response","ransomware","cryptocurrency","detection","t1490","immutable","disaster-recovery","restore-testing",{"skillNo":218,"name":219,"nameZh":6,"description":220,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":221,"categories":222,"keywords":224,"publishedAt":48},"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",[223],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[225,226,227,37,228,229,230,231,232,233,234,34,235,236,237,238,182,239,240,241],"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":243,"name":244,"nameZh":6,"description":245,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":246,"categories":247,"keywords":249,"publishedAt":48},"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",[248],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[250,251,252,37,253,254,255,256,257,258,259,260,261,262,263,264,265,266,267,268],"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":270,"name":271,"nameZh":6,"description":272,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":273,"categories":274,"keywords":276,"publishedAt":48},"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",[275],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[153,277,37,278,279,280,281,282,283,284,285,47,286,213,287,288,289,290,291,292],"triaging security incident","siem","file","ioc","soc","NIST-800-61","NIST","severity","edr","execution","analysis","classification","severity-classification","incident-triage","SANS-PICERL","SOC-operations"]