GRC · Service
ISO 27701 privacy management
Certify how you handle personal data, with each control mapped to DPDP and GDPR.
What it covers
What an ISO 27701 privacy management system is
ISO/IEC 27701 is the international standard for a privacy information management system, or PIMS: the roles, privacy risk assessment, controls and records a company runs to handle personal data as a controller, a processor or both. The 2025 edition stands on its own, so it can be certified without ISO 27001, though it is written to sit beside it.
You end up with a PIMS that gives each privacy duty an owner, a control and evidence, with each control mapped to the DPDP Act 2023 and the GDPR. Once an accredited certification body has audited it, you hold a certificate. European and multinational customers rely on it when they check their processors under Art. 28 GDPR.
You need it when
- A European customer's data processing agreement, or its Art. 28 GDPR due diligence, asks how you govern the personal data you process for it.
- You hold ISO 27001, and customers now ask for its privacy counterpart.
- You are preparing for the DPDP duties that apply from 13 May 2027 and want each one owned, controlled and evidenced.
- You process personal data for clients as a BPO, SaaS or IT services company and keep answering the same privacy questionnaires.
What you get
The scope is agreed on the first call and written down before the work starts.
- A gap assessment against ISO/IEC 27701:2025.
- Your role as controller, processor or both, and the controls each role needs.
- Each control mapped to DPDP and GDPR duties, so one set of evidence serves all three.
- Support through the certification audit.
Deliverables
What you hold at the end of the engagement, and who each document is for.
| Document | What it holds | Who it is for |
|---|---|---|
| Gap assessment | Where you stand against ISO/IEC 27701:2025, with the gaps ranked and a plan that closes the biggest first. | Privacy lead and leadership |
| Role and scope statement | Which processing you do as a PII controller and which as a PII processor, and the controls each role brings in. | Legal and the auditor |
| Personal data map | What you collect, from whom, why, where it sits, who sees it and where it goes, including sub-processors and transfers abroad. | Privacy and engineering |
| Privacy risk assessment and Statement of Applicability | The risks to the people whose data you hold and to the company, the treatment for each, and which controls apply and why. | The certification body |
| Controls map to DPDP and GDPR | Each control lined up with the DPDP section or Rule and the GDPR article it serves, with the evidence that answers all three. | Privacy and legal teams |
How the work runs
Weeks 1 to 2
Role and scope
Settle which processing is in scope and whether you act as controller, processor or both for each activity, because the role decides which controls apply.
Weeks 2 to 4
Data map and gaps
Map the personal data and measure the gap against ISO/IEC 27701:2025. Where an ISO 27001 ISMS already runs, the gap covers only the privacy additions.
Months 1 to 3
Controls and mapping
Put in place the controls each role needs, from consent records and notices to rights handling, retention, processor contracts and breach handling, each mapped to DPDP and GDPR.
Before the audit
Internal audit and review
An internal audit against the PIMS requirements and a management review, folded into your ISO 27001 programme if you have one.
Months 2 to 4
Certification audit
Stage 1 and Stage 2 with an accredited certification body, combined with your ISO 27001 audit where the same body is accredited for both.
A row from the controller and processor controls map
The controls map lines up each ISO 27701 control with the DPDP and GDPR duties it serves, so one piece of evidence answers all three. This row was written for this page; it does not come from a client's map.
| Control | Obtaining and recording consent, a control for PII controllers in ISO/IEC 27701:2025 |
|---|---|
| Role | PII controller, for people who sign up to the consumer app. It does not apply to the data the company processes for business customers, where it acts as a PII processor. |
| DPDP Act 2023 | s. 6(1) consent that is free, specific, informed, unconditional and unambiguous; s. 6(4) withdrawal as easy as giving it; s. 6(10) the Data Fiduciary must prove notice and consent. Rule 3 sets what the notice must say. |
| GDPR | Art. 7(1) the controller must be able to show that the person consented; Art. 7(3) withdrawal at any time, as easy as giving it. |
| How it is met | Each consent is stored with the user ID, the version of the notice shown, the purposes chosen, the time and the channel. Withdrawal is one step in account settings and stops processing at the processors too, as s. 6(6) requires. |
| Evidence | An export of the consent log, every notice version with its dates, and a sample of withdrawals traced through to the processors. |
| Owner | Product manager for sign-up and account settings; the privacy lead reviews it each quarter |
| Status | Partly in place. Consents are logged but the notice version is not; the fix is due before the internal audit. |
Where it usually goes wrong
Calling yourself a processor for everything
Most processors are also controllers for their own staff, sales and marketing data, and the auditor will look for the controller controls there. Infofacility settles the role activity by activity before any control is written.
Separate programmes for the same duties
Running ISO 27701, DPDP and GDPR as separate projects means separate consent records, breach procedures and evidence for each. Infofacility maps each control to the DPDP and GDPR clauses it serves, so one control and one set of evidence answer all three.
Treating the certificate as legal compliance
An ISO 27701 certificate is not a GDPR certification under Art. 42, and the DPDP Act does not recognise any certificate, so a customer or a regulator can still find a gap. Infofacility checks each control against the law it maps to as well as against the standard.
The requirements it answers
The frameworks, laws and regulators whose requirements this work gives you evidence for.
Pricing
ISO 27701 privacy management
Price on request
Scope sets the price. Book a scoping call for a written quote, in US dollars or rupees.
What sets the price
- Whether you act as controller, processor or both, which sets how many controls apply.
- The number of products, processing activities and business units in scope.
- How many sub-processors and transfers abroad the data map has to cover.
- Whether an ISO 27001 ISMS already runs for the PIMS to build on.
What Infofacility needs from you
- A privacy lead or Data Protection Officer who owns the PIMS and can make decisions.
- Your contracts with customers and processors, your privacy notices and any records of processing you keep.
- Time with the teams that collect and use personal data: product, engineering, marketing, HR and customer support.
- Your ISO 27001 documents, if you hold the certificate, so the shared clauses are reused rather than rewritten.
Questions
Do we need ISO 27001 before ISO 27701?
Not under the 2025 edition, which ISO describes as an independent management system standard, and NABCB now accredits PIMS certification separately from ISMS. Under the 2019 edition you did. Whether a given certification body will certify a PIMS on its own depends on its accreditation scope, so ask before you plan. Most companies still do both, because the controls overlap.
How long does ISO 27701 take?
Two to four months for most companies, from the gap assessment to the certification audit. It is quicker where an ISO 27001 ISMS already runs, because the management system clauses are shared and only the privacy risk assessment and the privacy controls are new. Your role as controller, processor or both, and the number of processing activities, set the rest.
Does ISO 27701 make us GDPR or DPDP compliant?
No certificate does. ISO 27701 organises the work and gives EU customers an audited answer to their Art. 28 due diligence, but it is not a GDPR certification under Art. 42. The DPDP Act 2023 does not require or recognise any certificate. The value is a working programme that gives each legal duty an owner, a control and evidence.
What is the difference between a PII controller and a PII processor?
A PII controller decides why and how personal data is processed; a PII processor processes it on the controller's behalf and on its instructions. They match Data Fiduciary and Data Processor under the DPDP Act, s. 2(i) and s. 2(k), and controller and processor under Art. 4(7) and Art. 4(8) GDPR. ISO 27701 has a separate control set for each role.
Who issues the ISO 27701 certificate?
An accredited certification body, after a Stage 1 and a Stage 2 audit, not Infofacility. NABCB launched a standalone accreditation scheme for PIMS certification bodies in May 2026, so check that the body's accreditation covers ISO/IEC 27701:2025. The certificate runs for three years, with a surveillance audit each year. Infofacility prepares you and supports you through the audit.
How is ISO 27701 different from the privacy category of SOC 2?
ISO 27701 ends in a certificate from an accredited certification body that your privacy management system meets the standard. The SOC 2 privacy category (criteria P1 to P8) is added to the security criteria in a CPA firm's attestation report, which gives an opinion on your controls rather than a certificate. US customers tend to ask for SOC 2; European customers more often ask for ISO 27701.
Keep reading
The library pages behind this work, written and reviewed by the same people.
Framework · Library
ISO 27701
ISO/IEC 27701 is the international standard for a privacy information management system, or PIMS: the governance, controls and records an...
Glossary · Library
PII controller and PII processor
The two roles the ISO privacy standards attach controls to.
Comparison · Library
GDPR vs DPDP
The EU's General Data Protection Regulation and India's Digital Personal Data Protection Act, 2023 side by side, on the same criteria, with the...
Law · Library
Digital Personal Data Protection Act, 2023
India's data protection law: 44 sections in 9 chapters and a Schedule of penalties, coming into force in phases under notification G.S.R. 843(E) of...
Related services
GRC · Service
ISO 27001 certification support
From gap assessment to the certification audit, with the Statement of Applicability written with you.
3 to 6 months
GRC · Service
ISO 42001 AI management system
Policies, impact assessments and the Annex A controls that apply to the AI you build or use.
3 to 6 months
GRC · Service
SOC 2 Type 2 readiness
Scope, controls and evidence ready for your auditor, then support through the observation period.
8 to 12 weeks, then the observation period
Request a callback
Tell Infofacility what you need and by when. A consultant calls you back to agree the scope and send a quote.