Who is the risk owner

A risk owner is the designated party responsible and accountable for keeping a risk within enterprise requirements, as NIST IR 8286 defines it. The risk owner is not automatically the system owner or the signer: in a federal system only the authorizing official can accept risk. NIST wording read 19 Nov 2026.

  1. RemediateCovered here
  2. Mitigate now, fix laterCovered here
  3. Accept with a dated exceptionCovered here

The definition and where it is used

NIST IR 8286 lists the risk owner as a field of the cybersecurity risk register: "The designated party responsible and accountable for ensuring that the risk is maintained in accordance with enterprise requirements. The Risk Owner may work with a designated Risk Manager who is responsible for managing and monitoring the selected risk response". NIST IR 8286B, Section 2.4.3, says the field records "the personnel and/or organizational element responsible for ensuring that the described risk response is implemented", chosen "at the discretion of the enterprise but should be consistently used".

IR 8286C is stricter about the person: "The party designated as the risk owner must be continually knowledgeable about relevant risk conditions and must also have the accountability and authority to manage the risk." It asks that responsibility "be periodically reviewed (e.g., monthly) to ensure that the risk owner is the appropriate designee".

Which role answers which question

Role wording as read on 19 Nov 2026.
RoleQuestion it answersWhat the source says
Risk ownerWho owns the loss if the finding is exploited?"in whom the organization has invested the authority and accountability for making risk-based decisions and who owns the loss associated with a realized risk scenario" (NIST IR 8286B)
Risk managerWho recommends the treatment?"may or may not be the system owner"; helps recommend treatment (NIST IR 8286B)
System ownerWho schedules the patch and runs the change?"an organizational official responsible for the procurement, development, integration, modification, operation, maintenance, and disposal of a system" (NIST SP 800-37 Rev. 2, Appendix D); the provider that operates the system when it is hosted
Authorizing officialWho signs a dated acceptance in a federal system?"the only organizational official who can accept the security and privacy risk to organizational operations, organizational assets, and individuals" (NIST SP 800-37 Rev. 2, Appendix D and Task R-4)
Authorizing official designated representativeWho runs day-to-day risk activities for the authorizing official?The one activity that "cannot be delegated" to the representative is "the authorization decision and signing of the associated authorization decision document (i.e., the acceptance of risk)" (NIST SP 800-37 Rev. 2, Appendix D)
Signer outside the federal settingWho signs when SP 800-37 does not apply?The role named in your own policy; see who may sign
More senior stakeholder named in advanceWho decides when a time limit or threshold is crossed (escalation), or when the matter is sensitive or critical (elevation)?Escalation by time frame or risk condition, elevation of the response decision (NIST IR 8286B)

IR 8286B separates the last two terms. "Risk Escalation occurs when a particular threshold is reached, either based on a time frame or some other risk condition", for example "a risk that has remained through more than two fiscal periods without adequate treatment". "Risk Elevation is the process of transferring the decisions on risk response to a more senior stakeholder when the factors involved (e.g., a regulatory compliance risk) are particularly sensitive or critical." Both need criteria written in advance, so an expired exception has a defined next owner.

Worked case: SharePoint, 11 Aug to 14 Oct 2026

