Building an Integrated Management System with ISO 27001, ISO 9001 and ISO 22301

Integrated management system: common high-level structure and clause mapping, elements that can be combined and those that stay standard-specific, a shared document set, combined internal audit and management review.
Technical summary
Technology
ISO/IEC 27001:2022, ISO 9001:2015, ISO 22301:2019, Annex SL (Harmonized Structure), ISO 19011
Topic
Combining several ISO management systems into a single structure
Level
Intermediate–advanced
Prerequisites
  • At least one management system set up and in operation
  • Familiarity with the clause structure of the relevant standards
In this article7 sections

Three different corrective action forms, three different document coding systems and the same board meeting three times a year in the same company: when ISO 27001 is added on top of ISO 9001, then ISO 22301, and each is run separately, the picture soon turns into this. It isn’t sustainable. Because these standards share the same high-level structure, a single integrated management system (IMS) is possible. For quality, information security and continuity managers, this guide makes concrete which elements can be combined, which must stay standard-specific and which risks integration creates in audits.

Common high-level structure and clause mapping

ISO management system standards use the common structure defined in Annex SL of the Consolidated ISO Supplement to the ISO/IEC Directives Part 1. This structure used to be called the High Level Structure (HLS); it was updated in 2021 and renamed the Harmonized Structure (HS). ISO/IEC 27001:2022 is aligned with this current structure, while ISO 9001:2015 and ISO 22301:2019 follow the structure of the period in which they were published. In practice, the main clauses 4–10 of all three standards have the same headings; the differences are in the subclauses and in the content of clause 8. In addition, the amendments published in 2024 for all three standards (Amd 1:2024) added the consideration of climate change to the context (4.1) and interested parties (4.2) clauses.

Clause Shared content Standard-specific addition
4.1–4.2 Context, interested parties Interested party requirements differ by standard
4.3 Scope In 9001, justification for non-applicable requirements; scopes may differ
5 Leadership, policy, roles 9001: customer focus (5.1.2)
6.1 Risks and opportunities 27001: 6.1.2 risk assessment, 6.1.3 risk treatment and SoA
6.2–6.3 Objectives, planning of changes Objectives are measured separately for each discipline
7 Resources, competence, awareness, communication, documentation 9001: monitoring and measuring resources (7.1.5), organizational knowledge (7.1.6)
8 Operational planning and control (8.1) 27001: 8.2–8.3; 9001: 8.2–8.7; 22301: 8.2–8.6
9 Monitoring, internal audit, management review 9001: customer satisfaction (9.1.2)
10 Nonconformity, corrective action, improvement Subclause numbers differ by standard

The main point when reading the table is this: clauses 4, 5, 7, 9 and 10 are largely shared. The real work is in 6.1 and clause 8.

Elements that can be combined

Most of the clauses in the common structure can meet more than one standard with a single process and a single record:

  • Context and interested parties: A single context analysis; a column in the interested parties table showing which management system addresses each requirement.
  • Leadership and roles: A single management representative structure or management systems committee; quality, information security and continuity roles together in the RACI matrix.
  • Document control (7.5): A single document control procedure, a single coding and approval flow, a single document management system. We explained version and approval management in the document control guide.
  • Competence, training and awareness: A shared training matrix; awareness training can be combined in modules.
  • Communication: A single table for the internal and external communication plan.
  • Nonconformity and corrective action: A single corrective action record and root cause method; each record shows the affected management system area. A backup failure is both an information security and a continuity corrective action; opening two separate records leads to two different people interpreting the root cause in two different ways.
  • Internal audit and management review: A shared program and a shared meeting (detailed below).

What must stay standard-specific

A mistake you may come across in integration is dissolving specific requirements into general statements. The following must stay separate and recognizable:

  • ISO 27001: The information security risk assessment method and acceptance criteria (6.1.2), the risk treatment plan and Statement of Applicability (6.1.3), repeating the risk assessment at planned intervals (8.2) and evidence of implementing Annex A controls.
  • ISO 9001: Requirements for products and services, design and development, externally provided processes, production and service provision, release of products and services, control of nonconforming outputs (8.2–8.7), customer satisfaction.
  • ISO 22301: Business impact analysis and risk assessment (8.2), business continuity strategies and solutions (8.3), plans and procedures (8.4), the exercise program (8.5) and evaluation of business continuity documentation and capabilities (8.6).

The concept of risk needs particular attention. “Risks and opportunities” in ISO 9001 is a general planning tool. In ISO 27001, however, an information security risk assessment that produces repeatable results with defined criteria is mandatory; ISO 22301 also separately requires a business impact analysis and an assessment of disruption risks. A single “corporate risk table” can be set up; but it must also be traceable that information security risks are assessed against the criteria in 6.1.2 and that BIA outputs are linked to continuity strategies. A concrete example: the RTO target for the ERP server comes from the BIA; the replication and backup architecture that meets that target is written into the 22301 strategy, and the risk of unauthorized access to the same server into the 27001 risk assessment. Same asset, two different questions. We covered the requirements of ISO 22301 in the article ISO 22301 requirements.

