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

A.2.3.2 Comply with obligations to PII principals

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

An online retailer receives a request from a customer to delete all her data. The data sits in the shop platform, in the newsletter tool and in a service provider’s ticket system. The platform offers a deletion function, and the service provider does not. It asks for a ticket, which is processed after six weeks. The retailer misses its deadline and tells the supervisory authority it was waiting for its provider. A.2.3.2 requires you to give the customer the means to meet their obligations to data subjects, and to lay these means down in the contract wherever the customer depends on you.

The rights of data subjects remain words on paper until someone implements them technically. If the data is with you, fulfilling these rights depends on your functions and procedures.

What does the standard require?

A.2.3.2 is the only control of Table A.2 in the group on obligations to data subjects (A.2.3). It bundles what Table A.1 spreads across several controls.

  • Provide the means. You give the customer the tools and procedures to meet their obligations to data subjects.
  • Where the obligations come from. The controller’s obligations can arise from laws, from other regulations or from contracts.
  • Services used for implementation. The customer often uses your service to carry out these obligations. The standard gives the example of correcting or deleting personal data in good time.
  • Laid down in the contract. If the customer depends on information or technical measures from you, these are described in the contract.

In practice

Build self-service into the product. The more the customer can do alone, the more reliably they meet their deadlines. Proven features include searching for a person across all data areas, exports in a common machine-readable format, rectification in the interface and deletion that covers every storage location.

Set a service channel for the rest. Whatever the product does not cover runs through a fixed channel: form or address, named responsibility, agreed handling time, feedback to the customer.

Forward direct requests. Data subjects sometimes contact the service provider directly. Decide that such requests go to the customer at once. The decision on the reply lies with the controller.

Think deletion through to the end. Deletion in the product often misses backups, exports, logs and subcontractors. Describe what happens to these copies and by when they disappear, so that the customer can give the data subject an honest answer.

Write it into the contract and test it. Put the table of functions and handling times into the contract. Test the functions regularly with test data, especially after larger changes to the product.

Typical audit evidence

For A.2.3.2, auditors typically expect:

  • Contract annex listing the means for each data subject right and the agreed handling times
  • Product documentation on export, rectification and deletion
  • Procedures for service requests from customers and for requests that arrive directly from data subjects
  • Test records of the deletion and export functions (→ Deletion Evidence Log)
  • Analysis of handling times over a reporting period

KPI

% of data subject requests handled within defined processor SLAs

What counts are all requests that customers send you to implement data subject rights, plus the direct requests you forward. Within the agreed handling time means: completed or forwarded in full before the contractual deadline expires. The target is 100%.

Supporting KPIs:

  • Share of data subject rights customers can handle through self-service
  • Average time to forward requests that arrive directly
  • Number of successful tests of the deletion and export functions per year

Under Article 28(3)(e) GDPR, the processor assists the controller, insofar as this is possible, with appropriate technical and organizational measures in responding to requests to exercise the data subject rights of Chapter III. The rights themselves are set out in Articles 15 to 22, including the copy under Article 15(3), erasure under Article 17 and data portability under Article 20. Article 12(3) usually gives the controller one month to reply, extendable by two further months where the complexity and number of requests make this necessary (→ GDPR General Data Protection Regulation).

A.2.3.2 connects the rights of data subjects with your service:

Sources

Frequently asked questions

May I answer data subject requests myself?

As a rule, not without an instruction. The controller, your customer, decides on the answer. If a request reaches you directly, forward it to the customer without delay and tell the requester at most that it has been passed on, if the customer has decided so.

Is an export function in my product enough?

For access and data portability, it is a good start. The customer also needs ways to rectify, erase, restrict and act on objections. Whatever the product does not offer itself is covered by an agreed service channel with a fixed handling time.

How fast do I have to deliver?

The standard sets no deadline, and it does require the means to be laid down in the contract. The yardstick is the customer's deadline: under the GDPR, they usually have one month. Your handling time should be short enough to leave them enough time to review and reply.

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.