Shadow IT: the systems a company runs without knowing
Shadow IT is any system, service or device in use for company work that the IT and security teams did not approve and do not know about.
What it looks like in practice
None of these involve anybody breaking a rule on purpose.
- A software trial
- A team signs up for an online tool with work email addresses and starts uploading customer data.
- A cloud account on a team card
- Engineers open an account to meet a deadline. It is never moved under the company’s organisation.
- A campaign microsite
- An agency builds and hosts it. Two years later it still answers, on software nobody has updated.
- A test environment
- Created for a demonstration with a copy of production data, and left running.
- An acquired company
- Its whole estate arrives on the day the deal closes, with no register.
Why it is a security problem
A system the security team does not know about receives none of what the team provides. It is not patched on a schedule, not behind single sign-on, not in the backups, not in the log pipeline and not in the incident plan. It has no owner to call when something goes wrong.
To somebody scanning from the internet it looks exactly like any other company system.
Three ways it gets found
- 01
From the money
Expense claims and card statements show subscriptions that procurement never saw.
- 02
From the network and identity logs
Sign-ins with company addresses, and traffic to services that are not on the approved list.
- 03
From outside
External discovery finds the internet-facing part without anyone declaring it: the forgotten host, the unregistered cloud account, the agency site. Across first scans, outside-in discovery typically surfaces 30–60% more external assets than the internal inventory holds.
In ShadowMap
The capability this term leads to
Attack Surface Management Continuous outside-in discovery of the internet-facing estate, including the origin infrastructure sitting behind your edge. This is the ShadowMap capability that finds the internet-facing part of shadow IT from a single domain.Questions about shadow it
Is shadow IT always bad?
No. It usually shows where the approved tools were too slow or did not exist. The risk is in not knowing about it. Once a system is known it can be brought under control or retired.
Can shadow IT be prevented?
It can be reduced with faster approval routes and controls on sign-up and spending. It cannot be removed, which is why continuous discovery is used alongside policy.
Related terms
- EASM : External attack surface management (EASM) is the continuous discovery, inventory and assessment of everything an organisation exposes to the public internet, carried out from the outside and without relying on the organisation’s own asset list.
- CAASM : Cyber asset attack surface management (CAASM) is a category of tool that builds a single inventory of an organisation’s assets by reading records from the systems it already runs, through API integrations, and reconciling them.
- All glossary terms
See what your own external estate looks like
A 30-minute demo shows Attack Surface Management on your questions about shadow it. Or send one apex domain and receive a written exposure snapshot.