On this page
- Quick Reference (60 Seconds)
- What the Standard Actually Requires
- Why This Control Matters
- Scope and Applicability
- Key Definitions and Terminology
- Relationship to Other Clauses and Frameworks
- Detailed Implementation Guidance, The Seven Corrective-Action Moves
- Tools, Technologies, and Solutions
- Policy and Procedure Templates
- Risk Assessment and Treatment
- Audit and Compliance Checklist
- Metrics and KPIs
- Common Pitfalls and Audit Failures
- Illustrative Scenario 1: Failure, Vidya Healthtech and the Open-Loop Consent Nonconformity (Illustrative)
- Illustrative Scenario 2: Success, Setu Finance Builds a Privacy-Programme Corrective-Action Discipline (Illustrative)
- Multi-Framework Mapping
- Implementation Roadmap
- FAQ
- Industry-Specific Requirements
- Maturity Model
- Emerging Trends
- References and Further Reading
Quick Reference (60 Seconds)
| Attribute | Detail |
|---|---|
| Clause | ISO/IEC 27701:2025 Clause 10.2, Nonconformity and Corrective Action. The second sub-clause of the PIMS Improvement block (Clause 10), aligned to the Harmonized Structure shared by ISO/IEC 27001:2022 Clause 10.2, ISO 22301:2019 Clause 10.1, ISO 9001:2015 Clause 10.2 and ISO/IEC 42001:2023 Clause 10.2. Where Clause 9 produces findings and Clause 8 produces operational events, Clause 10.2 is where the organisation reacts to each detected nonconformity, controls and corrects it and deals with the consequences, evaluates the need to eliminate the root cause, implements corrective action where needed, reviews the effectiveness of that action, and feeds the changes back into the privacy risk register and the SoA, closing the PDCA "Act" loop on the PIMS. |
| What it asks for (paraphrase) | ISO/IEC 27701:2025 Clause 10.2 asks organizations to react to nonconformities and correct root causes. Six load-bearing ideas do the work. React to the nonconformity, acknowledge, control, start the formal loop. Take action to control and correct it, and deal with the consequences, containment, restoration to conformity, and consequence management (principal-notification despatch; the regulator-engagement clock; remediation offers to affected principals). Evaluate the need to eliminate the root cause, a deliberate, risk-based decision step; not every nonconformity warrants corrective action. Implement corrective action where the evaluation says so, corrective action is by definition root-cause oriented. Review the effectiveness of the corrective action, the most-omitted step. Update the privacy risk and opportunity thinking and the PIMS where needed, feed the changes back into Clause 6.1.2 / 6.1.3 (privacy risk register, RTP and SoA) and, where necessary, into the policy, the objectives, the documented information. |
| The marquee insight competitors miss | Most practitioner commentary treats Clause 10.2 as a generic ISO-management-system corrective-action obligation, "do a root-cause analysis, write a CAPA plan, close the finding". That under-uses the clause for a PIMS in four ways. First, in a PIMS the nonconformity surface is the privacy programme, the seven operational processes plus the Annex A.1 / A.2 / A.3 controls plus the SDF obligations under DPDP section 10. A PIMS nonconformity is the privacy programme failing, a consent record without the seven DPDP section 6 qualities; a rights-response SLA breach under section 13; a DPIA trigger missed under section 10; a sub-processor change-notification clock missed; a cross-border transfer without a current transfer-impact assessment; a breach-notification clock missed under section 8(6). The ten-family privacy-nonconformity catalogue is distinctive. Second, the line between 10.2, 6.3, 10.1 and Clause 8.x operational incident response is the most-confused demarcation in the Indian privacy landscape: a privacy breach is an operational incident handled under Clause 8.1 and the Annex A.3 incident-management controls; the gap the breach exposed is a nonconformity under 10.2; a planned redesign is a 6.3 planned change; an opportunity to improve is a 10.1 continual-improvement action. The four are distinct and not substitutable. Third, the DPDP enforcement overlay turns the loop into a regulator-facing statutory expectation: the Data Protection Board of India's section 27 to 32 powers (inquire, issue corrective directions, impose penalties up to two hundred and fifty crore rupees for section 8(5) failure and up to two hundred crore for sections 8(6) and 9; one hundred and fifty crore for section 10) mean an un-closed PIMS nonconformity is a penalty exposure, not just a certification risk. Fourth, the effectiveness check is the most-omitted step in the Indian growing-company segment, most NCR-to-CAPA cycles close at "action implemented" with no verification, which is the canonical Clause 10.2 finding the certification auditor writes. |
| Domain | Improvement (Clause 10). 10.2 sits beside 10.1 (continual improvement) as the reactive complement to 10.1's proactive stance. The Clause 10 block is where the PIMS learns from its own detections, 10.2 reacts to nonconformities; 10.1 raises the bar on what already works. Together they complete the PDCA "Act" loop on the PIMS. |
| What you must produce | (a) A Nonconformity and Corrective Action Policy (toolkit doc 01); (b) a Corrective Action Procedure (toolkit doc 02) operationalising the six-step loop; (c) a Nonconformity Register (toolkit doc 03), the single source of truth for every detected nonconformity; (d) a Root-Cause Analysis template (toolkit doc 09) using a defined method (5-Why, Ishikawa, fault-tree, IS / IS-NOT, bow-tie, FMEA); (e) an Effectiveness Evaluation template (toolkit doc 10); (f) a Corrective Action Tracker (toolkit doc 11) with per-action plan, owner, target date, evidence, effectiveness-check schedule and closeout; (g) the NC-to-Risk-and-SoA Update Link (toolkit doc 12); (h) the Nonconformity Incident Playbook (toolkit doc 08) for when an NC escalates (a regulator inquiry, a major breach, an SDF data-audit finding). |
| Typical owner | Top management owns the corrective-action discipline at the strategic level (Clause 5.1 lineage). The DPO / Privacy Lead owns it operationally, the Nonconformity Register, the per-NC owner assignment, the effectiveness-check programme. Business-process owners own the corrective action on their process area (the Head of Marketing owns the consent-flow corrective action; the Head of Customer Service owns the rights-response corrective action; the Head of Vendor Management owns the processor-chain corrective action). The Internal Audit Function (Clause 9.2) is a consultee that provides findings but does not own the corrective action, the independence rule. Top management receives the recurring-nonconformity pattern and the effectiveness-check dashboard at the management review (Clause 9.3) and signs off on the structural-treatment resources. |
| Minimum viable actions | (1) Stand up a single Nonconformity Register (toolkit doc 03) covering all sources; (2) classify each entry (conformity / observation / minor NC / major NC / opportunity for improvement); (3) run the six-step loop on each NC; (4) build the root-cause-analysis toolkit (5-Why, Ishikawa as the minimum; fault-tree and bow-tie for material NCs); (5) build the effectiveness-check programme (typically 30 / 60 / 90-day post-implementation review); (6) wire the recurring-nonconformity pattern into the management-review input under Clause 9.3 and the structural-treatment pipeline under Clause 6.3 / 10.1; (7) for SDFs, document the DPBI corrective-direction response procedure. |
| Maturity floor (L1) | A "spreadsheet-and-retraining" discipline: each finding gets a row in a spreadsheet; the corrective action for ninety percent of findings is "retrained staff" or "rewrote the procedure"; no RCA; no effectiveness check; no update to the risk register or the SoA; recurring findings year after year on the same operational area. The single most common Clause 10.2 audit nonconformity in the Indian growing-company segment. |
| Maturity target (L4 to L5) | A "privacy-programme corrective-action" PIMS: the Nonconformity Register is a first-class artefact covering the seven privacy-process families plus the Annex A controls plus the SDF obligations; the six-step loop is operational end-to-end with documented decisions at each step; the RCA uses the method appropriate to the NC (5-Why for simple, fault-tree for complex, bow-tie for high-consequence); the effectiveness-check programme runs on a 30 / 60 / 90-day cadence; the recurring-nonconformity pattern triggers structural treatment under Clause 6.3 or 10.1; the NC-to-risk-and-SoA update link is wired; the DPBI corrective-direction response procedure is drilled; the discipline demonstrably drives every Clause 9.3 decision and every Clause 6.1 risk-register update. |
| Audit red flag | A Register with ninety percent of corrective actions recorded as "retrained staff" or "rewrote procedure" (the shallow-RCA failure); a finding in three consecutive cycles on the same operational area (the recurring-NC failure, the recurrence is itself a major NC against Clause 10.2); a finding closed at "action implemented" with no effectiveness check (the open-loop failure); a major NC with no update to the privacy risk register or the SoA (the no-update failure); a finding from 9.2 internal audit with the same person writing both the finding and the corrective action (the independence failure); a regulator-engagement that produced no entry in the Register (the source-coverage failure); a breach under Clause 8.x with no NC raised against the underlying control gap (the demarcation failure). |
| Time to implement (first cycle) | Growing companies (50 to 250 staff): six to twelve weeks for the first defensible cycle. Mid-sized (250 to 2,000): twelve to twenty weeks, usually requiring integration with the enterprise GRC platform, the multi-process-owner RACI and the recurring-pattern-driven structural-treatment pipeline. Multi-entity enterprise or SDF under DPDP section 10: six to nine months, integrated with the enterprise corrective-action function, the SDF section 10 remediation cycle and the multi-jurisdiction enforcement ecosystem. |
| Related clauses | 4.1, 4.2, 4.4 (context, requirements, the PIMS whose NCs 10.2 addresses); 5.1, 5.3 (leadership owns the discipline; roles assigned); 6.1.2 / 6.1.3 (the privacy risk register, RTP and SoA updated by 10.2, the load-bearing update step); 6.2 (privacy objectives may be revised by 10.2); 6.3 (planned changes, 6.3 is the planned PIMS change; 10.2 is the reactive PIMS change); 7.1 to 7.5 (resources, competence on RCA methods, awareness, communication, documented information, the Register, RCA worksheets, effectiveness-check records, closeout); 8.1 to 8.3 (operational processes, the seven privacy processes whose NCs 10.2 addresses; the operational incident-response demarcation; the risk-assessment and SoA updated by 10.2); 9.1 (self-detection source); 9.2 (independent-detection source); 9.3 (management review, the forum where the recurring-NC pattern and the effectiveness dashboard are considered); 10.1 (continual improvement, the proactive sibling). Annex A.1 / A.2 / A.3 (control surfaces whose NCs 10.2 addresses). 10.2 is the closure engine every Clause 9 finding and every Clause 8 event hangs from. |
| Critical Indian context-bearing instruments the corrective-action discipline must reflect | DPDP Act 2023 (Act 22/2023), sections 8(5) reasonable security safeguards, 8(6) breach notification (the dual-clock: CERT-In six hours + DPDP without delay plus a seventy-two-hour detailed report via Rule 7), 9 children, 10 SDF obligations, 11 to 14 rights, 16 cross-border negative list, 18 Data Protection Board of India, 27 to 32 the Board's inquiry, corrective-direction and penalty powers, 33 + Schedule the penalty maxima. DPDP Rules 2025 (notified 13 November 2025), Rule 7; SDF designation thresholds; Consent Manager registration conditions; grievance-redressal response periods. CERT-In Directions 20(3)/2022-CERT-In (28 April 2022, the six-hour clock). Sector regulators, RBI (Storage of Payment System Data 2018; Digital Lending 2022; Cybersecurity Directions 2026); SEBI Cybersecurity and Cyber Resilience Framework 20 August 2024 (the "Learn" function is the sectoral restatement of 10.2); IRDAI Information and Cyber Security Guidelines 2023 (24 April 2023). Constitutional, Puttaswamy (2017) 10 SCC 1; Aadhaar (2019) 1 SCC 1. Companies Act 2013 sections 134(3)(n) and 177. Full citations in Section 24. |
If you only read one thing: Clause 10.2 is where the PIMS reacts to detected nonconformities and corrects their root causes so they do not recur. A 10.2-conformant PIMS is one in which every detected nonconformity, from 9.1 monitoring, 9.2 internal audit, 9.3 management review, Clause 8 operational events, complaints or regulator engagements, is logged in a Nonconformity Register, classified, owned, contained, corrected, root-caused, treated with corrective action, verified for effectiveness, closed out, and fed back into the privacy risk register and the SoA. Not a generic "retrain staff and rewrite the document" loop; a six-step closed-loop discipline with documented decisions at each step and a recurring-nonconformity pattern that triggers structural treatment under Clause 6.3 or Clause 10.1. The certification auditor will walk two or three sample nonconformities end-to-end through the loop; the Data Protection Board of India will, after a complaint or a breach, ask which nonconformities had been detected on the affected operational area, what the root cause was, and what the corrective action delivered. Get 10.2 wrong and however strong the Clause 8 operations and the Clause 9 detection are, the PIMS cannot demonstrate that it learns from its own detections, which under DPDP section 8(5) reasonable security safeguards and GDPR Article 32(1)(d) regular testing and evaluating is itself a nonconformity.
What the Standard Actually Requires
The paraphrased requirement
ISO/IEC 27701:2025 Clause 10.2 asks organizations to react to nonconformities and correct root causes. Six load-bearing ideas sit inside that paraphrase, and the certification auditor tests each separately.
The organisation must react to the nonconformity and take action to control and correct it, and deal with the consequences. Reacting is the immediate acknowledgement. Controlling is containment, stopping the bleeding, isolating the affected processing activity, preventing further harm to principals. Correcting is restoration to conformity, fixing the symptom (the consent record without the seven qualities; the rights-response SLA breach; the DPIA trigger missed). Dealing with the consequences is the privacy-specific dimension that distinguishes a PIMS nonconformity from a generic management-system nonconformity: the consequence may be harm to principals (a delayed rights response; an un-erased record; an unlawful cross-border transfer), harm to the regulator relationship (a missed clock; an incomplete filing), or harm to the controller-processor chain (a sub-processor change that should have been notified). Each consequence has its own remediation, the principal-notification despatch, the regulator-engagement clock, the remediation offer.
The organisation must evaluate the need for action to eliminate the root causes. "Evaluate the need" is the most-misunderstood element of Clause 10.2, organisations often treat it as a checkbox and jump to implementation. The actual requirement is a defensible, risk-based decision: is the root cause likely to recur elsewhere (the flawed consent template is used across twelve processing activities, fixing one without fixing the template guarantees eleven future nonconformities); what is the risk of recurrence against the cost and impact of the corrective action; is there a more fundamental PIMS change needed (policy, scope, objective); or is the right decision "no action beyond containment" because the NC was a one-off and the risk is negligible. All four answers are legitimate; the requirement is to have asked the question and to have an evidence trail for the answer.
The organisation must implement the corrective action needed. Corrective action is by definition root-cause oriented. The distinction between correction (the day-of symptom fix, "I fixed this consent record") and corrective action (the systemic fix, "I redesigned the consent flow so this class of error cannot recur") is load-bearing; a Nonconformity Register full of corrections and no corrective actions is the canonical shallow-RCA failure.
The organisation must review the effectiveness of the corrective action. This is the step most organisations omit and most auditors probe. After implementing the action, the organisation must verify whether it actually worked, did the nonconformity stay closed; did the root cause disappear; did the change have unintended side effects on other PIMS processes. The effectiveness check is typically a 30 / 60 / 90-day post-implementation review with documented evidence; for material NCs, a follow-on internal audit under Clause 9.2 at the next cycle.
The organisation must update the privacy risk and opportunity thinking and the PIMS where needed. Corrective action often changes the risk picture, a previously unidentified risk is now on the register; a control gap is now closed (the SoA control is now operating at higher maturity); a new opportunity to improve emerges. The organisation must feed those updates back into Clause 6.1.2 (privacy risk assessment) and 6.1.3 (privacy risk treatment and SoA), and where necessary into the documented information under Clause 7.5.
The organisation must retain documented information as evidence of the nature of the nonconformities and any actions taken, and the results of any corrective action. The evidence set comprises the Nonconformity Register; the RCA worksheets; the corrective-action plans; the implementation evidence; the effectiveness-check records; the closeout; the risk-and-SoA update trail; the management-review cross-reference. The Register is the certification auditor's first-stop artefact in the Stage 2 examination of Clause 10.2; its absence is a 10.2 finding even when individual corrective actions have been implemented.
The privacy nonconformity catalogue, the load-bearing 10.2 artefact competitors miss
Most practitioner commentary discusses Clause 10.2 in generic ISO-management-system terms, "find a gap, root cause it, fix it, verify the fix". That framing leaves the most important question unanswered for a PIMS: what counts as a privacy nonconformity? The Singahi privacy nonconformity catalogue (toolkit doc 03 Section 4) operationalises the answer. The catalogue has ten families; the first seven mirror the seven privacy-process audit subjects under Clause 9.2, and the last three are the PIMS-specific additions.
Family 1, Consent and notice nonconformities. The consent record is missing one or more of the seven DPDP section 6 qualities (free, specific, informed, unconditional, unambiguous, clear affirmative action, easily withdrawable). The notice content under DPDP section 5 and GDPR Articles 12 to 14 is incomplete or not in the prescribed language. The withdrawal mechanism is broken or not as-easy-to-give. The Consent Manager integration under DPDP section 2(1)(g) is not interoperable or not revocable. Annex A.1.2.3 and A.1.2.4 are not operating as documented.
Family 2, ROPA and record-keeping nonconformities. The ROPA under Annex A.1 and GDPR Article 30 does not reconcile with operational reality. A new processing activity was launched without a ROPA entry; a retired activity was not removed; the periodic reconciliation was missed; the customer-of-a-processor ROPA exchange under Annex A.2 was incomplete.
Family 3, Data-principal rights-fulfilment nonconformities. The rights operation under DPDP sections 11 to 14 and GDPR Articles 15 to 22 missed a prescribed response period (the section 13 Grievance Officer period; the GDPR Article 12(3) one-month period). A rights request was incomplete (the access response did not include the recipients of disclosure; the erasure response did not flow through to the processor chain). The nomination-handling workflow under DPDP section 14 failed. The ticketing system lost a rights-request ticket.
Family 4, DPIA-pipeline nonconformities. The DPIA pipeline under DPDP section 10 (for SDFs), GDPR Article 35 and ISO/IEC 29134:2017 did not fire on a trigger. A completed DPIA did not meet the Article 35(7) / 29134 structure. The prior-consultation register under GDPR Article 36 was not maintained. The review-on-change discipline was not applied. Annex A.1.2.5 is not operating as documented.
Family 5, Processor and sub-processor chain nonconformities. A processor was onboarded without due diligence under Annex A.2 and GDPR Article 28. A DPA did not include all the Article 28(3) mandatory clauses. A sub-processor change-notification under Annex A.2.5.9 was missed or late. An infringing instruction from a controller was not handled under Annex A.2.2.5. The audit-cooperation cycle under Article 28(3)(h) was not honoured. The deletion-certification intake was incomplete.
Family 6, Cross-border transfer nonconformities. A cross-border transfer under DPDP section 16 and GDPR Chapter V was made without a documented transfer basis (the negative-list screen under DPDP; the adequacy / safeguards / derogations analysis under GDPR). A transfer-impact assessment under Annex A.1.5.2 was missing or stale (post-Schrems II, CJEU C-311/18, 16 July 2020). Supplementary measures lapsed. The transfer register was incomplete.
Family 7, Breach-response nonconformities. A personal-data breach triggered the breach-response procedure but the dual-clock was missed (CERT-In six hours under Directions 20(3)/2022-CERT-In; DPDP without delay plus a seventy-two-hour detailed report via Rule 7). The principal notification under DPDP section 8(6) was delayed or incomplete. The breach-register entry was missing the Rule 7 intimation content. The sector-regulator clock was missed (RBI six hours; SEBI six hours; IRDAI twenty-four to seventy-two hours). Annex A.3 incident-management controls are not operating as documented.
Family 8, Privacy-by-design nonconformities. A new processing activity, system or feature was launched without a privacy-by-design review under Annex A.1.4 and GDPR Article 25. The default settings were not privacy-protective. Data minimisation was not applied. The pseudonymisation option was rejected without documentation.
Family 9, Children-data nonconformities. A processing activity involving children's data under DPDP section 9 did not apply verifiable parental consent. Behavioural monitoring or targeted advertising directed at children was not blocked. The age-assurance operation failed. The GDPR Article 8 child-consent threshold was not applied where applicable.
Family 10, SDF-obligation nonconformities. A Significant Data Fiduciary under DPDP section 10 had a vacant DPO role (the DPO must be based in India and accountable to the board). An SDF DPIA under section 10 was not completed within 12 months of the last one. The periodic independent data audit was not conducted. The algorithmic-software review was not conducted where the processing involved AI / statistical inference.
The ten families are not mutually exclusive. A single incident can engage several, a ransomware breach at a sub-processor that exposed the controller's principals engages families 5 (the sub-processor chain), 7 (the breach response), 6 (the cross-border transfer), 2 (the ROPA reconciliation) and 8 (the privacy-by-design dimension) simultaneously. Each family has its own corrective-action pathway; when an event engages several at once, each has a clean root-cause analysis and a clean corrective-action plan.
The line between 10.2, 6.3, 10.1 and Clause 8.x operational incident response
The Indian privacy practitioner ecosystem constantly conflates four distinct PIMS loops. The demarcation is load-bearing; getting it wrong produces duplicate cycles (wasted effort) or open loops (a nonconformity).
Clause 8.x operational incident response handles the operational event. A personal-data breach is an operational incident under Clause 8.1 operational planning and control and the Annex A.3 incident-management controls. The breach-response procedure runs detect, contain, eradicate, recover, notify (the dual-clock, CERT-In six hours + DPDP without delay plus a seventy-two-hour detailed report), communicate. The breach register captures the operational event. The procedure answers "what happened, who is affected, what we did, who we told".
Clause 10.2 handles the management-system nonconformity the event exposed. The same breach may expose a control gap, the access-control weakness that let the attacker in; the encryption gap that turned a minor incident into a major breach; the DPIA that should have flagged the risk. Each gap is a nonconformity under 10.2. The Register captures the management-system gap. The 10.2 loop answers "why did our PIMS let this happen, what root cause produced the gap, what corrective action eliminates the root cause, did the corrective action work".
Clause 6.3 handles planned changes to the PIMS. A planned redesign of the consent flow, a planned migration to a new cross-border transfer mechanism, a planned onboarding of a new processor class, these are Clause 6.3 planned changes, not Clause 10.2 corrective actions. The trigger differs: 6.3 is initiated by the organisation's own change pipeline; 10.2 is initiated by a detected nonconformity. The output may look similar (a new procedure; a new control; a new documented-information artefact), but the loop is different.
Clause 10.1 handles continual improvement. An opportunity to improve the PIMS that is not tied to a detected nonconformity, a privacy-by-design enhancement, a control maturity upgrade, an automation opportunity, is a Clause 10.1 continual-improvement action. The trigger differs: 10.2 is reactive; 10.1 is proactive.
The four loops share the same output medium but answer different questions. The certification auditor tests the demarcation by asking "which loop did this finding go through, and why that one"; an answer that says "the breach was handled by the breach-response procedure" without a Register entry is the canonical demarcation failure.
The line between 10.2, the SDF data-audit findings and the DPBI section 27 corrective direction
The Indian privacy enforcement ecosystem has three external-driver dimensions that engage Clause 10.2.
A certification-body nonconformity at surveillance or recertification is the standard external driver. The certification body issues a major or minor NC; the organisation enters it in the Register; the six-step loop runs; the corrective-action evidence is submitted within the prescribed window (typically forty-five to ninety days for a minor NC; a major NC requires a focused follow-up audit).
A DPBI section 27 corrective direction is the statutory external driver. Under DPDP Act 2023 sections 27 to 32, the Data Protection Board of India may, after an inquiry, issue corrective directions to a Data Fiduciary or Data Processor, directions to take steps to comply, to cease processing, to transfer or delete data, or to remedy the violation. A corrective direction engages Clause 10.2 because the direction is, in PIMS terms, a regulator-issued nonconformity finding; the six-step loop runs on the direction itself (react, acknowledge within the Board's timeline; control and correct, take the operational steps; evaluate the need, root-cause the underlying violation; implement corrective action, fix the systemic gap; review effectiveness, verify to the Board's satisfaction; update risk and SoA). The Board's section 33 + Schedule penalty powers (up to two hundred and fifty crore rupees for section 8(5) failure; up to two hundred crore for sections 8(6) and 9; one hundred and fifty crore for section 10) make the 10.2 loop on a Board direction a high-stakes statutory exercise.
The SDF's independent data audit and DPIA findings are the SDF-specific external driver. Under DPDP section 10 and Rule 13, an SDF must appoint a DPO based in India, carry out a DPIA and an independent data audit every 12 months, and verify its algorithmic software (the algorithmic-software review); Rule 13(2) requires the significant observations of the DPIA and the audit to be reported to the Board. Each gap the audit finds engages Clause 10.2 because it is a nonconformity against the section 10 obligations; the six-step loop runs on each gap. The Act has no separate SDF "remediation order": if the Board acts, it uses its inquiry and direction powers.
The three external drivers answer different questions: a certification-body NC asks "does the PIMS conform to ISO/IEC 27701:2025"; a DPBI corrective direction asks "does the Data Fiduciary comply with the DPDP Act"; an SDF data-audit finding asks "does the SDF meet the section 10 enhanced obligations". A mature Indian PIMS treats all three as inputs to the same Register; the source-tag dimension distinguishes the cycle each goes through.
What the standard does NOT require (the demarcation)
- 10.2 does not require corrective action on every detected nonconformity. The clause says "evaluate the need", a risk-based decision is allowed. A minor NC in a low-criticality area may legitimately be deferred or accepted; a major NC in a high-criticality area cannot. The decision must be defensible, documented and risk-based.
- 10.2 does not require the same person who detected the nonconformity to own the corrective action. The independence rule (ISO/IEC 17021-1:2015 and ISO 19011:2018 lineage) says the internal auditor who wrote the finding should not own the corrective action. The business-process owner owns it; the auditor verifies.
- 10.2 does not require preventive action as a separate step. The Harmonized Structure folded prevention into Clause 6.1 (risks and opportunities) and 10.1 (continual improvement). The CAPA acronym persists in industry usage, but the "P" is handled by Clause 6.1.2.
- 10.2 does not require a specific root-cause-analysis method. 5-Why, Ishikawa, fault-tree, IS / IS-NOT, bow-tie and FMEA are all acceptable. The requirement is to use a defined method, apply it correctly, and record the worksheet.
- 10.2 does not require every corrective action to be successful. A corrective action that does not deliver the intended outcome is information, it tells the organisation the root cause was misidentified or the action inadequate. The discipline is to learn and re-enter the loop.
- 10.2 does not require a tool. A spreadsheet-based Nonconformity Register is acceptable for the first cycle. The test is whether the Register, the RCA worksheets, the corrective-action plans, the effectiveness-check records and the closeout exist and are current.
- 10.2 does not require the DPO to own the corrective-action function. The DPO is typically the operational owner of the discipline; the corrective actions themselves are owned by the business-process owners.
- 10.2 does not require zero nonconformities. A PIMS with zero findings across multiple cycles is itself a red flag. The health signal is the closure rate, the effectiveness rate and the recurring-pattern rate, not the absolute count.
What auditors actually check
The certification auditor's Clause 10.2 examination has seven predictable moves. First, open the Nonconformity Register, does it exist as a distinct artefact; does it cover all sources (9.1, 9.2, 9.3, Clause 8 operational events, complaints, regulator engagements); is it current; is each entry classified and owned. Second, pick two or three sample nonconformities and walk them end-to-end through the six-step loop, the reaction, the containment, the correction, the consequences-handling, the root-cause evaluation, the corrective-action implementation, the effectiveness check, the closeout, the risk-and-SoA update. Third, test the root-cause analysis quality, read the worksheet, check whether the method was applied correctly (did 5-Why go five layers deep, or did it stop at layer two; did the Ishikawa cover the people / process / technology / external dimensions). Fourth, test the effectiveness-check discipline, is there a defined cadence; is the review documented; is the verifier independent of the implementer; is the closeout signed off. Fifth, test the recurring-nonconformity pattern, has any NC appeared in three consecutive cycles on the same operational area; if so, was the structural treatment under Clause 6.3 or 10.1 engaged. Sixth, test the demarcation, pick a recent breach or incident and trace whether the management-system gap entered the Nonconformity Register (the demarcation failure is a 10.2 NC). Seventh, for SDFs, test the DPBI-corrective-direction response procedure, is it drilled; does the procedure flow into the 10.2 Register or does it sit outside.
Why This Control Matters
The "open loop" failure pattern
Most PIMS failures that reach the public record are not detection failures, the problem was seen, escalated and documented, they are closure failures. The organisation detected the gap, contained it, declared victory and never closed the root-cause loop. Three to twelve months later, the same gap resurfaces in a different team, a different processing activity or a different incident. Regulators and certifiers treat recurrence as the single most damning evidence that the management system is not actually a system.
The pattern is reliable across the Indian privacy record. The publicly discussed incidents at Indian consumer-facing firms (Juspay approximately thirty-five million records in 2021, publicly acknowledged; BigBasket approximately twenty million records alleged in 2020; Air India and SITA approximately four-and-a-half million customers affected by the SITA breach disclosed in 2021; MobiKwik contested allegations, denied by the company) all carried post-incident examinations that tested whether the same operational area had been audited, what the findings were, and what corrective action was taken. An empty Nonconformity Register on a material area is the post-incident equivalent of a major nonconformity. The Data Protection Board of India, once it is fully operational through 2026 and 2027, is expected to apply the same recurrence test, a Data Fiduciary whose corrective-action loop did not close on a prior finding will face a much stiffer section 27 to 32 inquiry and a much higher section 33 + Schedule penalty exposure than one whose loop closed but the underlying risk materialised anyway.
The pattern has its own shorthand in audit culture: the recurring-finding-without-structural-treatment failure. A finding appears in two consecutive cycles; the corrective action under 10.2 is repeated (retrain staff; rewrite the procedure); the third cycle finds the same gap again. By the third cycle, the recurrence is itself a major NC against Clause 10.2, cascading into a Clause 9.3 management-review finding (top management did not resource the structural treatment) and possibly a Clause 5.1 leadership finding (the leadership did not ensure the PIMS was working). The structural treatment under Clause 6.3 (planned change) or Clause 10.1 (continual improvement) is the load-bearing off-ramp from the cycle.
The Indian regulatory weight behind 10.2
In India, Clause 10.2 carries a regulatory weight that goes beyond the ISO standard because the DPDP Act 2023 and the DPDP Rules 2025 impose affirmative corrective-action obligations that engage exactly when the organisation is a Data Fiduciary. The DPBI section 27 corrective-direction power is the marquee Indian statutory corrective-action obligation, the Board may direct a Data Fiduciary to take steps to comply, to cease processing, to transfer or delete data, or to remedy a violation. A corrective direction is, in PIMS terms, a regulator-issued nonconformity finding; the 10.2 loop runs on the direction. The section 33 + Schedule penalty regime sets the financial stakes: up to two hundred and fifty crore rupees for section 8(5) failure (reasonable security safeguards, which the Board can read to include the corrective-action discipline); up to two hundred crore rupees for sections 8(6) (breach notification) or 9 (children); one hundred and fifty crore rupees for section 10 (SDF obligations). The DPDP Rules 2025 prescribe the operational timelines (Rule 7, intimation without delay and a seventy-two-hour report) and the SDF designation thresholds, breach of which engages the 10.2 loop.
The lineage is the wedge. K.S. Puttaswamy v. Union of India, (2017) 10 SCC 1 (judgment delivered 24 August 2017 by a nine-judge Bench of the Supreme Court) declared the right to privacy, including informational privacy, a fundamental right under Articles 14, 19 and 21 of the Constitution. The Aadhaar judgment (2019) 1 SCC 1 set the proportionality test. The DPDP Act was enacted 11 August 2023. The DPDP Rules 2025 were notified 13 November 2025 with phased commencement. ISO/IEC 27701:2025 was published 14 October 2025, twelve days before the DPDP Rules were notified. The corrective-action discipline is where the legal landscape enters the PIMS closure frame: the 10.2 loop on a privacy nonconformity is the operational mechanism by which a Data Fiduciary demonstrates to the Board that it has remedied a violation, and to its principals that it has prevented recurrence.
The sector-regulator overlay adds corrective-action obligations on top of the DPDP. The RBI Cybersecurity Directions 2026 (31 July 2026) make the board and senior management accountable for the closure of supervisory findings, a bank whose RBI inspection raises deficiencies and does not close them within the agreed timeline faces supervisory action including restrictions on the digital products it can launch. The SEBI Cybersecurity and Cyber Resilience Framework (20 August 2024) structures the regime around six operational functions: Identify, Protect, Detect, Respond, Recover, and Learn. The "Learn" function is the sectoral restatement of Clause 10.2, a SEBI-regulated entity must turn incidents, exercises and audit findings into documented corrective actions, tracked to closure, and reported back to the regulator. The IRDAI Information and Cyber Security Guidelines 2023 (24 April 2023) require insurers to submit annual compliance reports within ninety days of financial year-end, including the status of corrective actions from prior-year findings. CERT-In Directions 20(3)/2022-CERT-In (28 April 2022) create a continuous stream of incidents, each reportable incident is a candidate nonconformity against the underlying control. The Companies Act 2013 section 134(3)(n) requires the Board's Report to include a statement on the development and implementation of a risk-management policy; the Audit Committee under section 177 evaluates whether prior findings were closed, un-closed findings across cycles are a board-reportable risk.
The cost of an open loop, by sector
The cost of a Clause 10.2 failure breaks down into four bands. Direct DPDP penalty exposure for an organisation whose corrective-action loop is absent or ineffective, and where the absence is exposed after a complaint or a breach, can engage the section 33 + Schedule maxima. The Board has explicit authority under the DPDP to consider the organisation's corrective-action posture as part of the reasonable-security-safeguards assessment. Indirect regulatory consequences are larger and slower, a 10.2 failure cascades through the management review (9.3), the continual improvement (10.1) and every other Clause 10 sub-clause because the closure engine is broken. Commercial cost is significant, a recurring privacy failure in the same operational area erodes customer trust and, for B2B firms, becomes a contract-renewal risk and an RFP-loss risk. Recoverable; entirely avoidable with a working 10.2 discipline.
Scope and Applicability
By organisation size
Growing companies (50 to 250 staff). A compact corrective-action discipline: a single Nonconformity Register (a structured spreadsheet is sufficient); the six-step loop run on each NC; the root-cause-analysis toolkit using 5-Why and Ishikawa as the minimum; the effectiveness-check at thirty days post-implementation. The DPO (or the Privacy Lead) is typically the operational owner; the corrective-action implementation sits with the business-process owner. The first cycle is deliverable in six to twelve weeks of internal effort.
Mid-sized (250 to 2,000 staff). A more granular discipline: a Nonconformity Register inside a GRC platform or a structured database; the six-step loop with decision rights documented at each step; the root-cause-analysis toolkit covering 5-Why, Ishikawa, fault-tree analysis and the bow-tie for material NCs; the effectiveness-check at 30 / 60 / 90 days; the recurring-nonconformity pattern triggering structural treatment under Clause 6.3 or 10.1. The DPO owns the discipline operationally; a Corrective-Action Board (the DPO, the CISO, the Head of Legal, the Head of Internal Audit, the top business-process owners) meets monthly to review the open-NC dashboard. The first cycle typically takes twelve to twenty weeks.
Multi-entity enterprise (2,000+ staff or multi-jurisdiction). A layered corrective-action architecture: an enterprise GRC platform with a CAPA module integrated with the audit-management, risk-management and incident-management modules; multiple RCA methods in regular use; statistical trend analysis; predictive KRIs; the integration with the enterprise risk and internal-audit functions; quarterly executive dashboards; the integration with the SDF section 10 remediation cycle and the multi-jurisdiction enforcement ecosystem. Typically six to nine months for the first cycle.
By PIMS role
PII controller (Data Fiduciary) primary. The corrective-action discipline leads with the seven privacy-process families and the Annex A.1 controls. The Nonconformity Register's load-bearing entries are the controller-side nonconformities, consent quality, rights response, DPIA pipeline, cross-border transfer, breach notification.
PII processor (Data Processor) primary. The corrective-action discipline leads with the Annex A.2 controls, the customer-agreement nonconformity, the infringing-instruction-handling nonconformity, the sub-processor-chain nonconformity, the audit-cooperation nonconformity. The seven privacy-process families apply in the processor-modified form (the consent operation becomes the consent-handling operation on the customer's behalf; the rights operation becomes the rights-cooperation operation).
Both controller and processor. The most common shape for Indian growing companies. The Nonconformity Register covers both Annex A.1 and Annex A.2 controls; the corrective-action discipline drives closure across both surfaces and at the boundary (joint-controller arrangements; processor-acting-as-controller drift).
By sector
Sector-specific overlays are addressed in Section 21 (BFSI, Healthcare, IT-ITeS, E-commerce, Edtech, Manufacturing), along with the cross-sector patterns (the dual-regulator corrective-action overlay, the SDF section 10 remediation overlay, the DPBI corrective-direction response pattern).
Key Definitions and Terminology
Nonconformity (NC). The non-fulfilment of a requirement. In the PIMS, an NC is any gap between what ISO/IEC 27701:2025 (or the organisation's own PIMS documentation) requires and what is actually happening.
Major nonconformity. An NC showing a significant breakdown of the PIMS, total absence of a required process, systemic failure across multiple areas, or a recurrence of a previously closed NC. Major NCs at certification audits result in conditions, suspension or non-recommendation.
Minor nonconformity. A single or isolated lapse that does not (yet) indicate systemic failure. Minor NCs typically need a corrective-action plan within a defined window (often sixty to ninety days) and verification at the next surveillance.
Observation / opportunity for improvement (OFI). Not a nonconformity. A suggestion that the organisation could improve. OFIs feed Clause 10.1, not 10.2.
Conformity. Fulfilment of a requirement, the default state the PIMS is supposed to be in.
Corrective action. Action to eliminate the cause of a detected nonconformity and prevent recurrence. By definition root-cause oriented.
Correction. Immediate action to fix the symptom. Correction is what you do on the day; corrective action is what you do to make sure it does not happen again.
Preventive action. Action to eliminate the cause of a potential nonconformity. The Harmonized Structure folds prevention into Clause 6.1 (risks and opportunities) and 10.1 (continual improvement); the term is not a standalone requirement in 27701:2025. The CAPA acronym persists in industry usage, but the "P" is handled by Clause 6.1.2 privacy risk assessment.
Containment. Action to limit the spread or impact of the nonconformity while the root cause is being investigated.
Root cause. The fundamental reason a nonconformity occurred, the factor that, if removed or changed, would prevent recurrence. Identifying the root cause is the central job of Clause 10.2.
Root-cause analysis (RCA). A structured method for identifying root causes. Common methods: 5-Why (iterative "why", five layers deep); Ishikawa / fishbone (causes by people, process, technology, external); fault-tree analysis (top-down deduction); the IS / IS-NOT matrix; the bow-tie analysis (threats, top events, consequences, barriers); FMEA.
Effectiveness check (verification of effectiveness). The post-implementation review that confirms the corrective action eliminated the root cause and the NC has not recurred.
Closure. The formal state where the NC is closed in the Register after the effectiveness check confirms success.
Recurrence. The reappearance of the same (or substantially similar) NC after closure. Recurrence is definitive evidence that the prior corrective action was ineffective, and itself becomes a new, more serious NC against Clause 10.2.
NCR (Nonconformity Report). The documented record of a single nonconformity and its lifecycle.
CAPA (Corrective and Preventive Action). The industry term for the formal action plan arising from RCA. In 27701:2025, "CAPA" usually means "corrective action plan" only.
NC Register / CAPA log. The single source of truth listing all open and closed NCs, with their lifecycle states. Required as documented information under Clause 10.2.
Loop closure. The completed end-to-end run of react → control-and-correct → evaluate-the-need → corrective action → effectiveness check → close.
Lesson learned. The generalised insight from a closed NC that, when fed back into the PIMS, prevents the same class of NC elsewhere, the multiplier effect that turns one closed NC into a system-wide improvement.
Trend / recurring-NC theme. A pattern across multiple NCRs pointing to a deeper systemic cause. Trends are the most important Clause 9.3 management-review input from the 10.2 process.
Privacy nonconformity. The PIMS-specific flavour of nonconformity, a gap between the PIMS requirements (27701:2025 clauses + Annex A controls + the DPDP obligations + GDPR where applicable + sector-regulator rules) and operational reality. The ten privacy-nonconformity families are the load-bearing taxonomy.
NC-to-risk-and-SoA update link. The artefact that operationalises the "update risks and opportunities and the PIMS" step, each closed NC produces a risk-register update and, where the corrective action changed the control surface, a SoA update.
DPBI corrective direction. A direction issued by the Data Protection Board of India under DPDP Act 2023 sections 27 to 32 after an inquiry, directing a Data Fiduciary or Data Processor to take steps to comply, to cease processing, to transfer or delete data, or to remedy a violation. In PIMS terms, a regulator-issued nonconformity finding.
SDF data-audit finding. A gap in the SDF obligations found by the independent data auditor (DPDP section 10(2)(b)) or in the SDF's DPIA. Rule 13(2) requires the significant observations to be reported to the Board.
The seven-privacy-process nonconformity families. The Singahi taxonomy mirroring the seven privacy-process audit subjects under Clause 9.2, consent and notice; ROPA; rights; DPIA pipeline; processor and sub-processor chain; cross-border transfer; breach response. Plus three PIMS-specific additions (privacy-by-design, children-data, SDF obligations).
Relationship to Other Clauses and Frameworks
Clause 10.2 is the consumer and closer of the PIMS's findings pipeline. It receives inputs from most other clauses and feeds outputs back into them.
Inside ISO/IEC 27701:2025, the evidence flow into 10.2
| Source clause | What it produces | What 10.2 does with it |
|---|---|---|
| 9.1 Monitoring, measurement, analysis and evaluation | KPI misses (consent-quality scores, rights-response SLA adherence, breach-clock adherence, DPIA-trigger latency), trend reports, self-detection results | Any KPI breach or sustained trend in the wrong direction is a candidate NC; logged and processed |
| 9.2 Internal audit | Audit findings: NCs and OFIs. The primary independent-detection source | NCs go into the Register; OFIs go to 10.1. Independence preserved (audit recommends, does not own the fix) |
| 9.3 Management review | Top-management decisions, follow-up actions, queries raised by the review | Review actions become tracked NCs; the review also consumes the 10.2 dashboard (open NCs, aging, recurrence, effectiveness) |
| 8.1 Operational planning and control | Operational incidents, the seven privacy processes (consent, ROPA, rights, DPIA, processor, transfer, breach) producing operational events | Each operational event that exposes a control gap becomes a candidate NC under 10.2 |
| 8.2 Privacy risk assessment | Outdated risk assessment, missed review cadence, risk found to be under-rated | Risk-assessment gaps feed NC pipeline; conversely, 10.2 corrective actions update 8.2 |
| 8.3 Privacy risk treatment | Risk-treatment failures; SoA control marked applicable but not implemented; residual-risk acceptance stale | Risk-treatment failures become NCs; conversely, 10.2 corrective actions update 8.3 (the load-bearing update step) |
| 6.1.2 / 6.1.3 Risks and opportunities | Risk-register updates; RTP and SoA changes; risk-treatment failures | Risk-treatment failure becomes an NC; conversely, 10.2 corrective actions feed back into 6.1 (the load-bearing update step) |
| 6.3 Planning of changes | Planned PIMS changes (the demarcation, 6.3 is planned change, 10.2 is reactive change) | 6.3 outputs may look similar to 10.2 outputs but the trigger differs; the demarcation is enforced |
| 7.5 Documented information | Document-control findings (out-of-version docs, missing approvals, lost records) | Doc-control NCs feed 10.2; corrective actions often change documented information |
| 7.2 / 7.3 Competence and awareness | Training gaps, awareness-survey failures | Competence NCs feed 10.2; retraining is sometimes (but only sometimes) the right corrective action |
| 5.1 / 5.3 Leadership and roles | Governance gaps, role-clarity issues | Leadership-level NCs are serious; their closure is closely watched |
| External sources | Certification / surveillance audit findings, customer audits, DPBI inquiries and corrective directions, sector-regulator inspections (RBI / SEBI / IRDAI / CERT-In), SDF independent-data-audit findings, supplier NCs, customer complaints, public incidents, whistleblower reports | All are valid NC inputs and must be in the same Register |
The decision flow out of 10.2
| Output | Destination | Why |
|---|---|---|
| Updated privacy risk register | Clause 6.1.2 | A corrective action often closes a risk, opens a new one, or changes a risk rating |
| Updated SoA | Clause 8.3 | A corrective action often changes the control surface, a control marked applicable is now implemented at higher maturity; a control gap is closed |
| Updated PIMS documentation | Clause 7.5 / 8.x | Policies, procedures, process criteria and templates change as corrective actions are implemented |
| Updated scope / policy / objectives | Clauses 4.3 / 5.2 / 6.2 | Major NCs can trigger scope, policy or objective changes |
| Updated privacy risk assessment | Clause 8.2 | A control gap that emerged in a NC may indicate the risk assessment missed a risk; the assessment is updated |
| Updated DPIA register | Clause 8.2 / Annex A.1.2.5 | A missed DPIA trigger becomes a NC; the trigger-test discipline is corrected |
| Updated exercise / drill programme | Clause 8.1 (operational) | Effectiveness checks often schedule a follow-on drill to validate the fix under load |
| Management-review input | Clause 9.3 | The 10.2 dashboard (open NCs, aging, recurrence, effectiveness) is a required management-review input |
| Continual improvement | Clause 10.1 | Lessons learned from closed NCs become the inputs to proactive improvement |
| Regulator / customer reporting | RBI / SEBI / IRDAI / CERT-In / DPDP / customer contracts | Many corrective actions are reportable (CERT-In post-incident report; SEBI quarterly compliance; DPDP breach follow-up; SDF section 10 audit remediation report) |
The 10.2 ↔ 9.2 ↔ 9.3 triangle (most-tested relationship)
The most-tested relationship in the PIMS is the triangle formed by 9.2 (internal audit), 10.2 (corrective action) and 9.3 (management review). 9.2 produces the findings; 10.2 closes them; 9.3 reviews both the findings and the closure discipline. The certification auditor traces a sample finding through all three clauses in a single walk, open the 9.2 audit report (the finding); open the 10.2 Register (the entry); open the RCA worksheet; open the corrective-action plan; open the effectiveness check; open the closeout; open the 9.3 management-review minutes (the reference to the finding and its closure). Any break in the chain is a finding on the clause where the break occurred.
The independence rule is the load-bearing discipline. The internal auditor who wrote the finding cannot own the corrective action; the business-process owner owns the corrective action; the auditor verifies at the next cycle. A 10.2 Register where the same person wrote the finding and the corrective action is the canonical independence failure, and a Clause 9.2 finding cascading into a Clause 10.2 finding.
ISO/IEC 27001:2022 Clause 10.2
Structurally identical on the infosec side. For organisations running both certifications, the combined 10.2 discipline has a shared Nonconformity Register spine (a single Register with the source-tag dimension distinguishing the PIMS NCs from the ISMS NCs), with clearly labelled sub-sections for the privacy-specific NC families (the seven-plus-three privacy catalogue) and the security-specific NC families (the access-control NCs, the vulnerability-management NCs, the security-operations NCs). The DPO and the CISO jointly own the integrated corrective-action discipline; the Corrective-Action Board reviews both surfaces monthly.
GDPR
Article 24(1) "the controller shall implement appropriate technical and organisational measures... and review and update those measures" is the explicit statutory anchor for the ongoing-basis dimension of 10.2, corrective action is how the controller updates the measures when a gap is detected. Article 32(1)(d) "regular testing, assessing and evaluating the effectiveness of technical and organisational measures" is the anchor for the effectiveness-check dimension of 10.2, the regular testing surfaces the gaps; 10.2 closes them. Article 5(2) accountability ("the controller shall be responsible for, and be able to demonstrate compliance" with the principles) is the anchor for the documented-information discipline, the Nonconformity Register is how the controller demonstrates it learns from its own detections. Article 33 to 34 breach notification feeds NCs into the 10.2 pipeline; the EDPB Guidelines 9/2022 on personal data breach notification operationalise the breach-NC linkage. Article 35(11) DPIA review (where there has been a change in the risk represented by the processing operations) is the anchor for the DPIA-pipeline NC dimension.
DPDP Act 2023 + DPDP Rules 2025
Section 8(5) reasonable security safeguards (the corrective-action discipline is part of the safeguards; the Board can read an un-closed NC as a section 8(5) failure). Section 8(6) + DPDP Rules 2025 Rule 7 (breach intimation without delay, the seventy-two-hour detailed report, a missed clock is a NC under family 7; the corrective action prevents recurrence). Sections 11 to 13 rights turnaround (a missed SLA is a NC under family 3). Section 10 SDF obligations (a vacant DPO or a missed SDF DPIA is a NC under family 10; the SDF's independent-data-audit findings are an external driver of the 10.2 loop). Section 13 Grievance Officer response period (the section 13 SLA). Section 16 cross-border negative-list screening (a transfer without a documented basis is a NC under family 6). Sections 27 to 32 the DPBI's inquiry and corrective-direction powers (a corrective direction is a regulator-issued NC; the 10.2 loop runs on the direction). Section 33 + Schedule penalty maxima (the financial stakes; the Board's penalty exposure engages when the 10.2 loop is absent or ineffective).
NIST Privacy Framework v1.0
Govern-P (Governance Structure, Privacy Risk Management Strategy, Monitoring and Review) is the closest functional analogue of the 10.2 discipline. The "Monitoring and Review" category of Govern-P captures the closed-loop discipline, detecting privacy risks, evaluating them, implementing responses, and verifying the effectiveness. The Communicate-P "Reporting" category captures the documented-information discipline (the Nonconformity Register as a reporting artefact to top management). The NIST PF's risk-based approach aligns with the 10.2 "evaluate the need" step.
SOC 2 Privacy TSC + Common Criteria
CC4.1 / CC4.2 (Monitoring) are the common-criteria monitoring anchors, CC4.1 covers ongoing and separate evaluations; CC4.2 covers evaluator competence, the evaluation cadence and the corrective-action follow-up. The Points of Focus 2022 update operationalises the monitoring and correction expectations. P8.0 (Monitoring for Compliance) is the privacy-monitoring criterion that maps to the 10.2 discipline on the privacy surface. A combined PIMS + SOC 2 corrective-action discipline is common in the Indian SaaS / ITeS segment, a single Nonconformity Register covering both the PIMS NC families and the SOC 2 monitoring findings.
ISO/IEC 27002:2022
Only 5.34 (Privacy and protection of PII) is PII-specific. 5.35 (Independent review of information security) is the structural ISMS analogue of the 9.2 internal-audit dimension that produces NCs for 10.2 to close. 5.36 (Compliance with policies, rules and standards) is the lineage for the self-detection dimension, the compliance review that surfaces NCs. The 10.2 discipline consumes NCs from both 5.35 and 5.36 alongside the privacy-specific NC families.
Other ISO siblings
ISO/IEC 29134:2017 (DPIA guidelines), the source methodology for the family-4 DPIA-pipeline NCs. ISO/IEC 27018:2019 (cloud PII processor), the source methodology for the family-5 processor-chain NCs on cloud processors. ISO 31000:2018 (risk management), Clause 6 Monitoring and Review is the structural analogue of 10.2 for the risk-management discipline. ISO/IEC 42001:2023 (AI Management System), Clause 10.2 alignment for the algorithmic-software dimension; an AI-Mss NC is closed via the same six-step loop. ISO 19011:2018, the audit-follow-up lineage (the audit programme's follow-up dimension consumes the 10.2 closeout evidence). ISO/IEC 27706:2025 (PIMS certification-scheme competence), the standard that governs the certification-body's competence for the certification audit, including the NC-management discipline.
Inside the harmonized structure, what 10.2 inherits
The harmonized structure means 10.2 is structurally aligned with the ISMS Clause 10.2, the AI-Management-System Clause 10.2, the BCMS Clause 10.2 and the QMS Clause 10.1. An organisation running an integrated 27001 + 27701 + 42001 programme can run a single combined corrective-action discipline with sub-sections for each discipline, a single Nonconformity Register, a single effectiveness-check programme, a single management-review input.
Detailed Implementation Guidance, The Seven Corrective-Action Moves
Figure · Process
What Clause 10.2 asks you to do

Move 1, Stand up the Nonconformity Register
The first move is to establish the Nonconformity Register (toolkit doc 03) as a single source of truth covering all NC sources. The Register is the load-bearing 10.2 artefact; it is the certification auditor's first-stop in the Stage 2 examination and the DPBI's first-stop in any post-incident inquiry. The Register has the following fields per entry:
- NC ID and title, the canonical label (for example, PIMS-NC-2026-014, Consent quality drift on telemedicine platform).
- Source, the detection source (9.1, 9.2, 9.3, 8.x operational event, complaint, regulator engagement, whistleblower, SDF section 10 audit, certification audit).
- Family, the privacy-nonconformity family.
- Detection date and Description (the fact, the criteria, the evidence).
- Classification (conformity / observation / minor NC / major NC / opportunity for improvement).
- Owner, the named business-process owner.
- Containment and correction record; Consequences-handling record (the principal-notification despatch; the regulator-engagement clock; the remediation offer).
- Root-cause analysis, the method used, the worksheet, the verified root cause(s).
- "Evaluate the need" decision, the risk-based decision and rationale.
- Corrective action plan, the action(s), owner, target date, implementation evidence.
- Effectiveness check, method, verifier, date, outcome.
- Closeout, date, outcome, sign-off.
- Risk-and-SoA update trail, changes to the privacy risk register and the SoA.
- Management-review cross-reference.
- Lifecycle state, open / in-progress / pending-effectiveness-check / closed / recurrence.
The Register is reviewed monthly by the Corrective-Action Board and quarterly by the management review. The recurring-nonconformity pattern is the load-bearing 9.3 input.
Move 2, Build the root-cause-analysis toolkit
The root-cause-analysis toolkit (toolkit doc 09) is the methodological foundation. The toolkit has the following methods, each with a template, a worked example and an applicability guide:
- 5-Why, the iterative "why" question, typically five layers deep. Best suited for single-cause NCs in well-understood processes (a missed consent-quality check; a single SLA breach; a single document-control lapse). The Singahi 5-Why template has space for the chain of "why" questions, the verified root cause, and the corrective-action linkage.
- Ishikawa / fishbone diagram, categorising causes by people, process, technology, external, measurement, environment. Best suited for multi-cause NCs (the breach drill that surfaced multiple gaps; the rights-response failure that traced to staffing, training and tooling simultaneously).
- Fault-tree analysis, top-down deduction from the event to the root causes through AND / OR logic gates. Best suited for high-consequence NCs (a major breach; a cross-border transfer violation affecting thousands of principals).
- IS / IS-NOT matrix, comparing what is and is not true about the event (what was affected; what was not; when it occurred; when it did not; where; who). Best suited for NCs where the boundary of the event needs to be defined (a partial breach; an intermittent SLA failure).
- Bow-tie analysis, mapping threats, top events, consequences and barriers (preventive and recovery). Best suited for NCs where the barrier analysis is the corrective action (a breach with multiple barrier failures).
- Failure-mode-and-effects-analysis (FMEA), systematic enumeration of failure modes, their effects, their severity, occurrence and detection scores, and the resulting risk-priority number. Best suited for NCs in a process redesign (the corrective action is the FMEA-driven redesign).
The toolkit mandates that the method used is named on the RCA worksheet; the certification auditor will check the method match the NC's complexity. A 5-Why on a major breach is a red flag; an FMEA on a single document-control lapse is over-engineered.
Move 3, Build the effectiveness-check programme
The effectiveness-check programme (toolkit doc 10) is the most-omitted dimension of the 10.2 discipline. The programme has the following elements:
- The cadence, typically 30 / 60 / 90 days post-implementation. For a minor NC, a thirty-day check may suffice. For a major NC, the 30 / 60 / 90-day cadence with the ninety-day check at the next 9.2 internal-audit cycle.
- The verifier, must be independent of the implementer (the business-process owner who implemented the corrective action cannot be the verifier). Typically the Internal Audit Function or the DPO; for material NCs, an external advisor.
- The method, observation (is the corrective action operating as designed); sample test (a sample of post-implementation events, consent records, rights requests, transfers, tested against the new criteria); walk-through (an end-to-end trace of the corrected process).
- The outcome, effective (the NC has not recurred; the root cause has been eliminated) / partially effective (the NC has not recurred but the root cause persists in a different form) / ineffective (the NC has recurred, or the root cause is unchanged).
- The follow-up, for partially-effective or ineffective, the re-entry into the loop with a deeper root-cause analysis and a revised corrective action.
The effectiveness-check programme is reviewed quarterly by the Corrective-Action Board; the effectiveness rate (the percentage of corrective actions that delivered the intended outcome) is the load-bearing 10.2 KPI.
Move 4, Build the NC-to-risk-and-SoA update link
The NC-to-risk-and-SoA update link (toolkit doc 12) is the artefact that operationalises the "update risks and opportunities and the PIMS" step. The link has the following dimensions:
- The risk-register update, each closed NC produces a risk-register update. A new risk may be added (the cross-border transfer without a TIA is now a transfer-risk entry); a risk rating may be changed (the consent-quality risk is upgraded from medium to high after the breach drill); a risk may be closed (the access-control gap that produced the breach is closed by the corrective action).
- The SoA update, where the corrective action changed the control surface, the SoA is updated. A control marked applicable may now be implemented at higher maturity (the consent flow is redesigned, the SoA description is updated); a new control may be added (the algorithmic-software review is added to the SoA); a control may be retired (the manual-rights-response workflow is replaced by the automated workflow, the manual control is retired).
- The documented-information update, the policy, the procedures, the process criteria may be updated by the corrective action. The document-control discipline under Clause 7.5 is engaged.
- The objectives update, where the corrective action materially changes the privacy-operation's maturity, the Clause 6.2 privacy objectives may be revised. A new objective may be added (the consent-quality score target is added); an existing objective may be tightened (the rights-response SLA target is reduced from seventy-two hours to forty-eight).
The update link is verified by the certification auditor in the Stage 2 examination, pick a sample NC and trace whether the risk register and the SoA were updated. A NC closed without a risk-register or SoA update is the canonical "no-update" failure.
Move 5, Build the recurring-nonconformity pattern response
The recurring-nonconformity pattern is the highest-signal 10.2 input to the management review. A finding that appears in two or three consecutive cycles on the same operational area signals one of three things:
- The corrective action under 10.2 was ineffective, the root cause was not addressed. The re-entry into the loop with a deeper RCA (perhaps a different method, fault-tree instead of 5-Why; bow-tie instead of Ishikawa) and a more systemic corrective action.
- The operational area has a structural problem that the corrective-action discipline cannot resolve, the area needs a Clause 6.3 planned change or a Clause 10.1 continual-improvement programme. The corrective action under 10.2 has reached its limit; the structural treatment under 6.3 or 10.1 takes over. The Nonconformity Register records the escalation; the 9.3 management review resources the structural treatment.
- The audit or detection mechanism is testing the wrong thing, the NC criteria or the method are not right for the area. The 9.2 audit programme is refreshed; the audit criteria are revised; the detection method is changed.
The recurring-nonconformity pattern is flagged in the Register's lifecycle state ("recurrence"); the management-review input summarises the recurring patterns and the structural-treatment response. The certification auditor tests the recurring-pattern response by asking "what is your recurring-NC list, and what structural treatment have you engaged".
Move 6, Build the DPBI corrective-direction response procedure
For Indian Data Fiduciaries, the DPBI corrective-direction response procedure (toolkit doc 08 Section 5) is the marquee 10.2 external-driver dimension. The procedure operationalises the response to a DPBI corrective direction under DPDP Act 2023 sections 27 to 32:
- React, acknowledge the direction within the Board's timeline (prescribed in the DPDP Rules 2025). Convene the DPBI Response Team (the DPO, the Head of Legal, the CISO, the business-process owner of the affected area, the executive sponsor).
- Control and correct; deal with the consequences, take the operational steps the direction requires (cease the processing; transfer or delete the data; remedy the violation). Notify the affected principals where required. Engage the regulator-engagement clock.
- Evaluate the need, root-cause the underlying violation. Why did the PIMS let this happen.
- Implement corrective action, beyond the operational steps the direction requires, fix the systemic gap. Update the privacy risk register and the SoA. Update the policy, the procedures, the documented information.
- Review effectiveness, verify to the Board's satisfaction that the corrective action delivered the intended outcome. The Board may require an independent verification (the SDF section 10 independent data auditor; an independent expert).
- Update risk and SoA, feed the lessons into the PIMS. The DPBI direction is a high-information event; the lessons are systemic.
The procedure is drilled annually. The drill simulates a DPBI direction on a sample operational area; the Response Team runs the procedure end-to-end; the drill report captures the timing, the decision points, the evidence; the lessons feed back into the procedure.
Move 7, Wire the corrective-action discipline into the management review
The seventh move is the reporting and decision wiring. The 10.2 discipline produces a monthly dashboard (the open-NC count; the aging profile; the closeout rate; the effectiveness rate; the recurring-pattern list; the risk-and-SoA update trail) that feeds the Corrective-Action Board monthly and the management review (Clause 9.3) quarterly. The DPO presents (or, for the integrated-with-distinction dimension, the DPO and the CISO jointly present) the dashboard to top management. The management review considers:
- The open-NC dashboard and the aging profile.
- The recurring-nonconformity pattern and the structural-treatment response.
- The effectiveness rate (the percentage of corrective actions that delivered the intended outcome).
- The risk-and-SoA update trail (the changes to the privacy risk register and the SoA resulting from the 10.2 discipline).
- The DPBI corrective-direction response status (any direction in flight; the closure status; the verification status).
- The implications for the PIMS (suitability, adequacy, effectiveness).
The output is the management-review decisions, including the resources for the structural treatment of the recurring patterns and the implications for the next cycle's audit programme under Clause 9.2.
The reporting line is the load-bearing 10.2-to-9.3 link. A Nonconformity Register that is maintained but never reported to the management review is the canonical reporting failure, the corrective-action work is done but the top-management decision loop is not engaged. The certification auditor tests the reporting line by asking for the management-review minutes that reference the 10.2 dashboard; the absence of such a reference is a 10.2 finding on the reporting dimension.
Worked example, the seven moves in sequence
To make the seven moves concrete, the Setu Finance build in Section 15 traces each move end-to-end: Move 1 (Register retro-load of one hundred and seven entries from the 9.2 audits, the breach register, the rights ticketing system, the RBI inspection findings and the complaint register); Move 2 (the RCA toolkit with 5-Why, Ishikawa and fault-tree, trained on forty-two business-process owners); Move 3 (the 30 / 60 / 90-day effectiveness-check programme with the Internal Audit Function as the verifier for material NCs); Move 4 (the NC-to-risk-and-SoA update link as a structured workflow); Move 5 (the recurring-pattern response that surfaced three patterns and escalated each to a Clause 6.3 structural treatment); Move 6 (the DPBI-direction response procedure drilled twice in the first year); Move 7 (the monthly Corrective-Action Board dashboard as the load-bearing 9.3 input, co-presented by the DPO and the CISO). The full outcome is in Section 15.
Tools, Technologies, and Solutions
The tool categories
CAPA-management GRC platforms. Modules that record the Nonconformity Register, the RCA worksheets, the corrective-action plans, the effectiveness-check records, the closeout, the risk-and-SoA update trail and the management-review reporting. Often bundled with the audit-management module (the same platform feeds NCs from the 9.2 audit directly into the 10.2 Register).
RCA-toolkit platforms. Specialised platforms or templates that structure the RCA, the 5-Why chain, the Ishikawa canvas, the fault-tree diagram, the IS / IS-NOT matrix, the bow-tie, the FMEA. Often a feature of the GRC platform rather than a standalone tool; sometimes a standalone visual-canvas tool.
Effectiveness-check workflow tools. Modules that schedule the 30 / 60 / 90-day effectiveness checks, assign the verifier, capture the verification evidence and record the outcome. Often a feature of the CAPA-management GRC platform.
Integrated incident-and-NC platforms. For organisations running the integrated-with-distinction posture with the ISMS, a single platform that handles the security incident, the privacy breach, the operational event and the management-system nonconformity on a unified workflow with the source-tag dimension distinguishing the cycle each goes through.
DPBI engagement-management tools. For Indian Data Fiduciaries, tools that manage the regulator-engagement dimension, the DPBI correspondence register, the corrective-direction response workflow, the timeline tracking, the evidence library submitted to the Board. Often a feature of the CAPA-management GRC platform with India-specific extensions.
Evidence-collection tools. Tools that gather the corrective-action evidence, the consent-record exports, the rights-request ticketing exports, the breach-register extracts, the transfer-register extracts. Often built into the operational platforms (the consent platform, the ticketing system, the breach register) rather than a separate corrective-action tool.
Sampling tools. Statistical sampling tools that draw the effectiveness-check sample with documented sample sizes, confidence levels and selection methods.
Selection criteria
Select on: India-DPDP coverage (most global platforms are GDPR-heavy and DPDP-thin); CAPA support (the Register, the RCA toolkit, the effectiveness-check workflow as first-class artefacts); the integrated-with-distinction support (the PIMS-plus-ISMS unified workflow); the NC-to-risk-and-SoA update link (the structured workflow from a closed NC to a risk-register or SoA update); the DPBI engagement-management extensions; the management-review integration (the dashboard as a first-class 9.3 input); and cost-to-value for the Indian growing-company segment.
Build vs buy
Most growing companies should buy the GRC platform with the CAPA module and build the corrective-action methodology in-house with external advisory for the first cycle. The methodology is too organisation-specific to outsource end-to-end; the tooling is too time-intensive to build internally. The RCA toolkit is the build item, it must be customised to the organisation's processes, systems and risk profile; the generic toolkit is a starting point, not a finished instrument.
Policy and Procedure Templates
Nonconformity and Corrective Action Policy (sample of our own drafting)
The organisation maintains a corrective-action discipline that reacts to detected nonconformities of the PIMS, controls and corrects them, evaluates the need to eliminate the root causes, implements corrective action where the evaluation says so, reviews the effectiveness of the action, and updates the privacy risk register and the Statement of Applicability where needed. The Nonconformity Register is the single source of truth covering all sources (9.1 monitoring, 9.2 internal audit, 9.3 management review, Clause 8 operational events, complaints, regulator engagements, whistleblower reports, SDF section 10 audit findings, certification-audit findings). The classification taxonomy (conformity / observation / minor NC / major NC / opportunity for improvement) is applied per entry. The root-cause analysis uses a defined method (5-Why, Ishikawa, fault-tree, IS / IS-NOT, bow-tie, FMEA) appropriate to the NC's complexity. The effectiveness-check programme runs on a 30 / 60 / 90-day cadence with documented verification. The recurring-nonconformity pattern triggers structural treatment under Clause 6.3 or Clause 10.1. The Nonconformity Register, the RCA worksheets, the corrective-action plans, the effectiveness-check records and the closeout are Documented Information under Clause 7.5. For Indian Data Fiduciaries, the DPBI corrective-direction response procedure is operational; for SDFs, the SDF section 10 remediation-order response is integrated with the 10.2 discipline.
Corrective Action Procedure (sample of our own drafting, summarised)
- Scope and inputs, every detected nonconformity of the PIMS, from any source. The inputs are the 9.1 / 9.2 / 9.3 findings, the Clause 8 operational events, the complaints, the regulator engagements, the SDF section 10 audit findings and the certification-audit findings.
- Detection and logging, the NC is logged in the Register with the source, the family, the detection date, the description, the classification and the owner.
- Containment and correction; consequences-handling, the immediate action to control and correct; the principal-notification despatch where relevant; the regulator-engagement clock where relevant; the remediation offer to affected principals where relevant.
- Root-cause analysis, the method selected per the toolkit; the worksheet completed; the root cause verified.
- "Evaluate the need" decision, the risk-based decision on whether corrective action is needed; the rationale recorded; the decision (yes / no / partially) and the date.
- Corrective-action implementation, the action(s) implemented; the implementation evidence recorded.
- Effectiveness check, the verifier (independent of the implementer); the method; the cadence (30 / 60 / 90 days); the outcome.
- Closeout, the date; the outcome; the sign-off.
- Risk-and-SoA update, the changes to the privacy risk register and the SoA recorded.
- Management-review reporting, the dashboard input to the Corrective-Action Board monthly and the management review quarterly; the recurring-pattern response.
- For Data Fiduciaries, the DPBI corrective-direction response procedure (toolkit doc 08 Section 5).
- For SDFs, the SDF section 10 remediation-order response integrated with the 10.2 discipline.
- Roles and responsibilities, the executive sponsor, the DPO (operational owner), the Corrective-Action Board, the business-process owners (corrective-action owners), the Internal Audit Function (effectiveness verifier for material NCs), top management (recipient of the dashboard).
- Documented Information control, the Register, the RCA worksheets, the corrective-action plans, the effectiveness-check records, the closeout, the risk-and-SoA update trail, all retained as Documented Information per Clause 7.5.
Sample Nonconformity Register clauses
The Nonconformity Register is the single source of truth for every detected nonconformity of the PIMS. No nonconformity is corrected outside the Register; no closure is recorded without the effectiveness check.
Each entry in the Register has the load-bearing fields (NC ID, source, family, detection date, description, classification, owner, containment and correction record, consequences-handling record, RCA, "evaluate the need" decision, corrective action plan, effectiveness check, closeout, risk-and-SoA update trail, management-review cross-reference, lifecycle state).
The Register is reviewed monthly by the Corrective-Action Board. The recurring-nonconformity pattern is flagged and escalated to the structural-treatment pipeline under Clause 6.3 or Clause 10.1.
The Register is wired into the management-review input under Clause 9.3, the dashboard (open NCs, aging, effectiveness rate, recurring patterns, risk-and-SoA update trail) is a required input.
For Indian Data Fiduciaries, the Register includes the DPBI corrective-direction entries. For SDFs, the Register includes the SDF section 10 remediation-order entries.
Risk Assessment and Treatment
The 10.2 risk register (the corrective-action discipline's own risk)
The 10.2 discipline itself carries risk, the risk that the RCA is shallow, the risk that the effectiveness check is a tick-box, the risk that the recurring pattern is not escalated, the risk that the DPBI corrective-direction response is not drilled. The 10.2 risk register (a section of the Findings Register or a separate artefact) records these risks and the treatments.
The shallow-RCA risk
The shallow-RCA risk is the most-common 10.2 risk. Symptoms: ninety percent of corrective actions are "retrained staff" or "rewrote procedure"; the RCA worksheets stop at layer two of a 5-Why; the Ishikawa diagrams have three bones instead of the full people / process / technology / external / measurement / environment set. Treatment: the RCA toolkit with the worked examples; the auditor's review of the RCA worksheets (the certification auditor will check the depth); the recurring-pattern signal (a shallow RCA produces recurring patterns; the escalation forces a deeper RCA).
The effectiveness-check-as-tick-box risk
The effectiveness-check-as-tick-box risk is the second-most-common 10.2 risk. Symptoms: every effectiveness check concludes "effective" within thirty days; the verifier is the implementer; the method is "asked the implementer". Treatment: the independence dimension (the verifier is independent of the implementer); the method discipline (observation; sample test; walk-through); the cadence (the 30 / 60 / 90-day cadence with the 90-day check at the next 9.2 internal-audit cycle for material NCs).
The recurring-pattern-without-escalation risk
The recurring-pattern-without-escalation risk is the most-tested 10.2 risk. Symptoms: the same NC appears in three consecutive cycles; the corrective action under 10.2 is repeated; the structural treatment under Clause 6.3 or Clause 10.1 is not engaged. Treatment: the recurring-pattern flag in the Register's lifecycle state; the management-review escalation; the structural-treatment pipeline under Clause 6.3 or Clause 10.1.
The no-update risk
The no-update risk is the demarcation risk between 10.2 and 6.1.2 / 6.1.3 / 8.3. Symptoms: the NC is closed but the privacy risk register and the SoA are unchanged; the lessons learned do not flow back into the PIMS. Treatment: the NC-to-risk-and-SoA update link as a structured workflow; the certification auditor's verification that each closed NC produced a risk-register or SoA update entry.
The DPBI-direction-not-drilled risk
For Indian Data Fiduciaries, the DPBI-direction-not-drilled risk is the marquee external-driver risk. Symptoms: the DPBI corrective-direction response procedure exists but has never been drilled; the Response Team has never run the procedure end-to-end; the regulator-engagement clock has never been tested. Treatment: the annual drill; the drill report; the procedure refinements.
Audit and Compliance Checklist
The 26 questions below cover the audit-evidence surface for Clause 10.2. Expected evidence and red flags noted. Most can be answered from the toolkit doc 04 audit-evidence checklist.
- Is there a Nonconformity Register as a distinct artefact? Expected: dated, version-controlled, accessible. Red flag: missing; or the Register exists only inside the audit reports.
- Does the Register cover all sources (9.1, 9.2, 9.3, Clause 8 events, complaints, regulator engagements, whistleblower, SDF section 10 audit, certification audit)? Red flag: only 9.2 audit findings.
- Does the Register use the ten privacy-nonconformity family taxonomy?
- Is each entry classified (conformity / observation / minor NC / major NC / opportunity for improvement)?
- Is each entry owned by a named business-process owner? Red flag: "the DPO" or "the privacy team" as the owner for every entry.
- Is the containment and correction record on file per entry?
- Is the consequences-handling record on file per entry (principal-notification despatch; regulator-engagement clock; remediation offer)?
- Is the RCA on file per entry (method named; worksheet; verified root cause)?
- Is the RCA method appropriate to the NC's complexity (5-Why for simple; Ishikawa for multi-cause; fault-tree for high-consequence; FMEA for process redesign)? Red flag: a 5-Why on a major breach; an FMEA on a single document-control lapse.
- Is the "evaluate the need" decision on file (the risk-based decision and rationale)?
- Is the corrective-action plan on file (action, owner, target date, evidence)?
- Is the corrective action root-cause oriented? Red flag: ninety percent of corrective actions are "retrained staff" or "rewrote procedure".
- Is the effectiveness check on file (verifier, method, cadence, outcome)?
- Is the effectiveness verifier independent of the implementer? Red flag: the same person implemented and verified.
- Is the effectiveness-check cadence appropriate (30 / 60 / 90 days; 90-day check at the next 9.2 cycle for material NCs)? Red flag: every check concludes "effective" within thirty days.
- Is the closeout on file (date, outcome, sign-off)?
- Is the risk-and-SoA update trail on file? Red flag: NC closed but risk register and SoA unchanged (the no-update failure).
- Is the management-review cross-reference on file (the Clause 9.3 input where the NC was reported)?
- Is the recurring-nonconformity pattern flagged in the Register's lifecycle state?
- Is the recurring-nonconformity pattern escalated to the structural-treatment pipeline under Clause 6.3 or 10.1?
- Is the Internal Audit Function independent of the corrective-action implementation? Red flag: the same person wrote the 9.2 finding and owns the 10.2 corrective action.
- For Indian Data Fiduciaries, is the DPBI corrective-direction response procedure operational (procedure document; Response Team; annual drill report)?
- For SDFs, is the SDF section 10 remediation-order response integrated with the 10.2 discipline?
- Is the integrated-with-distinction posture with the ISMS operational (single Register with the source-tag dimension)?
- Is the Register wired into the management-review input under Clause 9.3? Red flag: the Register maintained but never reported.
- Is the 10.2 discipline evaluated annually for effectiveness (RCA quality; effectiveness-check rate; recurring-pattern rate; no-update rate; certification-audit divergence)?
Evidence the auditor will physically request
- The Nonconformity Register (the single source of truth).
- The RCA worksheets for a sampled set of NCs (typically two or three, including at least one major NC).
- The corrective-action plans, the effectiveness-check records, the closeout records and the risk-and-SoA update trail for the sampled NCs.
- The management-review minutes referencing the 10.2 dashboard.
- The recurring-nonconformity pattern list and the structural-treatment escalation records.
- For Data Fiduciaries: the DPBI corrective-direction response procedure and the annual drill report.
- For SDFs: the SDF section 10 remediation-order entries in the Register.
- The integrated-with-distinction evidence: the PIMS Register and the ISMS Register reconciled (or the unified Register with the source-tag dimension).
Common Stage-1 nonconformities the auditor will write up
- NC 1: Nonconformity Register does not exist; only the audit reports and the corrective-action plans scattered across files. Major NC. Remediation: build the Register, four to eight weeks.
- NC 2: Register covers only 9.2 audit findings; the 9.1, 9.3, Clause 8 operational events, complaints and regulator-engagement sources are not in the Register. Major NC. Remediation: retro-load the missing sources, four to twelve weeks.
- NC 3: Shallow RCA, ninety percent of corrective actions are "retrained staff" or "rewrote procedure"; the RCA worksheets stop at layer two of a 5-Why. Minor or major NC. Remediation: rebuild the RCA toolkit, re-run the RCA on the open NCs, six to twelve weeks.
- NC 4: No effectiveness check, the NCs are closed at "action implemented" with no verification. Major NC. Remediation: stand up the effectiveness-check programme, re-run on the closed NCs, six to twelve weeks.
- NC 5: No-update failure, the NCs are closed but the privacy risk register and the SoA are unchanged. Minor or major NC. Remediation: build the NC-to-risk-and-SoA update link, retro-update on the closed NCs, four to eight weeks.
- NC 6: Recurring-pattern-without-escalation, the same NC appears in three consecutive cycles; the structural treatment under Clause 6.3 or Clause 10.1 is not engaged. Major NC. Remediation: escalate to the structural-treatment pipeline, eight to sixteen weeks.
- NC 7: Independence failure, the internal auditor who wrote the finding also owns the corrective action. Minor or major NC. Remediation: reassign the corrective action to the business-process owner; the auditor verifies at the next cycle, four to eight weeks.
- NC 8: Reporting failure, the Register is maintained but never reported to the management review. Minor or major NC. Remediation: wire the dashboard into the 9.3 input pack, four to twelve weeks (next review cycle).
- NC 9: DPBI-direction-not-drilled (for Data Fiduciaries), the response procedure exists but has never been drilled. Minor NC. Remediation: schedule and conduct the drill, four to eight weeks.
- NC 10: Demarcation failure, a Clause 8.x operational incident (a breach; a complaint; a regulator engagement) produced no entry in the Nonconformity Register. Major NC. Remediation: retro-load the operational-event-derived NCs, four to twelve weeks.
Metrics and KPIs
Figure · Measures
The measures that show Clause 10.2 is working
- NC detection coverageall sources)Periodic
- Open-NC count and aging profileskewed to und…Periodic
- Closeout rate90 % within 90Periodic
- Effectiveness rate85 % plusPeriodic
- Recurring-NC ratedownward trendPeriodic
- NC detection coverage, count of NC sources covered in the Register (target: all sources).
- Open-NC count and aging profile, open NCs by aging band (under 30 / 30 to 60 / 60 to 90 / over 90). Target: skewed to under 60 days.
- Closeout rate, percentage of NCs closed within target (90 days minor; 180 days major). Target: 90 percent within 90 days; 100 percent within 180 days.
- Effectiveness rate, percentage of corrective actions that delivered the intended outcome. Target: 85 percent plus.
- Recurring-NC rate, count of NCs flagged "recurrence". Target: downward trend; recurring NCs trigger structural treatment.
- RCA depth score, percentage of RCA worksheets meeting the depth bar (method named; appropriate to complexity; chain complete). Target: 100 percent.
- "Retrained staff or rewrote procedure" rate, percentage of corrective actions in that shape. Target: under 30 percent.
- NC-to-risk-and-SoA update rate, percentage of closed NCs that produced a risk-register or SoA update. Target: 100 percent on major NCs; 60 percent plus on minor.
- Reporting-to-management-review latency, time from dashboard production to management-review presentation. Target: under 30 days.
- Independence test pass rate, percentage of NCs where the verifier is independent of the implementer. Target: 100 percent.
- Operational-event-to-NC conversion rate, percentage of Clause 8.x operational events exposing a control gap that produced a Register entry. Target: 100 percent.
- DPBI corrective-direction response time (for Data Fiduciaries), time from a DPBI direction to acknowledgment and operational steps. Target: within the Board's prescribed timeline.
- DPBI drill cadence (for Data Fiduciaries), drills per year. Target: at least one.
- SDF section 10 remediation-order closure rate (for SDFs), percentage closed within the prescribed timeline. Target: 100 percent.
- Integrated-with-distinction reconciliation, percentage of shared-control NCs handled in the unified workflow. Target: 100 percent.
Common Pitfalls and Audit Failures
Pitfall 1, The "retrained staff" corrective-action failure. Ninety percent of corrective actions in the Register are "retrained staff" or "rewrote procedure", the RCA is shallow and the root cause was never identified. The single most common 10.2 finding in the Indian growing-company segment. Treatment: Move 2 (RCA toolkit; per-NC worksheet depth review).
Pitfall 2, The no-effectiveness-check failure. NCs closed at "action implemented" with no verification, the loop is open at the last step. Treatment: Move 3 (the 30 / 60 / 90-day effectiveness-check programme with the independent verifier).
Pitfall 3, The recurring-pattern-without-escalation failure. The same NC in three consecutive cycles; the corrective action under 10.2 is repeated; the structural treatment under Clause 6.3 or 10.1 is not engaged. Treatment: Move 5 (escalation to the structural-treatment pipeline).
Pitfall 4, The no-update failure. NC closed but the privacy risk register and the SoA are unchanged, lessons do not flow back into the PIMS. Treatment: Move 4 (the NC-to-risk-and-SoA update link as a structured workflow).
Pitfall 5, The independence failure. The internal auditor who wrote the 9.2 finding also owns the 10.2 corrective action, the audit function loses independence for the next cycle. Treatment: the business-process owner owns the corrective action; the auditor verifies at the next cycle.
Pitfall 6, The demarcation failure. A Clause 8.x operational incident (a breach; a complaint; a regulator engagement) is handled by the operational procedure but produces no Register entry, the systemic gap is never corrected. Treatment: the operational-event-to-NC conversion discipline.
Pitfall 7, The source-coverage failure. The Register covers only 9.2 audit findings; 9.1, 9.3, Clause 8 operational events, complaints and regulator-engagement sources are missing. Treatment: Move 1 (cover all sources with the source-tag dimension).
Pitfall 8, The "evaluate the need" checkbox failure. Every entry says "yes, action needed" with no risk-based analysis. Treatment: the risk-based decision discipline (rationale recorded; decision defensible).
Pitfall 9, The shallow-family-tagging failure. Every entry tagged "privacy" generically rather than by the ten-family taxonomy. Treatment: Move 1 (the family-tag dimension per entry).
Pitfall 10, The reporting failure. The Register is maintained but never reported to the management review. Treatment: Move 7 (wire the dashboard into the Clause 9.3 input pack).
Pitfall 11, The document-only corrective-action failure. The corrective action updates the policy or the procedure with no operational change. Treatment: every corrective action must produce an operational change (workflow; tooling; staffing) in addition to the document change.
Pitfall 12, The DPBI-direction-not-drilled failure. The response procedure exists but has never been drilled, the regulator-engagement clock has never been tested. Treatment: Move 6 (the annual drill; the procedure refinements).
Pitfall 13, The audit-programme-sequence failure. The 9.2 internal audit ran before 8.2 / 8.3, the NC is detected against no criteria. Treatment: the sequence discipline (9.2 after 8.2 / 8.3; 10.2 closeout after 9.2).
Pitfall 14, The major-NC-without-recourse-to-section-6.3 failure. A major NC that requires a PIMS change is closed under 10.2 with a quick-fix when the appropriate response was a Clause 6.3 planned change. Treatment: route major PIMS-change NCs through Clause 6.3 with the 10.2 NC linked to the 6.3 change record.
Pitfall 15, The integrated-with-distinction failure. Two parallel Registers operate separately for the PIMS and the ISMS, duplicate NCs on the shared Annex A.3 / ISO/IEC 27002:2022 controls, NC gaps elsewhere. Treatment: a unified Register with the source-tag dimension.
Pitfall 16, The certification-audit-as-sole-source failure. The Register is populated only by certification-audit findings, a certification-audit-response artefact, not a PIMS-corrective-action artefact. Treatment: Move 1 (all sources; certification-audit findings are one source among many).
Pitfall 17, The consequence-mishandling failure. The NC is contained and corrected and the root cause is addressed, but the consequences to affected principals are not remediated, the DPDP section 13 Grievance Officer dimension is not engaged. Treatment: the consequences-handling record per NC (principal-notification despatch; regulator-engagement clock; remediation offer).
Pitfall 18, The board-invisible failure. The Register and the dashboard are not visible to the Audit Committee. Treatment: the Audit Committee reporting line (for listed entities and SDFs, this is mandatory).
Illustrative Scenario 1: Failure, Vidya Healthtech and the Open-Loop Consent Nonconformity (Illustrative)
Illustrative scenario, a composite example for guidance, not a specific Singahi engagement or a verified outcome. It is set after 13 May 2027, when the DPDP Act's duties and the Board's inquiry and penalty powers take effect.
Illustrative scenario. Vidya Healthtech in this scenario is a fictional Bengaluru-based K-12 adaptive-learning platform with two hundred and sixty staff, an in-house DPO (the Head of Legal doubling up), and approximately one-point-eight million student and parent accounts; the name is descriptive only and the facts are composite from publicly reported sector patterns. Nothing here should be attributed to any real organisation.
Vidya Healthtech built its PIMS in 2024 ahead of an ISO/IEC 27701:2019 certification push. The Nonconformity Register was a spreadsheet maintained by the DPO. The 9.2 internal audit in March 2027 surfaced a minor NC under family 1 (consent and notice), the verifiable-parental-consent flow on the new-adaptive-tutoring onboarding did not consistently capture the parent's identity verification (the DPDP section 9 verifiable-parental-consent requirement; the Annex A.1.2.3 control). The RCA was a 5-Why that stopped at layer two ("the form does not have a verification step", the symptom, not the root cause). The corrective action was "retrained the onboarding team and added a verification step to the form". The effectiveness check was a thirty-day verifier-less note from the DPO: "the form now has the step; effective". The risk register and the SoA were unchanged.
In June 2027 a parent filed a DPDP section 13 grievance with Vidya alleging that their child had been onboarded without verifiable parental consent. The Grievance Officer's response confirmed the issue and offered remediation. In July 2027 a second parent filed the same grievance. In August 2027 a third. The DPO reviewed the consent records of the cohort onboarded between March and August and found that approximately twelve thousand records (out of forty-eight thousand onboarded) had the same defect, the verification step had been added to the form but the form's client-side validation did not enforce it; the onboarding team could proceed without the verification.
The recurring pattern (the original March NC recurred) was a Clause 10.2 major NC by definition. The Data Protection Board of India preliminary inquiry under section 18 (triggered by the third grievance) requested the Nonconformity Register and the corrective-action record on the consent operation. The DPBI's working hypothesis became that the shallow RCA, the verifier-less effectiveness check and the no-risk-register-update pattern were themselves DPDP section 8(5) reasonable-security-safeguards failures, the organisation could not demonstrate that it had learned from its own detections.
The certification body issued a major nonconformity on Clause 10.2 at the next surveillance audit, cascading into nonconformities on 9.2 (the audit's RCA depth was inadequate), 9.3 (the management review had not considered the recurring pattern), 6.1.3 (the SoA was unchanged despite the control operating below the documented maturity) and Annex A.1.2.3 (the consent control was not operating as documented). The certificate was suspended pending remediation.
The remediation re-engineered the 10.2 discipline, the RCA toolkit with the 5-Why template redesigned to enforce the five-layer depth; the Ishikawa introduced for multi-cause NCs; the effectiveness-check programme with the independent verifier and the 30 / 60 / 90-day cadence; the NC-to-risk-and-SoA update link; the recurring-pattern escalation procedure.
The lessons: the "retrained staff" corrective-action pattern is the shallow-RCA signature; the verifier-less thirty-day effectiveness check is the open-loop signature; the no-update failure is the demarcation signature; the recurring-pattern-without-escalation is the structural-improvement signature; the absence of a working 10.2 discipline on an operational area is itself a section 8(5) exposure after a complaint or a breach.
Illustrative Scenario 2: Success, Setu Finance Builds a Privacy-Programme Corrective-Action Discipline (Illustrative)
Illustrative scenario. Setu Finance is a fictional Mumbai-based digital-lending Non-Banking Financial Company with one thousand four hundred staff and approximately two million borrower accounts; the facts are composite from publicly reported sector patterns and should not be attributed to any real organisation.
Setu ran an integrated ISO/IEC 27001:2022 + ISO/IEC 27701:2019 programme with a single GRC platform covering both the ISMS and the PIMS. The existing 10.2 discipline was a CAPA module in the GRC platform fed by the 9.2 internal-audit findings and the certification-audit findings; the operational-event-derived NCs (the breach register; the rights-request ticketing system; the complaint register; the RBI inspection findings) were not in the CAPA module. The RCA depth was uneven; the effectiveness check was a tick-box; the recurring-pattern rate was rising year-on-year.
In Q4 2025 the DPO commissioned a 10.2 refresh ahead of the 27701:2025 transition. The workshop surfaced six material shifts (worked example in Section 7.8 details the operational shape): the Nonconformity Register retro-loaded with all sources (one hundred and seven entries); the RCA toolkit rebuilt with 5-Why, Ishikawa and fault-tree templates; the effectiveness-check programme on a 30 / 60 / 90-day cadence with the Internal Audit Function as the independent verifier for material NCs; the NC-to-risk-and-SoA update link as a structured workflow; the recurring-nonconformity pattern response with the Clause 6.3 escalation pathway; the DPBI corrective-direction response procedure drilled twice in the first year.
The first cycle produced three recurring-pattern findings (consent-quality drift on the mobile-app onboarding flow; rights-response SLA breaches on the erasure category; sub-processor change-notification clock misses on the cloud-infrastructure vendors). Each was escalated to a Clause 6.3 planned-change programme (the consent-flow redesign with the new consent-management platform; the rights-response automation with the new workflow engine; the vendor-management process redesign with the new vendor portal). The structural treatments prevented DPDP section 8(5) penalty exposure on the consent operation alone.
The DPBI-direction drill in Q2 2026 simulated a corrective direction on the cross-border transfer to the cloud-infrastructure vendor (a jurisdiction newly added to the negative list in the simulated scenario). The drill surfaced two operational gaps (the Response Team's regulator-engagement clock was not calibrated; the evidence library for the cloud-infrastructure vendor was incomplete). The drill report drove procedure refinements before any real DPBI direction arrived.
The outcome: the integrated-with-distinction posture cut parallel-CAPA overhead; the recurring-pattern escalation (structural treatment under Clause 6.3 instead of repeated corrective-action cycles under 10.2) cut corrective-action-cycle cost; the consent-quality drift structural treatment prevented DPDP section 8(5) penalty exposure on the consent operation; the DPBI-direction drill positioned Setu for the regulator-engagement dimension without an additional remediation cycle.
The lessons: the Nonconformity Register's source coverage (all sources, not just 9.2 and the certification audit) is the highest-use 10.2 decision for most Indian growing companies; the RCA depth is the audit-finding signal; the effectiveness check (independent verifier; 30 / 60 / 90-day cadence) is the most-omitted dimension; the recurring-pattern escalation (route to Clause 6.3 or Clause 10.1, not 10.2) is the structural-improvement signal; the DPBI-direction drill is the 2026 / 2027 maturity dimension as the Board becomes operational.
Multi-Framework Mapping
| 27701:2025 10.2 theme | GDPR article | DPDP Act (India) section | NIST Privacy Framework | SOC 2 TSC | ISO/IEC standards | ISO 29100 principle |
|---|---|---|---|---|---|---|
| React, control, correct; deal with consequences | Art 5(2) accountability; Art 24(1) ongoing-basis measures; Art 32(1)(d) testing | s.8(5) safeguards; s.8(6) breach follow-up; ss.27 to 32 DPBI corrective direction | Govern-P (Monitoring and Review) | CC4.1, CC4.2 (Monitoring); P8.0 (Monitoring for Compliance) | ISO/IEC 27001:2022 Clause 10.2; ISO/IEC 27002:2022 5.34, 5.36 | Accountability; Security safeguards |
| Evaluate the need for corrective action (the risk-based decision) | Art 24(1) ongoing-basis review; Art 32(1)(d) regular evaluation | s.8(5) safeguards (risk-based); s.10 SDF DPIA review | Govern-P (Risk Management Strategy) | CC3.2 (Internal control); CC4.1 | ISO/IEC 27001:2022 Clause 10.2; ISO 31000:2018 Clause 6 | Accountability |
| Implement corrective action (root-cause oriented) | Art 5(2) accountability; Art 24(2) | s.8(5) safeguards (corrective dimension); s.27 corrective direction (statutory) | Govern-P (Monitoring and Review) | CC4.2 (corrective action); P8.0 | ISO/IEC 27001:2022 Clause 10.2; ISO 19011:2018 (audit follow-up) | Accountability |
| Review effectiveness of corrective action | Art 32(1)(d) regular testing, assessing and evaluating | s.8(5) safeguards (effective); s.10 SDF independent audit verification | Govern-P (Monitoring and Review) | CC4.2 (evaluator effectiveness review); P8.0 | ISO/IEC 27001:2022 Clause 10.2; ISO/IEC 27006 / 27706 (CB verification) | Accountability |
| Update risks, opportunities and the PIMS | Art 24(1) ongoing measures; Art 35(11) DPIA review | s.8(5) safeguards (continuous); s.10 SDF DPIA refresh | Govern-P (Risk Management Strategy) | CC3.3 (policies); P8.0 | ISO/IEC 27001:2022 Clauses 6.1, 10.2; ISO/IEC 27701:2025 Clauses 6.1.2, 6.1.3, 8.2, 8.3 | Accountability |
| The ten privacy-nonconformity families | Arts 7, 30, 15-22, 35, 28, Ch V, 33-34; Art 25 (PbD); Art 8 (children) | ss.5-6, 8, 11-14, 10, 16, 8(6); s.9 children; s.10 SDF | Identify-P; Control-P; Communicate-P; Protect-P | P1.0-P8.0 | ISO/IEC 29134:2017; ISO/IEC 27018:2019; ISO/IEC 27002:2022 5.34 | All 11 principles |
| Findings → corrective-action loop (the closed loop) | Art 5(2) accountability; Art 32(1)(d) | s.8(5) safeguards (continual); s.10 SDF review | Govern-P (Improvement) | CC4.2 (corrective action); P8.0 | ISO/IEC 27001:2022 Clause 10.2; ISO 19011:2018 (audit follow-up) | Accountability |
| Reporting to management (9.3 input) | Art 5(2) accountability; Art 24(2) (DPO reports to highest management) | s.8 (board accountability); s.10 SDF DPO accountable to governing body | Govern-P (Reporting) | CC4.2 (reporting); P8.0 | ISO/IEC 27001:2022 Clauses 9.3, 10.2 | Accountability |
| Recurring-NC pattern → structural treatment (6.3 / 10.1) | Art 5(2) accountability; Art 32(1)(d); Art 25(2) (prior-informed-by-iteration) | s.8(5) safeguards (continual improvement); s.10 SDF review | Govern-P (Improvement) | CC4.2 + CC5 (corrective action) | ISO/IEC 27001:2022 Clauses 6.3, 10.2, 10.1 | Accountability |
| Demarcation: 10.2 vs 6.3 vs 10.1 vs 8.x | Art 24(1) ongoing; Art 32(1)(d) regular testing; Art 25 PbD | s.8(5) safeguards; ss.27-32 corrective direction | Govern-P (Improvement; Risk Management Strategy) | CC4.2; CC5 (Control Activities) | ISO/IEC 27001:2022 Clauses 6.3, 8.x, 10.2, 10.1 | Accountability |
| DPBI corrective-direction response (for Data Fiduciaries) | (no direct EU DPBI analogue; Art 58 SA corrective powers) | ss.27-32 (corrective direction; inquiry; penalty); s.33 + Schedule (penalty maxima) | Govern-P (Independent assurance) | CC4.2 (regulator-response) | ISO/IEC 27706:2025 (CB corrective dimension); ISO/IEC 17021-1:2015 | Accountability |
| SDF section 10 remediation-order response (for SDFs) | (no direct EU SDF analogue; Art 58 SA powers) | s.10 SDF (independent data auditor; periodic data audit; remediation) | Govern-P (Independent assurance) | CC4.2 (independent evaluator) | ISO/IEC 27706:2025; ISO/IEC 29134:2017 | Accountability |
| Integrated-with-distinction posture with ISMS | Art 32 (security of processing) | s.8(5) safeguards (PIMS + ISMS combined) | Govern-P + Protect-P | CC4 (Monitoring) + P-criteria | ISO/IEC 27001:2022 Clause 10.2; ISO/IEC 27002:2022 5.34 / 5.35 / 5.36 | Security safeguards; Accountability |
| Documented-information discipline (the Register, the RCA worksheets, the effectiveness-check records) | Art 5(2) accountability ("demonstrate compliance") | s.8(5) safeguards (evidence); s.10 SDF audit records | Communicate-P (Reporting) | CC4.2 (reporting); P8.0 | ISO/IEC 27001:2022 Clauses 7.5, 10.2; ISO/IEC 27701:2025 Clauses 7.5, 10.2 | Accountability |
The densest cross-framework mappings are at the closed-loop row (GDPR Article 5(2) accountability; DPDP section 8(5) safeguards; ISO/IEC 27001:2022 Clause 10.2; ISO 19011:2018 audit follow-up), the effectiveness-check row (GDPR Article 32(1)(d); DPDP section 8(5); ISO/IEC 27001:2022 Clause 10.2), and the update-risk-and-SoA row (GDPR Article 24(1); DPDP section 8(5); ISO/IEC 27001:2022 Clause 6.1; ISO/IEC 27701:2025 Clauses 6.1.2 / 6.1.3 / 8.2 / 8.3). The unique-to-India rows are the DPBI corrective-direction response (DPDP sections 27 to 32; the closest EU analogue is GDPR Article 58 supervisory-authority powers) and the SDF section 10 remediation-order response (DPDP section 10; no direct EU SDF analogue).
Implementation Roadmap
30 days
- Stand up the Nonconformity Register (Move 1) using the Singahi template (toolkit doc 03). Decide the medium (spreadsheet for the first cycle; GRC module for the steady state).
- Retro-load the prior twelve months of findings from every source. Most growing companies retro-load eighty to one hundred and fifty entries in the first thirty days.
- Run the corrective-action framing workshop. Walk the ten privacy-nonconformity families with one real NC per family; for each, decide: the source, the family, the classification, the owner, the target date.
- Identify the recurring-pattern candidates. Flag for escalation.
90 days
- Build the root-cause-analysis toolkit (Move 2). Adopt the 5-Why and Ishikawa templates as the minimum. Train the business-process owners and the DPO function.
- Build the effectiveness-check programme (Move 3). Assign the verifier (independent of the implementer); define the cadence; document the method.
- Build the NC-to-risk-and-SoA update link (Move 4) as a structured workflow.
- Run the six-step loop on the open NCs.
- Build the recurring-nonconformity pattern response (Move 5). Escalate the recurring-pattern candidates to the structural-treatment pipeline under Clause 6.3 or 10.1.
180 days
- Build the DPBI corrective-direction response procedure (Move 6) for Indian Data Fiduciaries. Identify the Response Team; document the procedure; schedule the first drill.
- Run the first DPBI-direction drill. The drill report drives procedure refinements.
- Wire the corrective-action discipline into the management review (Move 7). The monthly dashboard is the load-bearing input. The DPO presents quarterly.
- Update the awareness programme (Clause 7.3) and the training programme on the RCA toolkit (Clause 7.2).
- For SDFs, integrate the SDF section 10 remediation-order response with the 10.2 discipline.
12 months
- Run the full corrective-action cycle (the Register, the RCA toolkit, the effectiveness-check programme, the NC-to-risk-and-SoA update link, the recurring-pattern response, the DPBI-direction drill, the management-review wiring).
- Run the 10.2-discipline effectiveness evaluation.
- Refresh the discipline for the next cycle. Apply the recurring-pattern lessons; the regulatory-change log; the operational-change log.
- For SDFs, complete the first SDF section 10 remediation-order response cycle and integrate the lessons.
FAQ
Q1. Our Nonconformity Register is a spreadsheet. Is that acceptable?
Yes, for the first cycle. The test is whether the Register exists as a distinct artefact, covers all sources, uses the family taxonomy, and has the load-bearing fields per entry. The medium is not the test. A GRC-platform CAPA module is a maturity upgrade for the mid-sized and enterprise segment.
Q2. Our internal auditor wrote the 9.2 finding. Can the auditor own the corrective action?
No, the independence rule. The internal auditor who wrote the finding cannot own the corrective action; the business-process owner owns the corrective action; the auditor verifies at the next cycle.
Q3. How do we decide whether a nonconformity needs corrective action?
Through the "evaluate the need" step, a risk-based decision. Is the root cause likely to recur elsewhere. What is the risk of recurrence against the cost and impact of the corrective action. Is there a more fundamental PIMS change needed. Or is the right decision "no action beyond containment" because the NC was a one-off. All four answers are legitimate; the requirement is to have asked the question and to have an evidence trail.
Q4. Most of our corrective actions are "retrained staff" or "rewrote procedure". Is that a problem?
Yes, the shallow-RCA failure. If ninety percent of corrective actions are in that shape, your RCA is not reaching the root cause. Retraining and rewriting are sometimes the right answer, but only after a real RCA points there. The signal is the recurring-pattern rate.
Q5. Do we have to conduct an effectiveness check on every corrective action?
Yes. The effectiveness check is the most-omitted step and the most-probed step in the certification auditor's Clause 10.2 examination. The verifier (independent of the implementer) confirms the corrective action delivered the intended outcome. For material NCs, the 90-day check at the next 9.2 cycle.
Q6. Our NC is closed but our privacy risk register and SoA are unchanged. Is that a problem?
Yes, the no-update failure. A closed NC that produced no risk-register or SoA update is an open loop on the update dimension. Build the NC-to-risk-and-SoA update link as a structured workflow.
Q7. The same nonconformity appears in three consecutive cycles. What should we do?
Escalate to the structural-treatment pipeline under Clause 6.3 or 10.1. The recurring pattern is the load-bearing signal that the corrective-action discipline under 10.2 has reached its limit; the structural treatment takes over.
Q8. We had a privacy breach handled by the breach-response procedure. Do we need a 10.2 entry as well?
Yes, if the breach exposed a control gap. The breach-response procedure handled the operational event. The control gap the breach exposed is a nonconformity under 10.2; the six-step loop runs on the gap. An operational event handled by the breach-response procedure with no Register entry is the canonical demarcation failure.
Q9. We received a DPBI corrective direction. How do we handle it?
Through the DPBI corrective-direction response procedure. Acknowledge within the Board's timeline; convene the Response Team; take the operational steps the direction requires; root-cause the underlying violation; implement the corrective action beyond the operational steps; verify to the Board's satisfaction; update the risk register and the SoA. The direction is, in PIMS terms, a regulator-issued nonconformity finding.
Q10. Can we use the same Register for the PIMS and the ISMS?
Yes, the integrated-with-distinction posture. A unified Register with the source-tag dimension distinguishing the PIMS NCs from the ISMS NCs avoids duplicate NCs on the shared Annex A.3 / ISO/IEC 27002:2022 controls. The DPO and the CISO jointly own the integrated Register.
Q11. Our SDF section 10 independent data audit produced findings. Do they go in the Register?
Yes. The SDF section 10 audit findings are nonconformities against the SDF section 10 obligations; they go in the Register under family 10. The six-step loop runs on each finding; the closure status is reported to the independent data auditor at the next audit.
Q12. What is the difference between 10.2 and 10.1?
10.2 is reactive, triggered by a detected nonconformity. 10.1 is proactive, the ongoing raising of the suitability, adequacy and effectiveness of the PIMS. The same output (a plan change; a control improvement) can come from either, but the trigger differs.
Q13. What is the difference between 10.2 and 6.3?
6.3 is the planned-change clause, the organisation plans a PIMS change in advance. 10.2 is the reactive-change clause, the organisation changes the PIMS in response to a detected nonconformity. A major NC that requires a PIMS change can produce a Clause 6.3 planned-change record linked to the 10.2 NC.
Q14. How do we test the RCA quality?
Through the RCA-toolkit review. For each NC, the method used is named on the worksheet; the method is appropriate to the NC's complexity; the chain of analysis is complete (the 5-Why went five layers deep; the Ishikawa covered the people / process / technology / external dimensions). The certification auditor will read the worksheet and check the depth.
Q15. Our internal audit produced zero findings. Is that good?
It is a red flag, the shallow-audit signature. A zero-finding 9.2 audit programme across multiple cycles signals that the audit work is too shallow to detect nonconformities. The signal is the operational-event-to-NC conversion rate, if operational events are producing NCs that the 9.2 audit did not, the audit missed them.
Industry-Specific Requirements
BFSI
Banks, NBFCs, payment aggregators, payment gateways, insurers. The BFSI corrective-action discipline carries the heaviest regulatory load: the DPDP section 8(5) safeguards dimension (an un-closed NC is a section 8(5) failure); the section 8(6) dual-clock; the section 10 SDF overlay (most large BFSI players are likely SDFs); the RBI Cybersecurity Directions 2026 (31 July 2026), board and senior management accountable for closure of supervisory findings within the agreed timeline; the SEBI CSCRF (20 August 2024) "Learn" function; the IRDAI Information and Cyber Security Guidelines 2023 (24 April 2023), annual compliance report within ninety days of financial year-end including corrective-action status. The BFSI Nonconformity Register is typically integrated with the sector-regulator-mandated NC cycles (RBI inspection findings; SEBI CSCRF findings; IRDAI findings), a single Register with the source-tag dimension. The algorithmic-software NC (on the credit-scoring, fraud-detection or collections engines) is critical for SDFs.
Healthcare
Hospitals, telemedicine platforms, healthtech, insurers processing health data. The corrective-action discipline must surface the heightened sensitivity of health data. The DPIA-pipeline NCs are critical, most material processing activities require DPIA treatment under 8.2. The consent-operation NCs must surface the verifiable-consent dimension where the patient is a minor or a person with disability (DPDP section 9). The cross-border-transfer NCs must surface cross-border affiliate flows (clinical second-opinion services; teleradiology; pharmacovigilance reporting). The rights-operation NCs must surface the patient-rights workflow (access to medical records; correction; the sensitive erasure-versus-retention balance against clinical-record-retention rules). The role declaration is complex, hospitals are controllers for patient data, processors for some insurance-claim data, joint controllers with referring physicians in some cases; role-confusion NCs are common.
IT-ITeS and SaaS
IT services firms, BPOs, SaaS providers, cloud processors. The discipline is almost always "both", the Annex A.1 NCs for the organisation's own employees, marketing-lead contacts and beta-test users (controller-side); the Annex A.2 NCs for the customer's principals reached through the organisation's processing (processor-side). The processor-chain NC (infringing-instruction handling; sub-processor controls; audit-cooperation cycle) is the marquee processor-side NC family. The standalone-PIMS scoping decision lets SaaS firms scope a PIMS to the customer-data plane only. The cross-border transfer NC is central, most ITeS firms process data of overseas principals under GDPR / CCPA jurisdiction; the TIA-currency NC and the SCC-currency NC are dense. The audit-cooperation NC tests whether the organisation responds to customer audits within the contractual clock.
E-commerce and Retail
D2C brands, marketplaces, e-commerce platforms, omni-channel retailers. The discipline must address consumer-privacy expectations at scale; the children's-data regime where minors are in the user base (DPDP section 9, the family-9 NC tests verifiable parental consent and the no-behavioural-monitoring / no-targeted-advertising controls); the marketing-lead consent regime (the family-1 NC tests lead-capture forms against the seven-quality checklist); the supplier-ecosystem processor chains; the payment-data overlays (RBI Tokenisation; the Payment Aggregator obligations). The loyalty programme is typically a joint-controller arrangement under A.1.2.8. The Consent Manager integration (DPDP section 2(1)(g)) is particularly relevant for consumer-facing firms.
Edtech
K-12 platforms, higher-edtech, skilling platforms, test-prep. The children's-data regime (DPDP section 9) is the central corrective-action subject, the principal is a minor, the consent dynamic is parental, and the section 9 verifiable-parental-consent plus no-behavioural-monitoring-or-targeted-advertising regime is load-bearing. The family-9 children-data NC is the densest single NC family in the edtech Register. The DPIA threshold is low, most material processing activities require DPIA treatment under 8.2. The rights-operation NC must surface the parental-rights workflow. The cross-border-transfer NC must surface the cross-border affiliate flows (overseas tutors; overseas content providers; cross-border exam delivery).
Manufacturing
Discrete and process manufacturing, automotive, chemicals, pharma manufacturing. The discipline must address the OT-IT convergence (operational technology systems increasingly connected, with PII exposure in HR, contractor and visitor data), the supply-chain processor ecosystem, and the geopolitical context for cross-border manufacturing data flows. The principal set includes employees, contractors, visitors, customers (where the manufacturer operates a direct-to-customer channel), and patients (for pharma manufacturing with patient-level pharmacovigilance data). The employee-monitoring NC is typically the marquee NC family. The pharmacovigilance NC (for pharma) tests the safety-reporting workflow and the regulator-reporting disciplines. The Register is often lighter on the Annex A.1 / A.2 NC families and heavier on the Annex A.3 security NCs.
Cross-sector patterns
Three patterns recur across sectors and are worth flagging in any 10.2 discipline regardless of industry.
The dual-regulator corrective-action-overlay pattern. BFSI and listed entities carry dual-regulator exposure, DPDP via the Data Protection Board plus the sector regulator (RBI, SEBI, IRDAI). The Register covers both regulatory streams; the dual-clock pattern (CERT-In six hours, DPDP without delay plus a seventy-two-hour detailed report, sector six hours) is the NC test on the breach operation; the sector-regulator NC cycles are coordinated with the 10.2 cycle to avoid duplication.
The SDF section 10 remediation-order overlay pattern. SDFs carry a statutory independent-data-audit obligation under DPDP section 10 on top of the 10.2 obligation. The two cycles are coordinated through the Register's source-tag dimension; the SDF section 10 NCs feed the 10.2 loop; the 10.2 closeout reports feed the SDF section 10 audit cycle.
The AI-driven processing NC pattern. AI-driven processing activities (credit-scoring, marketing-lead scoring, recommendation engines, fraud detection, adaptive learning, algorithmic hiring) require the algorithmic-software review dimension. The family-10 NC tests whether the review is operating as a release gate; whether the review's findings are routed to corrective action; whether the MLOps pipeline integration is operating. For SDFs, the Register tests the Rule 13(3) algorithmic-software dimension specifically.
Maturity Model
Figure · Tiers
Maturity levels for nonconformity and corrective action
- OptimisedContinuous-learning capability.
- ManagedA privacy-programme-corrective-action-l…
- DefinedA structured Nonconformity Register
- ReactiveA Register exists
- InitialNo Nonconformity Register
| Level | Description |
|---|---|
| L1, Initial | No Nonconformity Register, or a Register covering only the certification-audit findings. The corrective action for ninety percent of NCs is "retrained staff" or "rewrote procedure". No RCA toolkit; no effectiveness check; no update to the risk register or the SoA; recurring findings year after year on the same operational area. |
| L2, Reactive | A Register exists but is under-resourced. The family-tagging is partial (only some NCs tagged). The RCA is 5-Why only; the depth is uneven. The effectiveness check is a tick-box. The recurring-pattern rate is rising. The Register is reported to the management review but not to the Audit Committee. The DPBI-direction procedure exists on paper but has not been drilled. |
| L3, Defined | A structured Nonconformity Register with the ten privacy-nonconformity families, the source-tag dimension and the lifecycle-state dimension. The RCA toolkit covers 5-Why, Ishikawa and fault-tree; the worksheets meet the depth bar. The effectiveness-check programme runs on a 30 / 60 / 90-day cadence with the independent verifier. The NC-to-risk-and-SoA update link is operational. The recurring-pattern response triggers structural treatment under Clause 6.3 or Clause 10.1. The Register is reported to the management review and to the Audit Committee. The DPBI-direction procedure is drilled annually. For SDFs, the SDF section 10 remediation-order response is integrated with the 10.2 discipline. |
| L4, Managed | A privacy-programme-corrective-action-literate PIMS. The Register is integrated with the GRC platform's CAPA module; the source coverage is complete (all sources); the RCA toolkit includes the bow-tie and FMEA for high-consequence and process-redesign NCs; the effectiveness check uses the 9.2 internal-audit cycle for material NCs; the recurring-pattern response drives structural treatment; the NC-to-risk-and-SoA update link is verified by the certification auditor at each surveillance. The integrated-with-distinction posture with the ISMS is fully operational. The DPBI-direction drill surfaces operational gaps that drive procedure refinements. The Audit Committee reporting line is mature. |
| L5, Optimised | Continuous-learning capability. The Register is integrated with the GRC platform with automated source-coverage (the 9.1 monitoring KPI misses auto-create NC entries; the 8.x operational events auto-create NC entries through the breach register and the complaint register integrations); the RCA toolkit is calibrated against the certification-audit findings and the regulator-engagement findings (the divergence is the calibration signal); the effectiveness-check programme uses statistical sampling and walk-throughs; the algorithmic-software NC is integrated with the MLOps pipeline for AI-driven activities; the integrated PIMS-plus-ISMS-plus-sector-register programme is fully operational for BFSI and listed entities; the board-visible dashboard is mature; the discipline demonstrably drives every Clause 9.3 decision and every Clause 6.1 risk-register update. For SDFs, the section 10 remediation cycle and the 10.2 cycle are coordinated with shared evidence library and joint reporting. |
Emerging Trends
The Data Protection Board of India's emergence and the corrective-direction cycle. The DPBI, constituted under DPDP section 18, is emerging through 2026 and 2027. Its early orders, its interpretation of the section 27 to 32 corrective-direction powers, and its precedent on the corrective-action-follow-up dimension will reshape the 10.2 landscape. After a complaint or a breach, the DPBI is expected to issue corrective directions that engage the 10.2 loop on the direction itself; the closure status is reportable within prescribed timelines.
The SDF data-audit cycle. Section 10 and Rule 13 apply from 13 May 2027, and the Central Government designates SDFs by notification. Designated SDFs must run the independent data audit every 12 months (Rule 13(1)). The findings that follow engage the 10.2 loop, and the closure status is reported to the independent data auditor at the next audit.
The AI-driven processing NC dimension. The Rule 13(3) algorithmic-software review, the 2025 edition's callout of AI-driven profiling and automated decision-making, and the parallel development of ISO/IEC 42001:2023 are reshaping the 10.2 landscape. For organisations using AI / ML on personal data, the algorithmic-software NC is the highest-use 10.2 family.
The integrated PIMS-plus-ISMS-plus-AI-Management-System corrective-action discipline. The harmonized structure enables integrated 27001 + 27701 + 42001 governance. The corrective-action discipline is the natural point of integration, a unified Nonconformity Register covering all three management systems with the source-tag dimension.
The generative-AI-in-the-corrective-action-function dimension. The use of generative AI inside the corrective-action function (for RCA drafting, plan drafting, effectiveness-check reporting) is a 10.2 trend. The opportunity is efficiency; the risk is over-reliance. The discipline is to use generative AI as a corrective-action assistant, not a replacement, the RCA worksheet still needs the human's analysis and the effectiveness check still needs the human's verification.
The sector-regulator convergence. RBI, SEBI and IRDAI are each tightening their corrective-action expectations (the RBI Cybersecurity Directions 2026; the SEBI CSCRF "Learn" function; the IRDAI ICS 2023 annual compliance report). The DPDP Act sits as a horizontal layer above these sectoral instruments; the 10.2 Register must monitor both the horizontal and the sectoral streams.
The certification-scheme maturation under ISO/IEC 27706:2025. The new PIMS certification-scheme standard (replacing ISO/IEC TS 27006-2:2021) is maturing through 2026 and 2027. The certification-body competence expectations, the impartiality rules, and the NC-management expectations are settling into practice. The 10.2 Register benefits indirectly, the higher the certification-audit quality, the more the 10.2 discipline is held to the same bar.
The board-visible dashboard dimension. Companies Act 2013 section 134(3)(n) and section 177, and SEBI LODR Regulation 21, increasingly frame the corrective-action discipline as a board-level concern. The board-visible dashboard (the open-NC count, the aging profile, the effectiveness rate, the recurring-pattern list, the DPBI-direction status) is the operational expression of the board's risk-management oversight duty. The Audit Committee reporting line is the 2026 / 2027 maturity dimension for listed entities and SDFs.
References and Further Reading
Primary instruments (India). Digital Personal Data Protection Act, 2023 (Act No. 22 of 2023, enacted 11 August 2023), MeitY, in particular sections 8(5) (reasonable security safeguards, the corrective-action discipline is part of the safeguards), 8(6) (breach notification, the dual-clock), 9 (children), 10 (SDF, DPO, SDF DPIA, periodic independent data audit, algorithmic-software review), 11 to 14 (rights), 16 (cross-border negative list), 18 (Data Protection Board of India), 27 to 32 (the Board's inquiry, corrective-direction and penalty powers), 33 + Schedule (penalty maxima up to two hundred and fifty crore rupees for section 8(5) failure; two hundred crore for sections 8(6) and 9; one hundred and fifty crore for section 10). Digital Personal Data Protection Rules, 2025 (notified 13 November 2025), MeitY, Rule 7 (breach intimation without delay, the seventy-two-hour detailed report and format); SDF thresholds and the independent-data-audit cadence; Consent Manager registration conditions; the grievance-redressal response periods. Information Technology Act, 2000, sections 43A, 72A, 70B. IT (Reasonable Security Practices and Procedures and Sensitive Personal Data or Information) Rules, 2011 (notified 11 April 2011). CERT-In Directions 20(3)/2022-CERT-In (28 April 2022), the six-hour clock. RBI Storage of Payment System Data (6 April 2018); RBI Digital Lending Guidelines (2 September 2022); RBI Tokenisation (22 September 2021); RBI Cybersecurity Directions 2026 (31 July 2026), the board and senior management accountability for the closure of supervisory findings. SEBI Cybersecurity and Cyber Resilience Framework (20 August 2024), the "Learn" function. IRDAI Information and Cyber Security Guidelines 2023 (24 April 2023), annual compliance report within ninety days of financial year-end including the status of corrective actions. Companies Act 2013, sections 134(3)(n), 177 (the Audit Committee dimension); SEBI LODR Regulation 21 (the Risk Management Committee dimension).
Primary jurisprudence (India). K.S. Puttaswamy v. Union of India, (2017) 10 SCC 1 (nine-judge Bench, 24 August 2017). Justice K.S. Puttaswamy (Retd.) v. Union of India (Aadhaar), (2019) 1 SCC 1 (five-judge Bench, 26 September 2018).
Primary instruments (global). Regulation (EU) 2016/679 (GDPR), OJ L 119, 4.5.2016, p. 1; application from 25 May 2018, Articles 5(2) (accountability), 24(1) (ongoing-basis controller responsibility), 24(2) (DPO reports to highest management level), 25 (data protection by design and by default), 28(3)(h) (processor audit-cooperation), 32(1)(d) (regular testing, assessing and evaluating), 33 to 34 (breach notification), 35(11) (DPIA review), 58 (supervisory-authority corrective powers, the closest EU analogue to the DPBI section 27 to 32 powers), 83 (fines). EDPB Guidelines 9/2022 on personal data breach notification. NIST Privacy Framework v1.0, NIST.CSWP.01162020, 16 January 2020, the Govern-P function (Monitoring and Review; Risk Management Strategy; Reporting). AICPA, 2017 Trust Services Criteria (with 2022 Points of Focus update), CC4.1, CC4.2 (Monitoring), CC5 (Control Activities), P8.0 (Monitoring for Compliance). Brazil LGPD, Lei nº 13.709/2018. China PIPL, Article 55 (mandatory PIA).
ISO/IEC standards. ISO/IEC 27701:2025 (2nd ed., published 14 October 2025), Clause 10.2 (nonconformity and corrective action); Clause 9.1 (monitoring, the self-detection source); Clause 9.2 (internal audit, the independent-detection source); Clause 9.3 (management review, the closure forum); Clause 6.1.2 / 6.1.3 (privacy risk, updated by 10.2); Clause 6.3 (planned changes, the demarcation); Clause 8.1 / 8.2 / 8.3 (operational processes, the event source); Clause 7.5 (Documented Information, the Register, the RCA worksheets, the effectiveness-check records); Annex A.1 / A.2 / A.3 (the control surface whose NCs 10.2 addresses); Annex B (normative in 2025, the implementation guidance). ISO/IEC 27701:2019 (1st ed., for transition reference). ISO/IEC 27001:2022 Clause 10.2 (infosec nonconformity and corrective action, the integrated-with-distinction partner). ISO/IEC 27002:2022, only 5.34 is PII-specific; 5.35 (independent review) and 5.36 (compliance) are the lineage for the detection dimensions. ISO 19011:2018 (Guidelines for auditing management systems, the audit-follow-up lineage). ISO/IEC 29134:2017 (DPIA guidelines, the source methodology for the family-4 DPIA-pipeline NCs). ISO/IEC 27018:2019 (cloud PII processor, the source methodology for the family-5 processor-chain NCs on cloud processors); ISO/IEC 27017:2015 (cloud security); ISO/IEC 29151 (PII protection code). ISO/IEC 42001:2023 (AI Management System, Clause 10.2 alignment for the AI-driven processing NC dimension). ISO/IEC 27706:2025 (PIMS certification-scheme competence, the standard governing the certification-body's competence for the certification audit; the NC-management discipline). ISO/IEC 17021-1:2015 (universal management-system certification rule-set, the impartiality rules that prohibit the certification body from also providing the corrective-action consulting). ISO/IEC 27006 (current ed.; ISMS certification-body requirements, the partner scheme to 27706). ISO 31000:2018 (risk management, Clause 6 Monitoring and Review function is the structural analogue). ISO 9001:2015 Clause 10.2 (quality-management-system nonconformity and corrective action, the harmonized-structure alignment).
Edition-transition sources (practitioner commentary used as research input). ANAB Heads Up #550 (transition timeline). The 2025 edition's structure, the harmonized-structure alignment of Clause 10.2, the integrated-with-distinction posture, the corrective-action discipline, the NC-to-risk-and-SoA update link, the DPBI corrective-direction response and the SDF section 10 remediation-order response are confirmed from the official 2025 PDF (OCR) and corroborated by tier-1 practitioner commentary. The common-nonconformity patterns (the "retrained staff" corrective-action failure; the no-effectiveness-check failure; the recurring-pattern-without-escalation failure; the no-update failure; the independence failure; the demarcation failure; the source-coverage failure; the DPBI-direction-not-drilled failure) are drawn from tier-1 cert-body practitioner commentary on the canonical "common problems in 27701 certification" catalogue and from the broader ISO-management-system audit-experience base. The ten privacy-nonconformity families (consent, ROPA, rights, DPIA, processor, transfer, breach, privacy-by-design, children, SDF) derive from the Clause 8.1 operational-process taxonomy and the Annex A control themes. All clause text in this guide is paraphrased; the official text is copyrighted by ISO/IEC and has not been reproduced.
This guide is published by Singahi. The ISO/IEC 27701:2025 clause text is copyrighted by ISO/IEC and has not been reproduced; all requirements are paraphrased. Brand names of competitors, cert bodies, and reference books are intentionally omitted. Scenarios are illustrative and should not be attributed to any real organisation.