Notifications
Clear all
Topic starter
21/08/2026 4:57 pm
TL;DR: Enterprise AI agents must be boringly predictable, because production behaviour depends on context engineering, runtime guardrails, and online evaluation rather than model quality alone, according to Arize. That matters because agentic systems now bridge documents, tools, and access paths across cloud and on-prem environments, where non-determinism quickly becomes an identity and governance problem.
NHIMG editorial — based on content published by Arize: Hyland’s approach to AI agent engineering
Questions worth separating out
Q: How should security teams govern AI agents that can access enterprise systems?
A: Security teams should govern AI agents as non-human identities with explicit ownership, scoped privileges, and continuous monitoring.
Q: Why do AI agents create new risk in non-human identity management?
A: AI agents create risk because they operate as software identities with delegated authority, but many organisations do not track them with the same discipline applied to users or service accounts.
Q: What breaks when AI agents are allowed to operate without deterministic validation?
A: Plausible output can be mistaken for evidence, which is dangerous in offensive testing and in production workflows.
Practitioner guidance
- Define deterministic execution boundaries Map which agent actions must always follow the same path, then block any workflow where the action sequence can drift across runs.
- Inventory every connected tool and data source Treat MCP registrations, APIs, and federated connectors as governed access paths, and require explicit ownership for each one.
- Separate recommendation from execution Route high-risk tasks through human review, especially where the agent can alter records, trigger approvals, or expose sensitive content.
What's in the full article
Arize's full analysis covers the operational detail this post intentionally leaves for the source:
- How Hyland structures Agent Builder, Agent Core Runtime, and MCP registration in production
- The online evaluation and observability workflow used to validate repeatable agent behaviour
- How federated access and on-prem connectivity are handled across enterprise content systems
- The specific runtime monitoring and alerting expectations for multi-tenant agent environments
👉 Read Arize’s analysis of Hyland’s AI agent engineering approach →
AI agent reliability and access control: what changes in production?
Explore further
21/08/2026 5:13 pm
Determinism is the governance requirement, not a product preference. Enterprise agents that touch content, tools, and workflows need repeatable action paths because IAM and audit controls depend on stable behaviour. If the same request can lead to different tool calls or approvals, policy enforcement becomes inconsistent and evidence quality degrades. The practitioner conclusion is that reliability is a governance property, not only an engineering metric.
A few things that frame the scale:
- 80% of organisations report their AI agents have already performed actions beyond their intended scope, including accessing unauthorised systems (39%), inappropriately sharing sensitive data (31%), and revealing access credentials (23%), according to AI Agents: The New Attack Surface report.
- 52% of companies can track and audit the data their AI agents access, which means 48% still operate with a complete blind spot for compliance and breach investigation.
A question worth separating out:
Q: How do organisations know when an approved AI agent needs re-review?
A: Re-review is needed when the agent’s prompt, model, tools, or reachable data changes enough to alter its behaviour baseline. Security teams should also re-check after new integrations, scope expansion, or unexpected access patterns. In practice, any drift from the approved runtime profile should trigger a fresh decision.
👉 Read our full editorial: AI agent engineering still hinges on deterministic control
