AI Access Governance: The Missing Layer Beneath Every AI Governance Programme
Three disciplines, three questions
Most organisations are running two of the three. Data Governance answers: what data do we hold, how is it classified, and who is responsible for it? It is a mature field with frameworks, dedicated teams, and a decade of tooling. AI Governance answers: are our model outputs correct? Are they biased, hallucinated, or non-compliant? Who approved this model for production?
Both are legitimate disciplines worth investing in. Neither answers the question that comes before them.
The layer underneath
| Layer | The question it answers | What it assumes |
|---|---|---|
| Layer 3 — AI Output Governance | Are model outputs correct and compliant? | That you know which AI tools are active |
| Layer 2 — Data Governance | What data do we hold? Who owns it? | That your inventory of systems touching data is accurate |
| Layer 1 — AI Access Governance | Which AI tools are connected, and who authorised them? | Nothing — it establishes the ground truth |
Before you can govern your data, you need to know which systems currently access it. Before you can govern model outputs, you need to know which AI tools operate in your environment at all. Most organisations assume they know. Most are wrong.
AI Access Governance is not a subset of the other two — it is the prerequisite to both. Data Governance assumes an accurate inventory of systems touching your data; AI Access Governance asks whether that inventory reflects reality. AI Governance assumes you know which AI tools are active; AI Access Governance asks whether that list is policy or truth. These are not the same question, and the gap between them is exactly where shadow AI lives.
Why the gap keeps widening
Employees connect tools individually. Tokens accumulate. Departed employees leave grants active — the ghost token problem. Audit cycles run annually while the actual landscape shifts every week. By the time a governance programme assesses the environment, it is measuring something that no longer exists.
A programme that starts at layer two or three — without first confirming layer one — is building on an unverified assumption about what is actually running. That assumption is where most compliance exposure hides.
To test whether your own layer-one picture is documented or assumed, run the AI Governance RADAR. Which layer does your current governance programme start from?
Start at layer one.
Pyroniq maps every AI tool actually authorised in your M365 or Google Workspace tenant — the inventory the other two layers assume you have.
This article is for awareness only and does not constitute legal advice. DPDPA obligations depend on your organisation's specific circumstances — confirm them with qualified counsel.