The sample organization is invented; the CVE, Microsoft and CISA dates are real (NVD, the Microsoft Security Response Center update guide and the CISA KEV feed, version 2026.11.18, read 19 Nov 2026). Its on-premises SharePoint Server 2019 farm of four servers holds leave and payroll forms. Roles in its policy: risk owner, the Director of HR Operations; system owner, the Head of Collaboration Platforms; signer for any date past a CISA due date, the CISO.

  1. 11 Aug 2026: Microsoft publishes CVE-2026-65660 with the August security updates, as revision 1.0 titled a spoofing issue with a CVSS 3.1 base score of 6.5. On 14 Aug the owner and system owner triage it as Medium on that rating, because 6.5 falls in the Medium band of CVSS 3.1 (4.0 to 6.9), and set the patch for the 30 Sep cycle. The risk register entry names the owner and a backup, per IR 8286B.
  2. 27 Aug: Microsoft's revision 1.1 updates the impact, title and FAQs; the vulnerability is now titled SharePoint Server Remote Code Execution, with CVSS 3.1 base score 8.8 (up from 6.5). Nobody is notified; the entry still reads Medium.
  3. 14 Sep: the monthly owner review (the IR 8286C example interval) picks up the revision, 18 days after it. The owner re-rates the entry High and moves the patch to 5 Oct.
  4. 25 Sep: Microsoft revision 1.2 records evidence of observed attacks and CISA adds the CVE to KEV with a due date of 28 Sep. The sample policy's escalation rule (any KEV listing goes to the CISO the same day) fires. The CISO, as signer, rules that the 5 Oct date cannot stand.
  5. 27 Sep: the system owner installs KB5002894 and KB5002896 (the SharePoint Server 2019 updates, fixed build 16.0.10417.20198) on all four servers, one day inside the 28 Sep due date, and reports the build. The owner confirms; the CISO closes the entry.
  6. 14 Oct: the next monthly review confirms the owner is still the right designee, as IR 8286C asks, and the closed entry keeps the dates above.

Three roles acted on one finding. The risk owner acted four times: 14 Aug, 14 Sep, 27 Sep and 14 Oct; the system owner on 14 Aug and 27 Sep; the CISO on 25 Sep and 27 Sep. The gap that mattered was 27 Aug to 14 Sep, a monthly review catching a vendor revision; the escalation rule did the rest. A weekly feed check on vendor revisions would close that gap, and the record would show who is assigned to it.

How owner assignment fails

IR 8286C asks for an owner with "the accountability and authority to manage the risk" and for periodic review of the designation. Three failures break that, and each leaves a trace in the finding record. The causes are this site's reading; the requirement is NIST's.

Failure modes of risk owner assignment, with the NIST wording they depart from named in the text. Read 19 Nov 2026.
FailureWhat happensWhat the record showsRepair
Orphaned owner after a reorganizationThe named person or role no longer exists, so escalation criteria point at nobody and the finding agesA "last confirmed" date older than the review interval (IR 8286C gives monthly as an example), or an owner field naming a retired roleName a role and a backup, not only a person; re-confirm the owner whenever the organization chart changes
Owner is the requesterThe person who asks for the exception also owns the risk and signs it, so no second check existsThe requester and approver fields hold the same roleKeep the approver a separate role, as in the sample signing rule
Shared platform with no single business unitSeveral units use one farm or service, none has the authority to decide for the others, and the owner defaults to IT operations, which runs the system but does not bear the lossOwner and system owner hold the same role; the affected business units appear nowhereName an owner at the level that holds authority over all users of the platform, list the units affected, and use elevation (IR 8286B) when they disagree

When the usual answer is wrong

The usual split is the risk owner decides, the system owner patches and the signer accepts. Two setups change it.

  • Vendor-hosted software. The vendor is the system owner and schedules the fix, so the customer's owner cannot schedule the patch. IR 8286B gives the example: "a system owner may be a cloud service provider that operates a hosted application, while the risk owner may be a corporate business unit that processes important data within that application". The customer's business unit still owns the loss and decides whether to wait, add a control or leave the service. The record carries a vendor-dependency row until the vendor ships; see SaaS you cannot patch.
  • Shared services. A shared service has one provider-side owner and several consuming business units. Each consumer owns its own loss, so the register holds one row for the platform finding and one owner per consuming unit, with the provider as system owner on all of them. This is this site's practice; IR 8286B supplies the terms.

What the finding record holds

  • One named risk owner, with a backup if the enterprise uses one (IR 8286B).
  • The system owner or operating provider, as a separate field. A finding waiting on a fix also carries a plan of action and milestones entry.
  • A separate approver role for acceptance; for a federal system the authorizing official (SP 800-37 Rev. 2).
  • The date the owner was last confirmed, against the monthly example in IR 8286C.
  • The escalation and elevation criteria that apply, copied from policy.

Sources

Last reviewed