Every IT team has a shadow IT problem. The more honest version is that most of the unauthorized tools in your environment are there because IT said no, or the official process took longer than the deadline the person was facing. That changes how you should think about fixing it.
Shadow IT is not primarily a rogue behavior problem. It is a procurement and responsiveness problem wearing a security costume. And if you approach it only as a security risk to stamp out, you will stamp it out into better hiding, not out of existence.
Here is how I audit for it, what I actually find, and what I do when I find it.
What Shadow IT Actually Looks Like Now
Forget the 2015 image of a developer running their own server in a closet. In 2026, shadow IT is mostly SaaS, mostly free-tier or personal-card billing, and mostly being used for genuinely legitimate work.
Three categories show up most often in my experience:
Personal tools doing work jobs. A salesperson sharing files through a personal Dropbox because the company SharePoint is too slow. A support agent routing customer messages through their personal WhatsApp Business number because nobody got around to setting up a proper shared inbox. A recruiter managing candidates in a Google Sheet because the ATS is locked to HR and they needed something now.
Team-level tools that bypassed procurement. A marketing team using an analytics platform that never went through security review. A design team running a project management tool that is not connected to SSO. A customer success team logging notes in a tool that has no offboarding protocol because IT does not know it exists.
Critical workflows running on one person's login. This is the most dangerous category. The company's LinkedIn ad account sitting under a contractor's personal email. The main Stripe dashboard accessible only through the CEO's Google account. An API integration that authenticates as a former employee whose account was disabled but whose tokens were never revoked.
That last one has bitten me more than once during offboarding. The account is disabled. The tokens keep working for months.
Four Ways I Find the Tools We Are Not Supposed to Know About
Expense report mining. This is the simplest and most underused method. Search the last six months of expense reports or reimbursement requests for the words "software," "subscription," "app," and "license." Personal-card billing shows up here before it shows up anywhere else. You are not auditing for misconduct; you are auditing for coverage gaps. When you find a recurring SaaS charge being expensed by three different people on the same team, you have found a tool the team genuinely needs and nobody formalized.
SSO gap audit. If you have enforced SSO through Azure AD, Okta, or Google Workspace, any service that employees have connected to their corporate identity but that is not in your sanctioned app catalog is a shadow service. Pull the list of authorized apps from your identity provider quarterly. The ones you do not recognize are the conversation starters. This takes roughly an hour once the query is set up. If you have not enforced SSO, start there first because this audit becomes much more valuable once you have.
DNS and email header review. Some shadow services send email from your domain without being listed in your SPF record. A quarterly SPF audit catches services that are touching your domain reputation without IT's knowledge. I have found unsanctioned email marketing tools, outbound sales platforms, and once, a newsletter tool a single team member had connected to the company domain for a personal project. These are deliverability risks as much as they are governance risks.
Offboarding as an audit event. When someone leaves and you work through their access revocation, you will discover services they had that nobody else knows about. The discipline is to write those down every single time and feed them back into a running inventory. Treat every departure as a free audit of one person's digital footprint inside your environment. Over a year, the pattern across twenty offboardings tells you more about your shadow IT landscape than any dedicated scan.
The Actual Risks You Are Managing
It helps to be specific about what you are protecting against, because a vague "security risk" framing leads to heavy-handed responses that drive the problem underground.
Orphaned access after departure. A service under one person's login has no offboarding path. When they leave, that account stays active. If it is a customer-facing tool, it may also still be sending or receiving data. This is the clearest risk and the most concrete to address.
Data residency you did not consent to. Customer data in an unsanctioned CRM sitting in a jurisdiction your contracts did not account for is a compliance problem, not just a convenience one. Most small-team SaaS tools store data in the US by default. If you are operating under GDPR or handling sensitive data under a customer's specific requirements, the location of that data matters.
Single-point billing failures. A critical workflow billing to a personal card is a reliability risk. When the card expires, is stolen, or when the person leaves, the workflow stops. I have seen customer-facing automations go dark because a subscription renewed to a card that no longer existed. Nobody knew the tool existed until the complaints started.
Invisible integrations. Third-party tools connected to your core systems through APIs or OAuth can read and write data outside your data governance model. An unsanctioned sales tool connected to your CRM's OAuth may have read access to your entire contact database. That access persists until you explicitly revoke it, regardless of whether anyone still works with the tool.
What To Do When You Find Something
The goal here is governance, not discipline. Coming in with a "who authorized this?" posture creates a chilling effect where people stop telling you what they are using, which makes the problem worse. The more effective approach:
For each discovered tool, ask two questions. First, is this filling a real gap? If three people on the same team are all paying individually for the same tool, the gap is real and IT should fix it, not punish the workaround. Second, can IT sanction and manage it properly? That means SSO connection, an owner who is not the person who found it, and a documented offboarding protocol.
Once a year, run a formal amnesty window. Tell all teams: for the next two weeks, you can declare any tool you are using that has not gone through IT procurement. We will review it, either sanction it or offer a managed alternative, and there will be no questions about how it got there. The teams that take you up on it hand you exactly the inventory you have been trying to build from the outside.
Shadow IT exists where IT governance has a gap. Closing the gap closes the shadow, in a way that locking things down never will.
The Running Inventory That Keeps This Manageable
None of this has to be a big project. The practical cadence I use:
Monthly: review the last three months of expense reports for recurring software spend not in the IT inventory.
Quarterly: pull the sanctioned app list from the identity provider and review anything added since the last quarter. Run the SSO gap check.
On every offboarding: document every tool, account, and integration discovered during access revocation. Add it to the inventory. Flag anything that had no offboarding process.
Annually: run the amnesty window. Review the full SPF and DNS record set for services sending from your domain.
The first time you do this, the list of discovered tools is usually longer than you expect. After two or three cycles, you are mostly catching new additions rather than backlogged history. The inventory becomes a living document instead of a one-off cleanup project.
The goal is not a perfectly clean environment. That does not exist in any organization of meaningful size. The goal is knowing where the edges are, so when something breaks or someone leaves, you are not discovering the dependency at the worst possible moment.
Working through a shadow IT audit or trying to build a tool inventory for the first time? I am happy to talk through the approach. Reach out here.