Cloud storage can be secure. Major providers encrypt data in transit and at rest, replicate it across facilities and run mature security programs. Security still depends on how the service is set up: who can access the data, how it is shared, how accounts are protected and whether backups exist. Many publicly reported cloud data exposures trace back to configuration mistakes, stolen credentials or excessive permissions, rather than a flaw in the storage platform itself.
What the provider secures and what you secure
Cloud security follows a shared responsibility model. The provider and the customer each own part of the job.
- The provider secures the data centers, hardware, the underlying platform and the service’s own software. It also operates the encryption infrastructure, and many services ship with secure defaults.
- You decide who has access, how accounts are protected, which data is shared or made public, which encryption keys are used, how backups are kept and whether your setup meets your own rules.
Most of the controls that matter day to day sit on the customer side of that line.
Encryption: in transit, at rest and who holds the keys
Encryption protects data in two places:
- In transit: data travels over TLS, typically TLS 1.2 or higher.
- At rest: data on the provider’s storage is encrypted, commonly with AES-256. Amazon S3, for example, encrypts new objects by default with S3-managed keys, a default in place since January 2023.
The bigger question is who controls the keys. Your choice of key option decides who can read the data:
| Key option | Who manages the keys | Trade-off |
|---|---|---|
| Provider-managed | The provider holds and rotates them | Simplest to use; the provider can access the data as the service requires |
| Customer-managed keys (AWS KMS, Azure Key Vault, Cloud KMS) | You, within the provider’s key service | More control and audit logging; you manage key policies |
| Customer-supplied keys (SSE-C, CSEK) | You, sent with each request | You must protect the keys; a lost key means lost data |
| Client-side (end-to-end) | You, before upload | The provider cannot read the data; you handle recovery and sharing yourself |
Standard consumer services such as Google Drive, Dropbox and OneDrive hold their own keys. End-to-end encrypted options exist, such as Proton Drive and Tresorit, but they often limit features like web previews, search and collaboration. Some providers also offer end-to-end encryption for certain data types, with availability that varies by country.
Access control and sharing
- Least privilege. Give each user, group and application only the access it needs, and review it regularly.
- Multi-factor authentication (MFA). Turn it on for every account, and especially for administrators. An authenticator app or hardware key is stronger than SMS codes.
- Sharing links. Remove “anyone with the link” links and stale collaborators you no longer need.
- Time-limited access. For one-off sharing, use links that expire. For example, an S3 presigned URL can last up to 7 days with Signature Version 4.
- Audit logs. Turn on logging so you can see who accessed what. Examples include AWS CloudTrail, Azure Monitor and Google Cloud Audit Logs.
Common risks
- Stolen or reused passwords. Credentials taken from other breaches are a common way into accounts. A password manager and MFA reduce this risk.
- Misconfigured storage. A bucket or share set to public, or a link shared too widely, can expose sensitive files. Block public access by default, and check exceptions.
- Over-permissive roles. An application role with broad access can be abused if the application is compromised.
- Accidental deletion and ransomware. Versioning and immutable backups protect against both.
- Synced mistakes. Sync services copy deletions and encrypted files to every device.
- Provider access and legal requests. If the provider holds the keys, it can access the data, and it may receive legal requests. The location of a data center does not by itself decide which laws apply. For example, the US CLOUD Act can apply to US providers wherever the data is stored.
- Outages and shutdowns. Services can fail or close. Keep an independent copy of critical data.
Notable incidents
Two well-known incidents show where the risk usually sits:
- Capital One, 2019. An attacker used a server-side request forgery flaw, made possible by a misconfigured firewall, to reach credentials for an over-permissive role. The attacker then accessed data about roughly 100 million people in the United States and 6 million in Canada.
- Snowflake customers, 2024. Attackers used login credentials stolen from other sources to access customer accounts on the data platform. Many of the affected accounts did not use multi-factor authentication.
In both cases, the weakness was in configuration or account security, not in the core storage platform.
Ransomware and deletion
Deleting a file may not remove every copy. Versions, backups and trash copies can remain for a period, depending on the service. For ransomware defense, combine two controls:
- Versioning, so earlier versions of files survive an attack.
- Immutable retention, such as S3 Object Lock or Google Cloud retention policies, so backup copies cannot be changed or deleted during the retention period.
For how to structure those copies, see what is cloud backup and how does it work?
Compliance and data location
Providers publish independent attestations, such as SOC 2, ISO/IEC 27001, FedRAMP and PCI DSS. These show that the provider’s controls were audited. They do not make your own configuration compliant.
For regulated health data in the United States, HIPAA requires a business associate agreement (BAA) with the provider. You still configure the service to meet HIPAA’s requirements. For data residency, choose regions that meet the rules that apply to you, and check the provider’s terms.
This section is a summary, not legal or compliance advice. Check your obligations with your own advisers.
A practical checklist
For personal use:
- Turn on two-factor authentication, preferably with an authenticator app.
- Use a unique, strong password for each account, stored in a password manager.
- Review shared links and remove the ones you no longer need.
- Keep your devices and apps updated.
- Keep a second copy of irreplaceable files outside the cloud.
- Encrypt highly sensitive files before you upload them.
For a business:
- Enforce MFA for all users, with extra protection for administrators.
- Apply least privilege to users, roles and service accounts.
- Block public access by default, and audit every exception.
- Use customer-managed keys where your policies require them, and keep key policies tight.
- Turn on versioning and immutable backups for critical data.
- Enable audit logs and alert on unusual access.
- Test offboarding and file recovery before you need them.
For the storage side of these choices, see object storage in cloud computing and Amazon S3 explained, which covers the default encryption and public-access settings. For Google’s approach, read Google Cloud Storage explained.