The problem: A team lead signs up for a 30-day free trial of a file-sharing tool, to share large files with customers. Nobody in security or IT is told. The vendor extends the trial twice. Fourteen months later, 200 staff use it, customer data sits inside it, and there is no contract, no security review, and no entry on the asset list.
Words used here: a trial is a short, free test of a product. Production means a system that is in real, daily use with real data. Shadow IT means a tool used at work without IT or security knowing. An asset list is the company’s list of the systems it owns and uses.
Think of the temporary footbridge
A council puts up a wooden footbridge over a stream while the real bridge is repaired. It is meant to last a month. The real bridge is delayed, then forgotten. A year later, hundreds of people cross every day, a school group uses it, and nobody has inspected it. Everyone assumes someone else did.
The trial is the temporary bridge. The customer data is the school group.
What it looks like at work
The team lead is not careless. He needs to send 2 GB files to customers, and the email system rejects them. A search finds a tool with a free trial and a simple sign-up page. He tries it, and it works. A month later, the vendor offers an extension. These are example numbers.
Over the following months, colleagues join, then another department. Customer contracts and personal data go in, because it is easy. Nobody told security because it was only a trial. When the auditor asks for the list of tools that hold customer data, this one is not on it, and the vendor’s sales team sends a price that is much higher than the trial.
- 11. Real need2 GB files, and email rejects them
- 22. Free trialSimple sign-up, nobody in IT told
- 33. ExtendedTwice, with no one owning the end date
- 44. Spreads200 staff, customer data goes in
- 55. AuditNot on the list, no contract, high price
Both sides have a fair point. The team lead solved a real problem quickly, and a formal process would have taken weeks. Security is right that a tool that holds customer data needs a contract and a review. Neither side acted in bad faith. The trial simply had no end, and no one noticed when it turned into the real thing.
You will notice it when:
- A tool is in use that is not on the asset list.
- Staff mention a tool that IT and security have never heard of.
- A “free” account has been renewed or extended more than once.
- Real customer data is in a tool that was meant to be a test.
- The first time anyone in security hears of it is the vendor’s invoice or an audit.
What exactly needs fixing
The fix is not to ban trials. It is a simple rule for how trials work, a clear decision at the end of each one, and a regular sweep for forgotten ones. This card shows the whole problem on one page:
A free file-sharing trial is now used by 200 staff and holds customer data, with no contract or review.
The file-sharing tool, the asset list, and the way trials are started.
A breach at the vendor exposes customer data held with no contract.
- Legal gap
- Failed audit
- Forced move at short notice
- Hard to leave
- 11. Trial ruleThirty days, no real data, tell security first, answer in two days
- 22. End or adoptAt the end, adopt properly with a contract and review, or shut it down
- 33. Sweep for othersLook in expense claims, sign-in logs and email for forgotten trials
Who fixes it: head of security with the team lead
By when: rule published and sweep done in 4 weeks
A blank copy of this card is in the Tools section.
Why it happens
- A trial is free and quick. A formal buy is slow.
- Nobody owns the end date. The vendor is happy to extend.
- There is no rule for trials. So people use judgement, and judgement varies.
- Real data creeps in. Staff use what is easiest.
- No one looks for forgotten trials. So they stay forgotten.
What happens if you ignore it
The company ends up depending on a tool it has never examined.
- Customer data is held with no contract, so there is no promise on where it is kept or how it is deleted.
- If the vendor is breached, the company may not even know it was a customer.
- Moving off the tool becomes costly because 200 people rely on it.
- The auditor finds a tool that was not on the list, and asks what else is not.
At a glance
| Question | Answer |
|---|---|
| How likely is it to hurt us? | Very likely, wherever a credit card or an email address is enough to sign up. |
| Worst case? | A breach at the vendor exposes customer data held with no contract. |
| What does it cost? | A legal gap, a failed audit, and a forced move at short notice. |
| What if we wait? | More users and more data go in every month. |
| What does the fix cost? | A one-page rule and a monthly sweep. |
How to fix it, step by step
Set a rule, decide at the end, then sweep for the trials already running.
- Write a one-page trial rule. Thirty days, no real customer or staff data, and tell security before you start.
- Make it easy to follow. A short form and a quick answer, within two working days.
- Set the end date at the start. Put it in the calendar of the person who signed up.
- At the end, decide. Either adopt it properly, with a contract and a review, or shut it down.
- Sweep for existing trials. Check expense claims, single sign-in logs, and email for sign-up messages.
- For each one found, ask what data is in it. Prioritise those with customer data.
- Offer an approved alternative. If people use the tool because there is no good one, give them one.
The picture shows the order: set a rule, decide at the end, then sweep for the trials already running. The sweep usually finds more than anyone expects.
Who to bring in: The head of security (writes the rule), the team lead who started it (explains the need), legal or privacy (checks the data position), procurement (negotiates if it is adopted), and finance (spots the card payments).
Tools and templates
Trial register
| Tool | Who started it | Start date | End date | Real data in it? | Decision |
|---|---|---|---|---|---|
| Tool 1 | Yes / No | Adopt / Shut | |||
| Tool 2 | Yes / No | Adopt / Shut | |||
| Tool 3 | Yes / No | Adopt / Shut |
Blank finding card
| Field | Write here |
|---|---|
| What is broken | One line, in plain words |
| Where it is | The system, team, or process |
| What could go wrong | In one sentence |
| What it costs us | Money, time, a failed audit, lost trust |
| The fix | The exact action |
| Who fixes it | One name or one team |
| By when | A date, not “soon” |
Email to the team lead
Subject: The file-sharing tool your team has been using
Hi. I saw that your team has used the file-sharing tool since last year, and it clearly solves a real problem. I would like to help make it official. Could we meet for 30 minutes to look at what data is in it, set up a proper contract, and make sure it is safe? I am not looking to take it away. I am looking to make it something we can rely on.
Field tip
When someone tells you about a trial, ask two questions: “When does it end?” and “Is there real data in it?”
Words used in this chapter
- Trial: a short, free test of a product.
- Production: a system in real, daily use with real data.
- Shadow IT: a tool used at work without IT or security knowing.
- Asset list: the company’s list of the systems it owns and uses.
- Sweep: a search for things that were forgotten.
- Adopt: to approve a tool properly, with a contract and a review.