Topic starter
27/10/2026 7:11 pm
TL;DR: Approov reflects on RSAC 2026 and argues that agentic traffic is reshaping enterprise security, with less than 10% of total volume already proving disproportionately influential. The post says identity security now has to verify legitimate action, not just origin, because trusted computing, cryptographic proof and least privilege are becoming the baseline for AI-driven environments.
Editorial analysis by NHI Mgmt Group, based on content published by Approov: “RSAC 2026: From Hype to Agency”.
By the numbers:
- agentic traffic is still less than 10% of total volume
Key questions
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 least-privilege models need to change for agentic AI?
A: Least privilege still matters, but agentic AI changes the timing and granularity of enforcement.
Q: How should security teams verify identity when AI-generated profiles look authentic?
A: Security teams should stop relying on visual realism or message quality as proof of identity.
Practitioner guidance
- Separate agent governance from generic bot monitoring Treat AI agents, automation and ordinary bots as different control classes.
- Bind authorisation to each action request Move policy decisions closer to the transaction so that an agent, workload or user is checked against purpose, scope and session context before the action runs.
- Inventory where cryptographic proof is still missing Map the systems that rely on channel trust, static tokens or weak origin checks and identify where stronger proof of entity and intent is required.
Bottom line: Agentic traffic is forcing security teams to govern behaviour at the action level, not just authenticate the source of a request.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →