ISO/IEC 27001 and AI flows

Regulation · ISO/IEC 27001

ISO/IEC 27001 and AI agents: connect mission evidence to the ISMS

A client wants to include an agent mission in its information-security approach. Exporting a log is insufficient: explain which risk is addressed, which measure works, who reviews it and what remains to be corrected. Useful evidence stays tied to the management system’s actual scope.

ISO/IEC 27001 is a management-system standard, not an AI-specific regulation. This article prepares work with ISMS owners. It offers neither a certification audit nor automatic compliance through DUBSAR.

In brief

The question and the useful result.

Question
How should an agent mission connect to the ISMS and the evidence the organisation needs to examine?
Useful result
An ISMS mapping record for a mission and its changes, usable in the client’s existing tools.

ISO/IEC 27001 and AI flows

Understand the standard and certificate

The public ISO/IEC 27001:2022 overview describes requirements for an information security management system: establishing, implementing, maintaining and improving a risk-management approach. ISO’s catalogue also lists Amendment 1:2024 to that edition.

Certification involves independent assessment, as explained on ISO’s certification page. A hosting or software provider’s certificate does not automatically certify the client organisation, its agents or every use. Examine the relevant certificate’s scope, covered services and validity.

The standard’s existence does not make it a universal legal obligation. Contractual commitments or particular requirements can nevertheless make its implementation necessary in a given context. The client should establish that context with appropriate specialists.

ISO/IEC 27001 and AI flows

Prepare an ISMS mapping record

The following record is a preparation method, not a reproduction of the standard or an exhaustive requirements checklist. Public catalogue information was reviewed; the paid full text was not purchased for this article.

FieldInformation to connect
ScopeMission, process, systems, data and exclusions within the relevant ISMS.
RiskUnwanted situation, consequences, owner and reference to the existing assessment.
Selected measureControl, owner, actual implementation point and reason for application.
EvidenceVersion, date, verification method, observation and coverage limits.
GapUnestablished fact, corrective action, owner and closure condition.
Review and recoveryDecision, changes requiring reassessment, work state and assigned outstanding checks.

Connect material to the client’s procedures rather than creating a separate file promising “AI certification”. Selecting and justifying measures must relate to risks and the chosen scope; installing a product does not perform that work.

ISO/IEC 27001 and AI flows

Scenario: a new route after the initial review

In this illustrative example, the team had assessed a mission using a defined model and document store. A new processing route and support access are added. The ISMS owner needs to recover that change and decide which previous checks still apply.

The previous observation does not automatically cover new recipients or access. The integrator describes the change, data, owners and measures requiring reassessment. Existing results remain valid within their original scope, while new checks are assigned.

If a business operation remains uncertain during that transition, recovery must take its unresolved outcome into account. Evidence of a correct configuration does not establish that operation’s effect. This scenario describes no available DUBSAR audit-file export or connector.

ISO/IEC 27001 and AI flows

Separate execution evidence from a management conclusion

An acknowledgement may show that a request was received; a tested access control may show observed behaviour for one configuration. Each item should state that scope. It does not automatically demonstrate every measure’s effectiveness or the absence of incidents over time.

ISMS owners organise review, treatment of gaps and improvement under their approach. A competent certification body assesses evidence within its evaluation; a collection of logs does not replace that decision.

DUBSAR aims to connect durable mission state, authorisations, human decisions and evidence to support those discussions and handover. That role remains under qualification. This page establishes no certification of the product or its user.

ISO/IEC 27001 and AI flows

Frequently asked questions

Is ISO/IEC 27001 an AI-agent law?

No. It is an information security management system standard. Its relevance and the commitments to meet depend on organisational context, contracts and applicable requirements.

Does certified infrastructure extend its certification to the mission?

Not automatically. Examine the certificate, scope and client responsibilities. A mission can use a covered service without all its components, processes and uses being covered.

Does DUBSAR produce a file guaranteeing certification?

No such function or guarantee is established. Mission evidence can be prepared in the client’s tools; assess its scope within the ISMS approach and the relevant evaluation.

ISO/IEC 27001 and AI flows

Where DUBSAR fits

DUBSAR is developing a governance foundation for integrators and teams deploying agents for clients: durable mission state, explicit authorisations, human decisions, evidence and continuation of work. It aims to connect what was requested, what was permitted and what is established about the outcome.

Selected components and workflows have been tested; full B2B integration and validation are still underway. Pilots are not currently open.

ISO/IEC 27001 and AI flows

Sources and scope of review

Official sources reviewed on 20 October 2026. Scenarios and records are preparation methods that can be used without DUBSAR. They establish neither an available integration nor compliance.