DKDKCISSP
← Cybersecurity on the GroundCHALLENGE

The Cloud Storage IT Never Heard About

By Deepak Kumar, CISSP

The problem: A project team is under pressure to hit a client demo date. IT says new file storage takes three weeks. The team creates its own cloud storage on a team member’s account, in an hour, and puts client files in it. IT never hears about it. Months later, it turns up with a public link and no owner.

Words used here: cloud storage is a space on the internet where files are kept, such as a shared online drive. Shadow IT means systems or accounts that a team creates for itself without telling IT. A public link is a web address that lets anyone who has it open a file, with no sign-in.

Think of the worn path across the lawn

A park has a paved path that goes the long way around the lawn. A sign says “Keep off the grass.” But everyone is late, and the shortest way from the office to the cafe is straight across. After a few weeks, there is a brown line worn into the grass. The people are not careless. The official path was just too long.

The worn path across the lawn
Sign: KEEP OFF. A worn line across the grass
OfficeThe paved path goes the long way round.
CafeThe short way is straight across.
People take the short path. Make the right path the short one.

What it looks like at work

A project team has to show a demo to a client in five days. They need a place to share large test files with the client. They ask IT for a storage space, and IT says it takes three weeks, because it needs approval, a cost code and a security check. A developer opens a free cloud storage account in their own name, uploads the client’s sample files, and sends the client a link. The demo goes well. Four months later, a scan finds the storage space. The link is still public, the developer has moved to another team, and nobody knows who pays the small bill.

How a team ends up with its own cloud storage
  1. 11. Date is nearClient demo is in 5 days.
  2. 22. Ask ITNew storage takes 3 weeks.
  3. 33. ShortcutI will use my own cloud account.
  4. 44. It worksDone in an hour. No one is told.
  5. 55. Months laterPublic link, client files, no owner
Nobody was careless. The official way was just too slow.

Both sides are half right. The project team is right that the date is real, and that waiting three weeks could lose the client. IT and security are right that client files must not sit in a place nobody owns. What is missing is a fast, approved way, so that the safe path is also the short path.

You will notice it when:

  • Teams say “IT takes too long” and give an actual number of weeks.
  • Expense claims show small payments to cloud or file-sharing services.
  • Client files are found in places IT does not manage.
  • Nobody can say who owns a storage space that someone found.
  • The team looks surprised, not guilty, when it is found.

What exactly needs fixing

The first fix is not to punish the team. It is to find the storage, close the public link, and give the team a fast approved way. This card shows the whole problem on one page:

A project team created its own cloud storage
WHAT IS BROKEN

A project team set up its own cloud storage for client files, and nobody in IT knows about it.

WHERE IT IS

A cloud storage space on a team member's own account.

WHAT COULD GO WRONG

A public link leaks client files, and nobody owns it.

WHAT IT COSTS US
  • Client data leak
  • No backups
  • No owner
  • Hidden bill
THE FIX, IN THREE MOVES
  1. 1
    1. Find it today
  2. 2
    2. Move to approved
  3. 3
    3. Add a fast lane
WHO FIXES IT

Who fixes it: IT head, project lead

BY WHEN

By when: found in 1 week

A blank copy of this card is in the Tools section.

Why it happens

  • The official way is slow. Three weeks against a five-day deadline is no contest.
  • The cloud makes it easy. A free account takes minutes and needs no approval.
  • Teams are judged on dates. Not on where the files are kept.
  • Nobody told the team the risk. A public link feels like a normal way to share.
  • IT does not see it. The bill is small and sits on a personal card.
  • People move on. The owner leaves, and the storage stays.

What happens if you ignore it

Client files sit in a place that nobody guards, and nobody remembers.

  • The public link leaks client files, and the client finds out before we do.
  • There are no backups, so the files can be lost.
  • A bill keeps running on a personal card, until the card expires and the files vanish.
  • Auditors ask where client data is kept, and we cannot answer fully.

At a glance

QuestionAnswer
How likely is it to hurt us?Very likely. It happens in most teams that face tight dates.
Worst case?Client files leak through a link nobody knew existed.
What does it cost?A client incident, a contract problem, and a failed audit.
What if we wait?More teams copy the shortcut, and more storage appears.
What does the fix cost?A fast lane in IT, and one scan to find what exists.

How to fix it, step by step

Find it, fix it quietly, and then make the right path the short one.

  1. Do not start with blame. Ask the team what they needed and why. They will tell you about the slow path.
  2. Find what is in it, today. Which files? Client files? Who can open it? Is the link public? Turn off the public link first.
  3. Name an owner. One person, usually the project lead. Put a label on the account so it is visible.
  4. Move the files to approved storage. Set a date, for example two weeks (set your own). Then close the shortcut.
  5. Count how long the official way takes. From request to ready. If it is weeks, that is the real finding.
  6. Build a fast lane. A ready-made, approved storage space that a project can get in a day, with the safe settings already switched on.
  7. Allow safe self-service where it makes sense. Teams can create storage themselves, but only inside an approved account where public links are switched off.
  8. Look for the others. Check expense claims for cloud services, and scan for unknown accounts. Treat each as a find, not a fault.
Make the right path the fast path
A. Fast lane in ITApproved storage in one day, not three weeks.
B. Safe self-serviceTeams create it, but public links are off.
C. Find and adoptLook for unknown cloud accounts. No blame.
Do all three. A and B stop it, C finds what is already there.

The picture shows three ways to make the right path fast. A and B stop new shortcuts from appearing. C finds the ones that already exist.

Who to bring in: The head of IT, the project lead, the person who owns the budget or finance approvals, security, and the client contact if client files were exposed.

Tools and templates

Where to look for storage nobody told IT about

PlaceWhat to check
Expense claims and company cardsSmall, repeated payments to cloud or file-sharing services
Single sign-on logsSign-ins to cloud services that IT did not set up
Network scanTraffic to unknown cloud storage addresses
Ask the teams“Where do you keep client test files?”

Request for approved storage (the fast lane)

FieldWrite here
Project and ownerName of the project and one person
What will be storedClient files? Test data? Code?
Who needs accessNames or groups
How long it is neededA date
Safe settingsPublic links off, sign-in required, backups on (already set)

Blank finding card

FieldWrite here
What is brokenOne line, in plain words
Where it isThe system, team, or process
What could go wrongIn one sentence
What it costs usMoney, time, a leak, lost trust
The fixThe exact action
Who fixes itOne name or one team
By whenA date, not “soon”

Email to the project lead

Subject: The cloud storage we found, and a faster way for next time

Hi [name]. We found a cloud storage space with client files that was not set up through IT. I am not looking to blame anyone. I understand the demo date was tight and the official way takes three weeks. Could we meet for 20 minutes? I would like to turn off the public link today, agree who owns it, move the files to approved storage, and then work with you and IT on a faster way for the next project.

Field tip

Do not ask, “Who set this up?” Ask, “What did you need, and why was the official way too slow?” The answer is the fix.

Words used in this chapter

  • Cloud storage: a space on the internet where files are kept, such as a shared online drive.
  • Shadow IT: systems or accounts a team creates for itself without telling IT.
  • Public link: a web address that lets anyone who has it open a file, with no sign-in.
  • Fast lane: a quick, approved way to get what a team needs, with safe settings already on.
  • Approved account: an account that IT owns and manages, with safety rules already set.