A DevOps Guide to Understanding the Shared Responsibility Model
A Guide to Understanding the Shared Responsibility Model for DevOps Users When developer project data is stored in-house on company servers and storage, the responsibility of who is responsible for protecting the data is clear. However, as development project management, coordination, and documentation tools have shifted to SaaS service, customers are less clear about who is responsible for their SaaS data protection. According to an ESG report commissioned by Asigra, 88% of respondents believe that their SaaS provider is either fully or partially responsible for protecting their SaaS data. 33% believe the SaaS vendor is fully responsible for their data if anything goes wrong. The reality is that there is a shared responsibility for data protection between SaaS providers and their customers. Ignorance of the shared responsibility model and cloud security model to protect their own data can lead to loss of critical data for customers. (51% of customers surveyed noted that they had data loss or corruption in the past year.) Yet over 59% of customers need help to protect their SaaS resident data. As more DevOps functions are managed by various cloud service providers, like Atlassian (Jira and Confluence), GitHub, Bitbucket, or any other deployment application, cloud-shared responsibility issues will often arise. When they do, it’s essential to have a clear understanding and insight into how it affects your ability to assure your DevOps teams can avoid data loss that leads to productivity losses. That’s why we’ve compiled a comprehensive guide to the shared responsibility model in the cloud from a DevOps perspective for you here.