Shadow SaaS discovery rarely starts with a scan. It starts with a help desk ticket. "Can you add me to the whiteboard tool?" IT has never heard of it. By Friday, the same tool shows up in three tickets, two expense reports, and one nervous team chat.
The app was never hidden. It was just never on IT's list.
Here is the short version. Shadow SaaS discovery means finding the cloud apps teams use without IT review. You do not need to buy another tool to start. Finance, the help desk, and team leads each hold part of the picture. Connect those views, assign an owner to each app, and repeat the check at key moments.
Shadow SaaS Is an Ownership Gap, Not Just a Visibility Gap
Shadow SaaS is any cloud app used for work without IT review. Someone signs up with a work email, pays with a team card, or clicks "Sign in with Google." It is a subset of shadow IT, and shadow AI tools are a fast-growing part of it.
Most articles call these apps invisible. In our experience, that is rarely true. Marketing knows about the design tool. Finance approved the charge. The team uses it daily. IT is simply the last to hear.
Take a typical offboarding. A designer leaves. Two weeks later, nobody can open the mockup tool with the client files because the account used a deactivated email. Everyone knew the tool existed. Nobody owned it.
So shadow SaaS discovery is less about seeing more. It is about joining the partial lists that already exist and putting a name next to every app.
That is also why your usual tools miss it. IT asset discovery finds laptops, servers, and printers on your network. Shadow SaaS lives in accounts and invoices, not in network scans.
The Discovery Signals You Already Own
Good shadow SaaS discovery starts with data your company already collects. Each source below shows part of the picture, and each one has a blind spot.
Notice the pattern. Identity signals show logins, and money signals show purchases. A free plan created with a personal email slips past both. Those accounts often hold client files, so the team lead survey later in this article matters more than it looks.
The SSO gap is bigger than most teams expect. Obsidian Security reports that more than 80% of the apps it sees are not federated behind an identity provider. SSO logs alone will miss most of your shadow SaaS.
When Buying a Discovery Tool Finally Makes Sense
Paid shadow SaaS discovery tools add signals you cannot easily collect by hand. Browser extensions see which web apps people actually open. Email scanning finds welcome messages and invoices. CASB and proxy tools watch network traffic. Older on-premises proxies see little once people work from home, so check whether a tool needs an endpoint agent to cover remote staff.
Each one has a cost beyond the price. Browser and email monitoring touch employee data, so bring in HR and legal early and tell staff what you collect. Hidden monitoring kills the honest survey answers you need later.
Buy a tool when
- You cannot pass the breach-news drill described at the end of this article.
- Regulators expect continuous audit evidence.
- Remote work leaves your card and ticket data too thin.
Wait when
- You have fewer than about 150 people (our rule of thumb, not a benchmark).
- You have not tried the free signals and a free scanner yet.
- Nobody is ready to own the results.
A tool that finds 300 apps with no owner just gives you a longer list of problems.
How to Run a Five-Day Shadow SaaS Discovery Sprint
This shadow SaaS discovery sprint works for most teams under 1,000 people. Block about two hours a day and keep one shared spreadsheet. Yes, a spreadsheet. We know. It is temporary.
Expect surprises. In a typical first sprint at a 150-person company, IT expects about 40 apps, then finds duplicate project tools across teams and an AI note-taker connected to the CEO's calendar. This is an illustrative pattern, not survey data.
Day 1: Pull App Access From Your Identity Tools
Export third-party app access from your admin console, or run the free Shadow IT Scanner against Google Workspace, Okta, or Entra ID. The scanner is a small command-line tool that runs on your own machine, so check its setup guide for the admin access it needs. Sort by user count and permission scope. An app with full access to Drive deserves attention before one that only reads a profile name. Export to CSV so merging on Day 5 is easier.
Day 2: Follow the Money
Pull 12 months of expense lines and the AP vendor list. Filter for recurring charges with words like "Pro," "Team," or "Monthly." If your card provider supports it, also filter by software merchant category codes such as 5734, 5817 and 7372. Annual plans renew once a year, so a shorter window misses them. Ask finance for the export instead of building it yourself.
Day 3: Mine the Help Desk
Search ticket history for access requests and app names you do not recognize. Tickets show the tools people depend on, not just the ones they tried once. Pay extra attention to "who has the login" requests. They usually point to a shared account with no clear owner.
Day 4: Run a SaaS Amnesty Survey
Send a short survey to team leads. Promise that nobody gets in trouble, then ask two questions. What tool would break your week if it vanished? What do you pay for yourself and expense later? Keep it under two minutes and send one reminder. Short surveys get answers. Long ones get ignored until next quarter.
Day 5: Merge, Dedupe and Name Everything
Merge the lists and remove duplicates. Normalize names, because Zoom , zoom.us and Zoom Video Communications are one vendor wearing three hats. Three tabs, one VLOOKUP, zero trust.
Give every row the same columns. App name, owner, number of users, data it touches, monthly cost, where you found it, and renewal date. The owner column matters most. An app with no name next to it goes to triage first.
Sanction, Replace, Retire or Tolerate: What to Do With Each App
Your shadow SaaS discovery list will probably be longer than expected. Do not try to fix everything at once. Run each app through three quick questions we call the Data, Spread, Spend check. Does it touch customer, financial, or personal data? How many people depend on it? Does it cost money or overlap a tool you already approved?
The answers usually point to one of four actions.
- Sanction it when it holds sensitive data and many people rely on it. Add SSO, sign a proper contract, and name an owner.
- Replace it when it does the same job as a tool you already pay for. Move the users and data, then close the accounts.
- Retire it when few people use it but it still holds company data. Export the data, revoke OAuth access, and cancel.
- Tolerate it when data risk, cost, and user count are all low. Log it and look again next quarter.
Here is how it plays out. Your shadow SaaS discovery sprint finds an AI note-taker used by six people. It reads calendars and records client calls, so Data is high. Spread is low and Spend is zero. That points to retire. If those six people have a real need, sanction one approved note-taker for everyone instead.
The people side matters as much as the decision. Blocking without offering an alternative rarely works. The same app comes back a month later under a personal email. Pair every "no" with a faster way to request tools.
Triage decides what stays. Keeping those apps under control over time, through renewals, seat reviews, and access changes, is ongoing SaaS management work.
Make Discovery Event-Driven, Not a Yearly Project
A yearly scan is out of date almost as soon as you export it. Instead, attach a small shadow SaaS discovery check to events that already happen, such as onboarding, offboarding, and renewals.
Then test yourself with the breach-news drill. When a SaaS vendor makes the news for a breach, time how long it takes to answer three questions. Do we use it? Who uses it? What data is in it? If it takes days, your inventory is not ready.
How AssetLoom Supports Shadow SaaS Discovery and Follow-Through
Everything above works with a spreadsheet and some patience. Sooner or later, though, the spreadsheet goes stale, and nobody trusts it during an audit. Our tools cover the two jobs in this article: finding apps and keeping them owned.
Find. The free Shadow IT Scanner pulls apps from Entra ID, Okta, Google Workspace, and access logs in read-only mode. It flags AI and risky apps and exports results to CSV, JSON, or HTML. It reads identity and access signals, so keep your card, AP, and help desk checks.
Track. Once you sanction an app, add it to AssetLoom as a license with its seats, assigned users, and purchase cost. You manage it the same way you manage installed software.
Offboard. When someone leaves, one record shows the laptop to collect and the licenses to reclaim. No three-tab VLOOKUP required.
Start with the scanner. It is free and gives you a clean list for Day 1. Move to AssetLoom when that list is ready to become your real inventory.
FAQs
1. Is shadow SaaS discovery legal, and do we need to tell employees?
Reviewing company card data and admin consoles is normal IT work. Email and browser monitoring need HR and legal review and clear notice to staff. Rules differ by country, so check local privacy law first.
2. Can SSO handle shadow SaaS discovery on its own?
No. SSO only sees apps connected to it, and shadow SaaS usually is not. Use SSO logs as your baseline of approved apps, then compare the other signals against it.
3. How often should we run shadow SaaS discovery?
Run one full sprint, then attach light checks to onboarding, offboarding, renewals, and card changes. Repeat the full sprint once a year to catch what slipped through.
4. Should we block every unapproved app we find?
No. Blocking without an alternative pushes people to personal accounts, which are even harder to see. Triage first and block only the high-risk apps.
5. How do we handle shadow AI tools?
Include them in every shadow SaaS discovery pass, but check data access first. AI note-takers and assistants often ask for calendar, mail, or file access, so review those permissions early.
Final Thoughts
The apps were never really hidden. Finance paid for them, teams used them daily, and nobody connected the two. You already own most of the signals you need. Join them, triage each app with a simple rule, and check again at every onboarding, offboarding, and renewal.
The free Shadow IT Scanner can handle the identity side without a new budget line. When every approved app needs a real owner, AssetLoom keeps licenses and devices together, so your shadow SaaS discovery keeps paying off.





Top comments (0)