Integrating security into organisational decisions: who decides, on what evidence
How security enters organisational decisions: context, mandate and accountability.

A security programme can be well run and still change nothing at the top. Integration is the point at which cybersecurity risk becomes one of the inputs to the decisions the organisation already makes about strategy, money and priorities — and named people answer for those decisions. This sheet is about that decision layer: who inside the organisation decides, on whose evidence, and where the arrangement is written down.
The test is simple. Integration is present when a security decision can be traced to the organisation’s mission, taken by an accountable owner, and fed into the same risk view used for every other kind of risk. It is absent when security decides about itself in a register that never reaches the people who set strategy.
The decision starts from the organisation’s context
CSF 2.0 begins with context, not controls. Its first stated outcome is “GV.OC-01: The organizational mission is understood and informs cybersecurity risk management” (lines 744–745), and context is the circumstances — “mission, stakeholder expectations, dependencies, and legal, regulatory, and contractual requirements – surrounding the organization’s cybersecurity risk management decisions” (lines 740–742). Two further outcomes complete the frame: “GV.RM-01: Risk management objectives are established and agreed to by organizational stakeholders” (lines 763–764), and “GV.RR-01: Organizational leadership is responsible and accountable for cybersecurity risk and fosters a culture that is risk-aware, ethical, and continually improving” (lines 792–793). The ordering matters. The objectives are agreed with stakeholders rather than handed down, and the accountability stays with leadership even when the work is delegated.
From risk beside the enterprise register to risk inside it
The mechanism that turns context into decisions is enterprise risk management (ERM). NIST IR 8286r1 places cybersecurity where it belongs: “Cybersecurity risk is one portion of the spectrum of an enterprise’s core risks” (line 544). It defines ERM as “an effective agency-wide approach to addressing the full spectrum of the organization’s significant risks by understanding the combined impact of risks as an interrelated portfolio rather than addressing risks only within silos” (lines 307–310). The register is not the decision; the profile is. The document states that “Enterprise-level decision-makers use the risk profile to choose which enterprise risks to address, allocate resources, and delegate responsibilities to appropriate risk owners” (lines 355–357), and that “The enterprise risk profile is a subset of carefully selected risks from the larger enterprise risk register” (lines 2478–2479). Integration is complete when the concurrent processes “create a vertically and horizontally integrated risk management process that connects the boardroom to the server room” (lines 461–463).
Who decides, who advises, who assures
The IIA’s Three Lines Model separates the roles by function, not by seniority. The governing body “Accepts accountability to stakeholders for oversight of the organization” (line 205) and “Determines organizational appetite for risk and exercises oversight of risk management (including internal control)” (lines 216, 218). First line roles are “most directly aligned with the delivery of products and/or services to clients of the organization” (lines 129–130) and keep the risk they take: “responsibility for managing risk remains a part of first line roles” (lines 137–138). Second line roles “provide assistance with managing risk” (line 130) but are “never fully independent from management, regardless of reporting lines and accountabilities” (line 370). The third line is where the separation is real: “Internal audit provides independent and objective assurance and advice on the adequacy and effectiveness of governance and risk management” (lines 142–143), and it is that independence that gives its assurance its weight.
DECIDE RUN ASSURE
------ --- ------
governing body first line third line
- sets appetite for risk - delivers, and owns - internal audit
and oversight the risk it takes - independent of
- accountable to second line management
stakeholders - advises, monitors,
challenges
\ | /
\ v /
+--------- the evidence the decision uses ----------+
: risk profile / risk register / appetite statement :
+---------------------------------------------------+
The management-system form of the same requirement
The same integration has a management-system form. The ISO/IEC 27001 store page states that “ISO/IEC 27001 is the world’s best-known standard for information security management systems (ISMS). It defines requirements an ISMS must meet” (line 20), and that the standard provides “guidance for establishing, implementing, maintaining and continually improving an information security management system” (line 21). The integrating claim is the one to keep: organisations that adopt the approach “make sure information security is built into organizational processes, information systems and management controls” (line 39). The standard’s clause text is paywalled, so this sheet cites only what the page states; the requirement’s content is not reconstructed.
The regulatory form: when the governing body is made responsible
Where a regulator intervenes, it does so at the same point. NIS2, Article 20(1), requires that “the management bodies of essential and important entities approve the cybersecurity risk-management measures taken by those entities in order to comply with Article 21, oversee its implementation and can be held liable for infringements by the entities of that Article” (line 845). Article 20(2) requires those members to “follow training” so that they “gain sufficient knowledge and skills to enable them to identify risks and assess cybersecurity risk-management practices” (line 847). The Directive’s recital states the intent: a high level of responsibility “at the level of the essential and important entities” (line 294). Approving the measures and answering for them is the statutory form of the accountability the frameworks describe.
Where integration stops being integration
Two failures look like integration. The first is a security register that never reaches the enterprise profile: the programme reports to itself and no decision at the top depends on it. The second is delegated accountability without the authority to match it — leadership is named as accountable but never given the risk profile, appetite statement or resource decision that accountability would need. The line between them is the evidence: integration exists when the people who decide can see the risk, and stops when they cannot.
The boundary with the neighbouring sheets follows. This sheet owns the decision layer — how security enters decisions and who holds the decision rights. The acceptance act itself belongs to the risk-acceptance and delegated-decisions sheet; the bridge from metrics and residual risk into strategy belongs to the metrics sheet; and the coordination layer between risk, controls, architecture and continuity belongs to the coordination sheet.
Level and prerequisites
L5 — specialist: the sheet is about integration and supervision across functions, not a new control, record or process. Prerequisites: the L1 vocabulary of governance and risk; the L2 records and criteria (asset inventory, risk and exception register, RACI, policy structure); the L3 processes (exceptions, traceability, prioritisation, change, suppliers, continuity); and the L4 sheets on frameworks, assurance, evidence and metrics — 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 — CSF 2.0 (NIST CSWP 29) — the Govern outcomes for context (GV.OC-01), risk-management objectives (GV.RM-01) and leadership accountability (GV.RR-01).
- NIST — IR 8286r1, Integrating Cybersecurity and Enterprise Risk Management — cybersecurity risk as one part of the enterprise portfolio, ERM defined against silos, the risk profile that directs decisions, and the boardroom-to-server-room integration.
- The IIA — The IIA’s Three Lines Model (2020) — the governing body, first, second and third line roles, and the assurance that independence gives the third line.
- ISO — ISO/IEC 27001:2022 store page — the information security management system as the management-system form of the requirement (page statements only; no clause text).
- EU — Directive (EU) 2022/2555 (NIS2), Article 20 and recital 137 — the management body’s approval duty and training requirement.