Shared-responsibility model
A shared-responsibility model is an arrangement in which multiple parties divide accountability for operating, securing, managing, or assuring a system or service.
Effective Platform Engineering
A shared responsibility model divides security responsibilities between a platform provider and the users of the platform.
- How it is used
- Clarifies ownership across platform security, application security, observability, and service operations.
- How deep it goes
- Defines responsibility layers and concrete duties, including security capabilities, resiliency, dashboards, alerts, collection, storage, and hosting.
- Examples
- Uses Epetech observability responsibilities and a cross-functional customer account team as operational examples.
- What you can do after
- Apply it via Grafana, Prometheus, or Datadog responsibilities that separate platform infrastructure from service-specific monitoring.
Read how Effective Platform Engineering explains shared-responsibility model →
Data-Driven Cybersecurity
Shared responsibility is an operating pattern in which a cloud provider secures the underlying infrastructure while the customer secures its data and workloads.
- How it is used
- Directs cloud threat detection toward customer-controlled data, workloads, and configurations rather than treating provider infrastructure security as complete coverage.
- How deep it goes
- Defines the provider–customer division and identifies configuration checks, but does not give a step-by-step implementation procedure.
- Examples
- Uses storage-bucket permissions, encryption policies, IAM roles, security groups, and newly deployed workloads as concrete security concerns.
- What you can do after
- Apply it via AWS Config or Azure Policy to check whether customer-controlled cloud configurations adhere to security policies.
Read how Data-Driven Cybersecurity explains shared-responsibility model →
Microsoft Azure in Action
The shared responsibility model is a cloud security framework that assigns responsibility for different aspects of operating and securing a cloud environment between the provider and the customer.
- How it is used
- Identifies where Azure security responsibility ends and customer responsibility begins across IaaS, PaaS, and SaaS.
- How deep it goes
- Explains the changing split through service and identity examples, without detailing how to harden each Azure product.
- Examples
- Contrasts a platform-managed web service with a virtual machine and identifies shared SaaS duties for users and endpoints.
- What you can do after
- Evaluate/understand which security areas your team must handle when choosing an Azure hosting option.
Read how Microsoft Azure in Action explains shared-responsibility model →
MongoDB 8.0 in Action, Third Edition
A shared responsibility model is a security arrangement that divides operational and security obligations among a service provider, infrastructure providers, and customers.
- How it is used
- Divides Atlas security and operational duties so cloud deployments assign data, platform, and infrastructure responsibilities explicitly.
- How deep it goes
- Maps responsibility layers and configuration tasks, but stops short of detailed implementation procedures or command examples.
- Examples
- Uses Atlas settings for federation, LDAP, MFA, data residency, KMS or BYOK, connectivity, auditing filters, and backups.
- What you can do after
- Operate/configure Atlas by assigning identity, data-access, network, encryption, auditing, and backup decisions to the correct party.
Read how MongoDB 8.0 in Action, Third Edition explains shared-responsibility model →
Azure Security
Shared responsibility is a division of accountability among multiple parties for managing and resolving a security outcome.
- How it is used
- Allocates Azure security accountability between Microsoft, customers, developers, and security teams.
- How deep it goes
- Defines physical, infrastructure, data, and resource duties, then relates responsibility changes to SaaS, PaaS, and IaaS.
- Examples
- Uses datacenter protection, virtual machines, missing encryption, and collaborative code-vulnerability remediation as examples.
- What you can do after
- Evaluate Azure ownership boundaries and apply layered controls with developers and security teams.
Read how Azure Security explains shared-responsibility model →
Google Anthos in Action
A shared responsibility model is an operating model in which responsibility for infrastructure, platforms, applications, and data is divided among participating parties.
- How it is used
- Coordinates application delivery across developers, operators, and security officers through shared methodologies and interfaces.
- How deep it goes
- Defines roles, configuration ownership, shared interfaces, and cluster-topology trade-offs, but stops short of detailed implementation procedures.
- Examples
- Uses personas, code repositories, image builds, Kubernetes manifests, and single-cluster versus multicluster deployments as concrete artifacts and choices.
- What you can do after
- Apply it via CI/CD and GitOps interfaces to coordinate ownership, standardize delivery, and choose deployment topology.
Read how Google Anthos in Action explains shared-responsibility model →
Related concepts
- cloud providercontrasts with · A cloud provider is an organization that delivers computing resources, platforms, or managed services over a network, typically on demand.
- Amazon Relational Database Service (RDS)used by · Amazon Relational Database Service is an AWS-managed service for deploying, operating, and scaling relational databases.
- software as a serviceuses · Software as a service is a software delivery model in which a provider hosts and operates applications that users access over a network.
- iaasuses · Infrastructure as a Service is a cloud service model that provides on-demand computing, storage, and networking resources while customers manage the operating systems and applications they run.
- platform as a serviceuses · Platform as a service (PaaS) is a cloud service model that provides a managed application development, deployment, or runtime platform while abstracting management of the underlying infrastructure.
- cloud computingconfigures · Cloud computing is the on-demand delivery of computing resources and services over a network from remotely managed infrastructure.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.