[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AFJSK8GEAW5HTYNEFRZ5MN":3,"skill-same:01M6AFJSK8GEAW5HTYNEFRZ5MN":127},{"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":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":68,"commitSha":69,"skillDirectory":70,"forksCount":71,"repositoryHtmlUrl":72,"repositoryHomepageUrl":73,"ownerHtmlUrl":74,"ownerBlogUrl":75,"ownerDescription":76,"updatedAt":77,"install":78,"resources":91},"01M6AFJSK8GEAW5HTYNEFRZ5MN","performing-access-review-and-certification",null,"Designs and runs access review and certification campaigns-scoping, reviewer selection, risk-based prioritization, micro-certification, and remediation tracking-to verify user access matches job roles for SOX, HIPAA, and PCI DSS compliance. Use when planning or executing periodic access recertification or preparing evidence for an IAM compliance audit.","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\u002Fperforming-access-review-and-certification\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,45,46,47,48],"performing access review and certification","certification","review","access-control","access-review","risk-based","t1098","risk","t1078","remediation","iam","hipaa","compliance","micro","audit","planning","pr","governance","identity","cybersecurity","2026-11-10 10:12:30",false,"---\nname: performing-access-review-and-certification\ndescription: Designs and runs access review and certification campaigns-scoping,\n  reviewer selection, risk-based prioritization, micro-certification, and remediation\n  tracking-to verify user access matches job roles for SOX, HIPAA, and PCI DSS compliance.\n  Use when planning or executing periodic access recertification or preparing evidence\n  for an IAM compliance audit.\ndomain: cybersecurity\nsubdomain: identity-access-management\ntags:\n- iam\n- identity\n- access-control\n- access-review\n- certification\n- compliance\n- governance\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- PR.AA-01\n- PR.AA-02\n- PR.AA-05\n- PR.AA-06\nmitre_attack:\n- T1078\n- T1110\n- T1556\n- T1098\n---\n# Performing Access Review and Certification\n\n## Overview\nConduct systematic access reviews and certifications to ensure users have appropriate access rights aligned with their roles. This skill covers review campaign design, reviewer selection, risk-based prioritization, micro-certification strategies, and remediation tracking for compliance with SOX, HIPAA, and PCI DSS requirements.\n\n\n## When to Use\n\n- When conducting security assessments that involve performing access review and certification\n- When following incident response procedures for related security events\n- When performing scheduled security testing or auditing activities\n- When validating security controls through hands-on testing\n\n## Prerequisites\n\n- Familiarity with identity access management concepts and tools\n- Access to a test or lab environment for safe execution\n- Python 3.8+ with required dependencies installed\n- Appropriate authorization for any testing activities\n\n## Objectives\n- Design and execute access review campaigns across enterprise applications\n- Implement risk-based prioritization for review scope\n- Configure reviewer selection (manager, application owner, hybrid)\n- Automate entitlement data collection and presentation\n- Track remediation of inappropriate access findings\n- Generate compliance evidence for auditors\n\n## Key Concepts\n\n### Access Review Types\n1. **User Access Review**: Manager certifies all entitlements for their direct reports\n2. **Entitlement Review**: Application owner certifies all users with specific entitlement\n3. **Role Review**: Role owner certifies role membership and permissions\n4. **Privileged Access Review**: Security team reviews high-risk\u002Fprivileged access\n5. **SOD Review**: Verify no users have conflicting separation-of-duty violations\n\n### Risk-Based Prioritization\n- **High Risk**: Privileged access, financial systems, PII\u002FPHI systems, external-facing apps\n- **Medium Risk**: Internal business applications, shared drives, collaboration tools\n- **Low Risk**: Standard employee tools, read-only access, public information systems\n\n### Review Campaign Lifecycle\n1. **Planning**: Define scope, reviewers, timeline, escalation\n2. **Data Collection**: Aggregate entitlements from all identity sources\n3. **Distribution**: Assign review items to appropriate certifiers\n4. **Certification**: Reviewers approve or revoke each entitlement\n5. **Remediation**: Revoke inappropriate access, enforce timeline\n6. **Reporting**: Generate compliance evidence and metrics\n7. **Closure**: Archive campaign, feed findings into next cycle\n\n## Workflow\n\n### Step 1: Define Review Scope and Schedule\n- Identify in-scope applications and systems\n- Determine review frequency: quarterly (SOX), semi-annual, annual\n- Define campaign timeline: review period, escalation dates, hard close\n- Establish escalation chain for non-responsive reviewers\n\n### Step 2: Data Collection and Aggregation\n- Extract user-entitlement mappings from each application\n- Correlate with HR data (active employees, role, department, manager)\n- Identify terminated\u002Ftransferred users still holding access\n- Flag high-risk entitlements (admin, DBA, system, privileged)\n- Calculate risk scores based on entitlement sensitivity and user role\n\n### Step 3: Reviewer Assignment\n- **Manager Reviews**: Direct manager certifies subordinate access\n- **Application Owner Reviews**: App owner certifies all users of their application\n- **Hybrid Model**: Manager reviews standard access, app owner reviews privileged\n- **Delegate Management**: Allow reviewers to delegate with audit trail\n\n### Step 4: Execute Certification Campaign\n- Send notifications to reviewers with clear instructions\n- Present entitlements with context (last used date, risk level, role justification)\n- Require reviewers to explicitly approve or revoke each item\n- Track completion percentage and send reminders\n- Escalate to management after deadline\n\n### Step 5: Remediation and Tracking\n- Automatically ticket revocations to IT operations\n- Set SLA for revocation execution (24-48 hours for high-risk)\n- Verify revocation completed (re-check entitlement)\n- Exception management for business-justified deviations\n- Document all exceptions with expiration dates\n\n### Step 6: Reporting and Evidence\n- Generate campaign completion metrics\n- Produce per-application compliance reports\n- Create audit-ready evidence packages\n- Track trends across review cycles\n- Feed findings into risk assessment process\n\n## Security Controls\n| Control | NIST 800-53 | Description |\n|---------|-------------|-------------|\n| Access Review | AC-2(3) | Periodic review of account privileges |\n| Account Management | AC-2 | Account lifecycle management |\n| Least Privilege | AC-6 | Minimum necessary access enforcement |\n| Separation of Duties | AC-5 | SOD conflict identification |\n| Audit Logging | AU-6 | Review of access audit records |\n\n## Common Pitfalls\n- Rubber-stamping: reviewers approving all access without examination\n- Incomplete scope: missing critical applications from review campaigns\n- No remediation tracking: revoking access on paper but not in systems\n- Inconsistent reviewer assignment causing gaps in coverage\n- Not including service accounts and non-human identities\n\n## Verification\n- [ ] All in-scope applications included in campaign\n- [ ] Reviewers assigned for 100% of entitlements\n- [ ] Campaign completion rate exceeds 95%\n- [ ] Revocations executed within SLA\n- [ ] Audit evidence package complete and archived\n- [ ] SOD violations identified and documented\n- [ ] Exceptions documented with business justification and expiry\n","# Performing Access Review and Certification\n\n## Overview\nConduct systematic access reviews and certifications to ensure users have appropriate access rights aligned with their roles. This skill covers review campaign design, reviewer selection, risk-based prioritization, micro-certification strategies, and remediation tracking for compliance with SOX, HIPAA, and PCI DSS requirements.\n\n\n## When to Use\n\n- When conducting security assessments that involve performing access review and certification\n- When following incident response procedures for related security events\n- When performing scheduled security testing or auditing activities\n- When validating security controls through hands-on testing\n\n## Prerequisites\n\n- Familiarity with identity access management concepts and tools\n- Access to a test or lab environment for safe execution\n- Python 3.8+ with required dependencies installed\n- Appropriate authorization for any testing activities\n\n## Objectives\n- Design and execute access review campaigns across enterprise applications\n- Implement risk-based prioritization for review scope\n- Configure reviewer selection (manager, application owner, hybrid)\n- Automate entitlement data collection and presentation\n- Track remediation of inappropriate access findings\n- Generate compliance evidence for auditors\n\n## Key Concepts\n\n### Access Review Types\n1. **User Access Review**: Manager certifies all entitlements for their direct reports\n2. **Entitlement Review**: Application owner certifies all users with specific entitlement\n3. **Role Review**: Role owner certifies role membership and permissions\n4. **Privileged Access Review**: Security team reviews high-risk\u002Fprivileged access\n5. **SOD Review**: Verify no users have conflicting separation-of-duty violations\n\n### Risk-Based Prioritization\n- **High Risk**: Privileged access, financial systems, PII\u002FPHI systems, external-facing apps\n- **Medium Risk**: Internal business applications, shared drives, collaboration tools\n- **Low Risk**: Standard employee tools, read-only access, public information systems\n\n### Review Campaign Lifecycle\n1. **Planning**: Define scope, reviewers, timeline, escalation\n2. **Data Collection**: Aggregate entitlements from all identity sources\n3. **Distribution**: Assign review items to appropriate certifiers\n4. **Certification**: Reviewers approve or revoke each entitlement\n5. **Remediation**: Revoke inappropriate access, enforce timeline\n6. **Reporting**: Generate compliance evidence and metrics\n7. **Closure**: Archive campaign, feed findings into next cycle\n\n## Workflow\n\n### Step 1: Define Review Scope and Schedule\n- Identify in-scope applications and systems\n- Determine review frequency: quarterly (SOX), semi-annual, annual\n- Define campaign timeline: review period, escalation dates, hard close\n- Establish escalation chain for non-responsive reviewers\n\n### Step 2: Data Collection and Aggregation\n- Extract user-entitlement mappings from each application\n- Correlate with HR data (active employees, role, department, manager)\n- Identify terminated\u002Ftransferred users still holding access\n- Flag high-risk entitlements (admin, DBA, system, privileged)\n- Calculate risk scores based on entitlement sensitivity and user role\n\n### Step 3: Reviewer Assignment\n- **Manager Reviews**: Direct manager certifies subordinate access\n- **Application Owner Reviews**: App owner certifies all users of their application\n- **Hybrid Model**: Manager reviews standard access, app owner reviews privileged\n- **Delegate Management**: Allow reviewers to delegate with audit trail\n\n### Step 4: Execute Certification Campaign\n- Send notifications to reviewers with clear instructions\n- Present entitlements with context (last used date, risk level, role justification)\n- Require reviewers to explicitly approve or revoke each item\n- Track completion percentage and send reminders\n- Escalate to management after deadline\n\n### Step 5: Remediation and Tracking\n- Automatically ticket revocations to IT operations\n- Set SLA for revocation execution (24-48 hours for high-risk)\n- Verify revocation completed (re-check entitlement)\n- Exception management for business-justified deviations\n- Document all exceptions with expiration dates\n\n### Step 6: Reporting and Evidence\n- Generate campaign completion metrics\n- Produce per-application compliance reports\n- Create audit-ready evidence packages\n- Track trends across review cycles\n- Feed findings into risk assessment process\n\n## Security Controls\n| Control | NIST 800-53 | Description |\n|---------|-------------|-------------|\n| Access Review | AC-2(3) | Periodic review of account privileges |\n| Account Management | AC-2 | Account lifecycle management |\n| Least Privilege | AC-6 | Minimum necessary access enforcement |\n| Separation of Duties | AC-5 | SOD conflict identification |\n| Audit Logging | AU-6 | Review of access audit records |\n\n## Common Pitfalls\n- Rubber-stamping: reviewers approving all access without examination\n- Incomplete scope: missing critical applications from review campaigns\n- No remediation tracking: revoking access on paper but not in systems\n- Inconsistent reviewer assignment causing gaps in coverage\n- Not including service accounts and non-human identities\n\n## Verification\n- [ ] All in-scope applications included in campaign\n- [ ] Reviewers assigned for 100% of entitlements\n- [ ] Campaign completion rate exceeds 95%\n- [ ] Revocations executed within SLA\n- [ ] Audit evidence package complete and archived\n- [ ] SOD violations identified and documented\n- [ ] Exceptions documented with business justification and expiry\n",{"name":5,"tags":54,"author":55,"domain":48,"license":15,"version":56,"nist_csf":57,"subdomain":62,"description":7,"mitre_attack":63},[39,47,32,33,30,41,46],"mahipal","1.0",[58,59,60,61],"PR.AA-01","PR.AA-02","PR.AA-05","PR.AA-06","identity-access-management",[64,65,66,67],"T1078","T1110","T1556","T1098","main","54a798831d2266a3ca61ce68a7acb80b81160d57","skills\u002Fperforming-access-review-and-certification",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":79,"prompt":89,"zipAvailable":90},[80,83,86],{"tool":81,"command":82},"npx","npx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill performing-access-review-and-certification",{"tool":84,"command":85},"bunx","bunx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill performing-access-review-and-certification",{"tool":87,"command":88},"pnpm","pnpm dlx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill performing-access-review-and-certification","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fperforming-access-review-and-certification\u002FSKILL.md",true,[92,98,103,109,113,117,123],{"path":93,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":96,"sourceHtmlUrl":97},"assets\u002Ftemplate.md","ASSET","资产文件",1316,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fperforming-access-review-and-certification\u002Fassets\u002Ftemplate.md",{"path":99,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":101,"sourceHtmlUrl":102},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fperforming-access-review-and-certification\u002FLICENSE",{"path":104,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":107,"sourceHtmlUrl":108},"references\u002Fapi-reference.md","REFERENCE","参考文档",1455,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fperforming-access-review-and-certification\u002Freferences\u002Fapi-reference.md",{"path":110,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":111,"sourceHtmlUrl":112},"references\u002Fstandards.md",1058,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fperforming-access-review-and-certification\u002Freferences\u002Fstandards.md",{"path":114,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":115,"sourceHtmlUrl":116},"references\u002Fworkflows.md",2317,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fperforming-access-review-and-certification\u002Freferences\u002Fworkflows.md",{"path":118,"resourceType":119,"resourceTypeDesc":120,"sizeBytes":121,"sourceHtmlUrl":122},"scripts\u002Fagent.py","SCRIPT","脚本",5525,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fperforming-access-review-and-certification\u002Fscripts\u002Fagent.py",{"path":124,"resourceType":119,"resourceTypeDesc":120,"sizeBytes":125,"sourceHtmlUrl":126},"scripts\u002Fprocess.py",12424,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fperforming-access-review-and-certification\u002Fscripts\u002Fprocess.py",[128,153,177,203,229,253],{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":135,"publishedAt":49},"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",[134],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[136,137,138,139,140,48,141,47,45,142,143,144,145,146,147,148,149,150,151,152],"sigstore","provenance","slsa","verifying build provenance with slsa sigstore","security","incident response","code","artifacts","ci","supply-chain","pipeline","supply-chain-security","t1195","attestation","code-signing","cosign","keyless",{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":160,"publishedAt":49},"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",[159],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[161,149,162,163,140,164,48,45,165,166,167,168,169,170,171,172,173,174,175,176],"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":178,"name":179,"nameZh":6,"description":180,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":181,"categories":182,"keywords":187,"publishedAt":49},"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",[183,186],{"categoryNo":184,"categoryName":185,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[171,188,189,190,191,48,192,193,165,41,194,195,196,197,198,37,199,200,201,202],"backup","recovery","validating backup integrity for recovery","testing","infrastructure","validation","hash-verification","incident-response","ransomware","cryptocurrency","detection","t1490","immutable","disaster-recovery","restore-testing",{"skillNo":204,"name":205,"nameZh":6,"description":206,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":207,"categories":208,"keywords":210,"publishedAt":49},"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",[209],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[211,212,213,48,214,215,216,217,218,219,220,221,222,223,224,225,168,226,227,228],"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":230,"name":231,"nameZh":6,"description":232,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":233,"categories":234,"keywords":236,"publishedAt":49},"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",[235],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[237,238,239,48,240,44,241,242,243,244,245,246,247,38,36,248,249,250,251,252],"vulnerabilities","framework","triaging vulnerabilities with ssvc framework","status","CISA","vulnerability-management","risk-management","nessus","qualys","openvas","cvss","vulnerability","api","prioritization","ssvc","decision-tree",{"skillNo":254,"name":255,"nameZh":6,"description":256,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":257,"categories":258,"keywords":260,"publishedAt":49},"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",[259],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[140,261,48,262,263,264,265,266,267,268,269,37,270,199,271,272,273,274,275,276],"triaging security incident","siem","file","ioc","soc","NIST-800-61","NIST","severity","edr","execution","analysis","classification","severity-classification","incident-triage","SANS-PICERL","SOC-operations"]