Capabilities overview
The core VULT Security concepts and the boundaries of the requesting organization's role.
This overview focuses on identity, current presence, event-specific approval, and evidence.
Identity establishment
Document validation, face matching, and liveness checks connect a claimed government-issued identity to a live person. VULTid represents the reusable identity established by that process. This is the foundation for a later check of the same person.
Read about verified-human identity
Current presence and approval
For an interaction selected by the organization, fresh liveness and server-side matching check whether the person linked to VULTid is participating now. If the interaction also requires authorization, the person is shown the specific action and explicitly decides whether to approve it. A biometric match alone is not an approval.
The action's material details matter. Approval for one set of details should not be reused for a changed request. Read the authorization model.
Evidence and responsibility
The model calls for evidence connecting the verified person, current presence, defined event, and decision. That evidence helps explain an authorization. The organization separately records and governs execution of the action.
| VULT Security concept | Organization's responsibility |
|---|---|
| Establish and recheck the person | Maintain accounts and decide which interactions require a check. |
| Connect an explicit decision to an event | Define the event and enforce permissions and scope. |
| Preserve authorization evidence | Record what the application actually executed. |
The organization also keeps its existing risk engines and transaction monitoring. VULT Security is not a replacement for those systems.
Data handling
The model distinguishes verification inputs, a retained biometric template, and authorization evidence. This guide does not state a retention default or a no-storage guarantee for government-ID images, face photographs, or videos.
Scope of this guide
Age and attribute checks, screening, duplicate detection, document-verification options, workflow tools, and integrations are outside this overview; the capability guide covers them field by field. No API, SDK, webhook, certification, or performance guarantee is specified here.
For an important boundary between local authentication and human identity, see Device biometrics vs VULTid.