TLCTC · A blind-spot in plain sight

What CIS
Cannot See

A framework that measures attack frequency by asset class can never detect over-investment by cause. Here is the blind spot — in one chart.

CIS RAM does not have a broken answer. It has a missing axis. And the consequence of that missing axis is not abstract — it is a specific, measurable distortion that the framework cannot perceive about itself.

To see it, you only need to ask one question CIS RAM never asks: where, by cause, does our control effort actually go?

Updated · 2 October 2026

The chart now comes from the published per-Safeguard mapping (a rebuild against CIS Controls v8.1.2; data on GitHub, comparison on the evidence page). The June version showed 19 : 1 between #2 and #6. The rebuild places flooding by effect — no Safeguard is written for it — and moves 18 data-layer Safeguards (encryption at rest, backups) to a separate DRE matrix; the preventive peak now sits on #1 and #4. The ratio changed. The blind spot did not.

The two axes

Every risk framework measures along some axis. The axis you choose determines what you can see — and what you can't.

CIS RAM measures by

Asset class hit
Users
Devices
Data
Software
Network

Six buckets. The VCDB Index. Frequency that an asset type appears as a target.

TLCTC measures by

Cause cluster
#1 Abuse
#2 Server
#4 Identity
#6 Flooding
#5 MITM

Ten mutually-exclusive generic vulnerabilities. The mechanism, not the target.

These are not two views of the same thing. "A server was attacked" (asset) and "the server was exploited / abused / reached with stolen credentials" (cause) are orthogonal. One asset bucket can hold three causes. One cause can strike five asset types. You cannot derive one axis from the other.

CIS chose the asset axis. So the cause axis is simply not in the data.

Map the Safeguards by cause. This appears.

Every CIS Controls v8.1.2 Safeguard that acts on a cause, placed in the cluster(s) whose generic vulnerability it acts upon — 135 system-layer Safeguards; the 18 that act after the compromise sit in a separate DRE matrix. Bar length = preventive placements on that cause.

#1Abuse of Functions
26
#4Identity Theft
26
#2Exploiting Server
18
#3Exploiting Client
18
#7Malware
16
#10Supply Chain
10
#5Man in the Middle
8
#9Social Engineering
7
#6Flooding Attack
3
#8Physical Attack
3
Preventive Safeguard placements per cause cluster · CIS Controls v8.1.2 · TLCTC cluster matrix · published mapping, October 2026
26:3
#1 Abuse · #4 Identity vs.
#6 Flooding (preventive)
52
of 135 preventive
placements sit on #1+#4
0
CIS RAM signals that
flag this distribution

Why CIS cannot see this

The skew above is not a secret. It is sitting in the control set, in plain sight, the whole time. The reason no CIS RAM assessment has ever surfaced it is structural: the chart is drawn on an axis CIS RAM does not possess.

CIS RAM's expectancy engine pairs two numbers — how often an asset class is hit, and how mature a Safeguard is. There is no cause variable anywhere in that calculation. So when the control set pours twenty-six preventive placements each onto function abuse and identity theft and three onto flooding — none of them written for flooding — the engine has no coordinate in which that fact can register. It can tell you that devices are attacked in 74% of incidents. It cannot tell you that your defenses against identity theft outnumber your defenses against flooding almost nine to one — because "identity theft" and "flooding" are not entries in its vocabulary. They are causes. CIS speaks assets.

A blind spot is not an error. It is a region the instrument cannot resolve — no matter how carefully you read it.

Why it matters

You might object: maybe identity theft deserves twenty-six controls. Maybe flooding needs no Safeguard of its own. Perhaps. But that is a decision a risk framework should let you make — and defend. Right now CIS RAM cannot present the distribution, so the distribution was never decided. It accreted. Each Safeguard was added on its own merits, against an asset-frequency justification, with nothing in the method ever asking "and how does this balance our effort across causes?"

The due-care consequence

Under DoCRA — CIS RAM's own standard — a "reasonable person" balances effort against foreseeable harm. But you cannot demonstrate a balanced, reasonable allocation across threats you cannot enumerate. If a flooding attack causes harm, "three controls helped by accident, weighted by asset-class frequency" is not a defense. "We deliberately allocated N controls to flooding because our cause-balanced assessment judged it an N-control risk" is. The first is an accident. The second is due care. Only the cause axis can produce the second.

This is the whole argument, and it is small enough to hold in one hand: CIS RAM can tell you whether a risk is reasonable to accept. It cannot show you how your own defenses are distributed across the causes of those risks — because it measures the wrong axis. The distribution is right there. CIS simply cannot see it.

The fix is free

The cause axis exists. It is ten mutually-exclusive clusters, openly published, CC BY 4.0. Adopt it underneath CIS RAM and nothing of value is lost: Impact × Expectancy stays, the reasonableness test stays, the legal translator stays. What is gained is sight — a control set that can finally see its own shape, name its own gaps, and defend its own balance.

CIS does not need to be replaced. It needs to be able to see.

Read the full argument: Why CIS Cannot Answer Your Cyber Threat Risk · or the evidence: 153 Safeguards → 74 objectives.

Distribution data: published per-Safeguard CIS Controls v8.1.2 → TLCTC mapping (rebuild, October 2026; mappings/cis-controls-v8.1), preventive placements judged per Safeguard. Asset-axis figures from the CIS RAM VCDB Index. The June 2026 version of this chart (19 : 1, #2 vs #6) came from an unpublished mapping; the evidence page compares both.