Shared Responsibility in SaaS
What you'll learn: How the shared responsibility model shifts most infrastructure burden to the provider in SaaS, while customers retain critical duties around data and access.
The SaaS Security Profile
In Software as a Service, the provider manages nearly everything: the application code, runtime environment, operating system, network, and physical infrastructure. This is the most hands-off model from a customer infrastructure perspective.
However, you still own what matters most: your data and who can access it.
What the Provider Secures
The SaaS vendor handles:
- Application security patches and updates
- Infrastructure hardening and maintenance
- Network security and DDoS protection
- Physical datacenter security
- Platform availability and resilience
Think of it like renting a fully furnished, managed apartment with 24/7 security — the building owner handles everything structural.
What YOU Must Secure
Despite minimal infrastructure responsibility, customers retain critical duties:
Data classification and handling: You determine what data goes into the SaaS application and whether it's appropriate for that service's security level. Uploading highly sensitive data to a consumer-grade SaaS tool is your risk.
Access control and identity management: You configure who can access the application, what permissions they have, and how they authenticate. Weak passwords or overly permissive sharing settings are customer failures.
Usage policies and compliance: You must ensure the SaaS application is used according to your organization's policies and regulatory requirements.
Data backup and retention (where applicable): Some SaaS providers offer limited recovery windows. Understanding and supplementing these capabilities is your responsibility.
The Bottom Line
You trade infrastructure control for convenience in SaaS, but you never outsource accountability for your data's security and appropriate access.
Key Takeaway: In SaaS, providers secure nearly all infrastructure, but customers remain solely responsible for data classification, access control policies, and ensuring appropriate use of the service.