Shared responsibility by model
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
apply the shared-responsibility model to security and operations for each model.
Planned topics
- The provider secures the cloud itself (facilities, hardware, hypervisor); the customer secures what they put in it.
- The line moves up the stack with each model, but data, identity, and configuration always stay with the customer.
- Most cloud incidents come from customer-side misconfiguration, not provider failure.
- Operations are shared too: backups, monitoring, incident response, and scaling each need a named owner.
- Write the split down; unwritten responsibilities become gaps.
Draft outline details
Demonstration
a responsibility table with rows (patching, identity, data encryption, backups, monitoring, incident response) and columns (IaaS, PaaS, SaaS) filled with Provider / Customer / Shared.
Check your understanding
In a SaaS CRM, who is responsible for who can export customer data?
Show answer
The customer; access configuration is always theirs.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.