Skip to content
NZSNextZen SecuritySecure AI engineering

Insights

ISO/IEC 42001 versus ISO 27001: what AI companies actually need

ISO/IEC 27001:2022 addresses information security management. ISO/IEC 42001:2023 addresses AI management. The appropriate scope and sequence depend on your activities, risks, and assurance requirements.

By Shantanuu Roy

What each standard covers

ISO/IEC 27001:2022 specifies requirements for an information security management system. Its focus is the management of information security risk within a defined scope, including the protection of confidentiality, integrity, and availability. Certification concerns conformity of that management system to the standard. It does not certify that every product is secure or that an organization will avoid all security incidents.

ISO/IEC 42001:2023 specifies requirements for an AI management system. It addresses organizational responsibilities for developing, providing, or using AI systems within a defined scope. Relevant concerns include AI risk assessment, impact assessment, lifecycle processes, and responsible use. Certification does not establish that a model is always accurate, that an application is suitable for every purpose, or that all legal obligations are satisfied.

Define scope before comparing requirements

Start by identifying the services, teams, locations, and activities the management system will cover. An organization using an external model in a support workflow has different responsibilities from one developing models for external distribution. Record the AI inventory and the role performed for each system. A broad statement that the company uses AI is not enough to select meaningful controls or prepare evidence.

Read certificate scopes carefully during procurement. A certificate covering a limited internal function may not cover the service a buyer is evaluating. Ask how the offered application, operating team, and relevant dependencies relate to the certified scope. The same care applies to suppliers: a supplier certificate can inform assurance, but it does not transfer responsibility for integration choices or downstream use.

Where they overlap

Both standards use a management-system structure that includes organizational context, leadership, planning, support, operation, performance evaluation, and improvement. Existing processes for document control, competence, internal audit, management review, and corrective action can support an integrated approach. Reuse is sensible when the process actually addresses both scopes and gives the relevant decision makers the information they need.

Risk treatment also needs a documented rationale. Both standards include reference controls in Annex A, but their control sets serve different purposes and should not be treated as interchangeable. Applicability decisions should follow the relevant requirements and assessment results. Copying a control mapping does not demonstrate implementation, and a shared policy needs evidence that it operates for the AI activities in scope.

Where ISO/IEC 42001 goes further

AI management requires explicit attention to intended use and effects on individuals, groups, and society. AI system impact assessment is related to risk assessment but should not be reduced to a conventional security checklist. A system may preserve confidentiality while producing outcomes that are unsuitable for its intended users. The organization needs a process for examining such effects and determining appropriate responses.

Lifecycle evidence should connect requirements, data decisions, development or acquisition, verification, deployment, and operation. Depending on the system and applicable controls, this may include data provenance, quality criteria, evaluation limitations, human oversight, and information supplied to users. Changes in intended use or operating conditions should trigger review. A model update is not merely an infrastructure change when it alters relevant behavior or limitations.

Build evidence from operating processes

For a practical gap analysis, select a system and trace its records from approval through operation. Check whether ownership is clear, assessments reflect the current design, and risk treatments have observable evidence. Inspect how incidents, complaints, and evaluation failures reach responsible owners. Policies provide direction; tickets, approvals, test results, and review records show whether that direction is followed.

NIST AI RMF 1.0 can help organize AI risk activities through Govern, Map, Measure, and Manage. It is a voluntary risk management framework, not an alternative ISO certification standard. Likewise, technical references such as the OWASP Top 10 for LLM Applications 2025 can inform security scenarios without covering every management-system requirement. Map references to specific needs rather than claiming that one checklist satisfies them all.

Which to pursue first

Sequence work according to actual obligations, customer requirements, existing capabilities, and the risks of the services in scope. An information security management system may address an immediate assurance gap, while an AI management system may be necessary to formalize oversight of AI activities. Neither sequence is universal. An integrated program can share supporting processes while keeping distinct objectives and assessment criteria visible.

Before seeking certification, confirm the intended scope, applicable requirements, operating evidence, and internal audit arrangements. Keep remediation ownership separate from independent audit judgments. Explain to buyers what has been certified and what remains outside scope. The useful outcome is a management system that supports decisions and correction during operation, rather than a certificate presented as a substitute for technical evaluation or continuing accountability.

Review the scope as responsibilities change. Adding a new external use case, a different data source, or delegated decision authority can require updated assessments and controls even when the same underlying model remains in use.

← All insights

Tell us what changed.

Thirty minutes, no obligation. Written scope and fixed-fee proposal within one business day of your call.