Study guide
8.1 A.6 AI System Life Cycle — Design, Development, Verification
PECB ISO/IEC 42001 Lead Auditor AI Management
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Exam Orientation & AI Landscape
1.1 Current Exam Facts & PECB Credential Path 1.2 AI Concepts & ISO/IEC 22989 Terminology 1.3 AI Lifecycle & Trustworthiness Characteristics
2 Chapter 2: ISO AI Family & AIMS Purpose
2.1 ISO/IEC AI Standards Family 2.2 AIMS Purpose, PDCA & Management System Thinking 2.3 Global AI Governance Landscape for Auditors
3 Chapter 3: AIMS Requirements — Context & Leadership
3.1 Annex SL High-Level Structure & Clauses Overview 3.2 Clause 4 Context of the Organization 3.3 Clause 5 Leadership & AI Policy
4 Chapter 4: AIMS Requirements — Planning
4.1 Clause 6.1 Risks, Opportunities & AI Risk Assessment 4.2 Clause 6.1.4 AI System Impact Assessment 4.3 Clause 6.2 AI Objectives & Planning to Achieve Them 4.4 Clause 6.3 Planning of Changes
5 Chapter 5: AIMS Requirements — Support & Operation
5.1 Clause 7 Support 5.2 Clause 8 Operation & Operational Planning and Control 5.3 Clause 8 AI System Lifecycle Controls in Operation
6 Chapter 6: AIMS Requirements — Evaluation & Improvement
6.1 Clause 9 Performance Evaluation 6.2 Clause 10 Improvement 6.3 Integrated AIMS–ISMS Thinking for Auditors
7 Chapter 7: Annex A Controls — Governance & Resources
7.1 Annex A Architecture: 38 Controls Across A.2–A.10 7.2 A.2 Policies Related to AI & A.3 Internal Organization 7.3 A.4 Resources for AI Systems 7.4 A.5 Assessing Impacts of AI Systems
8 Chapter 8: Annex A Controls — Lifecycle & Data
8.1 A.6 AI System Life Cycle — Design, Development, Verification 8.2 A.6 Deployment, Operation, Monitoring & Documentation 8.3 A.7 Data for AI Systems 8.4 Bias, Fairness & Data Quality Audit Focus
9 Chapter 9: Annex A Controls — Transparency, Use & Third Parties
9.1 A.8 Information for Interested Parties 9.2 A.9 Use of AI Systems 9.3 A.10 Third-Party and Customer Relationships
10 Chapter 10: Fundamental Audit Concepts (ISO 19011)
10.1 Seven Audit Principles 10.2 Audit Types, Objectives, Criteria & Scope 10.3 Evidence-Based & Risk-Based Audit Approaches 10.4 Auditor Competence, Ethics & Impartiality
11 Chapter 11: Preparing an ISO/IEC 42001 Audit
11.1 Initiating the Audit & Feasibility 11.2 Determining Audit Objectives, Scope & Criteria 11.3 Document Review & Stage 1 Readiness 11.4 Audit Plan, Team & Working Documents
12 Chapter 12: Conducting an ISO/IEC 42001 Audit
12.1 Opening Meeting & On-Site Kickoff 12.2 Collecting Evidence: Interviews, Observation, Documents 12.3 AI-Specific Evidence: Model Cards, Lineage, Logs, Impact Assessments 12.4 Sampling Strategies & Generating Findings
13 Chapter 13: Closing an ISO/IEC 42001 Audit
13.1 Classifying Nonconformities & Observations 13.2 Audit Conclusions & Closing Meeting 13.3 Writing the Audit Report 13.4 Corrective Action Follow-Up & Verification
14 Chapter 14: Managing the AIMS Audit Program
14.1 Establishing & Implementing an Audit Program 14.2 Program Resources, Risks & Opportunities 14.3 Monitoring, Reviewing & Improving the Program 14.4 Certification Cycle: Surveillance, Recertification & Multi-Standard Audits
8.1 A.6 AI System Life Cycle — Design, Development, Verification
Key Takeaways Explain This Topic AI
Annex A.6 is the largest objective in Annex A with nine controls — A.6.1.2 and A.6.1.3 under management guidance for AI system development, plus A.6.2.2 through A.6.2.8 under the AI system life cycle; numbering starts at .2 because .1 is the objective statement, so A.6.1.1, A.6.2.1, and A.6.2.9 do not exist and verification and validation are one control (A.6.2.4), not two.
Auditors sample requirements traceability: intended purpose and constraints (A.6.2.2) must connect to documented design and development (A.6.2.3) and to verification and validation evidence (A.6.2.4).
Verification tests whether the system meets specified requirements; validation tests whether it is fit for the intended operational use—both need retained, attributable evidence.
Human oversight and fail-safe design are design controls, not only production dashboards; look for them in architecture decisions and acceptance criteria.
Weak SoA claims of “SDLC covers AI” fail when pipelines lack model versioning, evaluation gates, or documented design rationales for high-risk systems.
Last updated: August 2026
8.1 A.6 AI System Life Cycle — Design, Development, Verification
Auditor focus: Annex A.6 (AI system life cycle) asks whether the organization governs AI systems as managed products across their life—not as one-off data-science experiments. In this section you audit the front half: life cycle framework, requirements, design, development, and verification/validation. Deployment and logging follow in 8.2.
Control objective of A.6 (life cycle)
The A.6 control objective is to ensure AI systems are developed, verified, validated, deployed, operated, and retired under defined processes that manage AI-specific risks (data dependence, non-determinism, drift, human-oversight failure, opaque change). A.6 implements Clause 8 operational control and Clause 6 risk treatment for the system engineering path . It complements A.5 (impact assessment), A.7 (data for AI), and A.8–A.10 (transparency, use, third parties).
A.6 is the largest objective in Annex A with nine controls , split across two subclauses: A.6.1 Management guidance for AI system development (two controls) and A.6.2 AI system life cycle (seven controls).
Control Official title Auditor question Covered in
A.6.1.2 Objectives for responsible development of AI system Are development objectives set so that "responsible" is testable, not aspirational? 8.1
A.6.1.3 Processes for responsible AI system design and development Is there a documented, applied stage model for AI systems in scope? 8.1
A.6.2.2 AI system requirements and specification Are purpose, context, boundaries, and success criteria defined before build? 8.1
A.6.2.3 Documentation of AI system design and development Are design choices, models, code, and configs documented, versioned, and reproducible? 8.1
A.6.2.4 AI system verification and validation Do tests show requirements were met and that the system suits its intended use? 8.1
- A.6.2.5 AI system deployment Does only approved, verified code and model reach production? 8.2
- A.6.2.6 AI system operation and monitoring Is the running system observed for AI-specific degradation? 8.2
- A.6.2.7 AI system technical documentation Do technical documents match the deployed version? 8.2
- A.6.2.8 AI system recording of event logs Are life cycle and inference events recorded and protected? 8.2
Numbering warning. Annex A subclauses ending in .1 are objective statements, not controls . There is no A.6.1.1, no A.6.2.1, and no A.6.2.9 — controls start at .2 . Third-party summaries routinely invent them, and exam items quote real IDs, so a fabricated number costs the mark. Note also that verification and validation are a single control (A.6.2.4) , not two, and that retirement / decommissioning has no dedicated Annex A control (see Section 8.2).
Organizations may map stages to ISO/IEC 5338:2023 AI system life cycle processes or to internal MLOps/SDLC. Auditors do not mandate a brand name; they test defined stages, entry/exit criteria, roles, and records .
Development objectives and life cycle framework (A.6.1.2–A.6.1.3)
Strong evidence: approved AI life cycle procedure or standard; stage gates (concept → design → build → V&V → release → operate → retire); RACI for product, ML, risk, security, legal; inventory linking each in-scope system to its current stage; exceptions managed and time-bound.
Weak evidence: “We use Agile/Scrum”; a generic software SDLC with no AI gates (evaluation data freeze, fairness tests, impact assessment completion, model card); shadow models in production outside the framework.
Sampling: Select 2–4 systems (prefer high residual risk from risk/impact assessments). Confirm each is assigned a stage, owner, and gate history. One production system with no lifecycle record is stronger negative evidence than a perfect template never applied.
AI system requirements and specification (A.6.2.2)
Before design and training become uncontrolled science projects, the organization should specify:
Intended purpose and operational context (users, environment, decision type).
Boundaries and prohibited uses (out-of-scope tasks the model must not drive).
Performance and quality criteria (metrics, thresholds, acceptance bands).
Constraints (latency, cost, privacy, human-in-the-loop requirements, regulatory class if claimed).
Links to Clause 6.1 risks and Clause 6.1.4 / A.5 impact assessment conclusions where applicable.
- Artifact What good looks like Red flag
- Requirements / product brief Versioned; measurable; owner-approved Slide deck with slogans only
Intended use statement Clear decision supported; excluded uses listed “General intelligence helper” for high-stakes use
KPI / acceptance criteria Pre-defined thresholds (incl. slice or safety metrics where relevant) “Ship if accuracy looks OK” at demo time
Change of purpose Re-assessment when use expands Silent expansion from assistive to automated deny
Auditor probe: For one high-risk system, obtain the requirements baseline used at last major release. Trace one claimed metric (e.g., false-negative rate) through design decision → test plan → result. Broken chain = nonconformity against life cycle control, even if a model exists.
- Design and development documentation (A.6.2.3)
- Design choices (A.6.2.3, driven by the A.6.1.3 process)
Design should incorporate responsible AI by design : safety and robustness choices, fairness considerations, privacy-preserving architecture, explainability proportionate to risk, and human oversight design (when humans must confirm, override, or monitor).
Look for documented design choices and trade-offs —not only neural architecture diagrams. Examples: why a two-stage model with human review for low-confidence scores; why certain features were excluded as proxies; fallback to rule-based or manual path; rate limits and abuse controls for generative systems.
Development records (A.6.2.3)
Development controls typically include:
Source and model version control (code, configs, weights or registry IDs).
Reproducible training pipelines (environment, seeds, data snapshot IDs).
Secure development practices (secrets, dependency management, access to training infra).
Peer review / change control for model-affecting changes.
Segregation of duties : developers do not solely approve their own production release (links A.3.2 roles and responsibilities with the A.6.2.4 verification and A.6.2.5 deployment gates).
- Evidence sample Pass signal Fail signal
- Model registry entry Immutable version ID, lineage to data/code Unlabeled “final_v3_really.pt” on laptop
- Design decision log Risks and mitigations recorded No record of oversight design
- Pipeline run record Dataset version + hyperparams + metrics Unreproducible notebook only
- Access control Role-based; privileged training access logged Shared root credentials for GPU cluster
- Verification and validation (A.6.2.4)
Dimension Verification Validation
Core question Did we build it right vs specified requirements ? Did we build the right thing for intended use?
Typical tests Unit/integration tests, metric targets on held-out sets, requirement checklists, security scans User acceptance, operational scenario tests, shadow mode results, domain-expert review, real-world workflow fit
Common trap High accuracy on leaked/test-contaminated data Lab metrics good; production population or UX fails
Proportionate depth: High-impact decisioning systems warrant adversarial/OOD stress tests, slice performance, regression vs prior model, and documented residual risks. Low-risk internal classifiers need less ceremony but still need defined criteria and retained results .
Human oversight design evidence: acceptance tests that exercise override paths; UI/workflow showing human responsibility; criteria for when automation may not decide alone. Oversight that exists only as a policy sentence without design or test fails both A.6 design and later operational controls.
Documentation of design choices
Auditors need attributable records: model cards or equivalent technical docs; design reviews; decision records for fairness/safety trade-offs; linkage from impact assessment to design mitigations. Documentation need not be verbose marketing—it must allow reconstruction of what was decided, why, and against which requirements .
Cross-control: Incomplete design docs often cascade into A.8 transparency gaps and weak Clause 7.5 documented information. Raise the primary finding where the requirement fails most clearly (usually A.6 life cycle + SoA implementation description).
Auditor sampling playbook (front-half A.6)
SoA — Confirm A.6 controls applicable; read implementation description.
Inventory + risk tier — Sample high-risk first.
Requirements — Intended use, metrics, prohibited uses.
Traceability matrix (or reconstruct one): requirement → design → code/model version → test case → result → release approval.
V&V package — Test plan, datasets used (IDs), results, sign-offs, independence of validation where claimed.
Human oversight — Designed, tested, not only promised.
Exceptions — Hotfixes that skipped gates; how compensated.
Scenario: Hiring-screen model in production. Product brief says “assist recruiters.” Actual workflow auto-rejects below threshold with no human review. Impact assessment assumed assistive use. Finding path: requirements and intended-use mismatch (A.6.2.2), design documentation and oversight (A.6.2.3), validation against real use (A.6.2.4), and likely A.5 / 6.1.4 impact assessment not updated. Prefer multi-control analysis; severity driven by harm potential.
Exam trap: Confusing verification with validation , or accepting “we use GitHub” as a complete life cycle framework. Another trap: treating A.6 as optional “best practice” when the SoA includes it—normative Annex A controls selected in the SoA must be implemented and auditable.