[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AGDCW0Y4FXZ3362GT1941M":3,"skill-same:01M6AGDCW0Y4FXZ3362GT1941M":131},{"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":26,"publishedAt":47,"linkOnly":48,"markdownContent":49,"markdownBody":50,"frontMatter":51,"refName":86,"commitSha":87,"skillDirectory":88,"forksCount":89,"repositoryHtmlUrl":90,"repositoryHomepageUrl":91,"ownerHtmlUrl":92,"ownerBlogUrl":93,"ownerDescription":94,"updatedAt":95,"install":96,"resources":109},"01M6AGDCW0Y4FXZ3362GT1941M","validating-backup-integrity-for-recovery",null,"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.","mukul975\u002FAnthropic-Cybersecurity-Skills","mukul975","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F42860185?v=4","01M6ADEQR8T5M4EEG6C67BQCWF","Mahipal","01M6ADJPMYWG1E5GM1FWBE3128",35925,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fvalidating-backup-integrity-for-recovery\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46],"validating backup integrity for recovery","recovery","backup","integrity","detection","restore-testing","disaster-recovery","immutable","t1490","t1078","testing","cryptocurrency","ransomware","incident-response","hash-verification","compliance","verification","validation","infrastructure","cybersecurity","2026-11-10 10:12:30",false,"---\nname: validating-backup-integrity-for-recovery\ndescription: Validates backup integrity through cryptographic hash verification,\n  automated restore testing, corruption detection, and recoverability checks to\n  confirm backups are reliable for disaster recovery and ransomware response. Use\n  before relying on backups for recovery, when building post-backup validation\n  pipelines, auditing backup infrastructure for compliance, or checking immutable\u002Fair-gapped\n  backups for silent corruption or tampering.\ndomain: cybersecurity\nsubdomain: incident-response\ntags:\n- incident-response\n- backup\n- integrity\n- hash-verification\n- restore-testing\n- disaster-recovery\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- RS.MA-01\n- RS.MA-02\n- RS.AN-03\n- RC.RP-01\nmitre_attack:\n- T1486\n- T1490\n- T1070\n- T1078\n- T1489\nmitre_f3:\n  version: '1.1'\n  tactics:\n  - positioning\n  - monetization\n  techniques:\n  - id: T1531\n    name: Account Access Removal\n    tactic: positioning\n    source: attack\n  - id: F1018\n    name: Convert to Cryptocurrency\n    tactic: monetization\n    source: f3\n  - id: F1047\n    name: Transfer of funds\n    tactic: monetization\n    source: f3\n  - id: F1017.001\n    name: 'Conversion to Physical Monetary Instruments: Cash'\n    tactic: monetization\n    source: f3\n---\n# Validating Backup Integrity for Recovery\n\n## When to Use\n\nUse this skill when:\n- Verifying backup integrity before relying on backups for ransomware recovery\n- Building automated backup validation pipelines that run after each backup job\n- Auditing backup infrastructure to confirm recoverability for compliance (SOC 2, ISO 27001, NIST CSF RC.RP-03)\n- Detecting silent data corruption (bit rot) in backup storage before a disaster occurs\n- Validating that immutable or air-gapped backups have not been tampered with\n\n**Do not use** for initial backup configuration or scheduling. This skill focuses on post-backup validation.\n\n## Prerequisites\n\n- Access to backup storage (local, NAS, S3, Azure Blob, GCS)\n- Python 3.9+ with `hashlib` (standard library)\n- Backup manifests or baseline hash files for comparison\n- Isolated restore environment for restore testing\n- Backup tool CLI access (restic, borgbackup, rclone, or vendor-specific)\n\n## Workflow\n\n### Step 1: Generate Baseline Hash Manifest\n\nCreate a cryptographic fingerprint of every file at backup time:\n\n```bash\n# Generate SHA-256 manifest for a directory\nfind \u002Fdata\u002Fproduction -type f -exec sha256sum {} \\; > \u002Fmanifests\u002Fprod_baseline_$(date +%Y%m%d).sha256\n\n# Verify manifest format\nhead -5 \u002Fmanifests\u002Fprod_baseline_20260319.sha256\n# e3b0c44298fc1c149afbf4c8996fb924...  \u002Fdata\u002Fproduction\u002Fconfig.yaml\n# a7ffc6f8bf1ed76651c14756a061d662...  \u002Fdata\u002Fproduction\u002Fdatabase.sql\n```\n\n### Step 2: Verify Backup Archive Integrity\n\nCheck that the backup archive itself is not corrupted:\n\n```bash\n# Restic: verify backup repository integrity\nrestic -r s3:s3.amazonaws.com\u002Fbackup-bucket check --read-data\n\n# Borg: verify backup archive\nborg check --verify-data \u002Fbackup\u002Frepo::archive-2026-03-19\n\n# Tar with gzip: verify archive integrity\ngzip -t backup_20260319.tar.gz && echo \"Archive OK\" || echo \"Archive CORRUPTED\"\n\n# AWS S3: verify object checksums\naws s3api head-object --bucket backup-bucket --key daily\u002F2026-03-19.tar.gz \\\n  --checksum-mode ENABLED\n```\n\n### Step 3: Perform Restore Test to Isolated Environment\n\n```bash\n# Restore to isolated test directory\nrestic -r s3:s3.amazonaws.com\u002Fbackup-bucket restore latest --target \u002Frestore-test\u002F\n\n# Generate hash manifest of restored data\nfind \u002Frestore-test -type f -exec sha256sum {} \\; > \u002Fmanifests\u002Frestored_$(date +%Y%m%d).sha256\n\n# Compare baseline and restored manifests\ndiff \u003C(sort \u002Fmanifests\u002Fprod_baseline_20260319.sha256) \\\n     \u003C(sort \u002Fmanifests\u002Frestored_20260319.sha256)\n```\n\n### Step 4: Validate Data Completeness\n\n```bash\n# Count files in original vs restored\necho \"Original: $(find \u002Fdata\u002Fproduction -type f | wc -l) files\"\necho \"Restored: $(find \u002Frestore-test -type f | wc -l) files\"\n\n# Check total size\necho \"Original: $(du -sh \u002Fdata\u002Fproduction | cut -f1)\"\necho \"Restored: $(du -sh \u002Frestore-test | cut -f1)\"\n\n# Database consistency check after restore\npg_restore --list backup.dump | wc -l  # Count objects in dump\npsql -c \"SELECT schemaname, tablename FROM pg_tables WHERE schemaname='public';\" restored_db\n```\n\n### Step 5: Detect Ransomware Artifacts in Backups\n\nBefore trusting a backup for recovery, scan for ransomware indicators:\n\n```bash\n# Check for common ransomware file extensions\nfind \u002Frestore-test -type f \\( \\\n  -name \"*.encrypted\" -o -name \"*.locked\" -o -name \"*.crypt\" \\\n  -o -name \"*.ransom\" -o -name \"*.pay\" -o -name \"*.wncry\" \\\n  -o -name \"*.cerber\" -o -name \"*.locky\" -o -name \"*.zepto\" \\\n\\) -print\n\n# Check for ransom notes\nfind \u002Frestore-test -type f \\( \\\n  -name \"README_TO_DECRYPT*\" -o -name \"HOW_TO_RECOVER*\" \\\n  -o -name \"DECRYPT_INSTRUCTIONS*\" -o -name \"HELP_DECRYPT*\" \\\n\\) -print\n\n# Check file entropy (high entropy = possible encryption)\n# Files with entropy > 7.9 out of 8.0 are likely encrypted\npython agent.py --entropy-scan \u002Frestore-test\n```\n\n### Step 6: Automate and Schedule Validation\n\n```yaml\n# cron-based validation schedule\n# Run nightly after backup window\n0 4 * * * \u002Fopt\u002Fbackup-validator\u002Fagent.py --validate-latest --notify-on-failure\n# Weekly full restore test\n0 6 * * 0 \u002Fopt\u002Fbackup-validator\u002Fagent.py --full-restore-test --config \u002Fetc\u002Fbackup-validator\u002Fconfig.json\n```\n\n## Key Concepts\n\n| Term | Definition |\n|------|-----------|\n| **Hash Manifest** | File containing cryptographic hashes (SHA-256) for every file in a dataset, used as integrity baseline |\n| **Bit Rot** | Gradual data corruption on storage media that silently alters file contents |\n| **Immutable Backup** | Backup that cannot be modified or deleted for a defined retention period |\n| **Restore Test** | Process of recovering data from backup to an isolated environment to verify recoverability |\n| **File Entropy** | Measure of randomness in file contents; encrypted files have entropy near 8.0 bits\u002Fbyte |\n| **3-2-1 Rule** | Keep 3 copies of data, on 2 different media types, with 1 offsite copy |\n| **Backup Chain** | Sequence of full and incremental backups that must all be intact for recovery |\n\n## Tools & Systems\n\n| Tool | Purpose |\n|------|---------|\n| Restic | Encrypted, deduplicated backup with built-in integrity verification |\n| BorgBackup | Deduplicating backup with archive verification |\n| Rclone | Cloud storage sync with checksum verification |\n| AWS S3 Object Lock | Immutable backup storage with WORM compliance |\n| Azure Immutable Blob | Tamper-proof backup storage for compliance |\n| sha256sum | Standard hash computation for file integrity |\n| pg_restore | PostgreSQL backup validation and restore testing |\n\n## Common Pitfalls\n\n- **Never testing restores**: The most common failure mode. Backups that are never restored are untested assumptions.\n- **Checking only archive integrity, not data integrity**: A valid tar.gz can contain corrupted file contents. Always hash individual files.\n- **Trusting last backup without scanning for ransomware**: Backups may contain encrypted files if the infection predates the backup.\n- **Ignoring incremental chain integrity**: A single corrupted incremental backup can break the entire restore chain.\n- **No alerting on validation failures**: Backup validation must be monitored with alerts, not just logged silently.\n- **Using MD5 for integrity**: MD5 is cryptographically broken. Use SHA-256 or SHA-3 for integrity verification.\n\n## References\n\n- NIST SP 800-184: Guide for Cybersecurity Event Recovery\n- NIST CSF 2.0 RC.RP-03: Backup Integrity Verification\n- CIS Controls v8: Control 11 - Data Recovery\n- CISA Ransomware Guide: https:\u002F\u002Fwww.cisa.gov\u002Fstopransomware\n","# Validating Backup Integrity for Recovery\n\n## When to Use\n\nUse this skill when:\n- Verifying backup integrity before relying on backups for ransomware recovery\n- Building automated backup validation pipelines that run after each backup job\n- Auditing backup infrastructure to confirm recoverability for compliance (SOC 2, ISO 27001, NIST CSF RC.RP-03)\n- Detecting silent data corruption (bit rot) in backup storage before a disaster occurs\n- Validating that immutable or air-gapped backups have not been tampered with\n\n**Do not use** for initial backup configuration or scheduling. This skill focuses on post-backup validation.\n\n## Prerequisites\n\n- Access to backup storage (local, NAS, S3, Azure Blob, GCS)\n- Python 3.9+ with `hashlib` (standard library)\n- Backup manifests or baseline hash files for comparison\n- Isolated restore environment for restore testing\n- Backup tool CLI access (restic, borgbackup, rclone, or vendor-specific)\n\n## Workflow\n\n### Step 1: Generate Baseline Hash Manifest\n\nCreate a cryptographic fingerprint of every file at backup time:\n\n```bash\n# Generate SHA-256 manifest for a directory\nfind \u002Fdata\u002Fproduction -type f -exec sha256sum {} \\; > \u002Fmanifests\u002Fprod_baseline_$(date +%Y%m%d).sha256\n\n# Verify manifest format\nhead -5 \u002Fmanifests\u002Fprod_baseline_20260319.sha256\n# e3b0c44298fc1c149afbf4c8996fb924...  \u002Fdata\u002Fproduction\u002Fconfig.yaml\n# a7ffc6f8bf1ed76651c14756a061d662...  \u002Fdata\u002Fproduction\u002Fdatabase.sql\n```\n\n### Step 2: Verify Backup Archive Integrity\n\nCheck that the backup archive itself is not corrupted:\n\n```bash\n# Restic: verify backup repository integrity\nrestic -r s3:s3.amazonaws.com\u002Fbackup-bucket check --read-data\n\n# Borg: verify backup archive\nborg check --verify-data \u002Fbackup\u002Frepo::archive-2026-03-19\n\n# Tar with gzip: verify archive integrity\ngzip -t backup_20260319.tar.gz && echo \"Archive OK\" || echo \"Archive CORRUPTED\"\n\n# AWS S3: verify object checksums\naws s3api head-object --bucket backup-bucket --key daily\u002F2026-03-19.tar.gz \\\n  --checksum-mode ENABLED\n```\n\n### Step 3: Perform Restore Test to Isolated Environment\n\n```bash\n# Restore to isolated test directory\nrestic -r s3:s3.amazonaws.com\u002Fbackup-bucket restore latest --target \u002Frestore-test\u002F\n\n# Generate hash manifest of restored data\nfind \u002Frestore-test -type f -exec sha256sum {} \\; > \u002Fmanifests\u002Frestored_$(date +%Y%m%d).sha256\n\n# Compare baseline and restored manifests\ndiff \u003C(sort \u002Fmanifests\u002Fprod_baseline_20260319.sha256) \\\n     \u003C(sort \u002Fmanifests\u002Frestored_20260319.sha256)\n```\n\n### Step 4: Validate Data Completeness\n\n```bash\n# Count files in original vs restored\necho \"Original: $(find \u002Fdata\u002Fproduction -type f | wc -l) files\"\necho \"Restored: $(find \u002Frestore-test -type f | wc -l) files\"\n\n# Check total size\necho \"Original: $(du -sh \u002Fdata\u002Fproduction | cut -f1)\"\necho \"Restored: $(du -sh \u002Frestore-test | cut -f1)\"\n\n# Database consistency check after restore\npg_restore --list backup.dump | wc -l  # Count objects in dump\npsql -c \"SELECT schemaname, tablename FROM pg_tables WHERE schemaname='public';\" restored_db\n```\n\n### Step 5: Detect Ransomware Artifacts in Backups\n\nBefore trusting a backup for recovery, scan for ransomware indicators:\n\n```bash\n# Check for common ransomware file extensions\nfind \u002Frestore-test -type f \\( \\\n  -name \"*.encrypted\" -o -name \"*.locked\" -o -name \"*.crypt\" \\\n  -o -name \"*.ransom\" -o -name \"*.pay\" -o -name \"*.wncry\" \\\n  -o -name \"*.cerber\" -o -name \"*.locky\" -o -name \"*.zepto\" \\\n\\) -print\n\n# Check for ransom notes\nfind \u002Frestore-test -type f \\( \\\n  -name \"README_TO_DECRYPT*\" -o -name \"HOW_TO_RECOVER*\" \\\n  -o -name \"DECRYPT_INSTRUCTIONS*\" -o -name \"HELP_DECRYPT*\" \\\n\\) -print\n\n# Check file entropy (high entropy = possible encryption)\n# Files with entropy > 7.9 out of 8.0 are likely encrypted\npython agent.py --entropy-scan \u002Frestore-test\n```\n\n### Step 6: Automate and Schedule Validation\n\n```yaml\n# cron-based validation schedule\n# Run nightly after backup window\n0 4 * * * \u002Fopt\u002Fbackup-validator\u002Fagent.py --validate-latest --notify-on-failure\n# Weekly full restore test\n0 6 * * 0 \u002Fopt\u002Fbackup-validator\u002Fagent.py --full-restore-test --config \u002Fetc\u002Fbackup-validator\u002Fconfig.json\n```\n\n## Key Concepts\n\n| Term | Definition |\n|------|-----------|\n| **Hash Manifest** | File containing cryptographic hashes (SHA-256) for every file in a dataset, used as integrity baseline |\n| **Bit Rot** | Gradual data corruption on storage media that silently alters file contents |\n| **Immutable Backup** | Backup that cannot be modified or deleted for a defined retention period |\n| **Restore Test** | Process of recovering data from backup to an isolated environment to verify recoverability |\n| **File Entropy** | Measure of randomness in file contents; encrypted files have entropy near 8.0 bits\u002Fbyte |\n| **3-2-1 Rule** | Keep 3 copies of data, on 2 different media types, with 1 offsite copy |\n| **Backup Chain** | Sequence of full and incremental backups that must all be intact for recovery |\n\n## Tools & Systems\n\n| Tool | Purpose |\n|------|---------|\n| Restic | Encrypted, deduplicated backup with built-in integrity verification |\n| BorgBackup | Deduplicating backup with archive verification |\n| Rclone | Cloud storage sync with checksum verification |\n| AWS S3 Object Lock | Immutable backup storage with WORM compliance |\n| Azure Immutable Blob | Tamper-proof backup storage for compliance |\n| sha256sum | Standard hash computation for file integrity |\n| pg_restore | PostgreSQL backup validation and restore testing |\n\n## Common Pitfalls\n\n- **Never testing restores**: The most common failure mode. Backups that are never restored are untested assumptions.\n- **Checking only archive integrity, not data integrity**: A valid tar.gz can contain corrupted file contents. Always hash individual files.\n- **Trusting last backup without scanning for ransomware**: Backups may contain encrypted files if the infection predates the backup.\n- **Ignoring incremental chain integrity**: A single corrupted incremental backup can break the entire restore chain.\n- **No alerting on validation failures**: Backup validation must be monitored with alerts, not just logged silently.\n- **Using MD5 for integrity**: MD5 is cryptographically broken. Use SHA-256 or SHA-3 for integrity verification.\n\n## References\n\n- NIST SP 800-184: Guide for Cybersecurity Event Recovery\n- NIST CSF 2.0 RC.RP-03: Backup Integrity Verification\n- CIS Controls v8: Control 11 - Data Recovery\n- CISA Ransomware Guide: https:\u002F\u002Fwww.cisa.gov\u002Fstopransomware\n",{"name":5,"tags":52,"author":53,"domain":46,"license":15,"version":54,"mitre_f3":55,"nist_csf":75,"subdomain":40,"description":7,"mitre_attack":80},[40,29,30,41,32,33],"mahipal","1.0",{"tactics":56,"version":59,"techniques":60},[57,58],"positioning","monetization","1.1",[61,65,69,72],{"id":62,"name":63,"source":64,"tactic":57},"T1531","Account Access Removal","attack",{"id":66,"name":67,"source":68,"tactic":58},"F1018","Convert to Cryptocurrency","f3",{"id":70,"name":71,"source":68,"tactic":58},"F1047","Transfer of funds",{"id":73,"name":74,"source":68,"tactic":58},"F1017.001","Conversion to Physical Monetary Instruments: Cash",[76,77,78,79],"RS.MA-01","RS.MA-02","RS.AN-03","RC.RP-01",[81,82,83,84,85],"T1486","T1490","T1070","T1078","T1489","main","54a798831d2266a3ca61ce68a7acb80b81160d57","skills\u002Fvalidating-backup-integrity-for-recovery",4384,"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":97,"prompt":107,"zipAvailable":108},[98,101,104],{"tool":99,"command":100},"npx","npx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill validating-backup-integrity-for-recovery",{"tool":102,"command":103},"bunx","bunx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill validating-backup-integrity-for-recovery",{"tool":105,"command":106},"pnpm","pnpm dlx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill validating-backup-integrity-for-recovery","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fvalidating-backup-integrity-for-recovery\u002FSKILL.md",true,[110,115,121,125],{"path":111,"resourceType":111,"resourceTypeDesc":112,"sizeBytes":113,"sourceHtmlUrl":114},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fvalidating-backup-integrity-for-recovery\u002FLICENSE",{"path":116,"resourceType":117,"resourceTypeDesc":118,"sizeBytes":119,"sourceHtmlUrl":120},"references\u002Fapi-reference.md","REFERENCE","参考文档",4005,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fvalidating-backup-integrity-for-recovery\u002Freferences\u002Fapi-reference.md",{"path":122,"resourceType":117,"resourceTypeDesc":118,"sizeBytes":123,"sourceHtmlUrl":124},"references\u002Fcleanup.md",9193,"https:\u002F\u002Fgithub.com\u002FChachamaru127\u002Fclaude-code-harness\u002Fblob\u002Fmain\u002Fcodex\u002F.codex\u002Fskills\u002Fmaintenance\u002Freferences\u002Fcleanup.md",{"path":126,"resourceType":127,"resourceTypeDesc":128,"sizeBytes":129,"sourceHtmlUrl":130},"scripts\u002Fagent.py","SCRIPT","脚本",10734,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fvalidating-backup-integrity-for-recovery\u002Fscripts\u002Fagent.py",[132,159,181,207,234,258],{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":139,"publishedAt":47},"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",[138],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[140,141,142,143,144,46,145,146,147,148,149,150,151,152,153,154,155,156,157,158],"sigstore","provenance","slsa","verifying build provenance with slsa sigstore","security","incident response","identity","pr","code","artifacts","ci","supply-chain","pipeline","supply-chain-security","t1195","attestation","code-signing","cosign","keyless",{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":166,"publishedAt":47},"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",[165],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[167,155,168,169,144,170,46,147,43,171,172,173,174,175,30,176,177,178,179,180],"boot","TPM","validating tpm measured boot attestation","policy","ZeRO","firmware","Tools","measured-boot","PCR","secrets","remote-attestation","tpm2-tools","integrity-verification","trusted-computing",{"skillNo":182,"name":183,"nameZh":6,"description":184,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":185,"categories":186,"keywords":188,"publishedAt":47},"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",[187],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[189,190,191,46,192,193,194,195,196,197,198,199,200,201,202,203,173,204,205,206],"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":208,"name":209,"nameZh":6,"description":210,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":211,"categories":212,"keywords":214,"publishedAt":47},"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",[213],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[215,216,217,46,218,219,220,221,222,223,224,225,226,227,228,229,230,231,232,233],"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":235,"name":236,"nameZh":6,"description":237,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":238,"categories":239,"keywords":241,"publishedAt":47},"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",[240],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[144,242,46,243,244,245,246,247,248,249,250,36,251,35,252,253,254,255,256,257],"triaging security incident","siem","file","ioc","soc","NIST-800-61","NIST","severity","edr","execution","analysis","classification","severity-classification","incident-triage","SANS-PICERL","SOC-operations",{"skillNo":259,"name":260,"nameZh":6,"description":261,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":262,"categories":263,"keywords":265,"publishedAt":47},"01M6AGCYCY9QW562V4CDK3X2RY","triaging-security-incident-with-ir-playbook","Classifies and prioritizes security incidents using structured IR playbooks and SIEM\u002Fcase-management queries (Splunk, TheHive) to determine severity, assign response teams, and initiate the appropriate response procedures. Use when a new SOC alert needs triage, multiple concurrent incidents require prioritization, or automated triage rules need validation or tuning.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ftriaging-security-incident-with-ir-playbook\u002FSKILL.md",[264],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[144,266,267,46,243,268,269,44,246,270,40,249,36,35,271,272,253,231,254],"playbook","triaging security incident with ir playbook","triage","teams","splunk","tuning","thehive"]