AI Governance Institute
← News
Research2026-07-26

Trend Micro Identifies Four Agentic AI Controls Enterprises Are Missing: Inventory, Least-Agency, Supply Chain, and Communication Monitoring

Source

Closing the Governance Gap in Agentic AI

Trend Micro

Via Trend Micro

What happened

Trend Micro published Closing the Governance Gap in Agentic AI, a research paper warning that agentic AI systems present a fundamentally different risk profile from conventional software because they can reason, plan, and take multi-step actions across enterprise environments without direct human observation at each step. The paper identifies four control gaps that existing governance programs typically fail to close: the absence of a structured agent inventory, the failure to apply least-agency principles that constrain agents to the minimum scope needed for a task, the treatment of AI tools and extensions as trusted software rather than supply-chain risks, and the lack of monitoring on the communication flows between agents as opposed to monitoring only endpoint outputs. This analysis joins a growing body of practitioner guidance on agentic risk, including IBM's Agentic AI Governance Playbook and Anthropic's CISO Playbook for Agentic AI, both of which have similarly emphasized identity, scope, and approval-gate controls. Trend Micro recommends that enterprises pair inventory and access constraints with explicit approval gates for any autonomous action that could have irreversible or high-impact consequences.

Why it matters

  • ·Agents operating without an inventory create an immediate audit and compliance gap: organizations cannot demonstrate control over systems they cannot enumerate, which becomes directly problematic under frameworks such as the EU AI Act Implementation Timeline and emerging sector-specific agentic rules signaled by regulators like the Bank of England.
  • ·The supply-chain framing for AI tools and extensions expands the vendor risk surface significantly, because a compromised or malicious plugin can inherit an agent's permissions and act at scale across enterprise systems, as illustrated by incidents like the Meta Sev-1 Agent Incident where authorization failures enabled unexpected lateral action.
  • ·Communication-flow monitoring between agents is an operationally new requirement that existing security information and event management programs were not designed to handle, meaning compliance teams may face a gap between what they attest to auditors and what their tooling can actually detect.

Governance controls affected

What to do now

  • ☐Conduct an agent inventory exercise to enumerate every deployed agentic system, including those embedded in third-party platforms, documenting owner, task scope, and permission set for each.
  • ☐Review agent permission configurations against a least-agency standard, confirming that each agent can access only the data sources, APIs, and actions its specific task requires and that no standing broad permissions remain.
  • ☐Classify all AI tools, plugins, and extensions connected to agentic systems as supply-chain risk items and route them through your existing third-party AI risk assessment process.
  • ☐Extend your monitoring architecture to capture inter-agent communication flows, not only endpoint outputs, and establish behavioral baseline thresholds that trigger review when agent activity deviates.
  • ☐Define and document which autonomous agent actions require a human approval gate before execution, with particular attention to actions that modify data, initiate financial transactions, or are difficult to reverse.

What to watch next

Regulatory pressure on agentic AI controls is accelerating from multiple directions. The DHS and CISA guidance on AI agents in critical infrastructure is likely to inform sector-specific rulemaking, and the Bank of England's signals on bespoke agentic AI rules suggest that financial services firms will face mandatory autonomy controls within the next regulatory cycle. Compliance teams should also watch for whether the NIST AI RMF Playbook is updated to incorporate agentic-specific guidance, and monitor whether the Illinois AI Safety Measures Act audit requirements, which took effect alongside China's agent rules, produce early enforcement patterns that set a de facto standard for agent documentation and inventory practices.

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.

Powered by Buttondown.

Related Coverage

Standards2026-09-15

Chrome's WebMCP Guidance Sets a Browser-Vendor Baseline for Agent Tool Security

Google Chrome Developers published official WebMCP tool security guidance recommending that enterprises label untrusted content, mark state-changing tools, restrict tool exposure to trusted origins, and require confirmation gates for non-reversible agent actions. The guidance formalizes tool metadata as a governance artifact and distinguishes read-only from consequential tool access. Enterprise compliance teams deploying browser-integrated AI agents now have a named vendor baseline against which their controls will be evaluated.

Research2026-09-24

Agentic Remediation Needs Formal Oversight Controls, Not Just Human Sign-Off

A SecurityWeek practitioner guide argues that agentic AI should automate the remediation phase of continuous threat exposure management, handling patch application and configuration changes without manual intervention. The article draws on supervisory control theory to specify two oversight models: human-in-the-loop for high-risk actions requiring explicit approval, and human-on-the-loop for lower-risk autonomous action within a constrained action space. Key governance controls specified include bounded agent action vocabularies, mandatory rollback plans, standardized approval paths, and tabletop exercises for agentic failure modes.

Corporate Policy2026-09-21

Amazon Blocks Meta's Muse Agent, Exposing a Third-Party Terms-of-Service Gap

Amazon blocked Meta's AI shopping agent Muse from completing purchases on its platform, citing a violation of its Conditions of Use by an unauthorized AI agent. Users received an explicit error message invoking Amazon's terms of service as the basis for denial. The incident reveals a largely unaddressed gap in enterprise agentic AI governance: whether agent deployments have been assessed against the acceptable-use policies of every external platform they access.