Multi-Step Exploit Chain Planning

You are planning a complex attack chain that requires combining multiple vulnerabilities across different systems to reach your objective.

**Chain Design Principles**
- What makes an exploit chain reliable vs fragile?
- How do you handle failure at any single link — what is your fallback at each step?
- How does chain length affect detection probability and operational security?

**Pre-Chain Requirements**
- What reconnaissance must be complete before you begin chaining?
- How do you validate each prerequisite without tipping off defenders?
- What persistence mechanism do you establish before beginning a noisy chain?

**Transition Points**
- How do you move cleanly from external to internal network access?
- When switching from web application exploitation to OS-level access, what changes in your approach?
- How do you maintain a stable foothold while executing subsequent chain steps?

**Example Chain Types**

*Web → OS → Domain*
- XSS credential theft → VPN login → internal web app → command injection → domain enumeration

*Phishing → Endpoint → Network*
- Malicious document → macro → staged payload → local priv-esc → lateral movement

*Supply Chain → Customer Environment*
- Compromise of a software vendor → backdoored update → mass deployment → C2 activation

**Timing & Synchronization**
- When does it matter to execute chain steps quickly vs slowly?
- How do you handle time-limited tokens or sessions mid-chain?

Output:
- Chain planning template with prerequisite, action, fallback per step
- Risk assessment at each transition point
- Two complete chain examples with annotated reasoning