The PDPL has no certificate. This does.
ISO/IEC 27701 is the certifiable standard for a privacy information management system. As of the 2025 edition it stands alone — you no longer need ISO 27001 first, which removes the barrier that kept most Saudi organisations away from it.
This page reflects how we see ISO/IEC 27701 applied in practice. It is not an official reference. The authoritative source is the standard as published by ISO and IEC, which may be revised — confirm what applies to your organisation against it and with your certification body.
What is ISO 27701?
From the compliance programmes we build and run in Saudi Arabia: ISO/IEC 27701 is the international standard for a privacy information management system — a PIMS. It sets out how an organisation establishes, operates and improves the governance around personal data it handles as a controller, a processor, or both, and it can be independently certified.
The reason it matters here is an asymmetry. The Saudi PDPL is mandatory, and SDAIA enforces it — but there is no PDPL certificate. Nothing to show a buyer, nothing to attach to a tender response, nothing that says an independent party has examined how you handle personal data.
ISO 27701 is the reverse. It is entirely voluntary, and it produces exactly that.
What changed in 2025
If you researched ISO 27701 before late 2025, or read an article that has not been updated, what you learned is now wrong in the way that matters most.
The practical consequence for a Saudi organisation is large. Under the 2019 edition, a company that wanted a privacy certification first had to build and certify a full ISMS — which for many was reason enough not to start. That gate is now open.
The 2019 edition was, by its own title, an extension to ISO/IEC 27001 and ISO/IEC 27002. You could not implement or certify a PIMS without first holding a certified ISMS. That prerequisite is gone.
The second edition, published in October 2025, is a standalone management system standard. An organisation can now implement and certify a privacy information management system without ISO 27001 certification.
The standard now follows the ISO High-Level Structure used by ISO 27001:2022 and other management system standards — context, leadership, planning, support, operation, performance evaluation, improvement.
Controls previously split between PII controllers and PII processors are consolidated into A.1, A.2 and A.3, which simplifies scoping for organisations acting in both roles — as most platforms and service providers do.
Coverage extends to biometric data, health data, IoT environments, and privacy risks arising from artificial intelligence — areas the 2019 edition predated.
New guidance governs how certification bodies audit a PIMS, replacing the previous technical specification. If you are selecting a certification body, this is what they now work to.
Requirements for both roles are set out more fully, which matters for any organisation that is a controller for its own data and a processor for its customers' — a common position and an awkward one to evidence.
Because the standard became standalone rather than being amended, transition arrangements for existing 2019 certificates took longer to settle than a normal revision. Confirm your own position and timeline with your certification body rather than assuming the usual pattern applies.
ISO 27701 and the Saudi PDPL
They are not alternatives, and confusing them is the mistake we see most often on this topic.
Read the last row carefully, because it is the one buyers and vendors both get wrong. A 27701 certificate is strong evidence that you have built privacy governance properly. It is not a defence, and SDAIA is not bound by it. What it does is make the case to a customer far faster than a questionnaire ever will.
| Saudi PDPL | ISO/IEC 27701 | |
|---|---|---|
| Status | Mandatory law | Voluntary standard |
| Who requires it | SDAIA, as the supervisory authority | Your buyers, partners, and increasingly your board |
| What it gives you | Obligations to meet | A certificate demonstrating you meet a recognised standard |
| Scope | Personal data of individuals in the Kingdom | Whatever PIMS scope you define and certify |
| Independent examination | None — you self-assess unless investigated | An accredited certification body audits you |
| Does it satisfy the other? | The PDPL applies whether or not you are certified | Certification evidences privacy governance; it does not discharge the PDPL |
Who ends up needing it
The 2025 change widened this considerably, because the ISO 27001 prerequisite is gone.
If your customers are controllers under the PDPL, their obligations flow to you. A certificate answers the processor-diligence section of their assessment without a bespoke exchange each time.
Transfers require conditions to be met and assessments to be recorded. A certified PIMS is where those records live, and it travels better with an international counterparty than a description of your internal process.
ISO 27701 is recognised internationally and maps onto major privacy regimes. It communicates your privacy position to a buyer who has never read the PDPL and is not going to.
The 2025 edition addresses biometric and health data explicitly. If you process either, this is now the standard that speaks to your risk rather than a general security certification.
Privacy risks arising from AI are within the 2025 edition's scope — a question buyers now ask that no earlier privacy certification answers cleanly.
The route that existed before still works and is the shortest one. Your management system, internal audit and management review already exist; the PIMS extends them rather than starting over.
Running ISO 27701 in Govrly
The records a PIMS audit examines are the records a PDPL programme keeps. Running them twice is the waste this removes.
Processing records, lawful bases, retention decisions and transfer assessments satisfy your PDPL obligations and evidence your PIMS from the same records — not two registers maintained in parallel and drifting apart.
Each processing activity records which role you hold, which is what the standard asks and what most organisations cannot answer cleanly when the auditor asks.
Scope, leadership, internal audit and management review held as records with owners and dates, rather than activities someone recalls performing before the audit.
Access control, encryption and logging implemented for the NCA ECC or ISO 27001 are the same controls protecting personal data under the PIMS — carried from the same record rather than re-evidenced.
Rights requests tracked against their deadline and breach assessments with the reasoning preserved — the operating evidence a certification audit looks for, produced as the process runs.
Root cause, corrective action, owner and a verification step, closing only when verification completes — which is what the surveillance audit examines the following year.
ISO 27701, ISO 27001, and SOC 2 Privacy
Three ways to evidence privacy governance to a buyer, and they are not interchangeable.
In our experience the sequencing question answers itself once you know who is asking. A customer worried about how you handle their employees' data wants 27701. A customer running a general vendor security review wants 27001 or SOC 2. Organisations facing both stop choosing and map both onto one control library.
| ISO 27701 | ISO 27001 | SOC 2 Privacy | |
|---|---|---|---|
| Subject | Personal data governance | Information security broadly | Personal information, as one optional category |
| Output | Certificate | Certificate | Attestation report under NDA |
| Prerequisite | None, since the 2025 edition | None | Security category is mandatory alongside it |
| Depth on privacy | Highest — it is the entire subject | Limited; privacy appears through security controls | Moderate; one category among five |
| Strongest with | Buyers who care specifically about personal data | Buyers assessing security posture generally | North American buyers |
A practical path to certification
If you already run a PDPL programme properly, you are further along than the standard's newness suggests.
- 01/08Decide whether you are starting standalone or extending
If you hold ISO 27001, extending is shorter — the management system exists. If you do not, the 2025 edition lets you start here directly, which was not an option before.
- 02/08Define the PIMS scope
Which processing activities, which systems, which entities. Scope creep is more expensive here than in a security certification, because privacy obligations attach per processing activity.
- 03/08Establish your role for each activity
Controller, processor, or both. This determines which requirements apply, and it is the question organisations most often answer incorrectly at first pass.
- 04/08Start from your PDPL records
Your processing inventory, lawful bases, retention periods and transfer assessments are the foundation. If they are current, most of the operational substance is already there.
- 05/08Map your existing security controls
Access control, encryption, logging and incident response already implemented for the ECC or ISO 27001 protect personal data too, and carry across rather than being rebuilt.
- 06/08Build the management system layer
Scope, leadership, objectives, internal audit and management review. This is the part a PDPL programme usually lacks, because the law asks for outcomes rather than a management system.
- 07/08Run it before the audit examines it
A certification body looks for a system that operates, not one that was assembled. Rights requests handled, reviews performed, findings closed — with the records to show it.
- 08/08Select a certification body accredited for PIMS
Confirm they are accredited for ISO 27701 specifically and working to the current certification body guidance, and ask them directly about transition arrangements if you hold a 2019 certificate.
Your processing records, lawful bases, retention decisions and transfer assessments carry your PDPL obligations and evidence your PIMS from the same records — while the access controls and logging protecting that data are the same controls already carrying your NCA ECC or ISO 27001 requirements.
ISO 27701 — FAQs
The international standard for a privacy information management system, or PIMS. It sets out how an organisation establishes, operates and improves the governance around personal data it handles as a controller, a processor, or both, and it can be independently certified by an accredited certification body.
Not any more. The 2019 edition was an extension to ISO 27001 and ISO 27002, and a certified ISMS was a prerequisite. The second edition, published in October 2025, is a standalone management system standard — you can implement and certify a PIMS without ISO 27001 certification. If you already hold ISO 27001, extending it remains the shorter route.
No. The PDPL applies whether or not you are certified, and SDAIA is not bound by a certificate. What certification does is evidence that an independent body examined your privacy governance against a recognised standard — which is persuasive to a customer, and considerably faster than answering a questionnaire.
The standard became standalone rather than an extension. It adopts the ISO High-Level Structure with clauses 4 to 10, consolidates the Annex A controls previously split between PII controllers and processors, and extends coverage to biometric data, health data, IoT and privacy risks arising from artificial intelligence. New guidance for certification bodies was published alongside it.
Confirm your position with your certification body. Because ISO 27701 became a standalone standard rather than being amended, transition arrangements took longer to settle than they would for a routine revision, and your certification body is the authority on what applies to your certificate and by when.
Closely, and in your favour. Your processing inventory, lawful bases, retention periods, rights request handling and transfer assessments are the operational substance a PIMS audit examines. What a PDPL programme usually lacks is the management system layer — scope, objectives, internal audit and management review — because the law asks for outcomes rather than a management system.
It depends on who assesses you. If your customers are domestic and assess you under the ECC or the SAMA CSF, ISO 27001 usually carries further. If your customers care specifically about personal data — or if you process health, biometric or employee data on their behalf — 27701 speaks directly to what they are worried about in a way a general security certification does not.
Yes, and most platforms and service providers are both — a controller for their own employee and customer data, and a processor for data their customers place in the service. The 2025 edition consolidates the controls for both roles, which simplifies scoping for exactly that position.
Depth and output. ISO 27701 is entirely about privacy and produces a certificate; SOC 2 Privacy is one optional category alongside Security and produces an attestation report shared under NDA. If privacy is the specific concern your buyer raised, 27701 answers it more completely.
Yes. Controls, processing records and evidence are shared objects, so one implemented control and one approved artefact can support a PIMS requirement, an NCA ECC requirement, an ISO 27001 Annex A control and a PDPL obligation at the same time — with each framework keeping its own scope, scoring and reporting.
Your PDPL records are most of a PIMS already
See what your existing privacy programme covers against ISO 27701, and what the management system layer would add.
