AI Governance Institute
← News

Microsoft CISO Guidance Makes Agent Identity and Observability the Enterprise Baseline

What happened

Microsoft's security blog published The CISO's evolving role: Protecting and defending in the agentic era on October 28, 2026, authored by the company's security leadership. The guidance sets out three foundational requirements for enterprises running AI agents. Each agent should have its own governed identity rather than borrowing a human employee's login. Agents should receive only the access their specific task requires. Security teams should maintain continuous visibility into what each agent owns, what systems it can reach, and what actions it has taken. Microsoft frames these not as aspirational controls but as the minimum security posture for production agentic deployments. The guidance arrives alongside a wave of documented incidents. These include reports that 55% of organizations run system-changing AI agents without identity controls. Findings also show that agents running as users create a structural identity control gap. It also follows Microsoft's own acknowledgment that internal AI agents present an insider-threat risk requiring pre-action controls.

Why it matters

  • ·Regulators and examiners are already benchmarking agent governance against practitioner standards. Banking supervisors, the UK Financial Conduct Authority, and EU data protection authorities are asking whether organizations can demonstrate who owns each agent and what it can access. Microsoft's guidance gives those reviewers a concrete baseline to measure against.
  • ·Agents that borrow human credentials bypass every standard access review an organization runs. Without governed identities for agents, routine controls such as periodic access reviews and leaver processes will miss a growing category of privileged activity. This creates compliance gaps that existing identity programs are not designed to catch.
  • ·The observability requirement has direct implications for audit readiness and incident response. If an agent causes harm or leaks data, organizations without continuous behavioral logs face a serious evidentiary problem. This problem was highlighted when the first confirmed AI agent breach triggered a data protection authority notification in the Netherlands: there is no trail to reconstruct what happened or when.

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

  • ☐Ask your identity and access management team to produce a list of every AI agent currently running in production and confirm whether each has its own dedicated identity or is borrowing a human employee's login credentials.
  • ☐Review the access permissions granted to each agent and confirm that no agent holds access beyond what its specific assigned task requires. Flag any agent with broad file, email, or system access for immediate scoping review.
  • ☐Confirm that your security operations team receives a continuous behavioral log for each agent, including what actions it took, what data it touched, and what external systems it contacted. If no such log exists, treat this as a priority gap.
  • ☐Assign a named human owner to every deployed agent and document that ownership in your AI model registry or equivalent record. Verify that the owner has the authority and awareness to stop the agent if needed.
  • ☐Check whether your existing access review cycle explicitly includes AI agents. If agents are excluded from joiner-mover-leaver and periodic recertification processes, escalate this to your identity governance team as a control gap.

What to watch next

Regulatory pressure on agent identity and observability is accelerating. The European Central Bank required bank AI cyber action plans by October 31, 2026, and supervisors in multiple jurisdictions are expanding examination scope to include agentic systems. Pending guidance under the Five Eyes Guidance on the Careful Adoption of Agentic AI Services is expected to formalize behavioral monitoring and identity requirements. So is the EU AI Act (Regulation (EU) 2024/1689). Compliance teams should also track whether Microsoft's guidance is cited by auditors or examiners as a de facto standard. This has happened with similar practitioner publications in financial services model risk management.

Related Coverage

Corporate Policy2026-11-16

Agent 365 Brings Tool-Level Governance to MCP Servers and AI Plugins

Microsoft announced expanded Agent 365 capabilities, part of Microsoft 365 E7. Enterprises can discover, register, and govern tools AI agents connect to, including MCP servers, plugins, and skills. The system blocks unsanctioned tools and allows granular access controls for approved users and functions. Capabilities were detailed at Microsoft Ignite, held November 17-20, 2026 in San Francisco.

Research2026-11-12

KPMG and Cequence Set Runtime Controls as the Agentic Governance Baseline

Cequence Security and KPMG in Singapore have published a joint report, "Delegating Outcomes, Not Authority: Agentic AI Runtime Security, Governance, and Control." The report argues that static permissions alone are insufficient to govern AI agents. The report recommends runtime controls that evaluate each agent action before it executes, covering least-privilege access, non-human identity, tool-use monitoring, audit trails, and prompt injection defense. Cequence field data from October 2026 tracked more than 281,000 AI agent visits across five industries in a single week.

Research2026-11-12

WEF Report Sets Systemic Risk Baseline for Agentic AI Governance

The World Economic Forum published 'Governing Agentic AI: Managing Systemic Risk for Trusted Adoption' in November 2026. It proposes a governance framework for AI agents operating autonomously across organizations and systems. The report calls for verifiable agent identities, named human or legal owners for each agent, least-privilege access credentials, comprehensive action logging, and incident and near-miss reporting. These recommendations span AI inventories, identity and access controls, third-party risk management, operational resilience, and cross-organizational incident response.