"Is ISO 27701 certifiable?" is a fair question, because the standard is marketed almost like a product that a vendor could have audited in isolation, sitting on a trust centre page next to SOC 2 badges and PCI logos as if it were an equivalent, separate line item. We have covered the standard's privacy content and its relationship to GDPR in what ISO 27701 is and whether it covers GDPR; this piece looks specifically at the certification mechanics. The answer, drawn from certificates actually published in the CertReports index, is no. ISO/IEC 27701 is structured as an extension to an information security management system, and every certificate referencing it in the index on 2026-11-12 is tied to an underlying ISO/IEC 27001 certificate number. This article sets out why that is a structural requirement rather than a marketing choice, what a genuine certificate document contains, and what to ask a vendor whose questionnaire answer mentions ISO 27701 but says nothing about ISO 27001.
What ISO/IEC 27701 actually certifies
ISO/IEC 27701:2019 is formally a set of requirements and guidance for a Privacy Information Management System, or PIMS. It does not define a management system of its own. Instead it adds privacy-specific requirements and controls on top of the information security management system described in ISO 27001, reusing the same clause numbering and much of the same Annex A control set that a buyer is already used to reading on a certificate scope statement. The standard was written, from first publication, as an add-on module that extends a base management system rather than replacing it.
Why there is no standalone ISO 27701 certificate
Certification bodies accredited under ISO/IEC 17021-1 audit management systems against a defined scheme, and the scheme published for ISO/IEC 27701 is explicitly described as ISO/IEC 27001 plus the PIMS extension, with the applicable annex depending on whether the organisation acts as a PII controller, a PII processor, or both. There is no accreditation scheme that lets an auditor certify a privacy management system without first certifying, or concurrently certifying, the information security management system it sits on top of. A vendor cannot ask an auditor to assess only the privacy controls, because the extension's own clauses on risk assessment, the Statement of Applicability and management review point straight back to the base ISMS clauses in ISO 27001.
This also explains why the 2022 edition transition matters for anyone holding the extension. Certificates still citing the ISO/IEC 27001:2013 edition lapsed on 31 October 2025 under IAF MD 26, and because the PIMS extension rides on the same certification cycle as the base ISMS, an organisation cannot keep a 27701 extension alive against a lapsed 2013-edition certificate. The practical effect, covered from the index side in ISO 27001:2013 lapsed, vendor pages have not caught up, is that a stale ISO 27001 reference on a trust centre page is itself a reason to question any 27701 claim sitting next to it.
ISO/IEC 27701 adds requirements and guidance to ISO/IEC 27001 and ISO/IEC 27002 to establish, implement, maintain and continually improve a Privacy Information Management System (PIMS).
What the certificates in the index actually show
We looked at how ISO 27701 appears across certificates captured in the CertReports index. Browse the ISO/IEC 27701 framework page and the pattern is consistent: the extension is never the only standard named on a document, and it is never assigned its own independent certificate number with no reference back to an ISMS.
- 0
- Standalone ISO 27701 certificates
- found in the CertReports index on 2026-11-12; every listing references an underlying ISO 27001 certificate
- 1
- Base standard required per listing
- ISO/IEC 27001, named on the same certificate or a directly linked annex, per the index on 2026-11-12
- 31 Oct 2025
- ISO 27001:2013 lapse date
- certificates citing the 2013 edition stopped being valid under IAF MD 26, which also governs how 27701 extensions transition to the 2022 edition
| What is on the certificate | Standalone ISO 27001 | ISO 27001 with ISO 27701 extension |
|---|---|---|
| Management system audited | Information security management system (ISMS) | ISMS plus Privacy Information Management System (PIMS) |
| Base clauses referenced | ISO/IEC 27001 clauses 4 to 10 | Same ISO/IEC 27001 clauses 4 to 10, read with ISO/IEC 27701 clauses 5 to 7 |
| Annex controls in scope | Annex A only | Annex A, plus the 27701 PII controller and/or PII processor annex |
| Certificate presentation | Single standard named | Both standards named, usually one certificate number with the extension noted, or a clearly linked pair |
| What a lapsed base certificate does to the extension | Not applicable | Extension lapses with it, since it has no independent validity period |
Based on certificate formats observed in the CertReports index on 2026-11-12.
How to get ISO 27701 certification
- 1
Certify or recertify ISO 27001 first
Agree a scope statement and a Statement of Applicability for the information security management system, because the PIMS extension cannot be audited without a live ISMS to extend.
- 2
Identify your PIMS role
Decide whether the organisation acts as a PII controller, a PII processor, or both, since ISO/IEC 27701 adds a different additional annex of controls for each role.
- 3
Run a gap assessment against the 27701 clauses
Map clauses 5 to 7 of ISO/IEC 27701 against existing ISMS documentation covering data subject rights handling, privacy risk assessment, retention schedules and purpose limitation records.
- 4
Fold the PIMS into the existing audit cycle
Certification bodies expect the privacy extension to be reviewed in the same management review meetings and internal audit programme as the ISMS, not run as a parallel system with its own calendar.
- 5
Book a combined audit with an accredited certification body
Confirm the chosen body appears on a recognised accreditation list, as described via auditors and certification bodies, then ask it to issue or reissue the ISO 27001 certificate with the ISO 27701 extension noted in the same certification decision. - 6
Check the certificate text names both standards
A valid certificate shows ISO/IEC 27001 and its edition together with ISO/IEC 27701, the applicable controller or processor annex, and either one certificate number or a clearly linked pair.
How to implement ISO 27701
Implementation is an extension project, not a greenfield one. Organisations that treat it as a separate build usually end up with duplicated risk registers and two audit trails that do not reconcile, which slows the combined audit down rather than speeding it up.
- Map data flows and processing purposes before writing privacy policies, because the 27701 clauses expect a PII processing inventory, not just a security asset inventory.
- Extend the existing risk assessment methodology to privacy risk, rather than building a separate privacy risk register from scratch.
- Update the Statement of Applicability to reference the additional 27701 controls alongside the Annex A controls already in scope, the same controls discussed in ISO 27001 Annex A: what buyers should ask for.
- Train internal auditors on the controller or processor annex relevant to the organisation, since the two sets of additional controls are not identical.
- Keep both certification cycles synchronised, so the ISO 27701 extension renews alongside the ISO 27001 certificate rather than drifting onto a separate expiry date.
Reading a vendor's certificate: what to check
The card below shows how a vendor's public trust centre lists ISO 27701 next to its ISO 27001 certificate rather than as a standalone line item. When checking a vendor's evidence, look at whether the ISO 27701 entry sits under the same certificate scope and body as ISO 27001, or whether it is listed with no base standard mentioned at all, which is the pattern worth questioning before accepting the claim.

