In depth
ISO/IEC 42001 follows the same harmonized structure as ISO/IEC 27001, so the two can run as one management system. Its clauses 4 to 10 cover context and scope, leadership and AI policy, planning (including AI risk assessment and AI system impact assessment), support, operation, performance evaluation (including internal audit and management review) and improvement. Annex A lists 38 controls in nine areas: AI policies, internal organization, resources, impact assessment, the AI system life cycle, data, information for interested parties, use of AI systems, and third-party and customer relationships. An organization records which controls apply, and why, in a Statement of Applicability. Certification is awarded by an accredited certification body after a two-stage audit, first of the documentation and then of the system in operation, and runs on a three-year cycle with annual surveillance audits.
Why it matters
Customers, regulators and procurement teams increasingly ask organizations to show how they govern AI, not just to state it. ISO/IEC 42001 gives a recognized, auditable answer and a structure that can be run alongside an existing security management system. Like any management system, it is certified on evidence of operation: an inventory of AI systems, records of what they did, proof that intended-use boundaries were enforced, and controls on AI suppliers. Ferentin publishes a control-by-control mapping of how its platform supports an ISO/IEC 42001 AI management system.
Common use cases
- Preparing for ISO/IEC 42001 certification
- Extending an ISO/IEC 27001 security management system to cover AI
- Structuring AI risk and AI system impact assessments
- Answering AI governance questions in customer and vendor assessments
- Producing operating evidence for Annex A controls such as event logging and intended use
How Ferentin handles it
Ferentin is the trust layer for AI agents. The platform centralizes identity, policy enforcement and audit across LLMs, MCP servers and AI tools. ISO/IEC 42001 is one of the primitives this trust layer is designed around. See the platform overview for how it fits into the service edge, control plane and observability plane.