Skip to content
IdentitéTrust starts here
English
EnglishEspañolPortuguês
Contact

Solutions / Digital trust and AI

When imitation gets easier, trust needs a stronger basis.

AI changes who can appear convincing and what software can do on our behalf. Identité® addresses two distinct moments: verifying the requesting service and asking a person to approve a sensitive action.

Explore the two trust questionsTry an agent-action approval
An illustrated agent workflow pauses for a person to approve on a phone
Software prepares. The person decides.

The imitation may be someone your user trusts.

Consider a message that appears to come from a bank, a physician, an executive or a public agency. The person behind the account may be real; the party asking them to act may be the imitation.

The question changes from “Is this really our user?” to “How does our user know it is really us?” FDA answers at the authentication interaction: the enrolled app verifies the authentication server and the person checks the request. It provides a basis for service verification when a convincing appearance is not enough.

Full Duplex AuthenticationThe King Arthur story

A real agent may still need your approval.

Now consider an authorized AI agent preparing a payment or another sensitive business action. The agent can prepare the work while the responsible person keeps the final decision.

The system owner defines the approval checkpoint. NoPass™ takes the request to the person’s phone, and the application waits for the device confirmation before proceeding.

Operation approval

Two questions. Two useful responses.

Two questions. Two useful responses.
SituationQuestionNext step
A convincing request from an apparent institutionHow does the person establish who is asking?Understand the FDA relationship and service verification.
A sensitive action prepared by an authorized agentDoes the responsible person approve this operation?Connect a NoPass approval checkpoint to the application.

Explore the approval experience.

Explore an agent-action approval below: the application pauses, the person checks the request on both screens, and a decision on the phone determines what happens next.

Contact

AI-agent action approval · interactive example

A sensitive operation is ready.

The application sends a NoPass approval request to the person responsible. Start the request in the application.

Your application
Example application request

Agent-prepared supplier payment

Recipient
Example supplier
Amount
USD 1,250.00
Reference
PAY-1042
NoPass
Enrolled deviceReady when you are.

Try the highlighted button or use the controls below.

Review a human-approval checkpoint

Follow the thinking behind the approach.

Explore the blog

Where would you like to go next?

Enterprise

Help employees reach their work and keep sensitive decisions with the people responsible. NoPass brings mutual authentication and explicit operation approval to enterprise workflows.

What is digital trust?

Digital trust is confidence, supported by evidence and accountable controls, that a digital interaction will behave as expected and respect its agreed boundaries. Identity is one input. Privacy, security, limited authority and recovery also matter.

A convincing interface or an authenticated account is insufficient on its own. Ask which participant is acting, what evidence supports that identity, what it may do and how an error or misuse will be contained.

How should an AI agent authenticate and obtain authority?

Give the workload a managed identity, short-lived credentials where supported and only the permissions needed for its task. Keep the deploying owner, delegated user and executing workload distinguishable. The application must enforce scope and policy at each sensitive operation.

A human checkpoint is appropriate where consequences exceed delegated authority: for example, releasing a high-impact payment or exporting sensitive records. Define thresholds with the workflow owner. Routine low-risk actions can remain within a bounded delegation; prompting for everything can weaken attention.

NoPass can provide the documented human approval checkpoint in a supported integration. Generic agent credentials, continuous monitoring, tool isolation and policy enforcement require separate systems. OWASP excessive-agency guidance · Review operation approval.

Human approval: present scope and future vision

Current documented scope: enrolled-user/configured-server flows and supported application checkpoints. Review the supplied request and keep application policy in control of execution.

Agent identity, delegated permissions and continuous monitoring complete the wider AI architecture; these need their own controls alongside a supported human checkpoint.

Human approval: present scope and future visionView full screen