Study guide

8.2 A.6 Deployment, Operation, Monitoring & Documentation

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.2 A.6 Deployment, Operation, Monitoring & Documentation

Key Takeaways Explain This Topic AI

Deployment (A.6.2.5) requires controlled release — readiness criteria, staged rollout where appropriate, recorded approval, and rollback readiness — not informal “push to prod.”

Operation and monitoring (A.6.2.6) must detect AI failure modes such as performance degradation, drift, incidents, and oversight failures, not only infrastructure uptime.

Technical documentation (A.6.2.7) and recording of event logs (A.6.2.8) enable reconstructability of what version ran, on what data assumptions, with what human actions.

Retirement has no dedicated Annex A control — there is no A.6.2.9 — so audit decommissioning against the A.6.1.3 life cycle process, Clause 8.1 operational control, and the inventory and records requirements it touches.

Auditors probe production monitoring ownership, incident/override logs, and whether rollback was tested—not only whether a model card PDF exists.

Last updated: August 2026

8.2 A.6 Deployment, Operation, Monitoring & Documentation

Auditor focus: After design and V&V, A.6 asks whether the organization releases, runs, observes, records, and retires AI systems under control. A perfect offline accuracy report with uncontrolled production deployment is a classic major gap.

Deployment (A.6.2.5)

Deployment control ensures only approved versions enter production under defined conditions. Typical elements:

Element Auditor tests

Release criteria V&V complete; impact assessment current; security/privacy gates; monitoring pack ready; rollback defined

  • Approval authority Independent of sole developer where SoD requires; recorded decision
  • Release method Blue/green, canary, shadow, feature flags—proportionate to risk
  • Environment control Separation of train/test/prod; promotion via registry/CI, not manual copy
  • Rollback readiness Prior known-good version restorable; triggers and owners defined

Sampling probes:

Last three production promotions for a high-risk system: who approved, against which checklist, which model/data versions.

Evidence of rollback test or actual rollback; time-to-restore.

Hotfix exceptions: risk acceptance, compensating monitoring, retrospective V&V.

Vendor-hosted models: client-side acceptance and version pin/change control (links A.10 ).

Weak signals: “ML engineer has prod write access and ships when ready”; no link between model registry ID and production endpoint; canary process described but never used for AI releases; rollback plan is “retrain overnight.”

Operation and monitoring (A.6.2.6)

Operation control keeps the system within intended performance and risk envelope after go-live. Monitoring must be capable of detecting AI-specific degradation.

  • Monitoring family Examples Why it matters in A.6
  • Quality / performance Error rate, precision/recall, calibration Silent failure after data shift
  • Data / concept drift Feature distributions, prediction drift Core ML production failure mode
  • Fairness / slices Group metrics where relevant Equity claims must be operational
  • Human oversight Override rates, review SLAs, disagreement rates Oversight design still works in prod
  • Safety / abuse Harmful output rates, jailbreak patterns (genAI) Misuse and unsafe outputs
  • Incidents AI incident tickets, rollbacks, complaints Feeds Clause 10 and management review
  • Infrastructure Latency, availability Necessary but not sufficient alone

Ownership: Named on-call or product owner; thresholds; escalation path; analysis frequency. Unowned dashboards are decoration.

Link to Clause 9.1: A.6.2.6 operational monitoring for systems should align with AIMS monitoring design. Finding placement may reference both; avoid double-counting the same gap without clear requirement mapping.

Scenario: Credit model monitors only API 200-rate and CPU. Portfolio default rates for a protected subgroup spike after a data pipeline change; no alert. Deployment was clean; operation/monitoring design is inadequate . Finding against A.6.2.6 (and possibly 9.1 / A.7 if data quality broke).

Technical documentation (A.6.2.7)

Technical documentation supports transparency, continuity, and audit reconstructability. Typical artifacts:

Model cards or system cards (intended use, metrics, limitations, ethical considerations).

Architecture and data-flow descriptions.

