Articles

Third-party and supply chain risk: governing the dependencies you do not own

Supply-chain risk as a governed domain: priority, resilience and the recorded reason.

Reading: 5 minCybersecurity Governance

Article cover: Third-party and supply chain risk: governing the dependencies you do not own

Third-party and supply-chain risk owns the dependencies an organisation does not control: which suppliers matter, who decided that they matter, and what happens when one fails. As a checklist it asks whether the questionnaire was sent; as a governed risk domain, which dependencies can hurt the mission and who is accountable.

The domain folds supply-chain risk into risk management, prioritises suppliers by criticality, and draws the most critical into the organisation’s own resilience work.

   supplier risk as a governed domain, not a checklist
   ---------------------------------------------------
   integrate    C-SCRM into risk management at every level
                (enterprise / mission and business process / operational)
   prioritise   know the suppliers, rank them by criticality
   rehearse     include critical suppliers in contingency planning,
                incident response and disaster recovery
   record       criticality is a judgement someone made - write it down

C-SCRM integrates supply-chain risk into risk management

NIST SP 800-161 Rev. 1 (upd. 2022) provides “guidance to organizations on identifying, assessing, and mitigating cybersecurity risks throughout the supply chain” and “integrates cybersecurity supply chain risk management (C-SCRM) into risk management activities by applying a multilevel, C-SCRM-specific approach” (lines 127–130). The multilevel structure is SP 800-39’s — “1) the enterprise level, 2) the mission and business process level, and 3) the operational level” — across which “the C-SCRM process is seamlessly carried out” (lines 1495–1496, 1501–1502). The risk is entered where it can be acted on.

Knowing and prioritising the critical suppliers

Prioritisation is the domain’s first act: mapping suppliers into “strategically relevant groupings” lets the organisation “assign priority to those critical suppliers of the most strategic or operational importance to the enterprise and its mission and business processes” (lines 2335, 2340–2341). NISTIR 8276 lists “Know and Manage Critical Suppliers” as a key practice (line 188) and defines critical suppliers as “those suppliers which, if disrupted, would create a negative business impact on the organization”, reached by prioritising first “critical missions, assets, systems, processes, and data” (lines 606–610). CSF 2.0 states the outcome as “GV.SC-04: Suppliers are known and prioritized by criticality” (line 838).

Assurance checks a supplier once; resilience asks what happens when it fails. NISTIR 8276 observes that the perimeter “is no longer meaningful; threat actors intentionally target the suppliers of more cyber-mature organizations to take advantage of the weakest link” (lines 99–100), and its sixth key practice is “Include Key Suppliers in Resilience and Improvement Activities” (line 191). It notes that “Incidents will happen to even the most mature organizations”; mature acquirers “include their critical suppliers, products, and assets in their contingency planning, incident response, and disaster recovery” (lines 723–726). SP 800-161 Rev. 1 requires the same: enterprises should “Include critical suppliers in contingency planning, incident response, and disaster recovery planning and testing” (lines 2842–2843).

The programme outcome: agreed by stakeholders, integrated into risk management

CSF 2.0 expresses the governance result as “GV.SC-01: A cybersecurity supply chain risk management program, strategy, objectives, policies, and processes are established and agreed to by organizational stakeholders” (lines 829–830), alongside “GV.SC-03: Cybersecurity supply chain risk management is integrated into cybersecurity and enterprise risk management, risk assessment, and improvement processes” (lines 835–836). The test: a programme is “agreed to by” stakeholders, not one a security team issues alone.

For an EU financial entity, DORA turns the dependency into a legal record: Article 28(3) requires financial entities to “maintain and update at entity level, and at sub-consolidated and consolidated levels, a register of information in relation to all contractual arrangements on the use of ICT services provided by ICT third-party service providers” (line 923). Keeping it at every group level makes concentration visible above the signing entity. NIS2 works the other way: the Cooperation Group, with the Commission and ENISA, “may carry out coordinated security risk assessments of specific critical ICT services, ICT systems or ICT products supply chains, taking into account technical and, where relevant, non-technical risk factors” (Article 22(1), line 881).

The supplier-relationship view

ISO/IEC 27036-1:2021, the “Overview and concepts” part of the supplier-relationship family, states on its ISO Store page that it “addresses perspectives of both acquirers and suppliers” (line 13). The parts that carry the requirements are paywalled, so only the page’s own statement is used here. A relationship has two sides whose expectations must meet, so governance concerns its terms, not only the acquirer’s checklist.

Where the domain meets its limits

Three limits keep it honest. First, assessing a supplier is not assessing its sub-processors: NISTIR 8276 describes supply chains as having “multiple layers of sub-suppliers” (line 660) and treats “Propagate security requirements to suppliers’ sub-suppliers” as a separate activity (line 846). Second, a contract clause is a control only if its operation can be observed — the document is evidence that something was specified, not that it happens. Third, criticality is a business judgement the organisation records, not a property the supplier carries; two organisations may rank the same supplier differently, so the recorded reason, not the ranking, is the governable artefact.

Level and prerequisites

L5 — specialist: the sheet adds no new control, record or process (the lower levels own those) but integrates them into a governed risk domain and fixes what the organisation must be able to say about its dependencies. Prerequisites: the L2 sheets on suppliers and external services, and on service criticality and dependencies, and the L3 sheets on supplier evaluation and critical dependencies and on security requirements for external services.

Where to go next

References

  • NIST — SP 800-161 Rev. 1 (upd. 2022), Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations — C-SCRM as a multilevel integration into risk management and the obligation to include critical suppliers in contingency planning, incident response and disaster recovery.
  • NIST — NISTIR 8276, Key Practices in Cyber Supply Chain Risk Management: Observations from Industry — the key practices of knowing and managing critical suppliers and including key suppliers in resilience and improvement activities, and why threat actors target less mature suppliers.
  • NIST — CSF 2.0 (NIST CSWP 29) — the GV.SC supply-chain risk management outcomes (GV.SC-01, GV.SC-03, GV.SC-04).
  • ISO — ISO/IEC 27036-1:2021, Cybersecurity — Supplier relationships — Part 1: Overview and concepts (ISO Store page) — the overview part addresses both acquirers and suppliers.
  • EU — DORA, Regulation (EU) 2022/2554 — Article 28(3), the register of information at entity, sub-consolidated and consolidated level.
  • EU — NIS2, Directive (EU) 2022/2555 — Article 22(1), coordinated security risk assessments of critical supply chains.
Nodrius Field Kit — cover

Get the Nodrius Field Kit

Enter your email and we'll send you the complete Field Kit: eight technical resources in one download.

Your email address is sent to Nodrius and used to deliver the Field Kit to you by email. Marketing messages are separate and optional: the checkbox does not affect your download, and you are only added to our updates list if you tick it. Privacy Policy.

Privacy & cookies

This site does not use cookies, analytics or tracking, and it does not profile you. There is nothing technical to switch off, so Accept and Reject change nothing about how the site works: either choice lets you browse everything normally.

The only difference is what your browser remembers: two entries in local storage — your choice here, so this notice is not shown again, and a marker that the Field Kit offer has already been made — so the offer is presented once and not on every page. They contain no identifier, they are not shared with anyone, and the site sets no cookie for either.

What we do with your data
How your email address is used when you ask for a Resource, how long it is kept and which rights you have — in the Privacy Policy.
What the site stores in your browser
Two entries in local storage — your choice on this notice and whether the Field Kit offer has been shown — and no cookies, no session storage, no third-party content: in the Cookie Policy.