A useful way to think about it
Why the assumption is common
Cloud services are operated by specialist providers, often with significant investment in their underlying platforms. That can reasonably give customers confidence in the resilience and security of the provider's infrastructure.
However, cloud security is shared. A provider may manage the underlying service while your organisation controls user accounts, permissions, information, connected devices and many configuration choices. The split differs between products, so it is important to check the service and contract rather than rely on a general assumption.
Identity and access still matter
Cloud services are reached through identities. If an account has excessive permissions, is shared between people or remains active after someone leaves, a secure platform can still be used in ways the organisation did not intend.
Use named accounts, appropriate authentication, role-based access and regular access reviews. Consider administrator accounts separately from everyday accounts, and make sure there is a known process for changing access when people join, change roles or leave.
Authentication
Confirm which sign-in protections are enabled and whether additional verification is required for important accounts.
Permissions
Give users and suppliers access they need for their role; review privileged accounts and remove access that is no longer needed.
Configuration
Understand important security and sharing settings, who can change them and how unintended changes are noticed.
People and process
Help users recognise unusual requests and provide a clear, supportive route for reporting concerns.
Monitoring and responsibility need an owner
Security features are most useful when someone knows which alerts matter and what to do about them. Decide who reviews relevant activity, how urgent concerns reach the right person, and how responsibilities are divided between your staff, IT provider and cloud supplier.
If your organisation works with an external IT provider, clarify the scope of its monitoring and response. For teams with internal IT, co-managed support can help define where specialist monitoring or additional capacity fits.
Security is not the same as backup or recovery
A cloud service may keep a service available and may include retention or recovery features. Those capabilities are not automatically the same as an independent backup that meets your retention and restore requirements. Accidental deletion, malicious changes, account access and service availability are related but different questions.
Check what data is covered, how long it is retained, who can restore it and whether the recovery method is separate enough for your needs. Our guide to cloud backup and restore questions can help you review that part of the picture.
Then consider what happens if a critical service is unavailable, not just how a file is restored. A business continuity plan connects technical recovery with people, decisions and communications.
A short cloud security review
- List the cloud services that hold important information or support essential work.
- For each service, record who owns the account, configuration, access and supplier relationship.
- Review administrator access, sign-in protections, sharing settings and user lifecycle processes.
- Ask how relevant alerts are monitored and who responds outside normal working arrangements.
- Confirm retention, backup, restore testing and recovery responsibilities.
- Revisit the review when services, suppliers or business requirements change.
