Notifications
Clear all
Topic starter
22/06/2026 9:55 am
TL;DR: Estonia is exploring official digital identities for AI agents so automated systems can act with limited, auditable authority on behalf of people and organisations, with Prime Minister Kristen Michal backing the proposal on June 17, according to SumSub. The real issue is not registration, but whether identity governance can preserve accountability when an agent can initiate payments, view data, and spend within fixed limits.
NHIMG editorial — based on content published by SumSub: Estonia backs digital ID system for AI agents
Questions worth separating out
Q: How should security teams govern AI agents that act on behalf of users?
A: They should treat each agent as a distinct identity with its own scope, expiry, and owner, rather than as an extension of the user account.
Q: Why do AI agents complicate least privilege in IAM?
A: Because the actor can make runtime decisions inside a granted scope, least privilege is no longer only a provisioning problem.
Q: What breaks when an agent identity is reused across multiple workflows?
A: Reused identities collapse separation of purpose and widen blast radius.
Practitioner guidance
- Define agent identities as separate principals Create a distinct identity object for each AI agent, with its own owner, purpose, scope, and expiry rather than reusing the human user's account.
- Bind delegated rights to task scope Limit each agent to the exact data, actions, and transaction bounds required for one approved workflow, then expire those rights when the workflow closes.
- Record provenance for every delegation event Capture who authorised the agent, what it was allowed to do, and which business context justified the grant so auditors can reconstruct responsibility later.
What's in the full analysis
SumSub's full news piece covers the policy and implementation questions this post intentionally leaves at a higher level:
- The specific Eesti.ai proposal language around digital ID codes for AI agents and limited authority models
- The Prime Minister's comments on accountability, trust, and control in Estonia's digital state
- The early-stage policy status, including what the government has and has not committed to yet
- The public context around Estonia's digital identity infrastructure and why that history matters
👉 Read SumSub's coverage of Estonia's AI agent digital identity proposal →
AI agent identity codes in Estonia: what changes for governance?
Explore further
22/06/2026 10:36 am
AI agent identity is becoming a governance category, not just an implementation detail. Estonia's proposal shows that organisations are beginning to recognise agents as distinct actors with bounded authority rather than extensions of the person or system that launched them. That distinction matters because access reviews, audit trails, and accountability all behave differently once the executor is software that can act independently within approved limits. Practitioners should treat agent identity as a separate governance object, not as a UI layer on top of human IAM.
A few things that frame the scale:
- Only 44% of developers are reported to follow security best practices for secrets management, exposing a significant developer behaviour gap, according to The State of Secrets in AppSec.
- Companies are dedicating an average of 32.4% of their security budgets to secrets management and code security, with US organisations leading at 40.8%, according to GitGuardian and CyberArk.
A question worth separating out:
Q: Who is accountable when an authorised AI agent causes financial loss or data misuse?
A: Accountability should follow the delegation record, not the tool alone. Security, legal, and business owners need to know who authorised the agent, what it was allowed to do, and whether the agent stayed inside that scope. If those answers are missing, responsibility will be disputed even when the activity is fully logged.
👉 Read our full editorial: Estonia's AI agent identity proposal shifts autonomy governance
