A company certified to ISO/IEC 27001 has a management system for information security. One certified to ISO/IEC 27701 as well has extended it to privacy. Neither certificate is recognised by the DPDP Act as proof of compliance — but between them they cover a large share of what the Act requires, and the evidence they generate is the evidence the Board would ask for.
What maps, and what does not
| DPDP requirement | ISO 27001 | ISO 27701 | Still to do |
|---|---|---|---|
| Security safeguards | Largely covered | Covered | Check log retention is at least a year |
| Breach handling | Incident management process | Privacy breach handling | Add the two DPDP notices and the 72-hour report |
| Processor contracts | Supplier relationships | Processor agreements | Add DPDP-specific clauses |
| Data inventory | Asset inventory | Personal data mapping | Confirm it covers every system |
| Retention and erasure | Partly | Covered | Set and operate the periods |
| Notice and consent | Not covered | Principles covered | Build the notice and consent mechanism |
| Individual rights | Not covered | Covered in principle | Operate a request and grievance channel to 90 days |
| Children’s data | Not covered | Not specifically | Age and parental consent, if relevant |
| Training and awareness | Covered | Covered | Add DPDP content |
| Audit and review | Covered | Covered | Include DPDP obligations in the audit scope |
What certification really gives you
Less the controls than the habit. A certified organisation already keeps a risk register, records incidents, reviews suppliers, trains staff, audits itself and holds management reviews — and keeps the minutes. When the question is “show us”, it has something to show.
Where certified companies get caught
- Scope. The certificate covers a defined scope; personal data outside it is not protected by it.
- Logs kept for ninety days because nothing asked for more.
- A breach procedure that reports to the customer but not to the affected individuals or the Board.
- Consent, which the standards treat as a principle and the Act treats as a mechanism.
A practical order of work
- Extend the scope statement, or confirm it covers every system with personal data.
- Add the DPDP obligations to the legal register and the risk register.
- Amend the incident procedure and the supplier agreement template.
- Add DPDP to the internal audit programme and the management review agenda.
- Treat notice, consent and rights as a separate project owned by the product team.
- Does ISO 27001 certification mean DPDP compliance?
- No. It covers most security safeguards but not notice, consent or individual rights.
- Is ISO 27701 required by the DPDP Act?
- No. It is voluntary, but it is the closest standard to what the Act expects of a privacy programme.
- Will the Board accept a certificate as a defence?
- The Act does not provide for that. A certificate is evidence that safeguards exist and are reviewed.
- What is the biggest gap for a certified company?
- Usually breach notification to individuals, log retention, and the consent mechanism.
This is a working summary for people who have to act on the law, not legal advice. Read the Act and the Rules, and take advice on your own facts.