Topic starter
21/08/2026 5:01 pm
TL;DR: Agentic AI now extends beyond prompts into tools, databases and code, AccuKnox says, so the security problem moves to the cognition layer. Runtime monitoring and per-call authorisation become the controls that limit damage when agents step outside scope.
Editorial analysis by NHI Mgmt Group, based on content published by AccuKnox: “Securing Agentic AI In 2026: The Journey From Code To Cognition”.
Key questions
Q: Why do AI agents create more risk than traditional automation?
A: AI agents create more risk because they can interpret context, choose actions, and invoke tools autonomously.
Q: How do security teams know if agentic AI controls are failing?
A: The main signs are session drift, repeated retry loops, unauthorized tool calls, and behaviour that diverges from the documented task sequence.
Q: What breaks when agentic AI is governed like a normal application account?
A: Security controls break down because agentic systems do not behave like fixed-function applications.
Practitioner guidance
- Verify every agent identity Assign each AI agent a distinct identity instead of using a shared service account or a human developer's permissions.
- Scope MCP access by role Authorize each tool call based on the agent's role and the sensitivity of the target data, not on a generic application trust decision.
- Add runtime behavioural controls Monitor for anomalous actions such as unexpected shell execution, new external connections, or database activity outside the agent's normal task pattern.
Bottom line: Agentic AI shifts security from prompt hygiene to governing the cognition layer where tools, data, and code execution converge.
Glossary terms: Cognition Layer, Agent Identity, Object-Scoped Authorisation, Runtime Behaviour Monitoring
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 3 days ago by NHI Mgmt Group
21/08/2026 5:16 pm
Cognition is becoming the new identity boundary: Agentic AI breaks the old assumption that identity ends at login and starts again at a tool request. Once the system can decide which action to take, the real security question is whether that decision is being made inside a governed identity boundary. That shifts the control plane from access checkout to action approval, which is a material change for IAM and NHI governance.
A few things that frame the scale:
- 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.
- 67% of organisations still rely heavily on static credentials despite the risks they pose to agentic AI deployments, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: What should organisations do when an AI agent requests data or actions it is not permitted to use?
A: The correct response is to enforce the policy at the point of request, before the model or downstream tool receives the data. The decision should be recorded with the request, purpose, outcome, and governing policy so the organisation can prove why the action was denied or redirected. That evidence supports auditability, review, and future policy tuning.
👉 Read our full editorial: Agentic AI moves enterprise risk into the cognition layer
This post was modified 3 days ago by NHI Mgmt Group