Most small businesses we talk to think they have an AI problem. They have a data governance problem wearing an AI costume.
The fear is real enough. Staff are pasting client information into chatbots, Copilot is surfacing files nobody remembers sharing, and the board wants to know who signed off on any of it. The instinct is to write an AI policy. The better move is to fix who can see what, because AI did not create that exposure. It just made it impossible to ignore.
This is the heart of data governance for small business in 2026: the controls that decide which people, and now which AI tools, can reach which information. Get that right and most of your AI risk disappears. Get it wrong and no policy document will save you.
Average loss per cyber incident for an Australian small business
Breaches that trace back to excessive access or accidental sharing
An AI agent can inherit, but never exceed, the permissions of the person running it
Strip away the jargon and data governance answers four questions. What information do we hold? Where does it live? Who is allowed to touch it? And how do we prove all of that when someone asks?
For a 30-person firm that usually means Microsoft 365: SharePoint sites, Teams channels, shared mailboxes, a CRM, and a few line-of-business apps. The problem is rarely that the data is unprotected. It is that permissions have sprawled. A site shared “just for now” three years ago is still open to the whole company. A departed contractor still has a guest account. Finance records sit in a folder marked “everyone”.
That mess was tolerable when only humans clicked through it, because people generally do not go hunting through folders they have no reason to open. AI does not have that restraint.
Here is the mechanism that catches businesses out. When you point an AI assistant at your environment, it does not get special powers. It acts as the person using it and can reach exactly what that person can reach. Ask Copilot to summarise everything it knows about a salary review, and if your permissions are loose, it will happily pull pay data the asker was never meant to see.
The AI did nothing wrong. It followed the access rules you set, or failed to set. This is why the industry has stopped treating AI governance as a separate discipline and started describing it as data governance applied to a faster, more thorough user. The login is no longer the only boundary. What a given identity is allowed to reach is the boundary.
So the order of operations matters. You cannot govern AI on top of broken permissions. You fix the foundation first, then layer the AI rules on top. We wrote more about where that foundation stops at the platform edge in our piece on why AI governance has to extend beyond Microsoft 365.
Frameworks have many pages. The controls that move the needle for a small business are few, and they are the same ones that make AI safe to switch on.
Notice that none of those five are AI controls. They are data governance controls. Once they are in place, governing AI is mostly a matter of pointing the tools at data that is already organised and deciding which tools are approved. That is the bridge: do the old discipline properly and the new one becomes manageable. Our guide to AI governance in Australia covers the policy layer that sits on top.
We typically start with a discovery pass: a map of where sensitive data sits and who can currently reach it. Most businesses are surprised by the answer. From there it is a methodical cleanup of permissions, a sensible labelling scheme, and a review rhythm that keeps the mess from creeping back.
It is not glamorous work and it does not make a good headline. It is also the reason a business can adopt AI with confidence instead of crossing its fingers. The firms getting AI right in Perth are not the ones with the cleverest policy. They are the ones whose cyber security foundations were already in order.
We will map where your sensitive data sits and who can reach it, then fix the gaps before AI makes them a problem. Our Perth-based team can help on 1300 EPIC IT.
