Skip to content

Free for nonprofits, NGOs, think tanks, and institutes. Grant funded by James Scott, administered by the Embassy Row Project.

ArtOfTheHack home

8 minute read

Zero Trust Is a Decision Problem

Identity, device, and network controls are enforcement. Zero trust maturity depends on the quality of the decision that precedes enforcement.

Enforcement without reasoning

Most zero trust programs are described in terms of enforcement points: identity providers, device posture agents, microsegmentation, privileged access brokers. Each of these can allow or deny. Very few of them can explain the basis of a specific allow or deny in terms that survive review.

The result is a program that is architecturally correct and operationally opaque. Policy drifts, exceptions accumulate, and nobody can state with confidence what a given identity can actually reach today.

The decision that sits before the gate

Every access outcome is a decision made under uncertainty about identity, device state, behavior, sensitivity of the target, and business context. Treating that decision as a first-class object rather than an implicit side effect makes the program measurable.

  • Continuous evaluation instead of point-in-time authentication
  • Explicit reachability modeling rather than inferred segmentation
  • Exception governance with expiry and evidence of ongoing need
  • Access decisions retained and replayable during audit

Measuring maturity honestly

A mature program can answer three questions on demand: what can this identity reach, why was that access permitted, and what would change if the identity were compromised right now. Those are decision questions, not enforcement questions.