Study guide
5.1 Clause 7 Support
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
5.1 Clause 7 Support
Key Takeaways Explain This Topic AI
Clause 7.1 requires resources adequate for establishing, implementing, maintaining, and continually improving the AIMS—including people, compute, data infrastructure, tooling, and specialist support.
Clause 7.2 competence is a four-step loop: determine needed competence, ensure people are competent (education/training/experience), evaluate effectiveness of actions taken, and retain appropriate evidence.
Clause 7.3 awareness covers the AI policy, contribution to AIMS effectiveness, implications of not conforming, and benefits of improved AI performance—not a one-slide annual video alone.
Clause 7.4 requires determining what, when, with whom, how, and who communicates—internally and externally—for AI-relevant topics such as incidents, model changes, and transparency notices.
Clause 7.5 documented information must be created/updated with identification, format, and review/approval, then controlled for availability, protection, distribution, retention, and disposition—critical for model cards, SoA, impact assessments, and training records.
Last updated: August 2026
5.1 Clause 7 Support
Auditor focus: Do people, tools, and records exist so the AIMS can work? Can the organization prove competence for AI roles? Are model cards, impact assessments, and the SoA controlled as documented information—not orphan files on a laptop?
Clause 7 is the Support block of the Harmonized Structure. After Clauses 4–6, the organization must equip the AIMS with resources, competent people, aware personnel, planned communication, and controlled documented information. For AI, support failures are concrete: wrong people approve models, training is generic "AI ethics" with no role mapping, and critical artifacts lack version control.
Subclause Map for Auditors
Subclause Requirement theme Evidence auditors request Frequent weakness
7.1 Resources AI governance capacity, MLOps/monitoring platforms, compute/data pipelines Policy exists; no sustained tooling for oversight
7.2 Competence Role matrix, training records, effectiveness checks Certificates collected; effectiveness never evaluated
7.3 Awareness Campaign materials; interview probes Staff know a policy exists but not contribution or nonconformity implications
7.4 Communication Plan for what/when/whom/how/who No plan for model-change or external transparency notices
7.5 Documented information SoA, model cards, impact assessments, training evidence under control Uncontrolled wikis; model cards with no owner/version
7.1 Resources
The organization shall determine and provide resources needed to establish, implement, maintain, and continually improve the AIMS.
Resource type AI-specific examples Why auditors care
People Model owners, AI risk roles, data stewards, human-oversight operators Unowned production models; committees with no capacity
- Infrastructure Compute, feature stores, logging/monitoring stacks Monitoring promised but no platform
- Data & information Evaluation sets, lineage tooling Bias/impact work starved of resources
- Budget / time Independent evaluation, gated releases "Ship weekly" with zero gate funding
- External support Specialists, validators, cloud AI under contract Over-reliance without oversight
Probe: If risk treatment requires drift monitoring but tooling and on-call roles are "next year," 7.1 (and linked Clause 8) is in play.
7.2 Competence
Competence is the most exam-sensitive Support subclause—a closed loop:
Determine necessary competence for persons whose work affects AIMS performance and AI outcomes.
Ensure competence via education, training, or experience.
Where applicable, take actions to acquire competence and evaluate effectiveness of those actions.
Retain documented information as evidence of competence.
Role Competence themes to sample Evidence examples
Data scientists / ML engineers Evaluation design, bias metrics, secure MLOps Project history, evaluation reports
Model / product owners Risk tiering, gates, impact assessment, change control Decision records, procedure training
- AI risk / compliance 42001 process, risk method, residual risk acceptance Method training, authored risk files
- Human-oversight operators Escalate/stop rules, interface limits, authority Scenario drills, SOP sign-off
Procurement / vendor managers Third-party AI due diligence, contract clauses RFP checklists, supplier assessments
Effectiveness trap: An LMS completion rate of 100% without post-training assessment, observed correct use of release checklists, or other effectiveness evaluation does not close the 7.2 loop.
Scenario: A bank maps all data scientists to "AI ethics e-learning," yet credit-model owners cannot design fairness evaluation and outsource it without understanding results. Finding: 7.2—competence not determined/ensured for roles affecting AI outcomes; effectiveness of actions not evaluated.
7.3 Awareness
Persons doing work under the organization's control shall be aware of the AI policy , their contribution to AIMS effectiveness (including benefits of improved AI performance), and the implications of not conforming .
Awareness is broader than competence. A call-center agent may not need model-training skill, but must know acceptable use, data restrictions, escalation, and that shadow public chatbots for customer data are nonconforming.
Interview probe: What is the AI policy about? What if you paste personal data into an unapproved tool? How do you escalate a harmful output?
7.4 Communication
Determine internal and external communications relevant to the AIMS: on what , when , with whom , how , and who communicates.
- Direction Example topics
- Internal Policy updates; go-live/rollback; operator limitations; incident reporting
- External Transparency notices; regulator notifications; customer model-change notices; supplier coordination
Trap: "We have Slack and a website" is not a determination. High-impact systems need accountable channels for incidents, bias findings, and material model changes.
7.5 Documented Information
Create/update (7.5.2): identification and description (title, date, author, reference), format/media, review and approval for suitability.
Control (7.5.3): availability and protection; distribution, access, retrieval, use, storage, preservation, change control, retention, disposition. Control external-origin documented information determined necessary for the AIMS (vendor model cards, API terms, evaluation reports).
- Artifact Sampling expectation
- AI policy & objectives Approved, accessible
- SoA Versioned, approved, linked to risk treatment
- Risk / treatment files Current, change-controlled
- Impact assessments Identified, approved, retrievable
- Model / system cards Owner; version matches deployed model ID
- Competence records Retained as 7.2 evidence
- Auditor sampling of training records and AI docs
Pull document-control rules.
Sample 3–5 AI systems across risk tiers.
Trace: production model ID → model card → impact assessment → risk file → SoA references → model-owner competence evidence.
Test version alignment (card vs live model) and orphan stores (uncontrolled wikis/drives as the real procedure).
Scenario: Chatbot v3.2 is live; model card is an unapproved shared doc describing v2.1; impact assessment is email-only. Primary hook: 7.5 (often with 8.1).
Common Nonconformities
Resources promised in treatment plans not provided; competence as "data science degree" without AI-risk skills; training without effectiveness evaluation; awareness as generic IT modules only; no external communication determination; SoA/model cards/impact assessments uncontrolled or misaligned with deployment; vendor docs not identified as external-origin controlled information.
Clause 7 enables Annex A and Clause 8—it does not replace them. Weak support predicts operational evidence collapse.