A furniture retailer collects consent in seven places: the newsletter form, the cookie banner, a prize draw, the customer account, the app, photos taken at trade fairs and the applicant pool. Each department wrote its own text. At checkout, consent to advertising sits in the same sentence as acceptance of the terms and conditions. When a customer asks what exactly he agreed to, nobody can describe the process behind it. A.1.2.4 requires a defined and documented process that lets the organization show if, when and how it obtained consent.
The control is about planning. It settles in which cases consent is needed at all, which conditions apply to it and how the mechanisms in use satisfy those conditions. Obtaining consent in the individual case is then governed by A.1.2.5.
What does the standard require?
Consent is one of the bases from A.1.2.3. It is needed where no other basis applies, and those are exactly the cases the organization should know.
- Record cases and conditions. The organization writes down in which situations it has to ask for consent and what has to be observed when doing so.
- Link purposes and consent. The standard suggests noting, for each processing purpose, whether consent is obtained and by which route. That keeps both pieces of information consistent.
- Observe the rules of each jurisdiction. Some legal systems lay down how consent is to be collected and recorded. The standard gives the ban on bundling it with other agreements as an example.
- Take special cases into account. Additional requirements can apply to certain kinds of collection, scientific research for instance, and to certain groups of people, such as children.
- Show compliance. For each consent mechanism, the organization documents how it meets the relevant requirements.
In practice
Capture every collection point. List every place where the organization asks for agreement: web forms, banners, app permissions, events, photos of employees, talent pools. Often this is the moment you discover departments asking for consent to processing that actually rests on a contract.
Keep a requirements list per mechanism. Record for each mechanism what it has to deliver: separate from other declarations, one choice per purpose, an active step by the person, information before the decision, a note on withdrawal, a record of the event. The list later serves as a checklist for new forms.
Treat children and research separately. Where offers are aimed at children, an age check and a route to parental consent belong in the process. For research projects, settle how precisely the purpose must be defined at collection and which safeguards are added.
Match jurisdictions. Organizations active in several countries check each country’s rules on form, age and recording and note the result in the Legal Compliance Register. Adopting the strictest standard for all countries has proven itself, as long as it does not make the service disproportionately hard to use.
Approve texts centrally. New or changed consent texts pass through the data protection officer before they go live. Every approved version gets an identifier, so that the later record under A.1.2.5 can point to the exact wording.
Typical audit evidence
For A.1.2.4, auditors typically expect:
- Documented consent procedure naming the cases in which consent is needed and the requirements it has to meet
- Record of processing activities stating for each purpose whether and how consent is obtained
- Overview of jurisdictions with their special rules on form, age and recording (→ Legal Compliance Register)
- Approved consent texts with version and approval date (→ Document Control Register)
- Assessment per mechanism showing how a form or banner meets the requirements
KPI
% of consent-requiring processes with defined consent acquisition procedures
Defined means: the process has a named mechanism, an approved text and a documented check against the applicable requirements. The target is 100%. Processes without a procedure often surface only when a data subject asks.
Supporting KPIs:
- Number of collection points without an approved text
- Share of mechanisms checked against the rules of every jurisdiction concerned
- Share of offers aimed at children with an age check and a parental route
Link to the GDPR
Under Article 6(1)(a) GDPR, consent is one of the six lawful bases, and Article 4(11) defines its features. Article 7(2) requires a request for consent in a written declaration that also concerns other matters to be clearly distinguishable from them. That is the GDPR form of the bundling ban the standard cites as an example. Article 7(4) deals with tying consent to a contract. Children are covered by Article 8, special categories by explicit consent under Article 9(2)(a). Recital 33 allows consent to certain areas of research where the purpose cannot yet be fully specified at collection (→ GDPR General Data Protection Regulation). For end devices, section 25 of the German TDDDG applies in addition (→ TTDSG Telecommunications Telemedia Data Protection Act).
Related controls
The process from A.1.2.4 is the yardstick for the whole life cycle of a consent:
- A.1.2.3 Identify lawful basis: decides whether consent is the right basis in the first place.
- A.1.2.5 Obtain and record consent: puts the process into practice in the individual case.
- A.1.3.4 Providing information to PII principals: supplies the information given before consent.
- A.1.3.5 Providing mechanism to modify or withdraw consent: provides the way back.
- A.5.31 Legal, Statutory, Regulatory and Contractual Requirements: identifies the rules of each jurisdiction.
- A.5.34 Privacy and Protection of PII: anchors privacy in the ISMS.
Sources
- ISO/IEC 27701:2025, Annex A, Table A.1, A.1.2.4, and Annex B, B.1.2.4: Determine when and how consent is to be obtained
- Regulation (EU) 2016/679 (GDPR), Articles 4, 6, 7, 8 and 9 and Recital 33
- ISO/IEC 27701: Privacy Information Management System: structure of the standard and roles