Engineer working on a laptop connected to a device test rig, surrounded by wiring harnesses and test hardware

Firmware vulnerabilities & fixes

ISO/IEC 27001:2022 (information security management systems), explained

Last updated:

ISO/IEC 27001:2022, "Information security, cybersecurity and privacy protection — Information security management systems — Requirements," is the current, certifiable International Standard for an information security management system (ISMS), published 25 October 2022 by ISO/IEC JTC 1/SC 27. It is the third edition, superseding ISO/IEC 27001:2013 (withdrawn the same day), and its Annex A points to 93 controls across 4 themes — organizational, people, physical and technological — detailed in the companion standard ISO/IEC 27002:2022. Unlike most of the firmware- and device-specific standards covered elsewhere on this site, ISO/IEC 27001 is a general-purpose, organization-level management system standard: it specifies how an organization runs an information security program, not which technical controls a given product must implement.

Key takeaways

  • Because it follows the Harmonized Structure, formerly known as "Annex SL", that ISO uses for every management system standard.
  • Clause 6.1.3 d) lists four elements, and certification bodies check each one.
  • Annex A lists control titles only; the guidance lives in ISO/IEC 27002:2022, published in February 2022, about eight months before 27001.
  • The ones that cover how code is built, what third-party code goes in, and how vulnerabilities are handled after release.

Why does the clause numbering look familiar?

Because it follows the Harmonized Structure, formerly known as "Annex SL", that ISO uses for every management system standard. Per the ISO/TMBG Joint Technical Coordination Group communiqué, that annex "defines the terminology, high-level structure ('HLS') and core text to enhance the consistency of ISO's and IEC's portfolio of management system standards," and it forms "the basis for harmonization of over 40 individual management system standards." ISO 9001 and ISO 14001 share the same clause 4-10 skeleton, so a company already certified to one can fold ISO/IEC 27001 into an integrated management system.

The standard's scope is blunt: "Excluding any of the requirements specified in Clauses 4 to 10 is not acceptable when an organization claims conformity." Annex A controls can be scoped out with a justification; the clauses cannot.

Clause Title What an auditor typically asks to see
4 Context of the organization Internal/external issues (4.1), interested parties and their requirements (4.2), the documented ISMS scope (4.3)
5 Leadership Information security policy (5.2), assigned roles and authorities (5.3)
6 Planning Risk assessment process (6.1.2), risk treatment process and Statement of Applicability (6.1.3), objectives (6.2), planning of changes (6.3)
7 Support Resources, competence, awareness, communication, control of documented information (7.5)
8 Operation Operational planning and control (8.1), information security risk assessment (8.2) and risk treatment (8.3) carried out in operation
9 Performance evaluation Monitoring and measurement (9.1), internal audit programme (9.2), management review (9.3)
10 Improvement Continual improvement (10.1), nonconformity and corrective action (10.2)

Clause titles are from the standard's own contents page; the right-hand column summarises the "shall" statements in each clause.

What must a Statement of Applicability contain?

Clause 6.1.3 d) lists four elements, and certification bodies check each one. Per the ISO/IEC 27001:2022 preview text, the Statement of Applicability (SoA) contains:

  1. The necessary controls, as determined by the risk treatment process in 6.1.3 b) and c).
  2. The justification for their inclusion
  3. Whether each necessary control is implemented or not
  4. The justification for excluding any of the Annex A controls

Around that, 6.1.3 requires you to compare your chosen controls against Annex A "and verify that no necessary controls have been omitted," to formulate a risk treatment plan, and to obtain the risk owners' approval of that plan and their acceptance of residual risk. Note 1 adds that organizations "can design controls as required, or identify them from any source," and Note 3 says the Annex A list is "not exhaustive." That matters for product companies: a firmware signing control or a secure boot requirement can sit in the SoA even if no Annex A title names it.

How are the 93 Annex A controls organised, and how do they relate to ISO/IEC 27002?

Annex A lists control titles only; the guidance lives in ISO/IEC 27002:2022, published in February 2022, about eight months before 27001. ISO/IEC 27002's scope says it "provides a reference set of generic information security controls including implementation guidance" for use "within the context of an information security management system (ISMS) based on ISO/IEC 27001."

