Checklist: the duties around a ransomware payment decision, from sanctions risk to suspicious activity reports and CIRCIA
Twelve steps for the people who decide whether a ransom is paid: OFAC’s sanctions risk and reporting advice, FinCEN’s suspicious activity report guidance for financial institutions, CIRCIA’s 24-hour payment report once a final rule takes effect, and a state ban on public-entity payments as an example.
Four sources, different weights
The sources behind these steps carry different legal weight. OFAC’s Updated Advisory on Potential Sanctions Risks for Facilitating Ransomware Payments (September 21, 2021) is explanatory and does not have the force of law, but the sanctions it describes do, and OFAC says civil liability is strict [1]. FinCEN Advisory FIN-2021-A004 (November 8, 2021) reminds financial institutions of their existing suspicious activity report duties and asks for specific SAR entries [2]. The Cyber Incident Reporting for Critical Infrastructure Act of 2022 requires covered entities to report ransom payments to CISA within 24 hours, but that duty takes effect only on the dates a final rule sets (6 U.S.C. 681b(a)(7)) [3]. As checked on November 14, 2026, CISA says it continues to work on the final rule and that reports are not required until it takes effect [4]. State laws differ; North Carolina’s G.S. 143-800 is used here as one example of a ban on public-entity payments [5].
How to use the list
The steps run from preparation, through the decision, to the reports that follow a payment. Each names the source and the part of it the step rests on; the OFAC advisory has no numbered sections, so its headings are named. The U.S. government strongly discourages paying ransoms [1]; this checklist does not recommend paying or refusing. Where a step is our suggestion, it says so. The owner shown under each step is a typical role, not one the sources name, unless the step says a source names it. This checklist explains public guidance and law; it is not legal advice, and counsel should be involved in any payment decision.
Moraph’s teams help organizations with work like this. See our solutions.
The checklist
Tick the steps as you go. The ticks are kept in this browser only; nothing is sent to us.
Board or chief executive, with the general counsel
Our suggestion. OFAC’s advisory says the U.S. government strongly discourages paying ransom or extortion demands and recommends focusing on defensive and resilience measures [1], so the decision needs a named owner before it arises.
CISO with the general counsel
Under the heading on contacting government agencies, OFAC strongly encourages victims to report to those agencies as soon as possible and to report attacks and payments to OCCIP [1]. Under the heading on cooperation, OFAC says a self-initiated, complete report made as soon as possible after discovery is a voluntary self-disclosure and a significant mitigating factor if a sanctions nexus is found [1].
Sanctions compliance with the incident response firm
OFAC’s advisory, under the heading on facilitating payments, says U.S. persons are generally prohibited from dealing with SDNs, other blocked persons and embargoed jurisdictions, and that civil penalties are based on strict liability, even without knowledge [1]. Screening each party this way is our suggestion for checking that.
General counsel
OFAC asks victims to contact it if there is any reason to suspect a sanctions nexus, and its licensing policy says license applications involving ransomware payments are reviewed case by case with a presumption of denial [1].
CISO
OFAC says meaningful steps to reduce extortion risk, such as offline backups, incident response plans, training, updated anti-malware software and authentication protocols, are a significant mitigating factor, as is full and ongoing cooperation, including giving law enforcement technical details, the ransom demand and payment instructions as soon as possible [1].
General counsel with procurement
FinCEN’s advisory says some incident response firms and insurers facilitate payments, and that depending on the facts this could be money transmission, which requires registration with FinCEN as a money services business and brings SAR obligations [2]. OFAC says such companies’ sanctions compliance programs should account for ransomware risk [1].
BSA officer
FinCEN’s advisory reminds institutions that a SAR is required for suspicious transactions of $5,000 or more ($2,000 for money services businesses, with one exception), that this can include ransom payments made by institutions that are victims, and that it covers attempted and successful transactions [2].
BSA officer
FinCEN’s advisory says it and law enforcement treat these as situations requiring immediate attention, points institutions to FinCEN’s Financial Institution Hotline before filing, asks for the key term CYBER-FIN-2021-A004 in SAR field 2 and the narrative, field 42 and 42z with the keyword ransomware, and cyber indicators in fields 44(a)-(j), (z), and restates the five-year retention requirement [2].
General counsel with the CISO
6 U.S.C. 681b(a)(2) requires a covered entity that makes a ransom payment to report it to CISA within 24 hours, even if the attack is not a covered cyber incident; (a)(3) requires supplemental reports, (a)(4) data preservation, and (a)(5)(A) allows one report when a payment precedes the 72-hour incident report. Section 681b(a)(7) says paragraphs (1) through (4) take effect on the dates the final rule sets, and (a)(5)(A) works through procedures that rule will set [3]. Preparing now is our suggestion.
CISO
CISA’s CIRCIA page says reporting under CIRCIA is not required until the final rule goes into effect and encourages organizations to share cyber incident information voluntarily before then [4].
Agency counsel with the CIO
G.S. 143-800(a) bars North Carolina state agencies and local government entities from paying or otherwise communicating with an entity that has encrypted data and offered to decrypt it for a ransom, and 143-800(b) requires them to consult the Department of Information Technology under G.S. 143B-1379 [5]. Other states’ laws differ; this is one example.
Spotted an error? Tell us and we will check it and correct the checklist where needed.