In an era where cyber threats keep escalating, protecting your sensitive files matters more than ever. Whether you’re storing personal documents, business data or client-confidential matter files, keeping them secure at rest and in transit is essential to prevent breaches and unauthorised access.
This guide covers the practical steps that actually move the needle. Encryption, access controls, secure transfer tools, and the everyday habits that turn good intentions into real protection.
Key takeaways
- Strong passwords plus MFA on every account that holds files. Non-negotiable.
- Encrypt at rest (BitLocker, FileVault) and in transit (TLS, end-to-end encrypted transfer).
- Reputable cloud storage (OneDrive, SharePoint) is more secure than local drives for most SMBs.
- Regular backups, immutable where possible, are the single best defence against ransomware.
- Audit access regularly. Most leaks are from over-shared documents, not breached defences.

1. Strong passwords and MFA
Passwords are the first line of defence. They’re also the easiest to get wrong.
What good looks like
- Use a password manager (1Password, Bitwarden, LastPass) to generate and store unique passwords for every account.
- Passwords should be at least 12 characters, mixing letters, numbers and symbols. Pass-phrases like correct-horse-battery-staple are easier to remember and harder to brute-force.
- Never reuse passwords. The single biggest cause of corporate breaches is credential reuse from leaked databases.
- Enable multi-factor authentication on every account that supports it.
2. Encrypt your files
Encryption converts data into an unreadable format unless accessed with the correct key. Both at rest (when stored) and in transit (when moving across the network).
What good looks like
- Disk encryption on every laptop and desktop. BitLocker on Windows, FileVault on Mac. If a device is lost or stolen, the data on it is unreadable.
- End-to-end encryption on file transfer tools. Standard email is not end-to-end encrypted. Use Microsoft Purview Information Protection (sensitivity labels), or a secure file-share platform for client-confidential content.
- TLS / HTTPS on every web connection where files move (most modern services do this by default).
3. Choose secure cloud storage
Cloud storage, done right, is more secure than local drives. Major providers invest tens of millions in physical security, redundancy and threat monitoring that no SMB can match in-house.
What good looks like
- Use enterprise-grade providers (Microsoft 365, Google Workspace, Dropbox Business). Avoid mixed personal and consumer-grade services for business data.
- Configure sharing controls properly. By default, Microsoft 365 lets anyone share with anyone; tighten this. Restrict external sharing, require sign-in on shared links, set expiry dates.
- Use sensitivity labels on confidential content. They enforce protection automatically.
- Monitor sharing reports. Microsoft Purview shows who’s shared what externally; review monthly.
4. Set up regular backups
Backups are the difference between a ransomware incident being a bad afternoon and an existential crisis.
What good looks like
- Automated backups, ideally daily or more frequent for active data.
- The 3-2-1 rule: three copies of data, on two different media, with one off-site.
- Immutable backups for the off-site copy, the attacker shouldn’t be able to delete the backup even with admin credentials.
- Test restores regularly. A backup you’ve never restored from is a hope, not a backup.
- For Microsoft 365: do not assume Microsoft backs up your tenant in the way you’d want. Use a third-party backup tool (Datto, Veeam, Barracuda).
5. Use secure file-sharing tools
Email attachments are not secure. They sit in inboxes for years, get forwarded to the wrong people, and often aren’t encrypted in transit.
What good looks like
- Microsoft 365 sharing links with appropriate restrictions (sign-in required, expiry date, read-only) for most business sharing.
- SecureDrop, OnionShare or similar for genuinely confidential one-off transfers.
- SFTP/SSH for system-to-system file transfers.
- Avoid free WeTransfer for business-confidential content. If you must use it, encrypt the file first with a password, then share the password through a separate channel.
6. Audit and review access regularly
Most “data breaches” aren’t sophisticated attacks. They’re over-shared documents discovered months later. Files accessible to “everyone in the company” that shouldn’t be. Old contractors who never had access removed. Public links that were forgotten.
What good looks like
- Quarterly access reviews on shared SharePoint sites and OneDrive folders.
- Automated leaver process: when someone leaves, all access is removed within an hour.
- External team member reviews: who has guest access to your tenant? Why? Still needed?
- Sensitivity-label coverage: are your most confidential documents actually labelled, or floating around unmarked?
Frequently asked questions
Is OneDrive secure enough for client-confidential files?
For most professional services firms, yes, when configured properly. Microsoft 365 Business Premium with sensitivity labels, DLP, Conditional Access and immutable backups gives a stronger security posture than any reasonable local solution. The configuration is the key.
Should I encrypt files myself before uploading to cloud storage?
For ordinary business documents, no. The cloud provider’s encryption is sufficient and configuring team member-side encryption typically reduces usability. For genuinely highly-sensitive content (legal privilege, M&A, employee discipline files), additional encryption via Purview sensitivity labels is worth considering.
How does this fit with UK GDPR?
UK GDPR requires “appropriate technical and organisational measures” to protect personal data. The controls in this guide map almost directly to ICO expectations. Demonstrating you have them in place dramatically reduces both breach risk and regulatory exposure if something does happen.
Initial IT configures secure file storage as part of every managed-IT setup. Microsoft 365, sensitivity labels, immutable backups, sharing controls. The lot, done properly.
