Shadow AI governance4 min readField note 18

How to compare shadow AI activity with your approved tools list

Use a downloadable AI register and three Windows receipts to separate approved software, an unknown workspace and a tool that needs an owner.

Worked review of Cursor, Claude and Kimi against a fictional approved AI tools register.
The idea in focus

Three selected Northstar observations reconciled against an illustrative procurement list. The CSV contains the review fields and worked decisions.

Field note / 18
In brief

Product, surface, workspace and effective date can each change the approval decision.

  • Use the approval that applied at the event time.
  • Keep the observed action in the review row.
  • Give each missing or ambiguous approval a named owner.
In this article

Which approval was in force on the day?#

Start with the version of the approved tools list that applied during the reporting window. A purchase made on Friday cannot explain a Wednesday exception unless the approval explicitly covers Wednesday. In the downloadable example, Engineering may run Cursor on managed laptops. Finance may use Claude in its company workspace for public material. Kimi has no entry in this sample. Replace those assumptions before using the sheet in your own review.

Three register fields identify the approved surface, permitted use and effective dates.
Keep the dated policy or procurement decision beside the activity export. The register in this exercise is fictional.

Choose the devices and surfaces you can review#

Open Individual AI usage in the demo and search for NS-WIN-032. Copy the product, action and device for the Cursor and Kimi rows into separate lines. Then search NS-WIN-014 for the Claude paste. These three selected observations form the worked sample. For a fleet report, also record the eligible device count, reporting interval and missing browser or agent coverage. An empty row on a quiet laptop is weak evidence about adoption.

Three receipts on one Engineering laptop show a Cursor process, a Codex paste and a file selection on Kimi.
The fictional Northstar device timeline preserves the product and action for each event.

Does an approved editor settle the question?#

The Cursor receipt establishes that the approved editor was running on the managed Engineering laptop. Leave prompt content, model, repository and active editing time unknown. If a manager asks whether source code went into the model, route that question separately. The inventory row can be complete even while that question remains open.

Cursor process receipt on the Engineering device NS-WIN-032.
For the sample register, the product, desktop surface and Engineering device fall within the software approval.

What if the product matches but the workspace is unknown?#

Look up the Claude browser approval and record the condition attached to it. A destination match alone cannot tell the reviewer whether this session used the company workspace. Give the workspace owner the event reference and time for a scoped check. Security can review the detected categories in parallel. Mark the register row “scope unresolved” until the owner supplies evidence.

A Claude paste receipt shows API-key and email-address pattern counts.
EVT-1051 gives Security a paste to review. It leaves the approved company workspace and business purpose unverified.

Who investigates a tool missing from the register?#

Search the register by product name and documented aliases. Check whether Procurement renewed a parent contract or granted a dated team exception. For this sample, record “no matching entry” and give Procurement a follow-up. Record the observed action as file selection. A missing approval and a completed transfer are separate questions, and the reviewer needs evidence for each.

Kimi file-selection receipt on the same Engineering device as the Cursor process.
The selected file is Architecture_notes.md. The product on this receipt is Kimi.

Publish the exceptions with an owner and a date#

Save the register revision, observation reference, review date, disposition and next owner. Keep “approved but unobserved” as a separate list if Procurement also wants to check underused subscriptions. At the next review, carry open items forward and append decisions with their dates. A later approval can close a current gap while preserving how the original observation was assessed.

Worked review keeps the Cursor observation, routes Claude to the workspace owner and assigns Kimi to Procurement.
The three decisions can be repeated next week against the same register revision.
Read the primary sources

Sources & further reading

  1. Open the fictional device activity report
  2. Build the starting shadow AI inventory
  3. Look up a product and supported surface
  4. Evaluate employee AI visibility
← Back to all articlesBack to top ↑
A CLEAR PLACE TO START

Plan your AI visibility pilot.

Create a brief for your team. Your answers stay in this browser and are included in your download.

AI tools in scope
More supported tools

This creates a planning document. It does not enroll devices or submit a request.