TL;DR: AI risk in this post looks like insider risk because agents and copilots can move across trusted systems without staying inside one prompt, according to DTEX. Workflow lineage and identity context are what let security teams decide whether that activity created exposure.
Editorial analysis by NHI Mgmt Group, based on content published by DTEX: “Identify the AI Tools and Agents You Don’t Know You Have with DTEX AI Risk Management”.
Key questions
A: The common mistake is assuming approved tool lists are enough.
Q: What are the signs that an AI agent is acting like a privileged non-human identity?
A: The clearest signs are multi-step execution, access to knowledge bases or APIs, externally visible output and delegated authority that is not tied to a human session.
Q: How should security teams govern AI-enabled workflows that can act on their own?
A: Treat them as identity-governed execution paths, not just software features.
Practitioner guidance
- Build an AI workflow inventory Map where AI is used, which accounts initiate it, what data it touches and what actions follow across browsers, copilots, APIs and agents.
- Classify shadow AI by behaviour, not naming Look for recurring use patterns, personal-account access and sensitive uploads, then score the workflow rather than the tool label.
- Add lineage to AI investigations Preserve prompt lineage, data sources accessed, actions taken and downstream destinations so investigators can reconstruct an AI sequence end to end.
Bottom line: AI risk now behaves like insider risk because agents and copilots can move across trusted systems, not just generate text.
Glossary terms: AI Risk Management, Shadow AI, Agentic AI, Case Lineage
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
AI risk management is becoming a workflow control problem, not a prompt monitoring problem. The article correctly treats AI activity as a chain of behaviour that spans initiation, data access, output and external movement. That changes the governance question from “what was the prompt?” to “what sequence of actions actually occurred, and who or what was responsible at each step?” Practitioners should align AI oversight with the full workflow, not the first visible event.
A few things that frame the scale:
- Organisations that describe themselves as confident in their AI deployment actually experience a 72% security incident rate, compared to 33% for those who remain cautious, according to the 2026 Infrastructure Identity Survey.
- Only 13% of organisations feel extremely prepared for the reality of agentic AI despite the majority racing toward autonomous adoption, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: Should organisations prioritise AI agent governance before expanding autonomous workflows?
A: Yes. The article shows that AI creates both faster discovery and deeper trust exposure, so scaling autonomy without governance multiplies risk. Teams should establish ownership, visibility, and behavioural control first, then expand only where they can explain the agent’s access, decisions, and downstream effects.
👉 Read our full editorial: AI risk management needs workflow-level oversight for agents