Evaluation reports and known failure modes.

Runbooks for monitoring, incident response, and rollback.

Version history and dependency inventory (libraries, foundation models, prompts).

  • Audience Documentation need
  • Operators Runbooks, alert meaning, escalation
  • Auditors / CAB Traceability, control evidence
  • Interested parties (A.8) Proportionate disclosure—do not confuse marketing with A.6 technical docs
  • Future maintainers Enough to retrain, debug, or retire safely

Trap: Beautiful model card stale relative to production version. Always match document version ↔ deployed version ID .

Event logging and system recording (A.6.2.8)

Logging and recording under the life cycle objective typically include:

Inference-relevant events (where proportionate): request metadata, model version, outputs or decision class, confidence, policy blocks.

Human actions: overrides, approvals, manual labels fed back.

Lifecycle events: training runs, evaluation completions, deployments, config changes, rollbacks, decommission.

Security-relevant AI events: access to model artifacts, prompt/system-message changes, dataset access.

Integrity: Access control, retention period, time sync, protection against silent alteration (align with ISMS logging practices where integrated). Incomplete logs make incidents non-reconstructable—raise as control effectiveness failure, not a minor admin note.

Privacy note: Logging personal data in prompts or inputs may create legal obligations. Auditors look for defined logging scope and privacy risk handling, not “log everything forever” as automatic conformity.

Recording of AI system life cycle events

A practical life cycle event log (ticket system, registry, or CMDB-like AI inventory) should answer:

What system/version was created, changed, released, or retired?

When and by whom?

Against which approval and evaluation evidence?

What monitoring or incident followed?

  • Event type Minimum record fields
  • Train / retrain Data snapshot ID, code/config hash, metrics, operator
  • V&V complete Scope of tests, results, residual risks, approver
  • Deploy Version, environment, change ticket, rollback plan ID
  • Incident Detection time, impact, containment, linked CA
  • Retire Date, data/model archival, access removal, notices

Absence of life cycle event history for a multi-year production system is a strong indicator that A.6 is not effectively implemented.

Retirement and decommissioning — no dedicated Annex A control

There is no A.6.2.9. A.6.2 ends at A.6.2.8 (recording of event logs), so retirement is audited through other requirements rather than against a control of its own: the A.6.1.3 responsible design-and-development process should define the retirement stage, Clause 8.1 operational planning and control requires the process to be carried out as planned, A.4.2 resource documentation and the AI inventory must be updated, and A.7 plus Clause 7.5 govern what happens to data and records. An exam answer that cites "A.6.2.9" is wrong; an answer that raises retirement against the life cycle process and operational control is right.

Retirement controls prevent “zombie models” that still serve traffic or leak data:

Decision and approval to retire; replacement or manual process.

Disable endpoints, keys, and scheduled jobs.

Archive or securely destroy models, prompts, and data per retention rules.

Notify dependent teams and, where required, interested parties.

Update inventory, SoA references, and monitoring coverage.

Probe: Sample one retired system—confirm no residual inference path and that records remain for the retention period required by the AIMS and law.

Auditor probe set: production reality

Use this checklist in Stage 2 interviews and demos:

Show the production model ID and open its registry/docs.

Show live or recent monitoring for quality/drift (not only uptime).

Pull one incident or override from logs; walk detection → response → record.

Demonstrate rollback procedure and last test/use.

Correlate a recent retrain/deploy event in the life cycle log with monitoring baselines reset.

Ask who is paged when fairness or drift thresholds breach—validate competence and authority.

Integrated ISMS/AIMS tip: Security logging may exist while decision logs do not. Conversely, ML platforms may log predictions without protecting log integrity. Test both layers when AI decisions are in scope.

Exam scenarios often contrast (a) strong offline V&V with uncontrolled deploy, (b) monitoring without ownership/escalation, (c) documentation that does not match production, and (d) missing rollback. Correct answers emphasize operational control and reconstructability , not tool brand names.