Back to catalog
Static reviewDevelopment

Skill dossier

mapping-mitre-attack-techniques

Source declaration

Maps observed adversary behaviors, security alerts, and detection rules to MITRE ATT&CK techniques and sub-techniques to quantify detection coverage and guide control prioritization. Use when building an ATT&CK-based coverage heatmap, tagging SIEM alerts with technique IDs, aligning security controls to adversary playbooks, or reporting threat exposure to executives. Activates for requests involving ATT&CK Navigator, Sigma rules, MITRE D3FEND, or coverage gap analysis.

The author's original description, preserved in English. It describes intent, not verified performance.

Maps observed adversary behaviors, security alerts, and detection rules to MITRE ATT&CK techniques and sub-techniques to quantify detection coverage and guide control prioritization. Use when building an ATT&CK-based coverage heatmap, tagging SIEM alerts with technique IDs, aligning security controls to adversary playbooks, or reporting threat exposure to executives. Activates for requests involving ATT&CK Navigator, Sigma rules, MITRE D3FEND, or coverage gap analysis.

developmentreferencesscripts

Research summary

Machine-generated analysis; pending human review

These observations come from deterministic source parsing, not a human security review or controlled task evaluation.

Maps observed adversary behaviors, security alerts, and detection rules to MITRE ATT&CK techniques and sub-techniques to quantify detection coverage and guide control prioritization. Use when building an ATT&CK-based coverage heatmap, tagging SIEM alerts with technique IDs, aligning security controls to adversary playbooks, or reporting threat exposure to executives. Activates for requests involving ATT&CK Navigator, Sigma rules, MITRE D3FEND, or coverage gap analysis. This bilingual summary is generated deterministically from collected source text and file structure; it is pending human editorial review.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Workflow [Source statement; provisional, not tested. Evidence: skills/mapping-mitre-attack-techniques/SKILL.md:L68]
  • Step 1: Obtain Current ATT&CK Data [Source statement; provisional, not tested. Evidence: skills/mapping-mitre-attack-techniques/SKILL.md:L70]
  • Step 2: Map Existing Detections to Techniques [Source statement; provisional, not tested. Evidence: skills/mapping-mitre-attack-techniques/SKILL.md:L88]
  • Step 3: Prioritize Coverage Gaps Using Threat Intelligence [Source statement; provisional, not tested. Evidence: skills/mapping-mitre-attack-techniques/SKILL.md:L100]
  • Step 4: Build Navigator Heatmap [Source statement; provisional, not tested. Evidence: skills/mapping-mitre-attack-techniques/SKILL.md:L113]
  • Step 5: Generate Executive Coverage Report [Source statement; provisional, not tested. Evidence: skills/mapping-mitre-attack-techniques/SKILL.md:L136]

Limitations & scope

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Relevant for

  • Practitioners evaluating whether to inspect and install the source skill; this audience is inferred from the product context, not measured usage. [Evidence: skills/mapping-mitre-attack-techniques/SKILL.md:L1-L49]

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
4
Markdown files
2
scripts
1
references
1
Size
28.3 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/mapping-mitre-attack-techniques/LICENSEOther11 KB
skills/mapping-mitre-attack-techniques/references/api-reference.mdReference2.6 KB
skills/mapping-mitre-attack-techniques/scripts/agent.pyScript7.6 KB
skills/mapping-mitre-attack-techniques/SKILL.mdInstruction7.1 KB

SKILL.md frontmatter

