Skip to content
INTYGAStart free

Guides

Identity verification vs approval evidence: the difference

Identity verification establishes who a person is, or who is at the keyboard when a session starts. Approval evidence establishes what that person agreed to โ€” a signature over the exact action and its parameters โ€” in a form someone else can check later without trusting the system that recorded it. A strong sign-in proves the first and says nothing about the second.

Two questions that get answered as one

Most access control asks who someone is and what they are allowed to do. Good tools exist for both: identity proofing at onboarding, MFA and passkeys at sign-in, roles and scoped credentials afterwards. None of them records that a particular person looked at a particular irreversible action and agreed to it. That record is approval evidence, and it is a different artefact.

Identity verificationApproval evidence
Question it answersWho is this person, or who started this session?What did this person agree to, exactly?
When it happensAt onboarding, and at each sign-inAt each high-risk action, before it runs
What it producesA verified identity, a session or a tokenA signature over the action's canonical bytes: target, type, parameters, nonce and expiry
Who can check it laterThe issuer, and services that trust its tokensAnyone holding the approver's public key and the expected action, offline
What it cannot showWhich actions were taken in the session, or that anyone reviewed themThat the person understood the consequences, or that the action then succeeded

The same passkey can produce either

A WebAuthn passkey signs whatever challenge the ceremony gives it. At sign-in the challenge is a random value, so the signature proves the key was present at that moment. For an INTYGA approval the challenge is the canonical bytes of the action itself (DIV ยง4.4.5), so the same kind of signature also proves what was approved. The authenticator is the same; what it signs decides which evidence you hold.

Why a strong sign-in is not an approval record

A session outlives the decision it was opened for. Once someone is signed in, every request in that session carries the same proof of identity, whether the person reviewed it, an agent issued it under their token or a script replayed it. The session shows who was present; it cannot show which of those actions the person agreed to.

When you need approval evidence, not only identity

  • The action is irreversible or expensive: a production deploy, a payment, a permission change, a destructive database operation.
  • The request comes from automation โ€” an AI agent, a pipeline, a backend service โ€” so no person is at the keyboard when it runs.
  • Someone outside your organization may later ask you to show who approved this exact action: an auditor, a customer or an assessor.
  • The approval has to hold across systems, or outlive the tool that collected it.

If none of those apply โ€” a handful of actions a day on one platform โ€” a well-configured native control, such as a protected deployment environment or an MFA-protected API call, is probably enough.

What approval evidence still needs identity for

Approval evidence does not replace identity. A signature is only as good as the binding between the key and a named person: who enrolled the credential, how that person was verified and how the credential is revoked. In INTYGA a credential is bound to a person through an enrollment session or an administrator's invite, never through an identifier the requester supplies.

Where INTYGA fits

INTYGA holds high-risk actions by AI agents, pipelines and backend services until a person signs their exact parameters. The service that runs the action verifies that signature against what it is about to execute, and a tamper-evident record lets a third party check later what was approved โ€” not only who approved it.

For the verification step, see how to prove a human approved an AI agent's action. The FAQ compares INTYGA with MFA and just-in-time access.

Questions people ask next

Does a passkey sign-in count as approval evidence?

No. It proves who started a session. Approval evidence needs a signature whose challenge is the action itself, so it cannot stand for a different action.

If every action is signed, is identity verification still needed?

Yes. A signature proves which key approved; identity proofing and enrollment are what tie that key to a named person.