The integrated document set

A typical integrated document architecture has three layers:

  1. Shared top-level documents: An integrated management system manual or process map (not mandatory, but useful to show process interactions), an integrated policy or policy set, the context and interested parties analysis, roles and responsibilities.
  2. Shared support procedures: Document and record control, internal audit, management review, corrective action, training and competence, change management, supplier evaluation.
  3. Standard-specific documents: The risk assessment methodology and SoA (27001), topic-specific information security policies, the BIA and business continuity plans (22301), product realization and control plans (9001).

If an integrated policy is to be written, check that the commitments each standard requires in its policy clause are explicitly in the text. For ISO 27001, these are the commitments to satisfy applicable requirements and to continually improve the ISMS, and a framework for setting information security objectives. A general “quality and security policy” sentence may not meet the requirements of the three standards separately. The auditor looks for each commitment one by one.

Combined internal audit and management review

When the internal audit program is set up process by process, it becomes the area where integration pays off most. A process (e.g. purchasing) can be audited in a single audit from the perspective of 9001’s control of externally provided processes, 27001’s supplier security controls and 22301’s continuity assessment of critical suppliers. ISO 19011 is common to all management systems as audit guidance. For details of program design, see the article ISO 27001 internal audit program.

There are two conditions for a combined audit: the audit team must have sufficient competence for each standard, and the audit report must show separately against which clause of which standard each finding was written. Program records must be able to show whether the scope of each standard was fully covered within the audit cycle set by the organization (common practice is three years, aligned with the certification cycle).

Management review can also be held in a single meeting. The agenda starts with shared inputs (status of previous decisions, changes in internal and external issues, interested party needs, audit results, nonconformities, status of objectives), then moves to standard-specific inputs: customer satisfaction and product conformity for 9001, risk assessment results and the status of the risk treatment plan for 27001, BIA and exercise results for 22301. Decisions in the minutes should be labeled by standard. We covered management review content in detail in the management review guide.

On the certification side, if you’ll get a combined audit from the same body for all three standards and want accredited certificates, verify that the certification body has accreditation scope for all three standards. How audit time is adjusted in integrated audits is set out in IAF MD 11; the extent of any time reduction depends on the degree of integration and is assessed by the certification body. A system that is integrated on paper but run separately in practice doesn’t earn this reduction.

Limitations and risks of integration

Risk Symptom Mitigation
Specific requirements getting lost SoA or BIA dissolved into a general risk table Keep standard-specific documents separate
Scope confusion One scope sentence, different actual scopes A separate scope statement for each standard
Auditor competence A quality auditor audits security controls superficially A competent auditor for each discipline in the team
Dependence on one person All systems in one manager’s hands Process owners per discipline
Calendar clashes A problem in one system postpones the whole audit Program flexibility, separate close-out tracking

Integration isn’t the right choice for every organization. If the owners of the standards sit in different units and the scopes largely diverge, it may be more manageable to share only the support processes (document control, corrective action, training) and keep the risk and operations layer separate. Before deciding, go through these checks in order:

  • How much do the scopes overlap?
  • Are the process owners shared?
  • Is the certification body accredited for all the standards?
  • Is the document management infrastructure suitable for shared use?

If TISAX also enters the picture in the automotive supply chain, we compared shared controls with ISO 27001 in the article TISAX and ISO 27001 differences; for this kind of multi-framework structure, see our integrated TISAX, ISO 27001 and IATF 16949 compliance program page, and to add an ISMS to an existing quality system, our ISMS setup service. General information on the common structure of management system standards is on the ISO management system standards page.

Frequently asked questions

Is there a separate standard for an integrated management system?

There’s no separate certifiable ISO standard for an integrated management system. Integration is an approach the organization designs itself, using the common high-level structure of the standards; certification is done separately for each standard.

Is a single policy enough for ISO 9001 and ISO 27001?

It can be; but the text must contain, one by one, the commitments each standard’s policy clause requires. Since ISO 27001 also expects topic-specific information security policies, an integrated top-level policy doesn’t replace them.

Can standards with different scopes be integrated?

Yes. Support processes and management mechanisms are set up jointly, and each standard’s scope statement is written separately. The audit program and records must clearly show which activity falls within the scope of which standard.

Can a single auditor carry out an integrated internal audit?

It’s possible if the auditor is competent in all the relevant standards and independent of the area being audited. If the competence isn’t concentrated in one person, the audit team should be formed from auditors from different disciplines.

Support

Contact us for support or a discovery session on this topic.

Contact form
[email protected]

Eretek Compliance

We work with you on compliance with ISO 27001, IATF 16949, TISAX and similar standards, covering risk assessment, control design, documentation and audit preparation.

Knowledge Center

Other articles