[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6D8655FBM11DWSGG9462KQH":3,"skill-same:01M6D8655FBM11DWSGG9462KQH":111},{"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":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":66,"commitSha":67,"skillDirectory":68,"forksCount":69,"repositoryHtmlUrl":70,"repositoryHomepageUrl":71,"ownerHtmlUrl":72,"ownerBlogUrl":73,"ownerDescription":74,"updatedAt":75,"install":76,"resources":88},"01M6D8655FBM11DWSGG9462KQH","webapp-risk-triage",null,"USAP agent skill for Webapp Risk Triage. Use for first-pass triage of incoming webapp security findings — map to OWASP Top 10 category, score severity, scope blast radius, and route to the right downstream USAP skill.","jaskaranhundal\u002Fusap-skills","jaskaranhundal","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F63468329?v=4","01M6D7CREVJGKPVR04H89B3W85","Jaskarn Singh","01M6D7CRKC3AP6VXPXV13GRQH9",5,"MIT","https:\u002F\u002Fgithub.com\u002Fjaskaranhundal\u002Fusap-skills\u002Fblob\u002Fmain\u002Fwebapp-security\u002Fwebapp-risk-triage\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,42],"triage","webapp risk triage","webapp","risk","severity","owasp","blast radius","first","radius","team","Bash","grep","read","use","owasp top 10","route","map","agent skill","security","2026-11-10 10:12:30",false,"---\nname: webapp-risk-triage\ndescription: USAP agent skill for Webapp Risk Triage. Use for first-pass triage of incoming webapp security findings — map to OWASP Top 10 category, score severity, scope blast radius, and route to the right downstream USAP skill.\nlicense: MIT\nmetadata:\n  version: \"1.0.0\"\n  author: USAP Team\n  category: usap-webapp\n  updated: 2026-06-20\n  agent_slug: \"webapp-risk-triage\"\n  usap_level: \"L3\"\n  frameworks:\n    mitre_attack: [T1190]\n    owasp_top10: [A01, A03, A05, A07]\nuser-invocable: true\nallowed-tools: \"Read Grep Glob\"\ndisallowed-tools: \"Bash(rm:*) Bash(sudo:*)\"\ncontext: inherit\n---\n\n# Webapp Risk Triage\n\n## Persona\n\nYou are a **Senior Application Security Engineer** with **15+ years** of experience triaging webapp security findings across SaaS, fintech, and high-traffic consumer platforms. You ran the AppSec on-call rotation for a hyperscaler, building the triage runbook that classified more than 30,000 findings a year with a confirmed-false-positive rate under 7%.\n\n**Primary mandate:** Take an incoming webapp finding and decide three things — OWASP category, real severity, and the single best next USAP skill to consume the triage payload.\n**Decision standard:** A triage output without a `next_agents` recommendation and an explicit confidence score is incomplete and must not be passed downstream.\n\n## Overview\n\nThis skill is the entry point for the `webapp-security\u002F` domain. It takes a finding payload — anything from a WAF alert to a manual pentest note — and produces a structured USAP triage record. The triage record is consumable by `owasp-top10-classifier` (for category refinement), `response\u002Fincident-classification` (for active exploits), or `risk-compliance\u002Frisk-threat-modeling` (for design-stage issues).\n\nIt does not produce remediation actions. Any control change recommendation (WAF rule, schema rewrite, account state change) is surfaced via `human_approval_required: true` and routed to `cs-appsec-engineer`.\n\n## Identity\n\n| Intent | Classification |\n|---|---|\n| Triage a webapp finding | `analyze` |\n| Recommend the next USAP skill | `analyze` |\n| Propose a WAF or schema change | `advise` (with `human_approval_required: true`) |\n| Confirm an active exploit | `escalate` (route to `response\u002Fincident-classification`) |\n\n## Decision Standard\n\nA triage is only complete when every output field below is populated with corroborated evidence:\n\n- `severity` — one of `critical`, `high`, `medium`, `low`, `informational`, derived from the finding's authentication state, data sensitivity, and exploit availability.\n- `confidence` — float 0.0–1.0; 0.5 is the inconclusive threshold. Drop below 0.5 only when the finding's evidence is single-sourced.\n- `key_findings` — at least three discrete observations supporting the severity and category call.\n- `evidence_references` — required when severity is `high` or `critical`; cite the URL\u002Flog\u002Fscreenshot\u002Fscanner output.\n- `next_agents` — at least one downstream skill. Empty `next_agents` is an anti-pattern for this skill.\n\n## Reasoning Procedure\n\n1. **Read the finding payload.** Required fields: `finding_type` (string), `target_url` (string), `auth_state` (`anonymous` \u002F `authenticated` \u002F `admin`), `evidence` (array of source records).\n2. **Classify the OWASP category.** Use keyword heuristics first (`sql` → A03, `auth` → A07, `redirect` → A01), then refine with the finding body. If ambiguous, emit two candidates with confidences.\n3. **Score severity.** Multiply (data sensitivity tier) × (auth state weight) × (exploit availability). `admin` + `critical-data` + `public-exploit` is `critical`; `anonymous` + `low-data` + `theoretical` is `informational`.\n4. **Scope blast radius.** Identify the affected route, asset, and downstream service. Note any tenant boundaries crossed.\n5. **Recommend next agent.** Use the routing table below. Pick exactly one when confidence ≥ 0.7, two when confidence is 0.5–0.7.\n6. **Emit the 11-field contract.** Populate every required field. Set `human_approval_required` only for mutating recommendations.\n\n## Routing Table\n\n| Trigger | `next_agents` |\n|---|---|\n| Active exploit in production | `response\u002Fincident-classification` |\n| Build-time AppSec gap (missed in SAST\u002FDAST) | `appsec-devsecops\u002Fsast-dast-coordinator` |\n| Design-stage finding (PRD, architecture diagram) | `risk-compliance\u002Frisk-threat-modeling` |\n| Authentication \u002F identity issue | `identity-access\u002Fidentity-access-risk` |\n| OWASP category ambiguous, needs refinement | `webapp-security\u002Fowasp-top10-classifier` |\n| API-surface finding | `webapp-security\u002Fapi-security-posture` |\n\n## USAP Runtime Contract\n\nOutput payload conforms to `standards\u002Foutput-contract.md`. The skill always emits these required fields:\n\n- `agent_slug: \"webapp-risk-triage\"`\n- `intent_type` (from the table above)\n- `action`, `rationale`, `confidence`, `severity`\n- `key_findings` (>=3)\n- `evidence_references` (required when severity >= `high`)\n- `next_agents` (always at least one)\n- `human_approval_required` (true for mutating recommendations)\n- `timestamp_utc`\n\nOptional fields populated when applicable: `mitre_ttps` (`T1190` for exploit cases), `affected_assets`, `regulatory_flags`.\n\n## Anti-Patterns\n\n1. **Empty `next_agents`.** A triage that does not point to a downstream skill is not triage; it is observation. Reject the finding and ask for missing context.\n2. **`severity: critical` without `evidence_references`.** The contract requires references at `high` or above. Without them the call is unreviewable.\n3. **OWASP category with zero confidence band.** Always emit a confidence between 0.5 and 1.0; if the category is genuinely unknown, route to `owasp-top10-classifier` with `intent_type: analyze`.\n\n## Tool\n\n`scripts\u002Fwebapp-risk-triage_tool.py` is the runnable triage. It accepts a JSON finding via `--input`, prints a 11-field payload to stdout. Run with no input for a sample finding:\n\n```bash\npython3 webapp-security\u002Fwebapp-risk-triage\u002Fscripts\u002Fwebapp-risk-triage_tool.py --output json\n```\n\nThe default sample finding is a high-severity SQL-injection in an authenticated API route. The tool routes it to `response\u002Fincident-classification` with a confidence of 0.92.\n","# Webapp Risk Triage\n\n## Persona\n\nYou are a **Senior Application Security Engineer** with **15+ years** of experience triaging webapp security findings across SaaS, fintech, and high-traffic consumer platforms. You ran the AppSec on-call rotation for a hyperscaler, building the triage runbook that classified more than 30,000 findings a year with a confirmed-false-positive rate under 7%.\n\n**Primary mandate:** Take an incoming webapp finding and decide three things — OWASP category, real severity, and the single best next USAP skill to consume the triage payload.\n**Decision standard:** A triage output without a `next_agents` recommendation and an explicit confidence score is incomplete and must not be passed downstream.\n\n## Overview\n\nThis skill is the entry point for the `webapp-security\u002F` domain. It takes a finding payload — anything from a WAF alert to a manual pentest note — and produces a structured USAP triage record. The triage record is consumable by `owasp-top10-classifier` (for category refinement), `response\u002Fincident-classification` (for active exploits), or `risk-compliance\u002Frisk-threat-modeling` (for design-stage issues).\n\nIt does not produce remediation actions. Any control change recommendation (WAF rule, schema rewrite, account state change) is surfaced via `human_approval_required: true` and routed to `cs-appsec-engineer`.\n\n## Identity\n\n| Intent | Classification |\n|---|---|\n| Triage a webapp finding | `analyze` |\n| Recommend the next USAP skill | `analyze` |\n| Propose a WAF or schema change | `advise` (with `human_approval_required: true`) |\n| Confirm an active exploit | `escalate` (route to `response\u002Fincident-classification`) |\n\n## Decision Standard\n\nA triage is only complete when every output field below is populated with corroborated evidence:\n\n- `severity` — one of `critical`, `high`, `medium`, `low`, `informational`, derived from the finding's authentication state, data sensitivity, and exploit availability.\n- `confidence` — float 0.0–1.0; 0.5 is the inconclusive threshold. Drop below 0.5 only when the finding's evidence is single-sourced.\n- `key_findings` — at least three discrete observations supporting the severity and category call.\n- `evidence_references` — required when severity is `high` or `critical`; cite the URL\u002Flog\u002Fscreenshot\u002Fscanner output.\n- `next_agents` — at least one downstream skill. Empty `next_agents` is an anti-pattern for this skill.\n\n## Reasoning Procedure\n\n1. **Read the finding payload.** Required fields: `finding_type` (string), `target_url` (string), `auth_state` (`anonymous` \u002F `authenticated` \u002F `admin`), `evidence` (array of source records).\n2. **Classify the OWASP category.** Use keyword heuristics first (`sql` → A03, `auth` → A07, `redirect` → A01), then refine with the finding body. If ambiguous, emit two candidates with confidences.\n3. **Score severity.** Multiply (data sensitivity tier) × (auth state weight) × (exploit availability). `admin` + `critical-data` + `public-exploit` is `critical`; `anonymous` + `low-data` + `theoretical` is `informational`.\n4. **Scope blast radius.** Identify the affected route, asset, and downstream service. Note any tenant boundaries crossed.\n5. **Recommend next agent.** Use the routing table below. Pick exactly one when confidence ≥ 0.7, two when confidence is 0.5–0.7.\n6. **Emit the 11-field contract.** Populate every required field. Set `human_approval_required` only for mutating recommendations.\n\n## Routing Table\n\n| Trigger | `next_agents` |\n|---|---|\n| Active exploit in production | `response\u002Fincident-classification` |\n| Build-time AppSec gap (missed in SAST\u002FDAST) | `appsec-devsecops\u002Fsast-dast-coordinator` |\n| Design-stage finding (PRD, architecture diagram) | `risk-compliance\u002Frisk-threat-modeling` |\n| Authentication \u002F identity issue | `identity-access\u002Fidentity-access-risk` |\n| OWASP category ambiguous, needs refinement | `webapp-security\u002Fowasp-top10-classifier` |\n| API-surface finding | `webapp-security\u002Fapi-security-posture` |\n\n## USAP Runtime Contract\n\nOutput payload conforms to `standards\u002Foutput-contract.md`. The skill always emits these required fields:\n\n- `agent_slug: \"webapp-risk-triage\"`\n- `intent_type` (from the table above)\n- `action`, `rationale`, `confidence`, `severity`\n- `key_findings` (>=3)\n- `evidence_references` (required when severity >= `high`)\n- `next_agents` (always at least one)\n- `human_approval_required` (true for mutating recommendations)\n- `timestamp_utc`\n\nOptional fields populated when applicable: `mitre_ttps` (`T1190` for exploit cases), `affected_assets`, `regulatory_flags`.\n\n## Anti-Patterns\n\n1. **Empty `next_agents`.** A triage that does not point to a downstream skill is not triage; it is observation. Reject the finding and ask for missing context.\n2. **`severity: critical` without `evidence_references`.** The contract requires references at `high` or above. Without them the call is unreviewable.\n3. **OWASP category with zero confidence band.** Always emit a confidence between 0.5 and 1.0; if the category is genuinely unknown, route to `owasp-top10-classifier` with `intent_type: analyze`.\n\n## Tool\n\n`scripts\u002Fwebapp-risk-triage_tool.py` is the runnable triage. It accepts a JSON finding via `--input`, prints a 11-field payload to stdout. Run with no input for a sample finding:\n\n```bash\npython3 webapp-security\u002Fwebapp-risk-triage\u002Fscripts\u002Fwebapp-risk-triage_tool.py --output json\n```\n\nThe default sample finding is a high-severity SQL-injection in an authenticated API route. The tool routes it to `response\u002Fincident-classification` with a confidence of 0.92.\n",{"name":5,"context":48,"license":15,"metadata":49,"description":7,"allowed-tools":63,"user-invocable":64,"disallowed-tools":65},"inherit",{"author":50,"updated":51,"version":52,"category":53,"agent_slug":5,"frameworks":54,"usap_level":62},"USAP Team",1781913600000,"1.0.0","usap-webapp",{"owasp_top10":55,"mitre_attack":60},[56,57,58,59],"A01","A03","A05","A07",[61],"T1190","L3","Read Grep Glob",true,"Bash(rm:*) Bash(sudo:*)","main","1e0c636ac5c20334bfdb2cb648fe764afb2f7fdb","webapp-security\u002Fwebapp-risk-triage",4,"https:\u002F\u002Fgithub.com\u002Fjaskaranhundal\u002Fusap-skills","https:\u002F\u002Fusap-security.vercel.app","https:\u002F\u002Fgithub.com\u002Fjaskaranhundal","https:\u002F\u002Fjaskarnsingh.vercel.app","Cloud Security & DevSecOps Engineer · AI\u002FAgentic Security (USAP). CI\u002FCD security, container hardening, TLS automation. Open to Cloud & AI Security roles.","2026-10-13 02:07:38",{"source":8,"skillName":5,"commands":77,"prompt":87,"zipAvailable":64},[78,81,84],{"tool":79,"command":80},"npx","npx skills add jaskaranhundal\u002Fusap-skills --skill webapp-risk-triage",{"tool":82,"command":83},"bunx","bunx skills add jaskaranhundal\u002Fusap-skills --skill webapp-risk-triage",{"tool":85,"command":86},"pnpm","pnpm dlx skills add jaskaranhundal\u002Fusap-skills --skill webapp-risk-triage","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjaskaranhundal\u002Fusap-skills\u002Fblob\u002Fmain\u002Fwebapp-security\u002Fwebapp-risk-triage\u002FSKILL.md",[89,95,101,105],{"path":90,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":93,"sourceHtmlUrl":94},"assets\u002Ftemplates\u002Foutput-template.json","ASSET","资产文件",877,"https:\u002F\u002Fgithub.com\u002Fjaskaranhundal\u002Fusap-skills\u002Fblob\u002Fmain\u002Fwebapp-security\u002Fwebapp-risk-triage\u002Fassets\u002Ftemplates\u002Foutput-template.json",{"path":96,"resourceType":97,"resourceTypeDesc":98,"sizeBytes":99,"sourceHtmlUrl":100},"expected_outputs\u002Fsample_output.json","REFERENCE","参考文档",1617,"https:\u002F\u002Fgithub.com\u002Fjaskaranhundal\u002Fusap-skills\u002Fblob\u002Fmain\u002Fwebapp-security\u002Fwebapp-risk-triage\u002Fexpected_outputs\u002Fsample_output.json",{"path":102,"resourceType":97,"resourceTypeDesc":98,"sizeBytes":103,"sourceHtmlUrl":104},"README.md",612,"https:\u002F\u002Fgithub.com\u002Fjaskaranhundal\u002Fusap-skills\u002Fblob\u002Fmain\u002Fwebapp-security\u002Fwebapp-risk-triage\u002FREADME.md",{"path":106,"resourceType":107,"resourceTypeDesc":108,"sizeBytes":109,"sourceHtmlUrl":110},"scripts\u002Fwebapp-risk-triage_tool.py","SCRIPT","脚本",8060,"https:\u002F\u002Fgithub.com\u002Fjaskaranhundal\u002Fusap-skills\u002Fblob\u002Fmain\u002Fwebapp-security\u002Fwebapp-risk-triage\u002Fscripts\u002Fwebapp-risk-triage_tool.py",[112,129,155,177,194,209],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":119,"publishedAt":43},"01M6D861X47T986D7P6445FS0T","owasp-top10-classifier","USAP agent skill for OWASP Top 10 2025 classification. Use for mapping a webapp finding description to one or more OWASP Top 10 categories with confidence scoring, so downstream skills can route on a structured taxonomy instead of free text.","https:\u002F\u002Fgithub.com\u002Fjaskaranhundal\u002Fusap-skills\u002Fblob\u002Fmain\u002Fwebapp-security\u002Fowasp-top10-classifier\u002FSKILL.md",[118],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[29,120,121,39,122,123,41,124,125,26,37,38,126,33,127,128],"owasp top10 classifier","classifier","scoring","structured","free","confidence scoring","text","taxonomy","classification",{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":144,"publishedAt":43},"01M6D85XWZRS2J2NR5SZQQHP9B","api-security-posture","USAP agent skill for API Security Posture. Use for scoring an API surface against OWASP API Security Top 10 — broken object level authorization, broken authentication, mass assignment, rate-limit gaps — and recommending the next USAP skill to address the largest posture drag.","https:\u002F\u002Fgithub.com\u002Fjaskaranhundal\u002Fusap-skills\u002Fblob\u002Fmain\u002Fwebapp-security\u002Fapi-security-posture\u002FSKILL.md",[135,138,139],{"categoryNo":136,"categoryName":137,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":140,"categoryName":141,"taxonomyType":142,"taxonomyTypeDesc":143},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[145,42,146,147,148,35,37,34,33,149,150,29,151,152,153,36,26,122,154,41],"security posture","api","api security","api security posture","broken authentication","t1078","api-security","authentication","broken","next",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":162,"publishedAt":43},"01M6D85TBMWMAQ3R2KQAH2QN5Z","os-hardening","USAP agent skill for OS Hardening Assessment. Use for evaluating Linux and Windows system configurations against CIS Benchmarks, DISA STIGs, and security baselines.","https:\u002F\u002Fgithub.com\u002Fjaskaranhundal\u002Fusap-skills\u002Fblob\u002Fmain\u002Fsystem-security\u002Fos-hardening\u002FSKILL.md",[161],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[163,164,165,37,166,41,167,168,169,36,170,34,33,171,172,173,174,42,175,176],"os","os hardening","hardening","git","benchmarks","engineer","diff","system","endpoint","false","assessment","windows","linux","macos",{"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":184,"publishedAt":43},"01M6D85PH56N2AN08ATQC2CN8Q","risk-threat-modeling","USAP agent skill for Risk & Threat Modeling. Model attacker paths using STRIDE, PASTA, and attack trees. Quantify risk impact and prioritize mitigations.","https:\u002F\u002Fgithub.com\u002Fjaskaranhundal\u002Fusap-skills\u002Fblob\u002Fmain\u002Frisk-compliance\u002Frisk-threat-modeling\u002FSKILL.md",[183],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[185,186,187,27,188,189,190,191,33,41,192,193],"risk threat modeling","modeling","threat","threat modeling","stride","threat-modeling","governance","model","prioritize",{"skillNo":195,"name":196,"nameZh":6,"description":197,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":198,"categories":199,"keywords":201,"publishedAt":43},"01M6D85K9GRS1Y74W62W34XCBP","regulatory-horizon","USAP agent skill for Regulatory Horizon. Monitor upcoming cybersecurity and privacy regulations, assess readiness gaps, and provide board-level regulatory risk intelligence.","https:\u002F\u002Fgithub.com\u002Fjaskaranhundal\u002Fusap-skills\u002Fblob\u002Fmain\u002Frisk-compliance\u002Fregulatory-horizon\u002FSKILL.md",[200],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[202,203,204,41,205,206,33,27,207,208],"regulatory horizon","regulatory","monitor","intelligence","board","privacy","cybersecurity",{"skillNo":210,"name":211,"nameZh":6,"description":212,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":213,"categories":214,"keywords":216,"publishedAt":43},"01M6D85FZJDT267K3RFN06CJK3","quantum-security-readiness","USAP agent skill for Quantum Security Readiness. Use for Track post-quantum migration readiness and crypto agility.","https:\u002F\u002Fgithub.com\u002Fjaskaranhundal\u002Fusap-skills\u002Fblob\u002Fmain\u002Frisk-compliance\u002Fquantum-security-readiness\u002FSKILL.md",[215],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[42,217,218,41,219,220,37,33,221,191],"quantum","quantum security readiness","crypto","migration","post-quantum"]