A.5 Organizational controls

A.5.21 Managing information security in the ICT supply chain

Not mandatory by default – decided in your SoA

What it means in plain language

Manage security risks in the ICT supply chain – including your suppliers’ suppliers, software components and hardware.

Is it mandatory? Not automatically. You must consider this control in your Statement of Applicability (6.1.3 d). Include it if your risk assessment, laws, contracts or business needs require it; if you exclude it, write down a justification an auditor will accept.

Why this control matters

The operational priority is to evaluate security risk beyond the direct supplier, including hosted services, software dependencies, hardware provenance, and the supplier’s own subcontractors. The operating model should connect procurement, architecture, legal, and engineering decisions so reviewers can see how due diligence, contractual flow-downs, and technical verification work together.

Common auditor findings to check for

Potential gaps to test in your own environment, not a claim about observed audit frequency.

  • Supplier due diligence records only cover the prime vendor, leaving subcontractors, hosting regions, or software component sources unreviewed for inherited risk.
  • Engineering releases consume third-party libraries or images without signature verification, SBOM review, or approved-source evidence tied to procurement decisions.
  • Contracts mention security vaguely but omit flow-down requirements for incident notice, change notice, vulnerability handling, or supplier-chain transparency.

How you can implement it

Tools and review intervals are examples; choose them according to risk, obligations and your operating environment.

  • Define a supplier-chain intake path owned by procurement with security review from architecture and legal before onboarding. Classify ICT suppliers by data access, integration depth, and business criticality, then require evidence appropriate to the tier, such as subprocessor lists, component provenance, update channels, vulnerability disclosure terms, and contractual flow-down clauses.
  • Use the Supplier Onboarding & Assessment Procedure to capture both direct and inherited dependencies. Include questions on hosting locations, manufacturing origin, managed-service subcontractors, open-source or commercial components, firmware sources, and patch delivery responsibilities. Record the rationale for accepting any residual risk and the accountable approver for exceptions.
  • For software and devices, require technical verification aligned to the route of supply: signed packages, checksum validation, SBOM review, dependency scanning, and trusted repository settings. For cloud or hosted services, document how tenant isolation, backup access, and support privileges are controlled. Keep change-trigger criteria for mergers, hosting relocation, major component changes, and subcontractor additions.
  • Review critical suppliers on an illustrative quarterly or annual cadence based on risk. Track incidents, SLA breaches, remediation commitments, and changes to service architecture in the Supplier Register. Escalate to risk owners when supplier evidence expires, when a product line changes, or when the supplier cannot evidence secure control over downstream providers.

What an auditor will ask to see

  • Completed supplier assessments showing subprocessor, hosting, and component-origin review for critical ICT vendors.
  • Signed contracts or order terms with security clauses on disclosure, incident notice, change notice, and flow-down obligations.
  • SBOMs, package-signature checks, dependency-scan results, or firmware provenance records linked to released assets.
  • Supplier Register entries with review dates, risk ratings, incidents, exceptions, and named approvers for acceptance.

Baseline documents in the kit

These free kit documents help you document or evidence A.5.21. Each one is tailored to your organization when you build your kit.

Connect this work to your ISMS

Review the dependencies with A.5.19 — Information security in supplier relationships and A.5.20 — Addressing information security within supplier agreements. Keep the ownership and evidence consistent across these activities.

NIS2 and ISO/IEC 27001: reuse controls and check legal gaps for the wider implementation context.

Use the SIG and CAIQ questionnaire accelerator to find supporting documents. A mapping is a starting point: verify your actual operating evidence before answering a buyer.

For help adapting this to your environment, explore ISO/IEC 27001 consulting, starting with a free one-hour consultation.

Get these documents tailored to your organization

109 ready-to-edit documents, including all 19 mandatory ones, tailored from a short scoping questionnaire and linked to your risk register and SoA.

Start free

Plain-language interpretation by an ISO/IEC 27001 lead implementer, not the official text of ISO/IEC 27001:2022.