- ClassificationCategorySupply Chain SecurityDomainSupply Chain SecurityFramework FamilyISO Industry Standards
- Regulatory ContextTypeStandardLegal InstrumentStandardSectorCross-SectorIndustryCross-Industry
- Region / PublisherRegionGlobalRegion DetailInternationalPublisherInternational Organization for Standardization (ISO), ISO/TC 292
- VersioningVersionISO 28000:2022 (second edition), with Amendment 1:2024Effective DateMarch 15, 2022 (publication date)Issue DateMarch 15, 2022 (second edition; replaces ISO 28000:2007); Amendment 1 published February 23, 2024
- AdoptionAdoption ModelCertificationImplementation ComplexityHigh
- Official ReferenceOpen Link in New TabSource
License included / downloadable: No
ISO 28000:2022 is a copyrighted ISO standard sold by ISO and by national standards bodies; its text is not included with the platform.
Framework text is licensed by its publisher and is included only where stated above.
- ISO 28000:2022 specifies requirements for a security management system, including aspects relevant to the supply chain.
- ISO/TC 292 published the second edition on March 15, 2022, replacing ISO 28000:2007, which is withdrawn.
- It applies to organizations of any type and size and is not industry or sector specific.
- An organization assesses its security environment, including supply chain dependencies, and aligns its controls with upstream and downstream processes.
- It follows the ISO management system clause structure and the Plan-Do-Check-Act model; conformity may be verified by external or internal audit.
Overview
ISO 28000:2022, Security and resilience — Security management systems — Requirements, is the international standard that specifies requirements for a security management system, including aspects relevant to the supply chain. The International Organization for Standardization (ISO) published the second edition on March 15, 2022 through technical committee ISO/TC 292, Security and resilience. It replaces ISO 28000:2007, which ISO lists as withdrawn, and it applies to organizations of any type and size.
The standard is not industry or sector specific (Clause 1). It requires an organization to assess the security environment in which it operates, including its supply chain and the dependencies and interdependencies in it, to determine whether adequate security measures are in place to manage security-related risks, to manage compliance with statutory, regulatory and voluntary obligations, and to align its security processes and controls, including the upstream and downstream processes and controls of the supply chain, with its objectives (Introduction). An organization may verify conformity by external or internal audit.
Organizations implement it through the clause structure shared with other ISO management system standards and the Plan-Do-Check-Act model: context and interested parties (Clause 4), leadership and the security policy (Clause 5), planning for security-related risks and objectives (Clause 6), support (Clause 7), operation, including risk assessment and treatment, controls, strategies and security plans (Clause 8), performance evaluation (Clause 9) and improvement (Clause 10). Amendment 1:2024 adds climate change to the context clauses.
Why does it matter?
The Introduction describes an increasing uncertainty and volatility in the security environment and notes that supply chains are dynamic, so some organizations that manage multiple supply chains look to their providers to meet related security standards as a condition of being included. ISO 28000:2022 gives both sides a common management system to point to.
Key benefits include:
- One system across the supply chain
The organization assesses its security environment including supply chain dependencies and interdependencies, and aligns upstream and downstream processes and controls with its objectives (Introduction and Clause 4.1).
- Obligations managed in one place
Clause 4.2.2 covers legal, regulatory and other requirements, and the Introduction requires the organization to manage compliance with statutory, regulatory and voluntary obligations.
- Risk assessment tied to treatment
Security-related risks and opportunities are determined and addressed in Clauses 6.1.2 and 6.1.3, and carried into operation through risk assessment and treatment in Clause 8.3.
- Plans for response and recovery
Clause 8.6 requires security plans with a response structure, warning and communication, defined content and recovery; the 2022 edition added these for consistency with ISO 22301.
- Fits other ISO management systems
The Introduction names ISO 9001, ISO 14001, ISO 22301, ISO/IEC 27001 and ISO 45001 as standards with which it supports consistent and integrated implementation.
How does it work?
ISO 28000:2022 applies the Plan-Do-Check-Act model (Introduction, Table 1). Plan establishes the security policy, objectives, targets, controls, processes and procedures; Do implements and operates them; Check monitors and reviews performance against the policy and objectives and reports results to management; Act maintains and improves the system through corrective action and management review.
The requirements run from Clause 4 to Clause 10. The organization determines its context, interested parties, legal, regulatory and other requirements, principles and scope (Clause 4), sets a security policy with top management commitment and assigned roles (Clause 5), and plans actions for security-related risks and opportunities, security objectives and changes (Clause 6). Clause 7 covers resources, competence, awareness, communication and documented information.
Clause 8 is where the system operates. The organization identifies its processes and activities (8.2), assesses and treats security risks (8.3), applies controls (8.4), selects security strategies and treatments with the resources they need (8.5) and maintains security plans (8.6). Clause 9 evaluates performance through monitoring, internal audit and management review, and Clause 10 handles nonconformity, corrective action and continual improvement.
Key Elements
- Context and principles (Clause 4)
Understanding the organization and its context (4.1), interested parties and their legal, regulatory and other requirements (4.2.1 and 4.2.2), principles (4.2.3), the scope (4.3) and the security management system (4.4).
- Leadership and security policy (Clause 5)
Top management commitment (5.1), establishing the security policy and its requirements (5.2.1 and 5.2.2) and roles, responsibilities and authorities (5.3).
- Planning (Clause 6)
Determining and addressing security-related risks and opportunities (6.1.2 and 6.1.3), establishing and determining security objectives (6.2.1 and 6.2.2) and planning of changes (6.3).
- Risk assessment, treatment and controls (Clauses 8.2 to 8.4)
Identification of processes and activities, risk assessment and treatment, and controls.
- Security strategies and plans (Clauses 8.5 and 8.6)
Selection of strategies and treatments (8.5.1), resource requirements (8.5.2), implementation (8.5.3), and security plans covering the response structure (8.6.2), warning and communication (8.6.3), content (8.6.4) and recovery (8.6.5).
- Evaluation and improvement (Clauses 9 and 10)
Monitoring, measurement, analysis and evaluation (9.1), the internal audit program (9.2.2), management review inputs and results (9.3.2 and 9.3.3), continual improvement (10.1) and nonconformity and corrective action (10.2).
What does it cover?
ISO 28000:2022 specifies requirements for a security management system, including aspects relevant to the supply chain (Clause 1). It applies to all types and sizes of organizations, such as commercial enterprises, government or other public agencies and non-profit organizations, can be used throughout the life of the organization and can be applied to any activity, internal or external, at all levels. The terms in ISO 22300 and in Clause 3 apply; ISO 22300 is the only normative reference (Clause 2).
What are its objectives?
The standard defines a security management system as a system of coordinated policies, processes and practices through which an organization manages its security objectives (Clause 3.5). Its aims, taken from the Introduction, are to:
Assess the security environment, including the supply chain and its dependencies and interdependencies.
Determine whether adequate security measures are in place to manage security-related risks.
Manage compliance with statutory, regulatory and voluntary obligations.
Align security processes and controls, including upstream and downstream supply chain controls, with the organization's objectives.
Maintain and improve the system through the Plan-Do-Check-Act model, with conformity verified by audit where the organization wants it.
Framework in Context
ISO 28000:2022 is the second edition. It cancels and replaces ISO 28000:2007, technically revised but maintaining the existing requirements so that organizations using the previous edition have continuity, and the Foreword lists two main changes: principles added to Clause 4 for better coordination with ISO 31000, and recommendations added to Clause 8 for consistency with ISO 22301, covering security strategies, procedures, processes and treatments and security plans. ISO/TC 292 prepared it. Amendment 1:2024, published February 23, 2024, adds ISO's climate change statements to Clauses 4.1 and 4.2.
Common Framework Mappings
Organizations map ISO 28000:2022 to the other ISO 28000-series standards listed below and to the information security and cybersecurity frameworks they run alongside it, so that one set of evidence serves several audits.
Mapped frameworks include:
ISO 28001
ISO 28002
ISO 28003
ISO 28004
ISO 28005
ISO/IEC 27001
ISO/IEC 27017
NIST Cybersecurity Framework
NIST SP 800-53
How SmartSuite Supports ISO 28000
SmartSuite provides the system for managing controls, evidence, mappings, assessments, and reporting.
Use Operational Resilience & Business Continuity, Third Party Risk Management and Cyber & IT Risk to hold the security policy, risk assessments, controls, security plans, supplier dependencies and audit results that Clauses 4 to 10 call for.
Security Policy and Objectives
Record the security policy, security objectives, roles, responsibilities and review dates (Clauses 5.2, 5.3 and 6.2).
Context and Obligations Register
Keep interested parties, the scope and the legal, regulatory and other requirements with owners and source references (Clauses 4.2 and 4.3).
Security Risk Assessment and Treatment
Log security-related risks, opportunities, treatment actions and decisions with owners and due dates (Clauses 6.1.2, 6.1.3 and 8.3).
Controls and Supplier Dependencies
Track the controls applied under Clause 8.4 and the suppliers and partners they depend on.
Security Plans and Recovery
Hold security plans with the response structure, warning and communication steps and recovery actions (Clause 8.6).
Audit, Review and Corrective Action
Plan internal audits, record management review inputs and results and follow nonconformities to closure (Clauses 9.2, 9.3 and 10.2).
Related frameworks