Docebo · Trust report
Education · Public evidence as of 16 Nov 2026
Framework overview
CertReports state for each framework with public evidence: 2 verified, 9 vendor-stated.
ISO 27701Vendor-statedTrust centre · 30 Sep 2026FedRAMPVerifiedModerate impact
DPFVerifiedValid to 30 Dec 2026
SOC 2Vendor-statedTrust centre · 30 Sep 2026GDPRVendor-statedTrust centre · 30 Sep 2026
PCI DSSVendor-statedTrust centre · 30 Sep 2026
ISO 27001Vendor-statedTrust centre · 30 Sep 2026
ISO 27017Vendor-statedTrust centre · 30 Sep 2026
ISO 27018Vendor-statedTrust centre · 30 Sep 2026
5Documents and agreements
Legal and review documents Docebo publishes or offers, as of 30 Sep 2026.
- Standard contractual clauses · On request
- Subprocessor list · Public
- Privacy policy · Public
- AI and data use policy · Public
- Public trust centre documents · Docebo SOC2 Report Renewal Statement (Bridge letter); Docebo ISO 27001, 27701, 27017, and 27018 latest certificate; Docebo ISO 9001 Certificate
2Security practices
Public statements from Docebo, shown as statements, not attestations, as of 30 Sep 2026.
- Penetration testing · annual
- Data residency · Australia, Canada, EU, India, US
1Subprocessors
Named on Docebo's public subprocessor list, last seen 30 Sep 2026.
Common mistakes buyers make
- Treating "ISO 27701 certified" as a claim that can stand on its own in a vendor questionnaire response. Ask for the paired ISO 27001 certificate number, scope statement and expiry date.
- Assuming the extension proves GDPR compliance outright. ISO 27701 maps closely to GDPR accountability obligations but is not a GDPR certificate, and the two should not be conflated.
- Comparing ISO 27701 to SOC 2 as if the two were interchangeable attestations. One is a certification against a management system standard, the other is a report produced by an auditor; see SOC 2 vs ISO 27001: what to ask vendors for for how the two sit alongside each other in a review.
- Accepting a self-reported badge without checking the certification body's scope statement, which should name both standards, the applicable annex, and a current, non-lapsed edition.
- Confusing ISO 27701 with the related data-handling standards ISO 27017 and ISO 27018, which cover cloud security and cloud PII protection respectively rather than a full privacy management system, as set out in ISO 27017 vs 27018: what vendors actually publish.
What a valid pairing looks like on paper
A genuine ISO 27701 extension names the ISO/IEC 27001 edition and scope, the ISO/IEC 27701 clauses in use, the applicable controller or processor annex, the accreditation body logo, and either a single certificate number or two numbers explicitly cross-referenced on both documents. If any of those elements are missing, ask the vendor for the underlying ISO 27001 certificate directly.
People also ask
How to get iso 27701 certification?
An organisation must already hold, or concurrently pursue, an ISO 27001 certificate, because 27701 is issued as a privacy extension to that information security management system, not as a separate scheme. The route runs through certifying or recertifying the ISMS, deciding the PII controller or processor role, running a gap assessment against the 27701 clauses, then booking a combined audit with an accredited certification body.
How to implement iso 27701?
Implementation means extending an existing information security management system rather than building something separate. Map PII processing activities, extend the risk assessment methodology to privacy risk, update the Statement of Applicability with the controller or processor annex controls, and align management review and internal audit cycles with the existing ISMS programme.
Is iso 27701 a certifiable standard?
Yes, but only as an extension. ISO/IEC 27701 is written to be audited alongside ISO/IEC 27001, reusing the same management system clauses and adding a controller or processor annex. No accreditation scheme certifies a Privacy Information Management System without a live ISMS underneath it, which is why certificates in the CertReports index on 2026-11-12 always pair the two standards.
Is iso 27701 certifiable?
On its own, no. ISO/IEC 27701 can only be certified as an extension to an existing or concurrently audited ISO/IEC 27001 certificate. Every certificate referencing ISO 27701 in the CertReports index on 2026-11-12 names an underlying ISO 27001 scope and certificate reference; there is no standalone PIMS-only scheme available from accredited certification bodies.
Solomon Amos · Founder, CertReports
Solomon builds CertReports, the public evidence index for vendor security reviews. PhD in machine learning and cybersecurity, two years embedded at HMRC digital programmes, founder of TapTax. He writes about what registries, trust centres and auditors actually publish, and how buyers can use it before the questionnaire goes out.
Read next on CertReports
You might also like
ISO 9001 vs ISO 14001: What the Difference Means for Buyers
Solomon Amos · 17 Nov 2026 · 9 min read
What Is MTCS? Singapore's Cloud Security Standard Explained
Solomon Amos · 1 Nov 2026 · 9 min read