ISO 27001:2022 · Organizational controls
ISO 27001:2022 5.21: Managing information security in the information and communication technology (ICT) supply chain
ISO 27001:2022 5.21 covers Managing information security in the information and communication technology (ICT) supply chain. The held text names 5 evidence records for it, the first being Statement of Applicability entry for control A.5.21, showing inclusion or justified exclusion, implementation status and the risks it.... The common gap an assessor flags is Software is accepted without any bill of materials or component information.
Processes and procedures are to be defined and put in place to manage information security risks in the supply chain for ICT products and services. Purpose (stated in ISO/IEC 27002:2022): keeps security across the ICT product and service supply chain at the agreed level. As an Annex A reference control, it is compared with the controls determined in risk treatment (6.1.3 c) and recorded in the Statement of Applicability as included or excluded, with the justification and implementation status (6.1.3 d); implementation guidance is ISO/IEC 27002:2022 5.21.
What evidence supports 5.21?
- Annex A organizational controlStatement of Applicability entry for control A.5.21, showing inclusion or justified exclusion, implementation status and the risks it treats
- Annex A organizational controlSecurity requirements included in ICT acquisition specifications and contracts, including flow-down to sub-suppliers
- Annex A organizational controlSoftware component information such as SBOMs and descriptions of security functions and secure configuration obtained from product suppliers
- Annex A organizational controlA list of critical ICT components with provenance and traceability evidence
- Annex A organizational controlIntegrity verification records for delivered products such as hash or signature checks and anti-tamper inspections
Where this requirement comes from
This is our own statement of ISO 27001:2022 5.21, read from the copy we hold (licensed complete copy) and stated in our words, not the standard verbatim. The framework as we hold it.
Common gaps an assessor flags
- Software is accepted without any bill of materials or component information
- Downloaded software and firmware updates are installed without signature or hash verification
- Critical components have no identified alternative source
- Sub-suppliers are invisible because contracts do not require disclosure or flow-down
How it maps to SOC 2
- CC9.2 high Managing security in the ICT supply chain extends assessment to subcontractors.
A link is a topical overlap with a confidence and a reason. It does not establish that meeting one requirement satisfies the other, and it is not certification.