Ravindra BagaleCourses & study guides मराठी Track your progress

34. Indian Cyber Law and Cyber Crime Awareness

34.4 The Digital Personal Data Protection Act, 2023

By Last updated:

The DPDP Act, 2023 is India's personal data protection law. Its rules (the DPDP Rules) are being brought into force in phases, so check the current status on meity.gov.in.

Term Meaning
Data Principal The person the data is about (you, a customer, a student)
Data Fiduciary The organisation that decides why and how data is processed (a company, an app)
Data Processor A vendor that processes data for the fiduciary (for example a cloud or payroll provider)
Consent Must be free, specific, informed and clear, with an easy way to withdraw
Data Protection Board of India The body that inquires into breaches and imposes penalties

What organisations must do, in short:

  • Collect only what is needed, for a stated purpose, and delete it when no longer needed.
  • Protect it with reasonable security safeguards (everything in Chapters 29–33).
  • Notify the Board and affected people about a personal data breach.
  • Take extra care with children's data (verifiable parental consent).
  • Respect rights of individuals: access, correction, erasure and grievance redressal.

Penalties are large: the Act allows fines of up to ₹250 crore for failing to take reasonable security safeguards (check the Schedule of the Act for each category).

Ravindra Bagale's Tip

Because of DPDP, security is no longer just an IT topic – it has become a business risk. Customer data leaking from a public S3 bucket = a big penalty. So in interviews, say that "Block Public Access" from Chapter 30 is part of legal compliance.

Practice task

For the reels app from Chapter 16, list what personal data it collects (name, email, phone, videos, IP address). For each, write the purpose, where it is stored, who can access it and when it should be deleted. Draft a two-line consent message for the sign-up page.

Extended teaching notes

Why this lesson matters

In India, unauthorised access can be a crime under the IT Act. CERT-In issues directions for certain organisations. The DPDP Act 2023 raises expectations around personal data. When unsure, stop testing and ask.

  • Written permission and exact scope before any test.
  • Report financial fraud quickly via 1930 / cybercrime.gov.in.
  • Preserve evidence (screenshots, IDs, hashes) without altering originals.
  • Bug bounties only on programmes that list the target.

Mini case study

Suppose we are on a purple-team exercise for an Indian mid-size company (sample data). Red notes a technique from this lesson against a lab clone. Blue must show the control that stops it, the log that would have fired, and the ticket that hardens production. That is the standard this course trains you for.

Defender's worksheet (do this today)

  1. Write the lesson title, date and the exact lab target you are allowed to use.
  2. List three owned systems (VMs, apps, or cloud accounts) where this lesson applies.
  3. Run one safe check from the lesson on a lab system only. Paste the command and output.
  4. Write a two-sentence fix you would give a teammate.
  5. Name one related public advisory (CERT-In, CISA, NVD, or a vendor bulletin) with its date.

Indian workplace (sample data)

Suppose we are a junior analyst at Infosys, TCS, Wipro or a fintech SOC in Bengaluru/Pune. Turn this lesson into one checklist item with an owner, a due date and a place to store evidence (ticket + screenshot).

Global practice

Compare your notes with OWASP, CIS Benchmarks, NIST CSF/IR guidance or a cloud Well-Architected security question. Write five lines on what overlaps.

Everyday analogy

Explain the risk and the fix to a family member without jargon. If they can repeat the warning, you understand it well enough to teach juniors.

Key terms

  • Control: a safeguard (patch, config, process, detection).
  • Finding: a weakness backed by evidence.
  • Remediation: the fix plus how you verified it.
  • Scope: systems you have written permission to touch.
  • Least privilege: only the access the task needs.
  • Defence in depth: several layers so one failure does not end the story.

Common mistakes

  • Skipping written permission "just for a quick scan".
  • Practising on hostel, office or public targets without authorisation.
  • Collecting tool output without writing the fix.
  • Copying attack steps onto production to "verify". Defenders verify with versions, configs and patches.
  • Publishing screenshots that contain secrets, cookies or internal hostnames.

Recap

  • Evidence, fix, owner, date.
  • Own lab only.
  • Fix > spectacle.