Per the UKAS transition bulletin, Annex A "has been aligned with the controls defined in ISO/IEC 27002:2022, which contains 93 controls (11 of which are new) organised in 4 themes. In addition to the 11 new controls, 24 have been merged and 58 have been updated." The same bulletin notes that clause 6.1.3 c) and d) notes were also revised.

Theme Clause range Controls
Organizational 5.1-5.37 37
People 6.1-6.8 8
Physical 7.1-7.14 14
Technological 8.1-8.34 34

The 2013 Annex A is widely described as 114 controls in 14 clauses. ISO/IEC 27002:2022 carries its own correspondence table to the 2013 controls in Annex B, which is the place to check any one-to-one mapping.

Which Annex A controls matter most to a firmware team?

The ones that cover how code is built, what third-party code goes in, and how vulnerabilities are handled after release. ISO/IEC 27001 does not specify product security requirements, but these control titles, taken from the ISO/IEC 27002:2022 contents, are where an auditor will look for engineering evidence:

Control (27002:2022) What it means for a device or firmware team Evidence that usually satisfies an auditor
5.7 Threat intelligence Track advisories for the chips, RTOS and open-source packages you ship Subscribed feeds, triage log
5.21 Managing information security in the ICT supply chain Know which third-party and open-source components are in each image Per-release SBOM, supplier security clauses
5.24-5.27 Incident management planning, assessment, response, learning A defined route from vulnerability report to fix PSIRT procedure, closed tickets, post-incident review
8.8 Management of technical vulnerabilities Match shipped components to published CVEs and decide what to fix Vulnerability match reports, risk decisions, fix dates
8.9 Configuration management Controlled build configurations and secure defaults Versioned build configs, default-settings review
8.25 Secure development life cycle Security activities defined across the development process SDL procedure, release gates
8.28 Secure coding Coding rules and their enforcement Coding standard, static analysis results
8.29 Security testing in development and acceptance Security tests before release Test plans, fuzzing or penetration test reports
8.30 Outsourced development Contract firmware and ODM work held to the same rules Contract clauses, supplier test evidence
8.32 Change management Controlled changes to code and build pipelines Change records linked to releases

For the product-level process these controls point at, see our guides to setting up a PSIRT at a hardware company and IEC 62443-4-1 secure development, and the OWASP firmware testing methodology for 8.29 test depth.

What did Amendment 1:2024 change?

Two sentences, both in clause 4. Per the IAF/ISO joint communiqué of 22 February 2024, clause 4.1 gains "The organization shall determine whether climate change is a relevant issue," and clause 4.2 gains the note "Relevant interested parties can have requirements related to climate change." The same text went into a batch of ISO management system standards; ISO's 27001 catalogue page lists ISO/IEC 27001:2022/Amd 1:2024 at CHF 0.

The communiqué states that "the overall intent of the requirements for clauses 4.1 and 4.2 remain unchanged." UKAS treats it as "a clarification rather than a new requirement," so no full transition programme applies; certification bodies simply audit whether the climate question was considered. For most device makers the answer will be a short, documented "not relevant" or a link to an existing business-continuity risk.

How does certification and the 2022 transition work?

ISO does not certify anyone. Per UKAS, "certification is the third-party confirmation via audit of an organisation's systems or products, whilst accreditation is independent third-party recognition that an organisation has the competence and impartiality to perform specific technical activities such as certification"; accreditation bodies "check the checkers." An accredited certification body runs a two-stage initial audit; the certificate typically runs three years, with surveillance audits in years one and two and recertification in year three.

The UKAS bulletin set the transition dates:

Date Milestone
25 October 2022 ISO/IEC 27001:2022 published
31 October 2023 All initial certifications against the 2022 edition
31 October 2025 All certified clients transitioned to the 2022 edition

So any certificate a supplier shows you in late 2026 should name ISO/IEC 27001:2022. One landscape change: per the IAF website, as of 1 January 2026 the International Accreditation Forum "is no longer operational," and its work and ILAC's moved to the Global Accreditation Cooperation Incorporated (Global ACI).

Worked example: how would a small router maker scope its ISMS?

