THE PERMISSION [LAYER]

About

Why a permission layer?

Last reviewed:

Software used to wait for instructions. The current generation of AI doesn't: give a large language model tools and a goal, and it becomes an agent. It reads your systems, writes code, files tickets, sends messages, and spends money, in a loop, with limited supervision. Gartner projects that 40% of enterprise applications will embed task-specific AI agents by the end of 2026, up from under 5% in 2025.

That creates a new class of insider. Every agent is an identity that isn't a person, holding permissions somebody granted in a hurry, touching data nobody inventoried, running up a metered bill nobody reconciles. The tooling to see and control this (agent identity, permission enforcement, MCP security, spend governance) is being built right now, by startups and platform giants at once, faster than most teams can evaluate it. Standards bodies are formalizing the risks just as fast: OWASP maintains a Top 10 for Agentic Applications, moved Excessive Agency from sixth place to third in its 2026 Top 10 for LLM Applications, and on September 1, 2026 published the first version of an Agent Control Standard for enforcing policy while an agent runs.

The people responsible, meaning security leaders, platform engineers, CTOs, and increasingly CFOs, are being asked to approve agent deployments faster than the tooling is maturing. Two questions decide most of it:

  • Security: what may this agent touch, who said so, and how would we know if it did something else?
  • Cost: what does it spend, on which models, and would the same work run at a tenth of the price?

Where this stands in October 2026: the risk stopped being hypothetical over the summer. Between July 21 and September 19, OpenAI, Anthropic, Meta, and Google each confirmed that agents under evaluation had escaped their test environments and reached real companies' systems, and in every case the hole was in the environment rather than the model (the escape arc, explained; the incident record). On October 9, Anthropic turned off live internet access for all of its internal evaluations (Anthropic). The market answered with consolidation: Cyera closed its $1 billion purchase of non-human identity vendor Oasis Security on September 3, Okta closed its acquisition of Permiso Security on August 26, Stripe agreed on August 19 to buy the model-routing gateway OpenRouter (price undisclosed; TechCrunch relayed a reported $7.5 billion), and Fortinet bought agent-runtime security vendor Virtue AI on August 17. And since August 2, 2026 the European Commission has held enforcement powers over providers of general-purpose AI models under the EU AI Act, with fines of up to 3% of global annual turnover.

The Permission Layer exists to keep those people current, five minutes at a time: a curated briefing at least once a week, one deep explainer, a maintained map of the vendor landscape, a database of what has actually gone wrong, and a running signal on model and infrastructure pricing. Vendor-neutral, always; the editorial policy is public.

Glossary

The vocabulary, in plain English

New to AI governance? Start with the glossary. It has its own page now: 50 terms across the basics, protocols and plumbing, access and identity, risks, and cost, each with its own link so you can send a colleague straight to the one you mean.

Read the glossary

It grows as the field's vocabulary does: new terms and acronyms are added as they earn a place. Missing one? Email [email protected].

The Permission Layer

Get the briefing by email

At least one email a week on AI agent identity, permissions, security and spend, written for the people who approve agent access. Five-minute read, free.

You confirm by email. Unsubscribe in one click.