网络安全 Analyzing Cyber Kill Chain

Analyzing Cyber Kill Chain：网络安全 skill: analyzing-cyber-kill-chain，适用于安全分析、取证与威胁排查场景。

Skill Documentation

网络安全 Analyzing Cyber Kill Chain

摘要

Analyzing Cyber Kill Chain：网络安全 skill: analyzing-cyber-kill-chain，适用于安全分析、取证与威胁排查场景。

> 来源: mukul975/Anthropic-Cybersecurity-Skills (18k stars) — 网络安全专业技能集

> 原文件: skills/analyzing-cyber-kill-chain/SKILL.md

> 模型推荐: claude-opus-4-7 (安全分析深度推理)

这个 skill 是干嘛的

mukul975 整理的 100+ 个网络安全专业 skill,覆盖渗透测试 / 取证 / 威胁情报 / 合规审计 / 云安全 / 移动安全 等领域。每个 skill 对应一个具体的安全分析任务。

michael 强调"skill 要有相应的指导功能,指导用户使用",所以加了下面两节让 Agent 和用户对接。

---

🤖 Agent 使用说明

1. 用户提到"分析 X 日志 / 取证 / 检测威胁 / 渗透测试 / 安全审计"时,触发对应 skill

2. skill 会按操作步骤一步步执行(取证镜像 / 解析日志 / 跑威胁情报 / etc.)

3. 涉及破坏性操作(rm/drop/format)前必须 ask user 确认

4. 完工后让 Agent 跑自检 step

5. 如果用户要求做"防御性分析" — 区分恶意代码审计 vs 渗透测试

👤 用户需要做什么?

1. 告诉 Agent 你要做什么(分析日志 / 取证 / 安全审计 / 渗透测试)

2. 如果需要提供文件/镜像/日志/哈希,按 Agent 提示提供

3. 涉及破坏性操作时明确告诉 Agent"继续"或"取消"

4. 全程 Agent 自动化,你只需提供数据 + 回答决策点

---

原 skill 内容(mukul975/Anthropic-Cybersecurity-Skills/skills/analyzing-cyber-kill-chain/SKILL.md,截断到 12k chars)

---

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.

'

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

---

Analyzing Cyber Kill Chain

When to Use

Use this skill when:

• Conducting post-incident analysis to determine how far an adversary progressed through an attack sequence
• Designing layered defensive controls with the goal of interrupting attacks at the earliest possible phase
• Producing threat intelligence reports that communicate attack progression to non-technical stakeholders

**Do not use** this skill as a standalone framework — combine with MITRE ATT&CK for technique-level granularity beyond what the 7-phase kill chain provides.

Prerequisites

• Complete incident timeline with forensic artifacts mapped to specific adversary actions
• MITRE ATT&CK Enterprise matrix for technique-level mapping within each kill chain phase
• Access to threat intelligence on the suspected adversary group's typical kill chain progression
• Post-incident report or IR timeline from responding team

Workflow

Step 1: Map Observed Actions to Kill Chain Phases

The Lockheed Martin Cyber Kill Chain consists of seven phases. Map all observed adversary actions:

**Phase 1 - Reconnaissance**: Adversary gathers target information before attack.

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

**Phase 2 - Weaponization**: Adversary creates attack tool (malware + exploit).

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

**Phase 3 - Delivery**: Adversary transmits weapon to target.

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

**Phase 4 - Exploitation**: Adversary exploits vulnerability to execute code.

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

**Phase 5 - Installation**: Adversary establishes persistence on target.

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

**Phase 6 - Command & Control (C2)**: Adversary communicates with compromised system.

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

**Phase 7 - Actions on Objectives**: Adversary achieves goals.

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

Step 2: Identify Phase Completion and Detection Points

Create a phase matrix for the incident:

Phase 1: Recon        → Completed (undetected)
Phase 2: Weaponize    → Completed (undetected — pre-attack)
Phase 3: Delivery     → Completed; phishing email bypassed SEG
Phase 4: Exploit      → Completed; CVE-2023-23397 exploited
Phase 5: Install      → DETECTED: EDR flagged scheduled task creation (attack stalled here)
Phase 6: C2           → Not achieved (installation blocked)
Phase 7: Objectives   → Not achieved

