In the evolving landscape of cybersecurity, effective threat modeling frameworks are essential for organizations to identify, categorize, and mitigate potential security risks. Two significant frameworks in this domain are Microsoft's STRIDE and the newer Top Level Cyber Threat Clusters (TLCTC). While STRIDE has been a staple in security discussions for years, TLCTC offers a more robust, logically consistent approach to threat categorization.
Core Philosophical Differences
The fundamental difference between STRIDE and TLCTC lies in their underlying approach to threat categorization:
STRIDE: A Categorical Checklist
STRIDE is a mnemonic designed to help developers consider six categories of security threats:
- Spoofing identity
- Tampering with data
- Repudiation
- Information disclosure
- Denial of service
- Elevation of privilege
While useful as a quick reference, STRIDE lacks a comprehensive methodology explaining why these specific categories were chosen or how they relate to each other.
TLCTC: A Structured Taxonomy Based on Generic Vulnerabilities
TLCTC, in contrast, is built upon a set of clearly defined axioms and a rigorous thought experiment that systematically identifies generic vulnerabilities, resulting in ten distinct threat clusters:
Critical Limitations of STRIDE from a TLCTC Perspective
1. Mixing of Disparate Concepts
The Problem: STRIDE's six letters are six negated security properties, and those properties sit on different layers of an incident. Read against the TLCTC consequence chain, System Risk Event → Data Risk Event → Business Risk Event, they sort like this:
| STRIDE | Negated property | Layer | TLCTC v2.7 |
|---|---|---|---|
| Spoofing | Authentication | System layer (SRE) | A state: one identity accepted as another. The step that reaches it is #4 Identity Theft, credential use; how the credential was obtained is a separate, earlier step (Axiom X). |
| Tampering | Integrity | Data layer (DRE) | [DRE: I], refined where known into Ii (incorrect state) or If (misattributed state). Recorded on whichever step caused it. |
| Repudiation | Non-repudiation | Neither: a control gap | Missing evidence design (Axiom V: control failures are not threats). A record that claims an author it does not have is [DRE: If]. |
| Information Disclosure | Confidentiality | Data layer (DRE) | [DRE: C]. No refinement: disclosed data is disclosed, however it leaked. |
| Denial of Service | Availability | Data layer (DRE) | [DRE: A], refined into Av (gone or unreachable) or Ac (present but unusable). Only capacity exhaustion makes the cause #6 Flooding Attack. |
| Elevation of Privilege | Authorization | System layer (SRE) | A state: the system now lets the attacker do more than before. Reached through a cause step; that step is what gets classified. |
Three letters (T, I, D) are consequences on the data layer: they say what happened to a record, not why. Two (S, E) describe what a compromised system now permits, the state a cause step leaves behind. One (R) names a control gap. None of the six names a generic vulnerability, so none of them is a cause: six categories, zero generic vulnerabilities.
The TLCTC Solution: TLCTC classifies the cause side only, by the generic vulnerability a step exploits, and records consequences in their own layers: the System Risk Event every successful cluster step records, then the Data Risk Events and Business Risk Events that may follow.
2. Failure to Distinguish Between System Risk Events and Data Risk Events
A crucial advancement in TLCTC is its implementation of the bow-tie model for risk analysis, which clearly distinguishes between:
- System Risk Event (Central Event): The point where a threat step succeeds and the system's behaviour, privileges, data or trust relationships leave what their owner controls: System Compromise — Loss of Control. Every cluster step records one.
- Data Risk Events (Consequences): The outcomes that may follow a system compromise:
[DRE: C]Loss of Confidentiality: data disclosed to a party not entitled to it[DRE: I]Loss of Integrity, refined where known intoIi(incorrect state: the content is wrong) andIf(misattributed state: the record claims an origin or author it does not have)[DRE: A]Loss of Availability/Accessibility, refined intoAv(data gone or unreachable) andAc(data present but unusable, e.g. encrypted by ransomware)
- Business Risk Events (further consequences): what the business then suffers: an outage declared, a notification filed, a fine imposed. The full chain is
SRE → DRE → BRE*; BREs may chain.
STRIDE fails to make this critical distinction. It lists data risk events (Tampering, Information Disclosure, Denial of Service) and system states (Spoofing, Elevation of Privilege) side by side, as if they were threats of one kind. This conflation makes it difficult to establish clear cause-and-effect relationships and implement appropriate controls.
Keeping the layers apart matters because every causal transition in the chain carries a Δt, the causal interval between the two events. Δt is not itself the detection window; it bounds it. Compromise detection that acts inside the Δt between the System Risk Event and the first Data Risk Event stops the chain before any data is touched. This distinction is operationally significant because:
- It reflects the reality of modern attacks, where adversaries often maintain persistence before executing their ultimate objectives.
- It enables more precise mapping of detective and reactive controls in the interval between compromise and data risk events.
- It acknowledges that some transitions are effectively instantaneous. Where Δt is close to zero, no detection can act in time and only prevention counts.
3. Ambiguity and Overlap in Categories
Because STRIDE mixes concepts, its categories frequently overlap, creating confusion about where particular threats should be classified. For example, Microsoft's own documentation lists "Threat #4" as simultaneously falling under three STRIDE categories (Spoofing identity, Information disclosure, and Elevation of privilege).
TLCTC's distinct clusters, based on non-overlapping generic vulnerabilities, eliminate this ambiguity. Each threat is categorized based on the initial vulnerability being exploited, providing clarity even in complex attack scenarios.
4. Incomplete Coverage
STRIDE's lack of a foundational methodology makes it difficult to assess its completeness. The framework doesn't provide a systematic way to determine if all possible threats are covered.
TLCTC, derived from a comprehensive thought experiment designed to cover all IT assets, makes a stronger claim to completeness. Its systematic derivation process ensures that each generic vulnerability is addressed by exactly one threat cluster.
5. Limited Actionability
The STRIDE categories are too broad and inconsistent to map directly to specific security controls. "Tampering," for example, could involve everything from SQL injection to altering network packets, making it challenging to translate STRIDE analysis into concrete security measures.
TLCTC, by focusing on the generic vulnerability, provides a clearer path to control implementation. For instance, identifying a threat as #2 Exploiting Server immediately guides you toward server-side code security, input validation, and web application firewalls.
How TLCTC Addresses STRIDE's Concerns
Despite STRIDE's categorization flaws, it raises valid security concerns that TLCTC effectively addresses:
| STRIDE Category | TLCTC Coverage |
|---|---|
| Spoofing | The accepted false identity is a system state; the step that reaches it is primarily #4 Identity Theft (credential use). Acquiring the credential is a separate step under its own cluster. |
| Tampering | A data risk event, [DRE: I] (Ii where the content is wrong, If where the record claims a false origin), recorded on the step that caused it. The cause can be #1 Abuse of Functions, #2 Exploiting Server, #3 Exploiting Client, #5 Man in the Middle, #7 Malware or #8 Physical Attack, depending on how the record was changed. |
| Repudiation | Not a cause: a gap in logging and evidence design (Axiom V — control failures are not threats). Where a record ends up claiming an author it does not have, the outcome is [DRE: If]; manipulating or deleting evidence classifies by its own cause. |
| Information Disclosure | A data risk event, [DRE: C], recorded on the step that caused it — reachable from many clusters (#1, #2, #3, #5, #7, #8, #9 …). |
| Denial of Service | A data risk event, [DRE: A], refined into [DRE: Av] or [DRE: Ac]. The cause is #6 Flooding Attack only when finite capacity is exhausted; a crash bug is #2/#3, ransomware is #7, a cut cable is #8. |
| Elevation of Privilege | A change of authorization state, on the system layer, reached through a cause step; that step's cluster is what gets classified (#1, #2, #3, #4, #7 …). Where a privilege boundary inside one system is crossed, it can be annotated as |[privilege][@user→@root]| without changing the cluster. |
Advanced Capabilities of TLCTC Not Present in STRIDE
TLCTC offers several capabilities that STRIDE simply doesn't address:
1. Attack Sequence Representation
TLCTC can represent complex attack paths using a standardized notation (e.g., #9 → #3 → #7), illustrating how threats can chain together. This provides crucial context for understanding sophisticated attacks and implementing appropriate defensive measures at each stage.
Engineering
Exploit
Execution
2. Strategic-Operational Bridge
TLCTC explicitly connects strategic risk management with operational security, offering a two-tiered approach:
- Strategic Layer: High-level risk management, policy-making, and program governance.
- Operational Layer: Detailed security control implementation, monitoring, and adjustment.
3. Comprehensive Control Framework Integration
TLCTC integrates with the six NIST CSF 2.0 functions (Govern, Identify, Protect, Detect, Respond, Recover): ten clusters × six functions gives a 60-cell control matrix, one control objective per cell.
Practical Application Example
Consider a phishing attack that leads to credential theft and eventual data exfiltration:
- Spoofing (the attacker uses stolen credentials)
- Information Disclosure (sensitive data is exposed)
[DRE: C] belongs.- Clear separation between the causes and the data risk events.
- Precise mapping to appropriate controls at each stage.
Microsoft's STRIDE Examples Demonstrate the Framework's Confusion
Microsoft's own documentation reveals STRIDE's weaknesses. For example, "Threat #4" is categorized under three different STRIDE categories simultaneously:
- Spoofing identity
- Information disclosure
- Elevation of privilege
This overlap demonstrates the fundamental conceptual confusion in STRIDE's approach, where a single threat scenario doesn't fit cleanly into any one category because the categories mix different types of concepts.
Conclusion
While STRIDE has served as a helpful high-level brainstorming tool for developers, TLCTC provides a more rigorous, consistent, and complete approach to threat categorization. By focusing on generic vulnerabilities, clearly separating threats from consequences, and enabling the representation of complex attack sequences, TLCTC offers significant advantages for modern cybersecurity risk management.
The bow-tie model implemented in TLCTC—with its clear distinction between system risk events and data risk events—provides operational clarity that STRIDE lacks. This framework bridges the gap between strategic risk management and tactical security operations, enabling organizations to develop more effective security strategies in an increasingly complex threat landscape.
For organizations seeking to move beyond checklists to a comprehensive, structured approach to threat modeling and risk management, TLCTC represents the clear path forward.
Reference: The STRIDE Threat Model
Excerpt from Microsoft.com (Article 11/12/2009):
When you are considering threats, it is useful to ask questions such as these:
- How can an attacker change the authentication data?
- What is the impact if an attacker can read the user profile data?
- What happens if access is denied to the user profile database?
You can group threats into categories to help you formulate these kinds of pointed questions. One model you may find useful is STRIDE, derived from an acronym for the following six threat categories:
Applying STRIDE (Sample Threats to a Web Site):
| Threat #1 | A malicious user views or tampers with personal profile data en route from the Web server to the client or from the client to the Web server. (Tampering with data/Information disclosure) |
| Threat #2 | A malicious user views or tampers with personal profile data en route from the Web server to the COM component or from the component to the Web server. (Tampering with data/Information disclosure) |
| Threat #3 | A malicious user accesses or tampers with the profile data directly in the database. (Tampering with data/Information disclosure) |
| Threat #4 | A malicious user views the Lightweight Directory Access Protocol (LDAP) authentication packets and learns how to reply to them so that he can act "on behalf of" the user. (Spoofing identity/Information disclosure/Elevation of privilege) |
| Threat #5... | ...An attacker places his own Web server on the network after killing the real Web server with a distributed DoS attack. (Spoofing identity...) |
References
- Kreinz, B. Top Level Cyber Threat Clusters (TLCTC), Core Paper v2.7 — §3.4 cause, event and consequence (SRE → DRE → BRE*), §7.6 DRE tags and refinement tree
- Kreinz, B. TLCTC Application Paper v2.7, §12 Harmonizing threat-modeling methods & standards
- Kreinz, B. Layered Event Modelling v1.0, causal and normative edges, Δt
- Microsoft, The STRIDE Threat Model (2009), excerpted above