Standards and authorizations for cloud service providers and the SaaS products built on them. 7 entries, 3 with a full guide.
Cloud compliance is about shared responsibility. Your infrastructure provider's certificates cover their data centres and platform; you remain responsible for how you configure and run your service on top of them. Auditors will ask you to show both.
FedRAMP is mandatory for cloud services used by US federal agencies and is in the middle of a major change (FedRAMP 20x). Commercial SaaS vendors usually rely on SOC 2 or ISO 27001, extended with ISO/IEC 27017 (cloud security controls) and ISO/IEC 27018 (personal data in public clouds).
The Cloud Security Alliance's STAR registry and Cloud Controls Matrix give a cloud-specific control set that maps to all of these.
ISO/IEC 27001:2022 Information security, cybersecurity and privacy protection: Information security management systems (ISMS) requirements
Certifiable standardVoluntaryGlobal
ISO/IEC 27001 is the international standard for an information security management system (ISMS). It requires you to define a scope, assess information security risks, choose controls from Annex A (93 controls in four themes) or elsewhere, and run a cycle of monitoring, internal audit, management review and improvement. It is voluntary, but an accredited ISO 27001 certificate is the most widely recognised proof of security for IT companies worldwide.
Covers, who needs it and key requirements
What it covers
Governance of information security: scope, risk assessment and treatment, policies, Annex A controls (organisational, people, physical, technological), internal audit, management review and continual improvement.
Who needs it
IT service providers, software and SaaS companies, data centres, BPOs, fintechs and any organisation whose clients ask for independent proof of information security.
Why it matters
It answers most security questionnaires with one certificate, is recognised in every market and is often a precondition for enterprise, banking and government contracts.
System and Organization Controls 2 (SOC 2) report on controls relevant to security, availability, processing integrity, confidentiality or privacy
Attestation reportVoluntaryUS / global
SOC 2 is an independent attestation report, produced by a licensed CPA firm under AICPA standards, on how a service organisation's controls meet the Trust Services Criteria for security and, optionally, availability, processing integrity, confidentiality and privacy. A Type I report tests control design at a point in time; a Type II report tests operating effectiveness over a period, usually 6 to 12 months. It is the security report most US enterprise customers ask SaaS vendors for.
Covers, who needs it and key requirements
What it covers
Security (the mandatory common criteria CC1 to CC9: control environment, risk assessment, monitoring, logical and physical access, system operations, change management, risk mitigation) plus optional availability, processing integrity, confidentiality and privacy criteria.
Who needs it
SaaS, cloud, data and managed service providers that store or process customer data, especially those selling to US enterprises.
Why it matters
It is the default evidence enterprise security and procurement teams request, and a clean Type II report shortens security reviews.
Applies in
United States origin; used worldwide by companies selling to US-based customers
Government authorizationMandatory if in scopeUS federal
FedRAMP is the US government programme that standardises security assessment and authorization of cloud products used by federal agencies. Cloud service providers implement a NIST SP 800-53 baseline (Low, Moderate or High), are assessed by an accredited third-party assessment organisation (3PAO), and receive an authorization listed on the FedRAMP Marketplace, followed by continuous monitoring. FedRAMP 20x, launched in 2025, is replacing document-heavy Rev. 5 packages with automated, machine-readable evidence.
Covers, who needs it and key requirements
What it covers
Cloud service offerings (IaaS, PaaS, SaaS) used by federal agencies: security baselines, system security plan, 3PAO assessment, authorization, continuous monitoring, incident reporting and significant change management.
Who needs it
SaaS, PaaS and IaaS providers that sell, or want to sell, to US federal agencies, and their subcontractors handling federal data.
Why it matters
Agencies cannot use a cloud service without it, and a FedRAMP authorization is reused across agencies and trusted by state governments and regulated industries.
Choose an impact level (Low, Moderate, High) based on FIPS 199 categorisation
Implement the FedRAMP baseline controls from NIST SP 800-53 Rev. 5
Document the system security plan and boundary (or 20x key security indicators)
Independent assessment by an accredited 3PAO
Authorization by an agency or the FedRAMP Board
Continuous monitoring: monthly vulnerability scanning, POA&M updates and annual assessments
ISO 27017
ISO/IEC 27017:2015 Code of practice for information security controls based on ISO/IEC 27002 for cloud services
Certifiable standardVoluntaryGlobal
ISO/IEC 27017 adds cloud-specific guidance to the ISO 27002 controls and seven extra controls for cloud service providers and customers, such as shared roles and responsibilities, removal of customer assets, segregation in virtual environments, virtual machine hardening and monitoring of cloud services. It is usually assessed as an extension to an ISO 27001 certification and shows customers how a cloud or SaaS provider splits security responsibilities with them.
Covers, who needs it and key requirements
What it covers
Cloud-specific implementation guidance for ISO 27002 controls and additional controls on shared responsibility, customer asset removal, tenant segregation, administrator operations and cloud monitoring.
Who needs it
Cloud service providers, SaaS vendors and managed hosting providers, and enterprise cloud customers.
Why it matters
It answers the shared-responsibility questions cloud customers ask and strengthens an ISO 27001 certificate for cloud services.
Document shared roles and responsibilities between provider and customer
Segregate customer environments in shared virtual infrastructure
Harden virtual machines and protect administrative operations
Return or securely remove customer assets at contract end
Give customers the ability to monitor relevant cloud activity
ISO 27018
ISO/IEC 27018:2025 Code of practice for protection of personally identifiable information (PII) in public clouds acting as PII processors
Certifiable standardVoluntaryGlobal
ISO/IEC 27018 sets privacy controls for public cloud providers that process personal data on behalf of customers. It covers processing only on customer instructions, transparency about sub-processors and data locations, support for data subject requests, return and deletion of data, breach notification and restrictions on using customer data for marketing. A new edition was published in 2025. It is usually certified alongside ISO 27001 and helps cloud vendors meet GDPR processor duties.
Covers, who needs it and key requirements
What it covers
Public cloud PII processing: customer instructions, consent and purpose limits, transparency, sub-processor disclosure, data location, return and deletion, breach notification and audit rights.
Who needs it
Public cloud, SaaS and hosting providers that process customer personal data.
Why it matters
It is a recognised way for cloud processors to show privacy controls to customers and regulators.
Process PII only on documented customer instructions
Disclose sub-processors and processing locations
Support customers with data subject requests
Notify customers of breaches involving their PII
Return or delete PII at the end of the contract
CSA STAR
Cloud Security Alliance Security, Trust, Assurance and Risk (STAR) programme and Cloud Controls Matrix (CCM)
Certifiable standardVoluntaryGlobal
CSA STAR is the Cloud Security Alliance's public registry and assurance programme for cloud providers, built on the Cloud Controls Matrix (CCM), a cloud-specific control framework now at version 4.1. Level 1 is a free self-assessment published in the registry using the Consensus Assessments Initiative Questionnaire (CAIQ). Level 2 adds third-party validation, either STAR Certification (with ISO 27001) or STAR Attestation (with SOC 2). It helps SaaS vendors answer cloud security questionnaires publicly.
Covers, who needs it and key requirements
What it covers
Cloud Controls Matrix domains such as application security, data security, identity and access, encryption, logging, supply chain and threat management.
Who needs it
SaaS, PaaS and IaaS providers that want public, standardised cloud security transparency.
Why it matters
A public STAR entry and CAIQ answers reduce one-off security questionnaires and map to ISO 27001 and SOC 2.
Complete the CAIQ against the Cloud Controls Matrix
Publish a Level 1 self-assessment in the STAR Registry
For Level 2, combine with an ISO 27001 certification or SOC 2 attestation
Keep the registry entry current
EU Data Act
Data Act, Regulation (EU) 2023/2854 on harmonised rules on fair access to and use of data
LawMandatory if in scopeEU
The EU Data Act, applying since 12 September 2025, gives users of connected products and related services rights to access and share the data they generate, limits unfair data-sharing terms in contracts, and makes cloud and other data processing service providers support customer switching and remove switching charges in stages (fully by 12 January 2027). It also sets safeguards against unlawful non-EU government access to non-personal data held in the EU.
Covers, who needs it and key requirements
What it covers
Access to IoT and related service data, B2B contract fairness, public sector access in emergencies, cloud switching and interoperability, and international data safeguards.
Who needs it
Makers of connected products and related services, and cloud, SaaS and data processing service providers with EU customers.
Why it matters
Cloud and SaaS providers must support switching and data export, which changes contracts and product design.