Shadow IT is any software, device or cloud service your team uses for work without your IT provider knowing about it or approving it. The main risks are data leaks, security gaps nobody patches, compliance trouble, lost cyber insurance coverage and wasted spend. The good news: for a small business it is manageable. You find what is in use, decide what stays, and make the approved path easier than the workaround.
If you run a company in Ohio or Michigan with 10 to 200 employees, you almost certainly have some shadow IT today. That is not a sign of a bad team. It is a sign that people are trying to get work done. This guide covers what shadow IT looks like in a small office, what it can cost you, how to discover it, and how to build a policy that people will follow.
TL;DR
- Shadow IT is technology used for work without IT’s approval or knowledge, such as personal cloud storage, unsanctioned chat or video tools, and AI assistants.
- The biggest risks are data breaches, unpatched and unbacked-up systems, compliance exposure, and possible nullification of cyber insurance.
- Find it by comparing what is on your network to what you approved, reviewing logs and app sign-ins, and asking staff without blame.
- Bans rarely work. A short policy, a fast request process and an approved app list work better.
- A managed IT partner can run discovery, monitoring and the approval process for you.
Table of Contents
- What shadow IT is and why your employees use it
- Common shadow IT examples in a small office
- The main shadow IT risks
- Shadow AI: the newest shadow IT risk
- How to discover shadow IT in your business
- Deciding what to do with what you find
- What a shadow IT policy should cover
- How to control shadow IT without slowing people down
- Our perspective on shadow IT
- How Mavericks helps you find and manage shadow IT
- FAQ
- Sources
What shadow IT is and why your employees use it
IBM defines shadow IT as software, hardware or other IT resources used on an enterprise network without the IT department’s approval, knowledge or oversight. The UK’s National Cyber Security Centre describes the same thing as unknown assets used for business purposes that are not covered by asset management or aligned with company IT policy.
The reasons are ordinary. According to IBM, employees adopt these tools because they can start using them without waiting for approval, or because they believe the tool works better than what IT offers. The NCSC makes a point worth remembering: shadow IT is rarely malicious. It usually happens because staff struggle to complete a task with the sanctioned tools, so they improvise.
That matters for how you respond. If the person who set up a free file-sharing account was trying to get a proposal to a customer by 5 p.m., a reprimand teaches everyone to hide the next one. The NCSC warns that a poor security culture makes shadow IT harder to detect, because staff will not come forward if they fear punishment.
How common is it? IBM cites Cisco data indicating that 80% of employees use shadow IT, and an IBM Institute for Business Value study found that 41% of employees acquired, modified or created technology without their IT team’s knowledge. Those figures describe workers broadly, not only large enterprises, so assume your office is not an exception.

Shadow IT versus business-managed IT
Not every tool outside the IT closet is shadow IT. ISACA draws a useful line: shadow IT is adopted without the IT department’s knowledge, while business-managed IT is sanctioned but run by a department or outside vendor. The first is a blind spot. The second is a decision you made. Your goal is to move tools from the first category to the second, or remove them.
Common shadow IT examples in a small office
IBM’s examples are simple and familiar: sharing work files through a personal cloud storage account, running meetings on an unauthorized video conferencing platform, or starting an unofficial group chat. In a typical Ohio or Michigan small business, the list tends to look like this:
- Personal file storage. A sales rep syncs customer quotes to a personal cloud drive so they can open them at home.
- Personal email forwarding. Someone forwards work email to a personal inbox to read it on the road.
- Free file converters and PDF tools. An office manager uploads a contract to a random website to merge pages.
- Unapproved messaging and video apps. A crew chat in a consumer app, or a customer call on a platform you do not license.
- AI chat assistants. A team member pastes customer data into a public AI tool to draft a reply.
- Personal devices and home equipment. Phones, tablets and laptops that never went through setup, or a network device someone plugged in to fix weak Wi-Fi.
- Cameras and smart gadgets. A consumer camera or smart device bought on impulse and connected to the office network. If you have one, these steps for securing P2P cameras are a good starting point for locking it down or deciding to replace it.
- Departmental software subscriptions. Marketing buys a design or email tool on a credit card, and nobody in IT ever hears about it.
Notice that none of these looks sinister. Each solves a real problem, which is exactly why they spread.
The main shadow IT risks
The most authoritative list for a US business comes from the Federal Financial Institutions Examination Council. Its IT Examination Handbook says that failing to address shadow IT can create an unknown attack vector, because management does not know the devices, software or services exist. It lists specific risks. Here they are in plain business terms.
Security weaknesses and data breaches
A tool nobody configured probably does not meet your security standards. The NCSC notes that any device or service not set up by the organization will probably fall short of required security standards, could introduce malware, and could even be pulled into botnets or used for cryptomining. No multi-factor authentication, weak passwords and shared logins are the usual culprits. Our password policy checklist covers the baseline every account should meet.
No patching, no backup, no recovery
You cannot update what you do not know about. The FFIEC lists the inability to patch unknown devices and software, and the inability to back up and recover them. If the only copy of a customer file lives in a personal account and that employee leaves, the file leaves too. The FFIEC also warns that malware can spread through automatic backups.
Compliance and legal exposure
Data in the wrong place can break your obligations. The FFIEC points to legal risks tied to data use or ownership and software or service license penalties. If you handle customer financial information, our guide to the FTC Safeguards Rule shows why knowing where data lives is a requirement, not a nice-to-have. Academic researchers Haag and Eckhardt describe shadow IT as an insider threat to a company’s security posture, with data loss, leaks and regulatory breaches possible when sensitive data sits on third-party servers, even when intentions are good.
Cyber insurance problems
This one surprises owners. The FFIEC lists the potential nullification of cyber insurance among shadow IT risks. If an incident traces back to an unmanaged system that contradicts what you told your insurer about your controls, a claim can get complicated. See what underwriters actually look at in our cyber insurance requirements guide.
Hidden costs
Rogue subscriptions duplicate tools you already pay for, and a breach has its own price tag. Haag and Eckhardt report research indicating that one in five companies has faced a cybersecurity incident linked to shadow IT, at an average cost above $4.88 million in 2024. That figure comes from companies of all sizes, so treat it as a sense of scale rather than a forecast for your business. For context, IBM and the Ponemon Institute reported in 2025 that the average US data breach cost reached a record $10.22 million. Even a small fraction of those numbers is serious for a small company.

