ISO 27701 as an Extension, Not a Rebuild: Automating PIMS Controls

ISO 27701 is not a second management system bolted onto your ISO 27001 certification. It is an extension of the one you already run — and treating it as a fresh build is the most expensive mistake firms make on the way to a privacy certificate.

The clue is in the title. The 2019 standard is formally called an extension to ISO/IEC 27001 and ISO/IEC 27002 for privacy information management. It does not stand up a parallel privacy programme with its own risk process, its own audit cycle and its own evidence store. It layers a privacy information management system — a PIMS — onto the information security management system you were already certified against. Nearly everything an auditor will ask to see for the privacy scope is the same class of artefact you already produce for security: a control, a test that the control operates, and evidence that the test ran. The build is not a new machine. It is wiring a handful of extra controls into the machine you already own.

What 27701 actually adds

Strip away the certification-body prose and the standard does four things on top of ISO 27001. First, its clause 5 modifies the management-system requirements themselves — context, planning, risk assessment — so that privacy risk to individuals sits alongside security risk to the organisation. Second, its clause 6 provides privacy-specific guidance on the existing ISO 27002 controls, so a control you already run for security is read again through a privacy lens. Third and fourth, it introduces additional controls that have no security-only equivalent: a set for organisations acting as PII controllers, in its Annex A, and a further set for organisations acting as PII processors, in its Annex B.

Free · 4 minutes

Do you know where AI is already being used in your business — and what it can see?

Fourteen questions on shadow AI, data exposure, oversight, and governance debt — the gap between how fast AI is arriving and how much control you have over it. Banded finding on screen, full sheet by email.

That structure is the whole point. The bulk of the standard reuses controls you have already implemented and tested. Only a comparatively small band of genuinely new controls — consent records, data-subject request handling, purpose limitation, controller-to-processor instructions, retention and disposal for personal data specifically — needs fresh collection. If your programme treats every one of the standard’s controls as new work, you will pay to re-evidence things your ISO 27001 auditor signed off last quarter.

The three buckets that decide the cost

The way to scope the work honestly is to sort every PIMS control into one of three buckets against your existing control set, before anyone opens a project plan.

  1. Maps one-to-one. The control is an existing ISO 27001 control that 27701 reads through a privacy lens. Access control, cryptography, logging, supplier management, incident response. The control test does not change; you extend its scope statement to say it also covers personal data, and you re-point the same evidence at the privacy certificate. No new collection.
  2. Maps with an added assertion. The control exists, but privacy demands one extra thing the security version never checked. Your retention policy exists, but it never distinguished personal data with a lawful-basis-driven clock. Your asset inventory exists, but it never tagged which stores hold PII. The test is extended, not rebuilt, and it draws on a new field in an existing evidence source.
  3. Genuinely new. There is no security analogue. Records of consent and its withdrawal, handling of data-subject access and erasure requests within a deadline, records of controller instructions to processors. These need a new evidence hook — usually an export from an application or a ticketing system that your ISMS never had reason to touch.

In most estates the first bucket is the largest by a wide margin, and the third is the smallest. That distribution is the argument for extension over rebuild in a single line. The disciplined crosswalk that produces it is the same exercise we describe in crosswalking AI RMF, ISO 42001 and the Cybersecurity Framework: run every new obligation against the control environment you already operate, and you buy the delta rather than the whole.

Mapping to the same evidence machinery

The mistake that makes 27701 feel like a rebuild is treating the mapping as a spreadsheet a consultant hands over once. It is not a document; it is configuration. If your ISO 27001 control tests already run as code against evidence sources — a cloud API, an identity provider, a ticketing system — then adding the PIMS controls means adding rows to that catalogue and pointing them at the evidence hooks that satisfy them. The control plane does not change. The catalogue grows.

Here is the shape of a control-mapping file that extends an existing ISO 27001 catalogue with the 27701 additions. Each entry names the parent 27001 control it inherits from, the privacy assertion it adds, and the evidence hook that proves it — so the automation that already collects for security collects for privacy in the same run.

