Skip to content
TECH CEO Daily

Senate passes health care cybersecurity bill that would mandate MFA and encryption

The bipartisan bill would have HHS write minimum security rules for providers, health plans and their vendors, add grants for small providers and head to the House next.

By · Editor

· 3 min read · Fact-checked

The 60-second brief

  • 1The Senate passed the Health Care Cybersecurity and Resiliency Act by unanimous consent; the House must still act.
  • 2HHS would update HIPAA rules to require multifactor authentication, encryption of patient data and penetration testing.
  • 3New rules would take effect 36 months after enactment; grants target nonprofit hospitals, rural clinics and community health centers.

The news

The US Senate has passed the Health Care Cybersecurity and Resiliency Act by unanimous consent, SecurityWeek reported on October 5. The bipartisan health care cybersecurity bill would require health care organizations and their vendors to adopt minimum safeguards, including multifactor authentication and encryption.

The bill, S. 3315, is led by Sen. Bill Cassidy (R-La.), who chairs the Senate Health, Education, Labor and Pensions (HELP) Committee, with Sens. Mark Warner (D-Va.), John Cornyn (R-Texas) and Maggie Hassan (D-N.H.). The HELP Committee advanced it 22-1 on February 26, with only Sen. Rand Paul (R-Ky.) opposed, CyberScoop reported. A congressional tracking site lists the Senate passage date as September 30; SecurityWeek did not give a date. The bill now goes to the House.

The core change is in the version the committee reported on March 23. It directs the Department of Health and Human Services (HHS) to update the HIPAA Security Rule, the federal rule for protecting electronic patient data, so that providers, health plans and their business associates adopt minimum risk-based practices. Those include multifactor authentication, encryption of protected health information, and monitoring that includes penetration testing, which means hiring testers to try to break in. The standards would be based on frameworks such as NIST's Cybersecurity Framework and health sector performance goals, and would take effect 36 months after the law is enacted.

The text also lets HHS award grants of up to three years to community health centers, Indian Health Service facilities, nonprofit hospitals and rural health clinics for hiring security staff, moving to cloud systems, risk assessments and incident response plans. It authorizes such sums as may be necessary for fiscal years 2026 through 2030 but names no dollar amount. HHS would have to issue cybersecurity guidance for rural providers within a year, weigh documented security practices and investments when setting HIPAA fines, and convene a working group with agencies including CISA, the SEC, the FBI and the FTC to cut duplicative incident reporting.

When the committee advanced the bill in February, Cassidy said there were more than 730 cyber breaches affecting over 270 million Americans the previous year, according to CyberScoop.

The attacks have not let up. SecurityWeek reported on October 5 that Clover Health, of Jersey City, New Jersey, notified HHS of a breach affecting 138,677 people, and AngMar Management Services, of Mansfield, Texas, reported one affecting 126,196, a breach claimed by the Interlock ransomware group. The Record reported the same day that a ransomware attack made University of Illinois Chicago College of Medicine systems temporarily unavailable; the university said patient care at UI Health was not affected.

The numbers

HELP Committee vote, Feb. 26
22-1
Time to comply after enactment
36 months
Maximum grant period
3 years
Grant funding authorized
Such sums as necessary, FY2026-2030
People affected, Clover Health breach
138,677
People affected, AngMar breach
126,196

Why CEOs should care

For CISOs and CIOs at hospitals, clinics and health plans, the bill turns common best practices into likely legal requirements. Run a gap check now: where is multifactor authentication still missing, which systems hold unencrypted patient data, and when did an outside team last run a penetration test? A 36-month clock sounds long, but replacing legacy clinical systems that cannot support modern logins or encryption often takes that long.

Vendors are in scope too. Because the requirements would cover business associates, the billing, IT, analytics and software firms that handle patient data for health systems should expect customers to ask for proof of these controls in contracts. Technology sellers into health care should map their products against the bill's list before procurement teams do it for them.

For CFOs and boards, two provisions matter. The grants are authorized but not funded, so do not plan budgets around them until Congress appropriates money. And the bill would have HHS consider documented security practices and investments when setting HIPAA fines, which makes keeping clear records of security spending and controls worth the effort.

The bigger picture

Health care remains a frequent target. SecurityWeek noted that the Change Healthcare attack exposed more than 190 million records. The bill's working group is aimed at a different burden: overlapping federal and state rules that can require several reports for the same incident.

The bill is not law. The House must pass it, and the final text could differ from the committee version described here.

What’s next

Watch for House action on the Senate-passed bill and whether the House changes the 36-month timeline or the list of required controls. If it becomes law, HHS would then have to write the updated HIPAA Security Rule, which is where specific technical requirements would be set.

What “Fact-checked” means

Fact-checking means testing a story’s facts against the evidence before it is published. This story went through at least two separate checks before this version was published.

What we checked
Its names, figures, dates, job titles, quotes and who said what were checked against the story’s sources, including its main source where it could be opened. The headline was checked for accuracy and overstatement.
How
A first check reviewed the whole story. If it passed, a second, skeptical check went back to the sources to look for mistakes in the most important facts. If a check flagged the story, it was edited to fix the problems found, and a separate re-check then reviewed the whole story again.
Who
The checks are made by our newsroom, as steps kept separate from the writing, under rules set by our editor, . A story the checks still flag is held for the editor, who decides whether it is fixed, published or dropped.
If something is wrong
“Fact-checked” does not mean error-free. If a material error is found after publication, we correct the story and add a note saying what changed. Report an error

How we fact-check →

Bill CassidyHHSCISAHIPAAHealth care cybersecurity

Written by

Editor · Technology & Business Writer

Hussein is a writer and business technology enthusiast focused on the intersection of technology, entrepreneurship, finance, artificial intelligence, and digital innovation.

CoversAICybersecurityBig TechSaaSStartupsFintech

About this story. Researched from primary sources whenever they are available and fact-checked before publication.

Published by Tech CEO Daily, an independent publication. Masthead · Editorial standards

Follow Tech CEO Daily on Facebook for the day’s top stories in your feed.

Free newsletters

The technology briefing for people running businesses.

Daily, weekly, bi-weekly or monthly. You choose.

How often

The Daily Brief · Monday to Saturday, 7 a.m. ET

Free forever. One click to unsubscribe. We never sell your email.