Shadow AI: the newest shadow IT risk
The NCSC notes that shadow IT can include AI technologies used without permission, often called shadow AI. The practical danger is simple: someone pastes a customer list, a contract or a spreadsheet of employee data into a public AI tool to save an hour, and that data has left your control.
The same IBM and Ponemon research reported that 20% of organizations studied suffered a breach involving shadow AI security incidents. If your team is experimenting with AI, read our post on AI cybersecurity mistakes and put an AI line in your acceptable use policy now, before someone writes it for you by accident.
How to discover shadow IT in your business
Discovery is the first real step. You cannot manage what you cannot see. Combine technical checks with honest conversations.
1. Compare your network to your approved inventory
The FFIEC recommends regularly comparing network assets to approved inventories and using detection tools to catch unauthorized IoT devices and rogue Wi-Fi connections. If you do not have an inventory, building one is step zero.
2. Look at cloud apps in use
Cloud access security tools can reveal applications nobody told you about. Microsoft’s tutorial on discovering shadow IT with Defender for Cloud Apps describes running cloud discovery, integrating with endpoint protection and collecting firewall or proxy logs. Its catalog covers more than 31,000 apps scored against over 90 risk factors. If you run Microsoft 365, ask your IT provider what discovery your licenses already include.
3. Review identity and expense records
Check which third-party apps employees have signed into with their work email or granted access to company accounts. Then scan company card statements and expense reports for software subscriptions IT never approved. This is cheap and surprisingly revealing.
4. Ask your people, without blame
ISACA recommends a multifaceted approach: network traffic analysis, cloud access security brokers, employee surveys and interviews, and asset management tools. It specifically notes that nonpunitive surveys reveal what people use and why. A short anonymous form asking “What tools do you use that IT does not provide, and what problem do they solve?” can teach you more than a log review.
5. Add data loss prevention
The FFIEC also points to data protection and data loss prevention tools as a way to see sensitive data moving where it should not. We cover how to start in our data loss prevention checklist for small businesses.
Deciding what to do with what you find
Discovery produces a list, and the temptation is to delete everything on it. Resist that. The FFIEC cautions that identifying shadow IT does not eliminate it, and that removing it without a plan can disrupt a department process and even affect service delivery and revenue.
Its suggested approach works well for a small business. For each item:
- Identify the security risk and whether there was any malicious intent (almost always there was not).
- Find out why it is used.
- Determine which customers or processes depend on it.
- Check connections to third-party providers.
- Decide: remove it, or move it to infrastructure you manage.
- Review your policies and tools to see what let it happen.
A practical way to sort the list is by two questions: does it touch sensitive data, and is there an approved alternative that does the same job? Anything touching customer, financial or employee data with an easy alternative gets migrated first. Low-risk tools with no alternative can be formally approved.
What a shadow IT policy should cover
Your policy does not need to be long. ISACA says it should give clear guidelines for evaluating and approving new technologies, channels for employees to suggest solutions, the risks and consequences of unauthorized systems, and a way to bring valuable tools into the official IT portfolio.
Translated for a small business, one to two pages should answer:
- What needs approval? Any software, app, AI tool, device or account that touches company data.
- How do I ask? One email address or form, with a promised response time.
- What data can never go in an unapproved tool? Customer records, financial data, employee information, anything covered by a contract or regulation.
- What happens if I already use something? Tell IT, and the answer is a review, not a penalty.
- Who decides? Name an owner, whether your IT provider, an operations lead or both.
If you already have an acceptable use policy, add shadow IT and AI to it rather than creating a second document. Our guide to acceptable use policies walks through what to include and how to roll it out so staff actually read it.
How to control shadow IT without slowing people down
IBM notes that organizations once tried to ban shadow IT entirely, but IT leaders increasingly accept it as inevitable and have come to value the agility it can bring. The NCSC’s guidance points the same way: avoid unnecessary lockdowns, make it simple and quick to request services, provide controlled access to tools outside the usual offerings, bring unsanctioned services under control, and build a culture where staff talk openly about issues.
For a company your size, that adds up to a short routine:
- Publish an approved app list. People should know what is already available before they go looking.
- Set a fast approval lane. If a request takes weeks, people will skip it. Aim for answers in days for low-risk tools.
- Offer amnesty once. Invite staff to declare what they use, with no penalty, then handle each item using the steps above.
- Require business accounts and multi-factor authentication on anything that holds company data. Our SaaS security checklist covers what to check before you approve a new cloud tool.
- Review quarterly. New tools appear constantly. A recurring review, not a one-time cleanup, keeps the list honest.
- Assign ownership. ISACA suggests a cross-functional team to oversee shadow IT, which for a small company can be an owner, an operations manager and your IT partner meeting briefly each quarter.
ISACA also argues that valuable shadow IT can be turned into business-managed IT by assessing value and risk, formalizing adoption, integrating the tool with your existing systems and providing training. In other words, the tool your team found might become the one you standardize on.
Our perspective on shadow IT
We see the same pattern in small businesses again and again. Nobody sets out to create risk. A good employee needs something done, the approved route is slow or unclear, and a free tool is one click away.
That is why we do not treat shadow IT as a discipline problem. We treat it as a visibility and service problem. When a business has a single outsourced IT department handling support, security, phones, print and cloud, there are fewer gaps for unofficial tools to fill, and fewer places for them to hide.
Our approach is built around a proactive support model with 24/7 monitoring and a local, USA-based help desk in Ohio, with an average help desk response of under 12 minutes. When someone can reach a real person quickly and get an answer, they are far less likely to go find their own workaround.
If you are not sure what your team is using today, start with an honest inventory and a conversation, not a crackdown. We can help you run both, then keep watching so the list does not drift.
Jeffrey
How Mavericks helps you find and manage shadow IT
Mavericks Office Solutions operates as an outsourced IT department for small and medium-sized businesses. For shadow IT, that means one provider handling managed IT services and cybersecurity together: help desk support, 24/7 monitoring, and security planning, with the same team also covering voice, print, cloud hosting and Microsoft 365.

