[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A8A7PVC1D439PV220X4JCB":3,"skill-same:01M7A8A7PVC1D439PV220X4JCB":115},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":60,"commitSha":61,"skillDirectory":62,"forksCount":14,"repositoryHtmlUrl":63,"repositoryHomepageUrl":6,"ownerHtmlUrl":64,"ownerBlogUrl":6,"ownerDescription":65,"updatedAt":66,"install":67,"resources":80},"01M7A8A7PVC1D439PV220X4JCB","implementing-mitre-attack-coverage-mapping",null,"Implement MITRE ATT&CK coverage mapping to identify detection gaps, prioritize rule development, and measure SOC detection maturity against adversary techniques.","NeelakshSaxena\u002FVayu","NeelakshSaxena","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F87892838?v=4","01M7A3B9YFS6F6N9DD1787DT86","Neelaksh Saxena","01M7A3B9ZKBT09MNMPX2XN69BY",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-mitre-attack-coverage-mapping\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-mitre-attack-coverage-mapping\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: implementing-mitre-attack-coverage-mapping\ndescription: Implement MITRE ATT&CK coverage mapping to identify detection gaps, prioritize\n  rule development, and measure SOC detection maturity against adversary techniques.\ndomain: cybersecurity\nsubdomain: soc-operations\ntags:\n- mitre-attack\n- detection-coverage\n- gap-analysis\n- attack-navigator\n- soc\n- detection-engineering\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_ai_rmf:\n- MEASURE-2.7\n- MAP-5.1\n- MANAGE-2.4\natlas_techniques:\n- AML.T0070\n- AML.T0066\n- AML.T0082\nd3fend_techniques:\n- Token Binding\n- Restore Access\n- Application Protocol Command Analysis\n- Password Authentication\n- Reissue Credential\nnist_csf:\n- DE.CM-01\n- DE.AE-02\n- RS.MA-01\n- DE.AE-06\nmitre_attack:\n- T1078\n- T1685.002\n- T1685.005\n- T1566\n---\n\n# Implementing MITRE ATT&CK Coverage Mapping\n\n## Overview\n\nMITRE ATT&CK coverage mapping gives SOC teams a structured, adversary-centric lens to evaluate detection capabilities. Enterprise SIEMs on average have detection coverage for only 21% of ATT&CK techniques (2025 CardinalOps report), with 13% of existing rules being non-functional due to misconfigured data sources. Systematic coverage mapping identifies gaps, prioritizes rule development, and tracks detection maturity over time. ATT&CK v18.1 (December 2025) is the latest version.\n\n\n## When to Use\n\n- When deploying or configuring implementing mitre attack coverage mapping 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- Access to MITRE ATT&CK Navigator (https:\u002F\u002Fmitre-attack.github.io\u002Fattack-navigator\u002F)\n- Inventory of all active SIEM detection rules\n- MITRE ATT&CK technique mapping for each detection rule\n- Data source inventory (which log sources are ingested)\n- Understanding of adversary threat profiles relevant to your industry\n\n## Coverage Mapping Process\n\n### Step 1: Export Current Detection Rules\n\n```spl\n# Splunk ES - Export all active correlation searches with MITRE mappings\n| rest \u002Fservices\u002Fsaved\u002Fsearches\n| search disabled=0 action.correlationsearch.enabled=1\n| table title, search, action.notable.param.security_domain,\n    action.notable.param.severity, action.correlationsearch.annotations\n| eval mitre_techniques=mvfilter(match('action.correlationsearch.annotations', \"mitre_attack\"))\n```\n\n```kql\n\u002F\u002F Microsoft Sentinel - Export analytics rules with MITRE mapping\nSecurityAlert\n| summarize count() by AlertName, ProductName\n| join kind=inner (\n    resources\n    | where type == \"microsoft.securityinsights\u002Falertrules\"\n    | extend tactics = properties.tactics\n) on $left.AlertName == $right.name\n```\n\n### Step 2: Build the Coverage Matrix\n\n#### ATT&CK Navigator Layer Format\n\n```json\n{\n    \"name\": \"SOC Detection Coverage - 2025\",\n    \"versions\": {\n        \"attack\": \"16\",\n        \"navigator\": \"5.1\",\n        \"layer\": \"4.5\"\n    },\n    \"domain\": \"enterprise-attack\",\n    \"description\": \"Current detection coverage mapping\",\n    \"techniques\": [\n        {\n            \"techniqueID\": \"T1110\",\n            \"tactic\": \"credential-access\",\n            \"color\": \"#00ff00\",\n            \"comment\": \"2 active rules - Brute Force detection via EventCode 4625\",\n            \"score\": 75,\n            \"metadata\": [\n                {\"name\": \"rule_count\", \"value\": \"2\"},\n                {\"name\": \"data_sources\", \"value\": \"Windows Security Log, Linux Auth\"},\n                {\"name\": \"last_validated\", \"value\": \"2025-01-15\"}\n            ]\n        },\n        {\n            \"techniqueID\": \"T1059.001\",\n            \"tactic\": \"execution\",\n            \"color\": \"#00ff00\",\n            \"comment\": \"3 rules - PowerShell Script Block Logging\",\n            \"score\": 85\n        },\n        {\n            \"techniqueID\": \"T1055\",\n            \"tactic\": \"defense-evasion\",\n            \"color\": \"#ff0000\",\n            \"comment\": \"NO DETECTION - Requires Sysmon EventCode 8\u002F10\",\n            \"score\": 0\n        }\n    ],\n    \"gradient\": {\n        \"colors\": [\"#ff0000\", \"#ffff00\", \"#00ff00\"],\n        \"minValue\": 0,\n        \"maxValue\": 100\n    }\n}\n```\n\n### Step 3: Score Each Technique\n\n| Score | Color | Meaning | Criteria |\n|---|---|---|---|\n| 0 | Red | No Detection | No rules, missing data sources |\n| 25 | Orange | Minimal | Rule exists but not validated\u002Ftested |\n| 50 | Yellow | Partial | Rule works but limited coverage |\n| 75 | Light Green | Good | Validated rule with good data sources |\n| 100 | Green | Excellent | Multiple validated rules, tested with emulation |\n\n### Scoring Criteria Detail\n\n```\nScore = Data_Source_Score (0-25) + Rule_Quality_Score (0-25) +\n        Validation_Score (0-25) + Enrichment_Score (0-25)\n\nData_Source_Score:\n  25: All required data sources ingested and parsed\n  15: Primary data source available\n  5:  Partial data source coverage\n  0:  Required data sources not available\n\nRule_Quality_Score:\n  25: Rule uses CIM-compliant queries with proper thresholds\n  15: Rule works but may generate false positives\n  5:  Basic rule with no tuning\n  0:  No detection rule\n\nValidation_Score:\n  25: Validated with adversary emulation (Atomic Red Team)\n  15: Tested with synthetic data\n  5:  Logic reviewed but not tested\n  0:  Not validated\n\nEnrichment_Score:\n  25: Context-rich with asset, identity, and TI enrichment\n  15: Basic enrichment (asset lookup)\n  5:  No enrichment\n  0:  N\u002FA (no rule)\n```\n\n### Step 4: Identify Priority Gaps\n\n#### Gap Prioritization Framework\n\n```\nPriority = Technique_Prevalence x Impact x Feasibility\n\nTechnique_Prevalence (0-10):\n  - Based on MITRE Top Techniques report\n  - Frequency in your industry's threat landscape\n  - Observed in recent incidents\u002Fbreaches\n\nImpact (0-10):\n  - Damage potential if technique succeeds\n  - Difficulty of recovery\n  - Data sensitivity at risk\n\nFeasibility (0-10):\n  - Data source availability\n  - Rule complexity\n  - Engineering effort required\n```\n\n#### Top Priority Techniques to Cover (2025)\n\n| Technique | ID | Prevalence | Typical Gap Reason |\n|---|---|---|---|\n| Command and Scripting Interpreter | T1059 | Very High | Requires script block logging |\n| Phishing | T1566 | Very High | Email gateway integration |\n| Valid Accounts | T1078 | High | Baseline behavior needed |\n| Process Injection | T1055 | High | Requires Sysmon or EDR |\n| Lateral Movement (RDP\u002FSMB) | T1021 | High | Network segmentation visibility |\n| Scheduled Task\u002FJob | T1053 | High | Event log collection |\n| Data Encrypted for Impact | T1486 | High | File system monitoring |\n| Ingress Tool Transfer | T1105 | Medium | Network traffic analysis |\n\n### Step 5: Build Detection Roadmap\n\n```\nQuarter 1: Close Critical Gaps (Score 0, High Prevalence)\n  Week 1-2: Enable missing data sources\n  Week 3-4: Build and test rules for top 5 gap techniques\n  Week 5-8: Validate with adversary emulation\n  Week 9-12: Tune and operationalize\n\nQuarter 2: Improve Partial Coverage (Score 25-50)\n  - Upgrade existing rules with enrichment\n  - Add secondary detection methods\n  - Validate with purple team exercises\n\nQuarter 3: Mature Good Coverage (Score 50-75)\n  - Add behavioral analytics\n  - Implement detection-as-code pipeline\n  - Cross-technique correlation rules\n\nQuarter 4: Excellence (Score 75-100)\n  - Continuous testing with BAS tools\n  - Automated coverage regression testing\n  - Red team validation\n```\n\n## Automated Coverage Assessment\n\n### Data Source to Technique Mapping\n\n```python\n# Map available data sources to detectable techniques\nDATA_SOURCE_TECHNIQUE_MAP = {\n    \"Windows Security Event Log\": [\n        \"T1110\", \"T1078\", \"T1053.005\", \"T1098\", \"T1136\",\n        \"T1070.001\", \"T1021.001\", \"T1543.003\"\n    ],\n    \"Sysmon\": [\n        \"T1055\", \"T1059\", \"T1003\", \"T1547.001\", \"T1036\",\n        \"T1218\", \"T1105\", \"T1071\"\n    ],\n    \"Network Traffic (Firewall\u002FIDS)\": [\n        \"T1071\", \"T1048\", \"T1105\", \"T1572\", \"T1090\",\n        \"T1571\", \"T1573\"\n    ],\n    \"DNS Logs\": [\n        \"T1071.004\", \"T1568\", \"T1583.001\", \"T1048.003\"\n    ],\n    \"Email Gateway\": [\n        \"T1566.001\", \"T1566.002\", \"T1534\"\n    ],\n    \"Cloud Audit Logs\": [\n        \"T1078.004\", \"T1537\", \"T1530\", \"T1580\",\n        \"T1087.004\", \"T1098.001\"\n    ],\n}\n```\n\n## Reporting Dashboard Queries\n\n### Coverage Summary by Tactic\n\n```spl\n| inputlookup mitre_coverage_lookup\n| stats avg(score) as avg_score count(eval(score=0)) as no_coverage\n    count(eval(score>0 AND score\u003C50)) as partial\n    count(eval(score>=50 AND score\u003C75)) as good\n    count(eval(score>=75)) as excellent\n    count as total\n    by tactic\n| eval coverage_pct=round((total - no_coverage) \u002F total * 100, 1)\n| sort -coverage_pct\n```\n\n## References\n\n- [CyberDefenders - MITRE ATT&CK for SOC & DFIR Analysts](https:\u002F\u002Fcyberdefenders.org\u002Fblog\u002Fmitre-attack-framework\u002F)\n- [MITRE ATT&CK Navigator](https:\u002F\u002Fmitre-attack.github.io\u002Fattack-navigator\u002F)\n- [CardinalOps - SIEM Detection Coverage Report 2025](https:\u002F\u002Fwww.helpnetsecurity.com\u002F2025\u002F06\u002F09\u002Fsiem-detection-coverage\u002F)\n- [Datadog - Cloud SIEM MITRE ATT&CK Map](https:\u002F\u002Fwww.datadoghq.com\u002Fblog\u002Fcloud-siem-mitre-attack-map\u002F)\n- [Picus Security - MITRE ATT&CK Framework Guide](https:\u002F\u002Fwww.picussecurity.com\u002Fmitre-attack-framework)\n","# Implementing MITRE ATT&CK Coverage Mapping\n\n## Overview\n\nMITRE ATT&CK coverage mapping gives SOC teams a structured, adversary-centric lens to evaluate detection capabilities. Enterprise SIEMs on average have detection coverage for only 21% of ATT&CK techniques (2025 CardinalOps report), with 13% of existing rules being non-functional due to misconfigured data sources. Systematic coverage mapping identifies gaps, prioritizes rule development, and tracks detection maturity over time. ATT&CK v18.1 (December 2025) is the latest version.\n\n\n## When to Use\n\n- When deploying or configuring implementing mitre attack coverage mapping 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- Access to MITRE ATT&CK Navigator (https:\u002F\u002Fmitre-attack.github.io\u002Fattack-navigator\u002F)\n- Inventory of all active SIEM detection rules\n- MITRE ATT&CK technique mapping for each detection rule\n- Data source inventory (which log sources are ingested)\n- Understanding of adversary threat profiles relevant to your industry\n\n## Coverage Mapping Process\n\n### Step 1: Export Current Detection Rules\n\n```spl\n# Splunk ES - Export all active correlation searches with MITRE mappings\n| rest \u002Fservices\u002Fsaved\u002Fsearches\n| search disabled=0 action.correlationsearch.enabled=1\n| table title, search, action.notable.param.security_domain,\n    action.notable.param.severity, action.correlationsearch.annotations\n| eval mitre_techniques=mvfilter(match('action.correlationsearch.annotations', \"mitre_attack\"))\n```\n\n```kql\n\u002F\u002F Microsoft Sentinel - Export analytics rules with MITRE mapping\nSecurityAlert\n| summarize count() by AlertName, ProductName\n| join kind=inner (\n    resources\n    | where type == \"microsoft.securityinsights\u002Falertrules\"\n    | extend tactics = properties.tactics\n) on $left.AlertName == $right.name\n```\n\n### Step 2: Build the Coverage Matrix\n\n#### ATT&CK Navigator Layer Format\n\n```json\n{\n    \"name\": \"SOC Detection Coverage - 2025\",\n    \"versions\": {\n        \"attack\": \"16\",\n        \"navigator\": \"5.1\",\n        \"layer\": \"4.5\"\n    },\n    \"domain\": \"enterprise-attack\",\n    \"description\": \"Current detection coverage mapping\",\n    \"techniques\": [\n        {\n            \"techniqueID\": \"T1110\",\n            \"tactic\": \"credential-access\",\n            \"color\": \"#00ff00\",\n            \"comment\": \"2 active rules - Brute Force detection via EventCode 4625\",\n            \"score\": 75,\n            \"metadata\": [\n                {\"name\": \"rule_count\", \"value\": \"2\"},\n                {\"name\": \"data_sources\", \"value\": \"Windows Security Log, Linux Auth\"},\n                {\"name\": \"last_validated\", \"value\": \"2025-01-15\"}\n            ]\n        },\n        {\n            \"techniqueID\": \"T1059.001\",\n            \"tactic\": \"execution\",\n            \"color\": \"#00ff00\",\n            \"comment\": \"3 rules - PowerShell Script Block Logging\",\n            \"score\": 85\n        },\n        {\n            \"techniqueID\": \"T1055\",\n            \"tactic\": \"defense-evasion\",\n            \"color\": \"#ff0000\",\n            \"comment\": \"NO DETECTION - Requires Sysmon EventCode 8\u002F10\",\n            \"score\": 0\n        }\n    ],\n    \"gradient\": {\n        \"colors\": [\"#ff0000\", \"#ffff00\", \"#00ff00\"],\n        \"minValue\": 0,\n        \"maxValue\": 100\n    }\n}\n```\n\n### Step 3: Score Each Technique\n\n| Score | Color | Meaning | Criteria |\n|---|---|---|---|\n| 0 | Red | No Detection | No rules, missing data sources |\n| 25 | Orange | Minimal | Rule exists but not validated\u002Ftested |\n| 50 | Yellow | Partial | Rule works but limited coverage |\n| 75 | Light Green | Good | Validated rule with good data sources |\n| 100 | Green | Excellent | Multiple validated rules, tested with emulation |\n\n### Scoring Criteria Detail\n\n```\nScore = Data_Source_Score (0-25) + Rule_Quality_Score (0-25) +\n        Validation_Score (0-25) + Enrichment_Score (0-25)\n\nData_Source_Score:\n  25: All required data sources ingested and parsed\n  15: Primary data source available\n  5:  Partial data source coverage\n  0:  Required data sources not available\n\nRule_Quality_Score:\n  25: Rule uses CIM-compliant queries with proper thresholds\n  15: Rule works but may generate false positives\n  5:  Basic rule with no tuning\n  0:  No detection rule\n\nValidation_Score:\n  25: Validated with adversary emulation (Atomic Red Team)\n  15: Tested with synthetic data\n  5:  Logic reviewed but not tested\n  0:  Not validated\n\nEnrichment_Score:\n  25: Context-rich with asset, identity, and TI enrichment\n  15: Basic enrichment (asset lookup)\n  5:  No enrichment\n  0:  N\u002FA (no rule)\n```\n\n### Step 4: Identify Priority Gaps\n\n#### Gap Prioritization Framework\n\n```\nPriority = Technique_Prevalence x Impact x Feasibility\n\nTechnique_Prevalence (0-10):\n  - Based on MITRE Top Techniques report\n  - Frequency in your industry's threat landscape\n  - Observed in recent incidents\u002Fbreaches\n\nImpact (0-10):\n  - Damage potential if technique succeeds\n  - Difficulty of recovery\n  - Data sensitivity at risk\n\nFeasibility (0-10):\n  - Data source availability\n  - Rule complexity\n  - Engineering effort required\n```\n\n#### Top Priority Techniques to Cover (2025)\n\n| Technique | ID | Prevalence | Typical Gap Reason |\n|---|---|---|---|\n| Command and Scripting Interpreter | T1059 | Very High | Requires script block logging |\n| Phishing | T1566 | Very High | Email gateway integration |\n| Valid Accounts | T1078 | High | Baseline behavior needed |\n| Process Injection | T1055 | High | Requires Sysmon or EDR |\n| Lateral Movement (RDP\u002FSMB) | T1021 | High | Network segmentation visibility |\n| Scheduled Task\u002FJob | T1053 | High | Event log collection |\n| Data Encrypted for Impact | T1486 | High | File system monitoring |\n| Ingress Tool Transfer | T1105 | Medium | Network traffic analysis |\n\n### Step 5: Build Detection Roadmap\n\n```\nQuarter 1: Close Critical Gaps (Score 0, High Prevalence)\n  Week 1-2: Enable missing data sources\n  Week 3-4: Build and test rules for top 5 gap techniques\n  Week 5-8: Validate with adversary emulation\n  Week 9-12: Tune and operationalize\n\nQuarter 2: Improve Partial Coverage (Score 25-50)\n  - Upgrade existing rules with enrichment\n  - Add secondary detection methods\n  - Validate with purple team exercises\n\nQuarter 3: Mature Good Coverage (Score 50-75)\n  - Add behavioral analytics\n  - Implement detection-as-code pipeline\n  - Cross-technique correlation rules\n\nQuarter 4: Excellence (Score 75-100)\n  - Continuous testing with BAS tools\n  - Automated coverage regression testing\n  - Red team validation\n```\n\n## Automated Coverage Assessment\n\n### Data Source to Technique Mapping\n\n```python\n# Map available data sources to detectable techniques\nDATA_SOURCE_TECHNIQUE_MAP = {\n    \"Windows Security Event Log\": [\n        \"T1110\", \"T1078\", \"T1053.005\", \"T1098\", \"T1136\",\n        \"T1070.001\", \"T1021.001\", \"T1543.003\"\n    ],\n    \"Sysmon\": [\n        \"T1055\", \"T1059\", \"T1003\", \"T1547.001\", \"T1036\",\n        \"T1218\", \"T1105\", \"T1071\"\n    ],\n    \"Network Traffic (Firewall\u002FIDS)\": [\n        \"T1071\", \"T1048\", \"T1105\", \"T1572\", \"T1090\",\n        \"T1571\", \"T1573\"\n    ],\n    \"DNS Logs\": [\n        \"T1071.004\", \"T1568\", \"T1583.001\", \"T1048.003\"\n    ],\n    \"Email Gateway\": [\n        \"T1566.001\", \"T1566.002\", \"T1534\"\n    ],\n    \"Cloud Audit Logs\": [\n        \"T1078.004\", \"T1537\", \"T1530\", \"T1580\",\n        \"T1087.004\", \"T1098.001\"\n    ],\n}\n```\n\n## Reporting Dashboard Queries\n\n### Coverage Summary by Tactic\n\n```spl\n| inputlookup mitre_coverage_lookup\n| stats avg(score) as avg_score count(eval(score=0)) as no_coverage\n    count(eval(score>0 AND score\u003C50)) as partial\n    count(eval(score>=50 AND score\u003C75)) as good\n    count(eval(score>=75)) as excellent\n    count as total\n    by tactic\n| eval coverage_pct=round((total - no_coverage) \u002F total * 100, 1)\n| sort -coverage_pct\n```\n\n## References\n\n- [CyberDefenders - MITRE ATT&CK for SOC & DFIR Analysts](https:\u002F\u002Fcyberdefenders.org\u002Fblog\u002Fmitre-attack-framework\u002F)\n- [MITRE ATT&CK Navigator](https:\u002F\u002Fmitre-attack.github.io\u002Fattack-navigator\u002F)\n- [CardinalOps - SIEM Detection Coverage Report 2025](https:\u002F\u002Fwww.helpnetsecurity.com\u002F2025\u002F06\u002F09\u002Fsiem-detection-coverage\u002F)\n- [Datadog - Cloud SIEM MITRE ATT&CK Map](https:\u002F\u002Fwww.datadoghq.com\u002Fblog\u002Fcloud-siem-mitre-attack-map\u002F)\n- [Picus Security - MITRE ATT&CK Framework Guide](https:\u002F\u002Fwww.picussecurity.com\u002Fmitre-attack-framework)\n",{"name":5,"tags":25,"author":32,"domain":33,"license":15,"version":34,"nist_csf":35,"subdomain":40,"description":7,"nist_ai_rmf":41,"mitre_attack":45,"atlas_techniques":50,"d3fend_techniques":54},[26,27,28,29,30,31],"mitre-attack","detection-coverage","gap-analysis","attack-navigator","soc","detection-engineering","mahipal","cybersecurity","1.0",[36,37,38,39],"DE.CM-01","DE.AE-02","RS.MA-01","DE.AE-06","soc-operations",[42,43,44],"MEASURE-2.7","MAP-5.1","MANAGE-2.4",[46,47,48,49],"T1078","T1685.002","T1685.005","T1566",[51,52,53],"AML.T0070","AML.T0066","AML.T0082",[55,56,57,58,59],"Token Binding","Restore Access","Application Protocol Command Analysis","Password Authentication","Reissue Credential","main","7540bbccf0c1ded6156a467b02c95b61ad62413f",".agents\u002Fskills\u002Fimplementing-mitre-attack-coverage-mapping","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena","Currently exploring the intersection of tech","2026-09-11 03:02:31",{"source":8,"skillName":5,"commands":68,"prompt":78,"zipAvailable":79},[69,72,75],{"tool":70,"command":71},"npx","npx skills add NeelakshSaxena\u002FVayu --skill implementing-mitre-attack-coverage-mapping",{"tool":73,"command":74},"bunx","bunx skills add NeelakshSaxena\u002FVayu --skill implementing-mitre-attack-coverage-mapping",{"tool":76,"command":77},"pnpm","pnpm dlx skills add NeelakshSaxena\u002FVayu --skill implementing-mitre-attack-coverage-mapping","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-mitre-attack-coverage-mapping\u002FSKILL.md",true,[81,87,91,97,101,105,111],{"path":82,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":85,"sourceHtmlUrl":86},"assets\u002Ftemplate.md","ASSET","资产文件",989,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-mitre-attack-coverage-mapping\u002Fassets\u002Ftemplate.md",{"path":88,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":90,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":92,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":95,"sourceHtmlUrl":96},"references\u002Fapi-reference.md","REFERENCE","参考文档",1446,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-mitre-attack-coverage-mapping\u002Freferences\u002Fapi-reference.md",{"path":98,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":99,"sourceHtmlUrl":100},"references\u002Fstandards.md",1164,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-mitre-attack-coverage-mapping\u002Freferences\u002Fstandards.md",{"path":102,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":103,"sourceHtmlUrl":104},"references\u002Fworkflows.md",977,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-mitre-attack-coverage-mapping\u002Freferences\u002Fworkflows.md",{"path":106,"resourceType":107,"resourceTypeDesc":108,"sizeBytes":109,"sourceHtmlUrl":110},"scripts\u002Fagent.py","SCRIPT","脚本",7004,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-mitre-attack-coverage-mapping\u002Fscripts\u002Fagent.py",{"path":112,"resourceType":107,"resourceTypeDesc":108,"sizeBytes":113,"sourceHtmlUrl":114},"scripts\u002Fprocess.py",9055,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-mitre-attack-coverage-mapping\u002Fscripts\u002Fprocess.py",[116,123,130,137,144,151],{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":20},"01M7ACCCVNCFKMA9X6D15X6G98","runpodctl","Runpod CLI for managing GPU\u002FCPU workloads from the terminal — pods, serverless endpoints, templates, network volumes, Hub deploys, models, SSH, and file transfer (send\u002Freceive). Use for terminal\u002FCI\u002Fscripting, Hub browse\u002Fdeploy, SSH setup, `doctor`, or when the Runpod MCP tools are not connected. For structured tool calls in an MCP-enabled session, prefer runpod-mcp.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpodctl\u002FSKILL.md",[],[],{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":20},"01M7ACC63SRHEA5KMCHSMZK2TC","runpod","Start here for any Runpod task — running GPU\u002FCPU pods, deploying serverless endpoints, templates, network volumes, building images, or understanding how Runpod works. Routes to the right skill (runpod-mcp, runpodctl, flash, companion-clis, runpod-usage, runpod-templates, runpod-migrate) and indexes two dozen live-verified end-to-end examples (golden paths) — use it when the lane is unclear, and for any multi-step or provisioning task even when it is not.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod\u002FSKILL.md",[],[],{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":20},"01M7ACC0Q1C89N9BZBV91CTQTF","runpod-usage","How Runpod works and how to work it — pods vs serverless, GPU\u002FVRAM selection, storage, building a container, networking, plus the agentic pod development loop (provision → ssh-exec → set up → poll readiness) and on-pod install hygiene (uv\u002Fapt). Use to answer \"how does X work\", \"which GPU\", \"how do I build a container\", or \"how do I stand up a workload on a pod\". Guidance, not a tool — execute with runpodctl, runpod-mcp, or flash.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-usage\u002FSKILL.md",[],[],{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":143,"publishedAt":20},"01M7ACBRPE345GF5GM5B8P8RRC","runpod-templates","Runpod's official prebuilt pod templates (ComfyUI, PyTorch, and others): what each image ships, which ports and paths it uses, how to pick one, how to pin a version, and what is missing on first boot. Use when a task says \"run \u003CX> on a pod\" and an official template already covers it, instead of building an image — and when a user needs help with or wants to fix something about a Runpod template they are already running (won't boot, can't reach the UI, missing models, wrong CUDA line, broken ComfyUI workflow metadata on imported workflows): start here and route onward. Deploy with runpodctl or runpod-mcp; end-to-end walkthroughs live in the runpod router's golden paths.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-templates\u002FSKILL.md",[],[],{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":150,"publishedAt":20},"01M7ACBJATHKVX1TWES2F44GY8","runpod-migrate","Migrate a codebase from the Runpod GraphQL API or REST v1 to REST v2 — inventory which parts use which API version, rewrite the call sites, flag breaking changes, and verify. Use when someone asks to move to v2, asks what v2 would change, or asks which Runpod API their code is on. For managing infrastructure rather than migrating code, use runpod-mcp or runpodctl.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-migrate\u002FSKILL.md",[],[],{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":157,"publishedAt":20},"01M7ACBC7GHVH6T9YEAPCG2AP8","runpod-mcp","Manage Runpod infrastructure — pods, serverless endpoints, jobs, templates, network volumes, container-registry auth, GPU\u002FCPU catalog, and billing — via the Runpod MCP server's structured tool calls. Use when the Runpod MCP tools (create-pod, list-endpoints, …) are connected in this session, or to connect them (hosted OAuth or local npx). Prefer this over runpodctl for plain infra CRUD when MCP is available; use runpodctl for the terminal, file transfer, or SSH setup.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-mcp\u002FSKILL.md",[],[]]