Hospital cybersecurity performance goals: from voluntary to required, and when

HHS's goals for hospitals are still voluntary. CMS has asked questions, added one hospital attestation and dropped a clinician one, budgets dropped the payment plan, and the payment lever now sits in a Senate bill that would bite in FY 2031.

When HHS announced its health sector cybersecurity performance goals (CPGs) in December 2023, it said what it hoped would come next: money for hospitals first, then consequences [2]. Three years on, the goals have not moved from voluntary to required. This outlook follows only that question: which federal levers could turn the CPGs into a condition of participation or of payment, how far each has moved as checked on November 16, 2026, and what that implies for 2027 and 2028. The wider rule set facing health systems, including the HIPAA Security Rule proposal, CIRCIA and OCR enforcement, is covered in our healthcare cybersecurity outlook.

What the goals are, and the route HHS sketched

HHS describes the CPGs as a voluntary subset of cybersecurity practices that healthcare organizations, and healthcare delivery organizations in particular, can prioritize [1]. CMS's own summary lists 10 essential goals, such as multifactor authentication, email security and mitigating known vulnerabilities, and 10 enhanced goals, such as asset inventory, network segmentation and centralized log collection [11].

HHS's December 2023 strategy paper set out a route from voluntary to binding [2]. It said HHS would work with Congress for new authority and funding to support hospital investment and, in the long term, to enforce new requirements through financial consequences for hospitals [2]. It envisioned an upfront investments program for high-need providers to meet the essential goals and an incentives program for all hospitals to adopt the enhanced goals [2]. With additional authorities and resources, it said, HHS would propose building the CPGs into existing regulations and programs, and CMS would propose new cybersecurity requirements for hospitals through Medicare and Medicaid [2].

The FY 2025 budget priced the payment route, and later budgets dropped it

HHS's FY 2025 Budget in Brief turned that route into a legislative proposal. It would have paid $800 million from the Medicare Hospital Insurance Trust Fund over FY 2027 and FY 2028 to approximately 2,000 high-needs hospitals, then, from FY 2029, applied penalties within the Promoting Interoperability Program to hospitals that fail to adopt essential cybersecurity practices [7]. Those penalties could reach 100 percent of the annual market basket increase, with up to 1 percent off the base payment from FY 2031 [7]. A further $500 million would have supported enhanced practices in FY 2029 and FY 2030, and from FY 2031 CMS could have added enhanced practices to the required list [7]. Critical access hospitals would have faced a reduction of up to one percent [7]. The budget scored the package at $1.3 billion over 10 years [7].

The proposal did not return. The FY 2026 Budget in Brief mentions cybersecurity for HHS's own systems and HIPAA administration, with no hospital incentive or penalty [8]. The FY 2027 Budget in Brief is the same: its cybersecurity items cover the department's own program, Indian Health Service systems and device research, not Medicare hospital payment [9].

What CMS has done in its own rules

CMS's first references to the goals were promises to think about them. In the FY 2025 hospital payment rule, it noted that HHS had published recommended cybersecurity performance goals and said it would consider how the Medicare Promoting Interoperability Program could promote cybersecurity best practices, to inform potential future rulemaking proposals [3] [4]. It said the same about clinicians in the CY 2025 physician fee schedule rule [5]. As checked on November 16, 2026, a Federal Register search returns five CMS documents with the phrase, and the most recent is the April 14, 2026 proposed rule carrying a request for information [6].

That request for information summarized the strategy's four pillars and the CPGs, then asked whether CMS should propose effective cybersecurity practices as regulatory requirements within its purview, how clearinghouse enrollment affects resilience, and what barriers small and rural practices face [11]. It is a set of questions, not a proposal.

The one binding CMS step is narrower than the CPGs. The FY 2026 hospital payment rule requires eligible hospitals and critical access hospitals to attest "yes" to conducting security risk management, in addition to the existing security risk analysis attestation, beginning with the CY 2026 EHR reporting period [10]. That attestation sits inside a payment program: the same rule reduces the update by three-quarters of the applicable percentage increase for hospitals not considered meaningful EHR users [10].

Since then CMS has eased, not added. The FY 2027 hospital payment rule, effective October 1, 2026, finalized adding cyberattacks to the extreme and uncontrollable circumstances policy of the CJR-X episode model, and a text search of the rule finds no change to the Security Risk Analysis measure [12]. The CY 2027 physician fee schedule rule removed the Security Risk Analysis measure for MIPS eligible clinicians beginning with the CY 2027 performance period, saying the removal weakens no cybersecurity requirement because the measure derives from the HIPAA Security Rule, which still applies [13]. That rule also noted that the HIPAA Security Rule proposal had not been finalized [13], and the Federal Register still lists only the January 6, 2025 proposed rule under its identifier [15]. A search for CMS documents since January 1, 2024 that cite the hospital conditions of participation in 42 CFR part 482 and mention cybersecurity returns only the FY 2025 hospital payment proposed and final rules [14].

