The Granularity Illusion

Why 12 Weighted Labels Beat 10,847 Binary Permissions

12
Weighted Labels
1012
Effective States
17
Bits per Check
O(1)
Decision Time

1. The Counter-Intuitive Truth

More permissions ≠ More security.

Enterprise IAM systems advertise "fine-grained control" with 10,000+ discrete permissions. But granularity isn't about quantity—it's about expressiveness. A continuous dimension with 0.01 resolution expresses 100 states. Twelve such dimensions express 1012 states—10 trillion unique identities.

Traditional IAM gives you 10,847 light switches. FIM gives you 12 dimmer knobs. The dimmers are more expressive by a factor of 10 billion.

2. What Traditional IAM Actually Delivers

The Marketing Claim

"10,847 fine-grained permissions for maximum control"

Defined permissions10,847
Actually used487 (4.5%)
Regularly checked156 (1.4%)
Meaningful combos~52 (0.5%)

95.5% exists for "completeness"—creating complexity without security value.

The FIM Reality

12 continuous dimensions at 0.01 resolution

Dimensions12 (weighted)
States per dimension100
Total effective states1012
All actively used100%

Every label contributes. Nothing is vestigial.

The Hidden Cost

Each unused permission is attack surface. Each redundant rule is audit complexity. Each overlapping policy is a conflict waiting to happen. Traditional IAM isn't just inefficient—it's actively dangerous.

3. The Math That Makes It Work

Expressiveness Calculation

12 dimensions × 100 states = 1012 unique identities

Traditional IAM: 10,847 binary switches = 210847 theoretical states, but only ~500 actually used (role combinations). FIM: 12 weighted labels = 1012 practical states, all reachable.

Why Continuous Beats Binary

Aspect Binary Permissions Weighted Labels
State expression ON or OFF 0.00 to 1.00 (100 gradations)
Identity precision "Has permission X" "35% operator, 28% builder..."
Policy conflicts Constant (overlapping rules) Impossible (single vector)
Audit trail Which rules fired? Vector diff (one operation)
Access decision O(n) rule traversal O(1) vector comparison

4. Same-Size Holes in the Security Mesh

Every security system has gaps. The question isn't whether you have holes—it's whether you know where they are.

Traditional IAM Gaps

Hole size variance1 to 523 permissions
Standard deviation47.3
PredictabilityNone
Detection methodPenetration testing

FIM Grid Gaps

Hole sizeExactly 0.694% each
Standard deviation0.0
Predictability100%
Detection methodBy design
The Insight

In FIM, the "H" (Hole) state is intentional. You declare where escalation paths exist. Traditional IAM discovers gaps through breaches. FIM designs them into the architecture.

5. What This Means for Real Systems

For Security Teams

  • No more "permission sprawl" audits
  • Compliance reduces to vector comparison
  • Attack surface is knowable, not estimated
  • Escalation paths are visible by design

For Engineering Teams

  • O(1) permission checks (no ACL traversal)
  • No policy language to learn
  • Identity IS the policy (no drift)
  • ~200 lines vs 10,000+ for traditional

The Architectural Shift

Traditional IAM asks: "What is this user allowed to do?" (requires rule lookup)

FIM states: "This is what this user IS." (the vector is the policy)

The shift from "checking permissions" to "comparing shapes" is the same shift from "looking up words in a dictionary" to "recognizing a face." One is O(n), the other is O(1). One requires traversal, the other is immediate.

See It Working

The 12×12 identity grid isn't a concept—it's running in your browser right now.
Watch Sarah Chen get access to the Q4 press release in one O(1) comparison.

View Interactive Demo →