TL;DR: Behavioural drift, not broken permissions, is the sharper lens for AI agent insider risk, DTEX reports. Security teams need outside evidence from hosts, gateways and identity logs before trust is extended or maintained.
Editorial analysis by NHI Mgmt Group, based on content published by DTEX: “The Insider Risk Playbook Nadella Is Pointing at Already Exists”.
Key questions
Q: Why do AI coding agents increase insider risk so quickly?
A: AI coding agents increase insider risk because they amplify a user’s speed, persistence, and reach without requiring the same level of expertise.
Q: How can security teams tell whether an AI agent actually behaved as instructed?
A: They need independent evidence from hosts, gateways and identity logs, then compare that evidence with the instruction chain and the agent’s own account.
Q: What breaks when AI agents are not governed at runtime?
A: Without runtime governance, an agent can shift behaviour after provisioning and still execute actions that were never reviewed in context.
Practitioner guidance
- Implement behavioural trust review for AI agents Define a review process that compares agent actions with the original human instruction, the gateway record and the host effect before trust is extended.
- Correlate person and agent activity Join user device telemetry, sandbox activity and API outcomes so analysts can see collusion, compromise or request drift across the full workflow.
- Separate entitlement from trust decisions Keep authorisation checks in place, but add an independent decision on whether the observed workflow still matches approved intent.
Bottom line: AI agents can remain properly authorised and still create insider-risk exposure when the full workflow diverges from the human intent behind the request.
Glossary terms: Behavioral Trust Layer, Human-Agent Workflow, Insider Risk Management, Delegated Authority Model
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Behavioral trust is now the decisive control plane for agentic work: identity and access controls can still be correct while the workflow is wrong. That is because an authorised agent can complete a sequence that no human would have approved end to end, especially when tool use, timing and coordination happen at machine speed. The implication is that trust decisions must move from provisioning time to runtime evidence, with behavioural verification governing whether the workflow remains acceptable.
A question worth separating out:
Q: How should organisations govern agent and human authority together?
A: They should treat them as one operational control problem. The user's entitlements, the agent's scope, the workflow context and the service account path all need to be evaluated together so that no combination of access creates an unreviewed privilege path.
👉 Read our full editorial: AI agent insider risk depends on behavior, not permissions