| name | kill-chain-analysis |
| description | Kill chain analysis and attack path decision-making โ findings analysis, attack vector selection, target prioritization, phase transitions. |
| allowed-tools | Read |
| metadata | {"subdomain":"orchestration","when_to_use":"analyze findings, select attack vector, prioritize targets, which technique, attack path, next attack, choose approach, alternative vector, blocked what next","tags":"kill-chain, decision-making, attack-path, target-prioritization, technique-selection","mitre_attack":"TA0043, TA0001, TA0002, TA0003, TA0004, TA0005, TA0006, TA0007, TA0008"} |
Kill Chain Analysis & Attack Path Decision-Making
Decision Framework
When selecting the next action, evaluate in order:
- What does the OPPLAN say? โ Prioritized objectives drive decisions
- What do findings tell us? โ Previous phase results constrain options
- What's the risk/reward? โ Lower noise approaches first
- What's the OPSEC impact? โ Consult
opsec skill before noisy actions
Findings Analysis
After Recon Phase โ Selecting Attack Vectors
Read recon/ outputs and categorize:
| Finding Type | Indicates | Next Action |
|---|
| Web apps with known CVEs | Web exploitation path | exploit โ web techniques |
| AD services (88/389/636) | AD attack surface | exploit โ AD techniques (after initial access) |
| Exposed credentials (OSINT) | Credential-based access | exploit โ credential stuffing/spray |
| Cloud misconfigs (S3/blob) | Cloud attack path | exploit โ cloud-specific techniques |
| VPN/remote access services | Network perimeter entry | exploit โ VPN/RDP exploitation |
| Employee emails + breach data | Social engineering path | exploit โ phishing (if in scope) |
Attack Vector Prioritization
Rank available vectors by:
Score = (Success Probability ร Impact) / Detection Risk
1. Valid credentials from OSINT โ High prob, High impact, Low noise
2. Known web CVE (public exploit) โ High prob, Med impact, Med noise
3. AD misconfiguration (no patch) โ Med prob, High impact, Med noise
4. Password spray against O365 โ Med prob, High impact, High noise
5. Zero-day or custom exploit โ Low prob, High impact, Low noise
Always prefer: credentials > misconfigurations > known CVEs > brute force
After Exploitation โ Deciding Post-Exploit Strategy
Once a foothold is established, analyze:
| Context | Decision |
|---|
| Low-privilege user on workstation | Prioritize: privesc โ cred dump โ lateral to server |
| Service account on server | Prioritize: cred dump (may have cached admin creds) โ lateral |
| Domain user credentials | Prioritize: AD enumeration โ Kerberoasting โ DCSync path |
| Local admin on single host | Prioritize: cred dump โ check for cached domain creds โ lateral |
| Already domain admin | Prioritize: objective completion โ evidence collection โ reporting |
Handling Blocked Objectives
Failure Analysis Decision Tree
Objective BLOCKED
โ
โโโ WHY did it fail?
โ โโโ Defense mechanism (WAF/EDR/IDS)
โ โ โ Consult defense-evasion skill โ retry with evasion
โ โ
โ โโโ Missing prerequisite (need creds/access/info)
โ โ โ Identify which prior phase provides it โ re-order objectives
โ โ
โ โโโ Target hardened / not vulnerable
โ โ โ Check findings for alternative target โ redirect attack
โ โ
โ โโโ Tool failure / environment issue
โ โ Retry with different tool or approach
โ
โโโ Is there an ALTERNATIVE path?
โ โโโ YES โ Craft new delegation with adjusted approach
โ โโโ NO โ Mark BLOCKED, document reason, proceed to next objective
โ
โโโ Should we REVISIT later?
โโโ YES (new intel may help) โ Keep status BLOCKED, note in lessons_learned.md
โโโ NO (dead end) โ Mark BLOCKED permanently
Common Pivots
| Original Approach | Alternative When Blocked |
|---|
| SQLi on web app | SSTI, deserialization, SSRF, or move to different web app |
| Kerberoasting | AS-REP roasting, ADCS abuse, password spray |
| LSASS dump blocked by EDR | nanodump, comsvcs.dll, MiniDumpWriteDump via syscall |
| WinRM blocked | PsExec, WMI, DCOM, RDP, SMB exec |
| Password spray lockout | Low-and-slow spray, single-password-multiple-users |
MITRE ATT&CK Phase Mapping
Use this to map OPPLAN objective phases to ATT&CK tactics:
| OPPLAN Phase | ATT&CK Tactic | Sub-Agent |
|---|
| Recon | TA0043 Reconnaissance | recon |
| Initial Access | TA0001 Initial Access | exploit |
| Execution | TA0002 Execution | exploit |
| Persistence | TA0003 Persistence | postexploit |
| Privilege Escalation | TA0004 Privilege Escalation | postexploit |
| Defense Evasion | TA0005 Defense Evasion | exploit / postexploit |
| Credential Access | TA0006 Credential Access | postexploit |
| Discovery | TA0007 Discovery | recon / postexploit |
| Lateral Movement | TA0008 Lateral Movement | postexploit |
| Collection | TA0009 Collection | postexploit |
| Exfiltration | TA0010 Exfiltration | postexploit |
Target Prioritization
When multiple targets are available, prioritize:
- Crown jewels โ Targets explicitly named in OPPLAN objectives
- Domain controllers โ Access = domain-wide compromise
- File servers โ Likely contain sensitive data for objectives
- Admin workstations โ Cached credentials for further access
- Application servers โ May contain database credentials, API keys
- Standard workstations โ Lower value, but may provide stepping stones