Request a quote
Emergency SectorsCareers About us Blog Get in touch
Close-up of two monitors showing log lines and coloured terminal output

Cloud security best practices: what the provider does, and what you must do

Cloud security is a shared responsibility, and that is not a courtesy phrase. The provider secures its data centres, its hardware and its platform. Who signs in, which settings are open, which apps have access and whether anyone reads the logs is down to you. These cloud security best practices are about that second half, and about what you can expect from whom in an incident.

7 min read Written by the ITproposal team
Short answer

The provider secures the cloud itself; you secure what you put in it and how you configure it. Identities, settings, data and devices stay yours in every model.

The provider’s certificate or audit report covers its side. A SOC 2 report even lists the controls the customer is expected to have; read that list.

Most incidents start on the customer’s side: a compromised account, an open setting, an app with too many permissions or a log nobody reads.

The shared responsibility model, briefly

Every major cloud provider describes its security with the same model: it is responsible for security of the cloud, the customer for security in the cloud. How far its part reaches differs per service. On a virtual server you patch the operating system yourself; in Microsoft 365 the provider does that and you only manage the configuration.

Four things never move in any model: who has access, how the service is configured, what data is in it and which devices are used to sign in. That is where the work of cloud security lies for an organisation, and that is what the rest of this article covers. The UK’s NCSC publishes cloud security principles that are a useful way to question a provider about its half.

What the provider’s certificate does and does not prove

Providers like to show their ISO/IEC 27001 certificate or SOC 2 report. That is valuable, but it is about their side of the line. Three things to read before you rely on it in your own risk assessment:

  • The scope. Which services, locations and processes it covers. A certificate for the data centre says nothing about the application you buy on top of it.
  • The period and the exceptions. A SOC 2 report covers a period and records the auditor’s findings. A report two years old, or a list of findings without follow-up, is a question for the provider.
  • The controls expected of you. A SOC 2 report lists the complementary controls the customer must have in place, such as managing users and protecting its own credentials. That is literally your half of the model, written down by the provider’s auditor.

Cloud security best practices start with the settings

A cloud service supplies the switches; you choose their position. The default is designed to make the service usable quickly, not to make it as secure as possible. Many leaks therefore happen without an attack: something was open that should have been closed.

  • External sharing. Links anyone with the link can open, guest access with no expiry, storage that is publicly readable.
  • Legacy sign-in methods. Protocols that do not support multi-factor authentication are sometimes still enabled in older tenants, and then bypass everything else you have set up.
  • Automatic email forwarding to addresses outside the organisation. An attacker who takes over a mailbox turns that on first.

So record a baseline: which position each setting should have and why. Then check periodically whether the environment still meets it, because settings drift: an admin who opens something “just for now”, a new provider feature that is on by default. The security scores providers show are a useful first list, not a verdict.

Admin rights: few, separate and temporary

In the cloud, an admin account is the key to everything: every mailbox, every file, every setting, from anywhere with an internet connection. Treat those accounts differently from ordinary ones.

  • Separate. An administrator works with a normal account and uses the admin account only for administration, with no mailbox and no day-to-day use.
  • Strong authentication. Phishing-resistant multi-factor authentication, such as a hardware key or a passkey, and not just a code by text message.
  • Few and temporary. As few standing administrators as possible, and roles that are only activated when needed. A supplier who does something once a year does not need admin rights all year.
  • A break-glass account. One or two accounts for when everything else fails, stored safely, monitored on every use and tested periodically.

This is the start of a wider approach in which every sign-in is verified; how to introduce that step by step is in Zero Trust in practice.

The least known part of cloud security is the apps your users grant access to themselves. A calendar app, a signature tool or an AI assistant asks for access to email or files when you sign in, and with one click on “accept” a third party has that access, even if the password is changed afterwards.

  • Limit who may grant consent. Let users approve only apps with limited permissions, and route the rest through an administrator.
  • Inventory what is already there. Which apps have access now, with which permissions, and who still uses them. A first review almost always turns up something nobody recognises.
  • Integrations between systems often use a key or secret that never expires. Give them an owner, an expiry date and only the permissions they need.
  • Previous suppliers. A support partner who has left may still have an account or an integration. Remove it on the day of the handover.

