ISO/IEC 42001:2023·Annex A A.8.5·medium·Component: Organizational controls

What this control requires

Appropriate information about AI systems shall be provided to relevant interested parties based on their needs and obligations.
— ISO/IEC 42001:2023, Annex A A.8.5

In plain English

Appropriate information about AI systems shall be provided to relevant interested parties based on their needs and obligations. In practice, this means you can prove you manage ai systems-level controls on a defined cadence.

Why it matters

ISO 42001 is the first audited evidence regulators, customers and investors can ask for that you are managing AI risk. Each Annex A control is a check-box in that audit; it is also the management system enterprises are starting to require from AI vendors before an MSA can be signed.

What an auditor looks for

An ISO 42001 auditor verifies you have an AI policy, a risk-based system of impact assessments for each AI system, lifecycle controls from data acquisition through retirement, and third-party-AI controls that pierce the vendor's wrapper to underlying model behaviour.

Within Organizational controls, the assessor will trace your implementation back to the catalogue reference (Annex A A.8.5) and look for objective evidence on the latest two assessment cycles.

How to implement

Policy Management

Docs. Keep each policy in version-controlled Markdown alongside the code that implements it; ship a signed PDF snapshot at each annual review and link the SHA into the SoA.

Operational checklist

  • Manage. Document the trigger, the owner and the cadence.
  • Monitor. Document the trigger, the owner and the cadence.
  • Scope: ai systems, interested parties.

Evidence to collect

  • Policy Document. A signed and version-controlled policy / standard / procedure document.

Approved policies and controlled records should demonstrate that relevant interested parties receive appropriate information about AI systems based on need and obligation. Focus: Information for interested parties.

Common pitfalls

  • Policies that no engineer has read; the version in Confluence drifts from the version that's actually being enforced.

How it maps to other frameworks

Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit.

Related controls in ISO/IEC 42001:2023

References

Topics: governance risktransparencystakeholder communicationpolicy managementstakeholder management