Internal Audits
Purpose
This procedure sets Rygen Technologies’ internal audit program for the AI Management System (AIMS), as ISO/IEC 42001:2023 Clause 9.2 requires. Internal audits show whether the AIMS conforms to Rygen’s own requirements and to the standard, and whether it is effectively implemented and maintained.
Scope
This procedure applies to every internal audit of the AIMS. Audits cover all processes, activities and areas within the AIMS scope, including:
- AI systems (X1 Platform, Corsair, internal AI tools)
- AIMS processes and procedures, including AI governance and risk management
- All organizational units involved in AI activities
Audit Program Framework
Audit Frequency
An AIMS internal audit is conducted annually. Appendix A.1 sets the clauses each year’s audit covers. The Annex A control effectiveness audit is also annual (see Control Effectiveness Verification).
Audit Method
Audits use:
- Document review of AIMS documentation and records
- Observation of AI activities and processes
- Interviews with personnel involved in AI activities
- Representative sampling of AI systems and processes
- Verification of implementation through objective evidence
Responsibilities
- Principal AI Engineer: audit program owner; plans and schedules audits and approves audit reports. The lead auditor for each audit is named in the annual audit schedule.
- CTO: approves the audit program, allocates resources, and manages audit results.
- AI Governance Committee: receives audit reports. The Principal AI Engineer approves corrective action plans (AI-014).
- Team Leads: support audits, give access to personnel and records, and implement corrective actions.
- Auditees: cooperate with audits, provide requested information, and take part in interviews.
Audit Planning and Scheduling
The Principal AI Engineer shall develop the annual audit plan for the following year by December 31st. The plan takes into account the importance of each process, the results of previous audits, risk assessment outcomes, new AI systems or processes, auditor availability and workload, and business priorities.
Audit Process
Audit Preparation
Each audit defines its objectives, criteria and scope.
- Objectives: verify conformity to requirements, assess effectiveness and identify improvements, with focus areas drawn from risk assessment and previous audit results.
- Criteria: internal requirements (AIMS policies and procedures, AI governance frameworks, risk management processes, and performance objectives and targets) and external requirements (ISO/IEC 42001:2023, applicable legal and regulatory requirements, and client contractual requirements).
- Scope: the processes, organizational units, time period and locations covered, and any exclusions with the reason for each.
Auditor Selection and Competence
The lead auditor needs ISO 42001 knowledge and certification, AIMS implementation experience, auditing skills and experience, and objectivity and impartiality.
Additional auditors, when needed, are selected for technical expertise, process knowledge, availability, and objectivity, meaning no responsibility for the area being audited.
To ensure objectivity and impartiality:
- Auditors shall not audit their own work.
- There is no direct reporting relationship between auditor and auditee.
- External auditors may be used where internal objectivity is compromised.
- Audit assignments are rotated when practical.
Audit Execution
An opening meeting confirms the audit objectives, criteria, scope, plan and timeline, and how the auditor and auditees will communicate.
The auditor gathers information by the methods above:
- Document review: AIMS policies and procedures, process documentation, records, previous audit reports, and corrective action records
- Process observation: AI development, AI system operation, risk management, and training and competence activities
- Personnel interviews: structured interviews on roles and responsibilities, knowledge of procedures, and training and competence
The auditor collects objective evidence, judges conformity and the effectiveness of implementation, identifies areas for improvement, and records each finding with its supporting evidence.
A closing meeting presents preliminary findings, discusses observations, clears up misunderstandings, and sets next steps and a timeline.
Audit Findings and Reporting
Finding Classification
Major Nonconformity
The absence of, or failure to implement, a requirement; a situation that would seriously affect the AIMS’s capability; or a pattern of minor nonconformities in the same area.
Minor Nonconformity
An isolated failure to meet a requirement that is unlikely to seriously affect AIMS capability, including documentation issues that do not affect implementation.
Observation
An area for potential improvement, good practice worth noting, or a trend that could become an issue.
Audit Report Content
Each audit report shall include:
- Executive summary: key findings and overall assessment
- Audit details: objectives, criteria, scope, dates and participants
- Findings, with evidence and references
- Conclusions on overall conformity and effectiveness
- Recommendations for improvement
- Appendices with supporting documentation and evidence
Report Distribution
Audit reports shall be distributed to:
- The CTO, within 5 business days
- AI Governance Committee members
- Auditees and their managers
- The audit record in the aims-governance repository
Follow-up and Corrective Action
Corrective Action Requirements
- Major nonconformities require an immediate corrective action plan.
- Minor nonconformities require corrective action under AI-014 by the target date set in the CAR.
- Observations are considered for improvement planning.
Corrective Action Process
Corrective action follows AI-014: root cause analysis, action planning, implementation, verification of effectiveness, and closure once the action is verified effective.
Follow-up Audits
Corrective action effectiveness is verified under AI-014. A follow-up audit is conducted when management requests more verification.
Control Effectiveness Verification
Annual Control Effectiveness Audit
Annex A control effectiveness shall be audited every year in a dedicated audit, separate from the annual internal audit. The dedicated audit shall assess every Annex A control against three criteria:
- Existence: does objective evidence exist, and is it current?
- Implementation: is the control operating as described in the AIMS documentation?
- Outcome: is the control producing the intended result?
The annual internal audit shall sample a subset of controls for effectiveness rather than re-auditing all of them.
The annual audit schedule sets the timing of the dedicated audit. Its plan and checklist templates are kept in the aims-governance repository.
Audit Records and Documentation
Required Records
- Annual audit plans
- Individual audit plans
- Audit checklists and working papers
- Audit reports
- Corrective action plans and evidence
- Follow-up audit reports
- Auditor competence records
Record Management
- Storage:
content/audits/in the aims-governance repository, one directory per audit - Retention: at least 3 years
- Backup: included in organizational backup procedures
- Access: controlled by role and responsibility
Program Evaluation and Improvement
Program Effectiveness Monitoring
Audit program effectiveness is judged from audit completion against the schedule, trends in findings, and the status of corrective actions, as reported at each management review.
Program Review and Improvement
- Continuous: updates for changes in AIMS scope or processes, new requirements or standards, lessons learned from audits, stakeholder feedback, and external audit recommendations
Integration with Management Review
Audit program results are an input to management review: audit activities and findings, trends in nonconformities and observations, corrective action effectiveness, recommended AIMS improvements, and audit completion against the schedule. Appendix A.4 sets the frequency and source of each input.
Templates and Forms
Each year’s audit schedule is kept as content/audits/AUD-schedule-YYYY.md. The following templates support this procedure:
- Internal audit checklist:
internal-audit-checklist-template.md - Control effectiveness audit plan and checklist:
control-effectiveness-audit-plan-template.mdandcontrol-effectiveness-audit-checklist-template.md - Corrective action report:
corrective-action-report-template.md
Templates are in content/templates/ in the aims-governance repository. Each audit’s plan and report follow the contents this procedure sets.
Revision History
| Version | Date | Author | Summary of Change |
|---|---|---|---|
| 1.0 | 2025-06-05 | Field Bradley | Initial draft. |
| 1.1 | 2025-09-02 | Field Bradley | Migrated to markdown and gitlab |
| 1.2 | 2025-01-13 | Field Bradley | Added Audit Program Appendix (A.1-A.6) |
| 1.3 | 2026-03-09 | Hank Galbraith | Added annual control effectiveness verification requirement |
| 1.4 | 2026-07-14 | Field Bradley | Audit-results reporting to management review aligned to the every-four-months review cadence (AI-1759) |
| 1.5 | 2026-09-15 | Field Bradley | Corrected the audit-record storage and distribution locations from Confluence to the aims-governance repository, which is where the records are held (AI-1976) |
| 2.0 | 2026-11-09 | Field Bradley | Shortened every section, corrected approvals, cross-references and dates, and removed the mandatory audit triggers, keeping the annual internal audit and escalation re-audits (AI-2173, AI-2131). The committee receives audit reports; minor nonconformities follow the CAR target date; effectiveness is verified under AI-014; program effectiveness is judged from what management review reports. |
| 2.1 | 2026-11-10 | Field Bradley | The Principal AI Engineer may be named lead auditor. Auditors still do not audit their own work (AI-1976). |
Appendix: Audit Program
A.1 Three-Year Audit Cycle Schedule
Every ISO/IEC 42001:2023 clause is audited at least once in a three-year cycle. High-risk areas are audited every year, and lower-risk foundational elements rotate.
Audit Coverage by Year
| Section | Title | Y1 | Y2 | Y3 | Frequency |
|---|---|---|---|---|---|
| Clause 4: Context of the Organization | |||||
| 4.1 | Understanding the Organization and Its Context | X | Triennial | ||
| 4.2 | Understanding Needs and Expectations of Interested Parties | X | Triennial | ||
| 4.3 | Determining the Scope of the AIMS | X | Triennial | ||
| 4.4 | AI Management System | X | Triennial | ||
| Clause 5: Leadership | |||||
| 5.1 | Leadership and Commitment | X | Triennial | ||
| 5.2 | AI Policy | X | X | X | Annual |
| 5.3 | Roles, Responsibilities and Authorities | X | Triennial | ||
| Clause 6: Planning | |||||
| 6.1.1 | Actions to Address Risks and Opportunities - General | X | X | X | Annual |
| 6.1.2 | AI Risk Assessment | X | X | X | Annual |
| 6.1.3 | AI Risk Treatment | X | X | X | Annual |
| 6.1.4 | AI System Impact Assessment | X | X | X | Annual |
| 6.2 | AI Objectives and Planning to Achieve Them | X | Triennial | ||
| 6.3 | Planning of Changes | X | X | Biennial | |
| Clause 7: Support | |||||
| 7.1 | Resources | X | Triennial | ||
| 7.2 | Competence | X | X | Biennial | |
| 7.3 | Awareness | X | Triennial | ||
| 7.4 | Communication | X | Triennial | ||
| 7.5.1 | Documented Information - General | X | X | Biennial | |
| 7.5.2 | Creating and Updating | X | X | Biennial | |
| 7.5.3 | Control of Documented Information | X | X | Biennial | |
| Clause 8: Operation | |||||
| 8.1 | Operational Planning and Control | X | X | X | Annual |
| 8.2 | AI Risk Assessment (Operational) | X | X | X | Annual |
| 8.3 | AI Risk Treatment (Operational) | X | X | X | Annual |
| 8.4 | AI System Impact Assessment (Operational) | X | X | X | Annual |
| Clause 9: Performance Evaluation | |||||
| 9.1 | Monitoring, Measurement, Analysis and Evaluation | X | X | X | Annual |
| 9.2.1 | Internal Audit - General | X | Triennial | ||
| 9.2.2 | Internal Audit Program | X | Triennial | ||
| 9.3 | Management Review | X | X | X | Annual |
| Clause 10: Improvement | |||||
| 10.1 | Continual Improvement | X | X | X | Annual |
| 10.2 | Nonconformity and Corrective Action | X | X | X | Annual |
Annual Focus Summary
Year 1 focuses on context (4.1 to 4.4), risk and impact (6.1.x), operations (8.x) and policy (5.2). Year 2 focuses on leadership (5.1, 5.3), objectives (6.2), resources (7.1) and the internal audit program (9.2.x). Year 3 focuses on awareness (7.3) and communication (7.4). Annual items are covered every year, and biennial items (6.3, 7.2, 7.5.x) in Years 1 and 3.
A.2 Audit Frequency Definitions
The Frequency column in A.1 assigns each clause to one of these frequencies.
| Frequency | Rationale |
|---|---|
| Annual (every year) | High-risk areas with direct impact on AI system safety, effectiveness and compliance |
| Biennial (every two years) | Medium-risk supporting processes that change moderately often |
| Triennial (every three years) | Lower-risk foundational elements that change rarely |
A.3 Escalation Criteria and Re-Audit Requirements
Nonconformities found in an audit are escalated and re-audited as follows.
Escalation Matrix
| Finding Type | Immediate Actions | Re-Audit Required | Re-Audit Timeline |
|---|---|---|---|
| Major Nonconformity | Notify CTO and AI Governance Committee within 24 hours; immediate corrective action plan required | Yes, full clause re-audit | Within 60 days of corrective action implementation |
| Multiple Minor Nonconformities (3 or more in the same clause) | Escalate to CTO; root cause analysis required | Yes, targeted re-audit of the affected area | Within 60 days of corrective action completion |
| Single Minor Nonconformity | Standard corrective action per AI-014 | Verification only, not a full re-audit | At next scheduled audit |
| Repeat Nonconformity (same finding as previous audit) | Escalate to CTO; effectiveness review of previous corrective action | Yes, expanded scope re-audit | Within 60 days of corrective action completion |
| Pattern of Observations (3 or more related observations) | Review at next management review | Optional, at auditor discretion | At next scheduled audit |
Scope Expansion Criteria
A re-audit’s scope may be expanded as follows:
| Original Finding Scope | Expansion Criteria | Expanded Scope |
|---|---|---|
| Single process | Root cause affects multiple processes | Related processes in same clause |
| Single AI system | Systemic issue identified | All AI systems using same process or component |
| Documentation issue | Control effectiveness concern | Full clause including implementation |
| Implementation gap | Training or competence concern | Add Clause 7.2 (Competence) to scope |
A.4 Integration with Management Review
Audit program results are reported to the management review (AI-012) as follows:
| Input | Frequency | Source |
|---|---|---|
| Audit completion status against schedule | Every four months | Audit program records |
| Summary of findings by clause | Every four months | Audit reports |
| Corrective action status and effectiveness | Every four months | Jira and corrective action records |
| Trend analysis of nonconformities | Every four months | Historical audit data |
| Re-audit results and outstanding items | Every four months | Re-audit reports |
| Recommended schedule adjustments | Annual | Audit program review |
A.5 AIMS Document to ISO Clause Cross-Reference
This table maps AIMS handbook documents to the ISO/IEC 42001:2023 clauses they address, for audit planning and evidence collection:
| AIMS Document | ID | Primary ISO Clause(s) |
|---|---|---|
| AI Policy | AI-001 | 5.2 |
| AIMS Objectives | AI-002 | 6.2 |
| AIMS Scope | AI-003 | 4.1, 4.2, 4.3 |
| AIMS Charter | AI-004 | 4.4, 5.1 |
| Roles and Responsibilities | AI-005 | 5.3, 7.1 |
| Document Control | AI-006 | 6.3, 7.5.1, 7.5.2, 7.5.3 |
| Communication Policy | AI-007 | 7.4 |
| Risk Management Framework | AI-008 | 6.1.1, 6.1.2, 6.1.3, 8.2, 8.3 |
| Impact Assessment Process | AI-009 | 6.1.4, 8.4 |
| Security Policy | AI-010 | 8.1 |
| Data Management | AI-011 | 8.1 |
| Management Review | AI-012 | 6.3, 9.3 |
| System Development Lifecycle | AI-013 | 8.1 |
| Nonconformity and Corrective Action | AI-014 | 10.1, 10.2 |
| Internal Audit | AI-015 | 9.2.1, 9.2.2 |
| Acceptable Use Policy | AI-016 | 8.1 |
| Performance Monitoring | AI-017 | 9.1 |
| Competency Matrix | AI-018 | 7.2 |
| Governance Committee Roles | AI-019 | 5.3 |
| Approved Tools | AI-020 | 8.1 |
| Training and Competence | AI-021 | 7.2, 7.3 |
| Statement of Applicability | AI-022 | 6.1.3 |
| Incident Response | AI-023 | 8.1 |
| Problem-Definition Method | AI-024 | 8.1 |