If you want strategic guidance without a full-time hire, our fractional IT leadership can help you write the policy, set up the approval process and own the quarterly review. To talk through where you stand, contact Mavericks Office Solutions. If you are still weighing providers, our eight-point scorecard for choosing a managed IT provider is a useful way to compare.
FAQ
What are the risks of shadow IT?
The main risks are data breaches and data loss, security weaknesses in unmanaged tools, an inability to patch or back up unknown systems, compliance and legal exposure, software license penalties, and possible nullification of cyber insurance. These are the risks the FFIEC handbook lists. Wasted spend on duplicate tools is a common side effect.
What is an example of shadow IT?
An employee saving customer files to a personal cloud drive is the classic one. Others include running meetings on an unapproved video platform, starting an unofficial group chat, or pasting company data into a public AI tool. Each is usually a workaround for a real task, not an act of bad faith.
How do I find shadow IT in my company?
Start by comparing devices and apps on your network to your approved inventory. Then review cloud app usage, third-party sign-ins and software charges on company cards, and run a no-blame survey of your staff. Your IT provider can also use cloud discovery tools to surface apps nobody reported.
Should I ban shadow IT?
A blanket ban usually pushes it further out of sight. A better path is a short policy, a quick approval process, an approved app list and a one-time amnesty, so people bring tools forward and you can approve, migrate or retire each one deliberately.
What should a shadow IT policy include?
It should say what needs approval, how to request it, which data may never go into unapproved tools, what to do if you already use something, and who decides. It should also describe how valuable tools can be added to your official IT portfolio.
Sources
- What Is Shadow IT? | IBM
- Shadow IT | NCSC
- FFIEC IT Examination Handbook: III.B.3 Shadow IT
- ISACA Journal 2024, Volume 6: Navigating the Shadows
- Dealing Effectively with Shadow IT, MIS Quarterly Executive
- Data breach costs study, BNN Bloomberg
- Discover and manage Shadow IT, Microsoft Learn
- Secure P2P Cameras: 5 Steps for Tech Savvy Homeowners