Coordinating risk, controls, architecture and continuity: four concerns, one fabric
The devices that stop risk, controls, architecture and continuity drifting apart.

An integrated programme produces four bodies of artefact: a risk register, a control set, an architecture map and a continuity plan. Each is defensible on its own: nothing forces the other three to agree, so a change lands in one and is invisible in the rest. A control is selected that no architecture element owns; a system is re-architected without touching the risk it was answering.
Coordination is not a fifth document. It is the set of devices that carries one understanding of the enterprise through all four concerns, so the same change is visible in each. This sheet names those devices and the test that shows whether they work.
The multilevel idea: one risk process across three tiers
The integrating device in NIST’s risk guidance is the tiered process. SP 800-39 states: “To integrate the risk management process throughout the organization, a three-tiered approach is employed that addresses risk at the: (i) organization level; (ii) mission/business process level; and (iii) information system level” (lines 834–836). The three tiers — organization (Tier 1), mission/business process (Tier 2) and information system (Tier 3) — are why risk and architecture cannot be separate conversations: “the information security architecture portion of the enterprise architecture developed at Tier 2 influences and guides the allocation of information protection needs which, in turn, influences and guides the allocation of the security controls to specific components of organizational information systems at Tier 3” (lines 896–899).
The programme-level controls that carry coordination
SP 800-53 Rev. 5’s organisation-tier PM family carries coordination in three controls. PM-7 Enterprise Architecture (line 13830) requires an enterprise architecture maintained with consideration for information security, privacy and the resulting risk (lines 13832–13834): it coordinates the map. PM-9 Risk Management Strategy (line 13892) requires the strategy to be implemented “consistently across the organization” (line 13904), and its discussion places the organisation’s risk tolerance inside that strategy (line 13914): it coordinates the currency, so every function judges risk alike. PM-11 Mission and Business Process Definition (line 13963) requires mission and business processes to be defined with information security, privacy and their resulting risk in view (lines 13967–13969): it coordinates the trace.
The aggregate understanding the disciplines share
Coordination needs one object all four concerns can point at; NISTIR 8286Cr1 supplies it: “because cybersecurity risk is only one of dozens of risk types in the enterprise risk universe, that risk understanding will itself be integrated with similar aggregate observations of other collective risk points” (lines 331–333). The shared object is that aggregate: the enterprise risk view the register, the control evidence and the architecture decisions roll up into.
The same device in ISO terms: one managed system
Where NIST uses tiers and controls, ISO/IEC 27001 uses the management system: its ISO Store page describes “guidance for establishing, implementing, maintaining and continually improving an information security management system” (line 21) and states that such a system is a tool for risk management and cyber-resilience (line 26). Risk management and the controls live inside one managed system, not parallel registers; the standard is paywalled, so only the page’s statements are cited, and the requirements content is the ISMS sheet’s subject.
The seams: appetite, and continuity inside a change
Two seams show whether the fabric is real. The first is the appetite statement: the Cybersecurity Framework (CSF) 2.0 requires that “GV.RM-02: Risk appetite and risk tolerance statements are established, communicated, and maintained” (lines 766–767). One communicated statement lets risk, controls and architecture be judged in one currency.
The second is continuity. Contingency planning is not a document filed beside the architecture: SP 800-34 Rev. 1 makes it part of change control, requiring that “the ISCP be reviewed and updated regularly as part of the organization’s change management process” (lines 2093–2094). The practical reading is a test: which decisions in a change have to consult the continuity plan? At least those that alter a system, a process or a dependency the plan relies on.
Where coordination stops
Three failure modes separate a fabric from a folder. Uncoordinated artefacts are not coordination: four documents that never reference one another are four documents. An architecture map nobody updates becomes fiction: a decision never revised describes an enterprise that has moved on. A continuity plan that was never consulted during a change is a document, not a control. The test is four questions for every change: who holds the risk, which control implements the response, where it lands in the architecture map, and what it does to the continuity plan. A change that cannot answer all four has fallen between the seams.
the change the four questions it must answer
---------- ---------------------------------
who holds the risk? (risk)
a proposed change -> which control answers? (controls)
where in the map? (architecture)
what to the plan? (continuity)
Level and prerequisites
L5 — specialist: the sheet creates no control, record or process; it describes the devices that keep four concerns describing one enterprise. Prerequisites: the L1 vocabulary of risk, control and evidence; the L2 records (risk register, control objectives, asset and service inventory); the L3 processes of change management, configuration management and business impact analysis with continuity; and the L4 sheets on frameworks and on the ISMS. Sheet 1 owns the decision layer; this sheet owns the coordination layer; the L3 change, configuration and BIA/continuity sheets are named, not rebuilt.
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-39, Managing Information Security Risk — the three-tiered approach and the Tier 2 architecture that guides Tier 3 control placement.
- NIST — SP 800-53 Rev. 5 — PM-7 enterprise architecture, PM-9 risk management strategy and PM-11 mission and business process definition.
- NIST — IR 8286Cr1 — the integration of a cybersecurity risk understanding into aggregate enterprise risk.
- NIST — CSF 2.0 (NIST CSWP 29) — the GV.RM-02 risk appetite and tolerance outcome.
- NIST — SP 800-34 Rev. 1, Contingency Planning Guide — the contingency plan reviewed and updated as part of change management.
- ISO/IEC — ISO/IEC 27001:2022, ISO Store page — the management system as the integrating device.