Zum Hauptinhalt springen
ISO/IEC 27701:2025 · Annex A, Table A.1 · Control for PII controllers

A.1.2.9 Records related to processing PII

Updated on 5 min Reviewed by: Cenedril Editorial
ISO/IEC 27701:2025GDPR

An engineering company set up its record of processing activities as a spreadsheet in 2018, just in time for the GDPR deadline. Since then, HR has moved to cloud software, sales scores prospects with a lead-scoring tool and video surveillance has been extended to the warehouse. After a data breach, the supervisory authority asks for the record. Almost half of today’s processing activities are missing from it. A.1.2.9 requires the organization to determine the records its processing obligations rely on and to keep them protected and up to date.

The record of processing activities is the backbone of privacy management. Purpose, lawful basis, impact assessment, information for data subjects and deletion: almost every other control draws on its entries.

What does the standard require?

The control closes the group of conditions for collection and processing and gathers what the preceding controls decide.

  • Determine the necessary records and keep them secure. The organization decides which records support its processing obligations and protects them.
  • An inventory of processing. As a proven route, the standard names a list of all the organization’s processing activities.
  • Possible content. The list can hold the type of processing, its purposes, the categories of data and of the people concerned (children, for example) and the categories of recipients, including those in third countries and international organizations. An overview of the technical and organizational measures and the report of a privacy impact assessment complete it.
  • A responsible person. The inventory has someone who stands behind its accuracy and completeness.

In practice

Capture the full picture. Go through departments and systems together: which processes use personal data, which applications store it? Processing at PII processors belongs in the record as well, because it remains the organization’s own activity.

Use fixed fields and shared categories. Work with a template whose fields cover Article 30 GDPR and the standard’s list, and with uniform catalogues for data categories, groups of people and recipients. Free text in every field makes analysis impossible.

Tie changes to existing routines. Project kick-off, software purchasing and change management each trigger a check of whether an entry needs to be created or adjusted. That keeps the record from going stale between the yearly reviews.

Split responsibility in two tiers. One person owns the record as a whole, in many organizations the data protection officer. Each entry also gets a responsible person from the business unit who confirms it at least once a year and after changes.

Protect the records. Only the responsible roles have access, changes are versioned and the data is included in backups. The record describes the weak points of the entire data processing and is confidential accordingly.

Typical audit evidence

For A.1.2.9, auditors typically expect:

KPI

% of processing activities fully recorded in the processing register

Fully recorded means: the activity has an entry, all mandatory fields are filled in and the linked evidence exists. The target is 100%. The denominator comes from comparisons with systems and departments; otherwise the figure only measures what is already known.

Supporting KPIs:

  • Share of entries reviewed in the last twelve months
  • Number of processing activities newly found in comparisons or audits
  • Share of entries with a responsible person from the business unit

A.1.2.9 largely corresponds to Article 30 GDPR. Paragraph 1 requires the name and contact details of the controller, the purposes, the categories of data subjects and data, the recipients, transfers to third countries and, where possible, the envisaged deletion periods and a general description of the measures under Article 32. The record is kept in writing, electronic form being sufficient (paragraph 3), and made available to the supervisory authority on request (paragraph 4). The exemption in paragraph 5 applies only within narrow limits. Behind the duty stand the accountability principle in Article 5(2) and the controller’s responsibility under Article 24(1). For processors, Article 30(2) applies (→ GDPR General Data Protection Regulation).

The record takes in the results of many controls:

Sources

Frequently asked questions

Does the exemption for organizations with fewer than 250 employees apply?

Rarely. Article 30(5) GDPR exempts smaller organizations only if the processing poses no risk, happens only occasionally and involves neither special categories nor data on criminal offences. Payroll and customer administration run all the time, so almost every organization needs a record.

How does the standard's list differ from Article 30 GDPR?

The standard gives an open list without deletion periods and without the controller's contact details. Article 30(1) GDPR requires the contact details, deletion periods where possible, and information on transfers to third countries. Organizations subject to the GDPR therefore build the record on Article 30 and add the impact assessment report from the standard's list.

Who maintains the record?

The standard requires a person who owns the record and stands behind its accuracy, often the data protection officer or a privacy coordinator. The business units supply the content, because only they know what actually happens in their processes. Assigning each entry a responsible person from the business unit as well has proven itself.

No Cookies!

This wiki collects nothing, bakes nothing and leaves nothing behind. There's nothing to consent to. Privacy doesn't get better than this.