Skip to content
VULT SecurityGet started

Bots Can Look Human. The Internet Needs a Way to Know the Difference.

How verified identity, real-time presence, and action-specific approval help establish who is truly behind an online interaction.

What is a verified-human? VULT Security verifies a person against government-issued identity evidence, confirms their presence in real time and binds their authorization to a specific action.

An account can have a convincing profile, fluent messages and a history of ordinary activity without telling an organization who is actually using it. When that account requests a sensitive change, the system may recognize its credentials and device while still lacking fresh evidence that the person associated with it is participating. A familiar account can conceal a very different actor.

AI makes appearances less dependable. The FBI has documented criminals using generated text, fabricated images, cloned voices and synthetic video to support fraud and impersonation. For organizations trying to distinguish a customer from an impostor, a convincing conversation or realistic image is an increasingly difficult place to put their trust.

The internet needs a practical way to establish which real person is participating when an action matters. That is the purpose of a verified-human identity: connecting a verified person to their activity, with fresh evidence of their presence when an organization requires it.

What Is a Verified-Human?

At VULT Security, a verified-human is a real person whose identity has been established by validating a government-issued identity document, matching the person’s live face to the document’s portrait and checking liveness. The resulting identity is bound to that person through a protected biometric template, creating a reference for future verification.

These checks address different questions. Document validation examines the identity evidence; face matching connects the person presenting it to the portrait; liveness checks assess whether a living person is participating. NIST’s identity-proofing guidance similarly distinguishes validating evidence from verifying that the applicant is its rightful owner, and includes requirements for biometric comparison and presentation attack detection.

VULTid is VULT Security’s reusable verified-human identity. Once established, it allows the person to return and demonstrate that they are the same human linked to the verified identity. An organization can then require that fresh verification at the particular moments when it needs the person’s participation.

Looking Human and Proving Who Is Present Are Different Tests

Bot detection is essential to operating online services. Cloudflare describes bots as software that performs automated tasks, including activity that imitates or replaces human behavior. Traffic analysis and bot-management systems help organizations distinguish harmful automation from legitimate activity, including useful bots.

CAPTCHAs assess interactions to help distinguish people from automated software. Passing such a challenge does not establish a person’s government-verified identity or connect them to the owner of a particular account. An interaction can appear human without answering the organization’s more consequential question: which person is here?

Those distinctions matter when someone requests account recovery, changes banking instructions or asks for sensitive records. Bot detection can identify suspicious activity around the request. Verified-human identity gives the organization a way to check the person behind it.

Verification Has to Reach Beyond Enrollment

An identity check at account opening establishes evidence about the applicant at that time. Months later, the account may return through a password, passkey, one-time code or existing session. The earlier identity check remains part of its history, but it does not establish who is participating in the current action.

NIST’s Digital Identity Guidelines distinguish identity proofing from authentication, which verifies possession and control of authenticators associated with an account. That distinction helps explain why successful authentication and fresh verification of the government-ID-linked human are different requirements.

VULTid begins with document validation, live face matching and liveness checks during enrollment. At every protected event afterward, it requires fresh real-time liveness, Proof-of-Presence and server-side biometric matching against the protected template bound to that verified identity. The person ordinarily does not need to scan their ID again; the system checks that the same person is present now.

The organization determines which events require this assurance. Once a workflow requires verified-human authorization, an earlier enrollment, a familiar device or an active session does not satisfy the requirement for the current event. The person must participate again.

The Organization Keeps Its Accounts and Permissions

A verified-human identity works alongside an organization’s existing relationships. A bank still maintains its customer accounts, an employer still assigns roles, and a healthcare provider still determines who may access a record. VULTid connects the verified person to the relevant organizational identifier without taking over those permission decisions.

This is what it means for the human to become the key. The identifier locates the account and its permissions, while fresh verification establishes the person exercising them. No substitution for the human means that information associated with the person is not accepted in place of their live participation at a protected event.

Question

Organization’s role

VULT Security’s role

Which account applies?

Maintains the account and its identifier.

Connects the verification request to the associated VULTid.

What may the person do?

Grants and manages permissions.

Verifies the person exercising those permissions.

Who is present?

Requests verified-human assurance for designated events.

Confirms the person through fresh liveness and server-side biometric matching.

What is being authorized?

