top of page

Your AI Has Access. Who Gave It Authority?

11 minutes ago
3 min read

If your board’s answer to identity security is “we have MFA”, your governance conversation is dangerously behind your technology.

AI is entering your documents, dashboards, customer relationships, finance processes and operational decisions. Increasingly, agents can execute actions across connected systems.

Every connection raises the stakes. Who—or what—can see, retrieve, change, approve, export or delete? Under whose authority? For how long? Who can stop it?


Your AI Has Access. Who Gave It Authority?
Your AI Has Access. Who Gave It Authority?

Identity and access management now determines how safely your organisation can operate, automate and grow.


The wake-up call is already measurable.


IBM’s 2026 research, covering 602 breached organisations, puts the global average breach cost at US$4.99 million, up 12%. Roughly one in five reported a breach involving AI models or applications. Among that group, 92% lacked proper AI access controls. Fewer than half were actively securing non-human identities. These findings describe the studied organisations, but the warning deserves every board’s attention. IBM, 2026

Verizon’s 2026 DBIR adds another uncomfortable reality: 31% of breaches began with vulnerability exploitation, while 48% involved third parties. Identity governance must therefore connect with patching, architecture, supplier assurance and operational resilience. A strong login cannot compensate for an exposed application or an uncontrolled integration. Verizon, 2026


MFA (in all its forms, versions and variatins) remains essential, of course. Use phishing-resistant methods wherever possible. But authentication answers only the opening question: can this identity prove itself? It does not establish whether its permissions are appropriate, its purpose remains legitimate or its next action should be allowed. CISA guidance.


An authenticated employee can still hold excessive access. A supplier account can outlive its contract. An automation can retain administrator rights long after deployment. An AI agent can inherit authority nobody intended it to exercise.


A valid identity can still represent an unacceptable risk.


Consider business intelligence. Connecting AI to reporting can unlock faster analysis, better forecasting and earlier detection of operational problems. Yet access to a dashboard, its underlying dataset and the ability to export records represent different powers. Those distinctions need deliberate design.

Microsoft explicitly warns that existing oversharing becomes more visible when agents retrieve and summarise information on demand. AI can make yesterday’s neglected permissions today’s immediate disclosure. Microsoft guidance


The exposure also reaches decision integrity. If someone can alter source data, semantic models or reporting logic, leaders may receive persuasive answers built on corrupted foundations. Quality access management protects confidentiality, accuracy, accountability and confidence in decisions.

That requires an operating discipline across the enterprise.

Give every employee, contractor, customer, partner, service account and AI agent an identifiable owner and defined purpose. Automate access changes when people join, move or leave. Remove dormant accounts. Review supplier access against current contracts.


Grant the minimum authority required. Separate administrative duties from everyday work. Use temporary privileged access, short-lived credentials and controlled secrets. Reassess access as devices, behaviour and risk change.


For AI, define which data, models, tools and actions each system may use. Enforce permissions at retrieval and execution. Require human approval for consequential actions. Test prompt injection, unauthorised disclosure and excessive agency. Log decisions and actions, and prove that access can be revoked quickly.

Governance must also cover data provenance, quality, privacy, residency, retention and intellectual property. Assign accountability for model evaluation, unreliable outputs and business consequences. A policy document cannot substitute for controls demonstrated in production.


This is where transformation oversight becomes decisive. Require evidence before each release - permissions tested, sensitive data protected, owners assigned, incidents rehearsed and benefits measured. Boards need visibility into exceptions, unresolved exposure and strategic drift.


RARE Ai-Intelligence places data, identity, permissions and standards within the foundation for governed AI. Its focus on legacy impairment, fragmented platforms, operational outcomes and transformation control makes identity a design requirement from the outset.


RARE Strategy connects that foundation to strategic fit, operational reality, systems assurance, vendor control and board intelligence. Leaders need that connected view to judge whether digital investment is producing capability while preserving control.

The benefits are commercial: faster onboarding, clearer collaboration, fewer access bottlenecks, reduced licence waste, stronger audit evidence and safer automation. IBM’s 2026 findings associate security AI and automation with average breach-cost savings of US$1.93 million—evidence that disciplined enablement can improve resilience. IBM, 2026


Start now. Inventory identities and AI connections. Trace access to critical systems and data. Remove unjustified privilege. Establish accountable owners and those not so. Give executives a dashboard showing exposure, remediation, access exceptions and value delivered. Measure revocation time, ownerless identities, excessive permissions and overdue reviews alongside adoption and productivity. Put access quality into investment decisions, procurement requirements and transformation reporting.


If you cannot explain what your AI can access, whose authority it carries and how you will stop it, you are accelerating beyond your ability to govern.


Take back control before delegated access becomes delegated damage.

Comments


bottom of page