Shared-responsibility model

As explained in Effective Platform Engineering

A shared responsibility model divides security responsibilities between a platform provider and the users of the platform.

A shared-responsibility model divides security and operational responsibilities between a platform team and the developers who use the platform. The platform team protects the platform and supplies enabling capabilities; developers remain responsible for application security and service-specific operation. section 1.3.3 section 5.2.3

A practical boundary assigns responsibilities by layer:

• Platform teams manage platform security, resiliency, collection infrastructure, data storage, and hosted observability tooling. section 1.3.3 section 5.2.3
• Development teams secure application code and configure dashboards, alerts, and trace publishing for their services. section 1.3.3 section 5.2.3
• The platform can assess code and expose vulnerability capabilities, but it cannot automatically remove vulnerabilities created by developers. section 1.3.3

Epetech observability

Epetech assigns application teams responsibility for service dashboards, meaningful alert thresholds, and trace publication, while the platform team maintains scraping, ingestion, storage, and dashboard hosting. Clear boundaries reduce friction and make monitoring more actionable. section 5.2.3 section 5.5

Figure 5.6 A shared responsibility model is critical to reducing friction when teams adopt any platform service.

Use the responsibility-model figure to navigate the boundaries that reduce friction when teams adopt a platform service. section 5.2.3

How Effective Platform Engineering covers it

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.

How it connects

Connects platform engineering with application security, observability, governance, resiliency, and DevOps.

liveBookmanning.com

Read Effective Platform Engineering on liveBook Get the book at manning.com

Also explained in

• 

  liveBookmanning.com
  Data-Driven CybersecurityShared responsibility is an operating pattern in which a cloud provider secures the underlying infrastructure while the customer secures its data and workloads.
• 

  liveBookmanning.com
  Microsoft Azure in ActionThe 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.
• 

  liveBookmanning.com
  MongoDB 8.0 in Action, Third EditionA shared responsibility model is a security arrangement that divides operational and security obligations among a service provider, infrastructure providers, and customers.
• 

  liveBookmanning.com
  Azure SecurityShared responsibility is a division of accountability among multiple parties for managing and resolving a security outcome.
• 

  liveBookmanning.com
  Google Anthos in ActionA shared responsibility model is an operating model in which responsibility for infrastructure, platforms, applications, and data is divided among participating parties.

Compare how 6 books explain shared-responsibility model →

Related concepts

• Amazon Relational Database Service (RDS)used by · Amazon Relational Database Service is an AWS-managed service for deploying, operating, and scaling relational databases.
• cloud providercontrasts with · A cloud provider is an organization that delivers computing resources, platforms, or managed services over a network, typically on demand.
• 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.
• 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.
• cloud computingconfigures · Cloud computing is the on-demand delivery of computing resources and services over a network from remotely managed infrastructure.

This explainer was generated by Manning's knowledge graph from the text of Effective Platform Engineering. The section links point to the parts of the book it draws on.