ISO/IEC 27001:2022 specifies requirements for an information security management system: Clauses 4 to 10, risk treatment, the Statement of Applicability and 93 Annex A controls.

ISO/IEC 27002:2022 is the reference set of 93 information security controls in four themes, with attributes and implementation guidance, that supports an ISO/IEC 27001 ISMS.

NIST CSF 2.0 (CSWP 29, February 26, 2024) is the voluntary cybersecurity framework with six Functions including Govern, 22 Categories, 106 Subcategories, Profiles and Tiers.
Frequently Asked Questions For ISO 28000 (Supply Chain Security Management System)
ISO 28000:2022 is the second edition of the security management system standard, published by ISO on March 15, 2022 through ISO/TC 292. It cancels and replaces ISO 28000:2007 and, per its Foreword, adds principles in Clause 4 for better coordination with ISO 31000 and recommendations in Clause 8 for consistency with ISO 22301. Amendment 1:2024 adds climate change considerations to the context clauses.
No. Clause 1 says the standard specifies requirements for a security management system, including aspects relevant to the supply chain, and that it is not industry or sector specific. It applies to all types and sizes of organizations and to any activity, internal or external, at all levels.
The Introduction says conformity of the security management system to the standard may be verified by an external or internal auditing process, so certification by an accredited body is an option, not a requirement. ISO lists the 2007 edition as withdrawn. Ask your certification body which transition arrangement applies to an existing 2007 certificate.
The organization identifies its processes and activities (8.2), assesses and treats security risks (8.3), applies controls (8.4), selects security strategies and treatments and the resources they need (8.5) and maintains security plans (8.6). The plans cover the response structure, warning and communication, their content and recovery.
The Foreword ties Clause 4 to ISO 31000 and Clause 8 to ISO 22301, and the Introduction names ISO 9001, ISO 14001, ISO 22301, ISO/IEC 27001 and ISO 45001 as standards it is consistent with. The shared structure lets an organization combine policies, audits and management reviews across these systems.

Put this framework to work in SmartSuite
Manage controls, risks, evidence, and audits in one platform designed for modern governance, risk, and compliance.


