Your newest privileged user was never hired, never onboarded, and doesn’t appear in any access review.
It is an autonomous agent, and it can run an entire end-to-end process under its own identity.
As organizations embrace SAP's Autonomous Enterprise vision, a new governance challenge is emerging. Autonomous agents are becoming active participants inside business processes, often operating with authorizations, responsibilities, and risks that existing access governance models were never designed to manage.
Before exploring the governance challenges introduced by autonomous agents, it is helpful to understand how the execution model itself is changing.
The shift is subtle but important: users are increasingly moving from executing transactions themselves to invoking agents that execute business processes on their behalf.
Imagine arriving at work on Monday morning and discovering that a vendor was created, bank details were changed, an invoice was posted, and a payment was released before anyone reviewed the activity.
The actor that performed all of them was an agent provisioned to run procure-to-pay end to end, and the access review that should have caught the conflict never included it. The person who triggered the agent holds almost no access of their own.
Nothing in that sequence required a breach. It required an actor the access model was never built to see.
SAP access governance has always rested on one assumption: the actor performing a transaction is a named human user. Identity management, role design, Segregation of Duties analysis, emergency access, all of it is built on that single idea - A user requests access. An approver grants it.
The system records who did what. Accountability lands on a person.
That assumption is now beginning to change.
SAP's Autonomous Enterprise vision introduces a new category of actor into enterprise processes: autonomous agents that can authenticate, make decisions, and execute transactions with varying degrees of human involvement.
Before an agent can make a decision, it must authenticate, receive authorizations, access business data, and interact with business processes.
At SAP Sapphire 2026, SAP positioned the Autonomous Enterprise at the center of its future enterprise strategy. More than 200 agents and over 50 assistants are arriving across five domains:
These are not assistants that summarize a report or answer a question. They create master data, validate conditions, post documents, and release transactions, often with little human involvement.
Over the last few months, conversations around SAP Business AI have shifted noticeably. Organizations are no longer asking whether they should adopt AI. They are asking how they can govern it.
The most common assumption we encounter is that agent governance is primarily an AI governance or AI ethics problem.
In reality, it is often an identity and access governance problem first.
In our discussions with SAP customers, one theme appears consistently. Organizations are investing significant effort into defining AI use cases, but considerably less effort into defining how those agents will be governed once they enter production. That gap is where many of the future control challenges will emerge.
Security teams should care because autonomous agents introduce governance questions that existing SAP security frameworks were never designed to answer consistently.
Before deploying autonomous agents into production, organizations should be able to answer five governance questions:
The actor model underneath SAP access governance now has a participant it was never designed to hold: the autonomous agent.
The reflex in most security teams is to treat this as a policy question. It is one, but the policy cannot be written until the mechanics are clear. Before you decide how to govern an agent, you have to be precise about what an agent is inside the landscape, how it authenticates, and where its authorizations come from.
From a governance perspective, one question matters more than any other:
Is the agent acting as itself, or is it acting as the user?
Everything else follows from that answer.