Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is the Shared Responsibility Model?

The shared responsibility model divides cloud security between provider and customer. The dividing line moves with the service type, and almost every cloud breach sits on the customer’s side of it.

Illustration for the cybersecurity term Shared Responsibility Model
Home / Blog / Cybersecurity Terms / What Is the Shared Responsibility Model?
17 November 2026

What Is the Shared Responsibility Model?

What Is the Shared Responsibility Model?

The shared responsibility model is the agreement, set out by every major cloud provider, about which party secures which part of a cloud service. Amazon phrases it as security of the cloud versus security in the cloud: the provider protects the physical sites, the hardware, the hypervisor, and the managed service software, while the customer protects their data, identities, configurations, and applications. Microsoft and Google publish equivalent charts. The model is not a legal nicety — it is the reason most cloud incidents are the customer’s to prevent and the customer’s to report.

The Line Moves With the Service

ResponsibilityOn-premisesIaaSPaaSSaaS
Physical and network fabricYouProviderProviderProvider
Hypervisor and hostYouProviderProviderProvider
Guest operating system and patchingYouYouProviderProvider
Application code and dependenciesYouYouYouProvider
Service configurationYouYouYouYou
Identities and permissionsYouYouYouYou
Data and its classificationYouYouYouYou

Read the bottom three rows carefully, because they never change. Whatever the service model, you own your data, who can reach it, and how the service is configured. Google describes a variant it calls shared fate, in which the provider supplies opinionated secure defaults, blueprints, and guardrails rather than simply drawing a line — a useful corrective to a diagram that can read as a disclaimer.

Where the Assumptions Break

Incidents cluster around a small number of beliefs that the model quietly contradicts.

The 2019 Capital One breach is the canonical illustration of the whole model. A misconfigured web application firewall, an over-permissive role, and data accessible to that role produced a breach affecting more than 100 million people — every link in the chain on the customer side of the line.

Using the Model as a Working Tool

Treat the provider’s diagram as a template, then produce your own version per service you consume, naming the internal team that owns each row. The exercise is more valuable than it sounds: it routinely surfaces responsibilities that everyone assumed belonged to somebody else, particularly logging, backup, key management, and vulnerability management for managed services.

Extend it to your suppliers. If a managed service provider administers your tenant, the division between you, them, and the cloud provider should be written into the contract rather than inferred. The same applies in reverse where you are the provider: your customers need to know which parts of tenant isolation and configuration are theirs to manage.

The Regulatory Position in the UK

Data protection law does not recognise the shared responsibility model, and that is the point worth understanding. Under UK GDPR, you are generally the controller and the cloud provider is a processor acting on your instructions. Accountability for the security of processing stays with the controller, as does the duty to notify the ICO within 72 hours where a breach is likely to result in risk to individuals. “The configuration was the default” has never been accepted as mitigation.

The NCSC Cloud Security Principles are structured around the same division, asking what the provider asserts and what you must implement. For financial entities, DORA and the UK critical third parties regime push further still, requiring firms to map dependencies and keep accountability even where a designated provider is supervised directly.

If you want an independent view of which side of the line your current gaps fall on, our cloud security services assess configuration, identity, and exposure across AWS, Azure, and Google Cloud.

FAQ – Frequently Asked Questions

Does the Model Change Between AWS, Azure, and Google Cloud?

The principle is identical and the diagrams differ only in presentation and terminology. What genuinely varies is the detail within equivalent services: default encryption behaviour, how permission inheritance works, what logging is enabled without being asked, and which hardening the provider applies to managed components. Read each provider’s documentation for the specific services you use rather than relying on a general chart.

Who Is Responsible for Backing Up SaaS Data?

You are. Providers such as Microsoft and Google offer retention policies, versioning, legal hold, and recycle bins, which serve compliance and accidental deletion rather than recovery from a destructive incident. Their terms are explicit that customer data remains the customer’s responsibility. If your recovery requirement is restoring a defined state at a defined time, you need a third-party backup with its own retention.

If the Provider Has an Outage, Is That Our Problem?

To your customers and your regulator, yes. The provider owes you whatever its service level agreement promises, which is typically a service credit rather than compensation for your losses. Accountability for the availability of your service remains with you, which is why resilience planning, multi-region design, and tested recovery sit firmly on the customer side of the model.

Does Using a Managed Service Provider Change Anything?

It adds a third party to the division without removing your accountability. Write down precisely which controls the provider operates, which remain yours, and how evidence is supplied, then put that in the contract rather than leaving it to assumption. Gaps between a cloud provider’s responsibilities and a managed service provider’s scope are a common and well-exploited source of unmonitored systems.

Related Terms

You May Be Interested In These

What Is Software-Defined Radio?

Cybersecurity Terms

17 November 2026

What Is Software-Defined Radio?

Read More
What Is Alert Triage?

Cybersecurity Terms

17 November 2026

What Is Alert Triage?

Read More
What Is eIDAS?

Cybersecurity Terms

17 November 2026

What Is eIDAS?

Read More