Governing complex programmes and dependencies: who owns each relationship
Governing a programme across many suppliers means owning each dependency, not listing it.

A security programme whose dependencies reach outside it — suppliers of critical services, shared platforms, providers that hold its data or run part of its service — cannot be governed like one that owns everything it depends on. Its programme-level instruments exist to be coordinated: an organisation-wide supply chain risk management strategy, a continuous monitoring strategy, a tiered priority scheme, and an aggregate view of the risk registers where those dependencies sit.
The governance question is not how many suppliers a programme has. It is who owns each relationship, what is monitored while it runs, what happens when it ends, and where the dependency appears in the risk register and the continuity plan. A dependency that becomes visible only when an incident reveals it was never governed — it was discovered.
The programme-level instruments exist to be coordinated
SP 800-53 Rev. 5 gives a programme two organisation-level strategies it must align. PM-30 requires the organisation to “Develop an organization-wide strategy for managing supply chain risks associated with the development, acquisition, maintenance, and disposal of systems, system components, and system services” (lines 14660–14662), a strategy whose discussion states its contents: “an unambiguous expression of the supply chain risk appetite and tolerance for the organization, acceptable supply chain risk mitigation strategies or controls, a process for consistently evaluating and monitoring supply chain risk” (lines 14670–14673). PM-31 adds the monitoring side — an organisation-wide “continuous monitoring strategy” with organisation-defined metrics and frequencies (line 14711). The two are not parallel. PM-9’s discussion states the link: “The supply chain risk management strategy described in PM-30 can also provide useful inputs to the organization-wide risk management strategy” (lines 13924–13926). The dependency strategy feeds the top-level risk strategy rather than standing beside it.
Tiered prioritisation is what makes many suppliers governable
A programme with dozens of dependencies cannot treat them all alike and stay governable. SP 800-161r1-upd1 is explicit: “agencies should establish a tiered set of priority levels commensurate with the criticality and potential for risk impact”, a tiering that “can then be used to guide or compel the timing of, order, scope, and frequency of” assessments (lines 12742–12745), and the segmentation “helps to focus attention and assign priority to those critical suppliers of the most strategic or operational importance to the enterprise” (lines 2338–2341). CSF 2.0 states the same outcome — “GV.SC-03: Cybersecurity supply chain risk management is integrated into cybersecurity and enterprise risk management, risk assessment, and improvement processes”, with “GV.SC-04: Suppliers are known and prioritized by criticality” (lines 835–836, 838). Priority is what turns a supplier list into something a programme can govern.
The practices that show what programme-level work looks like
NISTIR 8276 records the industry practices behind that priority: its key practices include “3. Know and Manage Critical Suppliers” and “6. Include Key Suppliers in Resilience and Improvement Activities” (lines 188, 191); a critical supplier is one “which, if disrupted, would create a negative business impact on the organization” (lines 606–607). Mature organisations “include their critical suppliers, products, and assets in their contingency planning, incident response, and disaster recovery” (lines 724–726), and the practice continues across the relationship — “Mature acquirers establish supplier-monitoring programs that cover the entire supplier relationship life cycle and monitor a variety of risks” (lines 758–759). SP 800-161r1-upd1 carries the same instruction at programme level: “Include critical suppliers in contingency planning, incident response, and disaster recovery planning and testing” (lines 2842–2843).
Keeping a complex programme legible: aggregation and the register
A programme cannot govern what it cannot see whole. NISTIR 8286Cr1 describes the machinery: for register input into enterprise risk, “there are three key phases to take to ensure the quality, efficacy, and efficiency of the data: aggregation, normalization, and analysis” (lines 532–534), and because the registers aggregated “from the system level” upward increase in number, the “process of aggregation should scale with the enterprise” (lines 566–568). The return is legibility — “Systematic aggregation, normalization, and analysis of cybersecurity risk registers (CSRRs) help risk managers gain a comprehensive understanding of an enterprise’s cybersecurity risk posture” (lines 1958–1960). The legal form of the same idea is a register: under DORA, “financial entities shall 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” (Article 28(3), line 923). NIS2 requires no such register; it carries the coordination instead — Article 22 governs “Union level coordinated security risk assessments of critical supply chains” (line 880), and Article 21(3) requires entities to “take into account the results of the coordinated security risk assessments of critical supply chains carried out in accordance with Article 22(1)” (line 873).
The governance test for a dependency
Four questions separate governing a dependency from merely documenting it. Who owns the relationship — a named owner inside the programme, not a procurement contact. What is monitored — across the whole relationship, not a one-off check before onboarding. What happens at exit — for the function the dependency supports. Where the dependency appears — in the risk register as an identified risk, and in the continuity plan as a dependency of the function it serves.
for each dependency:
1. owner -> who is accountable inside the programme
2. monitoring -> what is watched, over the whole relationship
3. exit -> how the function continues without it
4. register -> where it appears in risk and continuity records
Where a programme chart stops being governance
A programme chart maps an organisation; it governs nothing in it, because a box on a chart assigns no ownership, monitors nothing and plans no exit. A dependency discovered during an incident was never governed — it was invisible until it failed, so the register and the continuity plan were both incomplete. And the more critical suppliers a programme has, the less meaningful an unweighted count of them is: a number that treats a commodity provider and a single point of failure alike hides the concentration the programme exists to manage. Exit planning is part of the dependency decision, not an afterthought — what replaces a supplier, or how a function continues without it, is settled when the dependency is accepted, not when the contract ends.
Level and prerequisites
L5 — specialist: the sheet integrates what the lower levels produce and asks the governance question above them — how a dependency-heavy programme stays owned, prioritised and legible across functions and organisations. It supervises no single framework, audit or measure but the whole dependency portfolio of a programme and the programme-level instruments that must be coordinated. Prerequisites: the L1 vocabulary of dependencies and accountability, the L2 records (service criticality and dependencies, suppliers and external services, owner and custodian) and the L3 processes — supplier evaluation and critical dependencies, security requirements for external services, business impact analysis and continuity — none re-derived here.
Where to go next
- Knowledge — the Knowledge register this sheet belongs to.
- Cybersecurity Governance — the macro-area.
- Security governance foundations — the node this sheet sits in.
References
- NIST — SP 800-53 Rev. 5, Security and Privacy Controls — the programme-level supply chain risk management strategy (PM-30), the continuous monitoring strategy (PM-31) and the PM-9 discussion line that links them.
- NIST — SP 800-161 Rev. 1 (upd. 2022), C-SCRM Practices for Systems and Organizations — the tiered priority levels and the instruction to include critical suppliers in contingency and recovery planning.
- NIST — IR 8276, Key Practices in Cyber Supply Chain Risk Management — the industry key practices: knowing critical suppliers, including them in resilience work, and monitoring across the relationship.
- NIST — IR 8286Cr1, Staging Cybersecurity Risks for ERM and Governance Oversight — aggregation, normalization and analysis of cybersecurity risk registers.
- NIST — CSF 2.0 (NIST CSWP 29) — the GV.SC-03 and GV.SC-04 outcomes.
- European Union — DORA, Regulation (EU) 2022/2554 — the Article 28 register of information on ICT third-party arrangements.
- European Union — NIS2, Directive (EU) 2022/2555 — Article 22 coordinated security risk assessments of critical supply chains.