CAIQ Lite, explained
The CAIQ — the Cloud Security Alliance's Consensus Assessments Initiative Questionnaire — is how many customers ask cloud vendors about their security. CAIQ Lite is its shorter version. This page explains, in plain English, what each area is getting at, and gives you an original starter checklist so you can prepare your answers before the spreadsheet arrives.
Download the starter checklist (CSV, 34 items)
We don't reproduce CAIQ questions. Get the official questionnaire from the Cloud Security Alliance or from your customer; use this page to prepare.
How CAIQ Lite is organized
CAIQ questions are grouped by the control domains of CSA's Cloud Controls Matrix (CCM). Most are yes/no questions with room for a short explanation, so a good answer is a clear yes or no followed by one or two sentences of evidence. Domain names and numbering differ between CCM versions — check which version your customer sent. Below we use the CCM v4 domain titles, which cover the same ground as earlier versions under slightly different names.
What each domain is really asking
| Domain | In plain English |
|---|---|
| A&A — Audit & Assurance | Whether independent people check your controls, how often, and what you do with their findings. |
| AIS — Application & Interface Security | How you build and test software and APIs so they resist common attacks. |
| BCR — Business Continuity Management & Operational Resilience | How you keep running, or recover, when something big breaks. |
| CCC — Change Control & Configuration Management | How changes to production are approved, tracked and reversible. |
| CEK — Cryptography, Encryption & Key Management | How data is encrypted and who controls the keys. |
| DCS — Datacenter Security | Physical security of the places your data is stored — usually inherited from your cloud provider. |
| DSP — Data Security & Privacy Lifecycle Management | What data you collect, where it lives, how long you keep it and how you delete it. |
| GRC — Governance, Risk & Compliance | Who owns security, which policies exist, and how risks are managed. |
| HRS — Human Resources | Background checks, confidentiality, training and offboarding for staff. |
| IAM — Identity & Access Management | Who can log in to what, with which factors, and how access is reviewed. |
| IPY — Interoperability & Portability | Whether customers can get their data out in a usable format. |
| IVS — Infrastructure & Virtualization Security | Network segmentation, hardening and separation between environments and tenants. |
| LOG — Logging & Monitoring | What you log, how long you keep it and who watches the alerts. |
| SEF — Security Incident Management, E-Discovery & Cloud Forensics | How you detect, handle and communicate security incidents. |
| STA — Supply Chain Management, Transparency & Accountability | How you choose, contract and monitor the vendors that touch customer data. |
| TVM — Threat & Vulnerability Management | Scanning, patching and penetration testing. |
| UEM — Universal Endpoint Management | How company laptops and phones are secured. |
How to prepare in a day
- Collect your evidence first. Policies with review dates, your latest audit or pen test letter, your cloud provider's compliance reports, your subprocessor list and your incident response plan. Most CAIQ answers point to one of these.
- Answer the checklist below in your own words, replacing the bracketed parts. Keep each answer short and true.
- Mark inherited controls clearly. Physical data-centre security is usually your cloud provider's; say so and point to their report rather than claiming it as your own.
- Import the answers into RFPKit and approve them. When the real CAIQ arrives, upload it as a project and each question is matched to your prepared answers.
Starter checklist
A&A — Audit & Assurance
- Are our security controls reviewed by an independent party?
Starter answer: Our controls are assessed by [an independent auditor / an external consultant] every [12 months]. The latest assessment was completed in [month year].
Have ready: Audit report or assessment letter; dates of the last two assessments - How do we track audit findings to closure?
Starter answer: Findings are logged in [our ticketing system] with an owner and due date and reviewed monthly until closed.
Have ready: Findings tracker export with owners and status
AIS — Application & Interface Security
- Do we follow a secure development process with code review?
Starter answer: Every change is peer-reviewed and passes automated tests and dependency scanning before release.
Have ready: Branch-protection settings; CI pipeline description - Are our APIs authenticated and rate limited?
Starter answer: All API endpoints require authentication with [API keys / OAuth] and are rate limited per client.
Have ready: API documentation; rate-limit configuration
BCR — Business Continuity Management & Operational Resilience
- Do we have tested backups and recovery objectives?
Starter answer: Backups run [continuously] and are restore-tested [twice a year]. Our RTO is [4 hours] and RPO is [1 hour].
Have ready: Backup configuration; last restore test record - Do we have a business continuity plan?
Starter answer: Our continuity plan covers loss of a region, key vendors and key staff, and is exercised [annually].
Have ready: Continuity plan; last exercise notes
CCC — Change Control & Configuration Management
- How are production changes approved and recorded?
Starter answer: Production changes go through pull requests with review and are deployed by CI/CD; every deployment is logged and can be rolled back.
Have ready: Deployment log sample; rollback procedure - Do we manage infrastructure configuration as code?
Starter answer: Infrastructure is defined [as code in our repository] and changes follow the same review process as application code.
Have ready: Repository structure; review policy
CEK — Cryptography, Encryption & Key Management
- Is customer data encrypted at rest and in transit?
Starter answer: Data is encrypted at rest with [AES-256] and in transit with TLS [1.2+].
Have ready: Cloud encryption settings; TLS configuration scan - Who can access encryption keys, and are they rotated?
Starter answer: Keys are held in [our cloud provider's KMS], access is limited to [named roles], and keys rotate [automatically].
Have ready: KMS access policy; rotation settings
DCS — Datacenter Security
- Where is our infrastructure hosted, and who secures the data centres?
Starter answer: We run on [cloud provider]; physical data-centre security is provided and audited by them.
Have ready: Provider's compliance report (from their trust portal) - Do we operate any physical servers ourselves?
Starter answer: [No. We don't operate our own servers or data centres.]
Have ready: Architecture diagram
DSP — Data Security & Privacy Lifecycle Management
- Do we know what customer data we hold and where?
Starter answer: We keep a data inventory listing each data type, where it's stored and who can access it.
Have ready: Data inventory or data-flow diagram - How long do we retain customer data and how is it deleted?
Starter answer: Customer data is kept while the account is active and deleted within [30 days] of termination, including backups.
Have ready: Retention policy; deletion procedure
GRC — Governance, Risk & Compliance
- Who is accountable for information security?
Starter answer: Our [CTO] is accountable for security and reports to [the leadership team] [quarterly].
Have ready: Org chart; role description - Do we maintain and review security policies and a risk register?
Starter answer: Policies are reviewed [annually]; risks are tracked in a register with owners and reviewed [quarterly].
Have ready: Policy index with review dates; risk register
HRS — Human Resources
- Do staff get background checks, NDAs and security training?
Starter answer: Staff with access to customer data are background-checked where lawful, sign confidentiality agreements and complete security training [annually].
Have ready: Onboarding checklist; training completion records - How quickly is access removed when someone leaves?
Starter answer: Accounts are disabled [on the last working day] through our identity provider.
Have ready: Offboarding checklist; sample ticket
IAM — Identity & Access Management
- Is MFA required for administrative and production access?
Starter answer: Yes. MFA is enforced for all production, cloud-console and source-code access.
Have ready: Identity provider MFA policy screenshot - How often are user access rights reviewed?
Starter answer: Access to production and customer data is reviewed [quarterly] and removed when no longer needed.
Have ready: Last access review record
IPY — Interoperability & Portability
- Can customers export their data?
Starter answer: Customers can export all their data at any time in [CSV and JSON] without contacting support.
Have ready: Export feature documentation - Do we document our APIs for integration?
Starter answer: Our API is documented at [docs URL] [or: available on request].
Have ready: API reference link
IVS — Infrastructure & Virtualization Security
- Are production and non-production environments separated?
Starter answer: Production runs in separate accounts with separate credentials; production data isn't copied to test.
Have ready: Account structure diagram - How is one customer's data kept separate from another's?
Starter answer: Each customer's data is [logically isolated in its own database] and every request is authorized against its tenant.
Have ready: Architecture description; isolation tests
LOG — Logging & Monitoring
- Do we log security-relevant events and protect the logs?
Starter answer: Authentication, admin actions and data access are logged, retained for [12 months] and protected from modification.
Have ready: Logging configuration; retention settings - Who responds to security alerts?
Starter answer: Alerts go to [the on-call engineer] [24/7] with a documented escalation path.
Have ready: On-call schedule; alert runbook
SEF — Security Incident Management, E-Discovery & Cloud Forensics
- Do we have an incident response plan, and is it tested?
Starter answer: Our incident response plan defines roles and severity levels and is tested with a tabletop exercise [annually].
Have ready: IR plan; last tabletop notes - How fast do we notify customers of incidents affecting their data?
Starter answer: We notify affected customers without undue delay and within [72 hours] of confirming an incident.
Have ready: Notification clause in contracts or DPA
STA — Supply Chain Management, Transparency & Accountability
- Do we publish a subprocessor list and assess vendors?
Starter answer: Our subprocessor list is published at [URL]; vendors handling customer data are assessed before onboarding and reviewed [annually].
Have ready: Subprocessor list; vendor review records - Do our vendor contracts include security obligations?
Starter answer: Yes. Contracts with subprocessors include confidentiality, security and incident-notification obligations.
Have ready: DPA template
TVM — Threat & Vulnerability Management
- How quickly do we patch critical vulnerabilities?
Starter answer: Critical vulnerabilities are fixed within [7 days] and high ones within [30 days].
Have ready: Vulnerability SLA policy; scanner report - Do we have regular penetration tests?
Starter answer: An independent penetration test is performed [annually]; a summary letter is available under NDA.
Have ready: Pen test summary letter
UEM — Universal Endpoint Management
- Are company devices encrypted and centrally managed?
Starter answer: Company laptops use full-disk encryption, automatic updates and screen lock, and are managed with [MDM tool].
Have ready: MDM compliance report - Can we wipe a lost device remotely?
Starter answer: Yes. Lost or stolen devices can be locked and wiped remotely.
Have ready: MDM remote-wipe procedure
These are starting points, not compliance advice. RFPKit doesn't certify anything; you're responsible for every answer you send.
Prepare once, answer every CAIQ
Free, unlimited users and questionnaires. No account or email needed — you get a private link.
Create a free workspace