Back to catalog
Static reviewDevelopment

Skill dossier

analyzing-cyber-kill-chain

Source declaration

Analyzes intrusion activity against the Lockheed Martin Cyber Kill Chain framework to identify which phases an adversary has completed, where defenses succeeded or failed, and what controls would have interrupted the attack at earlier phases. Use when conducting post-incident analysis, building prevention-focused security controls, or mapping detection gaps to kill chain phases. Activates for requests involving kill chain analysis, intrusion kill chain, attack phase mapping, or Lockheed Martin kill chain framework.

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

Analyzes intrusion activity against the Lockheed Martin Cyber Kill Chain framework to identify which phases an adversary has completed, where defenses succeeded or failed, and what controls would have interrupted the attack at earlier phases. Use when conducting post-incident analysis, building prevention-focused security controls, or mapping detection gaps to kill chain phases. Activates for requests involving kill chain analysis, intrusion kill chain, attack phase mapping, or Lockheed Martin kill chain framework.

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.

Analyzes intrusion activity against the Lockheed Martin Cyber Kill Chain framework to identify which phases an adversary has completed, where defenses succeeded or failed, and what controls would have interrupted the attack at earlier phases. Use when conducting post-incident analysis, building prevention-focused security controls, or mapping detection gaps to kill chain phases. Activates for requests involving kill chain analysis, intrusion kill chain, attack phase mapping, or Lockheed Martin kill chain framework. 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/analyzing-cyber-kill-chain/SKILL.md:L54]
  • Step 1: Map Observed Actions to Kill Chain Phases [Source statement; provisional, not tested. Evidence: skills/analyzing-cyber-kill-chain/SKILL.md:L56]
  • Step 2: Identify Phase Completion and Detection Points [Source statement; provisional, not tested. Evidence: skills/analyzing-cyber-kill-chain/SKILL.md:L81]
  • Step 3: Map to MITRE ATT&CK for Technique Detail [Source statement; provisional, not tested. Evidence: skills/analyzing-cyber-kill-chain/SKILL.md:L96]
  • Step 4: Identify Courses of Action per Phase [Source statement; provisional, not tested. Evidence: skills/analyzing-cyber-kill-chain/SKILL.md:L107]
  • Step 5: Produce Kill Chain Analysis Report [Source statement; provisional, not tested. Evidence: skills/analyzing-cyber-kill-chain/SKILL.md:L117]

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/analyzing-cyber-kill-chain/SKILL.md:L1-L35]

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
31 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/analyzing-cyber-kill-chain/LICENSEOther11 KB
skills/analyzing-cyber-kill-chain/references/api-reference.mdReference2.7 KB
skills/analyzing-cyber-kill-chain/scripts/agent.pyScript10.2 KB
skills/analyzing-cyber-kill-chain/SKILL.mdInstruction7.1 KB

SKILL.md frontmatter

