Moraph Predictions 2027: twelve calls for banks, health systems and public agencies

Twelve dated, testable calls on the rules, deadlines and data that bank, health system and public agency leaders face in 2027, each with a confidence level and a public test.

How the twelve calls were made

Each call below names one event or threshold, a date by which it will be known, and the public record that will settle it, as our methodology sets out. Most restate or sharpen a prediction already made in one of this year's outlooks and trend reports, at the same confidence, and none contradicts one. We left out the CIRCIA final rule, which our other pieces treat as close to even odds for 2027. The confidence levels are spread on purpose: a set of calls held at the same level says nothing about which ones we doubt.

Moraph's view

Moraph's view: four calls sit at 80% or above, two at 60% or below, and the rest between. If the high calls fail more than about one time in five, or both of the low calls come true, our calibration is off and we will say so when we score them in 2027 and 2028.

Clocks keep getting shorter

The time an organization has to act after something goes wrong keeps falling. A bank must notify its regulator no later than 36 hours after it determines a notification incident has occurred, and a bank service provider must tell its bank customers when an incident has materially disrupted or degraded, or is reasonably likely to, covered services for four or more hours [22]. CIRCIA sets 72 hours for a covered cyber incident and 24 hours for a ransom payment, though reporting is not required until CISA's final rule takes effect [23]. Our incident reporting clocks trend report traces that fall regulator by regulator.

Patching clocks have moved the same way. BOD 26-04, issued June 10, 2026, replaced BOD 22-01 and sets a three-day remediation window, with a forensic triage, for some known exploited vulnerabilities, with CISA bound to reassess the timelines once each fiscal year [20]. The catalog those deadlines hang on held 1,781 entries at version 2026.11.13, and CISA added 282 from January through October 2026 [19]. The known exploited vulnerabilities trend report sets out the full series; our call P11 is that the catalog passes 2,000 entries by September 30, 2027 [19].

Federal rules move from guidance into contracts

The second thread is where federal security expectations live. Executive Order 14412 does not regulate banks or hospitals; it works through procurement, giving the FAR Council 180 days to propose a rule that requires covered contractors to meet NIST's standards, including post-quantum ones, by December 31, 2030 [18]. The same order leaves Sector Risk Management Agencies a supporting role with no deadline [18], and the G7 Cyber Expert Group says its financial sector roadmap sets no regulatory expectations [21]. Hence two calls that point in different directions: a FAR proposed rule by mid-2027 (P10), and no post-quantum deadline from the federal banking agencies in 2027 (P12). The post-quantum migration outlook carries the detail.

Federal cloud follows the same route. FedRAMP stops accepting applications for new Rev5 certifications on June 11, 2027 [15], while the FedRAMP Authorization Act's sections in title 44 are struck five years after its December 23, 2022 enactment [14]. We expect Congress to act before that sunset (P8). The wider rewrite of the acquisition rules is slower: seven proposed rules under the FAR overhaul were in the Federal Register by November 16, 2026, and no final rule [17]. The federal cloud and cyber procurement outlook covers the FedRAMP 20x pipelines [15] and CMMC.

Moraph's view

Moraph's view: for companies that sell to the government, the dates that bind in 2027 are contract and authorization dates, not rule dates. For banks and health systems, the same federal standards arrive second-hand, through vendors who have to meet them to keep federal customers.

Banks: supervision by guidance, with the gaps left open

For banks, 2027 is a year of finishing guidance rather than writing rules. The agencies proposed new third-party risk management guidance on September 11, 2026 and plan to replace the 2023 guidance once it is final [1], with comments now due December 16, 2026 [2]. The OCC said in April 2026 that the agencies plan a request for information on model risk management and AI, including generative and agentic AI, which the revised guidance leaves out [3]. The one gap we expect to stay open is the NCUA's lack of authority over credit union vendors, and the agency says vendors typically decline its examination requests [5]. The third-party risk outlook and the AI governance outlook for financial services go further.

Health systems: firm API dates, a slow security rule, and data on where risk sits

In healthcare we expect dates that are already set to hold and the security rule to slip. CMS wrote in May 2026 that electronic prior authorization interfaces from Medicare Advantage, Medicaid, CHIP and Marketplace plans go live on January 1, 2027 [7], and the rule text sets the same date for Medicare Advantage organizations' Provider Access and Payer-to-Payer APIs [24] and Prior Authorization API [25]. The HIPAA Security Rule proposal, by contrast, is listed as a long-term action with final action estimated for July 2027 [9], and the only document under its RIN is the January 2025 proposal [10]. Information blocking penalties have been available since September 1, 2023 [13], yet OIG's page listed no resolved case when last updated [12]; we hold our call that one arrives in 2027 at barely better than even.

