{"id":9066,"date":"2026-11-16T15:51:16","date_gmt":"2026-11-16T10:21:16","guid":{"rendered":"https:\/\/www.anakage.com\/blog\/?p=9066"},"modified":"2026-11-16T15:51:16","modified_gmt":"2026-11-16T10:21:16","slug":"dpdp-compliance-checklist-it-teams","status":"publish","type":"post","link":"https:\/\/www.anakage.com\/blog\/dpdp-compliance-checklist-it-teams\/","title":{"rendered":"DPDP Compliance Checklist for IT Teams (May 2027)"},"content":{"rendered":"<p dir=\"ltr\">A DPDP compliance checklist for IT teams has 12 steps, and all of them must work by 13 May 2027. The core IT duties are encryption, access control, one year of logs, backups, processor contracts and 72-hour breach reporting. Start with a personal data map and central logging, because you cannot create old logs later.<\/p>\n<h2 dir=\"ltr\">When Does DPDP Compliance Start for IT Teams?<\/h2>\n<p dir=\"ltr\">Most DPDP duties start on 13 May 2027. The Digital Personal Data Protection Rules, 2025 (G.S.R. 846(E)) arrived in November 2025 and roll out in three phases.<\/p>\n<ol dir=\"ltr\">\n<li><strong>13 November 2025:<\/strong> The Data Protection Board provisions took effect.<\/li>\n<li><strong>13 November 2026:<\/strong> Rule 4 on Consent Managers started. Most businesses have no action here.<\/li>\n<li><strong>13 May 2027:<\/strong> Rules 3, 5 to 16, 22 and 23 start. These cover notice, security safeguards, breach reporting, erasure and rights.<\/li>\n<\/ol>\n<p dir=\"ltr\">As of 16 November 2026, about 25 weeks remain. Some law firms print 14 May 2027, because the Gazette carried the Rules a day later. We plan to the earlier date.<\/p>\n<blockquote dir=\"ltr\">\n<p dir=\"ltr\"><strong>Data Fiduciary<\/strong> \u2014 the organisation that decides why and how personal data is processed. That is usually your company.<\/p>\n<\/blockquote>\n<blockquote dir=\"ltr\">\n<p dir=\"ltr\"><strong>Data Principal<\/strong> \u2014 the individual whose personal data is processed. That means customers, employees and contractors.<\/p>\n<\/blockquote>\n<p dir=\"ltr\">In January 2026, MeitY floated a cut from 18 months to 12. Reports differ on whether it covered everyone or only Significant Data Fiduciaries. We found no notified amendment through October 2026.<\/p>\n<p dir=\"ltr\">Plan for 13 May 2027 and keep a contingency plan for an earlier date. Trackers also report that the Data Protection Board has no appointed Chairperson or Members as of early November 2026. The Rules set the commencement date, so that gap does not move your deadline.<\/p>\n<h2 dir=\"ltr\">What Does DPDP Rule 6 Require for Security Safeguards?<\/h2>\n<p dir=\"ltr\">Rule 6 lists seven minimum safeguards. Each one maps to a task your team owns and a record an auditor reads.<\/p>\n<blockquote dir=\"ltr\">\n<p dir=\"ltr\"><strong>Personal data breach<\/strong> \u2014 any event that compromises the confidentiality, integrity or availability of personal data.<\/p>\n<\/blockquote>\n<div dir=\"ltr\">\n<table>\n<thead>\n<tr>\n<th scope=\"col\">Rule 6(1)<\/th>\n<th scope=\"col\">What it requires<\/th>\n<th scope=\"col\">IT task<\/th>\n<th scope=\"col\">Evidence to keep<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>(a)<\/td>\n<td>Encryption, masking, obfuscation or virtual tokens<\/td>\n<td>Encrypt at rest and in transit; mask test copies<\/td>\n<td>Key inventory, masking rules<\/td>\n<\/tr>\n<tr>\n<td>(b)<\/td>\n<td>Control access to computer resources<\/td>\n<td>SSO, MFA, role-based access, leaver process<\/td>\n<td>Access review records<\/td>\n<\/tr>\n<tr>\n<td>(c)<\/td>\n<td>Logs, monitoring and review of access<\/td>\n<td>Send logs to one store; set alert rules<\/td>\n<td>Log source list, alert rules<\/td>\n<\/tr>\n<tr>\n<td>(d)<\/td>\n<td>Keep processing going after a compromise<\/td>\n<td>Isolated backups; scheduled restore tests<\/td>\n<td>Restore test records<\/td>\n<\/tr>\n<tr>\n<td>(e)<\/td>\n<td>Keep logs and personal data for one year<\/td>\n<td>Set retention; size storage<\/td>\n<td>Retention settings<\/td>\n<\/tr>\n<tr>\n<td>(f)<\/td>\n<td>Security terms in processor contracts<\/td>\n<td>Add clauses to every contract<\/td>\n<td>Signed clause list<\/td>\n<\/tr>\n<tr>\n<td>(g)<\/td>\n<td>Technical and organisational measures<\/td>\n<td>Name owners; train staff; review<\/td>\n<td>Owner list, review calendar<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<p dir=\"ltr\">The Rules define &#8220;computer resource&#8221; through the IT Act, 2000. We read that to include laptops, desktops and servers.<\/p>\n<p dir=\"ltr\">These are floors. What counts as reasonable also grows with the volume and sensitivity of your data.<\/p>\n<h2 dir=\"ltr\">DPDP Compliance Checklist for IT Teams: 12 Steps Before May 2027<\/h2>\n<p dir=\"ltr\">Work through four groups of steps. Each group ends with proof you can show an auditor.<\/p>\n<h3 dir=\"ltr\">Know Your Data<\/h3>\n<ol dir=\"ltr\">\n<li><strong>Build a personal data map.<\/strong> List every system, spreadsheet, SaaS tool, backup and log store that holds personal data. Record the purpose, owner, location and retention period.<\/li>\n<li><strong>Inventory every endpoint and server.<\/strong> Include offline machines and employee-owned devices that reach personal data. You cannot encrypt or patch a device you do not know about.<\/li>\n<li><strong>Name an owner for each system.<\/strong> Each owner answers for controls and evidence. Also pick the business contact you will publish for privacy questions.<\/li>\n<\/ol>\n<h3 dir=\"ltr\">Lock It Down<\/h3>\n<ol dir=\"ltr\" start=\"4\">\n<li><strong>Encrypt and mask.<\/strong> Encrypt data at rest and in transit. Mask personal data in test and development copies, and tokenise identifiers where you can.<\/li>\n<li><strong>Tighten access.<\/strong> Use SSO and MFA, apply role-based access, and remove shared and dormant accounts. Run and record a quarterly access review.<\/li>\n<li><strong>Patch and harden.<\/strong> Rule 6 never names patching. We still expect auditors to ask why a vulnerable machine held personal data. On offline networks, patch through an internal WSUS server.<\/li>\n<li><strong>Back up and test restores.<\/strong> Keep one isolated copy. Restore one personal data system, record the time taken and fix the gaps.<\/li>\n<\/ol>\n<h3 dir=\"ltr\">Prove It<\/h3>\n<ol dir=\"ltr\" start=\"8\">\n<li><strong>Centralise logs for one year.<\/strong> Send access logs from every system on your data map to one store in India. Sync all clocks to NIC or NPL time so logs line up during an incident.<\/li>\n<li><strong>Update processor contracts.<\/strong> Add the Rule 6(1)(f) security clauses. Require one-year log retention and breach notice fast enough for your 72-hour report.<\/li>\n<li><strong>Automate retention and erasure.<\/strong> Schedule erasure jobs per dataset and document how deletion works in backups. Build one workflow that finds a person&#8217;s records across systems. Answer requests within your published period, which cannot exceed 90 days.<\/li>\n<\/ol>\n<h3 dir=\"ltr\">Respond<\/h3>\n<ol dir=\"ltr\" start=\"11\">\n<li><strong>Write and rehearse a breach playbook.<\/strong> Name who decides a breach has happened, who notifies people and who drafts the Board report. Time one rehearsal against the 72-hour clock.<\/li>\n<li><strong>Train staff and review.<\/strong> Train IT, HR and support teams on handling personal data. Set a review calendar and keep a record of every control test.<\/li>\n<\/ol>\n<h2 dir=\"ltr\">How to Meet DPDP Breach Notification Rules in 72 Hours<\/h2>\n<p dir=\"ltr\">Rule 7 runs two clocks at once. You tell each affected Data Principal without delay, and you tell the Board in two stages.<\/p>\n<p dir=\"ltr\">The Board gets a description of the breach without delay. A detailed report follows within 72 hours of you becoming aware, unless the Board allows longer on written request.<\/p>\n<p dir=\"ltr\">The detailed report has six parts. They cover updated facts, causes, mitigation, findings on who caused it, remedial measures and a report on your notices. Several law firm analyses note that India sets no materiality threshold, so every breach is reportable.<\/p>\n<p dir=\"ltr\">CERT-In runs a separate clock. Its 2022 Directions require reporting of listed incidents within 6 hours. One incident can trigger both.<\/p>\n<p dir=\"ltr\">Use this sequence when a breach happens:<\/p>\n<ol dir=\"ltr\">\n<li>Contain the affected systems and preserve their logs.<\/li>\n<li>Report to CERT-In within 6 hours if the incident is on its list.<\/li>\n<li>Send the Board its first description without delay.<\/li>\n<li>Notify each affected Data Principal in plain language.<\/li>\n<li>File the detailed six-part report within 72 hours.<\/li>\n<\/ol>\n<h2 dir=\"ltr\">How Long Must You Keep Logs Under DPDP and CERT-In?<\/h2>\n<p dir=\"ltr\">Keep logs and related personal data for at least one year under DPDP, unless another law needs longer. CERT-In also wants logs of all ICT systems for a rolling 180 days, stored in India.<\/p>\n<p dir=\"ltr\">One log store in India with one-year retention meets both rules. Set it up first, because you cannot recreate missing history after a breach.<\/p>\n<p dir=\"ltr\">The one-year floor also conflicts with aggressive erasure schedules. Reconcile your retention policy and your security policy in one document, written by one team.<\/p>\n<h2 dir=\"ltr\">How Do Endpoints Fit Into DPDP Compliance?<\/h2>\n<p dir=\"ltr\">Personal data lands on laptops through downloads, exports, email caches and local files. So Rule 6 evidence includes endpoint facts. These are encryption status, patch level, installed software and logins.<\/p>\n<p dir=\"ltr\">Cloud-managed tools work well for connected fleets. Microsoft Intune, Scalefusion and ManageEngine Endpoint Central cover managed devices, and Lansweeper adds discovery. Configuration Manager (SCCM) still serves many Windows estates.<\/p>\n<p dir=\"ltr\">Offline and air-gapped networks need a different design, because cloud tools cannot see them. Anakage is one option worth considering.<\/p>\n<p dir=\"ltr\">It runs on-premise and keeps data inside your perimeter. Its agents inventory endpoints and check antivirus, firewall, disk encryption and patch status.<\/p>\n<p dir=\"ltr\">One Indian private bank used it to reach 99% endpoint compliance and cut manual effort by 85%. That result covers endpoint compliance, not DPDP specifically.<\/p>\n<p dir=\"ltr\">It has limits. It does not find personal data inside files, manage consent or file breach reports.<\/p>\n<p dir=\"ltr\">It does not scan your network for unmanaged devices, so pair it with a network scanner. It also does not suit small businesses, cloud-first teams or teams that need free tools.<\/p>\n<p dir=\"ltr\">On-premise helps in one way. Fewer processors touch your data, so fewer Rule 6(1)(f) contracts need chasing. It does not remove any DPDP duty.<\/p>\n<h2 dir=\"ltr\">What Are the DPDP Penalties for Non-Compliance?<\/h2>\n<p dir=\"ltr\">The Act sets maximum penalties by type of failure. Penalties follow a Board inquiry and are not automatic.<\/p>\n<div dir=\"ltr\">\n<table>\n<thead>\n<tr>\n<th scope=\"col\">Failure<\/th>\n<th scope=\"col\">Maximum penalty<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>No reasonable security safeguards<\/td>\n<td>\u20b9250 crore<\/td>\n<\/tr>\n<tr>\n<td>No breach notice to the Board or individuals<\/td>\n<td>\u20b9200 crore<\/td>\n<\/tr>\n<tr>\n<td>Breach of children&#8217;s data duties<\/td>\n<td>\u20b9200 crore<\/td>\n<\/tr>\n<tr>\n<td>Breach of Significant Data Fiduciary duties<\/td>\n<td>\u20b9150 crore<\/td>\n<\/tr>\n<tr>\n<td>Any other breach of the Act or Rules<\/td>\n<td>\u20b950 crore<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<blockquote dir=\"ltr\">\n<p dir=\"ltr\"><strong>Significant Data Fiduciary<\/strong> \u2014 an organisation the Government notifies because of its data volume, sensitivity or risk.<\/p>\n<\/blockquote>\n<p dir=\"ltr\">If the Government notifies you, you must appoint an India-based DPO and an independent auditor. You must also run an annual impact assessment and audit.<\/p>\n<h2 dir=\"ltr\">What Should Banks, NBFCs and Manufacturers Check First?<\/h2>\n<p dir=\"ltr\">Banks and NBFCs should map DPDP against RBI rules before May 2027. Sector regulators such as RBI, SEBI and IRDAI run their own reporting clocks, so confirm them with your compliance team.<\/p>\n<p dir=\"ltr\">KYC and anti-money-laundering rules require long retention. DPDP erasure yields where another law requires retention. Document each exception, with the law that justifies it.<\/p>\n<p dir=\"ltr\">Manufacturers should look at shop-floor PCs and offline plant networks. These machines hold employee and contractor data, and they often miss patches and log retention.<\/p>\n<p dir=\"ltr\">Employee data needs care too. Section 7(i) lets employers process data for employment purposes without fresh consent. It does not cover unlimited monitoring, and notice and security duties still apply.<\/p>\n<p dir=\"ltr\">Ask counsel before you switch on endpoint monitoring.<\/p>\n<h2 dir=\"ltr\">A 25-Week Plan to Reach 13 May 2027<\/h2>\n<p dir=\"ltr\">This plan starts on 16 November 2026. Shift the dates if you start later.<\/p>\n<ol dir=\"ltr\">\n<li><strong>16 November to 13 December:<\/strong> Finish the data map and the endpoint and server inventory. Turn on logging and sync clocks.<\/li>\n<li><strong>14 December to 24 January:<\/strong> Roll out SSO and MFA, finish the access review and fix encryption gaps. Stand up the one-year log store.<\/li>\n<li><strong>25 January to 7 March:<\/strong> Run a restore test, update processor contracts and build the retention and erasure jobs.<\/li>\n<li><strong>8 March to 11 April:<\/strong> Rehearse a breach, launch the rights request workflow and train staff.<\/li>\n<li><strong>12 April to 12 May:<\/strong> Build the evidence pack, run a gap review and freeze changes.<\/li>\n<\/ol>\n<h2 dir=\"ltr\">FAQ<\/h2>\n<p dir=\"ltr\"><strong>Q: When does the DPDP Act come into force for businesses?<\/strong><\/p>\n<p dir=\"ltr\">A: Most duties start on 13 May 2027. That covers notice, security safeguards, breach reporting and erasure. Some law firms print 14 May 2027, so plan to the earlier date.<\/p>\n<p dir=\"ltr\"><strong>Q: What security safeguards does DPDP Rule 6 require?<\/strong><\/p>\n<p dir=\"ltr\">A: Rule 6 lists seven minimums. They are encryption or masking, access control, logging and monitoring, backups, one-year log retention, processor contract terms and supporting controls. They are floors, not a full programme.<\/p>\n<p dir=\"ltr\"><strong>Q: How long do we need to retain logs under DPDP?<\/strong><\/p>\n<p dir=\"ltr\">A: Keep logs and related personal data for at least one year, unless another law requires longer. CERT-In also requires 180 days of ICT logs in India. One store set to one year covers both.<\/p>\n<p dir=\"ltr\"><strong>Q: How quickly must we report a data breach under DPDP?<\/strong><\/p>\n<p dir=\"ltr\">A: Tell the Board and each affected person without delay. Send the Board a detailed report within 72 hours of becoming aware. CERT-In&#8217;s 6-hour clock runs separately.<\/p>\n<p dir=\"ltr\"><strong>Q: What is the penalty for DPDP non-compliance?<\/strong><\/p>\n<p dir=\"ltr\">A: Failing to keep reasonable security safeguards can cost up to \u20b9250 crore. Failing to notify a breach can cost up to \u20b9200 crore. Penalties follow a Board inquiry.<\/p>\n<p dir=\"ltr\"><strong>Q: Does DPDP apply to employee data and internal IT systems?<\/strong><\/p>\n<p dir=\"ltr\">A: Yes. The Act covers digital personal data of any individual, including employees. Section 7(i) allows employment-related processing without fresh consent, but security, notice and erasure duties still apply.<\/p>\n<p dir=\"ltr\"><strong>Q: Do on-premise or air-gapped systems fall under DPDP?<\/strong><\/p>\n<p dir=\"ltr\">A: Yes. The Act applies to digital personal data wherever you store it. Offline systems still need access control, encryption, one year of logs and a tested breach plan.<\/p>\n<p dir=\"ltr\"><strong>Q: Do we need to appoint a DPO?<\/strong><\/p>\n<p dir=\"ltr\">A: Only Significant Data Fiduciaries must appoint an India-based DPO. Every other fiduciary must publish a business contact who can answer privacy questions.<\/p>\n<p dir=\"ltr\">DPDP compliance for IT comes down to four things. Build a data map, keep one year of logs, test backups and rehearse a 72-hour breach plan. Finish those first, then close the rest before 13 May 2027.<\/p>\n<p dir=\"ltr\">If your environment runs on-premise or offline, Anakage offers a free 30 minute demo worth checking at <a href=\"https:\/\/anakage.com\/book-a-demo\" target=\"_blank\" rel=\"noopener\">anakage.com\/book-a-demo<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>A DPDP compliance checklist for IT teams has 12 steps, and all of them must work by 13 May 2027. [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":9067,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_themeisle_gutenberg_block_has_review":false,"footnotes":""},"categories":[278],"tags":[],"coauthors":[88],"class_list":["post-9066","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-end-point-compliance-non-compliance-detection-and-remediation"],"views":24,"_links":{"self":[{"href":"https:\/\/www.anakage.com\/blog\/wp-json\/wp\/v2\/posts\/9066","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.anakage.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.anakage.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.anakage.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.anakage.com\/blog\/wp-json\/wp\/v2\/comments?post=9066"}],"version-history":[{"count":1,"href":"https:\/\/www.anakage.com\/blog\/wp-json\/wp\/v2\/posts\/9066\/revisions"}],"predecessor-version":[{"id":9068,"href":"https:\/\/www.anakage.com\/blog\/wp-json\/wp\/v2\/posts\/9066\/revisions\/9068"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.anakage.com\/blog\/wp-json\/wp\/v2\/media\/9067"}],"wp:attachment":[{"href":"https:\/\/www.anakage.com\/blog\/wp-json\/wp\/v2\/media?parent=9066"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.anakage.com\/blog\/wp-json\/wp\/v2\/categories?post=9066"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.anakage.com\/blog\/wp-json\/wp\/v2\/tags?post=9066"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/www.anakage.com\/blog\/wp-json\/wp\/v2\/coauthors?post=9066"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}