{
  "name": "analyzing-cyber-kill-chain",
  "description": "Analyzes intrusion activity against the Lockheed Martin Cyber Kill Chain framework to identify which phases an adversary has completed, where defenses succeeded or failed, and what controls would have interrupted the attack at earlier phases. Use when conducting post-incident analysis, building prevention-focused security controls, or mapping detection gaps to kill chain phases. Activates for requests involving kill chain analysis, intrusion kill chain, attack phase mapping, or Lockheed Martin kill chain framework.\n",
  "domain": "cybersecurity",
  "subdomain": "threat-intelligence",
  "tags": [
    "kill-chain",
    "Lockheed-Martin",
    "MITRE-ATT&CK",
    "intrusion-analysis",
    "defense-in-depth",
    "NIST-CSF"
  ],
  "version": "1.0.0",
  "author": "team-cybersecurity",
  "license": "Apache-2.0",
  "nist_csf": [
    "ID.RA-01",
    "ID.RA-05",
    "DE.CM-01",
    "DE.AE-02"
  ],
  "mitre_attack": [
    "T1566.001",
    "T1190",
    "T1547.001",
    "T1071.001",
    "T1486"
  ]
}

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: Map Observed Actions to Kill Chain Phases

    Source-described action candidate under “Step 1: Map Observed Actions to Kill Chain Phases”; not verified execution.

  4. 04
    Action

    Indicators: DNS queries from adversary IP, LinkedIn scraping, job posting analysis, Shodan scans of organization infrastructure

    Source-described action candidate under “Step 1: Map Observed Actions to Kill Chain Phases”; not verified execution.

  5. 05
    Action

    Indicators: Malware compilation timestamps, exploit document metadata, builder artifacts in malware samples

    Source-described action candidate under “Step 1: Map Observed Actions to Kill Chain Phases”; not verified execution.

  6. 06
    Action

    Indicators: Phishing emails, malicious attachments, drive-by downloads, USB drops, supply chain compromise

    Source-described action candidate under “Step 1: Map Observed Actions to Kill Chain Phases”; not verified execution.

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

    Indicators: CVE exploitation events in application/OS logs, memory corruption artifacts, shellcode execution

    Source-described action candidate under “Step 1: Map Observed Actions to Kill Chain Phases”; not verified execution.

  2. 08
    Action

    Indicators: New scheduled tasks, registry run keys, service installation, web shells, bootkits

    Source-described action candidate under “Step 1: Map Observed Actions to Kill Chain Phases”; not verified execution.

  3. 09
    Action

    Indicators: Beaconing traffic (regular intervals), DNS tunneling, HTTPS to uncommon domains, C2 framework signatures (Cobalt Strike, Sliver)

    Source-described action candidate under “Step 1: Map Observed Actions to Kill Chain Phases”; not verified execution.

  4. 10
    Action

    Indicators: Data staging/exfiltration, lateral movement, ransomware execution, destructive activity

    Source-described action candidate under “Step 1: Map Observed Actions to Kill Chain Phases”; not verified execution.

  5. 11
    Action

    Step 2: Identify Phase Completion and Detection Points

    Source-described action candidate under “Step 2: Identify Phase Completion and Detection Points”; not verified execution.

  6. 12
    Action

    Create a phase matrix for the incident:

    Source-described action candidate under “Step 2: Identify Phase Completion and Detection Points”; not verified execution.

  7. 13
    Action

    Step 3: Map to MITRE ATT&CK for Technique Detail

    Source-described action candidate under “Step 3: Map to MITRE ATT&CK for Technique Detail”; not verified execution.

  8. 14
    Action

    Delivery → Initial Access (TA0001)

    Source-described action candidate under “Step 3: Map to MITRE ATT&CK for Technique Detail”; not verified execution.

  9. 15
    Action

    Exploitation → Execution (TA0002)

    Source-described action candidate under “Step 3: Map to MITRE ATT&CK for Technique Detail”; not verified execution.

  10. 16
    Action

    Installation → Persistence (TA0003), Privilege Escalation (TA0004)

    Source-described action candidate under “Step 3: Map to MITRE ATT&CK for Technique Detail”; not verified execution.

  11. 17
    Action

    C2 → Command and Control (TA0011)

    Source-described action candidate under “Step 3: Map to MITRE ATT&CK for Technique Detail”; not verified execution.

  12. 18
    Action

    Actions on Objectives → Exfiltration (TA0010), Impact (TA0040)

    Source-described action candidate under “Step 3: Map to MITRE ATT&CK for Technique Detail”; not verified execution.

  13. 19
    Action

    Step 4: Identify Courses of Action per Phase

    Source-described action candidate under “Step 4: Identify Courses of Action per Phase”; not verified execution.

  14. 20
    Action

    Detect COA: What detection would alert on adversary activity in this phase?

    Source-described action candidate under “Step 4: Identify Courses of Action per Phase”; not verified execution.

  15. 21
    Action

    Deny COA: What control would prevent the adversary from completing this phase?

    Source-described action candidate under “Step 4: Identify Courses of Action per Phase”; not verified execution.

  16. 22
    Action

    Disrupt COA: What control would interrupt the adversary mid-phase?

    Source-described action candidate under “Step 4: Identify Courses of Action per Phase”; not verified execution.

  17. 23
    Action

    Degrade COA: What control would reduce the adversary's effectiveness in this phase?

    Source-described action candidate under “Step 4: Identify Courses of Action per Phase”; not verified execution.

  18. 24
    Action

    Deceive COA: What deception (honeypots, canary tokens) would expose activity in this phase?

    Source-described action candidate under “Step 4: Identify Courses of Action per Phase”; not verified execution.

  19. 25
    Action

    Destroy COA: What active defense capability would neutralize adversary infrastructure?

    Source-described action candidate under “Step 4: Identify Courses of Action per Phase”; not verified execution.

  20. 26
    Output

    Step 5: Produce Kill Chain Analysis Report

    Source-described output candidate under “Step 5: Produce Kill Chain Analysis Report”; not verified execution.

  21. 27
    Action

    Attack narrative (timeline of phases)

    Source-described action candidate under “Step 5: Produce Kill Chain Analysis Report”; not verified execution.

  22. 28
    Action

    Phase-by-phase analysis with evidence

    Source-described action candidate under “Step 5: Produce Kill Chain Analysis Report”; not verified execution.

  23. 29
    Action

    Detection point analysis (what worked, what failed)

    Source-described action candidate under “Step 5: Produce Kill Chain Analysis Report”; not verified execution.

  24. 30
    Action

    Defensive recommendation per phase prioritized by cost/effectiveness

    Source-described action candidate under “Step 5: Produce Kill Chain Analysis Report”; not verified execution.

  25. 31
    Action

    Control improvement roadmap

    Source-described action candidate under “Step 5: Produce Kill Chain Analysis Report”; not verified execution.

  26. 32
    Action

    Key Concepts

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

  27. 33
    Action

    Tools & Systems

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

  28. 34
    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

6 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

4 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 4 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

2 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 2 location(s) in the collected text; 2 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/analyzing-cyber-kill-chain/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/analyzing-cyber-kill-chain/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/analyzing-cyber-kill-chain
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.