Identity Enforcement

Identity enforcement

Whether a store actually enforces the identity scheme it declares, measured from what it does, never assumed from what it says.

Declaring an identity scheme in a UCP profile is one line of JSON. Enforcing it takes a running verifier, key lookup against a directory, and a decision on every request. The store owner can't see the gap between the two: an integration "works" the same whether signatures are checked or ignored. That is why it is worth measuring.

How it's measured

We send one valid, correctly signed request as a baseline, then a series of probes: copies of that request with one thing changed. Enforcement is read as divergence: does the store treat the changed request differently from the valid one? Divergence, not rejection: a scheme that gives verified traffic more trust, rather than rejecting invalid traffic, still has visible effects, and that counts.

Probe dimensionThe question it asks
PresenceIs an unsigned request treated differently?
IntegrityIs a tampered signature treated differently?
Binding Is a signature over the wrong context treated differently?
FreshnessIs an expired signature treated differently?
ReplayIs a replayed nonce treated differently?
Key resolution Is a signature from an unknown key treated differently?
Note

Probes run only against reference stores, stores you own, or stores that have opted in. Never against someone else's production store unasked.

The five verdicts

These are not pass or fail on purpose: a store that accepts everything is not failing a scheme, it is ignoring it.

VerdictMeans
Enforced Valid requests accepted; every invalid variant treated differently.
Partial Some invalid variants treated differently; others accepted unchanged.
Not enforced No gating seen: signed and unsigned requests treated the same.
Inconclusive The valid signed request did not succeed, so enforcement could not be assessed. Never rendered as failure.
Not runHandshake only: the probes have not been run.

Two rules keep the readout fair. "Not enforced" is only reported for a store that declares the scheme: a store that never claimed it gets no identity verdict at all. And allowing unsigned traffic is not a downgrade: it is the Permissive posture, the recommended way to roll out, and it is reported beside the verdict, never folded into it.

Postures and verdicts

A posture is the stance a store is set up to take. A verdict is what we measure it actually doing. The readouts worth acting on are where the two disagree: a store that believes it is Strict but measures Partial, or declares a scheme and measures Not enforced.

PostureValidMissingInvalid
Strictallowrejectreject
Permissiveallowallowreject
Noneallowallowallow

Strict is the production stance and Permissive the rollout stance. None exists on reference stores so you can see what no enforcement looks like from the agent's side. Strict and Permissive both reject invalid signatures: that column matters most.

Where you see it

  • Conformance page: the verdict, with the readout for each probe.
  • The identity panel: you run the probe set from there, against a connected store.
  • Signature verification: the same checks from the other side, with your agent's signatures checked by our store.

Something wrong on this page?