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.

Key takeaways

What you need to know about ISO 27701

StandaloneSince 2025 you can certify ISO 27701 without an ISO 27001 certificate.
Your roleControls differ for PII controllers and processors; many companies are both.
Privacy riskRisk is assessed for PII principals, not only for the company.
GDPR fitThe controls map closely to GDPR articles and India's DPDP Act.
IntegratedRunning it with ISO 27001 shares clauses, audits and evidence.

Who needs ISO 27701?

No law requires it, but these situations make a certified privacy system valuable.

SaaS processorsCustomers want proof you handle their personal data correctly.
Data-heavy controllersShows regulators and partners that privacy is governed, not ad hoc.
Companies under GDPR or DPDPGives a recognised structure for accountability duties.
Healthtech and fintechSensitive data needs evidence beyond policies.
ISO 27001 holdersExtends an existing ISMS to privacy with shared audits.

QULDEX helps here first: the readiness check shows where you stand before you commit budget.

Management system + role controls

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.

Clause 4 Plan

Context

Your role as controller or processor, interested parties and PIMS scope.

In QULDEX: Scope and role set once per programme
Clause 5 Plan

Leadership

Privacy policy, roles and top-management commitment.

In QULDEX: Policy approvals with sign-off history
Clause 6 Plan

Planning

Privacy risk assessment, treatment and objectives.

In QULDEX: Risk register generates the SoA
Clause 7 Plan

Support

Competence, awareness and documented information.

In QULDEX: Training records in the evidence vault
Clause 8 Do

Operation

Run the privacy controls for your role.

In QULDEX: Control tasks run on schedule
Clause 9 Check

Evaluation

Monitoring, internal audit and management review.

In QULDEX: Audit workspace and review packs
Clause 10 Act

Improvement

Nonconformity and corrective action.

In QULDEX: Findings flow into CAPA
Requirements explorer

What 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.

2019 → 2025new edition
Extension → standalonecertifiable on its own
2 rolescontroller and processor
Same clausesharmonized structure 4–10

Showing up to 6 per group. Search, filter, or open a group to see all 39.

Management system (clauses 4–10) 15

  1. 4.1Context of the organisation

    Identify 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.

  2. 4.2Interested parties

    Identify 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.

  3. 4.3Scope of the PIMS

    Decide 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

  4. 5.1Leadership and commitment

    Top 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. 5.2Privacy policy

    Set a privacy policy that fits your role and commitments.

    In QULDEXPolicy approvals with named owners and sign-off history.

    Typical evidence
    Approved privacy policy

  6. 5.3Roles and responsibilities

    Assign 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

  7. 6.1Privacy risk assessment and treatment

    Assess 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

  8. 6.2Privacy objectives

    Set 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.

  9. 7.2Competence

    Make sure people doing privacy work are competent.

    In QULDEXTraining records kept in the evidence vault.

    Typical evidence
    Training records

  10. 7.5Documented information

    Create, control and retain the documented information the standard and your PIMS need.

    In QULDEXDocument control with versions, approvals and retention.

  11. 8.1Operational planning and control

    Plan, carry out and control the processes needed to meet privacy requirements.

    In QULDEXControl tasks run on schedule with evidence attached.

  12. 9.1Monitoring and measurement

    Monitor, measure and evaluate privacy performance.

    In QULDEXReadiness dashboards and metrics per objective.

  13. 9.2Internal audit

    Audit the PIMS at planned intervals.

    In QULDEXInternal audit workspace with sampling and findings.

    Typical evidence
    Audit programme and reports

  14. 9.3Management review

    Top management reviews the PIMS at planned intervals.

    In QULDEXManagement review packs generated from live data.

    Typical evidence
    Review minutes

  15. 10.2Nonconformity and corrective action

    React to nonconformities, fix causes and record corrective actions.

    In QULDEXFindings flow into CAPA with owners, due dates and verification.

PII controllers 10

  1. Ctrl 1Identify and document purpose

    Identify 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

  2. Ctrl 2Lawful basis

    Determine 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

  3. Ctrl 3Consent records

    Obtain 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

  4. Ctrl 4Privacy impact assessment

    Assess 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

  5. Ctrl 5Contracts with processors

    Put 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

  6. Ctrl 6Notices to PII principals

    Tell 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

  7. Ctrl 7Rights of PII principals

    Handle 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

  8. Ctrl 8Privacy by design and default

    Limit 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

  9. Ctrl 9Sharing, transfer and disclosure

    Control 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

  10. Ctrl 10Breach notification

    Notify 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

  1. Proc 1Customer agreement

    Make 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

  2. Proc 2Process only on instructions

    Process 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

  3. Proc 3Support customer obligations

    Help 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

  4. Proc 4Records of processing

    Keep 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)

  5. Proc 5Return or delete PII

    Return 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

  6. Proc 6Subprocessors

    Inform 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)

  7. Proc 7Transfers between jurisdictions

    Tell 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

  8. Proc 8Breach notification to customers

    Notify 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

  1. Sec 1Access control for PII

    Limit 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

  2. Sec 2Encryption of PII

    Protect 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

  3. Sec 3Logging of PII access

    Log 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

  4. Sec 4Secure deletion

    Delete 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

  5. Sec 5Supplier security

    Make 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

  6. Sec 6Incident management

    Detect 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

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.