Moraph's view

CMS's direction since 2025 points away from a CPG mandate it writes itself. It has used the payment rules to ask questions, to add one attestation that restates the HIPAA risk management duty, and then to remove the clinician version of that attestation to cut reporting burden. A condition of participation built on the CPGs would need CMS to decide that hospital cybersecurity is a health and safety standard; nothing on the record since the strategy paper shows that decision being prepared. We expect the hospital Security Risk Analysis attestation to be the high-water mark of CMS cybersecurity requirements through 2028.

Congress holds the payment lever

The strategy paper tied financial consequences to new authority from Congress [2], and the bills that would provide it follow the FY 2025 budget's design closely. S. 5218, the Health Infrastructure Security and Accountability Act of 2024, would have amended Medicare hospital payment to fund essential practices with $800 million in FY 2027 and FY 2028 and enhanced practices with $500 million in FY 2029 and FY 2030 [16]. It was referred to the Finance Committee on September 25, 2024 and went no further [17].

Its successor, S. 5443, was introduced on September 17, 2026 and referred to the Finance Committee [20]. It keeps the structure and moves each date by two years: $800 million in FY 2029 and FY 2030, $500 million in FY 2031 and FY 2032, attestation to essential practices from FY 2031 and to enhanced practices from FY 2032 [19]. Penalties for hospitals that do not attest would start at a 0.25 percentage point cut to the annual update in FY 2031 and rise to a 1.0 percentage point cut plus a 1.0 percent cut to the base operating DRG payment from FY 2035 [19]. The bill also names the CPGs directly: until new minimum standards take effect, the annual independent audits it would require of covered entities and business associates would assess compliance with HHS's sector-specific performance goals [19].

The bill that has moved is a different kind. S. 3315, the Health Care Cybersecurity and Resiliency Act of 2026, passed the Senate by unanimous consent on September 30, 2026 and was held at the desk in the House on October 5, 2026, the latest action in its status record [22]. Its section 8 would require HHS to update the HIPAA security regulations so that covered entities and business associates adopt minimum risk-based practices, including multifactor authentication, encryption and penetration testing, based on national frameworks, the Health Sector Coordinating Council's healthcare and public health cybersecurity performance goals and CISA's health care-specific goals [21]. The updated regulations would take effect 36 months after enactment [21]. None of its twelve sections changes Medicare payment or the conditions of participation [21]. Its 2024 predecessor, S. 5390, was referred to committee on November 21, 2024 and did not advance [18].

Routes from voluntary goals to binding requirements, as checked on November 16, 2026
RouteVehicleStatusEarliest binding date in the text
Medicare payment penaltiesS. 5443 [19]Referred to the Finance Committee [20]FY 2031 update [19]
HIPAA minimum practices drawing on sector goalsS. 3315 [21]Passed the Senate; held at the desk in the House [22]36 months after enactment [21]
HIPAA Security Rule updateProposed rule, January 6, 2025 [15]Not finalized [15] [13]None while it is a proposal
Hospital conditions of participationNone proposed [14]Request for information only [11]None
Promoting Interoperability attestationFY 2026 payment rule [10]In force from the CY 2026 reporting period [10]Already binding, but on risk analysis and risk management, not the CPGs [10]

Reading the timeline

Each route has its own clock, and none of them runs fast. A payment penalty needs a statute, and the only bill that would create one starts penalties in FY 2031 [19]. A HIPAA mandate under S. 3315 would bind 36 months after enactment [21], and the bill dies with the 119th Congress unless the House acts on it [22]. A condition of participation needs CMS to propose one, and as of November 16, 2026 it has not [14].

Moraph's view

Our answer to the question is no, not before 2029, and probably not as a condition of participation at all. The likeliest binding form of the CPGs is indirect: a HIPAA rule, written under the current proposal or under a statute like S. 3315, that names several of the same controls. If S. 3315 or a successor were enacted in 2027, its regulations would bind in 2030. A Medicare payment link needs a Finance Committee bill to pass, and HHS has not asked for one in the two budgets since FY 2025. We would revise this view if CMS published a proposed rule citing the CPGs as a requirement, or if a payment provision rode on a larger Medicare package.

What to do with voluntary goals in the meantime

The goals already carry weight without a mandate. CMS asks hospitals to attest to risk analysis and risk management every year [10], and the bills in both directions use the CPGs or sector goals as their reference point [19] [21]. A hospital that can show which essential goals it meets, with evidence, has the record each route would ask for.

