ServiceNow announced AI Passport on Oct. 15, 2026, with availability expected in the fourth quarter. The planned product would give enterprise teams a way to define and enforce the authority of software agents while they execute work, rather than relying only on records of what happened afterward.
Preview
What is planned for this quarter
In its announcement, ServiceNow describes AI Passport as a signed credential used to check an agent’s permitted scope at runtime. The company names Nvidia as a design and launch partner for an enforcement implementation using its Open Agent Safety Platform.
ServiceNow also expects shadow AI detection and AI Cost Management to become available in the fourth quarter. These are expected release windows, not confirmation that the products are generally available today. No exact launch date is supplied.
The company’s claims describe the intended design and behavior. They do not establish that the controls have been independently validated across every customer environment or third-party agent.
A demonstration shows the intended boundary
SiliconANGLE’s reporting describes a demonstration in which a customer-service agent could process refunds below $25. An $18 request proceeded, while a $40 request was rejected because it crossed a threshold requiring human review.
The publication also reports graduated responses, including pausing an agent, restricting its permitted tools or deactivating credentials. Those examples help explain the product’s intended operation; a controlled demonstration is not evidence that all real-world failures will be prevented.
For operations leaders, the important distinction is between observing an agent and limiting its authority before an action completes. A log can document a problem without having stopped it. A permission check needs to operate where the consequential action is attempted.
Questions for an enterprise evaluation
When the planned capabilities become available, a useful evaluation would test how a business rule becomes an enforceable limit. The refund example makes that question concrete: who sets the threshold, what happens above it and what record identifies the person responsible for approving an exception?
A second question is how quickly a changed permission reaches an active workflow. Buyers should seek evidence about revocation and exception handling in their own environment, not assume that a signed credential alone answers every operational question. Testing should include the failure case, not just a permitted request that completes successfully.
This preview identifies evaluation questions, not a security certification or a recommendation to deploy. The announced release window provides a planning point; product availability and demonstrated behavior will need to be checked separately.