A software company has kept a tidy record of processing activities for years. In the column “lawful basis”, almost every row says the same thing: “Art. 6 GDPR”. When the supervisory authority asks what the analysis of recorded support calls rests on, the search begins: contract, consent or legitimate interest? Nobody knows what was decided at the time, and no balancing test can be found anywhere. A.1.2.3 requires the organization to determine the lawful basis that carries each defined purpose, record it and actually run the processing in line with it.
The choice of basis reaches far beyond the record. It decides which rights data subjects have, whether consent can be withdrawn, what the privacy notice says and whether a later change of purpose holds. Whoever looks for a basis only after the fact usually finds one that fits the actual practice poorly.
What does the standard require?
The control follows straight on from A.1.2.2. First the purpose is fixed, then the basis that carries it in law.
- Settle lawfulness before the start. Some jurisdictions expect proof that lawfulness was examined before the processing began. A basis found afterwards helps little there.
- Six typical bases. The standard gives as examples consent, performance of a contract, a legal obligation, vital interests of the data subject, a task in the public interest and legitimate interests of the controller.
- Document per activity. The chosen basis is recorded for each individual processing activity, usually in the records under A.1.2.9.
- Balance legitimate interests. Information security objectives can also be a legitimate interest. They are weighed, however, against the privacy interests of the people concerned.
- Special categories in the classification scheme. Data that the law treats more strictly gets a level of its own there. This covers categories defined by the type of data, such as health details, and categories defined by the group of people, such as data about children. What counts as special differs between jurisdictions and sectors, and the organization needs to know which classification applies to its processing.
- A change of purpose means a fresh check. If a purpose is changed or extended, the existing basis may no longer hold. It then has to be revised, possibly with additional consent.
In practice
Enter the specific provision. In the record of processing activities, give article, paragraph and point: Article 6(1)(b) GDPR for handling the contract, Article 6(1)(c) GDPR together with section 147 of the German Fiscal Code for keeping accounting records. A blanket entry such as “Art. 6” can be neither checked nor defended.
Keep balancing tests in writing. Every processing activity based on legitimate interests needs a short balancing test on file. What interest does the organization pursue, how far does the processing intrude on the rights of the people concerned, which safeguards soften the intrusion? For log data used in security monitoring, the outcome usually hinges on two answers: how long the data is kept and who may read it.
Extend the classification scheme. Add the special categories to the existing scheme, so that a single label on the record sets both the protection level and the privacy treatment. Experience shows that a second, parallel scheme leads to contradictions.
Match jurisdictions. Hold the list of countries you operate in against the data categories and note, per country, what counts as special there. Sector rules for healthcare, finance or telecommunications come on top of general privacy law and deserve a separate check.
Tie changes of purpose to a check. Every changed or extended use triggers a review of the basis. Where consent carried the old purpose, the new one usually needs fresh consent. Silence from the data subject does not extend a consent.
Typical audit evidence
For A.1.2.3, auditors typically expect:
- Record of processing activities with the specific provision per activity (article, paragraph, point) and the date of the last review
- Documented balancing tests for all processing that rests on legitimate interests
- Classification scheme including the special categories (→ Information Classification & Labelling Policy)
- Overview of jurisdictions with the classifications and sector rules that apply there (→ Legal Compliance Register)
- Evidence for changes of purpose with a fresh review of the basis (→ Change Log)
KPI
% of processing activities with documented and verified legal basis
Verified means: the provision given matches the actual processing, and where a legitimate interest is relied on, the balancing test exists. The target is 100%. Every gap marks a processing activity that cannot be evidenced when it matters.
Supporting KPIs:
- Share of processing based on legitimate interest with a written balancing test
- Number of changes of purpose per year with a documented review of the basis
- Share of special-category processing with a named exception under Article 9(2) GDPR
Link to the GDPR
A.1.2.3 mirrors Article 6(1) GDPR. The standard lists the six bases as examples, whereas the GDPR lists them exhaustively. Special categories under Article 9(1) additionally need an exception under Article 9(2), and data on criminal convictions falls under Article 10. Recital 49 recognizes network and information security as a legitimate interest, yet the balancing test under Article 6(1)(f) is still needed. The duty to be able to demonstrate lawfulness follows from Article 5(2). Article 30(1) does not expressly require the lawful basis in the record. Keeping it there is still the simplest way to provide that proof. For changes of purpose, Article 6(4) sets out the compatibility test, and under Article 13(1)(c) and (d) data subjects learn the basis and, where relevant, the legitimate interest (→ GDPR General Data Protection Regulation).
Annex D of the standard maps A.1.2.3 to further articles in which the lawful basis decides what follows: Article 8 on a child’s consent to information society services, Article 17(3) with the exceptions to erasure, Article 18(2) with the grounds on which restricted data may still be processed, and Article 22(2) and (4) with the bases an automated individual decision can rest on.
Related controls
The lawful basis connects the purpose with the remaining obligations:
- A.1.2.2 Identify and document purpose: supplies the purpose the basis is assigned to.
- A.1.2.4 Determine when and how consent is to be obtained: governs the procedure where consent is the basis.
- A.1.2.9 Records related to processing PII: keeps purpose and basis per activity.
- A.1.3.3 Determining information for PII principals: carries the basis into the information for data subjects.
- A.5.12 Classification of Information: adds the special categories to the scheme.
- A.5.31 Legal, Statutory, Regulatory and Contractual Requirements: identifies the provisions the bases rely on.
Sources
- ISO/IEC 27701:2025, Annex A, Table A.1, A.1.2.3, and Annex B, B.1.2.3: Identify lawful basis
- Regulation (EU) 2016/679 (GDPR), Articles 5, 6, 8, 9, 10, 13, 17, 18, 22 and 30 and Recital 49
- ISO/IEC 27701: Privacy Information Management System: structure of the standard and roles