India DPDP Act 2023·Control SC-002·critical·Component: Scope & Classification

What this control requires

Define and document the categories of data principals (individuals, children under 18, persons with disability, guardians). Implement and maintain mechanisms to identify child/disabled data principals and obtain verifiable parental/guardian consent before processing their data. Objective: Ensure only lawful processing of personal data of children and disabled persons, with verifiable consent obtained prior to any processing.
— India DPDP Act 2023, Control SC-002

In plain English

Define and document the categories of data principals (individuals, children under 18, persons with disability, guardians). In practice, this means you can prove you maintain data principal identification-level controls on a defined cadence.

Why it matters

Penalties under the DPDP Act reach ₹250 crore per instance of significant non-compliance, and the Act applies extra-territorially to any entity processing personal data of individuals in India in connection with offering goods or services.

This control is rated critical in the source catalogue. Treat gaps here as production incidents in the risk register, not housekeeping.

What an auditor looks for

Indian DPAs and statutory auditors will look for: documented consent capture and revocation flows, a designated Data Protection Officer (for Significant Data Fiduciaries), breach-notification workflows tied to Data Protection Board notification timelines, and Records of Processing that match the consent notice the user saw.

Within Scope & Classification, the assessor will trace your implementation back to the catalogue reference (Control SC-002) and look for objective evidence on the latest two assessment cycles.

How to implement

Policy Management

Docs. Keep each policy in version-controlled Markdown alongside the code that implements it; ship a signed PDF snapshot at each annual review and link the SHA into the SoA.

Asset Inventory

AWS. AWS Config Aggregator across every account + region gives a real-time inventory; ship the daily snapshot to S3 and surface drift in Security Hub.

Azure. Azure Resource Graph plus Defender for Cloud's inventory blade enumerates every subscription; export to Log Analytics for retention and Workbooks for reporting.

GCP. Cloud Asset Inventory exports a daily feed of every resource and IAM binding; query via BigQuery and alert on appearance/disappearance.

Endpoints. Pipe MDM telemetry (Intune / Jamf / Workspace ONE) into your CMDB so laptops and phones are inventoried with the same rigour as cloud resources.

Operational checklist

  • Maintain. Document the trigger, the owner and the cadence.
  • Implement. Document the trigger, the owner and the cadence.
  • Define. Document the trigger, the owner and the cadence.
  • Scope: data principal identification, guardian consent management.

Evidence to collect

  • Policy Document. A signed and version-controlled policy / standard / procedure document.

Signed policies, procedures, and registers document the safeguard. Focus: Data Principal Identification & Guardian Consent Management.

Common pitfalls

  • Policies that no engineer has read; the version in Confluence drifts from the version that's actually being enforced.
  • Inventories that exclude SaaS, shadow IT and ephemeral cloud resources (Lambda, Cloud Run, K8s pods) miss the assets where most modern incidents start.

How it maps to other frameworks

Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit.

Related controls in India DPDP Act 2023

References

Topics: governance riskdata protectionprivacy managementpolicy managementasset inventory