A bank can verify a customer’s government-issued ID, complete its due diligence, and open the right account for the right person, then face a basic question a month later: who is actually requesting this transfer?
Imagine a customer who completed every onboarding check. Their identity is legitimate, their account is established, and their contact information is on file. Weeks later, a request arrives to add a new recipient and move $25,000. The password is accepted. A second factor passes. The request comes through an authenticated session.
Those results give the bank evidence to evaluate. But unless the workflow freshly verifies the person and connects that verification to the transfer, the original identity check cannot establish who is acting now.
The same question follows an employee into an enterprise system, a patient into a healthcare portal, or a customer into an account-recovery process. Organizations put considerable effort into establishing who someone is. What happens to that connection when the person returns?
At VULT Security, we believe the identity established at enrollment should remain the foundation for consequential actions throughout the relationship. When it matters, the organization should be able to verify the actual human in real time and establish exactly what that person authorized.
What Happens After KYC or Identity Verification?
Identity verification, often called IDV, establishes a connection between a person and the identity they claim. Know Your Customer, or KYC, is broader: it includes understanding the customer relationship and applying the relevant due diligence requirements. In banking, those responsibilities continue after onboarding. FinCEN’s customer due diligence guidance includes ongoing monitoring and updating customer information on a risk basis.
After enrollment, organizations typically issue or associate credentials with an account, assign permissions, authenticate returning users, and monitor activity. NIST’s Digital Identity Guidelines describe authentication in terms of establishing control of authenticators associated with a subscriber account.
That distinction matters. Identity proofing establishes the connection to the person. Later authentication provides evidence through the methods the organization accepts. The organization then decides what that evidence is sufficient to permit.
Stage | What it establishes | What a later protected action still needs |
Identity verification | The person’s connection to validated identity evidence | Fresh verification that the same person is participating |
Customer due diligence | Information about the customer and the relationship’s risks | Evidence of who is personally authorizing this event |
Account authentication | Control of the required account-associated authenticators | The verified human’s participation in the specific action |
Organizational permissions | What the account holder or representative is allowed to do | Evidence that the authorized person is exercising that permission now |
An organization can perform all four functions responsibly and still need a stronger connection between the human and the next action.
When Information Is Allowed to Stand In for the Human
Consider what many systems ask for after onboarding: a password, a one-time code, an authenticator response, a passkey, a recognized device, or an active session. If the required checks pass, the account proceeds.
In those workflows, evidence associated with the person is accepted as a substitute for verifying the actual human at that moment. The distinction becomes consequential when someone other than the rightful person obtains a usable route through the controls.
Different authentication methods offer different protections. Phishing-resistant authentication can substantially strengthen account security. The question for a protected action is whether the evidence also establishes that the government-ID-verified person is present and personally authorizing what happens next.
A callback illustrates the issue. Calling a previously verified number can be a valuable safeguard, especially when the caller reviews the transaction details. But reaching that number and hearing a familiar voice is a different form of evidence from matching the live person to the identity established at enrollment.
The FBI has documented criminals using AI-generated audio, video, and identity documents to support impersonation and fraud. That makes it increasingly important to ask what a familiar signal actually proves.
A bank should be able to distinguish “the required checks passed” from “the verified customer personally authorized this transfer.”
Device Biometrics Have a Different Job
A face or fingerprint check can make authentication both convenient and secure. The important question is what reference the biometric is being compared against.
Apple explains that Face ID compares captured facial information with the facial data enrolled on the device. Applications receive an authentication result; they do not receive the enrolled facial data.
That successful local match does not, by itself, establish that the person matches the government-issued ID verified by a bank or employer. The device’s biometric enrollment and the organization’s identity verification are separate processes unless the implementation explicitly connects them.
The distinction also appears in the W3C WebAuthn specification, which explains that user verification does not give the relying service a concrete identification of the person.
For a consequential action, the organization needs to know more than whether an accepted authenticator was used. It needs a reliable connection to the specific person whose authority is being exercised.
No Substitution for the Human
VULT Security carries the verified identity forward into the moments when the organization needs it.
Enrollment validates a government-issued identity document, matches the live person to its photograph, and uses liveness detection to establish the person’s participation. The verified identity is bound to a protected biometric template used for subsequent comparisons.
When an organization requests a protected VULTid authentication or authorization, VULTid requires fresh, real-time liveness, Proof-of-Presence, and server-side biometric matching to that enrolled identity. The device captures the interaction. The identity comparison uses the protected server-side reference, rather than the phone’s local biometric enrollment.
No substitution for the human means that possessing the account’s password, knowing personal details, or operating an already authenticated device does not satisfy this additional requirement. The protected workflow requires current verification of the person.
This does not ordinarily mean scanning a government-issued ID again. Enrollment establishes the verified identity; later checks verify that the same living person is participating. VULT Security’s platform overview describes this approach to verification at the moment of action.
The organization chooses where to require it. Once a workflow requires that verification, an earlier login cannot satisfy a later protected event.
Knowing Who Is Present Must Connect to What They Authorize
Return to the $25,000 transfer. Verifying the customer’s face is one part of the requirement. The customer must also see the relevant transfer details and explicitly authorize that particular movement of funds.
Otherwise, a valid identity check could be attached to the wrong action.
VULT Security calls the combined model Event-and-Identity-Bound Authorization: binding a verified human’s identity and real-time presence to their explicit authorization of one specific action, supported by a protected evidence record.
For the transfer, the event includes the relevant accounts, recipient, amount, and currency. The authorization applies to that event, is single-use, and must be checked by the executing system before the protected action proceeds. A material change outside the authorized scope requires a new authorization.
This principle extends established transaction-security practice. OWASP’s transaction authorization guidance recommends presenting significant transaction information, protecting it against modification, and enforcing authorization at execution. VULT Security brings the government-ID-linked human and fresh proof of presence into that relationship.
The organization still grants permissions. VULT Security verifies the person exercising them and binds their authorization to the action.
The Gap Appears Wherever an Account Can Change Someone’s Life
Money movement is an obvious starting point, but the need extends across the account relationship. A small settings change can determine who receives the next security notification, where the next payment goes, or who can recover access.
Protected event | What verified-human participation adds |
Login or sensitive system access | Fresh verification of the person linked to the organizational account |
Financial transfer | The authorized human’s participation, bound to the specified transfer |
Bank-detail or payroll change | Verification of the person authorizing the new destination |
Recovery or contact-information change | Verification of the person requesting the exact recovery or account change |
Privileged enterprise action | The authorized employee’s participation, bound to the particular command or change |
Records release | Verification of the authorized patient, customer, employee, or representative and the defined disclosure |
Each organization determines who has permission to act, including representatives and delegated personnel. VULTid verifies the person whose participation the workflow requires.
Account recovery deserves particular attention because it can change who has future access. If the recovery workflow accepts personal information as sufficient proof of the person, an attacker may exploit information that was originally collected to establish identity. Requiring fresh verification of the enrolled human at that point strengthens the connection to the account’s rightful user.
A Better Place for the Risk Engine to Send the Request
Organizations already have risk engines, decision trees, transaction monitoring, and access policies. Those systems decide when additional assurance is needed. VULT Enterprise gives them a verification and authorization step they can invoke at that moment.
An organization might require VULTid for every transfer above a defined threshold, every payroll-destination change, every sensitive recovery request, or every entry into a protected system. It can also request verification when existing controls identify an unusual event.
The integration must enforce the result before the protected operation proceeds. Alternate routes to the same operation need to honor the same requirement.
This fits a layered security program. The FFIEC’s authentication guidance emphasizes risk assessment, layered controls, and monitoring. Verified-human authorization adds a specific requirement within that program: the designated action needs the verified person’s current participation.
The organization’s existing controls determine when to ask. VULTid supplies fresh verification of the human and, where required, their authorization of the event.
Repeated Verification Should Not Create Repeated Identity Exposure
Bringing the human back into the workflow should not require a growing collection of face photographs and ID images.
By default, VULT Security does not store face photographs, face videos, or government-issued ID images. It validates the ID, matches the live person to its photograph, binds the verified identity to a protected, non-reversible biometric template, and retains that template for future comparison.
Original face photographs, videos, and ID images are retained only when an organization explicitly requests it, such as a financial institution requiring particular records. The template remains biometric data and is protected using homomorphic encryption and rotating keys.
An organization can receive the verification result and relevant authorization evidence without maintaining its own biometric repository. This follows the privacy principle described in NIST’s identity-proofing guidance: minimizing unnecessary personal information reduces the information exposed to unauthorized access or use.
The protected evidence record preserves the connection between the person, their presence, the event, and their authorization. Linked execution records can then show what happened afterward. That gives an organization a stronger basis for investigating a dispute and gives the individual a record of the limits of what they authorized.
Make the Identity You Verified Matter After Enrollment
The value of verifying a person should extend beyond opening the account. It should help protect the customer when money moves, the employee when payroll changes, and the account holder when someone tries to redirect access.
A practical starting point is to identify the events that could materially affect someone financially, legally, reputationally, or physically. For each event, ask whether the workflow freshly verifies the person and captures their authorization of the precise action.
Where the answer is an accepted credential, a familiar device, or information somebody knows, there is an opportunity to require the verified human.
VULT Security makes that requirement part of the workflow. The person established at enrollment remains connected to the moments when their identity and authority matter most.
You went to the trouble of verifying the person. Keep the person in the decision.