Synthetic example, for illustration only. A 60-person company designs consumer routers, writes the firmware in-house on an embedded Linux base, and uses an ODM for manufacturing. Its largest customer, a telecom operator, asks for ISO/IEC 27001 certification.

  1. Scope (4.3)"Design, development, build, release and vulnerability handling of router firmware and the company's cloud management service." Manufacturing at the ODM is outside the scope, listed as an interface under 4.3 c).
  2. Risk assessment (6.1.2)Top risks: a signing key leak, an unpatched open-source component in a shipped image, and a compromised build server.
  3. Treatment (6.1.3)Controls chosen from Annex A and from outside it.
Control Applicable? Justification Implemented?
8.8 Management of technical vulnerabilities Yes Shipped images carry open-source packages with published CVEs Yes: SBOM per release, weekly CVE match
8.30 Outsourced development Yes ODM writes the bootloader port Partly: contract clause signed, test evidence pending
7.4 Physical security monitoring Yes, offices only Lab holds signing hardware Yes
Firmware image signing (own control, Note 1) Yes Key leak is the top risk Yes: HSM-held key, two-person release
5.23 Information security for use of cloud services Yes Management service runs on a public cloud Yes

The SoA records "partly" for 8.30, and the risk owner accepts that residual risk until the ODM test evidence arrives. An auditor will want that acceptance in writing under 6.1.3 f).

Where does ISO/IEC 27001 plug into the CRA and NIS2?

Partially, and not as a substitute. The Cyber Resilience Act grants presumption of conformity through harmonised standards cited in the EU Official Journal (Article 27), and its text does not name ISO/IEC 27001. ENISA's CRA standards mapping includes ISO/IEC 27001:2022 but says "we did not find a single standard that can, alone, satisfy all requirements listed in the two lists present in Annex I of the CRA," and notes that 27001 "does not cover specific technical measures for defence in depth, encryption at rest, or sandboxing." The ISMS covers the organization; the CRA asks about each product. A firmware SBOM, the firmware SBOM process behind it, and a working vulnerability-handling route serve both.

NIS2 is closer. Article 21 requires measures that take into account "relevant European and international standards," Article 25 tells Member States to "encourage the use of European and international standards," and recital 79 names "those included in the ISO/IEC 27000 series." ENISA's NIS2 technical implementation guidance maps its measures to ISO/IEC 27001:2022 and 27002:2022 but warns that the mapping "should not be interpreted as a measure of equivalency." In GB's energy sector, Ofgem's NIS guidance lists ISO 27001 among "output-based frameworks" an operator may map to NCSC CAF outcomes. Treat any claim that a 27001 certificate alone satisfies CRA or NIS2 as unconfirmed until the regulator or notified body agrees.

What are the common pitfalls?

  • Scoping out engineering. A certificate that covers only IT and HR tells a customer nothing about firmware. Check the scope statement on any certificate you rely on.
  • Treating Annex A as a checklist. The SoA must justify inclusions and exclusions from the risk assessment; ticking all 93 without that link is a finding.
  • Buying 27001 without 27002. The control titles alone are too thin to design an implementation.
  • No product-level evidence under 8.8. "We patch servers" does not cover vulnerabilities in shipped images.
  • Forgetting the climate sentence. Since February 2024, auditors check that 4.1 considered climate change, even if the answer is "not relevant."
  • Citing a 2013 certificate. After 31 October 2025, a certificate should name the 2022 edition.

Where does firmware evidence fit into an ISMS?

SoftWSP extracts an SBOM from a firmware image (CycloneDX 1.6 JSON), matches the components against NVD, CISA KEV, FIRST EPSS and CISA CSAF ICS advisories, and drafts a cited report that an engineer reviews. That gives a firmware team dated evidence for controls 5.21 and 8.8; the ISMS, the risk decisions and the certificate stay with you and your certification body. See Device & Firmware Security.

This guide summarizes publicly available ISO, IEC, UKAS, IAF and ENISA material; ISO/IEC 27001 and 27002's full text is copyrighted and must be purchased from ISO, IEC or a national member body. It is not a substitute for the standards or for compliance or legal advice.

Put this guide to work

Frequently asked questions

What is ISO/IEC 27001:2022, and who publishes it?

