ISO/IEC FDIS 27091/Stage 50.00/Planning date 18 Feb 2027 estimate/ISO/IEC JTC 1/SC 27
27091ISO 27091 CheckerAI privacy, read from the rules that apply today
A.6.1.2
ISO/IEC 42001:2023
A.6 AI system life cycle

Control A.6.1.2: Objectives for responsible development of AI system

Control in force todayISO/IEC 42001:2023, Annex APrivacy overlay: The lifecycle and where privacy risk entersReading

Identify and document objectives that guide responsible development of AI systems, take them into account and build measures to achieve them into the development life cycle.

What control A.6.1.2 asks

Identify and document objectives that guide responsible development of AI systems, take them into account and build measures to achieve them into the development life cycle.

Why it matters for privacy

An objective turns a policy sentence into something a team can be measured on. 'Reduce personal data in training sets' is an objective; 'respect privacy' is a sentiment.

The 27091 overlay

Where the draft lands: the direction of the lifecycle. The abstract asks for risks to be identified and treated across the lifecycle. An objective is how treatment reaches the design team.

Basis for A.6.1.2: the ISO page 56582 and the ISO/IEC 42001:2023 control record. The public record supports the point at the level of the abstract; the draft text is not public. The lifecycle and where privacy risk enters.

Evidence for control A.6.1.2

These are the records that turn the control from a statement into something checkable. For control A.6.1.2 the list is written for an AI system that touches personal data, so a system with no personal data will need a subset.

  • Responsible development Documented responsible development objectives (for example fairness)
  • Responsible development Evidence the objectives are reflected in requirements, data acquisition and conditioning, training and verification
  • Responsible development Mandated methods or tools that implement them

Where control A.6.1.2 commonly fails

  • Objectives stated but absent from development requirements
  • No measure linked to each objective

What to do about control A.6.1.2 before the draft lands

Set two or three objectives for each system, with a measure and a date. Include at least one that reduces the personal data used or retained.

The certificate, if you hold one, is against ISO/IEC 42001:2023. Control A.6.1.2 is where the privacy work lands, and it is auditable before the draft is published.

Read across from control A.6.1.2

← Control A.5.5 | Control A.6.1.3 →

Open the full index. The public record behind control A.6.1.2 shows the scope and the lifecycle.

The record behind control A.6.1.2 is the ISO/IEC 42001:2023 Annex A set, retrieved 22 October 2026. The public 27091 abstract supplies the privacy direction, not a draft requirement. Check the sources.