
CDPSE (Certified Data Privacy Solutions Engineer) from ISACA is a technical privacy certification. Unlike legal privacy credentials, it checks that you can build privacy into systems: data inventories and flows, privacy impact assessments, data minimisation, retention and deletion, consent and cookie management, anonymisation and pseudonymisation, encryption, access control and privacy in AI and ML. With India's Digital Personal Data Protection (DPDP) Act, 2023 and GDPR for global clients, Indian IT companies and GCCs need engineers and analysts who can turn privacy rules into working controls.
This guide follows ISACA's official CDPSE exam content outline and the ISACA exam candidate guide: exam facts, the four domains with weights and topics, privacy engineering techniques, an 8-week plan and 15 original practice questions.
Quick facts (ISACA, November 2026)
| Item | Detail |
|---|---|
| Questions | 120 multiple-choice questions |
| Duration | 3.5 hours (210 minutes) |
| Passing score | Scaled score of 450 or higher on a 200–800 scale |
| Delivery | PSI testing centre or online remote proctoring; registration is continuous |
| Fee | US$575 for ISACA members; US$760 for non-members |
| Language | English |
| Experience | 3 or more years in data privacy governance, privacy risk management and compliance, privacy engineering and/or data lifecycle work; no waivers or substitutions |
| After passing | You have 5 years to apply for the certification |
Read the official CDPSE exam content outline and the CDPSE certification page before you book.
The four domains and weights
| Domain | Weight | Topics (from the outline) |
|---|---|---|
| 1. Privacy Governance | 20% | Personal information; privacy principles (privacy by design, consent, transparency); laws and regulations; privacy documentation; culture and responsibilities; vendor and supply chain management; incident management; data subject rights, requests and notification |
| 2. Privacy Risk Management and Compliance | 18% | Risk process and policies; privacy impact assessments; training and awareness; threats and vulnerabilities; risk response; privacy frameworks; evidence and artefacts; programme monitoring and metrics |
| 3. Data Life Cycle Management | 23% | Data inventory, data-flow diagrams and classification; data quality; use limitation; analytics (aggregation, AI, data warehouses); data minimisation; disclosure and transfer; storage, retention and archiving; destruction |
| 4. Privacy Engineering | 39% | Infrastructure and cloud platforms; devices and endpoints; connectivity; secure development lifecycle; APIs and cloud-native services; asset management; IAM; patching and hardening; protocols; encryption and hashing; monitoring and logging; consent tagging; cookies and tracking; anonymisation and pseudonymisation; privacy-enhancing technologies; AI and ML considerations |
Privacy engineering techniques
| Need | Technique |
|---|---|
| Know what personal data you hold | Data inventory, data-flow diagrams and classification tags |
| Collect less | Data minimisation: collect only fields needed for a stated purpose |
| Use data for analytics safely | Pseudonymisation (reversible with a separately held key) or anonymisation (not reversible); aggregation |
| Respect user choices | Consent records and consent tags that travel with the data; cookie consent management |
| Protect data at rest and in transit | Encryption, hashing with salts for identifiers, TLS |
| Answer access and erasure requests | Searchable inventories and deletion workflows across systems and backups |
| Reduce exposure over time | Retention schedules and secure deletion |
| Assess new projects | Privacy impact assessments before launch |
8-week study plan
| Week | Focus |
|---|---|
| 1 | Domain 1: privacy principles, privacy by design, laws (DPDP Act, 2023 and GDPR as examples), roles, data subject rights |
| 2 | Domain 1 and 2: vendor management, incidents and notification, privacy impact assessments, frameworks |
| 3 | Domain 2: risk response, evidence, metrics and monitoring |
| 4 | Domain 3: inventories, data flows, classification, quality, use limitation, analytics and AI |
| 5 | Domain 3: minimisation, transfers, retention, archiving, destruction |
| 6 | Domain 4: cloud, endpoints, APIs, SDLC, IAM, hardening, encryption, logging |
| 7 | Domain 4: consent tagging, cookies, anonymisation, pseudonymisation, PETs, AI and ML privacy |
| 8 | Timed 120-question practice runs, review weak domains, book the exam |
15 practice questions with answers
These are original questions written for this guide, not exam questions.
1. What does privacy by design mean?
Building privacy into systems and processes from the start, with privacy as the default setting.
2. What should be done before launching a new system that processes personal data?
A privacy impact assessment.
3. What is data minimisation?
Collecting and keeping only the personal data needed for a stated purpose.
4. Pseudonymisation or anonymisation: which can be reversed?
Pseudonymisation, using separately held additional information.
5. Why build a data inventory first?
You can't protect, retain or delete personal data you don't know you have.
6. What does a data-flow diagram show?
Where personal data enters, moves, is stored and leaves, including third parties.
7. What is purpose (use) limitation?
Using personal data only for the purposes it was collected for.
8. A user withdraws consent. What should systems do?
Stop the processing that relied on that consent, using consent records or tags to find the data.
9. Why is deletion hard in practice?
Copies exist in backups, logs, analytics stores and vendor systems.
10. What should a vendor contract include for personal data?
Purpose limits, security requirements, breach notification, audit rights and data return or deletion.
11. Name one privacy risk in machine learning.
A model can memorise and reveal personal data from its training set.
12. Which control limits who can view personal data?
Role-based access control with least privilege.
13. What is a privacy-enhancing technology?
A technique such as differential privacy or secure computation that allows data use while protecting individuals.
14. Which CDPSE domain has the most weight?
Privacy Engineering at 39%.
15. Can experience waivers be used for CDPSE?
No. CDPSE has no experience waivers or substitutions.
Before and after CDPSE
- Pair it with CCSP for cloud data security, or CRISC and CGRC for risk and compliance.
- Learn hands-on in our Cyber Security course and Cloud Security course; see live jobs.
Cloud Soft Solutions in Ameerpet, Hyderabad teaches cyber security, cloud security and data engineering with real-time projects. See the APEX program and all courses.
📞 Call +91 96660 19191 · WhatsApp · Flat No. 513, 5th Floor, Nilagiri Block, Aditya Enclave, Ameerpet, Hyderabad
Frequently Asked Questions
How long is the CDPSE exam?
3.5 hours (210 minutes) for 120 multiple-choice questions.
What is the CDPSE passing score?
A scaled score of 450 or higher on a 200–800 scale.
How much does the CDPSE exam cost?
US$575 for ISACA members and US$760 for non-members.
How much experience does CDPSE need?
3 or more years in data privacy governance, privacy risk and compliance, privacy engineering and/or data lifecycle work, with no waivers.
Which CDPSE domain has the most weight?
Privacy Engineering at 39%.
Is CDPSE a legal certification?
No. It is a technical certification about building privacy into systems and data processes.



