Framework · Privacy · Certifiable
ISO 27701:2025 privacy management: requirements and certification
ISO/IEC 27701 is the international standard for a privacy information management system (PIMS). The 2025 edition is a standalone management-system standard, so you can certify it without holding ISO 27001. It sets management requirements plus controls for PII controllers and processors, and maps closely to GDPR.
What you need to know about ISO 27701
Who needs ISO 27701?
No law requires it, but these situations make a certified privacy system valuable.
QULDEX helps here first: the readiness check shows where you stand before you commit budget.
What does ISO 27701:2025 require?
ISO 27701:2025 requires a privacy information management system: scope, privacy risk assessment, policies, controls for your role as controller or processor, and the usual audit and review cycle. Clauses 4 to 10 follow the same structure as other ISO management systems.
Context
Your role as controller or processor, interested parties and PIMS scope.
In QULDEX: Scope and role set once per programmeLeadership
Privacy policy, roles and top-management commitment.
In QULDEX: Policy approvals with sign-off historyPlanning
Privacy risk assessment, treatment and objectives.
In QULDEX: Risk register generates the SoASupport
Competence, awareness and documented information.
In QULDEX: Training records in the evidence vaultOperation
Run the privacy controls for your role.
In QULDEX: Control tasks run on scheduleEvaluation
Monitoring, internal audit and management review.
In QULDEX: Audit workspace and review packsImprovement
Nonconformity and corrective action.
In QULDEX: Findings flow into CAPAWhat controls does ISO 27701 cover?
ISO 27701 combines management-system clauses with controls grouped by role: what PII controllers must do, what PII processors must do, and security controls applied to PII. Select any item to see what it asks for, typical evidence and the GDPR or DPDP articles it supports.
Showing up to 6 per group. Search, filter, or open a group to see all 39.
Management system (clauses 4–10) 15
4.1Context of the organisationIdentify internal and external issues that affect the privacy management system, including your role as PII controller, processor or both.
In QULDEXQULDEX gives this requirement an owner, a review cycle and an evidence request, shared with any other ISO management system you run.
4.2Interested partiesIdentify interested parties, such as PII principals, regulators and customers, and their privacy requirements.
In QULDEXQULDEX gives this requirement an owner, a review cycle and an evidence request, shared with any other ISO management system you run.
4.3Scope of the PIMSDecide and document the boundaries of the privacy information management system.
In QULDEXScope is set once per programme and drives which controls apply.
- Typical evidence
- Scope statement
5.1Leadership and commitmentTop management shows leadership of the PIMS and integrates it into business processes.
In QULDEXQULDEX gives this requirement an owner, a review cycle and an evidence request, shared with any other ISO management system you run.
5.2Privacy policySet a privacy policy that fits your role and commitments.
In QULDEXPolicy approvals with named owners and sign-off history.
- Typical evidence
- Approved privacy policy
5.3Roles and responsibilitiesAssign responsibility and authority for privacy, for example a privacy lead or DPO.
In QULDEXQULDEX gives this requirement an owner, a review cycle and an evidence request, shared with any other ISO management system you run.
- Typical evidence
- Role assignments
6.1Privacy risk assessment and treatmentAssess privacy risks to PII principals and to the organisation, decide treatments, and record applicable controls.
In QULDEXRisk register decisions generate the Statement of Applicability.
- Typical evidence
- Risk assessment, SoA
- Maps to
- GDPR Art. 35
6.2Privacy objectivesSet measurable privacy objectives and plan how to achieve them.
In QULDEXQULDEX gives this requirement an owner, a review cycle and an evidence request, shared with any other ISO management system you run.
7.2CompetenceMake sure people doing privacy work are competent.
In QULDEXTraining records kept in the evidence vault.
- Typical evidence
- Training records
7.5Documented informationCreate, control and retain the documented information the standard and your PIMS need.
In QULDEXDocument control with versions, approvals and retention.
8.1Operational planning and controlPlan, carry out and control the processes needed to meet privacy requirements.
In QULDEXControl tasks run on schedule with evidence attached.
9.1Monitoring and measurementMonitor, measure and evaluate privacy performance.
In QULDEXReadiness dashboards and metrics per objective.
9.2Internal auditAudit the PIMS at planned intervals.
In QULDEXInternal audit workspace with sampling and findings.
- Typical evidence
- Audit programme and reports
9.3Management reviewTop management reviews the PIMS at planned intervals.
In QULDEXManagement review packs generated from live data.
- Typical evidence
- Review minutes
10.2Nonconformity and corrective actionReact to nonconformities, fix causes and record corrective actions.
In QULDEXFindings flow into CAPA with owners, due dates and verification.
PII controllers 10
Ctrl 1Identify and document purposeIdentify and document the specific purposes for which PII is processed.
In QULDEXController evidence is captured once and also counts toward GDPR and DPDP programmes.
- Typical evidence
- Records of processing
- Maps to
- GDPR Art. 30DPDP Sec. 5
Ctrl 2Lawful basisDetermine and document the lawful basis for each processing purpose.
In QULDEXController evidence is captured once and also counts toward GDPR and DPDP programmes.
- Typical evidence
- Lawful basis register
- Maps to
- GDPR Art. 6
Ctrl 3Consent recordsObtain and record consent where it is the basis, and make withdrawal easy.
In QULDEXController evidence is captured once and also counts toward GDPR and DPDP programmes.
- Typical evidence
- Consent logs
- Maps to
- GDPR Art. 7DPDP Sec. 6
Ctrl 4Privacy impact assessmentAssess the impact of processing that is likely to be high risk.
In QULDEXController evidence is captured once and also counts toward GDPR and DPDP programmes.
- Typical evidence
- DPIA records
- Maps to
- GDPR Art. 35
Ctrl 5Contracts with processorsPut privacy requirements in contracts with every processor.
In QULDEXController evidence is captured once and also counts toward GDPR and DPDP programmes.
- Typical evidence
- Data processing agreements
- Maps to
- GDPR Art. 28
Ctrl 6Notices to PII principalsTell PII principals what you process, why and how to exercise their rights.
In QULDEXController evidence is captured once and also counts toward GDPR and DPDP programmes.
- Typical evidence
- Privacy notices
- Maps to
- GDPR Art. 13–14DPDP Sec. 5
Ctrl 7Rights of PII principalsHandle access, correction, erasure, objection and portability requests on time.
In QULDEXController evidence is captured once and also counts toward GDPR and DPDP programmes.
- Typical evidence
- Request log with response times
- Maps to
- GDPR Art. 15–22DPDP Sec. 11–14
Ctrl 8Privacy by design and defaultLimit collection, processing and retention to what each purpose needs.
In QULDEXController evidence is captured once and also counts toward GDPR and DPDP programmes.
- Typical evidence
- Design reviews, retention schedule
- Maps to
- GDPR Art. 25
Ctrl 9Sharing, transfer and disclosureControl and record transfers of PII, including cross-border transfers.
In QULDEXController evidence is captured once and also counts toward GDPR and DPDP programmes.
- Typical evidence
- Transfer register
- Maps to
- GDPR Art. 44–49
Ctrl 10Breach notificationNotify regulators and PII principals of breaches as the law requires.
In QULDEXController evidence is captured once and also counts toward GDPR and DPDP programmes.
- Typical evidence
- Breach register
- Maps to
- GDPR Art. 33–34DPDP Sec. 8(6)
PII processors 8
Proc 1Customer agreementMake sure the contract with each customer covers how you process PII on their behalf.
In QULDEXProcessor evidence is shared with customers through controlled, logged links instead of long questionnaires.
- Typical evidence
- Customer DPAs
- Maps to
- GDPR Art. 28
Proc 2Process only on instructionsProcess PII only for the purposes the customer instructs.
In QULDEXProcessor evidence is shared with customers through controlled, logged links instead of long questionnaires.
- Typical evidence
- Processing instructions
Proc 3Support customer obligationsHelp customers answer PII principal requests and meet their own obligations.
In QULDEXProcessor evidence is shared with customers through controlled, logged links instead of long questionnaires.
- Typical evidence
- Request support records
Proc 4Records of processingKeep records of processing carried out for each customer.
In QULDEXProcessor evidence is shared with customers through controlled, logged links instead of long questionnaires.
- Typical evidence
- Processor records
- Maps to
- GDPR Art. 30(2)
Proc 5Return or delete PIIReturn or securely delete PII at the end of the service.
In QULDEXProcessor evidence is shared with customers through controlled, logged links instead of long questionnaires.
- Typical evidence
- Deletion certificates
Proc 6SubprocessorsInform customers about subprocessors and flow down the same obligations.
In QULDEXProcessor evidence is shared with customers through controlled, logged links instead of long questionnaires.
- Typical evidence
- Subprocessor list, contracts
- Maps to
- GDPR Art. 28(2)
Proc 7Transfers between jurisdictionsTell customers where PII is processed and control cross-border transfers.
In QULDEXProcessor evidence is shared with customers through controlled, logged links instead of long questionnaires.
- Typical evidence
- Data location register
Proc 8Breach notification to customersNotify customers of breaches involving their PII without undue delay.
In QULDEXProcessor evidence is shared with customers through controlled, logged links instead of long questionnaires.
- Typical evidence
- Notification records
- Maps to
- GDPR Art. 33(2)
Security for PII 6
Sec 1Access control for PIILimit access to PII to people and systems that need it.
In QULDEXSecurity controls are mapped once and reused from your ISO 27001 programme when you run one.
- Typical evidence
- Access reviews
- Maps to
- ISO 27001 A.5.15
Sec 2Encryption of PIIProtect PII in transit and at rest with cryptography where appropriate.
In QULDEXSecurity controls are mapped once and reused from your ISO 27001 programme when you run one.
- Typical evidence
- Encryption settings
- Maps to
- ISO 27001 A.8.24
Sec 3Logging of PII accessLog access to PII and review the logs.
In QULDEXSecurity controls are mapped once and reused from your ISO 27001 programme when you run one.
- Typical evidence
- Log reviews
- Maps to
- ISO 27001 A.8.15
Sec 4Secure deletionDelete PII securely, including from backups and test data.
In QULDEXSecurity controls are mapped once and reused from your ISO 27001 programme when you run one.
- Typical evidence
- Deletion logs
- Maps to
- ISO 27001 A.8.10
Sec 5Supplier securityMake sure suppliers handling PII meet your security requirements.
In QULDEXSecurity controls are mapped once and reused from your ISO 27001 programme when you run one.
- Typical evidence
- Supplier assessments
- Maps to
- ISO 27001 A.5.19
Sec 6Incident managementDetect and respond to incidents involving PII.
In QULDEXSecurity controls are mapped once and reused from your ISO 27001 programme when you run one.
- Typical evidence
- Incident records
- Maps to
- ISO 27001 A.5.24
Nothing matches that search.
Clause numbers follow the harmonized structure. Control-area names are QULDEX groupings of the controller, processor and security controls, not the standard's own numbering; the ISO text is the authority.
How do you get ISO 27701 certified?
Build and run the privacy system, then an accredited certification body audits it in two stages. With an existing ISO 27001 ISMS it often takes 4 to 6 months; from scratch, 6 to 12.
Define scope and your role
Decide which processing activities are in scope and whether you act as controller, processor or both for each.
Map PII and assess privacy risk
Build records of processing, run privacy impact assessments where needed, and decide which controls apply.
Implement controls and collect evidence
Put role controls in place: notices, consent, rights handling, processor contracts, transfers, breach response.
Run an internal audit and management review
Clause 9 must operate at least once before certification.
Stage 1 audit: design and documents
The certification body checks scope, role decisions, risk process and documents.
Stage 2 audit: controls in operation
Auditors sample evidence, such as rights requests and processor contracts, to confirm controls work.
Keep it running for three years
Year 1Surveillance auditYear 2Surveillance auditYear 3Recertification audit
Durations are typical planning ranges from QULDEX audit delivery, not requirements of the standard.
Which documents does ISO 27701 require?
Auditors ask for these first. Most of them already exist if you run GDPR or DPDP compliance; ISO 27701 puts them inside one controlled system.
| Document or record | Clause or area | Where it lives in QULDEX |
|---|---|---|
| PIMS scope, including your controller or processor role | 4.3 | Program setup |
| Privacy policy | 5.2 | Evidence vault · policy library |
| Privacy risk assessment and treatment | 6.1 | Risk register |
| Statement of Applicability | 6.1 | Control library (generated) |
| Records of processing | Controller · Processor | Evidence vault |
| Privacy impact assessments | Controller | Risk register |
| Processor and customer contracts | Controller · Processor | Vendor register |
| Rights request log | Controller | Evidence vault |
| Breach register | Controller · Processor | CAPA automation |
| Internal audit and management review | 9.2 · 9.3 | Audit workspace |
Clause references follow the harmonized structure; check exact numbering against the 2025 text.
How long does ISO 27701 take and what drives the cost?
With an ISO 27001 ISMS in place, 4 to 6 months is common; from scratch, 6 to 12 months. Audit days are set by the number of people in scope, as for other ISO certifications.
Where the time goes
Bars show the upper end of each range on one scale (6 months = full width).
What changes the effort
- Your role: being both controller and processor doubles the control areas
- Processing activities: more purposes and systems mean more records and assessments
- Jurisdictions: cross-border transfers add contracts and checks
- Existing ISO 27001: shared clauses and audits cut effort sharply
- Rights volume: high request volumes need a tracked process
Are you ready for an ISO 27701 Stage 1 audit?
Stage 1 auditors look for these eight things first. Nothing you enter leaves this page.
How ISO 27701 maps to GDPR, India's DPDP Act and ISO 27001
ISO 27701 controls line up with the main privacy laws, so one tested control can support both certification and legal accountability. QULDEX keeps this mapping in its control library.
ISO 27701:2019 vs ISO 27701:2025
| 2019 edition | 2025 edition | |
|---|---|---|
| Type | Extension to ISO 27001 and 27002 | Standalone management-system standard |
| Certification | Only together with ISO 27001 | On its own, or integrated with ISO 27001 |
| Structure | Built on ISO 27001 clauses | Own clauses 4–10 in the harmonized structure |
| Controls | Controller and processor annexes | Controller and processor controls, plus security for PII |
| Status | Replaced | Current edition |
| In QULDEX | QULDEX maps 2019-based programmes to the 2025 structure so existing evidence carries over. | |
Privacy law crosswalk
| ISO 27701 area | GDPR | DPDP Act 2023 | ISO 27001:2022 | Shared evidence |
|---|---|---|---|---|
| Notices to PII principals | Art. 13–14 | Sec. 5 | — | Privacy notices |
| Consent | Art. 6–7 | Sec. 6 | — | Consent logs |
| Rights of PII principals | Art. 15–22 | Sec. 11–14 | — | Request log |
| Privacy by design and default | Art. 25 | Sec. 8 | A.8.25 | Design reviews |
| Processor contracts | Art. 28 | Sec. 8(2) | A.5.20 | DPAs |
| Records of processing | Art. 30 | — | A.5.9 | Processing records |
| Breach notification | Art. 33–34 | Sec. 8(6) | A.5.24–A.5.26 | Breach register |
| Impact assessment | Art. 35 | Sec. 10 (significant fiduciaries) | 6.1.2 | DPIAs |
| Cross-border transfers | Art. 44–49 | Sec. 16 | A.5.14 | Transfer register |
Indicative mapping for planning, not legal advice. The full crosswalk is in the QULDEX control library.
How QULDEX runs ISO 27701 from scope to certificate
QULDEX is ISO 27701 privacy compliance and audit management software built from EGV Group's audit delivery, used by the organisation getting certified and by the auditors who test it. Pick your role to see who does what.
For controllers and processors building a privacy management system.
- Scope and roleDecide what is in scopeRole-aware scoping that selects controller or processor controls
- PII mappingBuild records of processingProcessing records linked to systems, vendors and transfers
- ControlsRun privacy controlsRights requests, consent and DPIAs tracked with evidence
- Internal auditTest the PIMSAudit workspace, sampling and findings into CAPA
- CertificationHost the auditorControlled, logged evidence sharing
- SurveillanceKeep it runningLive readiness view for each year's audit
For DPOs, privacy consultants and internal audit.
- Scope and roleRun the gap assessmentA reusable ISO 27701 gap template
- PII mappingGuide the mappingProcessing record templates per client
- ControlsReview evidenceReview and approval states on every item
- Internal auditAudit and reportFindings with legal-article context
- CertificationPrepare the clientAn audit-ready pack
- SurveillanceStay on retainerOne dashboard across clients
For accredited bodies auditing privacy management systems.
- PlanningPlan audit daysScope, role and SoA in a standard format
- Stage 1Review documentsDocument review with comments tied to clauses
- Stage 2Sample evidenceView-only evidence access with download control and an access log
- FindingsGrade nonconformitiesMajor and minor findings recorded per clause
- DecisionCertifyA traceable audit record
- SurveillanceReturn each yearHistory across the 3-year cycle
Pre-mapped control library
Requirements with owners, test steps and the crosswalk to 50+ frameworks.
Explore →EvidenceSecure evidence vault
Evidence linked to controls and findings, with upload, review and approval history.
Explore →RiskRisk register
Risk assessment and treatment, with decisions traced to the controls they drive.
Explore →FindingsCAPA remediation
Findings from internal and external audits tracked to closure with due dates.
Explore →ISO 27701 questions people ask
Can you get ISO 27701 certified without ISO 27001?
Yes, since the 2025 edition. ISO/IEC 27701:2025 is a standalone standard. Under the 2019 edition, certification was only possible as an extension of ISO 27001.
What changed in ISO 27701:2025?
It became a standalone privacy management-system standard with its own clauses 4 to 10, instead of an extension to ISO 27001 and 27002. Controller and processor controls remain.
Does ISO 27701 make us GDPR compliant?
No standard guarantees legal compliance, but ISO 27701 controls map closely to GDPR accountability duties and give regulators evidence of a governed privacy programme.
What is the difference between a PII controller and processor?
A controller decides why and how personal data is processed. A processor processes it on the controller's behalf. Many companies are both for different activities.
How long is an ISO 27701 certificate valid?
Three years, with surveillance audits in years one and two and recertification in year three, like other ISO management-system certificates.
What happens to ISO 27701:2019 certificates?
They move to the 2025 edition through a transition set by accreditation bodies. Check the deadline with your certification body.
Can QULDEX run ISO 27701 alongside ISO 27001?
Yes. Shared clauses, controls and evidence are mapped once, and each standard keeps its own report.
Go deeper on ISO 27701
DPDP Rules 2025: the compliance timeline
What India's DPDP Rules require and when.
blog.quldex.comDPDP Act and AI training on personal data
Where consent and purpose limits apply to AI training data.
blog.quldex.comAudit evidence naming convention
A file-naming scheme that lets auditors sample without asking.
blog.quldex.comISO 27001 major vs minor nonconformity
How auditors grade findings in any ISO management system.
References
- ISO/IEC 27701:2025, Information security, cybersecurity and privacy protection: Privacy information management systems: Requirements and guidance. iso.org
- BSI, ISO/IEC 27701:2025 key changes and guidance. bsigroup.com
- ANSI blog, ISO/IEC 27701:2025 privacy management systems. ansi.org
- Regulation (EU) 2016/679 (GDPR). eur-lex.europa.eu
- Digital Personal Data Protection Act, 2023 (India). meity.gov.in
- ISO/IEC 27001:2022. iso.org
Reviewed by
Page history
- : Corrected to the 2025 standalone edition; added requirements explorer, GDPR and DPDP crosswalk and readiness check
- : Page first published
Find your ISO 27701 gaps in 15 minutes
Answer a short readiness check and get a gap summary by clause and role. No sales call needed to see the result.