Last updated: 20 November 2026
Quick answer: The CSA Cloud Controls Matrix (CCM) is a free, vendor-neutral cloud security control framework from the Cloud Security Alliance. Version 4.1, released on 27 January 2026, contains 207 controls across 17 domains, maps to major standards and underpins the CAIQ questionnaire and the STAR assurance programme used by cloud providers and their customers.
Every CISO now runs a cloud estate, whether it is a handful of SaaS applications or a multi-cloud platform. The hard part is rarely finding controls. It is knowing which controls the provider owns, which you own, and how to compare providers on the same basis.
This guide explains what the CSA Cloud Controls Matrix covers, what changed with v4.1, how it relates to CAIQ, STAR, ISO 27001 and SOC 2, and how to use it in a supplier assurance programme that also satisfies EU rules such as NIS2 and DORA.
What is the CSA Cloud Controls Matrix?
The CSA Cloud Controls Matrix is a cybersecurity control framework designed specifically for cloud computing. It lists control objectives, states whether each applies to the cloud service provider, the customer or both, and maps them to other standards so one assessment can support several compliance goals.
According to the Cloud Security Alliance’s CCM page, the matrix is free to download for internal use within an organisation, while commercial uses such as building it into products or consulting services require a licence. It is available as a spreadsheet and in machine-readable formats, including JSON, YAML and OSCAL.
The CCM is useful to two audiences. Cloud providers use it to structure their security programme and describe it to customers. Cloud customers, including CISOs, use it to assess providers and to design their own side of the shared responsibility model.
What changed in CCM v4.1?
CCM v4.1 is an update to the v4 framework rather than a redesign. The CCM and CAIQ v4.1 release, published on 27 January 2026, contains 207 controls across 17 security domains, up from 197 control objectives in v4.0.
The v4.1 bundle includes:
- The matrix itself with mappings to industry standards.
- CAIQ v4.1, the questionnaire version that can be submitted to the STAR Registry.
- Implementation guidelines and continuous auditing metrics.
- A change analysis comparing v4.0.3 with v4.1, so you can see which assessment questions moved.
In practice: if your supplier questionnaires reference CAIQ v4.0, use the change analysis to update your question set once, rather than asking each provider to explain the differences.
Which domains does the CCM cover?
The CCM groups its controls into 17 domains, the structure used since v4. Together they cover governance, technical security and supply chain topics.
| Code | Domain |
|---|---|
| A&A | Audit and Assurance |
| AIS | Application and Interface Security |
| BCR | Business Continuity Management and Operational Resilience |
| CCC | Change Control and Configuration Management |
| CEK | Cryptography, Encryption and Key Management |
| DCS | Datacenter Security |
| DSP | Data Security and Privacy Lifecycle Management |
| GRC | Governance, Risk and Compliance |
| HRS | Human Resources |
| IAM | Identity and Access Management |
| IPY | Interoperability and Portability |
| IVS | Infrastructure and Virtualization Security |
| LOG | Logging and Monitoring |
| SEF | Security Incident Management, E-Discovery and Cloud Forensics |
| STA | Supply Chain Management, Transparency and Accountability |
| TVM | Threat and Vulnerability Management |
| UEM | Universal Endpoint Management |
Two domains deserve particular attention from EU-regulated firms. IPY supports exit and portability planning, which matters for DORA exit strategies. STA covers supply chain transparency, which supports NIS2 supply chain requirements.
How does the shared security responsibility model work in the CCM?
For each control, the CCM guidance helps you record who is responsible: the provider, the customer, or both. This is the Shared Security Responsibility Model (SSRM) that runs through the v4 guidance.
Responsibility shifts with the service model. For infrastructure services, the customer usually owns operating system hardening, identity configuration and data encryption choices. For SaaS, the provider owns far more, but the customer still owns user access, data classification and configuration of security features.
Common mistake: accepting a provider’s certificate as proof that a control is covered. A SOC 2 report or ISO certificate shows what the provider does. It does not cover the customer-side half of shared controls, such as enforcing MFA for your own users.
How do CAIQ and STAR relate to the CCM?
The CAIQ turns the CCM into yes/no style questions, and STAR is the public registry and assurance programme built on both. As the CSA STAR programme page explains, there are two main levels:
- Level 1: self-assessment. The provider completes the CAIQ and publishes it in the STAR Registry. Suited to lower-risk use cases.
- Level 2: third-party audit. STAR Attestation builds on a SOC 2 examination and STAR Certification builds on ISO/IEC 27001 certification, each assessed against CCM criteria.
For AI services, CSA has also introduced STAR for AI. Since 20 November 2025, organisations can reach STAR for AI Level 2 by combining an AI-CAIQ assessment with ISO/IEC 42001 certification.
For a CISO, the STAR Registry is a free first stop in due diligence. Checking whether a provider has a current Level 1 or Level 2 entry often answers a large part of your questionnaire before you send it.
CSA CCM vs ISO 27001 vs SOC 2
These frameworks complement each other rather than compete. The table summarises how they differ.
| Aspect | CSA CCM | ISO/IEC 27001 | SOC 2 |
|---|---|---|---|
| What it is | Cloud-specific control framework | Management system standard (ISMS) | Attestation report on controls |
| Scope | Cloud services, provider and customer | Any organisation | Service organisations |
| Assurance route | CAIQ self-assessment or STAR Level 2 | Accredited certification | Independent CPA examination |
| Shared responsibility | Built in per control | Not cloud-specific | Via complementary user entity controls |
| Typical market | Global cloud buyers | Global, strong in the EU | Strong in North America |
If you already run an ISMS, the CCM slots in as a cloud-focused control set. See our ISO 27001 overview, our SOC 2 framework page and our comparison of SOC 2 vs ISO 27001 for detail on each.
Want to test CCM controls against your existing ISO 27001 evidence? Start your 14-day free trial and map them side by side.
How does the CCM help with NIS2 and DORA?
It gives you a structured way to assess and document cloud supplier security, which both regimes demand. It does not replace their specific legal requirements.
Under the NIS2 Directive, Article 21(2)(d) requires essential and important entities to address supply chain security, including security aspects of relationships with direct suppliers and service providers. CCM-based questionnaires and STAR evidence are practical inputs to that assessment.
For financial entities, DORA’s ICT third-party risk rules expect due diligence, contractual safeguards and exit planning for ICT providers. The CCM’s STA, IPY and BCR domains map well to those topics, but you still need DORA-specific artefacts such as the register of information. Our DORA framework page covers those requirements.
How should a CISO implement the CCM?
Treat it as a control library for cloud risk, not a separate compliance project. A practical sequence:
- Inventory cloud services. List every IaaS, PaaS and SaaS service and rank them by data sensitivity and business criticality.
- Tailor the control set. Select the CCM controls relevant to each service model and mark customer, provider and shared ownership.
- Map to existing frameworks. Link CCM controls to your ISO 27001 Annex A, SOC 2 criteria or NIST controls so evidence is reused. A cross-framework library such as the Compliance Universe helps here.
- Assess providers. Start with STAR Registry entries, then send CAIQ-based questions only where gaps remain.
- Assess yourself. Test your customer-side controls, such as identity configuration and logging.
- Track and review. Record findings in your vendor and third-party risk management process and reassess on renewal or major change.
What about AI services in the cloud?
CSA has extended the CCM approach to AI. The AI Controls Matrix (AICM), first released on 9 July 2025 and updated to v1.1 on 30 October 2025, contains 243 control objectives across 18 domains. It builds on the CCM and maps to ISO/IEC 42001, ISO 27001, the NIST AI RMF and the EU AI Act.
In practice: if you are assessing AI features offered by SaaS providers, use the CCM for the underlying cloud service and the AICM for model and data-specific risks.
Key takeaways
- The CSA Cloud Controls Matrix v4.1 has 207 controls across 17 domains and was released on 27 January 2026.
- It is free for internal use and maps to widely used standards, so one assessment can support several frameworks.
- Use the shared responsibility guidance to separate provider controls from your own.
- STAR Level 1 and Level 2 entries are a quick first check in cloud supplier due diligence.
- The CCM supports NIS2 and DORA supplier assessments but does not replace their specific requirements.
Frequently asked questions
Is the CSA Cloud Controls Matrix free?
Yes, for internal use. The Cloud Security Alliance allows organisations to download and use the CCM within their own organisation at no cost. Commercial uses, such as embedding the matrix in a product or using it to deliver consulting services, require a licence from CSA. Check the current licence terms on the CSA website before reuse.
Is CCM a certification?
No. The CCM is a control framework. Certification or attestation comes through the CSA STAR programme at Level 2, where STAR Certification builds on ISO/IEC 27001 and STAR Attestation builds on a SOC 2 examination. Level 1 is a self-assessment published in the STAR Registry, not an independent audit.
What is the difference between CCM and CAIQ?
The CCM lists the control objectives and guidance. The CAIQ, or Consensus Assessment Initiative Questionnaire, turns those controls into questions a cloud provider answers to describe its security posture. In v4.1, CSA publishes the CCM and CAIQ together, and a completed CAIQ can be submitted to the STAR Registry.
Should cloud customers use the CCM, or only providers?
Both. Providers use it to structure and demonstrate their controls. Customers use it to assess providers consistently and to design their own responsibilities under the shared security model, such as identity management, data classification and logging. Many security teams use CCM-based questions as the core of their cloud supplier questionnaire.
Does the CCM cover privacy requirements such as GDPR?
Partly. The Data Security and Privacy Lifecycle Management domain covers data classification, retention, privacy by design and related controls. It helps demonstrate security of processing, but it does not replace GDPR-specific work such as records of processing, lawful basis analysis, DPIAs or processor contracts.
Conclusion: one cloud control language for providers and customers
The CSA Cloud Controls Matrix gives CISOs a common language for cloud security that providers already recognise. Use it to divide responsibilities clearly, reuse evidence across ISO 27001, SOC 2 and EU regulation, and keep supplier reviews consistent. For wider supplier risk, read our article on third-party risk and executive liability. Enactia’s AI-powered GRC platform includes CSA CCM among its 50+ frameworks.
To see how CCM mapping fits into your compliance programme, contact us or book a demo or start your 14-day free trial.
