Interview question
An intrusion started with valid credentials against an internet-facing VPN, with no malware involved until well after initial access. How well does the Cyber Kill Chain describe this, and what would you use instead?
A question designed to see whether you can criticise a framework you are expected to know. Identity-based intrusions are exactly where the kill chain fails.
What a strong answer covers
- Recognises that weaponisation, delivery and exploitation are effectively absent or degenerate in this intrusion.
- Notes the kill chain's malware-centric and perimeter-shaped assumptions.
- Notes its linearity — real intrusions loop, and internal movement starts fresh chains.
- Notes that Actions on Objectives compresses everything post-compromise into one phase.
- Suggests ATT&CK as the better fit, because T1078 Valid Accounts and the post-compromise tactics describe this properly.
- May reference the Unified Kill Chain or a simple timeline as alternatives.
- Still finds the kill chain useful for communicating coverage to non-specialists.
- Connects the model choice to a practical consequence — where detection should be focused.
Expert answer
It describes it badly, and this is one of the clearest cases where the model's assumptions show.
Three of the seven phases essentially do not occur. There is no weaponisation, because no payload was paired with an exploit. Delivery is degenerate — the credential was simply used. Exploitation did not happen in the sense the model means, because nothing was exploited; a legitimate authentication succeeded. So the model's early phases, which is where it does most of its work, have nothing to describe.
That reflects two assumptions baked into a 2011 model. It is malware-centric, and it is perimeter-shaped — it assumes an outside-in intrusion with a payload crossing a boundary. Identity-based intrusions break both, and they are now a large share of real activity. It is also linear, whereas this kind of intrusion loops: the actor lands, discovers, moves laterally, and effectively starts a fresh chain internally. And everything interesting here — discovery, lateral movement, collection, exfiltration — collapses into the single Actions on Objectives phase.
ATT&CK fits much better. Initial access is T1078 Valid Accounts, and the post-compromise tactics give proper granularity for discovery, lateral movement, credential access and the rest, so I can describe what actually happened rather than forcing it into phases that do not apply. If I wanted a phase model I would reach for the Unified Kill Chain, which extends the post-compromise portion, or just build a timeline, which is often the honest answer.
I would still keep the kill chain for one purpose: talking to leadership about where controls sit. "We have good coverage at delivery and command and control and almost none at initial access via identity" is a sentence a non-specialist can act on. The practical consequence of this intrusion is exactly that — the detection investment belongs in identity and authentication anomaly work, not in payload inspection at the perimeter.
Mistakes that cost candidates points
- Forcing the intrusion into all seven phases rather than noting which do not apply.
- Defending the kill chain uncritically because it is a well-known model.
- Rejecting it entirely without acknowledging what it still does well.
- Not proposing a concrete alternative.
- Missing the practical consequence for where detection effort should go.
You have read the answer, which is the easy part. Answer it in your own words and get graded against this same rubric, with the follow-up probe an interviewer would ask next.
Go deeper
Related questions
- How do the Diamond Model, the Cyber Kill Chain and MITRE ATT&CK relate to each other? Do they compete?
- An endpoint alert shows that a scheduled task was created which launches a PowerShell one-liner from a user's AppData directory. Map this to MITRE ATT&CK.
- You have one piece of evidence: a single IP address that a compromised host was beaconing to. Walk me through how you would develop this.
- Your CISO says "I want to know about ransomware." Turn that into something you can actually collect against.
- What is F3EAD, and why do some CTI teams prefer it to the traditional intelligence cycle?