Logs: switched on, retained and someone watching

Cloud platforms record a great deal: sign-ins, changes to settings, who shared which file. But not everything is on by default, retention often depends on the subscription, and a log nobody reads only helps after the event.

  • Check what is recorded and for how long. An attack is sometimes discovered weeks later; you then want to be able to look back to the start.
  • Keep a copy outside the service if the default retention is too short, somewhere that cannot be deleted with the same admin accounts.
  • Set alerts on what actually matters: a sign-in from an unexpected country, a new administrator, a rule that forwards email, large volumes of downloaded files.
  • Agree who watches, evenings and weekends included. If you cannot organise that yourself, it can sit with managed security and monitoring.

In an incident: what the provider does and what you do

The line holds during an incident too. The provider investigates and fixes problems in its own platform and informs you under its terms. A compromised account inside your environment is not something it investigates for you; that is your incident, with your logs.

  • Data recovery. The provider keeps the service available; getting back data that a user, an attacker or a mistake deleted is usually your job. Your own backup of cloud data is therefore not a luxury.
  • Encryption. The major providers encrypt data at rest by default. If you want to manage the keys yourself, many services allow it, but you then also take on the risk of losing a key.
  • Reporting. Under UK GDPR or the GDPR you, as the controller, are the one who reports a personal data breach to the ICO or your supervisory authority within 72 hours where that is required. The provider is a processor and should inform you; the decision and the report are yours.

So write down in advance who does what in an incident, including the contact route to the provider and who on your side decides about reporting.

Where our work stops

What we do. We set up your half and keep it in order: a baseline and the checks against it, admin accounts and roles, multi-factor authentication, restrictions on app consent, logging and alerts, backup of cloud data and monitoring through our managed security service. In an incident inside your environment we investigate and recover with you.

What we do not do. We are not a cloud provider and have no influence over the security of the platform, the data centres or the availability of Microsoft or any other provider. We are not an auditor: we do not issue certificates or SOC 2 reports and we certify nobody. And whether an incident has to be reported is a legal judgement you make, with your data protection officer or a lawyer; we supply the facts from the logs.

Frequently asked

Questions we get about this

The five that come up most often.

What is the shared responsibility model in cloud security?

The cloud provider is responsible for the security of the cloud itself: data centres, hardware, network and the platform. The customer is responsible for what it puts in and how it configures it. How far the provider’s part reaches differs per service, but access, settings, data and devices always stay with the customer.

What are the most important cloud security best practices?

Multi-factor authentication on every account, few and separate admin accounts, a documented baseline that is checked periodically, limits on which apps may be granted access, logs retained for long enough and someone who reads the alerts. On top of that, your own backup of the data.

Is the cloud more secure than our own server?

A major provider’s platform is usually better protected than a server in an office. But most incidents start on the customer’s side: a compromised account, a setting left open or an app with too many permissions. The cloud is as secure as the half you manage yourself.

Does Microsoft back up our Microsoft 365 data?

Microsoft keeps the service available and protects its platform against outages. Data deleted by a user, an attacker or a mistake can only be recovered for a limited time with the standard features. Your own backup in another location is therefore sensible.

Can you certify our cloud platform?

No. We are not an auditor and do not issue certificates or SOC 2 reports. We set up the security that is your responsibility and can show how it is configured; the assessment for a certificate is done by an accredited body.

Related services

Further reading

What your half of cloud security connects to.

Shall we check your half?

We look at the settings, admin accounts, app consents and logs of your cloud environment, and tell you what is open and in which order to close it.

Practical IT knowledge in your inbox

New guides on management, security and the workplace, written by the people doing the work. No sales talk, and you can unsubscribe in one click.

We use your address for the newsletter only. See our privacy policy.

Request a quote Call