Introduction
The Top Level Cyber Threat Clusters (TLCTC) framework simplifies the complexity of cyber risk by grouping all technical attack vectors into ten mutually exclusive "Clusters" based on the generic vulnerability they exploit. This article explores how the TLCTC Radar tool translates these concepts into actionable intelligence.
Five Practical Applications of TLCTC Radar
The radar concept is flexible. It allows security leaders to visualize the 10 Clusters through different lenses depending on the strategic question being asked.
1. Organizational Boundary Analysis
This view answers: "Where are the threats originating relative to our trust boundaries?"
This visualization highlights the distinction between threats targeting the organization directly versus those crossing via trust boundaries:
- Customer Channel: High activity in #4 Identity Theft and #9 Social Engineering. Attackers abuse human trust to obtain credentials (the acquisition belongs to #9) and then use them to impersonate legitimate users (#4).
- 3rd Party: Significant risk in #10 Supply Chain Attack. #10 is the step where we accept a third-party artifact (an update, a package, a service response) that was subverted before it reached us. If its code then executes, that is a separate #7 Malware step. The ring itself is wider than #10: “third party” names a relationship, and a supplier's outage or a breach of our data at the supplier's site is third-party risk without any #10 step. See My Supply Chain Attack Risk Is Not My “Third-Party Risk”.
2. Infrastructure Domain Analysis
This view answers: "Which parts of our tech stack are being targeted by which clusters?"
- Servers & Cloud: High intensity in #2 Exploiting Server (implementation flaws in server-role components) and #1 Abuse of Functions (designed functions and configuration used outside their intended scope).
- Endpoints: The primary battleground for #3 Exploiting Client (implementation flaws in client-role components such as browsers and document viewers) and #9 Social Engineering.
- Network: The domain of #6 Flooding (capacity exhaustion) and #5 Man in the Middle (path interception).
3. Data Risk Impact Analysis (CIA)
This view connects Threat Causes (Clusters) to Risk Consequences (Data Risk Events).
- Confidentiality: On the radar it sits behind #4 Identity Theft and #5 Man in the Middle. In an attack path the disclosure (
[DRE: C]) is recorded on the step that reads the data: the #5 step itself, or the #1 step that follows a #4 login. - Availability: The domain of #6 Flooding Attack (data or service unreachable,
[DRE: Av]) and of #7 Malware that encrypts (data present but unusable,[DRE: Ac]). “Ransomware” names that outcome, not a cluster. - Integrity: Often compromised via #2 Exploiting Server (SQL injection modifying data) or #1 Abuse of Functions (logic manipulation): an incorrect state,
[DRE: Ii].
4. Threat Actor Capability Analysis
This view answers: "What is the preferred modus operandi of our adversaries?"
The actor is a lens for reading the radar, not a classification input: the same step maps to the same cluster whoever performs it (Axiom IV).
- Nation-State (APTs): Show broad capabilities across all clusters, with heavy reliance on #10 Supply Chain and #9 Social Engineering for stealthy initial access.
- Cyber Criminals: Heavily focused on monetization via #7 Malware (ransomware payloads) and #4 Identity Theft.
- Hacktivists: Often favor visible disruption via #6 Flooding and #1 Abuse of Functions (defacement).
5. Sector-Specific Threat Landscapes
This view answers: "How does the risk profile change based on my industry's business model?"
While the 10 TLCTC Clusters are universal, the intensity and frequency vary drastically by sector. A bank faces a different risk profile than a telecom provider or an IT service firm.
- Financial Services (Blue): High intensity in #4 Identity Theft and #9 Social Engineering. Attackers prioritize abusing human trust to steal credentials.
- IT Services & Providers (Green): The critical risk is #10 Supply Chain Attack, because for their customers IT providers are the supply chain. Where an attacker subverts what the provider ships or operates, the customer accepts it (#10) and it usually runs (#7 Malware). Where the attacker instead signs in to customers with the provider's credentials, the step is #4, not #10.
- Telecom (Orange): Unique exposure to #6 Flooding (DDoS against infrastructure) and #5 Man in the Middle (interception at the infrastructure level).
- Government (Red): A complex profile featuring high #10 Supply Chain and #9 Social Engineering.
Conclusion
The TLCTC Radar transforms the abstract 10 Clusters into a strategic tool. Whether you are analyzing your own organizational boundaries, profiling an APT group, or assessing sector-wide risks, the framework remains consistent.
By using the radar, security leaders can move from reactive "whack-a-mole" against individual exploits to a proactive defense strategy that addresses the fundamental Generic Vulnerabilities driving their specific risk landscape.
Note: This blog post utilizes the Top Level Cyber Threat Clusters (TLCTC) framework. Radar visualizations are open-source implementations of the framework's concepts.
Updated for TLCTC v2.7 in November 2026; the radar images are the 2025 originals. References: core paper §3.4 (cause–event–consequence model), §4 (the ten clusters), §5 (Axiom IV), §7.6 (data risk event tags).
Radar App Datasets: BACS 2024 Report
Use these JSON artifacts to visualize the BACS 2024 Cyber Landscape Report directly in the TLCTC Radar App. Each dataset corresponds to a specific analysis view.