CIPM Domains III–VI test the privacy operational life cycle as workflows: assess (data inventory, PIAs and DPIAs, vendor and M&A assessments), protect (privacy by design, security controls, retention), sustain (metrics, monitoring, audits), and respond (data subject requests, complaints, incidents). Questions usually ask which step comes first or what the privacy manager should do next, so learn each workflow as a sequence.
The CIPM framework domains (I and II) set up the programme. The operational domains (III–VI) are where it runs day to day, and they make up roughly 40–50 of the 75 scored questions. Learning them as step-by-step workflows is the most reliable way to answer "first" and "next" questions correctly.
nnTo see how these workflows appear as questions, review our CIPM sample questions and exam format, and commit the underlying model to memory with the CIPM privacy operations framework.
1. Data inventory and mapping (Domain III)
- Identify the business functions and owners.
- Catalogue processing activities: data categories, purposes, systems, recipients, locations, retention.
- Map data flows, including transfers and vendors.
- Assign owners and set a review cycle.
Why it matters: the inventory feeds PIAs, rights requests, breach assessments and records of processing. Questions often expect the inventory as the first step.
2. Privacy impact assessments (Domain III)
- Screen: does the project involve personal data or high-risk processing?
- Describe the processing and its purpose.
- Assess necessity, proportionality and risks to individuals.
- Identify mitigations and residual risk.
- Get sign-off (and, where the law requires it, consult the regulator).
- Track the actions and revisit the assessment when the processing changes.
Under the GDPR, a DPIA is mandatory where processing is likely to result in high risk (Article 35). Many organisations run lighter PIAs for everything else.
3. Vendor management (Domain III)
- Due diligence before selection: security, privacy practices, sub-processors, locations.
- Contract: data protection terms, audit rights, breach notification, return or deletion.
- Onboarding: access controls, data minimisation.
- Ongoing monitoring: reassessments, audit reports, incident tracking.
- Offboarding: confirm the data is returned or deleted.
4. Privacy by design and protection (Domain IV)
BoK v4.2.0 highlights the principles and purposes of privacy by design. The seven foundational principles are: proactive not reactive; privacy as the default; privacy embedded into design; full functionality (positive-sum); end-to-end security; visibility and transparency; and respect for user privacy. In practice, this means privacy requirements at the design stage, data minimisation, defaults that protect privacy, retention schedules, and security controls such as access management, encryption and logging.
5. Sustaining performance (Domain V)
- Metrics chosen for the audience: the board wants risk and trend, while operations need volumes and timeliness.
- Monitoring and audits: internal reviews, independent audits, compliance checks.
- Maturity assessment: for example ad hoc, repeatable, defined, managed, optimised.
- Continuous improvement: feed audit findings and incidents back into policies and training.
6. Data subject requests (Domain VI)
- Intake through defined channels.
- Verify identity in proportion to the risk.
- Locate the data, using the inventory.
- Assess exemptions and third-party data.
- Respond within the legal deadline (one month under the GDPR, extendable).
- Record the request and the outcome.
7. Incident response (Domain VI)
- Prepare: a plan, a team, roles, contacts and exercises.
- Detect and report: make sure staff know how to escalate.
- Contain and preserve evidence.
- Assess: is it a personal data breach, and what's the risk to individuals?
- Notify regulators and individuals as required. Deadlines vary by law, for example 72 hours to the regulator under the GDPR.
- Remediate and review lessons learned.
Practise the workflows in scenarios
The CIPM Complete Pack's 18 case studies put these workflows into realistic programme situations across 300 BoK v4.2.0 questions.
Get the Complete PackWho does what: a RACI view of the workflows
CIPM questions often ask who should be responsible or involved. This table shows a typical split (R = responsible, A = accountable, C = consulted, I = informed).
| Workflow | Privacy office | Business owner | IT / security | Legal |
|---|---|---|---|---|
| Data inventory | A | R | C | I |
| PIA / DPIA | A (reviews) | R (completes) | C | C |
| Vendor assessment | R | A | R (security review) | C (contract) |
| Data subject request | A | C (finds data) | R (extracts data) | C (exemptions) |
| Incident response | R | C | R (containment) | A or C (notification) |
The exact split varies, but the principle the exam rewards is that privacy works through the business. The privacy office can't run every workflow alone.
Deadlines the CIPM expects you to know
| Requirement | Deadline |
|---|---|
| GDPR access and other data subject requests | One month, extendable by two further months where necessary |
| CCPA/CPRA consumer requests | 45 days, extendable once by 45 days with notice |
| GDPR breach notification to the authority | Without undue delay and, where feasible, within 72 hours |
| HIPAA breach notification to individuals | Without unreasonable delay, and no later than 60 days after discovery |
| US state breach laws | Vary by state; some set fixed deadlines (such as 30 or 45 days), others say "without unreasonable delay" |
Metrics for each workflow
- Inventory: percentage of systems with an owner and a current record; time since last review.
- Assessments: percentage of new projects assessed before launch; average time to complete.
- Vendors: percentage of high-risk vendors assessed before contract; open findings.
- Requests: volume, average response time, percentage on time.
- Incidents: number by severity, time to contain, repeat causes.
Common exam traps across the workflows
- Skipping identity verification before releasing data in a request.
- Notifying before assessing whether a breach is likely to result in risk.
- Starting a DPIA too late, after design decisions are fixed.
- Treating vendor assessment as a one-off instead of a lifecycle with monitoring and offboarding.
- Building controls before the inventory, so you don't know what you're protecting.
Frequently asked questions
What is the privacy operational life cycle?
It's the CIPM's model for running a programme: assess, protect, sustain and respond (Domains III–VI).
Why is the data inventory so important on the CIPM?
It underpins assessments, rights requests, breach response and records of processing, so it's often the correct "first step".
Are breach-notification deadlines tested on the CIPM?
The CIPM tests the incident-response process. Specific legal deadlines, such as the GDPR's 72 hours, appear mainly as context.
Who completes a DPIA in a privacy programme?
Usually the business or project owner completes it with input from IT, security and legal, and the privacy office or DPO reviews and advises. The CIPM rewards answers where privacy works through the business rather than doing everything itself.
How long do you have to respond to a CCPA request?
45 days, which can be extended once by another 45 days if the business tells the consumer within the first period.
Sources
Last reviewed: October 2026.