---
type: "term"
title: "Cluster Quick Reference"
description: "| | Name | Generic Vulnerability | Topology | | | | | | | 1 | Abuse of Functions | Functional scope/trust (designed capabilities abused) | Internal | | 2 | Exploiting Server | Server side code implementation flaws | Internal | | 3 | Exploiting Client | Client side code implementation flaws | Internal | | 4 | Identity Theft | Identity artifact binding / credential lifecycle (use) | Internal | | 5 | Man in the Middle | Lack of end to end communication protection | Internal | | 6 | Flooding Attack | Finite capacity limitations | Internal | | 7 | Malware | Designed execution capability for untrusted content | Internal | | 8 | Physical Attack | Physical accessibility/interference | Bridge | | 9 | Social Engineering | Human psychological factors | Bridge | | 10 | Supply Chain Attack | Third party trust dependencies | Bridge | Reference: §4.1 (Cluster Definitions), §5.2 (Topology Classification) Related reading: [Mandiant M Trends 2025 — TLCTC](https://www.tlctc.net/tlctc mtrends 2025.html), [ENISA Threat Landscape 2025 — TLCTC](https://www.tlctc.net/tlctc enisa 2025 threat report.html), [Same Attack, Four Stories — vendor report comparison](https://www.tlctc.net/tlctc threat report chaos.html), [TLCTC × Threat Modeling Manifesto](https://www.tlctc.net/tlctc threat modeling manifesto.html), [End of Semantic Diffusion — Kuhn & TLCTC](https://www.tlctc.net/tlctc semantic diffusion.html), [TLCTC classification decision tree V2.0/V2.1](https://www.tlctc.net/tlctc decision tree.html), [Logical foundations of TLCTC](https://www.tlctc.net/tlctc logical foundation.html), [Why exactly ten?"
resource: "tlctc:term:cluster-quick-reference"
tags:
  - "glossary"
---
# Cluster Quick Reference

| # | Name | Generic Vulnerability | Topology |
| --- | --- | --- | --- |
| **#1** | Abuse of Functions | Functional scope/trust (designed capabilities abused) | Internal |
| **#2** | Exploiting Server | Server-side code implementation flaws | Internal |
| **#3** | Exploiting Client | Client-side code implementation flaws | Internal |
| **#4** | Identity Theft | Identity-artifact binding / credential lifecycle (use) | Internal |
| **#5** | Man in the Middle | Lack of end-to-end communication protection | Internal |
| **#6** | Flooding Attack | Finite capacity limitations | Internal |
| **#7** | Malware | Designed execution capability for untrusted content | Internal |
| **#8** | Physical Attack | Physical accessibility/interference | Bridge |
| **#9** | Social Engineering | Human psychological factors | Bridge |
| **#10** | Supply Chain Attack | Third-party trust dependencies | Bridge |

**Reference:** §4.1 (Cluster Definitions), §5.2 (Topology Classification)

**Related reading:** [Mandiant M-Trends 2025 — TLCTC](https://www.tlctc.net/tlctc-mtrends-2025.html), [ENISA Threat Landscape 2025 — TLCTC](https://www.tlctc.net/tlctc-enisa-2025-threat-report.html), [Same Attack, Four Stories — vendor report comparison](https://www.tlctc.net/tlctc-threat-report-chaos.html), [TLCTC × Threat Modeling Manifesto](https://www.tlctc.net/tlctc-threat-modeling-manifesto.html), [End of Semantic Diffusion — Kuhn & TLCTC](https://www.tlctc.net/tlctc-semantic-diffusion.html), [TLCTC classification decision tree V2.0/V2.1](https://www.tlctc.net/tlctc-decision-tree.html), [Logical foundations of TLCTC](https://www.tlctc.net/tlctc-logical-foundation.html), [Why exactly ten? — TLCTC architecture](https://www.tlctc.net/tlctc-why10-explainer.html), [10×10×10 — fun fact about TLCTC](https://www.tlctc.net/tlctc-10x10x10-fun-fact.html), [Agentic AI under the microscope — TLCTC](https://www.tlctc.net/tlctc-agentic-ai-microscope.html), [Quantum & AI — new magic, same 10 threats](https://www.tlctc.net/tlctc-quantum-ai-velocity.html), [AI conversation deep dive on TLCTC](https://www.tlctc.net/blog-tlctc-ai-conversation-from-scratch.html), [Grok AI 4.1 — independent TLCTC validation](https://www.tlctc.net/tlctc-grok-ai-validation.html), [G7 SBOM-for-AI — control fixation critique](https://www.tlctc.net/sbom-for-ai-control-fixation.html), [Capability-based planning via 10×(6×2) matrix](https://www.tlctc.net/tlctc-capability-based-planning.html), [TLCTC — the missing link between strategy and ops](https://www.tlctc.net/tlctc-fillthegap.html), [Tactics evolve, 10 threats are constant](https://www.tlctc.net/blog-cyber-hype.html), [Tactics evolve, 10 threats are constant — TLCTC](https://www.tlctc.net/tlctc-blog-cyber-hype.html), [TLCTC for everyone — the Blind Spot method](https://www.tlctc.net/tlctc-everyone-blind-spot.html), [Emerging technologies as threat enablers](https://www.tlctc.net/tlctc-emerging-tech-radar.html), [TLCTC v2.1 monster prompt — CISO & Risk](https://www.tlctc.net/tlctc-prompt-ciso.html), [TLCTC v2.1 monster prompt — CTI & Forensic](https://www.tlctc.net/tlctc-prompt-cti.html), [TLCTC v2.1 monster prompt — Regulators & Standards](https://www.tlctc.net/tlctc-prompt-regulators.html), [TLCTC v2.1 AI analysis prompt — teach any LLM](https://www.tlctc.net/tlctc-ai-analysis-prompt.html), [TLCTC v2.1 monster prompts — index](https://www.tlctc.net/tlctc-prompt-index.html), [The Risk Appetite Conversation Your Board Isn't Having](https://www.tlctc.net/tlctc-strategy.html), [Understanding cyber threats — a common language](https://www.tlctc.net/tlctc-executive-summary.html), [TLCTC — the missing link (brief)](https://www.tlctc.net/tlctc-brief-doc.html), [Strategic risk management implementation guide v2.1](https://www.tlctc.net/tlctc-big-picture.html)