Back to blog

AI Passport and agent delegation: what a signed credential still needs to prove

3 min read
AI Passport and agent delegation: what a signed credential still needs to prove

Sources checked: . FailSafe Research.

A credential can accurately describe a permission while an application applies that permission too broadly. ServiceNow's AI Passport announcement describes signed runtime authority, scoped delegation and revocation, with NVIDIA as a design and launch partner. The enterprise acceptance test should follow that authority all the way to a business action.

Translate authority into a permitted result

Select one realistic workflow, such as preparing an internal change request or accessing an approved test record. Specify the identity that initiates it, the agent that executes it and any downstream delegate. Then state the narrow action each component may perform.

Use a permission record that a reviewer can compare with the actual tool request. Avoid granting broad administrative access simply to make a proof of concept easier to demonstrate. That choice would remove the boundary the buyer needs to evaluate.

Watch what survives delegation

A downstream task should retain the restrictions relevant to its purpose. Review whether the delegated identity gains a broader resource set, longer lifetime or different action rights than the initiating workflow intended. Test these properties with approved identities and harmless objects.

Where an integration transforms the credential or switches to a service account, include that transition in the evidence. A valid signature at the first step does not describe the entire chain of authorization decisions.

Revoke and then inspect the resource

Agree an intervention point and remove the test authority through the designated control. Observe what the target service actually accepts afterward, including queued and delegated work. Keep cancellation, revocation and reversal of prior effects as separate results.

Retest legitimate access after the change. An assessment should make it possible to distinguish a safely restricted workflow from a broken one. Record unavailable telemetry rather than filling the gap with an assumption about the product.

Buy assurance for your deployed chain

FailSafe SWARM connects authorized testing to reproducible evidence, engineering guidance and retesting. That approach is useful when an enterprise wants to evaluate how its own agent-authority stack behaves across boundaries. Agree the access and observation needed for each component before the engagement.

This is a scoped assessment proposition, with AI application testing and local inference options where sensitive evidence requires them. ServiceNow's announcement describes its product; it does not establish results for your configuration or a FailSafe partnership. Ask for a demonstration of the actual workflow and the resulting evidence.

Source review, 2 November 2026: ServiceNow AI Passport announcement. Product availability and implementation details should be checked directly with the supplier.

Questions & answers

Questions about this topic

Direct answers to common questions about this page.

It establishes properties of the credential. The consuming application and delegated services still need to enforce the intended action and resource boundaries.

Preserve the intended permission, each identity transition, the operation observed at the target and the behavior after revocation.

Put this guidance to work

Bring the actual delegation chain and target action into an AI application assessment. Agree the interfaces and observations needed for a useful conclusion.

Startup offer: $999 USD for 250 credits and one authorized black-box run. Sign in to SWARM before Stripe checkout. Custom scope and sovereign deployments are separate.

Assess agent authority boundaries