[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AF7B8MD5KDXP5QTH8G1BXC":3,"skill-same:01M6AF7B8MD5KDXP5QTH8G1BXC":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":23,"publishedAt":42,"linkOnly":43,"markdownContent":44,"markdownBody":45,"frontMatter":46,"refName":61,"commitSha":62,"skillDirectory":63,"forksCount":64,"repositoryHtmlUrl":65,"repositoryHomepageUrl":66,"ownerHtmlUrl":67,"ownerBlogUrl":68,"ownerDescription":69,"updatedAt":70,"install":71,"resources":84},"01M6AF7B8MD5KDXP5QTH8G1BXC","implementing-just-in-time-access-provisioning",null,"Implements Just-In-Time (JIT) access provisioning to eliminate standing privileges by granting temporary, time-bound access, covering approval workflows, automatic expiration\u002Frevocation, and PAM\u002FIGA integration. Use when designing access approval workflows or replacing standing privileged accounts with time-bound, zero-trust-aligned grants.","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-just-in-time-access-provisioning\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41],"implementing just in time access provisioning","least-privilege","provisioning","PAM","just-in-time","t1098","t1078","zero-trust","IGA","cybersecurity","iam","access-control","ZeRO","jit","integration","pr","identity","workflows","2026-11-10 10:12:30",false,"---\nname: implementing-just-in-time-access-provisioning\ndescription: >-\n  Implements Just-In-Time (JIT) access provisioning to eliminate standing\n  privileges by granting temporary, time-bound access, covering approval\n  workflows, automatic expiration\u002Frevocation, and PAM\u002FIGA integration. Use when\n  designing access approval workflows or replacing standing privileged accounts\n  with time-bound, zero-trust-aligned grants.\ndomain: cybersecurity\nsubdomain: identity-access-management\ntags:\n- iam\n- identity\n- access-control\n- jit\n- provisioning\n- zero-trust\n- least-privilege\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# Implementing Just-In-Time Access Provisioning\n\n## Overview\nImplement Just-In-Time (JIT) access provisioning to eliminate standing privileges by granting temporary, time-bound access only when needed. This skill covers JIT architecture design, approval workflows, automatic expiration, integration with PAM and IGA platforms, and alignment with zero trust principles.\n\n\n## When to Use\n\n- When deploying or configuring implementing just in time access provisioning 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\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 JIT access request and approval workflows\n- Implement time-bound access grants with automatic expiration\n- Configure risk-based approval routing (auto-approve low-risk, multi-approval for high-risk)\n- Integrate JIT with PAM for privileged access elevation\n- Monitor and audit all JIT access grants and usage\n- Reduce attack surface by eliminating standing privileges\n\n## Key Concepts\n\n### JIT Access Models\n1. **Broker and Remove**: Grant access through approval, auto-remove after time window\n2. **Elevation on Demand**: User has base access, elevates to privileged upon request\n3. **Account Creation\u002FDeletion**: Temporary account created, destroyed after use\n4. **Group Membership Toggle**: Add to privileged group temporarily, auto-remove\n\n### Zero Standing Privilege (ZSP) Principle\n- No user has permanent privileged access\n- All privileged access requires explicit request with business justification\n- Access automatically expires after defined time window\n- All access events logged and auditable\n\n## Workflow\n\n### Step 1: Identify Eligible Access Types\n- Privileged admin access (domain admin, root, DBA)\n- Production environment access\n- Sensitive data access (PII, financial, healthcare)\n- Emergency\u002Fbreak-glass access\n- Third-party vendor access\n\n### Step 2: Design Approval Workflows\n- Self-service request portal with justification requirement\n- Auto-approve for pre-authorized low-risk access (\u003C 1 hour)\n- Single approver for medium-risk (manager or resource owner)\n- Dual approval for high-risk (manager + security team)\n- Emergency bypass with post-facto review\n\n### Step 3: Implement Time-Bound Access\n- Configure maximum access duration per resource type\n- Implement countdown timer with extension request capability\n- Auto-revoke at expiration regardless of session state\n- Grace period notification (15 min before expiry)\n- Automatic session termination on access expiry\n\n### Step 4: Integration Architecture\n- Connect to IAM\u002FIGA platform for provisioning\u002Fde-provisioning\n- Integrate with PAM for privileged credential checkout\n- Connect to ITSM for ticket correlation\n- Forward events to SIEM for monitoring\n- API integration for programmatic access requests\n\n### Step 5: Monitoring and Compliance\n- Log all JIT requests, approvals, grants, and revocations\n- Alert on access used beyond approved scope\n- Track access not used (request but never connected)\n- Measure mean time to access (request to grant)\n- Report on access patterns for baseline optimization\n\n## Security Controls\n| Control | NIST 800-53 | Description |\n|---------|-------------|-------------|\n| Temporary Access | AC-2(2) | Automated temporary account management |\n| Least Privilege | AC-6 | Time-bound minimum access |\n| Access Enforcement | AC-3 | Automated access grant\u002Frevoke |\n| Audit | AU-3 | Complete JIT access audit trail |\n| Risk Assessment | RA-3 | Risk-based approval routing |\n\n## Common Pitfalls\n- Setting time windows too long, negating JIT benefits\n- Not implementing automatic revocation at expiration\n- Complex approval workflows causing access delays for legitimate needs\n- Not providing emergency bypass for critical incidents\n- Failing to audit approved but unused JIT access\n\n## Verification\n- [ ] JIT request workflow functional end-to-end\n- [ ] Access automatically revoked at expiration\n- [ ] Approval routing correct for all risk levels\n- [ ] Emergency access bypass works with post-review\n- [ ] All JIT events logged to SIEM\n- [ ] Standing privileges reduced by measurable percentage\n- [ ] Mean time to access meets business SLA\n","# Implementing Just-In-Time Access Provisioning\n\n## Overview\nImplement Just-In-Time (JIT) access provisioning to eliminate standing privileges by granting temporary, time-bound access only when needed. This skill covers JIT architecture design, approval workflows, automatic expiration, integration with PAM and IGA platforms, and alignment with zero trust principles.\n\n\n## When to Use\n\n- When deploying or configuring implementing just in time access provisioning 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\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 JIT access request and approval workflows\n- Implement time-bound access grants with automatic expiration\n- Configure risk-based approval routing (auto-approve low-risk, multi-approval for high-risk)\n- Integrate JIT with PAM for privileged access elevation\n- Monitor and audit all JIT access grants and usage\n- Reduce attack surface by eliminating standing privileges\n\n## Key Concepts\n\n### JIT Access Models\n1. **Broker and Remove**: Grant access through approval, auto-remove after time window\n2. **Elevation on Demand**: User has base access, elevates to privileged upon request\n3. **Account Creation\u002FDeletion**: Temporary account created, destroyed after use\n4. **Group Membership Toggle**: Add to privileged group temporarily, auto-remove\n\n### Zero Standing Privilege (ZSP) Principle\n- No user has permanent privileged access\n- All privileged access requires explicit request with business justification\n- Access automatically expires after defined time window\n- All access events logged and auditable\n\n## Workflow\n\n### Step 1: Identify Eligible Access Types\n- Privileged admin access (domain admin, root, DBA)\n- Production environment access\n- Sensitive data access (PII, financial, healthcare)\n- Emergency\u002Fbreak-glass access\n- Third-party vendor access\n\n### Step 2: Design Approval Workflows\n- Self-service request portal with justification requirement\n- Auto-approve for pre-authorized low-risk access (\u003C 1 hour)\n- Single approver for medium-risk (manager or resource owner)\n- Dual approval for high-risk (manager + security team)\n- Emergency bypass with post-facto review\n\n### Step 3: Implement Time-Bound Access\n- Configure maximum access duration per resource type\n- Implement countdown timer with extension request capability\n- Auto-revoke at expiration regardless of session state\n- Grace period notification (15 min before expiry)\n- Automatic session termination on access expiry\n\n### Step 4: Integration Architecture\n- Connect to IAM\u002FIGA platform for provisioning\u002Fde-provisioning\n- Integrate with PAM for privileged credential checkout\n- Connect to ITSM for ticket correlation\n- Forward events to SIEM for monitoring\n- API integration for programmatic access requests\n\n### Step 5: Monitoring and Compliance\n- Log all JIT requests, approvals, grants, and revocations\n- Alert on access used beyond approved scope\n- Track access not used (request but never connected)\n- Measure mean time to access (request to grant)\n- Report on access patterns for baseline optimization\n\n## Security Controls\n| Control | NIST 800-53 | Description |\n|---------|-------------|-------------|\n| Temporary Access | AC-2(2) | Automated temporary account management |\n| Least Privilege | AC-6 | Time-bound minimum access |\n| Access Enforcement | AC-3 | Automated access grant\u002Frevoke |\n| Audit | AU-3 | Complete JIT access audit trail |\n| Risk Assessment | RA-3 | Risk-based approval routing |\n\n## Common Pitfalls\n- Setting time windows too long, negating JIT benefits\n- Not implementing automatic revocation at expiration\n- Complex approval workflows causing access delays for legitimate needs\n- Not providing emergency bypass for critical incidents\n- Failing to audit approved but unused JIT access\n\n## Verification\n- [ ] JIT request workflow functional end-to-end\n- [ ] Access automatically revoked at expiration\n- [ ] Approval routing correct for all risk levels\n- [ ] Emergency access bypass works with post-review\n- [ ] All JIT events logged to SIEM\n- [ ] Standing privileges reduced by measurable percentage\n- [ ] Mean time to access meets business SLA\n",{"name":5,"tags":47,"author":48,"domain":33,"license":15,"version":49,"nist_csf":50,"subdomain":55,"description":7,"mitre_attack":56},[34,40,35,37,26,31,25],"mahipal","1.0",[51,52,53,54],"PR.AA-01","PR.AA-02","PR.AA-05","PR.AA-06","identity-access-management",[57,58,59,60],"T1078","T1110","T1556","T1098","main","54a798831d2266a3ca61ce68a7acb80b81160d57","skills\u002Fimplementing-just-in-time-access-provisioning",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":72,"prompt":82,"zipAvailable":83},[73,76,79],{"tool":74,"command":75},"npx","npx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill implementing-just-in-time-access-provisioning",{"tool":77,"command":78},"bunx","bunx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill implementing-just-in-time-access-provisioning",{"tool":80,"command":81},"pnpm","pnpm dlx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill implementing-just-in-time-access-provisioning","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-just-in-time-access-provisioning\u002FSKILL.md",true,[85,91,97,102,106,110,114,120],{"path":86,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":89,"sourceHtmlUrl":90},"agents\u002Fopenai.yaml","REFERENCE","参考文档",158,"https:\u002F\u002Fgithub.com\u002Ffderuiter\u002FQRCraftly-web\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwait-what\u002Fagents\u002Fopenai.yaml",{"path":92,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":95,"sourceHtmlUrl":96},"assets\u002Ftemplate.md","ASSET","资产文件",1769,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-just-in-time-access-provisioning\u002Fassets\u002Ftemplate.md",{"path":98,"resourceType":98,"resourceTypeDesc":99,"sizeBytes":100,"sourceHtmlUrl":101},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-just-in-time-access-provisioning\u002FLICENSE",{"path":103,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":104,"sourceHtmlUrl":105},"references\u002Fapi-reference.md",1685,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-just-in-time-access-provisioning\u002Freferences\u002Fapi-reference.md",{"path":107,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":108,"sourceHtmlUrl":109},"references\u002Fstandards.md",1152,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-just-in-time-access-provisioning\u002Freferences\u002Fstandards.md",{"path":111,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":112,"sourceHtmlUrl":113},"references\u002Fworkflows.md",2307,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-just-in-time-access-provisioning\u002Freferences\u002Fworkflows.md",{"path":115,"resourceType":116,"resourceTypeDesc":117,"sizeBytes":118,"sourceHtmlUrl":119},"scripts\u002Fagent.py","SCRIPT","脚本",8370,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-just-in-time-access-provisioning\u002Fscripts\u002Fagent.py",{"path":121,"resourceType":116,"resourceTypeDesc":117,"sizeBytes":122,"sourceHtmlUrl":123},"scripts\u002Fprocess.py",13882,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-just-in-time-access-provisioning\u002Fscripts\u002Fprocess.py",[125,150,173,200,226,253],{"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":42},"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":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[133,134,135,136,137,33,138,40,39,139,140,141,142,143,144,145,146,147,148,149],"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":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":42},"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":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[158,146,159,160,137,161,33,39,162,36,163,164,165,166,167,168,169,170,171,172],"boot","TPM","validating tpm measured boot attestation","policy","verification","firmware","Tools","measured-boot","PCR","integrity","secrets","remote-attestation","tpm2-tools","integrity-verification","trusted-computing",{"skillNo":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":177,"categories":178,"keywords":183,"publishedAt":42},"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",[179,182],{"categoryNo":180,"categoryName":181,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[167,184,185,186,187,33,188,189,162,190,191,192,193,194,195,30,196,197,198,199],"backup","recovery","validating backup integrity for recovery","testing","infrastructure","validation","compliance","hash-verification","incident-response","ransomware","cryptocurrency","detection","t1490","immutable","disaster-recovery","restore-testing",{"skillNo":201,"name":202,"nameZh":6,"description":203,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":204,"categories":205,"keywords":207,"publishedAt":42},"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",[206],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[208,209,210,33,211,212,213,214,215,216,217,218,219,220,221,222,164,223,224,225],"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":227,"name":228,"nameZh":6,"description":229,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":230,"categories":231,"keywords":233,"publishedAt":42},"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",[232],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[234,235,236,33,237,238,239,240,241,242,243,244,245,246,247,248,249,250,251,252],"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":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":42},"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},[137,261,33,262,263,264,265,266,267,268,269,30,270,196,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"]