Shadow AI Detection Tools

Finding-to-Action Ladder methodology

The Finding-to-Action Ladder records, for 16 shadow AI detection vendors, which of six actions each documents for a discovered AI tool: warn or coach, block, require approval, revoke OAuth grants, redact or stop data, route to a ticket. One written rule sets every cell, and each cell cites fact ids from pages read on 16 Nov 2026.

Facts read on .

What the ladder is

Finding an AI tool is the first step. The ladder lists what a vendor documents doing next, in six steps, so a buyer can see how far each tool goes from a finding to a response.

The rule

Each cell is derived from the facts tagged for the actions criterion in that vendor's evidence file. Yes means a fact names that action specifically for discovered AI tools. Partial means the action is named in general terms, for some tools only, or as an alert without the action. None found means no fact names it.

The rule is applied the same way to all 16 vendors, Bay included. Facts not tagged for the actions criterion do not raise a level. A vendor's claim is recorded as the vendor's claim, not as a tested result, and third-party reports are marked as such in the cell note.

Sources

Cells cite fact ids from the vendor evidence files: product pages, documentation, release notes and press releases, with the URL and read date held on each fact. Where a vendor's page was searched for an action and nothing was found, the cell cites the fact that records the search; where no such fact exists, the cell cites no fact. A cell-by-cell audit of the 96 cells, with the deciding words of each fact, is kept with the site content.

Read date

All pages were read on 16 Nov 2026. Later changes are not reflected until the ladder is next updated.

How to cite

Cite as: Shadow AI Detection Tools, Finding-to-Action Ladder, edition of 16 Nov 2026, https://shadowaidetectiontools.com/finding-to-action-ladder/, CC BY 4.0.

License

The ladder and its CSV and JSON files are published under CC BY 4.0. Reuse with the citation above.

Corrections

To correct a cell, send the vendor, the action and a public page that documents it. Accepted changes are logged on the corrections page with their date.

Levels and counts