Most security teams are stuck telling half the story. They can tell you when it happened (Timeline) and how it happened (Technique), but they struggle to articulate why the system failed in a way that maps directly to strategic risk. It is time to synthesize.
The Fragmentation Problem
We operate in a fragmented landscape. The Cyber Kill Chain (CKC) gives us phases. MITRE ATT&CK gives us an encyclopedia of techniques. But neither explicitly categorizes the Generic Vulnerability—the root cause—that allowed the breach.
Without a root cause taxonomy, we cannot build effective metrics. You cannot measure "Phishing" (a technique) against "Firewall" (a control) effectively. You need to measure the threat cluster #9 Social Engineering against the Human asset.
We do not need to choose one framework. We need to stack them.
- CKC anchors the sequence (The Timeline).
- ATT&CK provides the granular detail (The Technique).
- TLCTC defines the root cause (The Driver).
The Kill Chain layer of this stack as a film: one phase holds several causes, one cause turns up in several phases. Embedded on top of The Kill Chain Fallacy.
The Tri-Layer Mental Model
Imagine every incident mapping to three distinct layers. This provides the "Rosetta Stone" for communicating with Analysts (How), Managers (When), and the Board (Why).
TLCTC is the core because it is cause-oriented. Outcomes (like "Data Loss" or "Ransomware") are effects, not threats (Axiom III). By driving with TLCTC, we ensure every step leads back to a generic vulnerability (#1-#10) that we can actually manage.
Mapping the Layers: A Cheatsheet
Here is how the layers align. Notice how multiple ATT&CK techniques often roll up into a single TLCTC cause — and how one CKC phase holds several causes. Technique verdicts follow the ATT&CK Enterprise → TLCTC mapping.
| CKC Phase | Typical ATT&CK Tactic | TLCTC Cluster (Cause) |
|---|---|---|
| Reconnaissance | Reconnaissance |
No step (reading public information)
#1 Abuse of Functions (active probing)
#9 Social Engineering (eliciting from your people)
|
| Weaponization | Resource Development |
No step (attacker's own infrastructure: a threat-intelligence topic)
|
| Delivery | Initial Access |
#9 Social Engineering (Phishing, T1566)
#8 Physical Attack (Hardware Additions, T1200)
#10 Supply Chain Attack (Supply Chain Compromise, T1195)
|
| Exploitation | Initial Access / Execution |
#2 Exploiting Server (Exploit Public-Facing Application, T1190)
#3 Exploiting Client (Exploitation for Client Execution, T1203)
No step when a user runs the file:
#9 → #7 (T1204)
|
| Installation | Execution / Persistence |
#7 Malware (foreign code runs, recorded at every execution moment)
#1 → #7 (Scheduled Task, T1053)
|
| Command & Control | Command and Control |
No new step: the beacon is a capability of the running #7 (T1071)
#1 Abuse of Functions (relay via a legitimate Web Service, T1102)
|
| Actions on Obj. | Lateral Movement / Exfiltration / Impact |
#4 Identity Theft (Valid Accounts, T1078)
#1 → #7 (Software Deployment Tools, T1072)
#7 Malware +
[DRE: Ac] (Data Encrypted for Impact, T1486)
#6 Flooding Attack + [DRE: Av] (Network/Endpoint DoS, T1498/T1499)
Exfiltration is an outcome: [DRE: C] on the step that caused it
|
Real-World Application: The Attack Path
Let’s look at a standard Phishing-led Ransomware attack. Using the synthesis, we can describe it with precision.
The Narrative
- CKC: Delivery → Exploitation → Installation → Actions on Objectives
- ATT&CK: T1566.001 (Spearphishing Attachment) → T1204.002 (Malicious File) → T1053.005 (Scheduled Task) → T1078 (Valid Accounts) → T1072 (Software Deployment Tools) → T1486 (Data Encrypted for Impact)
- TLCTC Analysis:
- The phish persuaded a user to open the attachment and enable its macro (#9) — crossing from the external sphere into the organization.
- The macro launched a loader: foreign code ran as designed (#7). No code flaw was exploited, so the CKC "Exploitation" box holds no step. The loader collected stored passwords — credential acquisition belongs to this enabling step and is recorded as [DRE: C] (R-CRED). Its beacon home is a capability of this #7, not a new step.
- Persistence was registered through the legitimate Task Scheduler (#1); when the task fired, the payload ran again (#7, a new execution moment per R-EXEC).
- The stolen credentials logged in on other hosts (#4 — credential application, separate from acquisition per Axiom X).
- The administrator's own deployment tool pushed the ransomware to every server (#1), and the ransomware executed (#7), leaving the data present but unusable ([DRE: Ac]).
The TLCTC Attack Path Notation
This entire complex narrative boils down to this string for your dashboard:
#9 ||[human][@External→@Org]|| → #7 + [DRE: C] → #1 → #7 → #4 → #1 → #7 + [DRE: Ac]
(Note: the deployment (#1) enables the execution (#7), so the order is known and the notation is sequential, #1 → #7. The parallel operator (#X + #Y) is reserved for genuinely independent steps. Add →[Δt=…] between steps to show how fast the attacker moved; see The Kill Chain Fallacy for the timed version.)
Where STRIDE Fits in this Stack
You might ask, "Where does STRIDE fit?" STRIDE names the security property an attacker violates — mostly effects, not causes. That makes it a fine design-review checklist, but not a cause taxonomy. TLCTC does not replace it; each STRIDE finding gains a cluster:
- Spoofing? Usually #4 Identity Theft: a credential presented at the point of authentication by someone who is not its holder.
- Tampering? An integrity event, [DRE: I], recorded on the step of whichever cluster caused it — #1, #2, #3, #5, #7 or #8.
- Information Disclosure? A confidentiality event, [DRE: C], again attached to its causing step.
- Denial of Service? An availability event, [DRE: Av], caused by #6 Flooding — or by a crash bug (#2/#3) or a physical attack (#8).
Separating the Cause (the 10 clusters) from the Effect (Data Risk Events in the Bow-Tie) is what makes STRIDE findings, Kill Chain phases and ATT&CK techniques comparable — and what allows the standardized notation you see above.
Conclusion: Your New Scorecard
By adopting this synthesis, you move from qualitative storytelling to quantitative risk management.
- Narrate with CKC.
- Detail with ATT&CK.
- Measure and Govern with TLCTC.
Use the 10 Top Level Cyber Threat Clusters to build your 10×6×2 control matrix: ten clusters × the six NIST CSF 2.0 functions (Govern, Identify, Protect, Detect, Respond, Recover) × local and umbrella scope. This is how we bridge the gap between the SOC analyst finding a TTP and the Board Member asking, "Are we safe?"
References
- Kreinz, B. Top Level Cyber Threat Clusters (TLCTC), Core Paper v2.6 — axioms, R-EXEC, R-CRED, DRE refinement tree
- Kreinz, B. TLCTC Application Paper v2.6, §12 Harmonizing threat-modeling methods & standards
- MITRE ATT&CK Enterprise → TLCTC mapping
- Hutchins, E. M., Cloppert, M. J., Amin, R. M. Intelligence-Driven Computer Network Defense Informed by Analysis of Adversary Campaigns and Intrusion Kill Chains (Lockheed Martin, 2011)