{
  "name": "mapping-mitre-attack-techniques",
  "description": "Maps observed adversary behaviors, security alerts, and detection rules to MITRE ATT&CK techniques and sub-techniques to quantify detection coverage and guide control prioritization. Use when building an ATT&CK-based coverage heatmap, tagging SIEM alerts with technique IDs, aligning security controls to adversary playbooks, or reporting threat exposure to executives. Activates for requests involving ATT&CK Navigator, Sigma rules, MITRE D3FEND, or coverage gap analysis.\n",
  "domain": "cybersecurity",
  "subdomain": "threat-intelligence",
  "tags": [
    "MITRE-ATT&CK",
    "ATT&CK-Navigator",
    "Sigma",
    "D3FEND",
    "TTP",
    "detection-engineering",
    "NIST-CSF"
  ],
  "version": "1.0.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "nist_ai_rmf": [
    "MEASURE-2.7",
    "MAP-5.1",
    "MANAGE-2.4"
  ],
  "atlas_techniques": [
    "AML.T0070",
    "AML.T0066",
    "AML.T0082"
  ],
  "d3fend_techniques": [
    "Executable Denylisting",
    "Execution Isolation",
    "File Metadata Consistency Validation",
    "Content Format Conversion",
    "File Content Analysis"
  ],
  "nist_csf": [
    "ID.RA-01",
    "ID.RA-05",
    "DE.CM-01",
    "DE.AE-02"
  ],
  "mitre_attack": [
    "T1591",
    "T1592",
    "T1593",
    "T1589",
    "T1685.002"
  ]
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Decision

    When to Use

    Source-described decision candidate under “When to Use”; not verified execution.

  2. 02
    Action

    Workflow

    Source-described action candidate under “Workflow”; not verified execution.

  3. 03
    Action

    Step 1: Obtain Current ATT&CK Data

    Source-described action candidate under “Step 1: Obtain Current ATT&CK Data”; not verified execution.

  4. 04
    Action

    Use the mitreattack-python library to query techniques programmatically:

    Source-described action candidate under “Step 1: Obtain Current ATT&CK Data”; not verified execution.

  5. 05
    Action

    Step 2: Map Existing Detections to Techniques

    Source-described action candidate under “Step 2: Map Existing Detections to Techniques”; not verified execution.

  6. 06
    Input

    Create a coverage matrix: list each technique ID and mark as: Detected (alert fires), Logged (data present but no alert), Blind (no data source).

    Source-described input candidate under “Step 2: Map Existing Detections to Techniques”; not verified execution.

Inspect all extracted workflow candidates (14 candidate steps)
  1. 07
    Action

    Step 3: Prioritize Coverage Gaps Using Threat Intelligence

    Source-described action candidate under “Step 3: Prioritize Coverage Gaps Using Threat Intelligence”; not verified execution.

  2. 08
    Action

    Step 4: Build Navigator Heatmap

    Source-described action candidate under “Step 4: Build Navigator Heatmap”; not verified execution.

  3. 09
    Output

    Export coverage scores as ATT&CK Navigator JSON layer:

    Source-described output candidate under “Step 4: Build Navigator Heatmap”; not verified execution.

  4. 10
    Input

    Import layer into ATT&CK Navigator (https://mitre-attack.github.io/attack-navigator/) for visualization.

    Source-described input candidate under “Step 4: Build Navigator Heatmap”; not verified execution.

  5. 11
    Output

    Step 5: Generate Executive Coverage Report

    Source-described output candidate under “Step 5: Generate Executive Coverage Report”; not verified execution.

  6. 12
    Action

    Key Concepts

    Source-described action candidate under “Key Concepts”; not verified execution.

  7. 13
    Action

    Tools & Systems

    Source-described action candidate under “Tools & Systems”; not verified execution.

  8. 14
    Action

    Common Pitfalls

    Source-described action candidate under “Common Pitfalls”; not verified execution.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Items warrant review

25 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useNot observed
Medium

Network access is mentioned

11 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 11 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

14 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 14 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
Inspect the pinned source at https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/mapping-mitre-attack-techniques/SKILL.md and follow the source repository's installation instructions. No installation was performed or verified by this static analyzer. Source license: Apache-2.0.

Prerequisites

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Example prompts

Not provided

A decision, with its limits attached

Strengths

  • The snapshot contains 4 collected file(s), 2 Markdown file(s), and 1 script file(s), enabling source-level inspection. [Evidence: skills/mapping-mitre-attack-techniques/SKILL.md:L1]

Considerations

  • No functional, security, or model-quality result has been established. Human review must inspect source context and all cited findings before installation or publication.
Research conclusion

Provisional deterministic static inventory only; pending human editorial review and, separately, controlled evaluation. No install recommendation, security assurance, or effectiveness claim is made.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

mukul975Anthropic-Cybersecurity-Skillsskills/mapping-mitre-attack-techniques
Source type
Community
Commit
54a798831d2266a3ca61ce68a7acb80b81160d57
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
Apache-2.0
Repository stars
36,446
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.