DPDP Data Fiduciary Security Safeguards for SaaS Teams

DPDP Data Fiduciary Security Safeguards for SaaS Teams

3 min read

DPDP · data fiduciary · SaaS · security · India

Authors

PandaONE Team

Under India’s DPDP Act, data fiduciaries must implement reasonable security safeguards and notify on breaches. What that means for SaaS auth, APIs, and proof — not just policies.

A tenant pulls another customer's export because org_id was not checked on the download route. That is a security bug. Under DPDP it is also a fiduciary failure.

Under the Digital Personal Data Protection Act, 2023, a Data Fiduciary (s.2(i)) is any person who alone or with others determines the purpose and means of processing personal data. If you run a SaaS product that decides why and how customer or employee personal data is processed, that language is aimed at you.

Primary text: DPDP Act PDF (MeitY). Consent Managers (now registering — portal explainer) do not replace fiduciary duties.

What the Act requires of fiduciaries (security-relevant)

From Chapter II, especially section 8:

ObligationAct hook
Reasonable security safeguards to prevent personal data breachs.8(5)
Intimation of breach to the Board and each affected Data Principals.8(6)
Appropriate technical and organisational measuress.8(4)
Erasure when consent withdrawn / purpose done (unless law requires retention)s.8(7)
Processor only under a valid contracts.8(2)
Completeness/accuracy when data drives decisions or is shareds.8(3)
Contact person / DPO publish + grievance mechanisms.8(9)–(10)

Children (s.9): verifiable parental/guardian consent; no tracking, behavioural monitoring, or targeted ads directed at children (with prescribed exceptions).

Significant Data Fiduciary (s.10): if notified — India-based DPO, independent auditor, DPIA, periodic audit.

Penalties (Schedule): failure of reasonable security safeguards under s.8(5) may extend to ₹250 crore; failure to notify breach under s.8(6) may extend to ₹200 crore. Amounts are Board-determined with gravity/mitigation factors (s.33).

What that means in practice for SaaS

Lawyers will argue the edges. Engineers ship the middle:

Control areaFiduciary-relevant failure mode
Access controlIDOR / broken object auth → one tenant reads another’s PII
AuthnSession fixation, missing MFA on admin, token leakage
ExposureDebug endpoints, open buckets, verbose errors with PII
InjectionSQLi / XSS turning into data theft
SecretsKeys in repos, over-broad cloud IAM
RetentionBackups that never honor erasure

If an attacker can pull personal data without authorization, your privacy program failed and your security program failed — same incident.

Breach notification is a security workflow

DPDP expects fiduciaries to notify the DPBI and affected individuals on personal-data breaches under the prescribed framework. That requires:

  1. Detection — logs, alerts, anomaly signals on data stores and APIs
  2. Containment — revoke tokens, rotate keys, patch the hole
  3. Evidence — what was accessed, for how long, whose records
  4. Notification — counsel + ops RACI, not improvisation at 2 a.m.

Point-in-time VAPT helps; continuous testing of PII-bearing surfaces helps more. See proof-backed findings and the May 2027 checklist.

Children’s data

Where you process data of children (under 18 in the Act’s framing), expect verifiable parental consent and limits on tracking / behavioural advertising. Age gates that are cosmetic fail both privacy and security review.

A 30-day security plan for fiduciaries

  1. List top 5 apps/APIs that return personal data.
  2. Run authenticated testing focused on authz and exposure (not only CVE scans).
  3. Fix Critical/High with retest — AI Security Engineer.
  4. Wire breach on-call + draft notification template with counsel.
  5. Confirm erasure path hits primary DB and known replicas/export jobs.

India buyers

Teams preparing SOC 2 / customer DDQs and DPDP readiness often need both continuous offensive coverage and a human-readable report story. Context: VAPT India.

DPDP does not invent the need for strong authz — it raises the cost of ignoring it. Consent Managers are infrastructure for consent; fiduciaries still secure the data.

Further reading: Consent Manager registration, Inc42 reporting.

Sources & further reading

Featured on ScrollLaunchFeatured on CodeHype