Sign in
Guide · Cloud security

CAIQ v4: a practical guide.

The Cloud Security Alliance’s Consensus Assessments Initiative Questionnaire, how it maps to the Cloud Controls Matrix, and how cloud providers keep their answers consistent.

10 min readWritten by the DeelSignal team
On this pageWhat the CAIQ is

If you run a cloud service, the CAIQ is the questionnaire that buyers reach for when they want a standard, cloud-specific view of your controls. The good news: it’s more predictable than most.

01What the CAIQ is

The Consensus Assessments Initiative Questionnaire (CAIQ) is published by the Cloud Security Alliance (CSA). Version 4 is aligned to the Cloud Controls Matrix (CCM) v4, CSA’s framework of cloud security control objectives. Each CAIQ question maps to a CCM control, so answering the CAIQ is effectively stating how you implement the CCM.

CAIQ and CSA STARProviders can publish a completed CAIQ to CSA’s STAR Registry as a Level 1 self-assessment. Many buyers check the registry before sending a questionnaire at all.

02Who sends it, and when

Security and procurement teams evaluating SaaS, PaaS or IaaS providers send the CAIQ, often early in an evaluation. Some accept a link to your STAR entry; others want the spreadsheet filled in again, sometimes alongside their own supplemental questions.

Because it is cloud-specific, it lands well with technical buyers. It’s also common as an attachment inside a larger RFP security section.

03How it’s structured

CAIQ v4 follows the domains of CCM v4. Questions are answered Yes / No / N/A, with columns to say whether the control is the responsibility of the cloud service provider (CSP), the customer (CSC), or shared, plus a free-text implementation description.

DomainWhat it asks aboutUsual owner
A&AAudit & assuranceIndependent audits, assessment planningGRC
AISApplication & interface securitySecure development, API securityEngineering
BCRBusiness continuity & resilienceBackups, DR, continuity testingOps / SRE
CEKCryptography & key managementEncryption at rest and in transit, key rotationSecurity
DSPData security & privacyClassification, retention, deletion, privacySecurity / Legal
IAMIdentity & access managementLeast privilege, MFA, access reviewsIT / Security
IVSInfrastructure & virtualizationSegmentation, hardening, tenant isolationEngineering
LOGLogging & monitoringAudit logs, alerting, log protectionSecurity
SEFIncident management & forensicsResponse plans, notification, e-discoverySecurity
STASupply chain transparencySubprocessors, shared responsibilityGRC / Procurement

Other domains cover change control, datacenter security, governance, HR, interoperability, threat and vulnerability management, and endpoint management.

04How long it takes

A first CAIQ typically takes one to three weeks, because it forces decisions about shared responsibility that may never have been written down. After that, updating it for a new buyer can take hours, as long as the previous answers are trusted and current.

05Common pitfalls

  • Wrong responsibility column. Marking a control as provider-owned when the customer actually configures it (for example, customer-managed SSO settings).
  • Inheriting your hosting provider’s answers wholesale. Your cloud provider’s controls cover their layer, not yours.
  • Empty implementation descriptions. A “Yes” with no description is the first thing reviewers question.
  • Drift from your STAR entry. The spreadsheet you send should match what’s published.
Shared responsibility is the hard partWrite down who owns each control once, review it with engineering, and reuse it. Most CAIQ follow-ups come from this column.

06Answer faster with an answer library

Because every CAIQ question maps to a stable CCM control ID, it’s ideal for an answer library keyed by control. Store the approved answer, the responsibility split and the source for each, and new CAIQs become a review exercise.

  1. Key answers by CCM control ID so they survive minor wording changes.
  2. Record CSP / CSC / shared ownership alongside each answer.
  3. Link each answer to the policy, runbook or audit excerpt that supports it.
  4. Reuse the same answers in SIGs and custom questionnaires that ask the same thing.
Sample question · CEKIllustrative sample

Are data at rest encrypted using industry-standard algorithms, and are encryption keys managed and rotated according to a defined policy?

Yes, provider responsibility. Customer data at rest is encrypted with AES-256 using keys held in a managed key service; keys are rotated at least annually and on suspected compromise.1 Data in transit is protected with TLS 1.2 or higher.2
1Cryptography & Key Management Standard v2.0 · Section 4
2Platform architecture overview · Data protection
Cited · 2 approved sourcesConfidence 0.92

Why it works: it states the responsibility split explicitly, names the algorithm and rotation interval, and cites the standard a reviewer can request.

07How DeelSignal handles a CAIQ

DeelSignal imports the CAIQ in the format it arrived in and drafts each answer from your approved sources only: policies, past approved answers, SOC 2 report excerpts and product documentation.

  • Sanitized first. Customer names, people, hosts, IPs, keys and amounts are swapped for placeholders before any model sees the text. Try the checker to see the idea.
  • Cited, always. Every drafted answer links to the source passage it came from, so reviewers check evidence instead of rewriting.
  • Stops and asks. When sources disagree or nothing covers a question, the agent holds it and routes it to the right expert over Slack or email.
  • Exports ready to send. An Excel workbook in import order, a portal paste list, DOCX or PDF.
A note on security postureDetails on encryption, SSO and data residency are on the security page.

Your next CAIQ, mostly drafted.

DeelSignal answers from your approved sources, cites every answer, sanitizes customer data first, and asks an expert when the sources don’t agree.