AI governance tools: what the categories actually do
The phrase "AI governance tool" currently covers at least four distinct product categories that solve different problems. Evaluations go wrong when a buyer compares a documentation platform against a runtime enforcement point as though they were alternatives. They are usually complements, and the useful first step is deciding which problem you actually have.
Updated 2026-09-18
The four categories
Each is legitimate. They are rarely substitutes for one another.
- Governance and documentation platforms — model inventories, risk assessments, control mappings and audit artefacts. Strong for demonstrating a programme exists; they do not sit in the request path.
- Model observability and evaluation — quality, drift, bias, hallucination and regression testing. Concerned with output, not authority.
- AI security posture management — discovery of AI assets, misconfiguration and exposure. Tells you what exists and how it is configured, mostly out of band.
- Runtime control planes — identity, policy and enforcement at the point of action, producing evidence as a by-product. The only category that can stop something.
Questions that separate them quickly
Three questions usually establish which category a product is in, regardless of how it is marketed.
- Can it deny an action in flight, or only report on it afterwards?
- Does it know which agent and which human initiated a specific action, or only which application?
- Is its evidence generated by a control decision, or assembled from documentation people maintain?
Matching the tool to the problem
If the requirement is an auditor asking to see a governance programme, a documentation platform addresses it directly. If it is a model producing poor outputs, observability is the right instrument. If it is not knowing what AI exists, posture management finds it.
If the requirement is that an agent must not be able to issue a refund above a threshold without approval, none of the first three can satisfy it — that needs a decision point in the path of the action.
A note on overlap
Vendors expand across these boundaries, so categories blur in marketing faster than in product. The evaluation that survives contact is a real scenario run end to end: pick one consequential action, and ask each candidate to show the action being attempted, the decision being made, the enforcement taking effect, and the record it produced.
Common questions
- What is the difference between an AI governance platform and AI security tooling?
- Governance platforms document programmes and map controls; they generally sit outside the request path. Security tooling — particularly runtime control planes — makes and enforces decisions at the moment of action.
- Do we need more than one?
- Often, because they solve different problems. The mistake is treating them as alternatives and concluding you are covered because one of them is in place.
- How should we evaluate?
- Run one real consequential action end to end and require each candidate to show the attempt, the decision, the enforcement and the resulting record. Marketing categories blur; that sequence does not.