A logistics company has a telematics provider track the vehicles in its fleet. One day an instruction arrives by ticket: tracking is to run around the clock from now on, including weekends and private trips, and the data is to be stored indefinitely. The provider’s project lead changes the configuration because the customer wants it that way. Nobody notices that the drivers’ private lives are now recorded without gaps. A.2.2.5 requires you to inform the customer when you consider one of their processing instructions to be unlawful.
A processor carries out instructions and brings its own expertise to the job. It often knows the technology better than its customer and is the first to see when a setting goes beyond what is permitted. The control turns this knowledge into a duty.
What does the standard require?
A.2.2.5 is one of the shortest controls in Table A.2, and it reaches into every customer relationship.
- Inform the customer. If, in your assessment, a processing instruction breaks laws or regulations, you tell the customer.
- Your assessment is the yardstick. The standard does not demand certainty. It is enough that you consider a breach to be present.
- Limits of what you can check. The implementation guidance accepts that your means are limited. Whether you can spot a breach depends on three things: the technical setting, what exactly the customer asks for, and what your contract with them says.
- A broad notion of law. The standard speaks generally of applicable laws and regulations. Besides data protection law, this can include other rules, for instance from employment law or telecommunications law.
In practice
Clarify what an instruction is. Instructions reach you through many channels: the contract, tickets, emails, change requests and settings the customer makes in the product. Decide which channels count as instructions and how they are recorded.
Name a reviewing function. Give the assessment of a conspicuous instruction to a named function, usually the data protection officer, with legal counsel where needed. The person handling the ticket does not decide alone.
Inform in writing and give reasons. The message to the customer names the instruction concerned, the rule it breaks in your view and a suggestion for reaching the goal lawfully. A constructive tone helps: many customers simply have not thought through the consequences.
Settle suspension in the contract. A proven approach is a clause allowing you to hold back an instruction you have flagged until it is clarified. Without such a rule, contractual duty and legal duty easily collide.
Document everything. Record every flagged instruction, your assessment, the message, the customer’s reply and the decision taken. This file is your evidence if a supervisory authority asks later.
Typical audit evidence
For A.2.2.5, auditors typically expect:
- Procedure description for checking conspicuous instructions, with warning signs and responsibilities
- Contract clause on informing the customer and, where agreed, on suspending execution
- Files on flagged instructions with assessment, message and decision
- Assessment of legal requirements relevant to typical customer instructions (→ Legal Compliance Register)
- Training records for support, project management and operations (→ Training Register)
KPI
% of infringing instructions identified and formally escalated
The total number of unlawful instructions is unknown, so the KPI needs a pragmatic basis. A proven approach is to count every instruction flagged by the warning signs and to measure how many of them were assessed and, where needed, reported to the customer. Spot checks of tickets also show whether conspicuous instructions slipped past the list.
Supporting KPIs:
- Number of instructions per year that triggered the warning signs
- Average time from instruction to message to the customer
- Share of spot checks without an overlooked conspicuous instruction
Link to the GDPR
The second subparagraph of Article 28(3) GDPR obliges the processor to inform the controller immediately if, in its opinion, an instruction infringes the GDPR or other Union or Member State data protection provisions. With its general notion of law, the standard reaches further. Under Article 29, the processor processes data only on instructions. Article 82(2) makes the processor liable for damage if it breaches obligations specifically addressed to processors or acts outside or against lawful instructions. A warning that was never given can therefore create liability of its own (→ GDPR General Data Protection Regulation).
Related controls
A.2.2.5 is the safeguard at the edges of the assignment:
- A.2.2.3 Organization’s purposes: the tie to instructions that A.2.2.5 limits from the outside.
- A.2.2.2 Customer agreement: the contract in which information and suspension are settled.
- A.2.5.6 Legally binding PII disclosures: checking requests from third parties on the same principle.
- A.2.5.8 Engagement of a subcontractor to process PII: obliges subcontractors, too, to report unlawful instructions.
- A.5.31 Legal, Statutory, Regulatory and Contractual Requirements: capturing the legal requirements against which instructions are measured.
Sources
- ISO/IEC 27701:2025, Annex A, Table A.2, A.2.2.5, and Annex B, B.2.2.5: Infringing instruction
- Regulation (EU) 2016/679 (GDPR), Articles 28, 29 and 82
- ISO/IEC 27701: Privacy Information Management System: structure of the standard and roles