Cloud Vendor Due Diligence: Assessing Cloud Service Provider Risk
How to evaluate cloud service providers across security, compliance, data sovereignty, and operational resilience dimensions, including shared responsibility assessment.
On this page
Why Cloud Vendor Due Diligence Is Different
Cloud services have fundamentally changed the vendor risk equation. When you host applications on-premises, you control the full stack, from physical security to application configuration. When you move to the cloud, you outsource layers of that stack to a service provider, creating a shared responsibility model that's uniquely prone to gaps. The 2024 Snowflake breach, where attackers compromised 165 customer environments through stolen credentials, demonstrated that even enterprise-grade cloud platforms can become vectors when shared responsibilities aren't clearly understood and implemented.
Cloud vendor due diligence must address risks that don't exist in traditional vendor relationships: multi-tenancy isolation (is your data truly separated from other customers?), data residency (where is your data physically stored, and does that comply with applicable laws?), portability (can you actually extract your data and move to another provider?), and the CSP's own supply chain (what fourth parties does your cloud provider depend on?). These questions require cloud-specific assessment methodologies.
The scale of cloud dependency makes this critical. The average enterprise now uses 130+ SaaS applications and 3-5 IaaS/PaaS providers. Each unassessed cloud vendor is an unmanaged risk in your environment.
The Shared Responsibility Model
Understanding and documenting shared responsibility is the foundation of cloud vendor due diligence. The model varies by service type:
IaaS (Infrastructure as a Service)
Provider Manages
Physical security, network infrastructure, hypervisor, storage hardware
Customer Manages
OS patching, application security, data encryption, access management, network configuration, monitoring
PaaS (Platform as a Service)
Provider Manages
All IaaS responsibilities plus OS, runtime, middleware
Customer Manages
Application code, data, user access, API security, configuration
SaaS (Software as a Service)
Provider Manages
All PaaS responsibilities plus application logic, availability
Customer Manages
Data classification, user provisioning/deprovisioning, configuration settings, integration security, monitoring
Cloud Vendor Assessment Framework
- Security certifications review: Verify SOC 2 Type II, ISO 27001, ISO 27017/27018, CSA STAR level, and any industry-specific certifications (FedRAMP, HITRUST, C5)
- Data residency mapping: Identify all regions where data will be stored, processed, and backed up, verify compliance with GDPR, data localization laws, and organizational policies
- Shared responsibility documentation: Create an explicit matrix mapping every security control to either the CSP or your organization, identifying any gaps
- Encryption assessment: Evaluate encryption at rest and in transit, key management options (provider-managed vs. customer-managed vs. BYOK), and cryptographic standards
- Identity and access integration: Assess SSO/SAML support, MFA enforcement, API authentication, role-based access, and integration with your identity provider
- Incident response evaluation: Review the CSP's breach notification SLA, incident response procedures, forensic support capabilities, and communication protocols
- Business continuity assessment: Evaluate uptime SLA, disaster recovery capabilities, data backup and retention, and geographical redundancy options
- Exit strategy planning: Assess data portability formats, export mechanisms, API availability for migration, and contractual provisions for post-termination data access
Data Sovereignty and Residency
Data sovereignty has become one of the most complex aspects of cloud vendor assessment. Organizations must navigate an increasingly fragmented landscape of data localization laws. GDPR restricts transfers outside the EEA without adequate safeguards. China's PIPL requires data localization for certain data categories. Russia's data localization law requires personal data of Russian citizens to be stored domestically. India's DPDP Act introduces data localization for "significant data fiduciaries." Even within the US, some states are implementing data residency requirements for government data.
When assessing cloud vendors, map data flows comprehensively: Where is primary data stored? Where are backups replicated? Where does processing occur (which may differ from storage)? Do support staff in other countries access data for troubleshooting? Does the CSP use subprocessors in restricted jurisdictions? The answers determine whether a cloud vendor can legally process your data, and non-compliance penalties can be severe (GDPR fines up to 4% of global revenue).
Cloud-Specific Red Flags
- No SOC 2 Type II or equivalent independent audit report available
- Inability to specify or guarantee data residency regions
- Customer-managed encryption keys not supported (provider holds all keys)
- No published incident response SLA or breach notification timeline
- Uptime SLA below 99.9% with inadequate service credits
- No data export API or proprietary-only data formats creating lock-in
- Shared tenancy concerns with no documented isolation controls
- Shadow IT discovery reveals unauthorized cloud services with sensitive data
Frequently Asked Questions
What is cloud vendor due diligence?
Cloud vendor due diligence is the process of evaluating cloud service providers (CSPs) across security, compliance, operational resilience, and contractual dimensions before migrating data or workloads to their platforms. It goes beyond traditional vendor assessments to address cloud-specific risks including shared responsibility model gaps, data sovereignty, multi-tenancy isolation, API security, and the provider's own subprocessor ecosystem. Due diligence should evaluate both the CSP's controls and your organization's responsibility for configuring and managing the cloud environment securely.
What certifications should cloud vendors have?
Essential certifications depend on your industry: SOC 2 Type II is the baseline for any cloud vendor. ISO 27001 demonstrates a mature information security management system. ISO 27017 is cloud-specific security guidance. ISO 27018 addresses PII protection in public clouds. CSA STAR (Cloud Security Alliance) provides cloud-specific assurance. FedRAMP is required for US government workloads. PCI DSS is needed for payment data. HIPAA/HITRUST for healthcare. C5 (BSI) for German government requirements. Look for certifications relevant to your regulatory environment.
How do you assess shared responsibility in cloud environments?
The shared responsibility model defines which security controls are managed by the CSP and which are your responsibility. For IaaS, the CSP manages physical infrastructure while you manage everything from the OS up. For PaaS, the CSP also manages the OS and runtime. For SaaS, the CSP manages nearly everything, but you still own data classification, access management, and configuration. The critical assessment task is identifying gaps where neither party has explicitly accepted responsibility, particularly around encryption key management, logging, identity federation, and incident response coordination.
What are the biggest risks with cloud vendors?
Top cloud vendor risks include: data residency and sovereignty violations (data stored in jurisdictions that breach compliance requirements), vendor lock-in through proprietary services and data formats, inadequate multi-tenancy isolation, misconfiguration by the customer leading to data exposure, CSP service outages affecting business continuity, subprocessor risk (CSPs use their own vendors), API security vulnerabilities, and cost unpredictability. Shadow IT, unauthorized cloud adoption, amplifies all these risks by creating unassessed cloud dependencies.
Conclusion
Cloud vendor due diligence demands a specialized approach that accounts for shared responsibility models, data sovereignty requirements, and cloud-specific security concerns. As organizations continue migrating critical workloads to the cloud, the thoroughness of CSP assessment directly determines the security and compliance posture of the entire organization. Build assessment frameworks that address cloud-native risks, maintain continuous monitoring of cloud vendor security posture, and plan exit strategies before you need them.