AI Security Governance
Your staff are already using AI. Would you know?
Could you show an auditor, a client or the board how AI is governed in your business? We help you find out where it’s being used, decide what you’re comfortable with, write it down in a way the board can sign and staff can follow, and keep the evidence.
Take the 3-minute quick check 12 questions. Your answers stay in your browser.
Looking for something specific?
Not sure where to start?Talk to us →When you don’t need this: if the basics aren’t there yet (identity, logging, incident response, privacy), AI governance on top is paint on a cracked wall. We’ll say so. Start with a conversation. And we’re not lawyers: where something needs legal interpretation, the regulatory map says so and routes it to one.
AI Discovery
Staff are already using AI. Nobody knows which tools, or what goes in.
First, find out which AI tools are already in use.
Governance starts with seeing what’s really in use. We find the AI tools your people use, then help you decide on each one: approve, restrict or block, with the reasons written down. How much we can see depends on your licences. Defender for Cloud Apps, for example, makes discovery much richer.
- Microsoft Copilot
- ChatGPT
- Claude
- Gemini
- Models you run yourselves
- AI built into apps you already use
We help you set rules that cover all of them, not just the one you bought.
- Every AI tool on one list, including the free ones
- What data each one can reach
- A decision and an owner for each
- Reviewed as new tools appear
- Approved and unapproved tools: a decision for each, from sanctioned to blocked, with the reason recorded.
- Business and personal accounts: which accounts staff may use, and the data retention and training settings on each.
- API keys, connectors and plug-ins: what each one can reach, who owns it, and how keys are stored.
- Self-hosted and private models: the same access and data controls as any other tool.
- Using what you already own: depending on your licences, Microsoft tools such as Defender for Cloud Apps, Purview and Entra can help find and control non-Microsoft AI too.
AI tools with no decision · example tenant
AI Governance Programme
Six stages. Each one leaves you holding something real.
One step at a time, each with something useful at the end.
Not one enormous framework you implement over two years. A sequence that builds properly, where each stage uses what the last one produced, and every stage ends with a document, a decision or a record you can put in front of an auditor, a client or the board.
1. Find out where you are
A 20-minute maturity assessment.
YOU’LL HAVEA scored baseline with prioritised gaps2. Decide what you’ll accept
A workshop on risk appetite.
YOU’LL HAVEA risk appetite statement the board can sign3. Write it down
Policy, acceptable use, risk register.
YOU’LL HAVEA policy pack, published not promised4. Know which rules apply
Your sector and use cases mapped.
YOU’LL HAVEA regulatory map with owners and evidence to collect5. Know how it gets attacked
A threat model on MITRE ATLAS.
YOU’LL HAVEInherent vs residual risk, with mitigation tracked6. Keep it running
Training, shadow AI audit, incidents.
YOU’LL HAVEA progress view for the board
We’re building WatchTower, our own AI governance toolkit. It isn’t needed for any of the work above, which we do with you directly. If you’d like to see it as it takes shape, ask us about early access.

AI Assurance
Four things you’ll be able to say about AI in your business.
Use AI with clear rules, not crossed fingers.
Plain answers for the client questionnaire, the auditor and the board. We work through each one with you, and keep the evidence. Every organisation and licence is different.
Data Access
“We know where AI is being used, and what data it touches.”
Sensitive files, like salaries and board packs, can be kept to the people who should see them.
- Who can see what
- SharePoint and OneDrive
- Sensitivity labels
- Old sites
- Every AI tool in use is on a list, including the free ones staff signed up for and the vendors with AI quietly built in.
- You know what each one can reach, starting with what Copilot can see in SharePoint and OneDrive, and what staff paste into other AI tools.
- Your AI supply chain is drawn on a map: vendors, data flows, where it’s stored, who depends on what.
AI Policy
“We’ve decided what we’re comfortable with, and written it down.”
Staff know what’s allowed, and why.
- What’s allowed
- What isn’t
- Who signs it off
- Staff training
- A risk appetite the board has actually agreed, so decisions downstream aren’t based on assumption.
- One policy for the board, and practical rules for each role: what data can go where, which tools are approved, who to ask.
- A risk register that starts full, not empty, scored for your context.
Use-Case Approval
“We know which rules apply to each AI use case, and why.”
Before a new AI idea goes live, someone checks it against the rules and signs it off.
- A list of AI uses
- Privacy checks
- An owner for each
- Each AI use case mapped to the rules that apply, by geography, sector and what the AI does, including emerging AI regulation.
- An honest view of the risk each one carries, with an owner, the data involved and the reasoning recorded.
- A privacy impact assessment for AI that shows where personal data goes in, how it’s used and how it’s disposed of.
AI Incident Readiness
“If AI goes wrong, we know what to do and who decides.”
A short plan, practised in advance, so everyone knows what to do if AI gets something wrong.
- Who decides
- Who to tell
- What to record
- Practice runs
- A threat model built on how AI systems are actually attacked, with real-world cases to show the board.
- Engineers get an OWASP LLM checklist with owners, evidence and closure, so governance reaches the code.
- One incident register so Legal, the DPO, Security and leadership share a decision trail before the pressure hits.
Questions people ask us
Straight answers, in plain English. Every organisation is different, so the details depend on your setup.
Do we have to ban AI?
No. The aim is to use it safely, not stop it. We help you decide what you’re comfortable with and write that down in a way staff can follow.
Is this just about Copilot?
No. Copilot, ChatGPT, Claude, Gemini or models you run yourselves, the same questions apply: who uses it, what goes in, and which accounts and settings are allowed. You don’t need to buy new AI tools to start. If you’re considering one, we help you check you’re ready before rollout.
Is this a legal review?
No. We help you see which rules may apply to each use of AI and who should own them. Where you need formal legal advice, we’ll say so and help you brief your advisers.
Will this save us money?
It can help. AI tools are usually paid per user, so knowing who actually uses what means you can buy the right number of licences. Discovery also tends to find overlapping AI subscriptions that staff have signed up to or expensed, and an approval process stops them multiplying. The main benefit is control over where your data goes, but less duplicate spend is a welcome side effect.
Where do we start?
The free 3-minute quick check gives you an indicative picture. It’s a self-check, not an assessment. Then a 30-minute call to talk it through.
Find out what your staff are already doing with AI.
Thirty minutes. Four questions.
How many AI tools are in use, what you’d send a client who asked for evidence, what you told the board, and what you’d do tomorrow if it went wrong. If you hesitate on one, that’s where we start.
Book a 30-minute callPick a time that suits you Or take the 3-minute quick check first