Defines and presents the exact action.

Binds the verified human’s explicit authorization to that event.

May the action proceed?

Applies current permissions, risk rules and execution policy.

Returns the verification result and protected authorization evidence.

That division gives an organization stronger evidence about the person without changing who governs its business. VULT Enterprise brings verified-human authorization into integrated workflows while existing identity, access and risk systems continue performing their roles.

One Verified Identity Can Serve More Than One Organization

People already maintain relationships with many organizations. Reusing a VULTid allows those relationships to recognize the same verified person without requiring a separate VULTid for every bank, employer or platform. Each organization maintains its own accounts, permissions and records; using the same identity does not give one organization access to another’s customer information.

This also changes how an organization can address duplicate accounts. Different email addresses, usernames or devices do not necessarily represent different people. When accounts are linked to the same VULTid, the organization can recognize that relationship and apply its policy on multiple accounts. Duplicate-enrollment checks can also help identify attempts to establish another verified identity, with potential matches reviewed through the appropriate process.

The policy remains the organization’s choice. A business might permit separate personal and professional accounts while prohibiting duplicate accounts used to evade restrictions or claim the same benefit repeatedly. Verified identity gives it a stronger basis for enforcing that distinction than counting credentials alone.

Presence Must Be Bound to the Action

Knowing who is present becomes more useful when that evidence is connected to what the person authorizes. Consider a platform changing the email address used for account recovery. A fresh identity check establishes the person’s participation, but the authorization also needs to identify the new address. Otherwise, evidence from a legitimate interaction could be associated with a different change.

At VULT Security, Event-and-Identity-Bound Authorization binds a verified human’s identity and real-time presence to their explicit authorization of one specific action, supported by a protected evidence record. The person is presented with the material details, and the resulting authorization applies to that event alone. A material change requires a new authorization.

The system carrying out the action must validate that the authorization is valid, unused and bound to the exact event, alongside the organization’s current permissions. This makes the requirement enforceable at execution. The protected evidence record can then support accountability and traceability by connecting the verified person, their presence and the event they authorized.

How Verified-Human Identity Helps Organizations Prevent Fraud

For organizations, the value lies in applying this requirement where impersonation or unauthorized activity would cause harm. Verified-human infrastructure can support several practical controls:

  • Account creation and duplicate-account controls: Establish the person behind a new relationship and help enforce policies on multiple accounts.
  • Account recovery and takeover prevention: Require fresh verification of the linked person before designated recovery steps or sensitive account changes.
  • Workforce and privileged actions: Confirm the verified employee behind payroll changes, access changes and other protected operations.
  • Transactions and sensitive records: Bind the authorized person to a specific transfer, disclosure, consent or records change.
  • AI-agent activity: Require the verified human’s authorization before an agent executes a designated consequential action.

People and organizations also deliberately give AI access to useful work. An assistant may be asked to prepare a request, research a decision or organize information. When that work reaches a protected action, VULT Security provides a point at which the verified human must appear in real time and personally authorize the exact event. The executing system enforces that boundary, rather than leaving the agent to decide whether human participation is necessary.

This approach allows automation to continue within its permitted scope. The organization chooses where fresh human verification is required and makes that requirement part of the workflow. Successful onboarding does not automatically make all later activity human-directed; each protected event receives its own verification and authorization.

Why Device Biometrics Answer a Different Question

Device biometrics can provide strong protection for a phone and the credentials it holds. Apple explains that Face ID compares captured facial data with facial data enrolled on the device, while applications receive an authentication result rather than access to that facial data. The local match has a defined purpose, but by itself it does not establish a connection to the government-issued identity used for an organizational account.

VULT Security’s reference is the verified identity established through government-ID validation and live face matching. At each protected event, the device captures the person while liveness assessment and biometric comparison occur server-side against that identity’s protected template. Possession of the expected phone does not replace the requirement to verify the human, and changing phones does not create a new person or a new organizational relationship.

Stronger Identity Without a Collection of Face Photos

Stronger verification should limit how much identity information organizations need to retain. VULT Security validates the government-issued ID, matches the live person to its portrait and binds the two through a protected, non-reversible biometric template. By default, VULT Security does not store face photographs, face videos or government-issued ID images.