ISO/IEC 27001:2022, "Information security, cybersecurity and privacy protection — Information security management systems — Requirements," is the third edition of ISO/IEC's certifiable standard for an information security management system (ISMS), published 25 October 2022 by ISO/IEC JTC 1/SC 27 and carrying ICS codes 35.030 and 03.100.70. It superseded the second edition, ISO/IEC 27001:2013, which ISO's own catalogue marks as withdrawn on the same date — 2022-10-25 — alongside that edition's two corrigenda. ISO's committee page lists the current edition at 19 pages and CHF 155 through the ISO and IEC webstores; ISO/IEC 27001 is copyrighted and must be purchased from ISO, a national member body (e.g. BSI in the UK, ANSI in the US) or an authorized reseller — no free full-text mirror is authorized, so this guide summarizes publicly available catalogue and committee information rather than quoting the standard's operative text at length. ISO/IEC 27001:2022 also has one published amendment, Amendment 1:2024 ("climate action changes"), per ISO's own catalogue — a change applied across ISO's management-system-standard portfolio from 2024, not specific to information security.

What is the clause 4-10 structure, and why do other ISO management standards look the same?

ISO/IEC 27001 follows the Harmonized Structure (formerly called "Annex SL") that ISO's own Technical Management Board Joint Technical Coordination Group mandates for all ISO/IEC management system standards, to keep their core clause numbering and terminology consistent. Per the governing ISO/TMBG communiqué, this structure "defines the terminology, high-level structure (HLS) and core text to enhance the consistency of ISO's and IEC's portfolio of management system standards" and "does form the basis for harmonization of over 40 individual management system standards." In ISO/IEC 27001:2022 this yields seven requirements clauses: 4 Context of the organization, 5 Leadership, 6 Planning, 7 Support, 8 Operation, 9 Performance evaluation, and 10 Improvement — the same clause skeleton used by ISO 9001 (quality) and ISO 14001 (environmental management), which is why an organization already certified to one can typically integrate a second ISO management system without rebuilding its documentation structure from scratch.

What is Annex A, and how many controls does it list?

Annex A lists the controls an ISMS can select from (via the standard's Statement of Applicability process) to treat identified risks; it does not describe each control in implementation detail — that full guidance lives in the companion standard ISO/IEC 27002:2022. Per UKAS (the UK's national accreditation body), ISO/IEC 27001:2022's "Annex A has been aligned with the controls defined in ISO/IEC 27002:2022, which contains 93 controls (11 of which are new) organised in 4 themes," and notes that "in addition to the 11 new controls, 24 have been merged and 58 have been updated" relative to the prior control set. ISO/IEC 27002:2022's own clause numbering lays out those 93 controls across four ranges: 5.1-5.37 (Organizational controls, 37), 6.1-6.8 (People controls, 8), 7.1-7.14 (Physical controls, 14) and 8.1-8.34 (Technological controls, 34). The prior, 2013-based control set is widely reported as having organized 114 controls into 14 clauses — that specific comparison is best understood as a commonly cited secondary figure rather than a directly quoted ISO statement.

How does ISO/IEC 27001:2022 relate to ISO/IEC 27002:2022, and how does certification work?

ISO/IEC 27002:2022 ("Information security, cybersecurity and privacy protection — Information security controls") was published first, in February 2022, roughly eight months ahead of ISO/IEC 27001:2022 in October 2022. ISO's own scope statement for 27002 says it "provides a reference set of generic information security controls including implementation guidance" designed for use "within the context of an information security management system (ISMS) based on ISO/IEC 27001" — in practice, 27001's Annex A gives only the control titles grouped by theme, while 27002 carries the full Control/Purpose/Guidance text an organization implements against. Certification itself is performed by accredited, independent certification bodies rather than by ISO: per the UK Accreditation Service (UKAS), "certification is the third-party confirmation via audit of an organisation's systems or products, whilst accreditation is independent third-party recognition that an organisation has the competence and impartiality to perform specific technical activities such as certification" — summarized as accreditation bodies "check the checkers." The typical cycle, reflected in accreditation-body guidance, is a two-stage initial audit, a certificate valid for three years, surveillance audits in years one and two, and a recertification audit in year three. Note for anyone tracking the accreditation landscape as of this guide's 2026 publication: the International Accreditation Forum (IAF) ceased independent operation on 1 January 2026, merging with ILAC into the Global Accreditation Cooperation Incorporated (Global ACI) — current certification-cycle guidance should be checked against Global ACI rather than the now-archival IAF.

