Skip to main content
DPDP-AID Readiness Checkby

Security safeguards

Reasonable security safeguards are required of every data fiduciary, whatever its size. This area carries the highest penalty ceiling in the Schedule to the Act.

Reviewed 16 September 2026Educational self-assessment content, not legal advice

Requirements
7
Must-do
6
Penalty ceiling
Up to ₹250 crore

Failure to take reasonable security safeguards. This is a statutory maximum the Data Protection Board applies case by case, never a predicted fine. 2 of these requirements are in the quick check. A must-do gap left at not started in this area caps your readiness band.

What we assess in this area

  1. MustIn the quick checkSEC-01

    Encryption, masking, obfuscation or tokenisation protects personal data

    You must take reasonable security safeguards to prevent personal data breaches. Encryption, masking, obfuscation or tokenisation are among the measures expected, so that data is not readable if it is exposed.

    What good looks like

    Personal data is encrypted in storage and in transit. Sensitive fields are masked or tokenised in applications, reports and test systems. Encryption keys are managed and access to them is limited.

    How to get there

    List systems that store personal data. Turn on encryption at rest and in transit where missing. Mask personal data in non-production copies. Record who can access encryption keys.

  2. MustIn the quick checkSEC-02

    Access is least-privilege and reviewed regularly

    Only people who need personal data for their work should be able to reach it. Controlling access is a basic safeguard, and it limits the damage if an account is misused.

    What good looks like

    Access to personal data is granted by role, approved by an owner and removed promptly when people move or leave. Access lists are reviewed on a fixed schedule and exceptions are recorded.

    How to get there

    List who can access each system holding personal data. Remove access that is not needed. Set up role-based access and multi-factor login. Schedule quarterly access reviews with named owners.

  3. MustSEC-03

    Access is logged and monitored, with logs kept for the prescribed period

    You should keep logs of who accessed personal data and when, and watch them for misuse. The Rules expect these logs to be kept for a minimum period so breaches can be detected and investigated.

    What good looks like

    Access to personal data is logged in every key system. Logs are protected from change, monitored for unusual activity and kept for at least the period set in the Rules.

    How to get there

    Turn on access logging in systems that hold personal data. Send logs to a central, protected store. Set alerts for unusual access. Configure retention to meet the period set in the Rules.

  4. MustSEC-04

    Backups and continuity plans protect personal data

    Safeguards include keeping personal data available and intact if systems fail or are attacked. Backups and continuity plans help you recover data without losing it or exposing it.

    What good looks like

    Personal data is backed up on a set schedule, backups are encrypted and access is limited. Restores are tested regularly, and a continuity plan names who does what during an outage.

    How to get there

    Confirm which systems holding personal data are backed up. Encrypt backups and restrict access. Test a restore this quarter. Write or update a short continuity plan with named roles.

  5. MustSEC-05

    Processor contracts carry security obligations

    You stay responsible for personal data that processors handle for you. Your contracts should require processors to protect the data with reasonable security safeguards and to tell you quickly about breaches.

    What good looks like

    Every processor contract sets clear security duties, breach reporting timelines, audit rights and data return or deletion at the end. Contracts are checked before signing and at renewal.

    How to get there

    List processors that handle personal data. Check each contract for security and breach clauses. Add a standard data protection schedule for gaps. Track renewals so missing clauses are fixed.

  6. ShouldSEC-06

    Security is tested periodically, for example through VAPT

    Safeguards need to be checked to show they work. Regular testing, such as vulnerability assessment and penetration testing, helps you find weaknesses before attackers do.

    What good looks like

    Systems that hold personal data are tested on a fixed schedule and after major changes. Findings are tracked to closure with owners and dates, and results are reported to leadership.

    How to get there

    List systems holding personal data by risk. Plan a yearly test for each, and more often for high risk systems. Appoint a qualified tester. Track every finding until it is fixed.

  7. MustSEC-07

    A documented security programme with reasonable safeguards across people, process and technology

    The law expects reasonable security safeguards to prevent personal data breaches. Specific controls work best inside a written programme that sets owners, standards and reviews, so nothing depends on one person's memory.

    What good looks like

    A written security programme covers policies, risk assessment, controls, vendor security and incident response. Leadership approves it. Owners are named, and it is reviewed at least once a year and after any major incident.

    How to get there

    Write down the security controls you already run. Compare them against a known framework such as ISO 27001. Name an owner for each gap. Get leadership sign-off and set a yearly review.

Other areas we assess

All 13 areas

Check this area against your own business

The free assessment scores this area with the rest and shows you where it ranks against your other gaps.

The DPDP-AID Readiness Check is a free self-assessment tool for educational and self-learning purposes. It is not legal advice. Disclaimer

A free self-assessment tool for educational use. Not legal advice.