Written by: Mio Kanzaki(Security Analyst (AI))Reviewed by: 千葉圭介Updated
The shared responsibility model is the idea that a cloud provider and a user divide the range of protection between them. CISA's material describes it as an idea that shows who holds which responsibility for technology, security, data, and so on. Using the cloud does not move all of the work of protection to the provider.
How does the shared responsibility model work?
The management of a condominium shows where the line falls. The management company protects the entrance and the shared corridors. But locking the door of each unit is the resident's job. In the cloud too, the part that corresponds to the building is held by the provider, and the settings and data inside the room are held by the user.
The division changes with the type of service. NIST's SP 800-144 says the responsibilities of the provider and the organization differ by the type of service. CISA's material explains that with SaaS the provider bears much of the responsibility for security and the user trusts the provider more. With IaaS, much of the responsibility falls on the user.
In addition, the definition of the line can differ by provider. CISA's material says the user must grasp clearly the line between their own responsibility and the provider's. It also recommends settling expectations and responsibilities in the service level agreement (SLA) of the contract.
NIST's SP 800-144 also touches on where final responsibility lies. Even if cost and efficiency are the motive for moving, giving up responsibility for security must not be the motive, and the organization bears final responsibility for the safety and privacy of the entrusted service, it says. CISA's material is aimed at US government agencies, but the thinking applies to private operators too.
Whether your settings are in order as divided is covered in the cloud assessment page. The free URL check shows only the outside view, so it cannot show how responsibility is divided in your setup.
Why does the shared responsibility model matter?
If you assume that it is the cloud, so security has been left to the provider, the settings on the user's side are seen by no one. The public range and permission settings are, in many cases, decided by the user. The mistakes that occur there are cloud misconfiguration.
When you contract, it helps to write down which parts the provider protects and which parts you protect. Your own part includes the permissions of those who can enter the admin screen, the public range of data, and checking logs. How to hold permissions is covered in IAM, and the mechanism for checking settings in CSPM. Even if the person in charge changes, a kept list of the division makes handover less likely to be missed. To work out the division together, contact us.
Related terms
- Cloud misconfiguration: a state in which wrong public-range or permission settings become a hole
- IAM: the mechanism that decides who may do what in the cloud
- CSPM: a mechanism that finds cloud misconfigurations automatically
- Public cloud storage: a state in which data in cloud storage can be seen by anyone
Frequently asked questions
If I use the cloud, does the provider take the responsibility for security?
No. NIST's SP 800-144 says that by moving to the cloud, an organization must not give up its responsibility for security. Final responsibility for the safety of work entrusted to the provider also remains with the organization.
Where do I check where the dividing line is?
Check in the description of the service you contract and in the contract (SLA). CISA's material says that because the definition of the division can differ by provider, you should grasp the line clearly and settle expectations and responsibilities in the contract.
Next step
For a cloud you contract, try writing the provider's part and your own part on one sheet. Checking your own part is covered in cloud assessment. The free URL check shows only what is visible from outside, and for sorting out the division, contact us.
Frequently asked questions
If I use the cloud, does the provider take the responsibility for security?
No. NIST's SP 800-144 says that by moving to the cloud, an organization must not give up its responsibility for security. Final responsibility for the safety of work entrusted to the provider also remains with the organization.
Where do I check where the dividing line is?
Check in the description of the service you contract and in the contract (SLA). CISA's material says that because the definition of the division can differ by provider, you should grasp the line clearly and settle expectations and responsibilities in the contract.