ISO 27001 Control A.5.21: Managing Information Security in the ICT Supply Chain
When you buy a cloud service, you are not buying from one company. You are buying from a chain: the provider, its hosting platform, its software libraries, its support subcontractors and its own suppliers. A weakness anywhere along that chain can reach your data, and you may never have a contract with the party that caused it. A.5.21 asks you to think about that chain deliberately. It is the 21st of 37 organizational controls in our walk through Annex A.
Recent years have shown how real the risk is, from compromised software updates to vulnerabilities in widely used open-source components. You cannot audit every link. The control is about understanding where you depend on others, asking for what you reasonably can and designing so that one failure does not take you down.
What the control requires
Annex A control 5.21 of ISO 27001:2022 states that processes and procedures shall be defined and implemented to manage the information security risks associated with the ICT products and services supply chain.
The key elements:
- Processes and procedures - defined, repeatable steps, applied when you select, buy and use ICT products and services
- ICT products and services - hardware, software, cloud services, managed services and components embedded in them
- Supply chain - not only your direct supplier, but the parties your supplier relies on
- Information security risks - risks such as tampered components, hidden subcontractors, discontinued products and inherited vulnerabilities
A.5.21 is a preventive control in ISO/IEC 27002:2022. Annex A states the control; ISO 27002 gives guidance, including that you should pass your information security requirements down the chain through your suppliers, ask suppliers to propagate them to their own suppliers, seek information about the origin and components of what you buy, and check that critical components can be traced and are genuine. It also suggests you take steps such as software bills of materials where appropriate, and considering the lifespan and support of products.
How to implement ICT supply chain security
Map the dependencies that matter
You do not need a diagram of the whole internet. Start with the ICT services your business cannot run without, and ask for each: whom does this depend on, and what happens to us if that dependency fails or is compromised? For a typical software company this includes the cloud platform, the identity provider, source code hosting, build and deployment tools, key libraries and a payment or email provider. Note which of those are single points of failure.
Keep the map next to your supplier register from information security in supplier relationships. Mark which suppliers are themselves critical dependencies of others, which is often how you discover hidden concentration, such as five of your tools all running on the same cloud region.
Pass requirements down the chain
Your own requirements should flow to suppliers and, through them, to their suppliers. In practice, that means including in your agreements, as discussed in addressing information security within supplier agreements, clauses on:
- Disclosure of subcontractors who handle your information, and notice of changes
- Equivalent security obligations for those subcontractors
- Notification when an upstream incident affects your service
- Provenance and integrity of software and hardware delivered to you
You often cannot negotiate with a large vendor, so look at what they publish: subprocessor lists, security whitepapers, certifications and vulnerability disclosure policies. Record what you relied on. Where something important is missing, decide whether to accept the risk, add your own mitigation or choose another product.
Build security into selection and procurement
Decide what you ask before buying ICT products. Sensible questions include how the vendor handles security updates and for how long, whether the product is end-of-life soon, how vulnerabilities are reported, where components come from and whether independent assurance exists. For hardware, buy from authorized channels and check packaging and serial numbers on delivery for equipment that goes into sensitive environments. For software, download from official sources and verify checksums or signatures where they are offered.
If you develop software, add your own dependencies to the picture: keep a list of third-party libraries and their versions, scan them for known vulnerabilities, pin versions and restrict who can add new packages. The technological controls on vulnerability management and secure development, covered later in the series, build on this.
Plan for failure and change
Resilience is part of supply chain security. For critical services, know your alternatives and how long a switch would take. Keep your own backups of data held by suppliers, and test restoring them. Include in your continuity thinking the possibility that a supplier or its provider is unavailable, which links to the later Annex A controls on security during disruption and ICT readiness for business continuity. Track end-of-support dates for products so that unsupported software does not linger by accident.
Review the chain when something changes: the supplier is acquired, moves its hosting, adds a subprocessor or has a public incident. Those events are the time to reassess, and ongoing oversight of supplier services is the subject of the next control in the series.
A small, honest example shows how modest the first step can be. Choose one critical service, write down its five most important dependencies on a single page, and for each note what you know, what you assumed and what you could ask. Even that short exercise tends to surface a surprise: an unsupported library, a support team in a country you did not expect, or a backup that lives with the same provider as the primary. Repeat it for the next service, and within a quarter you will have a useful map without any special tooling.
Related controls and clauses
A.5.19 connection. Information security in supplier relationships gives you the register and the risk tiers that the supply chain analysis builds on.
A.5.20 connection. Addressing information security within supplier agreements is where requirements for subcontractors and flow-down are written.
A.5.9 connection. The inventory of information and other associated assets should include software components and services you depend on.
A.7.9 and A.7.14 connection. Security of assets off-premises and secure disposal or re-use of equipment cover hardware that passes through third parties at either end of its life.
Clause 6.1 connection. Clause 6.1, Actions to address risks and opportunities, is the place to record chain risks and your treatment decisions.
Clause 4.2 connection. Clause 4.2, Understanding the needs and expectations of interested parties, helps identify customer and regulatory expectations about your suppliers.
Forward reference. Monitoring, review and change management of supplier services (A.5.22) follows next, and information security for use of cloud services (A.5.23) deals with an especially important part of the chain.
What auditors check
A defined process. Auditors look for documented steps for evaluating ICT products and services before purchase, and for how supply chain risk enters your risk assessment.
Visibility of dependencies. They ask you to talk through the dependencies of a critical service and see whether you know the main subcontractors and single points of failure.
Requirements passed down. Expect questions on how subcontractor obligations are covered in agreements or in the supplier’s published terms.
Procurement practice. They may sample recent purchases of ICT products to see whether security was considered, such as support lifespan and update policy.
Software dependencies. For development teams, auditors may ask how third-party components are tracked and kept patched.
Contingency. They look for evidence that you have considered what happens if a critical supplier or its upstream provider fails.
Common mistakes to avoid
Looking only at the first link. Assessing your direct vendor and ignoring its hosting and subprocessors misses where much of the risk sits.
Assuming big names are safe. Large providers invest heavily, but you still need to understand shared responsibility and your own configuration duties.
Unmanaged open-source dependencies. Nobody owns the list of libraries in production, so nobody notices when one is abandoned or vulnerable.
No view of concentration. Several critical tools relying on one underlying provider is a single point of failure that stays hidden.
Buying end-of-life products. A bargain that stops receiving security updates next year is not a bargain.
Treating it as a one-off exercise. The chain changes constantly. Build the review into your regular supplier oversight.
How 27kay can help
We help organizations map the dependencies that really matter and respond in proportion, without chasing every link. As part of ISO 27001 implementation, we run a short dependency workshop, connect the results to your risk assessment and prepare the evidence an auditor will ask for. For the full picture, see our ISO 27001 knowledge hub.
If your cloud provider’s own provider had a bad day, would you know, and would you know what to do? Get in touch - we will help you build that picture together.