Pick any framework for managing AI risk: they all begin the same way, with knowing what AI is in use, by whom, for what. Skip that layer and everything above it is architecture on sand. This page is about pouring the foundation, and keeping it poured.
Start the inventory freeRisk-management frameworks, phrased generically, all route through the same early gates. Each gate consumes the inventory.
Frameworks ask organizations to map where AI touches their operations and stakeholders. A map of systems nobody listed is not a map; the inventory supplies the territory.
Measurement needs units: which system, which data, which users. The audit's per-tool rows, with risk flags and dated training verdicts, are those units pre-assembled.
Policies, review boards and approval gates act on known systems. Shadow AI is precisely the set your governance cannot act on, which makes shrinking it the first governance KPI.
The framing to steal for your board deck: the inventory is not a compliance chore inside the framework, it is the substrate the framework runs on. Everything else is a function of its completeness.
Most organizations have attempted an AI inventory once. The failure mode is always the same: it was a project, not a process.
The living inventory costs a morning per quarter. The binder cost six weeks and was wrong by month two. This is the rare governance upgrade that is also a cost cut.
Per system, the fields governance actually consumes, and where the audit supplies them.
| Field | Governance use | Source in the audit |
|---|---|---|
| System identity | The unit every decision attaches to | Tool domain plus category and subcategory |
| Who uses it | Scoping for training, oversight and accountability | Per-user or per-device breakdown |
| Usage intensity | Separates pilots from dependencies | Hits and user counts per period |
| Data posture | Feeds risk assessment and privacy analysis | Training verdict with check date, sovereignty flag |
| Approval state | The governance status itself | Sanctioned split against your approved list |
| Red flags | Escalation triggers | Risk level and abusive-purpose flags |
| Change since last period | The living part | Deltas between quarterly reports |
The inventory's own data footprint stays small: hostnames, identities, timestamps. Uploads are discarded after each run; reports are deletable before their 90-day expiry.
What each quarter's run contributes once the loop is standing.
First full report; abusive flags blocked, top tools gated for sanctioning, owners assigned per category.
Sanctioned list published; the split becomes the adoption metric. Deltas show whether governance changed behavior.
Changed vendor verdicts between runs feed renewal decisions; new tools get gated within the quarter they appear.
Four PDFs tell the board a measured narrative: exposure found, decisions made, trend bending the right way.
The loop survives when three roles each hold one piece. It dies when all three assume another has it.
Owns the export and the upload, quarterly, same window. Twenty minutes of mechanics per run, documented in the runbook once. The walkthrough is the runbook's first draft.
Owns the triage, the decision minutes and the filing. Presents the delta slide wherever governance reports; the compliance officer page details the evidence chain.
Department owners answer for their category's tools: keep and contract, or drop. Governance that skips this role produces lists nobody follows.
The sample report is a governance inventory in finished form: systems, users, postures, flags, dated. Read it before your next framework workshop.
A register of sanctioned tools is a shopping list, not an inventory. The governance object is the gap between approved and observed, which only measurement reveals.
Teams delay the inventory until it can be complete, which is never. Publish the observed list with its stated scope; completeness grows by cadence, not by waiting.
If findings never change a contract, a block rule or a policy line, the loop decays into reporting theater. Every run should close with at least one decision minuted.
The consequence engine is the sequence on detect before you block: inventory, sanction, block, verify. Governance is that loop with minutes attached.
It is the workable floor. The register behind each run updates daily, so quarterly snapshots inherit current classifications; high-churn organizations step up to monthly.
Any of them, phrased generically: mapping, measuring and managing all consume the same inventory substrate. The audit is framework-agnostic evidence.
No. Exports from your existing DNS filter, proxy or firewall plus the audit cover the loop. The per-source mechanics live in the guides.
Roughly 300,000 domains are screened daily, so new tools enter the register continuously. The unmatched-domain count in each report keeps the residual visible.
Four numbers per quarter: tools found, high-risk count, sanctioned share, delta versus last quarter. One slide, dated PDFs behind it.
A morning per quarter plus report pricing: $99 single, packs at $66 and $60, or plan allowances for monthly cadence. Details on pricing.
Whatever framework your organization lands on, it will ask for the inventory first. Have it waiting.
Run the free audit