Securing cloud data: encryption, MFA, access control and recovery
A practical checklist for users and small teams: encryption, two-step verification, access control, sharing and recovery.
Secure cloud data in four layers: encryption with clear key management, two-step verification on your account, limited and monitored access, and a recovery plan with a backup and recovery key. Also check what the provider documents itself.
Who is it for: Users and small teams who want to protect their files in the cloud better with a clear checklist.
Where do you start?
Many problems with cloud data are not caused by the provider’s technology, but by weak passwords, folders shared more widely than necessary or the lack of a recovery plan. So start with the things you control yourself, and then look at what the provider does.
First make an overview: which files are stored there, who has access and which are sensitive? That helps with every choice below.
Encryption and key management
Check whether encryption is enabled in transit and on the server, and above all who manages the key. With keys held by the provider, the protection is limited to, for example, theft of hardware. For sensitive files you can choose end-to-end encryption or encrypt them yourself before you upload.
Metadata such as file names and sharing details are often not encrypted. Keep that in mind when naming files.
Account, access and sharing
Use a unique, long password and a password manager. Turn on two-step verification (MFA). Where possible, choose an authenticator app or security key over SMS, because those are less susceptible to misuse of your phone number.
Give people access only to what they need, and remove it again when a project or collaboration ends. For small teams it helps to use roles and to use an administrator account only for administration. When sharing via links, use a password or expiry date and regularly check which links are still active.
Pay attention to the devices you are logged in on. Revoke access for devices you no longer use or have lost.
- Unique passwords in a password manager
- Two-step verification on for every account
- Minimal permissions per person and per folder
- Share links with a password or end date, and periodic checks
- Overview and revocation of linked devices and apps
Recovery and evidence
Synchronisation is not a backup: a deleted or encrypted file is often updated everywhere straight away. Make a separate copy, preferably in another location or with another service, and test whether restoring works. Store recovery keys offline.
Ask a provider for evidence that explains how security is set up: the security documentation, a recent audit report and the data processing agreement. A claim without a source counts as unconfirmed.
- Check the encryption and the key holder.
- Turn on MFA and store recovery codes offline.
- Limit permissions and check shared links.
- Make a separate backup and test restoring it.
- Plan a periodic check of access and devices.
Checklist per layer
| Layer | What do you set up | Why |
|---|---|---|
| Encryption | Check key management, encrypt sensitive data additionally | Determines who can read the content |
| Account | Unique password, MFA, recovery codes offline | Prevents account takeover |
| Access | Minimal permissions, restrict share links, check devices | Limits damage from mistakes or misuse |
| Recovery | Separate backup, recovery key, restore test | Protects against loss, deletion and ransomware |
Who is this less suitable for?
- Larger organisations with fixed compliance requirements: they need additional policy, logging and often a security specialist.
- People who think a service with strong encryption alone is enough: account security and recovery are equally important.
- People who want to tick off the checklist once: access and devices change, so plan a periodic check.
Frequently asked questions
Is SMS verification enough?
It is better than nothing, but an authenticator app or security key is generally safer because a phone number is easier to abuse.
How often should I change my password?
You do not need to replace a long, unique password periodically. Do change it straight away if you suspect it has leaked.
What do I do if my phone is stolen?
Revoke the session and linked devices from another device, change your password and use your recovery codes to set up MFA again.
Should a small team appoint an administrator?
Yes, it helps to have a clearly responsible person for access, employees leaving and checking settings.
