Risk, control, owner and evidence: keeping one chain traceable
One chain from a treated risk to the owner and the evidence that it works.

Governance answers one question about a control at a time: which risk made us choose it, who answers for it, and what shows that it works. Those answers and the control itself are links in one chain — a risk the organisation decided to treat → the control that treats it → the accountable owner → the evidence that the control works. The chain breaks in four recognisable ways: a control with no risk behind it, a risk that never became a control, an owner named for a control that does not exist, and evidence that records activity instead of effect.
One chain, four breaks
the question the link that has to answer it
what did we decide to treat? → a risk in the register, with a response chosen
which control carries it? → a control in the plan, planned or implemented
who answers for it? → a named role, with the authority that goes with it
how do we know it works? → evidence produced by assessment
every arrow is a translation, and every arrow can be missing
The direction is the part usually lost: evidence is not the control’s proof of itself, it is what lets someone travel back to the risk. SP 800-53A states the direction — determination statements “are linked to the content of the control … to ensure the traceability of assessment results back to the fundamental control requirements” (line 1031). No document read for this sheet prescribes a traceability matrix; the phrase occurs in none of them, so where an organisation keeps one it is a local practice built on that mechanism, and nothing here rests on it.
Break one: a control with no risk behind it
NISTIR 8286r1 sets the order from the other end from the way plans are usually built: “Controls, whether implemented or planned, should be analyzed with respect to a cybersecurity risk in the risk register” (lines 1600–1601). A control that no risk selected is not a weak control, it is unallocated cost, and it consumes the assessment capacity the selected controls need. SP 800-53 Rev. 5 gives the response its own control: RA-7 requires organisations to “Respond to findings from security and privacy assessments, monitoring, and audits in accordance with organizational risk tolerance” (line 16263) — so a control with neither a risk nor a finding behind it has nothing to respond to.
Break two: a risk that never became a control
8286r1 names four responses to negative risk — accept, transfer, mitigate, avoid (lines 1708–1711) — and only one is expected to move the risk: “In many cases, mitigation to bring exposure to negative cybersecurity risks within risk tolerance levels is accomplished using security controls” (lines 1771–1772). Accepting and transferring are legitimate outcomes that produce no control; the failure is a risk recorded as mitigated with nothing at the other end. The register’s arithmetic is the check: after the responses are chosen, “the residual risk (i.e., the remaining risk after applying risk responses) should then be recorded in the risk register’s Residual Risk column” (lines 1607–1609). A residual value that does not move when a mitigation is claimed is the chain reporting that the control is doing nothing.
Break three: an owner for a control that does not exist
Neither source names a “control owner”. SP 800-53 Rev. 5 assigns responsibility for controls that exist: system-specific controls “are the primary responsibility of the system owner and the authorizing official for a given system” (lines 1918–1919), and in a hybrid control “the common control provider is responsible for ensuring the implementation, assessment, and monitoring of the common part” (lines 1928–1930) — while warning that unclear responsibility at that junction “can introduce risk” (lines 1931–1933). 8286r1 supplies the owner of the risk instead: “the designated party responsible and accountable for ensuring that the risk is maintained in accordance with enterprise requirements” (lines 847–850), and keeps the two words apart, since responsibility for a system’s risks “might be assigned to a System Owner, but accountability might be assigned to an Authorizing Official” (lines 1945–1946). A named role attached to a control that exists only in a document is doing bookkeeping; the assessor who arrives to check it can report only that no implementation was there to confirm.
Break four: evidence that shows activity, not effect
SP 800-53 Rev. 5 asks for the evidence to be chosen while the control is chosen: “During control selection and implementation, it is important for organizations to consider the evidence (e.g., artifacts, documentation) that will be needed to support current and future control assessments” (lines 2065–2067). CA-2 states the bar that evidence has to clear — controls assessed “to determine the extent to which the controls are implemented correctly, operating as intended, and producing the desired outcome” (lines 6355–6358). A signed backup log records an activity somebody performed; what shows the control’s effect is a restore that was carried out and observed. 8286r1 asks for the same thing when it warns that confirming a mitigation is effective requires the control to be “evaluated by a competent assessor” (lines 1792–1793).
What the chain produces
SP 800-53A turns the last link into a determination: assessment objectives are achieved by “compiling or producing the evidence necessary to make the determination associated with each assessment objective”, and each determination statement returns one of two findings, “satisfied (S); or other than satisfied (O)” — the second also covering the assessor who “was unable to obtain sufficient information” (lines 2160–2177). CA-5 requires a plan of action and milestones documenting “the planned remediation actions … to correct weaknesses or deficiencies noted during the assessment of the controls” (lines 6636–6643); CA-7 requires ongoing control assessments and the correlation of what assessments and monitoring produce (lines 6772, 6777). SP 800-37r2 gathers the result into one object — “Authorization packages include security and privacy plans, security and privacy assessment reports, plans of action and milestones, and an executive summary” (lines 4735–4736) — and states its purpose as “credible and actionable security and privacy evidence”, not “additional paperwork, artifacts, or documentation” (lines 645–652). CSF 2.0 asks for the same duties as outcomes: a standardised method for documenting and prioritising risk (GV.RM-06, lines 778–779), roles and authorities “established, communicated, understood, and enforced” (GV.RR-02, lines 795–796), and responses “chosen, prioritized, planned, tracked, and communicated” (ID.RA-06, line 903).
Level and prerequisites
L3 — process: this sheet coordinates four things normally held by different people, and its subject is the joins between them. It assumes the L1 vocabulary (a control designed, implemented and verified; evidence and audit trails) and the L2 records (the risk and exception register; control objectives and verification criteria). It does not re-derive the criterion, the assessment object or the assessment method — that is the L2 sheet’s subject — and it does not manage evidence collection across a programme, which is L4.
Where to go next
The other L3 sheets of this batch are unpublished too. The sheet that continues this one owns verifying the fix and the residual risk; the vulnerability sheet feeds the same register from the other side.
References
- NIST — IR 8286r1, Integrating Cybersecurity and Enterprise Risk Management (ERM) — https://doi.org/10.6028/NIST.IR.8286r1 — the risk-owner element of the register, the four risk-response types, residual risk, and the separation of responsibility from accountability.
- NIST — SP 800-53 Rev. 5, Security and Privacy Controls for Information Systems and Organizations — https://doi.org/10.6028/NIST.SP.800-53r5 — CA-2, CA-5, CA-7, RA-7, the evidence-at-selection sentence, and the responsibility split for system-specific and hybrid controls.
- NIST — SP 800-53A Rev. 5, Assessing Security and Privacy Controls in Information Systems and Organizations — https://doi.org/10.6028/NIST.SP.800-53Ar5 — the traceability sentence in §2.4 and the determination/evidence wording of §3.3.
- NIST — SP 800-37 Rev. 2, Risk Management Framework for Information Systems and Organizations — https://doi.org/10.6028/NIST.SP.800-37r2 — the contents and purpose of the authorization package.
- NIST — The NIST Cybersecurity Framework (CSF) 2.0, NIST CSWP 29 — https://doi.org/10.6028/NIST.CSWP.29 — GV.RM-06, GV.RR-02 and ID.RA-06.