July 8, 2024 By Jonathan Reed 3 min read

The FBI, CISA and NSA all strongly advise against organizations making ransomware payments if they fall victim to ransomware attacks. If so, why not place a ban on paying ransomware demands?

The topic came up at a recent Oxford Cyber Forum. Jen Easterly, Director of CISA, commented on the issue, saying, “I think within our system in the U.S. — just from a practical perspective — I don’t see it happening.” It’s unlikely this was a purely spontaneous remark as the issue of ransomware is top of mind for all cyber professionals, especially the director of CISA. For now, it looks like making ransomware payments a punishable offense is not going to happen.

Even more telling is that Easterly’s answer was made during an interview with Ciaran Martin, the former head of the U.K.’s National Cyber Security Centre. Earlier this year, Martin had called for a ban on all ransomware payments in an article she wrote for The Times newspaper.

So, should paying ransomware be banned or not?

Banning ransomware payments: More harm than good?

The Ransomware Task Force for the Institute for Security and Technology has also chimed in on the topic. The task force stated that placing a ban on ransomware payments in the U.S. at the current time will make it worse for victims, society and the economy. Small businesses typically cannot withstand a lengthy business disruption and might go out of business after a ransomware attack.

Additionally, if a ban was enforced, it could hamper the wider response to ransomware threats. If companies faced penalties for paying, they might be tempted to make ransomware payments secretly. This means accurate data about ransomware variants and threat intelligence would suffer.

Explore ransomware protection solutions

Fake ransomware rescue services

Other obstacles to a ransomware payment ban include fake “data recovery” firms. These scammers claim to be able to recover stolen data or crack encryption. But in reality, the alleged rescuers negotiate with ransomware gangs on the side, essentially paying the ransom and then charging the victims a fee. If ransomware payments were banned, these shady operations would likely increase.

Fight the good fight

Some say banning ransomware payments outright could be thought of as capitulation. It sends the message that the security community has no other means to thwart ransomware attacks. Instead, the federal government is mandating the reporting of cyber incidents, such as with the recent Cyber Incident Reporting for Critical Infrastructure Act (CIRCIA). By improving ransomware reporting rates, security teams can learn more about how attackers operate and share threat intelligence. This type of digital solidarity is believed to be more effective than trying to face these threats alone.

Law enforcement efforts should also be supported and ramped up in response to the ongoing ransomware threats. The LockBit ransomware-as-a-service gang is one example of a big win that brought intruders to justice.

Plus, there are efforts such as CISA’s pre-ransomware notification initiative, which aims to reduce risk by alerting organizations of early-stage ransomware activity. The initiative generated more than 1,200 pre-ransomware notifications in 2023.

The U.S. government also champions secure-by-design. At Oxford Cyber, Easterly said, “I do think we’ve made a difference, but I don’t think we’re going to make ransomware a shocking anomaly without successful implementation of a Secure-by-Design campaign,” said Easterly. “We cannot expect businesses that don’t have huge security teams to be able to secure that infrastructure unless that technology comes to them with dramatically reduced numbers of vulnerabilities.”

Setting priorities against ransomware

It’s no secret what the U.S. government feels is the best course for fighting ransomware—the plans are being laid out explicitly. They include stricter incident reporting standards, continued law enforcement efforts, shared intelligence, collaborative efforts and secure-by-design. For now, penalties for paying ransom aren’t part of the official game plan.

However, many entities, including IBM, strongly discourage paying ransomware. Instead, follow best practices and check out IBM’s Definitive Guide to Ransomware.

More from News

The rising threat of cyberattacks in the restaurant industry

2 min read - The restaurant industry has been hit with a rising number of cyberattacks in the last two years, with major fast-food chains as the primary targets. Here’s a summary of the kinds of attacks to strike this industry and what happened afterward. Data breaches have been a significant issue, with several large restaurant chains experiencing incidents that compromised the sensitive information of both employees and customers. In one notable case, a breach affected 183,000 people, exposing names, Social Security numbers, driver's…

DHS awards significant grant to improve tribal cybersecurity

4 min read - The Department of Homeland Security (DHS) has awarded $18.2 million in grants through the Tribal Cybersecurity Grant Program to boost cybersecurity defenses among Native American Indian Tribes. The program takes a big step in addressing the unique digital threats faced by tribal communities — a dedicated effort to improve cybersecurity infrastructure across these regions. The $18.2 million grant is just one component of DHS's broader strategy to enhance national cybersecurity. Administered by the Federal Emergency Management Agency (FEMA) in partnership…

ONCD releases request for information: Open-source software security

3 min read - Open-source software is a collective partnership across the development community that requires both private and public buy-in. However, securing open-source software can be tricky. With so many different people working on the coding, security measures are often overlooked, increasing the chances that a vulnerability will fall through the cracks and be exploited. The Open-Source Software Security Initiative (OS31) aims to provide governance over open-source security processes. After the Log4Shell vulnerability, securing open-source software became a top priority for the federal…

Topic updates

Get email updates and stay ahead of the latest threats to the security landscape, thought leadership and research.
Subscribe today