For each phase completed without detection, document the defensive control gap.

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

Each kill chain phase maps to multiple ATT&CK tactics:

• Delivery → Initial Access (TA0001)
• Exploitation → Execution (TA0002)
• Installation → Persistence (TA0003), Privilege Escalation (TA0004)
• C2 → Command and Control (TA0011)
• Actions on Objectives → Exfiltration (TA0010), Impact (TA0040)

Within each phase, enumerate specific ATT&CK techniques observed and map to existing detections.

Step 4: Identify Courses of Action per Phase

For each phase, document applicable defensive courses of action (COAs):

• **Detect COA**: What detection would alert on adversary activity in this phase?
• **Deny COA**: What control would prevent the adversary from completing this phase?
• **Disrupt COA**: What control would interrupt the adversary mid-phase?
• **Degrade COA**: What control would reduce the adversary's effectiveness in this phase?
• **Deceive COA**: What deception (honeypots, canary tokens) would expose activity in this phase?
• **Destroy COA**: What active defense capability would neutralize adversary infrastructure?

Step 5: Produce Kill Chain Analysis Report

Structure findings as:

1. Attack narrative (timeline of phases)

2. Phase-by-phase analysis with evidence

3. Detection point analysis (what worked, what failed)

4. Defensive recommendation per phase prioritized by cost/effectiveness

5. Control improvement roadmap

Key Concepts

| Term | Definition |

|------|-----------|

| **Kill Chain** | Sequential model of adversary intrusion phases; breaking any link theoretically stops the attack |

| **Courses of Action (COA)** | Defensive responses mapped to each kill chain phase: detect, deny, disrupt, degrade, deceive, destroy |

| **Beaconing** | Regular, periodic C2 check-in pattern from compromised host to adversary server; detectable by frequency analysis |

| **Phase Completion** | Adversary successfully finishes a kill chain phase and progresses to the next; defense-in-depth aims to prevent this |

| **Intelligence Gain/Loss** | Analysis of whether detecting at Phase 5 (vs. Phase 3) reduced intelligence about adversary capabilities or intent |

Tools & Systems

• **MITRE ATT&CK Navigator**: Overlay kill chain phases with ATT&CK technique coverage for integrated analysis
• **Elastic Security EQL**: Event Query Language for querying multi-phase attack sequences in Elastic SIEM
• **Splunk ES**: Timeline visualization and correlation searches for kill chain phase sequencing
• **MISP**: Kill chain tagging via galaxy clusters for structured incident event documentation

Common Pitfalls

• **Linear assumption**: Adversaries don't always progress linearly — they may skip phases (weaponization already complete from previous campaign) or loop back (re-establish C2 after detection).
• **Ignoring Phases 1 and 2**: Reconnaissance and weaponization occur before the defender has visibility. Intelligence about these phases requires external sources (OSINT, threat intelligence).
• **Missing insider threats**: The kill chain was designed for external adversaries. Insider threats may skip directly to Phase 7 without traversing earlier phases.
• **Confusing with ATT&CK tactics**: The 7-phase kill chain and 14 ATT&CK tactics are complementary but not directly equivalent. Maintain distinction to prevent analytic confusion.

常见问题（FAQ）

使用「Analyzing Cybe」这个 skill 能解决什么问题?

本 skill 专注于Analyzing Cybe，网络安全 skill: analyzing-cyber-kill-chain。它将相关流程标准化，帮助用户更快拿到可靠结果，减少重复手工操作。

什么情况下适合使用「Analyzing Cybe」?

当你需要在Analyzing Cyber Kill Chain相关工作中获得稳定、可复用的产出时最适合——无论是单次任务还是纳入日常工作流，都能直接调用。

使用「Analyzing Cybe」前需要准备什么?

需要明确授权范围内的目标系统或样本文件，并准备隔离的分析环境（虚拟机/沙箱）。