# pims-extension.yaml
# Extends an existing ISO 27001:2022 control catalogue with ISO 27701 PIMS
# controls. Parent controls are inherited; only the delta is defined here.

inherits: iso27001-2022-catalogue.yaml   # 93 Annex A controls, already tested

controls:
  # --- Bucket 1: maps one-to-one, scope extended to personal data ---
  - id: PIMS-A.5.15-PII
    role: controller
    parent: A.5.15            # Access control (unchanged test)
    privacy_assertion: "Access to PII stores is least-privilege and reviewed"
    evidence_hook: idp.entitlement_export   # same source as security test
    collection: reuse

  # --- Bucket 2: maps with an added assertion ---
  - id: PIMS-A.5.9-PII
    role: controller
    parent: A.5.9             # Inventory of information and assets
    privacy_assertion: "Assets holding PII are tagged with lawful basis"
    evidence_hook: cmdb.assets?filter=data_class%3Dpii
    collection: extend        # new field on an existing source

  # --- Bucket 3: genuinely new, needs a new hook ---
  - id: PIMS-7.3.5
    role: controller
    privacy_assertion: "DSAR resolved within statutory deadline"
    evidence_hook: ticketing.queue?type=dsar&state=closed
    collection: new
    sla_days: 30              # verify against the applicable national law

  - id: PIMS-8.5.6
    role: processor
    privacy_assertion: "Processing performed only on documented controller instruction"
    evidence_hook: contracts.dpa_register
    collection: new

The collection field is the honest part. Everything marked reuse costs you nothing but a scope line. Everything marked extend costs a field. Only new costs a fresh integration. Count the new rows and you have your actual build estimate — not the intimidating total control count a certification body quotes you.

Why the control-plane matters more than the certificate

Running privacy on the same control plane as security is not only cheaper to certify; it is cheaper to keep. Audit fatigue is a real cost, and it compounds when two teams collect two sets of evidence about the same systems on two different cadences. One catalogue, one collection run, one set of exceptions to chase means the privacy certificate stays true between audits instead of being reconstructed the fortnight before each one. This is the same discipline behind treating your Article 30 record as code generated from infrastructure metadata rather than a hand-maintained register — the evidence is a by-product of how the estate is instrumented, not a separate deliverable someone has to remember to update.

It also future-proofs the work. The privacy assertions you attach to controls today are the same objects you will crosswalk to the next framework that lands — an AI management system, a sector code, a supervisory expectation. A well-structured control catalogue, of the kind we set out in the AI Controls Matrix, absorbs new obligations by adding rows and mappings, not by standing up new machinery each time. The 2025 revision of 27701 makes this more visible still: it lets the PIMS certify as a standalone system and merges the controller and processor annexes, but the practical logic is unchanged — the controls still ride whatever evidence machinery you already operate. Verify the transition timetable against your certification body before you plan around it.

The firms that struggle with 27701 are the ones that let it become a second programme with a second budget and a second evidence store. The firms that breeze through it did one thing first: they wrote the mapping, saw that most of the work was already done, and bought only the delta.

Free interactive tool

Interactive deadline calculator

Check which regulations apply to you and when

Regulation across the EU, UK, US and Asia-Pacific has moved considerably in the past eighteen months, and several headline dates have shifted more than once. Twelve questions, about three minutes.

Results are shown on screen — no email required. A dated summary is available to download, and can be sent on if that's more useful. What we do with your answers.

Governance is what happens when nobody is watching.

Policies are easy. Consistent decision-making is harder. Understand where governance exists and where it has quietly become assumed.

Full Governance by Sixteen Pillars

Govern your business. Prove your compliance.

A board assurance cockpit for EU-regulated financial firms — tamper-evident, hash-chained proof of governance across DORA, GDPR, NIS2, ISO 27001, the EU AI Act and MiCA. In development.

See what's coming