Local and Cloud Data Security
Decide which security jobs belong to a cloud provider and which to you, protect a cloud account, and choose the narrowest safe file-sharing setting.
The contracts folder anyone could open
Sameer Joshi needs to send a medicine distributor in Mumbai the signed supply contract, so he opens Tulsi Health's cloud storage, clicks Share on the whole supplier contracts folder and picks "Anyone with the link". It is quick, and the distributor opens it in seconds. Two months later, Neha finds that the same link was pasted into a group chat with forty people in it, and that the folder holds the prices and terms agreed with every supplier. Nothing was hacked. The cloud service worked exactly as designed, and one setting chosen by a person decided who could see the data. That is the central idea of cloud data security: the provider keeps its part safe, and the settings and accounts are yours.
Your cupboard or someone else's building
Data can live in two broad kinds of places. Local storage means data kept on devices you own and hold yourself, such as the counter billing laptops or a small server (a computer that stores files and serves them to other computers) in the Kothrud office cupboard. Cloud storage means data kept on a provider's computers in large buildings called data centres, which you reach over the internet using an account. Tulsi Health uses both: MedLedger keeps each store's bills locally, while staff email, the shared drive and the customer app's database are in the cloud.
Neither is automatically safer. Local data depends on how well you look after the device; cloud data depends on how well you look after the account and its settings.
With local storage you have full control: you decide where the device sits, who touches it and when it is updated. You also carry every job yourself, from fixing a failed disk to locking the cupboard. With cloud storage you hand the building, the machines and much of the upkeep to a provider with far more staff and money for security than a pharmacy chain. What you lose is physical control, and in exchange the data becomes reachable from anywhere in the world by anyone who has the right password or link. The danger moves from the cupboard to the account.
Who locks which door
Living in a rented flat makes this clear. The landlord looks after the building: the structure, the main gate, the lift and the water pipes inside the walls. You look after your own flat: you lock your door, decide who gets a spare key and do not leave the window open when you go to Nashik for the weekend. If a burglar walks in through the door you left unlocked, the landlord did nothing wrong. Cloud services split the work in the same way, and the split is called the shared responsibility model.
The provider secures everything from the building up to the service. Everything about who can reach your data, and what data you put there, stays with you.
The exact line moves depending on what kind of service you use. If you rent bare computing power from a provider and install your own software on it, more of the stack is your job; if you simply use a ready-made file-sharing service, as Tulsi Health does, the provider handles more. One thing never moves, though: the customer is always responsible for its own data, its accounts and who it shares with. Most cloud breaches in the news come from that customer side, such as public folders, weak logins and old accounts, not from someone breaking into the provider's data centre.
Sort these jobs into the right column. For each one, ask whether a Tulsi Health employee could do it, or only the provider.
Protecting the cloud account itself
In the cloud, the account is the front door to everything, so it deserves the strongest lock you have. Every account needs a long password that is not used anywhere else, plus two-step login, where a second proof such as a code from an app on your phone is needed after the password. Administrator accounts, the few that can change settings for everyone, should be used only for that work and be protected even more carefully. The provider's alerts for sign-ins from new devices or cities should go to a person who reads them. Recovery details matter too, because an attacker who can change the recovery phone number can take over the account through the "forgot password" route.
Account hygiene is the other half. When someone leaves, their account is switched off the same day. Every few months Neha reviews which outside apps have been given access to staff accounts, because a free PDF tool that someone once allowed to "read your files" keeps that permission until it is removed.
Sharing files without handing out keys
Most cloud services offer a few sharing levels. You can share with specific people, who must log in with their own accounts to open the file. You can share with everyone in your organisation. Or you can choose anyone with the link, which lets whoever holds the web address open the file without logging in. That last option is like leaving your house key under the doormat for a friend: convenient, but anyone who learns where it is can let themselves in, and you will never know who did. Links get forwarded, pasted into chats and saved in browser history.
Three choices decide most of the risk: who can open it, whether they can change it, and when access ends.
Two more choices shrink the risk further. Permissions decide what a person can do with a shared file: view only, comment, or edit, and an outside distributor only needs to view. An expiry date makes access end automatically, so a link sent for one week does not stay open for two years. Share the single file rather than the whole folder, because a folder link also opens every file added to that folder later. And every few months, look at what is shared outside the company and switch off what is no longer needed.
Now make Sameer's sharing decisions yourself. Each wrong first choice becomes an incident on Neha's desk.