The template is retained for future comparisons and protected using homomorphic encryption and rotating keys. It remains biometric data and is protected accordingly. Original face photographs, videos or ID images are retained only when an organization explicitly requests that retention, such as a financial institution requesting ID images for its recordkeeping.

The organization can receive the verification result or identity attribute needed for its interaction without maintaining its own biometric template repository. An age gate may need confirmation that a person meets an age threshold; another service may need a verified name or confirmation that the account owner is present. These are different requests and should involve only the information required for the purpose.

People should be able to prove who they are while retaining control over how their identity is shared. Privacy and accountability can work together when an organization receives the evidence needed for its decision without routinely collecting the original images behind it.

A Safer Internet Starts With the Person

Organizations will continue to interact with people, software and software acting on people’s behalf. The useful security boundary is the point at which an action requires a particular person’s participation. Requiring fresh verification there gives an organization evidence it can connect to the event, rather than relying solely on the appearance of legitimate activity.

VULT Security’s focus within cybersecurity and identity security is human digital identity. Its category, Event-and-Identity-Bound Authorization, uses verified-human infrastructure to support fraud prevention and authorization accountability. The objective is practical: establish which person was present and what that person personally authorized.

Applied across banks, employers, healthcare providers, government services and digital platforms, this model can help reduce opportunities for impersonation and unauthorized actions. Those protections matter because identity fraud can harm people financially, legally, reputationally or physically. Broader adoption would put fresh human verification at more of the moments where those harms can begin.

The internet needs to make that distinction dependable. When an organization requires a person’s authorization, the interaction should return to the verified human and the precise event they are being asked to authorize. That is a stronger foundation for trust in an environment where looking human is becoming easier to imitate.


Frequently Asked Questions

What is a verified-human?

At VULT Security, a verified-human is a real person whose government-issued identity evidence has been validated and matched to their live face, with liveness checks. That identity is bound to a protected biometric template so the same person can be verified again at future protected events.

How can organizations distinguish real people from bots and AI agents?

Bot detection helps assess whether activity appears automated. VULT Security adds fresh liveness and server-side matching to a government-ID-verified identity when the organization requires a particular person. For a protected action, that person’s explicit authorization is also bound to the event.

Can a CAPTCHA verify someone’s identity?

A CAPTCHA helps assess whether an interaction is likely to be automated. It does not validate a government-issued ID, identify the rightful account owner or establish who participates in a later action.

Does VULTid require a new ID scan every time?

Ordinarily, no. Enrollment establishes the verified identity. Every protected event then requires fresh real-time liveness, Proof-of-Presence and server-side biometric matching to that identity.

What does it mean for the human to become the key?

The organization uses its identifier to locate the account and permissions, then requires the linked person’s live participation at a protected event. VULT Security verifies that person and binds their authorization to the action. The organization retains its permission and execution decisions.

Can the same VULTid work with multiple organizations?

Yes, across participating integrations. Each organization establishes its own relationship with the person and maintains its own accounts, permissions and records. Reusing the identity does not share one organization’s customer records with another.

How does verified-human identity help address duplicate accounts?

Accounts connected to the same VULTid can be recognized as belonging to the same person, even when their usernames or contact details differ. Duplicate-enrollment checks can help flag additional attempts. The organization applies its own rules and reviews potential matches.

Does VULT Security store face photos, videos or government-ID images?

Not by default. VULT Security verifies the ID, matches the live face and retains a protected, non-reversible biometric template for later comparisons. Original images or videos are stored only when an organization explicitly requests retention. The template remains biometric data and is protected using homomorphic encryption and rotating keys.

What is Event-and-Identity-Bound Authorization?

It binds a verified human’s identity, real-time presence and explicit authorization to one specific action. The authorization is single-use, applies to the exact event and is supported by protected evidence of who authorized what.

Further Reading

Explore VULT Security’s capabilities for the broader identity, privacy and authorization model. View the full capability and competitor comparison for the detailed feature and assurance assessment.

Sources

  1. FBI IC3: Criminals Use Generative Artificial Intelligence to Facilitate Financial Fraud
  2. NIST SP 800-63A-4: Identity Proofing and Enrollment
  3. Cloudflare: What Is a Bot?
  4. Cloudflare: How CAPTCHAs Work
  5. NIST SP 800-63-4: Digital Identity Guidelines
  6. Apple: About Face ID Advanced Technology