What this means for you

  • Hospital CISOs and compliance leads: Map controls to the 10 essential and 10 enhanced goals now [11], and keep that map next to the security risk analysis and risk management records CMS already requires hospitals to attest to [10]. Both pending bills reference the goals or sector goals [19] [21].
  • Health system finance leaders: Do not budget for the $800 million upfront funding: it exists only in a bill referred to committee [19] [20], and the last two HHS budget summaries do not request it [8] [9]. Track S. 5443's penalty schedule, which would start in FY 2031, as a long-range risk [19].
  • Critical access and rural hospitals: CMS asked in 2026 what barriers small and rural providers face [11]; the essential goals are the floor every funding design so far has paid for first [2] [7]. S. 3315 would also require HHS guidance on rural cybersecurity readiness [21].
  • Clinician groups in MIPS: The Security Risk Analysis measure leaves MIPS from the CY 2027 performance period, and CMS said the removal weakens no cybersecurity requirement because the HIPAA Security Rule still applies [13]; keep the analysis current for HIPAA, not for the score.

Moraph predictions

Every prediction is Moraph's view, not a fact. Each has a date, a confidence level (70% means we expect to be wrong about three times in ten) and a test anyone can apply. We score them on this page when the date comes and never remove one. How we make and score predictions.

  1. P1 By Confidence 70% Open

    S. 3315, the Health Care Cybersecurity and Resiliency Act of 2026, will not become law on or before January 3, 2027, when the 119th Congress ends.

    How we will check: The S. 3315 bill status record on GovInfo or congress.gov shows no action "Became Public Law" dated on or before January 3, 2027.

    Basis: The bill passed the Senate on September 30, 2026 and was held at the desk in the House on October 5, 2026, with no later action recorded [22]; its 2024 predecessor did not advance past referral [18].

  2. P2 By Confidence 85% Open

    No federal law enacted on or before December 31, 2028 will reduce Medicare hospital payments for failing to adopt cybersecurity practices.

    How we will check: No public law enacted on or before December 31, 2028 amends section 1886 of the Social Security Act to reduce payments to hospitals that do not adopt or attest to cybersecurity practices.

    Basis: The only bill with such penalties, S. 5443, was referred to the Finance Committee [20]; its 2024 version did not advance [17]; and the FY 2026 and FY 2027 HHS budget summaries do not request the authority [8] [9].

  3. P3 By Confidence 80% Open

    The FY 2028 IPPS/LTCH PPS final rule will not require hospitals in the Medicare Promoting Interoperability Program to attest to adopting HHS's cybersecurity performance goals.

    How we will check: The FY 2028 IPPS/LTCH PPS final rule, published in the Federal Register on or before September 30, 2027, adds no required Promoting Interoperability measure or attestation based on the HHS cybersecurity performance goals; if no such final rule is published by then, the prediction is scored right.

    Basis: CMS has said since 2024 only that it would consider how the program could promote cybersecurity practices [3] [4]; its 2026 step was a request for information [11]; the FY 2027 rule made no change to the Security Risk Analysis measure [12]; and CMS removed the clinician version of that measure [13].

  4. P4 By Confidence 75% Open

    HHS's Budget in Brief for FY 2028 will not propose Medicare incentive payments or penalties tied to hospital cybersecurity practices.

    How we will check: An HHS Fiscal Year 2028 Budget in Brief published on or before December 31, 2027 contains no Medicare proposal paying or penalizing hospitals based on cybersecurity practices; if none is published by then, the prediction is scored right.

    Basis: The FY 2025 budget proposed such a program [7]; the FY 2026 and FY 2027 budget summaries do not [8] [9].

  5. P5 By Confidence 85% Open

    HHS's cybersecurity performance goals will still be voluntary on December 31, 2027.

    How we will check: On December 31, 2027, the HHS performance goals page (or its successor on an HHS site) describes the goals as voluntary, and no HHS or CMS final rule published by then makes them mandatory.

    Basis: The page describes them as voluntary as checked on November 16, 2026 [1]; no CMS rule makes them a condition of participation [14]; and the bills that would bind similar practices would do so years after enactment [19] [21].

Facts on this page link to their sources. Text marked "Moraph's view", and every prediction, is our own analysis, not a fact or advice. Methodology.

Spotted an error? Tell us and we will check it and correct the piece where needed.

  • HHS cybersecurity performance goals
  • CMS
  • conditions of participation
  • Promoting Interoperability
  • Medicare payment
  • S. 3315
  • S. 5443
  • hospital cybersecurity