AI Governance Institute
← News
Research2026-09-19

Only 17% of Firms Secure Agentic AI Tool Access in Dev Standards

Source

AI Cyber Benchmark 2026: Governance matures, ...

Wavestone

Via Wavestone

What happened

Wavestone published its AI Cyber Benchmark 2026, a global study measuring organizational maturity across AI security and governance practices. The report found that one in three organizations has incorporated agentic AI into its governance frameworks, but fewer than one in five has extended secure development standards to cover AI tool and function access. That 16-percentage-point gap between governance posture and control implementation is the benchmark's central finding. Wavestone characterizes the weakness as concentrated in three areas: tool permission design, secure development standards, and operational governance for autonomous systems. The findings arrive as enterprise deployments of agentic AI are accelerating, with multiple recent incidents confirming that unsecured tool access is an active attack surface.

Why it matters

  • ·The gap between declared governance coverage and actual control implementation creates false assurance. Compliance programs that rely on policy attestation without verifying secure development practices will misrepresent an organization's real exposure when audited.
  • ·Tool permission design is now a documented enterprise control weakness. Findings like these, combined with a growing body of incident data on agentic AI trust boundary failures, mean regulators and insurers are likely to treat absence of secure-access standards as a material gap.
  • ·Organizations in regulated sectors face compounding risk. Frameworks such as the NIST Artificial Intelligence Risk Management Framework Playbook expect controls to be operationalized, not just documented. A benchmark showing 83% non-coverage of secure tool access will inform both regulatory examination and third-party audits.

Stay ahead of stories like this

Get every Global AI governance development like this one, plus the rest of the week's developments. Every Thursday.

Free every Thursday. Unsubscribe anytime.

Governance controls affected

What to do now

  • ☐Audit your secure development standards to confirm they explicitly address AI tool and function access permissions for any agentic system in development or production.
  • ☐Map governance framework coverage against actual control implementation: identify every agentic deployment listed in policy documents and verify corresponding technical controls exist.
  • ☐Review tool permission manifests for all deployed agents and confirm each follows a least-privilege design rather than broad default access.
  • ☐Add agentic AI tool-access standards as a required checkpoint in your AI deployment readiness gate process before any new agent goes to production.
  • ☐Include agentic secure development coverage as a standing item in the next vendor due diligence cycle for any third party supplying or operating AI agents on your behalf.

What to watch next

Compliance teams should monitor whether the Wavestone maturity gap triggers updated expectations from financial regulators and cyber insurers, both of whom increasingly reference benchmark data in examination guidance and underwriting criteria. The Five Eyes Guidance on the Careful Adoption of Agentic AI Services has already set sandbox and logging as baseline controls; further prescriptive guidance on secure development standards for agents is likely as incident frequency rises. Organizations that have not closed the tool-permission gap before the next wave of regulatory guidance arrives will face a harder remediation timeline.

Related Coverage

Standards2026-10-21

CSA Two-Gate Model Splits Tool Access From Tool Use for Agentic AI

The Cloud Security Alliance published guidance proposing that enterprises separate two authorizations. The first covers giving an AI agent access to a tool. The second covers letting that agent use the tool on a specific resource. The model adds a context-sensitive check covering identity, parameters, risk level, and current workflow state before any action runs. Organizations running AI agents that can call external tools, move data, or take system actions need to review how their current permission controls are structured.

Research2026-10-28

ChatGPT GitHub Connector Flaw Could Expose Private Repository Secrets

A disclosed vulnerability in ChatGPT's GitHub Connector allowed a malicious public repository to plant hidden instructions that the AI assistant could follow. Those instructions could cause ChatGPT to write code files into a separate private repository and surface sensitive configuration values stored there. The flaw points to missing permission separation and missing human approval requirements for cross-repository write actions.

Research2026-10-27

Google Cloud's Agent Compute Engine Exposes Non-Human Identity Gap

Google Cloud published implementation guidance for enterprise agentic AI governance, introducing Agent Compute Engine alongside controls for agent registries, unique agent identities, least-privilege access, and centralized policy enforcement. The guidance addresses how dynamic interactions among agents, tools, models, and data create compliance blind spots. Organizations running AI agents in production need to assess whether their current AI inventories and access controls cover non-human identities and agent-to-agent activity.