Does the EU Cyber Resilience Act or NIS2 recognize ISO/IEC 27001 certification directly?

Not as a named, binding mechanism in either law's own operative text. The Cyber Resilience Act's conformity-presumption mechanism (Article 27) runs through harmonised standards published in the EU Official Journal, which had not been adopted for the CRA as of November 2026, and the CRA's own text does not name ISO/IEC 27001. ENISA has published an unofficial analytical mapping of CRA requirements against existing standards that includes ISO/IEC 27001:2022, but explicitly cautions that it "did not find a single standard that can, alone, satisfy all requirements listed" in the CRA's Annex I, flagging for ISO/IEC 27001 specifically that it "does not cover specific technical measures for defence in depth, encryption at rest, or sandboxing." NIS2's operative articles (e.g. Articles 21 and 25) use only generic language encouraging "the use of European and international standards," without naming ISO/IEC 27001; a non-binding recital (Recital 79) does cite "European and international standards, such as those included in the ISO/IEC 27000 series" as illustrative. ENISA has separately published technical implementation guidance mapping NIS2's risk-management measures to ISO/IEC 27001:2022 and 27002:2022, while stating the mapping "should not be interpreted as a measure of equivalency." In the UK, energy-sector guidance from Ofgem (the NIS Regulations competent authority for that sector) names ISO 27001 as an example "output-based framework" operators may map against the NCSC Cyber Assessment Framework — useful context for an OT/energy audience, though it is sector guidance, not a certification mandate. Treat any claim that ISO/IEC 27001 certification alone satisfies CRA or NIS2 obligations as unconfirmed, and verify against the specific regulator or notified body involved.

Sources

  1. ISO/IEC: Information security, cybersecurity and privacy protection — Information security management systems — Requirements, ISO/IEC 27001:2022 (committee catalogue record: edition, publication date, pages, ICS codes, price)
  2. ISO: ISO/IEC 27001:2013 (withdrawn) — catalogue record showing withdrawal on 2022-10-25 and supersession by ISO/IEC 27001:2022
  3. UKAS: Transition arrangements for ISO/IEC 27001:2022 (Technical Bulletin) — 93 controls / 4 themes / 11 new, 24 merged, 58 updated
  4. UKAS: Accreditation vs certification — "accreditation bodies check the checkers"
  5. ISO/TMBG JTCG Task Force 14 Communiqué, Issue 2019-01 — governing text on the Harmonized Structure / "Annex SL" used across ISO/IEC management system standards
  6. ISO: ISO/IEC 27002:2022 — Information security, cybersecurity and privacy protection — Information security controls (catalogue record: edition, publication date, scope statement)
  7. ENISA: Cyber Resilience Act Requirements — Standards Mapping (official ENISA analytical mapping, incl. ISO/IEC 27001:2022 gap note)
  8. ENISA: Technical implementation guidance on cybersecurity risk management measures (NIS2), v1.0 — mapping to ISO/IEC 27001:2022/27002:2022 with non-equivalency caveat
  9. Ofgem: NIS Guidance for Downstream Gas and Electricity Operators of Essential Services in GB v2.0 — cites ISO 27001 as an example output-based framework mapped to the NCSC CAF
  10. ISO/IEC 27001:2022 preview (iTeh): foreword, scope, clauses 4.1-6.3 including 6.1.3 d) Statement of Applicability content
  11. ISO/IEC 27002:2022 preview (iTeh): contents with control titles and Annex B correspondence to the 2013 edition
  12. IAF/ISO Joint Communiqué on the addition of Climate Change considerations to Management Systems Standards (22 February 2024)
  13. UKAS: Inclusion of Climate Change considerations within Management System Standards (Technical Bulletin, 27 February 2024)
  14. IAF: Global Accreditation Cooperation Incorporated launch (1 January 2026)
  15. Directive (EU) 2022/2555 (NIS2): Articles 21 and 25, recital 79
Was this guide helpful?

In this cluster