Study guide

3.8 Statement of Applicability (SoA) Development & Justification

PECB Certified ISO/IEC 42001 Lead Implementer Study Guide Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: AI & AIMS Fundamental Concepts & Frameworks

1.1 Artificial Intelligence Concepts, Terminology & Taxonomy (ISO/IEC 22989 & 23053) 1.2 The ISO/IEC Standards Family for AI (42001, 23894, 5338, 38507, 42005) 1.3 Responsible AI Principles: Fairness, Transparency, Explainability, Safety & Robustness 1.4 Global AI Regulatory Landscape & Governance (EU AI Act, NIST AI RMF, Executive Orders) 1.5 The EU AI Act (Regulation 2024/1689): Risk Tiers, Compliance Obligations & Timeline 1.6 PECB Certification Framework & Lead Implementer Professional Role 1.7 Exam Format, Mechanics & PECB Credentialing Requirements

2 Chapter 2: ISO/IEC 42001 AIMS Core Requirements (Clauses 4-10)

2.1 Annex SL High-Level Structure & Harmonized Management System Principles 2.2 Clause 4: Context of the Organization & Understanding Interested Parties 2.3 Clause 5: Leadership, Commitment & Top Management Responsibilities 2.4 Clause 6 & 7: Planning & Support Infrastructure for AIMS 2.5 Clause 8, 9 & 10: Operation, Performance Evaluation & Continual Improvement Requirements

3 Chapter 3: Planning the AIMS Implementation & AI Risk Management

3.1 AIMS Project Initiation, Implementation Roadmap & Business Case 3.2 AIMS Scope Definition & Organizational Boundaries (Clause 4.3) 3.3 AI Policy Formulation, Leadership Commitment & Governance Structure 3.4 Baseline Gap Analysis & Readiness Assessment 3.5 AI Risk Assessment Methodology (ISO/IEC 23894 & Clause 6.1.2) 3.6 AI System Impact Assessment (Clause 6.1.4 & Annex A.5) 3.7 AI Risk Treatment Planning, Control Selection & Risk Acceptance 3.8 Statement of Applicability (SoA) Development & Justification

4 Chapter 4: Implementing Annex A Controls - Governance, Resources & Lifecycle

4.1 Annex A Overview & Control Architecture (38 Controls Across 9 Objectives A.2–A.10) 4.2 Policies & Internal Organization for AI (Annex A.2 & A.3) 4.3 Resources & Competence for AI Systems (Annex A.4) 4.4 AI System Life Cycle Controls: Objectives, Design & Development (Annex A.6.1–A.6.2.4) 4.5 AI System Verification, Validation, Deployment & Operation (Annex A.6.2.5–A.6.2.9) 4.6 Technical Documentation, Logging & Record-Keeping for AI Systems

5 Chapter 5: Implementing Annex A Controls - Data, Transparency, Use & Third Parties

5.1 Data Governance for AI Systems: Quality, Provenance & Preparation (Annex A.7) 5.2 Bias Mitigation & Fairness Engineering in AI Systems 5.3 Explainability, Interpretability & Transparency Methods (LIME, SHAP, Datasheets) 5.4 Information for Interested Parties & Communication (Annex A.8) 5.5 Use of AI Systems & Responsible Usage Controls (Annex A.9) 5.6 Third-Party Relationships, Vendor Risk & AI Supply Chain (Annex A.10)

6 Chapter 6: Monitoring, Performance Evaluation & Certification Audit Preparation

6.1 AIMS Performance Monitoring, Metrics & Key Performance Indicators (Clause 9.1) 6.2 Data Drift, Concept Drift & AI Model Performance Monitoring 6.3 Internal Audit of the AIMS (ISO 19011 & Clause 9.2) 6.4 Management Review & Operational Suitability Evaluation (Clause 9.3) 6.5 Nonconformity Management, Root Cause Analysis & Corrective Actions (Clause 10) 6.6 Certification Audit Preparation: Stage 1, Stage 2, Surveillance & Recertification

3.8 Statement of Applicability (SoA) Development & Justification

Key Takeaways Explain This Topic AI

The Statement of Applicability (SoA) is a mandatory document under Clause 6.1.3(d) detailing which Annex A controls are selected or excluded, with explicit justifications.

Certification auditors rely on the SoA as the definitive roadmap to verify the scope, applicability, and operational status of an organization's AIMS controls.

Exclusions of Annex A controls must be supported by valid technical, legal, operational, or role-based justifications; arbitrary exclusions result in audit non-conformities.

The SoA is a dynamic, living document that must be updated whenever significant changes occur in the organization's AI portfolio, risk profile, or regulatory context.

Last updated: July 2026

3.8 Statement of Applicability (SoA) Development & Justification

The Statement of Applicability (SoA) is arguably the single most important document produced during an ISO/IEC 42001 implementation. Required under Clause 6.1.3 (d) , the SoA serves as the primary bridge between the organization's risk assessment results and the normative control framework of Annex A . Certification auditors utilize the SoA as their primary roadmap to evaluate which controls apply, how they are implemented, and whether any excluded controls are legitimately justified.

Mandatory Elements of the Statement of Applicability

Under Clause 6.1.3 (d), the SoA must cover all 38 controls defined across Annex A.2 through A.10. For every single control, the document must explicitly state:

Control Reference & Title: The precise Annex A control reference number and name (e.g., A.6.2 Data Quality for AI Systems).