Certification path

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.

  1. Define scope and your role

    Decide which processing activities are in scope and whether you act as controller, processor or both for each.

  2. Map PII and assess privacy risk

    Build records of processing, run privacy impact assessments where needed, and decide which controls apply.

  3. Implement controls and collect evidence

    Put role controls in place: notices, consent, rights handling, processor contracts, transfers, breach response.

  4. Run an internal audit and management review

    Clause 9 must operate at least once before certification.

  5. Stage 1 audit: design and documents

    The certification body checks scope, role decisions, risk process and documents.

    1–3 days
  6. Stage 2 audit: controls in operation

    Auditors sample evidence, such as rights requests and processor contracts, to confirm controls work.

    Audit days set by headcountMulti-auditor workspace →
  7. Keep it running for three years

    Year 1Surveillance audit
    Year 2Surveillance audit
    Year 3Recertification audit

Durations are typical planning ranges from QULDEX audit delivery, not requirements of the standard.

Documented information

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 recordClause or areaWhere it lives in QULDEX
PIMS scope, including your controller or processor role4.3Program setup
Privacy policy5.2Evidence vault · policy library
Privacy risk assessment and treatment6.1Risk register
Statement of Applicability6.1Control library (generated)
Records of processingController · ProcessorEvidence vault
Privacy impact assessmentsControllerRisk register
Processor and customer contractsController · ProcessorVendor register
Rights request logControllerEvidence vault
Breach registerController · ProcessorCAPA automation
Internal audit and management review9.2 · 9.3Audit workspace

Clause references follow the harmonized structure; check exact numbering against the 2025 text.

Time and cost

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

Scope and role2–4 wk
PII mapping and risk3–6 wk
Implement controls2–5 mo
Internal audit, review3–6 wk
Stage 1 + Stage 24–8 wk

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
Readiness check · 2 minutes

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.

4.1Have you decided where you act as controller, processor or both?
6.1Do you have records of processing for in-scope activities?
6.1Have you assessed privacy risk to PII principals?
ControllerAre privacy notices published and up to date?
ControllerDo you log and answer rights requests on time?
ProcessorDo all processors and subprocessors have signed agreements?
BreachCan you notify regulators within legal deadlines?
9.2Have you completed an internal audit of the PIMS?
Crosswalk

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 edition2025 edition
TypeExtension to ISO 27001 and 27002Standalone management-system standard
CertificationOnly together with ISO 27001On its own, or integrated with ISO 27001
StructureBuilt on ISO 27001 clausesOwn clauses 4–10 in the harmonized structure
ControlsController and processor annexesController and processor controls, plus security for PII
StatusReplacedCurrent edition
In QULDEXQULDEX maps 2019-based programmes to the 2025 structure so existing evidence carries over.

Privacy law crosswalk

ISO 27701 areaGDPRDPDP Act 2023ISO 27001:2022Shared evidence
Notices to PII principalsArt. 13–14Sec. 5—Privacy notices
ConsentArt. 6–7Sec. 6—Consent logs
Rights of PII principalsArt. 15–22Sec. 11–14—Request log
Privacy by design and defaultArt. 25Sec. 8A.8.25Design reviews
Processor contractsArt. 28Sec. 8(2)A.5.20DPAs
Records of processingArt. 30—A.5.9Processing records
Breach notificationArt. 33–34Sec. 8(6)A.5.24–A.5.26Breach register
Impact assessmentArt. 35Sec. 10 (significant fiduciaries)6.1.2DPIAs
Cross-border transfersArt. 44–49Sec. 16A.5.14Transfer register

Indicative mapping for planning, not legal advice. The full crosswalk is in the QULDEX control library.

Where QULDEX fits

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.

  1. Scope and roleDecide what is in scopeRole-aware scoping that selects controller or processor controls
  2. PII mappingBuild records of processingProcessing records linked to systems, vendors and transfers
  3. ControlsRun privacy controlsRights requests, consent and DPIAs tracked with evidence
  4. Internal auditTest the PIMSAudit workspace, sampling and findings into CAPA
  5. CertificationHost the auditorControlled, logged evidence sharing
  6. SurveillanceKeep it runningLive readiness view for each year's audit
Without one systemWith QULDEX
Privacy records in spreadsheets per teamOne register linked to systems and vendors
Rights requests tracked in inboxesLogged requests with response times
Separate audits for ISO 27001 and privacyIntegrated audit with shared evidence
DPAs scattered across shared drivesContracts linked to each processor
10+years of audit delivery500+audits deliveredBoth sidesof the audit on one platformRBACand a full audit trail on every action
FAQ

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.

Sources

References

  1. ISO/IEC 27701:2025, Information security, cybersecurity and privacy protection: Privacy information management systems: Requirements and guidance. iso.org
  2. BSI, ISO/IEC 27701:2025 key changes and guidance. bsigroup.com
  3. ANSI blog, ISO/IEC 27701:2025 privacy management systems. ansi.org
  4. Regulation (EU) 2016/679 (GDPR). eur-lex.europa.eu
  5. Digital Personal Data Protection Act, 2023 (India). meity.gov.in
  6. ISO/IEC 27001:2022. iso.org

Reviewed by

Swati Chaturvedi

Framework reviewer · QULDEX

Reviewed this page against ISO/IEC 27701:2025: the standalone structure, controller and processor controls, certification path and the privacy-law crosswalk.

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.

Schedule
Book a Demo