Domain — AI Governance & Security
Your organisation is already using AI. The question your board will be asked is not whether you adopted it — it's whether you can account for it.
- 01
Discover
Every model, agent and supplier feature in use, sanctioned or not.
- 02
Scope
What each can read, write and trigger, and whose authority it inherits.
- 03
Attribute
Which identity acted, under whose mandate, on what record.
- 04
Own
A named owner and a review date against every system.
01
Contain what your AI agents can reach.
An agent is granted access so it can be useful, then keeps that access because nothing revokes it. Its reach is usually wider than the task that justified it, and it exercises that reach continuously rather than occasionally.
An AI agent is a non-human identity with initiative.
We establish what each agent can read, write and trigger, whose authority it inherits, and where a single credential spans systems that your controls assume are separate.
02
Know which of your suppliers is running AI on your data.
Vendors add model-based processing to existing products through release notes. The contract you signed and the processing now taking place may no longer describe the same service, and your data may be leaving a boundary your assessment recorded as closed.
We review supplier documentation, sub-processor positions and integration scopes, and report where AI processing has entered your estate through a third party.
03
Know what AI is running in your business, and on whose data.
Adoption rarely arrives through a governance forum. It arrives through licences a team already held, browser tooling, and pilots that quietly became dependencies. The result is an inventory nobody maintains.
We build a register of AI in use — sanctioned and otherwise — recording the data categories involved, the owning function, and whether a lawful basis and an accountable owner exist.
04
Prove your AI decisions are explainable, contestable and owned.
Explanation is a model question, contestation a process question. Attribution is neither: it depends on knowing which identity acted, under whose mandate, and on what record.
We test whether that trail exists for the decisions that matter to your regulator and your customers, and identify where it ends before it reaches a person.
Regulatory context
In Kenya, the Data Protection Act and guidance issued by the Office of the Data Protection Commissioner set expectations for lawful processing, accountability and the treatment of automated processing, including guidance addressing artificial intelligence. Institutions with European exposure also fall within the scope of the EU AI Act, which takes a risk-tiered approach to AI systems.
We do not read these instruments to you. Our position is narrower: each of them assumes an institution can say what is running, who owns it, and on what data. That assumption is where most programmes are weakest, and it is where we work.
The offer
The AI and Third-Party AI Exposure Register
A fixed-scope, fixed-fee assessment. Three weeks. Read-only. Ends in a document your risk committee can act on.
Take the AI Readiness AssessmentScope and fee are agreed before work begins.
Two halves of one argument
AI governance asks who decided. Only identity governance can answer. Every requirement to explain, contest or attribute an automated decision resolves, eventually, to a question about identity — and in most institutions that trail ends at a service account nobody owns.
Identity Governance & Security