The breach data show where the risk sits. Across both lists on the HHS breach portal, Under Investigation and Archive, as exported on November 16, 2026, Hacking/IT Incident was the type of 79% of reports submitted in 2022, 81% in 2023, 83% in 2024, 81% in 2025 and 86% in 2026 through October 16 [11]. The health data breaches trend report traces that shift over a decade, and the healthcare cybersecurity outlook and the interoperability and prior authorization outlook cover the rules.

Moraph's view

Moraph's view: hacking has been the dominant type of large health breach for several years running, so we treat it as the base case for 2027, and the work it implies, vendor access, remote access and recovery, does not wait on the final Security Rule.

What would change these calls

Three events would move several calls at once: a CIRCIA final rule, which would set reporting duties across all three sectors; a federal statute on AI preemption or vendor oversight; and a change of course on FedRAMP's 2027 dates. Our cybersecurity rulemaking volume trend report tracks how much of this reaches the Federal Register. We will score every call here on its date, keep the wording as published, and show any correction to a basis with its date.

What this means for you

  • Banks and credit unions: Plan third-party programs against the proposed guidance, which the agencies intend to replace the 2023 guidance with once final [1], and expect no federal exam of credit union vendors in 2027, so contracts and due diligence carry the load [5].
  • Health systems: Use the payer APIs going live on January 1, 2027 [7] [24] [25] in prior authorization workflows, and keep security work on hacking and vendor access moving without waiting for a final Security Rule [9] [11].
  • Public agencies: Build cloud buying plans around FedRAMP's June 11, 2027 end of new Rev5 certifications [15] and the coming FAR proposal on post-quantum standards for contractors [18].
  • Vendors to all three sectors: Expect federal security standards to arrive through contract clauses, from the Executive Order 14412 FAR rule [18] to the remediation windows BOD 26-04 sets for agencies' own systems [20].

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

    The OCC, the Federal Reserve Board and the FDIC publish final third-party risk management guidance that replaces the 2023 interagency guidance on or before September 30, 2027.

    How we will check: A Federal Register notice or joint press release from the OCC, the Board and the FDIC, dated on or before September 30, 2027, announcing final third-party risk management guidance and rescinding the 2023 interagency guidance.

    Basis: The agencies proposed the guidance on September 11, 2026 and said they plan to rescind and replace the existing guidance once it is final [1]; the comment period was extended to December 16, 2026 [2].

  2. P2 By Confidence 65% Open

    The OCC, the Federal Reserve Board and the FDIC publish a request for information on model risk management that covers banks' use of generative or agentic AI on or before June 30, 2027.

    How we will check: A Federal Register notice or joint release from the three agencies, dated on or before June 30, 2027, requesting information on model risk management that addresses generative or agentic AI.

    Basis: In April 2026 the OCC said the three agencies plan to issue such a request in the near future and that the revised guidance leaves generative and agentic AI out of scope [3]; no such request appeared in the Federal Register between April 1 and November 16, 2026 [4].

  3. P3 By Confidence 90% Open

    No federal law that gives the NCUA authority to examine credit unions' third-party vendors or credit union service organizations is enacted on or before December 31, 2027.

    How we will check: Congress.gov lists no public law enacted on or before December 31, 2027 that grants the NCUA examination authority over third-party service providers or credit union service organizations.

    Basis: The NCUA calls its lack of vendor authority a regulatory blind spot, reports that vendors typically decline its examination requests, and asked Congress to restore the power [5]; H.R. 10230, introduced September 2, 2026, was referred to the Committee on Financial Services [6].

  4. P4 By Confidence 80% Open

    CMS does not postpone, or announce enforcement discretion for, the January 1, 2027 compliance date for Medicare Advantage organizations' Provider Access, Payer-to-Payer and Prior Authorization APIs on or before March 31, 2027.

    How we will check: No final rule, interim final rule or CMS enforcement discretion notice published between November 16, 2026 and March 31, 2027 delays or suspends enforcement of those API requirements for Medicare Advantage organizations.

    Basis: Under CMS-0057-F, the current text of 42 CFR 422.121 requires Medicare Advantage organizations to run the Provider Access and Payer-to-Payer APIs beginning January 1, 2027 [24], and 42 CFR 422.122 sets the same date for the Prior Authorization API [25]; CMS wrote in May 2026 that electronic prior authorization interfaces will go live on January 1, 2027 [7], and its early adopter release the same month spoke of industry readiness ahead of that deadline [8].

  5. P5 By Confidence 70% Open

    HHS does not publish a final HIPAA Security Rule under RIN 0945-AA22 in the Federal Register on or before July 31, 2027.

    How we will check: A Federal Register search for RIN 0945-AA22 shows no document of type Rule published on or before July 31, 2027.

    Basis: The 2026 Unified Agenda lists the rule as a long-term action with final action estimated for July 2027 [9]; the only Federal Register document under the RIN is the January 6, 2025 proposed rule [10].

  6. P6 By Confidence 80% Open

    Hacking/IT Incident is the Type of Breach on at least 80% of reports with a 2027 Breach Submission Date on the HHS OCR breach portal.

    How we will check: On or after March 31, 2028, export the Under Investigation and Archive lists from the HHS OCR breach portal as CSV, keep rows whose Breach Submission Date falls in 2027, and divide rows with Type of Breach exactly "Hacking/IT Incident" by all such rows. Right if 80% or more.

    Basis: Across both of the portal's lists as exported on November 16, 2026, Hacking/IT Incident was the Type of Breach on 79% of reports submitted in 2022, 81% in 2023, 83% in 2024, 81% in 2025 and 86% in 2026 through October 16 [11]; the threshold has been met in each of the last four years, by one point in 2025.

  7. P7 By Confidence 55% Open

    HHS OIG publicly announces at least one resolved information blocking civil money penalty or settlement with a health IT developer, health information network or health information exchange on or before December 31, 2027.

    How we will check: OIG's information blocking page or an OIG or HHS press release, dated on or before December 31, 2027, describes a resolved information blocking penalty or settlement with a developer, network or exchange.

    Basis: The penalty provisions took effect September 1, 2023, with penalties of up to $1 million per violation [13]; OIG's information blocking page, last updated May 27, 2026, lists no resolved penalty or settlement [12].

  8. P8 By Confidence 70% Open

    Congress enacts a law that extends, removes or replaces the five-year sunset of the FedRAMP Authorization Act on or before December 23, 2027.

    How we will check: A public law enacted on or before December 23, 2027 amends or repeals the sunset in section 5921(d) of Public Law 117-263, or re-enacts 44 U.S.C. 3607 to 3616.

    Basis: The Act, enacted December 23, 2022, strikes sections 3607 through 3616 of title 44 five years after enactment [14], and FedRAMP's own rules publish the Act as their legal authority [14] and end new Rev5 certifications on June 11, 2027 [15].

  9. P9 By Confidence 60% Open

    The FAR Council publishes a final rule for FAR Case 2026-001, the overhaul of FAR parts 1, 2, 4, 33, 39, 40 and 53, on or before December 31, 2027.

    How we will check: A final rule for FAR Case 2026-001 (RIN 9000-AO86) appears in the Federal Register on or before December 31, 2027.

    Basis: The proposed rule was published June 23, 2026 with comments closing July 23, 2026 [16]; as checked on November 16, 2026, the Federal Register held seven proposed rules and no final rule under the overhaul's title [17].

  10. P10 By Confidence 65% Open

    The FAR Council publishes in the Federal Register the proposed rule required by section 6(c) of Executive Order 14412, requiring covered contractors to comply with NIST FIPS including post-quantum standards, on or before June 30, 2027.

    How we will check: A Federal Register search shows a proposed rule from the FAR Council (DoD, GSA and NASA) citing Executive Order 14412 and post-quantum cryptography, published on or before June 30, 2027.

    Basis: Section 6(c) of the order, signed June 22, 2026, gives the FAR Council 180 days to publish the proposed rule, with contractor compliance by December 31, 2030 [18]; as checked on November 16, 2026, the FAR Council's other rulemaking under the overhaul had produced seven proposed rules and no final rule [17], so we allow for the deadline slipping by more than six months.

  11. P11 By Confidence 75% Open

    CISA's Known Exploited Vulnerabilities catalog passes 2,000 entries on or before September 30, 2027.

    How we will check: Open the KEV JSON feed on or after September 30, 2027 and count records with a dateAdded on or before 2027-09-30, or read the count of the last catalog version released by that date. Right if 2,000 or more.

    Basis: The catalog held 1,781 entries at version 2026.11.13, and CISA added 282 entries from January through October 2026, about 28 a month [19]; BOD 26-04 directs CISA to update the catalog at the pace it identifies new exploited vulnerabilities [20].

  12. P12 By Confidence 85% Open

    None of the OCC, the Federal Reserve Board or the FDIC publishes a final rule that sets a post-quantum cryptography migration deadline for banks on or before December 31, 2027.

    How we will check: A Federal Register search for final rules from these three agencies published on or before December 31, 2027 that mention post-quantum cryptography and set a compliance date. Right if there are none.

    Basis: Executive Order 14412 does not name the financial sector and sets no deadline for Sector Risk Management Agencies [18]; the G7 Cyber Expert Group says its financial sector roadmap does not set guidance or regulatory expectations [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.

  • predictions
  • third-party risk
  • model risk
  • HIPAA Security Rule
  • prior authorization
  • information blocking
  • FedRAMP
  • FAR
  • post-quantum cryptography
  • KEV
  • incident reporting