Risk transfer vs risk acceptance

Risk transfer shifts liability for a risk to another party; risk acceptance keeps it. NIST SP 800-39 says transfer "reduces neither the likelihood of harmful events occurring nor the consequences", so a transferred vulnerability still needs a fix, a mitigation or a dated exception. Sources read 19 Nov 2026.

  1. Remediate
  2. Mitigate now, fix later
  3. Accept with a dated exceptionThis page is about it

What transfer is in three NIST texts

SP 800-39 defines the pair this way: "Risk transfer shifts the entire risk responsibility or liability from one organization to another organization (e.g., using insurance to transfer risk from particular organizations to insurance companies). Risk sharing shifts a portion of risk responsibility or liability to other organizations (usually organizations that are more qualified to address the risk)." The other two NIST texts treat transfer as partial.

Wording of transfer in three NIST publications, read 19 Nov 2026.
TextTransfer meansExample given
NIST SP 800-39, Task 3-1Shifting liability and responsibility when organizations "desire and have the means to shift risk liability and responsibility to other organizations"Insurance
NIST IR 8286, Table 3"For cybersecurity risks that fall outside of tolerance levels, reduce them to an acceptable level by sharing a portion of the consequences with another party"Cybersecurity insurance
NIST SP 800-40 Rev. 4, Section 2.1Reduce the risk by sharing consequences with another partyInsurance, or replacing installed software with SaaS "where the SaaS vendor/managed service provider takes care of patching"

What transfer leaves in place

SP 800-39: "It is important to note that risk transfer reduces neither the likelihood of harmful events occurring nor the consequences in terms of harm to organizational operations and assets, individuals, other organizations, or the Nation." NIST IR 8286 adds that "there are often consequences that cannot be transferred, like loss of customer trust". A vulnerability stays exploitable after a policy is bought; part of the bill moves.

SP 800-40 Rev. 4 states the default: "By default, an organization accepts the risk posed by using its software." Transfer is a step in addition to a response to the flaw, never the response itself. The finding still takes one of the outcomes on the decision table.

Which response each arrangement is

Arrangements sorted by this site against the response types in NIST IR 8286 Table 3 and SP 800-40 Rev. 4 Section 2.1. SP 800-40 lists replacing installed software with SaaS under Transfer because it shares consequences with another party. This table files it as Share because SP 800-39 reserves transfer for shifting the entire liability, and the customer keeps its data, configuration and the decision to move. NIST's mitigation covers both fixing the flaw and reducing its likelihood or impact; this site records the first as remediation and the second as mitigation. Read 19 Nov 2026.
ArrangementResponse typeWhat movesWhat stays with youRecord
Cyber insurance policy covering a finding you keepAccept, plus partial transferPart of the financial consequenceLikelihood, the outage, lost customer trust, and the finding itselfAcceptance record with expiry; policy number and exclusions noted
Move the product to SaaS where the vendor patchesShare (SP 800-40 Rev. 4 files this under Transfer)The patching taskConfiguration, data, and the decision to move; see SaaS you cannot patchException or vendor-dependency row until the move is done
Managed-service contract that names patch timesShareResponsibility for the actionLiability for missed dates unless the contract says otherwiseContract clause and owner for checking the provider
Federal agency buys a policyGenerally not availableNothingEverything (SP 800-39: self-initiated transfers by public sector organizations are "generally not possible")Authorizing official's acceptance in the risk acceptance form
Decommission the systemAvoidThe whole risk, by removing the assetNothing, once it is off the networkDecommission record
Apply the fixRemediate (NIST SP 800-39 files it under risk mitigation)The flawResidual risk, usually noneRescan evidence
Keep the finding, no policyAcceptNothingAll of itException register row with expiry

Worked case: a policy does not move the 19 Sep due date

The sample organization is invented, including its policy clause; the CVE, advisory and KEV dates are real (NVD and the Cisco advisory, read 19 Nov 2026). It runs two Cisco ISE nodes on release 3.3 and carries a cyber insurance policy.

CVE-2026-76460 is an authentication bypass in an ISE API, CVSS 10.0. Cisco published advisory cisco-sa-ISE-ABP-VNSW7Tn5 on 16 Sep 2026 with fixed patches (for 3.3, Patch 12) and said it was aware of active exploitation. CISA added the CVE to KEV the same day with a due date of 19 Sep 2026. Cisco lists no workaround and names access control lists as its mitigation.

SAMPLE policy clause (invented wording; read your own policy)

The insurer is not liable for loss arising from a vulnerability for which the software vendor published a fix more than 30 days before the loss, where the insured did not apply the fix or an equivalent control.

  1. 16 Sep 2026: the security lead asks whether the policy covers the exposure until the maintenance window. The answer is partial transfer at most: it moves some cost, leaves the exploitable API in place, and does not change the 19 Sep date the organization has adopted from CISA.
  2. 17 Sep to 23 Sep: access to the ISE nodes is limited with access control lists, a dated exception covers the gap between 19 and 23 Sep, and ISE 3.3 Patch 12 goes on both nodes on 23 Sep. The steps, owners and evidence for that sequence are in mitigate vs manage risk. The register records the response as Mitigate and notes the policy in a separate field as partial transfer of financial consequence.
  3. 16 Oct 2026: the sample clause's 30-day mark (16 Sep plus 30 days). A team that had treated the policy as the response would have been uninsured for this flaw from that day. The patch on 23 Sep, day 7, is well inside it.

The point of the case: the transfer instrument can itself require the fix. Read exclusions before writing "transferred" in a record.

The public sector case

SP 800-39 states that "the concept of risk transfer is less applicable in the public sector (e.g., federal, state, local governments) than the private sector, as liability of organizations is generally established by legislation or policy". For a federal system a policy purchase cannot be the stated response, and the authorizing official's acceptance is still needed. Risk sharing does remain available: SP 800-39 says it "may be a sharing of liability or a sharing of responsibility for other, adequate risk responses such as mitigation".

Transfer line for the exception record

Transfer or sharing (complete only if used)

  • What was shifted: liability / responsibility / financial consequence (choose, per SP 800-39)
  • To whom, and the instrument: policy or contract number, effective dates
  • What was not shifted: likelihood, outage, loss of customer trust (IR 8286)
  • Exclusions read: yes / no, and any that depend on patching
  • Response that still applies to the flaw: fix date, mitigation or dated exception (link the exception row)

Sources

Last reviewed