1. Frame the decision and its operating boundary
Define mandatory criteria
Before comparing products, write down the security and business requirements a candidate must meet. Separate mandatory requirements from weighted preferences. Evidence for a mandatory item must be reproducible; a sales slide or vague roadmap promise cannot earn a pass. In this setting, For AI agents with access to business tools, the real case is an assistant offered permission to update a customer account after reading a support message. Start with ticket ID, requester identity, tool-call trace and record change history and document the permission and data boundary that permits a change.
Any sensitive workflow needs a reliable denial path as well as a permitted one. Run an access request from an identity outside the permitted role. The business action should be denied at the destination and the reason visible in the audit record. Separate staff, supplier and automated identities. Each should have the minimum scope necessary to complete the approved task, and privileged access needs a specific expiry and owner. Where the result is unsafe, disable the agent’s write tool, revoke its credential and reconcile affected records. The risk owner should see the denial or correction evidence before approving further access. Before leaving the 1. frame the decision and its operating boundary stage, confirm who can repeat the test and how the next team will obtain the evidence.
Acceptance criteria should be agreed before the preferred configuration is demonstrated. Test a normal request and then include a misleading request inside the source document and verify that the tool refuses the unapproved action. Classify the result as accepted, safely refused, incomplete or incorrectly accepted, rather than reporting a single success percentage. An independent business participant should challenge at least one negative result and confirm whether the authorised workflow can still be completed safely. The record should be understandable to the customer-service lead, AI application owner and identity administrator, who can agree a pass, a revision or a pause based on observed outcomes. Before leaving the 1. frame the decision and its operating boundary stage, confirm who can repeat the test and how the next team will obtain the evidence.
Users should be able to tell whether the business task succeeded, not only whether the application responded. Define the first response, the named escalation owner and the information the next support team requires. An unresolved handoff should not disappear when the ticket moves between queues. Review repeated service failures for a common dependency or unclear ownership. Changes should produce a better diagnostic or decision path, not just another generic checklist. Where the outcome affects authorised data use, correct approvals and a reliable business outcome, the process owner and business reviewer should confirm that the user’s task can safely resume. Before leaving the 1. frame the decision and its operating boundary stage, confirm who can repeat the test and how the next team will obtain the evidence.
