Shadow AI metrics for the board
A board report on shadow AI needs six numbers: tools found, active users, share of use on personal accounts, high-risk findings open, median time to resolve, and coverage. Report monthly during a rollout and quarterly after, and state which sources and devices the numbers cover.
Facts read on .
Which numbers belong in a board report?
Six belong: AI tools in use found, active users per tool, share of use on personal accounts, high-risk findings open, median days to resolve a finding, and coverage (devices and identity tenants with a sensor). Each answers a board question: how much, who, how exposed, how fast, and how sure.
The data exists in the products. Microsoft's cloud discovery dashboard shows the types of apps used, open alerts, risk levels and top users. Zscaler documents usage by user and department, and Cyberhaven records who uses each tool and with what data.
Sources: View discovered apps on the Cloud discovery dashboard; Zscaler: public AI inventory, GenAI; Cyberhaven: AI security; Zscaler source (zscaler-12); Cyberhaven source (cyberhaven-23).
How often should they be reported?
Report monthly while the program is being rolled out and quarterly once it is steady, with an immediate note for a serious event. The monthly view shows whether discovery coverage is rising, and the quarterly view shows trend.
Align with the audit cycle so the board pack is the same evidence the auditor reads.
How do you present a first inventory fast?
For a first number inside 30 days, use whichever source can be live soonest and say what it covers. Vendors publish setup times such as Grip Security's 10 minutes with about 5 days for historic usage, Harmonic's first insight in about 30 minutes, and Bay's claim of under 5 minutes via one MDM or EDR script.
Present the count together with the coverage line, and promise a second source by a named date.
Sources: Grip Security: discover SaaS risks; Harmonic Security: shadow AI detection; Bay: shadow AI discovery; Grip Security source (grip-security-14); Bay source (bay-18).
What should be left out?
Leave out raw domain counts, vendor risk scores shown without context, and catalog size. A tool catalog of 4,000 or 20,000 apps says how much a product recognizes, not how much your staff use. Leave out any figure you cannot reproduce from a source.
Do not present a vendor's own benchmark of AI use as your own organization's data.
Sources: Palo Alto Networks: discover risks posed by GenAI apps; Aurascape: discover and monitor AI.
How do you show progress, not just exposure?
Show before and after for each action: personal-account share, tools moved to approved alternatives, grants revoked and blocks enforced. Progress numbers keep the board from reading a rising tool count as a failing program, since better discovery finds more.
State that explicitly: a higher count after a new source is added reflects coverage.
Sources: Push Security: shadow AI, how to discover, govern and secure AI apps.
What should the chart show?
Use one trend line for tools found and one for coverage, plotted on the same dates. When discovery improves, the count of tools rises first and then flattens as the inventory catches up; the coverage line explains the step.
Add a small table of the five highest-risk findings with owner, action and date. The board reads names and dates faster than totals, and it shows who is accountable for each.
Label every number with its source and date. A vendor dashboard figure is a vendor-computed value, and the report should say which product produced it. Microsoft's cloud discovery dashboard, for example, shows app types, open alerts, risk levels and top users, and a board slide quoting it should say so.
Close with the decisions you need from the board, such as approving an enterprise license for a tool staff already use. Keep that to a line or two.
Sources: View discovered apps on the Cloud discovery dashboard.
Sources
- View discovered apps on the Cloud discovery dashboard (learn.microsoft.com), read
- Zscaler: public AI inventory, GenAI (help.zscaler.com), read
- Cyberhaven: AI security (cyberhaven.com), read
- Grip Security: discover SaaS risks (grip.security), read
- Harmonic Security: shadow AI detection (harmonic.security), read
- Bay: shadow AI discovery (bay.io), read
- Palo Alto Networks: discover risks posed by GenAI apps (docs.paloaltonetworks.com), read
- Aurascape: discover and monitor AI (aurascape.ai), read
- Push Security: shadow AI, how to discover, govern and secure AI apps (pushsecurity.com), read