Skip to content

Documentation

VULT SECURITY DOCUMENTATION

Find the right section

Core concepts

Event-and-Identity-Bound Authorization

The relationship between a verified person, their current presence, and the action they approve.

This model addresses a gap between having permission and personally authorizing a particular action. It joins an established identity, a fresh check of the person, the action's defining details, and that person's explicit decision.

What is bound together?

  • Identity: the person linked to a verified identity.
  • Presence: a fresh check that this person participates in the protected interaction.
  • Event: the specific transaction, change, or release presented for approval.
  • Decision: the person's explicit approval of that event.

These four elements describe the authorization moment. The model also has two supporting elements: a protected evidence record that preserves their relationship, and infrastructure through which organizations request, enforce, confirm, and retrieve evidence of authorizations. These are conceptual roles, not integration contracts.

Define the event clearly

The organization must define the material details before requesting approval. For a transfer, these include the relevant accounts, amount, currency, and destination. For an account change, they include the affected account and proposed new setting. If material details change outside the authorized scope, the model requires a new authorization.

An authorization is single-use and limited to that event. The executing application must check its validity, unused status, and scope alongside current permissions. This guide does not specify validity periods, replay-prevention mechanisms, enforcement interfaces, transports, payloads, tokens, or endpoints.

Keep permission with the organization

VULT Security's role in this model is to check the human and connect their decision to the event. The organization determines whether that person has authority, when this check is required, and whether the action proceeds. A successful identity check cannot replace those policy decisions.

Separate authorization from execution

An authorization record describes who was present and what they approved. It does not, on its own, prove that a downstream system completed the action. The organization's execution records establish whether the operation succeeded, failed, or changed state.

Connecting those records supports review of the event from approval through outcome. This is a traceability concept, not a promise of legal admissibility or a defined evidence schema.

For the identity behind this flow, read What is a verified human?. The capabilities overview places authorization alongside the other core concepts.