Applicability Designation: Clear designation of whether the control is Applicable or Excluded .

Justification for Inclusion: Summary of the risk assessment findings, impact assessments, legal mandates, or business requirements that necessitate the control.

Justification for Exclusion: Detailed technical, legal, operational, or role-based rationale explaining why a control is not applicable (required for every excluded control).

Implementation Status: Current operational state (e.g., Implemented , In Progress , or Planned ).

Supporting Document References: Direct cross-references to supporting policies, SOPs, architectural diagrams, or audit logs.

Sample Auditable Statement of Applicability Structure

The following table illustrates the required format for an auditable ISO/IEC 42001 SoA:

Control ID Control Name Applicable? Implementation Status Technical & Risk Justification Supporting Artifacts

A.5.2 AI System Validation & Testing Yes Implemented Mandatory; mitigates risk of model accuracy degradation and unexpected behavior in credit underwriting. SOP-ML-VAL-004 , Model Validation Logs

A.6.3 Training Data Quality & Representativeness Yes Implemented Required under Clause 6.1.4 Impact Assessment to eliminate demographic bias in underwriting algorithms. DATA-GOV-SPEC-02 , Bias Audit Reports

A.5.6 AI System Design for Custom Pre-Training No (Excluded) N/A (Excluded) Excluded. Organization operates strictly as an AI Deployer utilizing commercial APIs; no custom pre-training performed. AIMS-SCOPE-STMT-01 , Vendor Policy

A.7.1 Transparency Disclosures to Users Yes Implemented Mandatory; ensures user notice when interacting with automated conversational AI tools. NOTICE-AI-DISCLOSURE , UX Specs

A.8.2 Human Oversight & Intervention Yes Implemented Mandatory under EU AI Act alignment; ensures human-in-the-loop review for high-risk automated rejections. OPS-HUMAN-OVER-01 , Escalation SOP

A.9.1 Supplier Risk Assessment for AI Yes In Progress Essential to manage third-party LLM API dependencies, data privacy, and service availability risks. VENDOR-RISK-FRAMEWORK , SLA Contracts

A.10.3 Operational Logging & Audit Trails Yes Implemented Required to record input prompts, model versions, and outputs for post-incident auditability. LOG-ARCH-SPEC-09 , SIEM Dashboards

Rules & Principles for Control Exclusions

Excluding an Annex A control is permissible, but subject to strict audit scrutiny:

Role-Based Exclusion Rules: An organization operating strictly as an AI Deployer (using external LLM APIs) may legitimately exclude custom pre-training controls under Annex A.5, provided it justifies how third-party risks are managed under Annex A.9.

No Arbitrary Exclusions: Stating "not required" or "not feasible" is an automatic audit non-conformity. Exclusions must reference specific operational boundaries or technical facts.

Interdependency Rules: An organization cannot exclude data quality controls (Annex A.6) while claiming to train custom machine learning models in-house.

Common SoA Audit Non-Conformities & How to Avoid Them

During Stage 1 and Stage 2 certification audits, external auditors subject the SoA to intense scrutiny. Implementers must avoid these common failure modes:

Unjustified Exclusions: Marking controls as "Excluded" without documenting a valid, technical, or risk-backed rationale.

Role Misalignment: An organization declaring itself an AI Producer while attempting to exclude Annex A.5 development controls, or an AI Deployer excluding Annex A.9 third-party controls.

Disconnect from Risk Register: Selecting controls in the SoA that do not correspond to any identified risks in the Clause 6.1.2 Risk Register, or leaving high-severity risks unmitigated by selected controls.

Static Document Management: Treating the SoA as a one-time project artifact rather than maintaining it as a living document.

SoA Maintenance & Lifecycle Change Management

The Statement of Applicability must be reviewed and updated continuously throughout the AIMS lifecycle. Mandatory update triggers include:

New AI System Deployment: Onboarding a new generative AI tool or custom ML algorithm into the enterprise inventory.

Risk Profile Shift: Re-evaluating risks following an AI security incident, model drift event, or bias discovery.

Regulatory Changes: Enactment of new statutory mandates or binding industry standards.

Management Reviews: Annual Clause 9.3 performance evaluations and internal audit findings.

Worked Implementation Scenario: Enterprise SaaS Provider SoA Development

Context: A SaaS company providing AI-driven HR analytics prepares its SoA for an ISO/IEC 42001 certification audit.

Execution Steps:

Control Mapping: The Lead Implementer reviews all 38 Annex A controls against the Clause 6.1.2 Risk Register and Clause 6.1.4 AISIA.

Documenting Inclusions: 35 controls are designated as Applicable , including A.6.3 (Data Quality) and A.8.2 (Human Oversight).

Justifying Exclusions: 3 controls related to hardware data center thermal management are designated as Excluded , with documented justification stating that all infrastructure is hosted in ISO 27001-certified AWS cloud data centers.

Audit Verification: The Stage 1 auditor verifies that all exclusions are supported by cloud SLA artifacts, issuing zero non-conformities.

Lead Implementer Exam Tips

Clause 6.1.3 (d) Requirement: Memorize that the SoA is explicitly mandated under Clause 6.1.3 (d).

All 38 Controls: Remember that the SoA must cover all 38 Annex A controls—omitting a control from the document is an automatic non-conformity.

Justification Requirement: Every single control entry in the SoA requires a documented justification, regardless of whether it is designated as Included or Excluded.