Insights

Corrections

Every correction made to Moraph Insights, with its date and what changed.

How corrections work

When we find or are told about an error, we check it against the primary source and correct the page. The page keeps a dated note saying what changed, and the correction is listed here. How we source and check facts is on Editorial standards.

Spotted an error? Tell us through our contact page, naming the page and the fact.

Comparison tables, sector and topic pages, explainers, checklists and data briefs

  1. · Explainer · OMB M-26-14: the federal logging memo that replaced M-21-31, explained

    Added that M-26-14 rescinded M-21-31, where the text mentions log stores built to M-21-31’s retention periods, so the older memorandum no longer reads as in force.

  2. · Checklist · Checklist: meeting OMB M-26-14 logging deadlines after CISA’s reference architecture

    Added that M-26-14 rescinded M-21-31, where the checklist suggests reviewing contracts that cite M-21-31’s event logging tiers, and named M-26-14 as the memorandum that applies to systems third parties operate.

  3. · Sector and topic page · Healthcare: economics and procurement

    The Electronic Prior Authorization point said a hospital attests to a request made through a Prior Authorization API "using data from" certified EHR technology. The FY 2027 IPPS final rule changed that wording to "using CEHRT"; the point now says so.

  4. · Explainer · OPM’s Annual Staffing Plan rule (5 CFR part 250), explained

    Source 3 retitled: the OMB address for Circular No. A-11 now serves the November 2026 edition (Transmittal Memorandum No. 100 of November 6, 2026), not the August 2025 edition the title named. The point it supports, that Part 6 sets the strategic planning and budget formulation cycle, is unchanged.

  5. · Explainer · OMB M-25-21 on federal AI use, and the “Super Intelligence” wording of Executive Order 14434, explained

    The status section named M-26-19 (September 10, 2026) as the most recent entry on OMB’s memoranda page. The page now lists a later entry, M-27-01 (October 23, 2026), so the section now names it. No entry on the page is titled as rescinding or replacing M-25-21.

  6. · Explainer · The NIST AI Risk Management Framework and its Generative AI Profile, explained

    Removed an unsourced statement that the four functions and current and target profiles are the parts of the AI RMF most organizations use; they are now described as the framework’s core structure.

  7. · Data brief · Large health data breaches reported to HHS in 2026: slightly fewer reports, a larger hacking share

    Source 1 and the dataset link updated: the portal address we cited (breach_report.jsf) now redirects to a new breach portal front page, and the list of HIPAA breach reports is at breach_report_hip.jsf. The method note now says the portal labels the business associate column in its list and that the CSV export gives that column no readable header, instead of saying the label appears only in the expanded view and the header is blank. A fresh export on November 14, 2026 gave the same 718 and 7,374 reports and the same figures.

  8. · Comparison table · Security frameworks compared: who must use them and how they are checked

    The SP 800-171 row's DFARS cell quoted only the codified text of DFARS 252.204-7012(b)(2) (the SP 800-171 in effect when the solicitation is issued). It now cites Class Deviation 2026-O0025, Revision 3, whose version of the clause, which contracting officers must use, names SP 800-171 Revision 2.

  9. · Comparison table · Security frameworks compared: who must use them and how they are checked

    The CISA CPGs row said the goals are for critical infrastructure entities of all sizes; CISA's page does not say that. It now says what the page says: a baseline broadly applicable across critical infrastructure, aimed at helping small- and medium-sized organizations.

  10. · Comparison table · Medicare and Medicaid enrollment revalidation and change reporting deadlines compared

    Added a row for the CY 2027 home health final rule (91 FR 72022, November 9, 2026), which makes every revocation for failure to report a change take effect the day after the reporting deadline, and rewrote the method to describe the November 9, 2026 amendments (including 424.516(f)(3) and (f)(4)) instead of saying none of them changed what the table shows.

  11. · Comparison table · Prohibited technology clauses in federal contracts: Kaspersky, section 889, TikTok and FASCSA orders

    Added the FAR Council’s June 23, 2026 proposed rule (FR Doc. 2026-12559), which would move these clauses into proposed FAR 52.240-3 in FAR part 40 with one 72-hour report, as a row clearly marked as a proposal.

  12. · Checklist · Checklist: getting an agency ready for OPM’s staffing-plan rule

    The OMB Circular A-11 source was listed as the August 2025 edition. The file at that address is now the November 2026 edition (Transmittal Memorandum No. 100, November 6, 2026), so the source title now names that edition. Part 6, which the checklist cites, is in the current edition.

  13. · Checklist · Checklist: ADA Title II web and mobile accessibility for state and local governments

    Step 10 said section 35.107 requires an entity to publish the responsible employee’s name, office address and telephone number. The rule says to make them available to all interested individuals; the step now says so.

Looking Back

955 corrections on 440 articles, newest first. Each is also shown on the article itself. Browse every article.

  1. · An exploited kernel flaw in an older platform showed that platform age is a control patches cannot supply

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  2. · When AI made flaws cheap to find, banks’ patch queues set the pace

    Reworded the hindsight sentence on the OCC’s Spring 2026 Semiannual Risk Perspective to what the report says (AI lowers the barrier to entry for threat actors and increases the speed, scale and sophistication of attacks), cited it, and cut the unsupported line that less capable people could increasingly do a specialist’s work. On 2026-11-15 an independent review (N-145) also reworded two references to briefing bank chief executives to what Vice Chair Bowman’s speech states, that Secretary Bessent and Chair Powell convened the largest banks.

  3. · Voya’s red flags program was written in 2009 and tested by phone in 2016

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  4. · Fair value as a fence: the 2018 Volcker proposal let the balance sheet decide what counted as trading

    N-150: Governor Brainard’s words are now paraphrased rather than quoted, since the series does not quote individuals. N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  5. · Volcker’s 2019 rewrite traded reports to examiners for records

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  6. · Texas’s ransomware day made the remote admin path an agency risk

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  7. · TEFCA’s second draft gave every connected provider a duty to answer

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  8. · Tailoring sorted banks by where they stood, not how fast they were moving

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  9. · What a supply chain label on a U.S. AI vendor asked of agencies and contractors

    N-150: the Secretary of Defense’s words are now paraphrased rather than quoted, since the series does not quote individuals.

  10. · Struts S2-057 was a test of knowing where the framework ran, and how

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  11. · SHIELD’s safe harbor covered safeguards, not the state notice filings

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  12. · Section 889 defined banned equipment by maker, role and purpose

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  13. · The SEC’s 2019 token framework made security status a fact to recheck

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  14. · Spoofed emails, real wires: the SEC put business email fraud inside payment controls

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  15. · SamSam chose the door, the hour and the backups

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  16. · Regulatory relief that lapses at the next release

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  17. · Regulation F’s 2019 draft gave creditors a specification for collection

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  18. · Regulation CC’s inflation clock turned deposit hold limits into a release every five years

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  19. · Purchase cards kept the security bans but dropped the clauses

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  20. · Point-of-sale drug discounts made a rebate fight into a claims-data problem

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  21. · Part 500’s September 2018 controls decided how much a breach could expose

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  22. · Part 2’s 2019 draft made a record’s origin the thing to track

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  23. · Cl0p’s Oracle campaign: an attack on the systems security teams did not run

    N-142: re-checked the Mandiant findings against the Google Threat Intelligence Group and Mandiant report and matched its hedging: the August 9, 2025 exploitation was of what may have been CVE-2025-61882, with additional suspicious activity from July 10.

  24. · One alert, three threats: how local agencies should have read the June 2025 Iran warning

    N-142: cut two unsourced hindsight details that rested on press reporting, that the ceasefire held through the summer and that hacktivist denial-of-service activity and claims of compromise followed, and reworded the remarks that assumed no large-scale campaign came.

  25. · OMB’s 2018 rescission list removed reminders, not the controls behind them

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  26. · OMB’s 2019 identity memo made every agency answer for the services it reused

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  27. · Oldsmar’s unidentified intruder, undisputed weaknesses

    N-142: cut the March 2023 account by the city’s former manager, the FBI’s comment to reporters and the sheriff’s office status, which rested only on the WUSF report, and the WUSF source; reframed the title, summary and the sections that relied on that revision around what the official advisories state (unidentified actors, a shared remote-access password).

  28. · OFR’s repo rule put LIBOR’s successor on a next-morning data feed

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  29. · NIST’s privacy draft counted harm where customers feel it

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  30. · Net neutrality’s 2018 repeal reached the public’s end of the connection, not the agency’s circuit

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  31. · Medtronic’s defibrillator radio flaw was answered in the device clinic, not the network

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  32. · Medicare’s 2019 virtual check-in priced a phone call and put the patient’s consent in the chart

    N-150: the CMS Administrator’s words from the press release are now paraphrased rather than quoted, since the series does not quote individuals. N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  33. · Medicare’s e-prescribing mandate ran through the credentialing office

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  34. · Medicare’s affiliation rule made enrollment data the evidence

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  35. · Easy to grant, hard to defend: M-24-10 put every federal AI exception on the record

    Reworded the sentence on credit unions and SR 11-7 (“did not bind them” is now “did not apply to them”) so it no longer reads as describing guidance still in force.

  36. · M-19-21 closed the archive’s door to paper and left open the processes that made it

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  37. · M-19-16 put a business case between agencies and their next back-office buy

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  38. · Libra’s design left the hard compliance work to the banks at its edges

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  39. · Lapse plans decided which federal cyber work kept running

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  40. · Why the LabMD ruling pushed regulators from “reasonable security” to named controls

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  41. · Kronos went down; the duty to pay public workers on time stayed up

    N-142: replaced The Record, CFO.com and SHRM with UKG’s own status updates and incident FAQ; rewrote the products, restoration and data-theft details to what UKG states, and cut the press-only details (the City of Cleveland and MTA, Franciscan Health’s manual payroll, pen-and-paper workarounds, employment lawyers’ warnings); replaced the unsourced Starbucks account of the Blue Yonder attack with Blue Yonder’s own notices, and reworded unsourced statements about what many employers found or did as possibilities. N-149: the sentence on employment lawyers’ warnings, which the note above lists as cut, was still in the body and has now been removed; it had no remaining source.

  42. · Paying dialysis providers for transplants: the kidney order priced outcomes they only partly controlled

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  43. · Kaseya and the most privileged system nobody on site runs

    N-142: replaced The Record’s report on Coop with Coop’s own website notice (archived July 4, 2021) and reworded the Coop details to what it states (a supplier’s IT attack stopped its tills and a majority of stores stayed closed over the weekend); cut the store count, the self-service checkouts and the Visma EssCom confirmation.

  44. · Janus made consent a payroll record, and California handed that record to the unions the same day

    N-150: the three quotations from Justice Kagan’s dissent are now paraphrased, since a dissent is one justice’s words and the series does not quote individuals; quotations from the Court’s opinion stay. N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  45. · Iowa’s caucus app failed at rollout before it failed in code

    N-142: rebuilt the caucus-night account (installation and sign-in steps, app usage, the coding error’s location in the national committee’s conversion tool, phone-line capacity and call counts) from the party’s November 10, 2020 internal review, which replaced the FEC disbursement record; corrected the second factor to a text-message code, dropped the illustrative chair’s evening and the Nevada payment amount, and reworded the contract-size remark; per the N-143 review, it also reworded the party’s February 7 statement to say the party would compare the reported numbers with the paper records, and paraphrased the two direct quotations from the party chair.

  46. · ION’s outage exposed a vendor no board had on its critical list

    N-142: cut two unsourced hindsight details that rested on press reporting, the November 2023 ICBC broker-dealer attack’s effect on Treasury settlement and the June 2024 CDK Global attack on car dealers.

  47. · Inflation’s first casualty in bank IT was the change budget

    N-150: Chair Powell’s remark on the word “transitory” is now paraphrased rather than quoted, since the series does not quote individuals.

  48. · The August 2024 selloff and the brokerage capacity limit before the first trade

    N-142: no company or official record of the August 5 login problems at Schwab, Fidelity and Vanguard could be verified (the companies’ own posts survive only as quoted in the press), so cut those reports, the Reuters source and the earlier-episode references, and reframed the title, summary, opening and the claim that the order path held around the pre-trade path as the article’s argument rather than a reported outcome; also reworded the unsourced statement that trading venues operated normally.

  49. · HIPAA’s 2019 penalty tiers made culpability a record to keep

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  50. · HICP sized health organizations by who could do the work

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  51. · A 2018 hacking complaint showed thieves editing the bank’s own record of its payments

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  52. · Guide 3’s uninsured-deposit line tied the 10-K to the call report

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  53. · GAO’s 2018 weapon system tests showed a control list is not evidence of security

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  54. · GAO’s 2019 high-risk list tied 16 other risks to missing skills

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  55. · Four weeks on paper: what Scripps exposed about downtime plans

    N-142: cut an unsourced hindsight detail, HHS’s January 2024 cybersecurity performance goals for the sector.

  56. · Florence’s waivers were narrow; the hospital’s own records carried the rest

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  57. · Five regulators’ AI questions read like an exam plan

    Put the description of the model risk sequence in SR 11-7 and the OCC’s 2011 bulletin in the past tense, since SR 26-2 and OCC Bulletin 2026-13 replaced that guidance on April 17, 2026.

  58. · First American’s 2019 leak tested the route from a pen test to the 8-K

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  59. · The OCC’s fintech charter wrote an uninsured bank’s duties into its approval letter

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  60. · Fedwire’s 2018 ISO 20022 plan split the format, the content and the duty to receive

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  61. · FedNow’s first demand on banks was a weekend treasury desk

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  62. · Pre-Cert tried to regulate the software maker, not each version

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  63. · FDA’s 2018 device playbook made cyber incidents a hospital staffing job

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  64. · Under FDA’s change-control model, the AI device a hospital validates will not stay the one it runs

    Reworded a hindsight sentence on model cards and subgroup figures (“became standard” is now “became common”) so it reads only as our view, not as a trend claim.

  65. · The FCC’s CIO rule named money and hiring and left contracts out

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  66. · FATF’s travel rule made each crypto transfer depend on a counterparty you could not see

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  67. · Evaluations inherited the proof appraisals used to supply

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  68. · Europe’s 2019 AI ethics checklist put procurement and QA in the governance table

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  69. · The EMP order tested continuity plans that count on distance

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  70. · Election security help came on request in 2018, which meant it could be withdrawn

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  71. · EDGAR’s hacked test filings put the pre-release path inside the perimeter

    N-150: Stephanie Avakian’s words are now paraphrased rather than quoted, since the series does not quote individuals. N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  72. · DOJ’s 2018 cyber report set out four lines of incident response, and the victim owned the fourth

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  73. · Emergency Directive 19-01 put registrar logins in the agency inventory

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  74. · The 2018 cyber strategy moved federal supplier security into the contract file

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  75. · A credit union’s first report of a vendor breach may come from the attacker

    N-142: no official or company source confirms ALPHV’s November 2023 SEC complaint against MeridianLink or its timeline, and MeridianLink’s statements reached the public only through the press, so cut that account and the BleepingComputer source; rebuilt the opening and summary around Mr. Cooper’s and Fidelity National Financial’s own 8-K filings and the Justice Department’s description of ALPHV’s methods, cut the unsourced ICBC and “first public confirmation” remarks, and reworded the MeridianLink references in the body and hindsight as general cases. N-149: the hindsight section still named Trellance, which the 2026-11-14 note lists as cut; that sentence is now a general statement of our view with no vendor named.

  76. · Cottage Health’s $3 million settlement tied a HIPAA evaluation to a server change

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  77. · Convincing faces, unauthenticated seats: the Hong Kong deepfake was a meeting-identity failure

    N-142: cut four unsourced hindsight details (the October 2024 New York DFS guidance, the UK reimbursement and EU payee-verification rules, and the FCC’s 2024 fine and settlement over the New Hampshire calls) and the unsourced remark that the case is one of the most cited, and described the FinCEN alert and the FBI’s December 2024 warning in more detail from those documents, and cut the press-only 2019 UK energy-firm voice-cloning case from the opening.

  78. · Commerce’s 2018 AI list made export control a staffing question

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  79. · Medicare’s clinic-visit cut priced hospital departments by address and history

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  80. · The CISA Act’s cloud clause mattered more than its new name

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  81. · CFIUS counted health data by what a company keeps

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  82. · Location records behind a warrant: the 2018 cell-site ruling made legal process a data classification job

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  83. · CBP’s 2019 pilot breach began with a vendor’s copy made to improve performance

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  84. · Capital One’s breach surfaced through a stranger’s report

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  85. · Bybit’s signers approved what their screens showed, which was not what they signed

    N-142: re-checked the Chainalysis figures against its December 18, 2025 report and restated them as it gives them (at least $2.02 billion stolen by North Korean actors, more than $3.4 billion industry-wide from January through early December, Bybit about $1.5 billion) in place of the rounded “about $2 billion” and “roughly 60 percent” of “about $3.4 billion”; the laundering-cycle description matched the report.

  86. · BlueKeep asked organizations to patch on a forecast, before any attack

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  87. · ChatGPT reached bank desks; recordkeeping set the longer limit

    N-142: no bank or official source confirms the February 2023 restrictions, so cut the JPMorgan report and the Bloomberg list of banks with the Fox Business and Fortune sources, and reframed the title, summary and opening around what banks’ own obligations required; also cut the press-only UBS user estimate, the Amazon and Samsung reports and the unsourced Morgan Stanley and JPMorgan assistant details, and sourced the March 2023 bug, the April 2023 data controls and ChatGPT Enterprise to OpenAI’s own announcements.

  88. · Backups could not answer the D.C. police data leak

    N-142: replaced the Infosecurity Magazine, Security Affairs and Associated Press sources with the U.S. Attorney’s Office for D.C. indictment release, Treasury’s Matveev sanctions release and SentinelLabs’ report on the leaked Babuk code; rewrote the account of the attack and the stolen data to what those sources state, and cut the press-only details (the informant threat and three-day deadline, the $4 million demand and $100,000 offer, the staged May releases and the AP’s file review, the Houston Rockets claim, the department’s statement, the “worst known” quote and Babuk’s announcement that it would stop encrypting).

  89. · APT10 made the provider’s admin account the client’s perimeter

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  90. · The 2018 AML innovation pledge protected the pilot, not the switch

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  91. · AMCA’s bankruptcy showed the labs would pay for their collector’s breach

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  92. · The 2019 AI order’s lasting demand was an inventory of data and models

    N-148: the published date now reads November 15, 2026, the day this article first went live; it had said November 14.

  93. · Zoom 5.0 fixed the vendor layer; configuration and records stayed yours

    Removed unsourced statements that managed accounts “became the norm” and that the platform remained widely used, and reworded unsourced statements about what many or most organizations did.

  94. · Zoom 5.0 fixed the vendor layer; configuration and records stayed yours

    Reworded as our view or as a possibility unsourced statements about what vendors, staff and institutions typically or often do (for example, “The evidence usually comes as a package”).

  95. · Your carrier’s routers belong in your threat model

    Removed or reworded as our view unsourced statements about what many or most organizations do (for example, “Many organizations still run unencrypted traffic over private circuits”).

  96. · Your carrier’s routers belong in your threat model

    Reworded as our view or as a possibility unsourced statements about what network providers and their customers typically or often do (for example, “The customer often cannot see the list”). Replaced Microsoft's Volt Typhoon blog with the joint advisory AA23-144A and reworded the router claim to what it says, added advisories AA24-038A and AA25-239A and the Justice Department's KV botnet release as sources, replaced the Cisco Talos findings with what advisory AA25-239A says about credentials, RADIUS and TACACS+ traffic and the Smart Install flaw, and cut unsourced passages on the Flax Typhoon botnet, the Treasury sanctions and the FCC's 2025 CALEA ruling and its rescission.

  97. · Why World Cup cyber risk sat in the city services residents use every day

    Removed or reworded as our view or a condition unsourced statements about how widely or how often organizations did something (for example, “the one most often skipped”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “rarely sit in one governance meeting”). Replaced the Recorded Future blog post with the Canadian Centre for Cyber Security’s World Cup threat bulletin and reworded the pre-tournament warning to what the bulletin states.

  98. · Why working from home failed when Texas froze

    Removed or reworded as our view unsourced statements about how widely or how often organizations did something (for example, “By February 2021, most organizations had spent eleven months proving that knowledge work could be done from home”).

  99. · Why working from home failed when Texas froze

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do in their continuity plans (for example, “Hospitals often house staff overnight during severe weather”).

  100. · Why WISeR providers should keep their own record while Congress argues

    Removed or reworded as our view or a condition unsourced statements about how widely or how often organizations did something (for example, “the concern critics of the model raise most often”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “They are rarely joined, and for traditional Medicare”). Replaced the LeadingAge source with the manager’s amendment adopted at the June 9 markup (House Committee Repository), replaced the KUOW report of a CMS corrective action plan with Virtix Health’s own statement of its peak 8.97-day turnaround against the three-day standard, and cut the Texas approval figures reported by the Washington Post via PYMNTS along with that source.

  101. · Why Windows 10’s end of support split every hospital fleet in three

    Removed or reworded as our view or a condition unsourced statements about how widely or how often organizations did something (for example, “Regulators and insurers increasingly ask hospitals”).

  102. · Why Windows 10’s end of support split every hospital fleet in three

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “End of support is usually run as a refresh project”).

  103. · Why valid when made left bank-fintech lenders two open questions

    Reworded as our view an unsourced statement about where partnerships most often go wrong.

  104. · Why valid when made left bank-fintech lenders two open questions

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “Fintech partners are often young companies funded by investors”). Replaced the Skadden client alert with the court’s February 8, 2022 order in the FDIC case and reworded the ruling to what that order says, since no official copy of the separate OCC order was available.

  105. · Why the spyware order put the burden on acquisition staff

    Reworded as a possibility unsourced statements about what spyware vendors and buyers typically or often do (for example, “Spyware vendors have often been organized as groups of companies”). Replaced the Access Now source with the USAspending.gov record of ICE contract 70CTD024P00000012 and added the Citizen Lab’s March 2025 Paragon report; reworded the ICE contract and Italy findings to what those sources state and cut the unsourced claims that the stop-work order was a review against the order, that it lifted after Paragon’s sale to a US investor and that ICE told Congress in April 2026 it had used Paragon’s tools, together with the conclusions that relied on them. On 2026-11-15 an independent review (N-145) reworded the Italy finding to say the spyware was used to target the journalist and rescue-organization members, which is what the Citizen Lab report states.

  106. · Why the Signal group chat was a channel design failure before it was a leak

    Removed or reworded unsourced statements about how widely Signal is used and respected and what many organizations and firms did (for example, “the alternative many organizations reach for”).

  107. · Why the Signal group chat was a channel design failure before it was a leak

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “enterprise tools often stop at the agency boundary”). Replaced an unsourced statement that off-channel messaging penalties “ran into the billions of dollars” with the SEC’s September 2022 release (sixteen firms, penalties totaling more than $1.1 billion), and removed unsourced references to CFTC cases and to WhatsApp and Signal. Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “Agencies that have taken this episode to heart tend to share several features.”). On 2026-11-15, replaced the Cornell Legal Information Institute copy of 44 U.S.C. 2911 with the govinfo United States Code and the archived Associated Press story with an Internet Archive copy of the inspector general’s report DODIG-2026-021, reworded the review request, findings and report date to what that report states, cut the unsourced March 18 memo, the New York Times second-chat report and the claim that the phone was not provided, and kept the Google Threat Intelligence Group source as Google’s own finding. On 2026-11-15 an independent review (N-145) changed “accepted” to “noted” for the inspector general’s treatment of the secretary’s classification decision, which the report records without endorsing.

  108. · Why the ownership registry never replaced the bank’s own file

    Removed or reworded as our view unsourced statements about how widely or how often organizations did something (for example, “Most companies with layered structures have ordinary reasons for them”).

  109. · Why the ownership registry never replaced the bank’s own file

    Reworded as our view or as a possibility unsourced statements about what banks, fintechs and examiners typically or often do (for example, “Community banks and credit unions often run onboarding on a vendor’s platform”). Replaced the Greenberg Traurig client alert with the text and amendment notes of 31 U.S.C. 5323 on govinfo, added the SEC’s whistleblower program page for the SEC’s 10 percent minimum, and reworded the description of the award fund to what the statute says.

  110. · Why the IRS’s ten-year budget needed a one-year payoff

    Removed an unsourced reference to “many companies”.

  111. · Why the IRS’s ten-year budget needed a one-year payoff

    Reworded as our view or as a possibility unsourced statements about what agencies and organizations usually or often do (for example, “Organizations often treat these conversations as advocacy”).

  112. · Why the FFIEC’s pandemic statement was an evidence checklist

    Removed or reworded unsourced statements about what most or many institutions did in 2020 (for example, “Within two weeks of the statement, most institutions had moved to their most severe planned stage”).

  113. · Why the FFIEC’s pandemic statement was an evidence checklist

    Reworded as our view or as a possibility unsourced statements about what banks and examiners typically or often do (for example, “A large bank typically has a dedicated continuity team”).

  114. · Why the CMS patient app pledge depends on the registration desk

    Removed or reworded as our view or a condition unsourced statements about how widely or how often organizations did something (for example, “the widely used format”).

  115. · Why the CMS patient app pledge depends on the registration desk

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “they are often the first to feel budget pressure”).

  116. · Why the air traffic control rebuild started with the wires

    Removed or reworded as our view or a condition unsourced statements about how widely or how often organizations did something (for example, “Many agencies share this hidden dependency”).

  117. · Why the air traffic control rebuild started with the wires

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “Budgets usually fund the new system and assume the old one simply stops”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “tends to win the argument”). On 2026-11-15, replaced the archived Associated Press article with the FAA’s December 4, 2025 prime-integrator announcement, added the FAA’s Newark statements and its May 8, 2025 plan announcement, reworded the April 28 and May 9 outages, the cause and the plan to what the FAA stated, attributed the $20 billion figure to the FAA Administrator, and cut the unsourced 30-to-90-second duration, the copper-line description and the $31.5 billion total.

  118. · Why the AI Act’s obligations follow your role, not your sector

    Added to the hindsight that SR 11-7 and OCC Bulletin 2011-12 were superseded on April 17, 2026, by SR 26-2 and OCC Bulletin 2026-13.

  119. · Why the AI Act’s obligations follow your role, not your sector

    Reworded as our view unsourced statements about what most or many organizations do and about adoption (for example, “The role register has proved one of the most reusable pieces of AI governance”).

  120. · Why the AI Act’s obligations follow your role, not your sector

    Reworded as our view or as a possibility unsourced statements about what banks, hospitals and agencies typically or often have in place (for example, “For a hospital group or a public agency, they often do not”).

  121. · Why a security attestation to government now carries fraud risk

    Removed or reworded as our view unsourced statements about how the settlement was described and what most or many organizations found (for example, “The list was longer than most organizations expected”).

  122. · Why a security attestation to government now carries fraud risk

    Reworded as our view or as a possibility unsourced statements about what organizations, agencies and relators typically or often do (for example, “A state agency typically has the most varied mix”).

  123. · Why the SEC’s hijacked account was most valuable the day before a decision

    Reworded unsourced statements about what most organizations and agencies do (for example, “Most organizations have done something similar under deadline pressure”).

  124. · Why the SEC’s hijacked account was most valuable the day before a decision

    Reworded as our view or as a possibility unsourced statements about what agencies and communications teams typically or often do (for example, “State and local agencies often have neither a dedicated security team”). Replaced the CyberScoop and The Record sources with the SEC’s own statements page and the Justice Department’s sentencing release, added the FCC’s SIM-swap order, and cut unsourced statements about an October 2023 false news report, the Mandiant account takeover, the January 10 deadline, the first trading day and X’s statement on multi-factor authentication. On 2026-11-15 an independent review (N-145) reworded the post about the compromise to what the SEC’s statement says, that its public affairs staff posted it on the chair’s account.

  125. · Why Scattered Spider’s turn to insurers should have set a deadline for the rest of finance

    Removed or reworded as our view or a condition unsourced statements about how widely or how often organizations did something (for example, “widely blamed”). Removed an unsourced statement that the group was publicly blamed for the 2023 intrusions at MGM Resorts and Caesars Entertainment. Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “as early filings usually are”). Replaced The Hacker News source with Mandiant’s own UNC3944 hardening guidance and rewrote the opening to what that guidance and the FBI–CISA advisory say, cutting the reported June 16 Google warning, the Marks & Spencer order suspension and £300 million estimate, the unsourced Google voice-phishing and Jaguar Land Rover and Transport for London passages, and adding DFS’s multifactor authentication guidance for the Part 500 date.

  126. · Why one phone call beat Twitter’s login controls

    Removed or reworded as our view unsourced statements about how widely or how often organizations did something (for example, “Senior leaders most often miss this part”).

  127. · Why one phone call beat Twitter’s login controls

    Reworded as a possibility unsourced statements about what help desks and organizations typically or often do (for example, “Outsourced service desks often run on their own scripts”). Replaced the American Hospital Association copy of the HC3 help desk alert with an Internet Archive copy of HHS’s own file, sourced the British defendant’s extradition and five-year sentence to the Justice Department release (correcting the dates to his April 2023 extradition and June 2023 sentencing), and cut the unsourced casino, Florida teenager, whistleblower, British retailer and £300 million, and Change Healthcare testimony details.

  128. · Why o1’s reasoning summaries added work for clinical AI committees

    The HTI-5 rule is now described as final: ASTP/ONC finalized the removal of the decision support model card (source attribute) requirements on October 28, 2026 (91 FR 67916), effective December 28, 2026. The earlier text described it only as a proposal. Removed unsourced statements that reasoning became a standard feature and that these questions became routine for clinical AI committees, and that Section 1557 reaches most hospitals and many practices and insurers; the post now says which kinds of entities the rule can include. Sourced the hindsight on later reasoning models to OpenAI’s GPT-5 system card and DeepSeek’s R1 release note, removed an unsourced January 2025 date for o3-mini and unsourced claims that Google released a reasoning model and that DeepSeek’s R1 displayed its full reasoning text, and described Claude 3.7 Sonnet’s visible reasoning as Anthropic’s research page does. Also reworded as possibilities two unsourced statements about what hospitals usually have (for example, “usually has a CMIO with a day job”). Sourced the Office for Civil Rights’ January 2025 guidance on the Section 1557 decision support provision to its January 10, 2025 letter, and the date and content of California’s AB 3030 rule to the Medical Board of California’s notice (it applies from January 1, 2025 and exempts communications read and reviewed by a licensed or certified provider; the text had said a licensed provider and dated the law’s enactment without a source). Replaced an unsourced description of a mid-2025 joint paper on chain-of-thought monitoring with what Anthropic’s listed research page says about monitoring, and removed unsourced statements about the FDA’s Digital Health Advisory Committee, the FDA’s January 2026 decision support guidance and joint Joint Commission and Coalition for Health AI guidance. Removed the December 2025 HTI-5 proposed rule and DeepSeek’s R1 release note from the sources to stay within the source limit: the final rule, still listed, gives the proposal’s December 29, 2025 date, and the sentence giving R1’s January 2025 release date was cut. Removed the description of a 2023 study in which reordered answer options steered models’ answers without being mentioned in their reasoning, which had no source in the list, and the unsourced statement that research had already shown stated reasoning does not always reflect what drove the output; the point is now made from OpenAI’s o1 system card, which called chain-of-thought faithfulness an open research question. Cut statements that the system card does not make and no listed source states (launch access limits and missing features, OpenAI’s user-experience and competitive reasons for hiding the reasoning, the separate summarizer model and billing for hidden reasoning tokens), and reworded the benchmark claim and OpenAI’s interest in monitoring the reasoning to what the o1 system card says.

  129. · Why LAUSD could keep classrooms open through a ransomware attack

    Removed unsourced statements about what many organizations do and dropped unsourced “widely” and “increasingly” descriptions (for example, “many organizations keep files long after the schedule allows”). Replaced an unsourced report that the 2023 attack on MGM Resorts began with a help desk call with the FBI and CISA’s November 2023 advisory on help desk calls by the Scattered Spider group.

  130. · Why hospitals could prepare for CIRCIA before CISA wrote its rule

    Removed unsourced statements about how many hospitals use incident command for cyberattacks (for example, “Many hospitals now list a cyberattack among their hazards”).

  131. · Why hospitals could prepare for CIRCIA before CISA wrote its rule

    Reworded as our view or as a possibility unsourced statements about what hospitals, insurers and attackers typically or often do (for example, “Legal teams often prefer to say nothing until an investigation concludes”).

  132. · Why hospital COVID reporting turned out to be infrastructure

    Removed or reworded unsourced statements about what most or many hospitals did (for example, “Many hospitals compiled daily reports by hand”) and an unsourced “used widely”.

  133. · Why hospital COVID reporting turned out to be infrastructure

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “A report built by an analyst alone often counts what is easy to query”). Replaced the copy of the HHS reporting guidance hosted by the National Association for Behavioral Healthcare with an Internet Archive copy of the hhs.gov original, replaced the Medical Laboratory Observer source with the HHS facility-level dataset on HealthData.gov, and reworded the suppression detail to what the dataset states.

  134. · Why good-faith estimates weighed most on the therapist’s office

    Reworded an unsourced statement about which question is “most often left without an answer” as our view.

  135. · Why good-faith estimates weighed most on the therapist’s office

    Reworded as our view or as a possibility unsourced statements about what small practices, patients and software vendors typically or often do (for example, “Those offices usually have no billing department at all”).

  136. · Why Form CRS was the easy part of Regulation Best Interest

    Reworded unsourced statements about what most or many firms did or captured (for example, “took data most firms never captured”).

  137. · Why Form CRS was the easy part of Regulation Best Interest

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “Examiners typically start with lists”). Replaced the Arnold & Porter client alert with SEC Chairman Clayton’s April 2, 2020 statement and reworded the compliance-date sentence to it, added the Second Circuit’s June 26, 2020 decision, the Labor Department’s June 29, 2020 release and FINRA Regulatory Notice 20-18 for previously unsourced statements, and cut an unsourced statement about Massachusetts’s fiduciary standard. On 2026-11-15 an independent review (N-145) corrected the description of the challengers to what the Second Circuit’s decision says (states, an organization of investment advisers and an individual investment adviser, not two advisory firms).

  138. · Why FedNow was a core-processor decision for community banks and credit unions

    Removed or reworded as our view unsourced statements about how FedNow adoption grew and what many institutions did (for example, “many institutions joined as receive-only first”).

  139. · Why FedNow was a core-processor decision for community banks and credit unions

    Reworded as our view or as a possibility unsourced statements about what banks, credit unions and their processors typically or often do (for example, “These institutions rarely run their own core systems”). Corrected the date of FedNow’s rise in its transaction limit from $500,000 to $1 million to June 2025 (it said late 2024), and added the later rise to $10 million effective November 2025. Sourced the launch fees and limits to the Fed’s January 2022 pricing announcement and replaced an unsourced participation count with the Fed’s June 2025 figure of about 1,400 banks and credit unions. Sourced the March 2025 order ending federal paper checks to Executive Order 14247 and described it as the order does (it directs the Secretary of the Treasury; the text had said the Bureau of the Fiscal Service was charged with much of the transition). Removed unsourced accounts of Synapse’s 2024 bankruptcy, the United Kingdom’s October 2024 reimbursement rule for authorized push payment scams and the CFPB’s December 2024 suit over Zelle and its later dismissal, and replaced a general statement about fraud features with the account activity thresholds described in the Fed’s June 2025 release, also the source for community banks and credit unions making up more than 95 percent of participants. Removed the FedNow Explorer common questions page from the sources; the Fed’s FedNow pages still listed cover what it was cited for. Removed two unsourced statements, with no room for another source under the eight-source limit: that banks had run Zelle since 2017, and that the United Kingdom introduced a confirmation-of-payee check in 2020, together with the comparison with US rails built on it.

  140. · Why North Korea’s fake remote hires succeed in the gaps between HR, IT and security

    Reworded unsourced statements about what most organizations or companies do (for example, “In most organizations the relevant facts are scattered”).

  141. · Why North Korea’s fake remote hires succeed in the gaps between HR, IT and security

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “Security teams are typically tuned to spot outside attackers”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “The gaps tend to show up in the first two or three cases.”). Added the May 2022 State, Treasury and FBI guidance on North Korean IT workers and corrected “up to $300,000 a year” to what it says: more than $300,000 a year in some cases.

  142. · Why exposure notification apps rose or fell on the back office

    Removed an unsourced statement that adoption of exposure notification apps “varied widely and was generally modest”, and an unsourced “widely cited”.

  143. · Why exposure notification apps rose or fell on the back office

    Reworded as a possibility unsourced statements about what health agencies and their teams typically or often did (for example, “Test orders often lacked a patient phone number”). Replaced the 9to5Mac, The Markup and Engadget sources with Google’s December 2020 Exposure Notifications update, the CVE-2021-31815 record and GAO report GAO-21-104622, added California’s CA Notify shutdown notice, the Nature study of the NHS COVID-19 app and the CARES Act, reworded the state counts, shutdown date, Android logging flaw and CDC funding to what those sources say, and cut the unsourced first-state names, Washington State case estimate, 100,000 contact tracer estimate and TraceTogether launch date.

  144. · Why community banks’ open banking experience sat with their core vendors

    Reworded unsourced statements about what lenders and most institutions do (for example, “Lenders increasingly read applicants’ transaction histories”) as possibilities.

  145. · Why community banks’ open banking experience sat with their core vendors

    Reworded as our view or as a possibility unsourced statements about what banks and credit unions typically or often do (for example, “A community bank typically licenses both rather than building them”). On 2026-11-15 replaced the ABA Banking Journal article with the CFPB’s personal financial data rights page and reworded the litigation sentences to it (the court stayed the compliance dates on October 29, 2025), and cut the unsourced claims about the CFPB calling the rule unlawful, the JPMorgan Chase and Plaid fee arrangement and the August 2026 review.

  146. · Why CISA’s Ivanti disconnect order was decided by people, before it was issued

    Reworded as conditions unsourced statements about what most or many agencies do (for example, “Many agencies do not operate their own edge devices”).

  147. · Why CISA’s Ivanti disconnect order was decided by people, before it was issued

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do during emergency patching (for example, “The workforce controls are simple and often missing”). Replaced The Record source with MITRE’s own disclosure of its breach and cut the statement that CISA said two of its own systems had been compromised, which no official source we could find states.

  148. · Why Change Healthcare’s missing MFA was a deal-integration failure

    Removed unsourced “widely” and “increasingly” descriptions of credential trading, HITRUST certification and session token theft.

  149. · Why Change Healthcare’s missing MFA was a deal-integration failure

    Reworded as our view or as a possibility unsourced statements about what health care acquirers, integration teams, insurers and attackers typically or often do (for example, “Integration teams often want to connect the acquired network to the parent’s quickly”).

  150. · Why buying the same software as your neighbors removes your fallback

    Removed or reworded unsourced statements about what most or many hospitals do and about trends (for example, “Most hospitals have them for short, planned outages”). Sourced the July 2024 CrowdStrike outage to CISA’s alert and Microsoft’s estimate of 8.5 million devices.

  151. · Why business email compromise belongs to the payments team

    Removed or reworded as our view unsourced statements about how widely or how often organizations did something (for example, “Many companies also use a treasury platform” and “a widely reported Hong Kong case”).

  152. · Why business email compromise belongs to the payments team

    Reworded as our view or as a possibility unsourced statements about what businesses, banks, insurers and criminals typically or often do (for example, “Mule accounts often show recognizable patterns”). On 2026-11-15 replaced the Cornell copy of UCC § 4A-202 with Minnesota’s enacted text and the GovInfoSecurity article with FinCEN alert FIN-2024-Alert004, cut the unsourced Hong Kong deepfake case and Arup identification, added the Eighth Circuit’s Choice Escrow opinion and Federal Reserve letter SR 21-14 for the court case and 2021 authentication guidance, and reworded the guidance sentence to what the letter states.

  153. · Why Basel’s 1,250% risk weight pointed banks toward custody

    Reworded unsourced statements about what most banks and institutions had or did in 2021 (for example, “Most banks did not have these people in 2021”) as conditions.

  154. · Why Basel’s 1,250% risk weight pointed banks toward custody

    Reworded as our view or as a possibility unsourced statements about what banks, exchanges, insurers and customers typically or often do (for example, “Crypto exchanges often offered custody cheaply”).

  155. · Why bank change control never saw the npm hijack

    Removed or reworded as our view or a condition unsourced statements about how widely or how often organizations did something (for example, “most banks read the news as someone else’s problem”).

  156. · Why bank change control never saw the npm hijack

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “The gaps it exposes are usually mundane”). On 2026-11-15, replaced the Aikido Security post with GitHub’s advisory for the malicious chalk release (published September 8, 2025), reworded the package count, download figure and removal to GitHub’s own account, and cut the unsourced count of 18 packages and the npmjs.help phishing-domain detail. On 2026-11-15 an independent review (N-145) reworded as a likelihood the unsourced statement that many of the downloads came in as indirect dependencies.

  157. · Why banking-as-a-service margins never covered the cost of knowing whose money it was

    Reworded as our view or as a possibility unsourced statements about what banks, fintechs and middleware providers typically or often do (for example, “So they were often assumed to sit with the middleware provider”).

  158. · Why the AI preemption order barely reached health care’s own AI rules

    Corrected the hindsight, which gave June 30, 2026 as the Colorado AI Act’s effective date: SB 26-189, signed on May 14, 2026, repealed and reenacted the law before that date, with developer duties from January 1, 2027.

  159. · Why the AI preemption order barely reached health care’s own AI rules

    Removed or reworded as our view or a condition unsourced statements about how widely or how often organizations did something (for example, “The reality inside most hospitals and health plans”). The Justice Department’s move in the xAI lawsuit against Colorado is now cited from the Department’s own April 24, 2026 release, which says it moved to intervene, in place of a news report.

  160. · Why the AI preemption order barely reached health care’s own AI rules

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “they often picture a robot diagnosing disease”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “Weaker programs tend to make the same errors:”).

  161. · Why the AI Act left bank credit models with the supervisor they already had

    Added to the hindsight that SR 11-7 and OCC Bulletin 2011-12 were superseded on April 17, 2026, by SR 26-2 and OCC Bulletin 2026-13, and that Colorado SB 26-189, signed on May 14, 2026, repealed and reenacted the AI law before its June 30, 2026 date, with developer duties from January 1, 2027; put the description of SR 11-7 as current guidance in the past tense.

  162. · Why the AI Act left bank credit models with the supervisor they already had

    Removed unsourced “increasingly” trend claims about banks’ use of machine learning in credit decisions.

  163. · Why the AI Act left bank credit models with the supervisor they already had

    Reworded as our view or as a possibility unsourced statements about what banks and supervisors typically or often do (for example, “Banks often do not collect that information”).

  164. · Why a Windows crypto patch was an asset inventory test

    Updated the hindsight to note that CISA revoked BOD 22-01 on June 10, 2026 and replaced it with BOD 26-04, and removed an unsupported statement that many state agencies, banks and hospitals use the catalog to set their own priorities.

  165. · Why a Windows crypto patch was an asset inventory test

    Removed or reworded as our view unsourced statements about what most or many organizations and agencies do (for example, “Most organizations hold at least three lists of their devices”) and dropped unsourced “widely” and “increasingly”.

  166. · Why a Windows crypto patch was an asset inventory test

    Reworded as our view or as a possibility unsourced statements about what agencies and other organizations typically or often do (for example, “Endpoints managed by central IT are usually well inventoried”).

  167. · Who may see the vaccination record: the negotiation behind the rollout

    Reworded as our view or as a possibility unsourced statements about what registries, agencies and vendors typically or often do (for example, “Those contracts often focused on getting appointments booked”). Replaced the ABA Journal and MIT Technology Review sources with the New York governor’s November 2, 2020 letter and CDC’s interim playbook, added CDC’s February 2021 MMWR report on vaccine recipients’ demographics, reworded New York’s objection to what the governor wrote and the six jurisdictions that reported no race or ethnicity, and cut the unsourced Minnesota position and the federal officials’ and HHS’s assurances, and the unsourced mid-September and mid-October playbook dates. On 2026-11-15 an independent review (N-145) removed the quotation marks around the data use agreement’s words in the New York passage and paraphrased them.

  168. · Who counts as a crypto broker mattered less than what brokers could not know

    Reworded as our view or as a possibility unsourced statements about what firms and customers typically or commonly do (for example, “Digital asset customers commonly buy on one platform”).

  169. · Who checked the people who moved FTX’s money

    Reworded unsourced statements about what most or many banks already have (for example, “routines most banks already run”).

  170. · Who checked the people who moved FTX’s money

    Reworded as our view or as a possibility unsourced statements about what banks, fintechs and depositors typically or often do (for example, “The work crosses lines that banks usually keep apart”). Replaced the NPR report on the sentencing with the Second Circuit's June 2026 opinion affirming the conviction and 25-year sentence, added the agencies' January and February 2023 crypto statements (withdrawn in April 2025), the June 2023 third-party guidance and the White House GENIUS Act fact sheet as sources, and cut unsourced details (the Bahamas arrest, the conviction and sentencing months, the bankruptcy plan and repayments, Silvergate, Synapse and the FDIC custodial account proposal).

  171. · No key to buy: WhisperGate and the agency recovery plan

    Removed or reworded unsourced statements about what many or most agencies did, and dropped unsourced “widely” descriptions (for example, “Most agencies that run one use a ransomware scenario”).

  172. · No key to buy: WhisperGate and the agency recovery plan

    Reworded as our view or as a possibility unsourced statements about what local governments and ransomware gangs typically or often do (for example, “Ransomware operators often spend weeks in a network before encrypting”). Added CISA advisory AA24-249A for the Unit 29155 attribution and the Cadet Blizzard name, attributed two WhisperGate details to Microsoft, and cut unsourced details (the North Carolina and Florida ransom-payment laws, the Kaseya date, National Guard teams, the $1 billion grant figure, the Oakland and Dallas attacks and the incident reporting law dates).

  173. · When vendors set facial recognition policy before agencies did

    Reworded unsourced statements about what many agencies did or knew (for example, “Facial recognition entered many agencies by routes that bypassed central governance”) and dropped unsourced “widely” and “increasingly”.

  174. · When vendors set facial recognition policy before agencies did

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “Small agencies often buy through state cooperative contracts”). Replaced The Logic, UPI, CNN (via KVIA) and Michigan Public sources with IBM’s own letter to Congress, Microsoft’s Face transparency note, the AWS Service Terms and Detroit Board of Police Commissioners minutes from June 2020 and April 2025, reworded the Microsoft, Amazon and Detroit passages to what those documents state, and cut the unsourced arrest details and settlement terms and date. On 2026-11-15 an independent review (N-143) removed the name of the man who was wrongly arrested, a private individual.

  175. · When the FBI offers a decryptor: what ALPHV’s takedown asked of public agencies

    Reworded unsourced generalizations about most agencies and ransomware groups and removed “widely” from an unsourced description (for example, “ALPHV, like most groups, stole data before encrypting it”).

  176. · When the FBI offers a decryptor: what ALPHV’s takedown asked of public agencies

    Reworded as a possibility unsourced statements about what ransomware affiliates and insurers typically or often do (for example, “Typically, an affiliate gets in through a weak point”). Replaced the CyberScoop sources with the Justice Department’s December 19, 2023 announcement (Internet Archive copy) and the CISA, FBI and HHS advisory AA23-353A; reworded the seizure and the group’s response to what they state and cut the unsourced “unseized” claim, the Change Healthcare superlative and the exit-scam account.

  177. · When AI made flaws cheap to find, banks’ patch queues set the pace

    Removed or reworded as our view or a condition unsourced statements about how widely or how often organizations did something (for example, “yet most banks could not use it”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “tend to get both benefits”). Replaced the CBS News and Bloomberg Law reports with Federal Reserve Vice Chair Bowman’s May 1, 2026 speech, rewording the bank chief executives’ meeting to what she said and cutting the unsourced timing and venue details and the reported pause in cyber examinations.

  178. · When a service portal is the target, the outage is the message

    Replaced an unsourced statement that the break was “widely described” as the first of its kind with our own hedged view.

  179. · When a service portal is the target, the outage is the message

    Reworded as our view or as a possibility unsourced statements about what agencies and attackers usually or often do (for example, “Shared platforms often struggle for money”). Added the White House statement of September 7, 2022 condemning the attack, reworded the September attack wave to what the FBI and CISA advisory says, and cut unsourced details (NATO condemnation, Iran's denial, the border control attack, Killnet's October 2022 attacks, the October 2020 email attribution, the 2011 to 2013 bank attack dates and 2016 indictment, and the 2024 campaign hack attribution and indictment). On 2026-11-15 (N-146) the unsourced account of denial-of-service attacks on U.S. banks “a decade before Albania” was reworded to the Justice Department’s March 2016 announcement of the indictment (46 victims, mostly in the U.S. financial sector, late 2011 to mid-2013), and the unsourced statement that the attacks did not reach account data was cut.

  180. · When a hospital diverts, the whole region absorbs the attack

    Dropped unsourced “widely” from statements about how the attack was reported and described, and reworded unsourced statements about what many organizations and health systems do.

  181. · When a hospital diverts, the whole region absorbs the attack

    Reworded as our view or as a possibility unsourced statements about what hospitals and attackers typically or often do (for example, “A full emergency department usually recovers within hours”). Replaced the Associated Press (SecurityWeek), MIT Technology Review and Health-ISAC (American Hospital Association) sources with the North Rhine-Westphalia justice minister’s reports to the state parliament (Vorlagen 17/3855 and 17/4545) and HHS’s Cybersecurity Performance Goals page; added the prosecutors’ finding that the delay was about 20 to 25 minutes rather than an hour, and cut the unsourced 32-kilometer distance, the “first death linked to ransomware” description and the January 2024 publication date.

  182. · What the Equifax indictment changed for banks, and what it did not

    Removed or reworded unsourced statements about what most or many banks and organizations do (for example, “Most banks have a patching policy”) and dropped unsourced “widely” and “increasingly”.

  183. · What the Equifax indictment changed for banks, and what it did not

    Reworded as our view or as a possibility unsourced statements about what financial institutions and criminals typically or often do (for example, “Their onboarding, online banking and call center tools usually come from a core processor”).

  184. · What the White House cyber summit’s training pledges left for agencies to fix

    Removed or reworded as our view unsourced statements about where most agencies lost candidates, how federal hiring was described and how discussion in the security field changed after 2021.

  185. · What the White House cyber summit’s training pledges left for agencies to fix

    Reworded as our view or as a possibility unsourced statements about what public employers and their hiring processes typically or often do (for example, “Public hiring processes often take months”).

  186. · What sanctioning SUEX changed for banks that serve crypto firms

    Reworded as our view or as a possibility unsourced statements about what banks and their staff typically or commonly do (for example, “Banks commonly organize risk in three lines”). On 2026-11-15 attributed the ransomware payment estimates by name to Chainalysis, whose own report is the source.

  187. · What payers’ first prior authorization numbers needed from providers to be useful

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “Prior authorization teams are often sized by headcount history”). Removed an unsourced characterization of what payers argued (that most decisions were quick) and replaced an unsourced statement that most required plans posted, with a tracker figure reported second-hand by a consulting firm, with what KFF’s August 2026 review states about the reports it collected. Kept KFF only for its own survey findings, and replaced its account of CMS’s July 2026 template and the 2026 proposed rule with the CMS template and the proposed rule itself, rewording to what they state.

  188. · What Hive’s victims gained by calling the FBI early

    Removed or reworded unsourced statements about how widely products were used and what many hospitals do (for example, “Many hospitals also notify their information sharing organization”).

  189. · What Hive’s victims gained by calling the FBI early

    Reworded as our view or as a possibility unsourced statements about what hospitals, insurers, executives and the FBI typically or often do (for example, “Executives often worry that information given to the FBI will surface in public”). Replaced the BleepingComputer report with the Justice Department's Hive announcement and reworded the takedown details to what it says, added the Justice Department's ALPHV/BlackCat announcement and the UnitedHealth chief executive's Senate testimony as sources, and cut unsourced details (the Memorial Health System attack, the leak site seizure notice, the 190 million affected count and the March 2024 OCR investigation).

  190. · What due diligence cannot outsource, as Wirecard’s partners found

    Reworded unsourced statements about what many institutions and firms discover or lack, and removed an unsourced “widely described as one of the largest accounting frauds”.

  191. · What due diligence cannot outsource, as Wirecard’s partners found

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “Ownership is where these routines usually fail”). Replaced two press sources (Al Jazeera, Crowdfund Insider) with official ones: the Munich I Regional Court’s January 2023 press release on the Wirecard proceedings, a May 2026 court press release on hearing dates, and BAFA’s 2024 account of the APAS sanctions on EY. Reworded the trial and EY sentences to what those sources state (the trial opened on December 8, 2022; the sanctions included a two-year ban on new statutory audit mandates at public-interest entities) and removed an unsourced statement that the former board member responsible for the Asian business remained a fugitive for years.

  192. · What a voluntary control systems memo could not give small water utilities

    Reworded as our view or as a possibility unsourced statements about what water utilities, vendors and intruders typically or often do (for example, “Intruders commonly reach a plant through the office network”).

  193. · What a stolen license number proves, and what banks treated it as proving

    Removed or reworded as our view unsourced statements about what many or most banks and organizations do (for example, “Many banks keep full scans anyway”).

  194. · What a stolen license number proves, and what banks treated it as proving

    Reworded as our view or as a possibility unsourced statements about what banks, staff and fraudsters usually or often do (for example, “Fraud investigators often resist deletion”).

  195. · Volt Typhoon left little to scan for, so agencies had to know their own normal

    Updated the text to say that M-21-31 applied at the time and that OMB rescinded it on May 22, 2026, with memorandum M-26-14.

  196. · Volt Typhoon left little to scan for, so agencies had to know their own normal

    Reworded unsourced statements about what many organizations monitor, log or have learned, and about a trend in regulators’ expectations (for example, “edge devices that many organizations monitor poorly”).

  197. · Volt Typhoon left little to scan for, so agencies had to know their own normal

    Reworded as our view or as a possibility unsourced statements about what agencies, utilities and integrators typically or often do (for example, “Integrators who maintain control systems often install their own remote access”).

  198. · Vendors repriced in a day, contracts run for years: the buyer’s side of the software selloff

    Removed or reworded as our view or a condition unsourced statements about how widely or how often organizations did something (for example, “Many organizations renew on familiar terms”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “That gave buyers something they rarely have:”). Replaced the Reuters report with the Federal Reserve’s March 2026 FOMC minutes, removed the Sevens Report source, and cut the unsourced February 3 market details, the Thomson Reuters record-fall report, the analysts’ views and the end-of-March ETF figures.

  199. · Vaccine access hinged on open appointments nobody could see

    Removed or reworded as our view unsourced statements about how widely or how often organizations did something (for example, “appear routinely in agency digital strategies” and “The CDC’s central scheduling tool was widely rejected”).

  200. · Vaccine access hinged on open appointments nobody could see

    Reworded as a possibility unsourced statements about what cities and insurers’ contractors often do (for example, “Large cities often run their own programs alongside the state”). On 2026-11-15 replaced the three NPR member-station articles with the CDC’s archived Vaccines.gov FAQ, the President’s remarks of March 11 and April 6, 2021, the White House fact sheet of February 2, 2021 on the Federal Retail Pharmacy Program and the Massachusetts preregistration announcement; cut the unsourced February 24 and May 1 locator dates and the February 18 Massachusetts site failure, and reworded the preregistration sentence to what the announcement states.

  201. · Vaccination status was the easy record; exemptions were the hard one

    Removed or reworded unsourced statements about what most or many organizations did about vaccination records (for example, “most organizations built it last and least”).

  202. · Vaccination status was the easy record; exemptions were the hard one

    Reworded as our view or as a possibility unsourced statements about what employers and their systems typically or often did (for example, “Systems built in a hurry for status collection often struggled here”).

  203. · In Ukraine’s bank DDoS, the rumor outran the outage

    Removed or reworded as our view unsourced statements about what most or many banks do and about regulatory trends (for example, “Many banks therefore use always-on protection”).

  204. · In Ukraine’s bank DDoS, the rumor outran the outage

    Reworded as our view or as a possibility unsourced statements about what banks, their contracts and attackers typically or often do (for example, “Mitigation contracts often protect the main website”). Replaced The Record, Interfax-Ukraine and CyberScoop with the Ukrainian Ministry of Digital Transformation's briefing notice and Fedorov statement and the White House briefing of February 18, 2022, added the bank incident notification rule and the California regulator's Silicon Valley Bank order, reworded the fake ATM text message passage to what the White House said, and cut unsourced details (PrivatBank's customer count and outage length, the January 14 defacement count, Shields Up, the February 23 wave, the 2020 sound practices paper, the NCUA rule, Killnet, Microsoft's 2023 outage, Rapid Reset and Cloudflare figures and the social media detail of the Silicon Valley Bank run).

  205. · What a nationwide EHR outage at UHS asked of nurses and unit leaders

    Removed or reworded as our view unsourced statements about how widely or how often organizations did something (for example, “Many organizations therefore use planned maintenance windows … as drills”).

  206. · What a nationwide EHR outage at UHS asked of nurses and unit leaders

    Reworded as our view or as a possibility unsourced statements about what hospitals and attackers typically or often do (for example, “A hospital typically runs a laboratory information system”). Replaced the Help Net Security, BleepingComputer and Health-ISAC (via AHA) sources with UHS’s own 10-K, the HHS cybersecurity performance goals page, Microsoft’s TrickBot announcement, the Federal Register proposed rule and the Unified Agenda entry; reworded the Ryuk attribution, ambulance diversion, restoration and financial-impact passages to what UHS and the CISA advisory state; and cut the Düsseldorf, Conti and Health Service Executive, Scripps, CommonSpirit, Ascension, 190 million and Medicare advance-payment details and the hospital-objections claim, which no source here supported.

  207. · UCSF’s ransom decision was shaped long before the attack

    Reworded unsourced statements about what many organizations do and dropped unsourced “increasingly”.

  208. · UCSF’s ransom decision was shaped long before the attack

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “Attackers commonly compress files”). Replaced the Security Affairs and The Record sources with the Justice Department’s January 2021 NetWalker release and the Senate Finance Committee hearing record, added the Middle District of Florida sentencing release and the FBI’s July 2020 NetWalker alert, cut the press-reported negotiation figures, the Michigan State and Columbia College details and the unsourced 190 million figure, and reworded the NetWalker leak-site, business-model and January 2021 action details to what the FBI and Justice Department stated. On 2026-11-15 an independent review (N-145) softened the claim that the partial payment showed ransoms are haggled over, since UCSF said only that it paid a portion, and added that the Change Healthcare screenshots were allegedly from stolen files, as the company’s written answers say.

  209. · A two-year telehealth runway is long enough to build on and too short to bet on

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “Medicare Advantage and commercial contracts, which often follow their own telehealth terms”). Replaced the K&L Gates, McGuireWoods and Holland & Knight alerts with Public Laws 119-37 and 119-75 and the DEA’s Federal Register extension rule, removed the American Action Forum summary, and reworded the unsourced claim about how CMS handled the January lapse to what the law and CMS’s telehealth FAQ state.

  210. · Two privacy laws on, one rulebook paused: compliance by capability map

    Removed or reworded as our view unsourced statements about what most organizations or many firms do (for example, “Most organizations first meet a new privacy law as a deadline”), and an unsourced statement about how a lawsuit was widely described.

  211. · Two privacy laws on, one rulebook paused: compliance by capability map

    Reworded as our view or as a possibility unsourced statements about what organizations and their vendors typically or often do (for example, “because their vendors often are covered”).

  212. · Twelve hours to report: the pipeline directive that set the clock for everyone

    An earlier version said CISA held town hall meetings on the CIRCIA rule in early 2026. CISA held them from June 15 to June 18, 2026, after funding lapses held up its rulemaking, and the text now says so.

  213. · Twelve hours to report: the pipeline directive that set the clock for everyone

    Removed unsourced statements about what many organizations did and which frameworks most regulators recognize (for example, “Many organizations map their controls to the NIST Cybersecurity Framework, which most regulators recognize”).

  214. · Twelve hours to report: the pipeline directive that set the clock for everyone

    Reworded as our view or as a possibility unsourced statements about what organizations and their lawyers typically or often do (for example, “Lawyers often want incident work routed through outside counsel”).

  215. · Trust nobody owned: the expired root certificate and hospital legacy clients

    Removed or reworded unsourced statements about how widely components were used and what many or most hospitals do (for example, “Many hospitals already ask device manufacturers for the Manufacturer Disclosure Statement”).

  216. · Trust nobody owned: the expired root certificate and hospital legacy clients

    Reworded as our view or as a possibility unsourced statements about what hospitals, vendors and IT teams typically or often do (for example, “Hospitals often turn that automatic update off”).

  217. · Treasury’s breach ran through a remote-support key the agency never held

    Removed or reworded unsourced statements about what most organizations have and trends in oversight (for example, “four controls most organizations only partly have”) as conditions or our view.

  218. · Treasury’s breach ran through a remote-support key the agency never held

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “IT operations usually buys the tools”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “Remote support tools tend to fall between chairs.”). Replaced the TechCrunch and two BleepingComputer sources with the Senate Banking ranking member’s letter to Treasury, Treasury’s January 2025 sanctions release (jy2792) and the Justice Department’s March 2025 charges, and added BeyondTrust’s own investigation page and CISA’s known exploited vulnerabilities catalog; reworded the intrusion details, the December 5 and 8 dates and the Silk Typhoon link to what those sources say, and cut the unsourced detail that the Office of Foreign Assets Control was among the offices hit, the unclassified documents wording and the CISA and FBI involvement statement. On 2026-11-15 an independent review (N-143) removed the name of the sanctioned and charged individual, in line with our rule against naming private individuals.

  219. · In the Treasury payment access dispute, “read-only” was a claim until the records proved it

    Reworded unsourced statements about what most or many organizations find or own (for example, “Most organizations only discover those mechanics in private”) as conditions.

  220. · In the Treasury payment access dispute, “read-only” was a claim until the records proved it

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “A county or city treasury often has the thinnest staff”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “their access tends to be the broadest”). Replaced The Hill report (via Yahoo News) and the two Civil Rights Litigation Clearinghouse case pages with the D.C. district court’s opinions of March 7, 2025 and March 5, 2026 (govinfo) and the New York court’s February 21, 2025 opinion, added the February 8 restraining order and the Oregon Department of Justice case tracker, reworded the interim order, modified restraining order, declaration and later injunction history to what those records state, added the March 2026 summary judgment, and cut the unsourced report of a departing career official, the letters to Congress, the Kansas City and maintenance-contractor details and the March 7 and April 11 New York orders.

  221. · Travelex’s outage was every white-label bank’s outage

    Removed or reworded as our view unsourced statements about what most or many banks do (for example, “Most banks sort their suppliers into tiers”) and dropped unsourced “widely” and “increasingly”.

  222. · Travelex’s outage was every white-label bank’s outage

    Reworded as our view or as a possibility unsourced statements about what banks, providers and attackers typically or often do (for example, “Banks often negotiate a separate, higher cap”). Replaced the Reuters (Insurance Journal) and BankInfoSecurity sources with Travelex’s own 2 March 2020 market statement and CISA advisory AA20-010A, added the Federal Reserve’s 2021 incident-notification release and the ESAs’ 2025 critical-provider designation, and cut the unsourced Sodinokibi attribution, Metropolitan Police date, named banks, BBC ransom and data claims, ICO comment, researcher and Bad Packets claims, NCSC warning, trade-press delay, Finablr share suspension and Wall Street Journal ransom-payment report.

  223. · TransUnion won Ramirez, and name-only matching still lost

    Reworded unsourced statements about standard practice and what many or most banks do (for example, “Many banks bring screening tools under the same model risk management framework”) as conditions or advice.

  224. · TransUnion won Ramirez, and name-only matching still lost

    Added to the hindsight that SR 11-7 and OCC Bulletin 2011-12 were superseded on April 17, 2026, by SR 26-2 and OCC Bulletin 2026-13.

  225. · TransUnion won Ramirez, and name-only matching still lost

    Reworded as our view or as a possibility unsourced statements about what banks, fintechs and screening teams typically or often do (for example, “Most commercial screening tools blend the two”).

  226. · TraderTraitor aimed fake job offers at the engineers who hold the keys

    Removed or reworded unsourced statements about what most or many firms do (for example, “Most firms find at least one step nobody owns”).

  227. · TraderTraitor aimed fake job offers at the engineers who hold the keys

    Reworded as our view or as a possibility unsourced statements about what firms, engineers and attackers typically or often do (for example, “Engineers often sign in to work tools from personal devices”).

  228. · Why the TRACED Act gave hospitals a two-way phone problem

    Matched the Hospital Robocall Protection Group report on telephone denial-of-service attacks: such an attack “may involve caller ID spoofing,” and extortion is “more common” than simple disruption, instead of saying the calls are often spoofed and often tied to extortion; reworded as our view or as possibilities unsourced statements about what usually, often or rarely happens.

  229. · Tornado Cash and the transfers nobody asked for

    Removed or reworded as our view unsourced statements about what many banks do and that blockchain analytics “became a standard part of sanctions programs”.

  230. · Tornado Cash and the transfers nobody asked for

    Reworded as our view or as a possibility unsourced statements about what examiners, institutions and customers usually or often do (for example, “Customers whose transfers were held often called the branch or contact center”).

  231. · ToolShell made patching the easy part of a SharePoint emergency

    Removed or reworded as our view or a condition unsourced statements about how widely or how often organizations did something (for example, “Most agencies finished the first within days”).

  232. · ToolShell made patching the easy part of a SharePoint emergency

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “It has no deadline imposed from outside, which is why it so often slips”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “The costs budgets tend to hide”). On 2026-11-15, removed the ProPublica source, which no text relied on, cut the unsourced Energy Department and NNSA statement, gave Eye Security’s own scan figures, and kept the Eye Security and Microsoft Threat Intelligence sources as those firms’ own findings.

  233. · Three things a delayed federal transition moved at once

    Removed or reworded as our view unsourced statements about how widely or how often organizations did something (for example, “many agencies use the National Archives’ Capstone approach”).

  234. · Three things a delayed federal transition moved at once

    Reworded as our view or as a possibility unsourced statements about what agencies and their staff typically or often do (for example, “Teams often find that each step has an owner”). Replaced the NPR (via WITF) report with GSA’s November 23, 2020 letter, the EveryCRSReport copy with an archived copy of CRS report R46602, and the Partnership for Public Service statement with the Michigan governor’s statement on certification; added the Senate HELP letter, the 9/11 Commission Report, 44 U.S.C. 2911 and OMB memoranda M-22-09 and M-23-07 for claims that had no source; cut the November 7 projection date, the unsourced list of critics, the dated details of the 2024 transition and the unsourced 2025 paragraph, and reworded the 2000 and 2022 law descriptions to what the sources state. On 2026-11-15 an independent review (N-143) corrected “members of Congress” to the one senator whose letter is cited, the ranking member of the Senate health committee.

  235. · Three SEC cyber proposals, three audiences, one rule adopted

    Reworded unsourced statements about what most or many firms do or find (for example, “Most firms rely on outside companies for everything from customer statements to cloud hosting”).

  236. · Three SEC cyber proposals, three audiences, one rule adopted

    Reworded as our view or as a possibility unsourced statements about what broker-dealers, advisers, providers and attackers typically or often do (for example, “A firm with a few dozen staff rarely has in-house forensic capability”). Sourced the July 2024 CrowdStrike outage to CISA’s alert and Microsoft’s estimate of 8.5 million devices, and replaced an unsourced statement that it hit banks and brokerages with Microsoft’s description of those affected.

  237. · Three seats at ICBC’s ransomware attack, and the plan each one needed

    Reworded unsourced statements about what most or many firms, boards and attackers do (for example, “For most companies, ransomware is a painful outage”) and removed “widely reported”.

  238. · Three seats at ICBC’s ransomware attack, and the plan each one needed

    Reworded as our view or as a possibility unsourced statements about what broker-dealers, clearing firms and attackers typically or often do (for example, “Smaller firms with thinner security teams often cannot”). Sourced the July 2024 CrowdStrike outage to Microsoft’s estimate of 8.5 million devices and replaced an unsourced statement that it hit banks and market participants with Microsoft’s description of those affected. Replaced the Associated Press (via NY1) source with the Financial Stability Oversight Council’s 2023 annual report and the Mondo Visione copy with SIFMA’s own press release; reworded the opening and coordination account to the Council’s report and cut the unsourced LockBit attribution, Emsisoft figures, Boeing incident, details of ICBC Financial Services’ statement, settlement-bank debt and parent capital, firms disconnecting, and Treasury and Secretary Yellen’s remarks.

  239. · The tool that checked for supply-chain risk was the supply-chain risk

    Removed or reworded as our view or a condition unsourced statements about how widely or how often organizations did something (for example, “most organizations write only a small fraction of the code they run”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “The weaker ones tended to share a handful of habits:”). Replaced the Wiz and Akamai research posts with Checkmarx’s and Telnyx’s own incident notices, attributed the late-February credential and payload details to Aqua’s and LiteLLM’s own advisories, and cut the Sophos-sourced claim that harvested credentials were used by a ransomware operation.

  240. · The scammers’ window: patient communication when a hospital goes dark

    Removed or reworded as our view or a condition unsourced statements about how widely or how often organizations did something (for example, “Most organizations use one identity system for nearly everything”).

  241. · The scammers’ window: patient communication when a hospital goes dark

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “Outage communication is usually filed under public relations”). On 2026-11-15, replaced the Chief Healthcare Executive and TechTarget articles with Kettering Health’s own outage updates and incident FAQ, removed the GovInfoSecurity and HIPAA Journal articles, corrected the scam-call warning to May 20 and added Kettering’s note that the calls had not been linked to the outage, reworded the attribution, data and recovery passages to what Kettering stated, and cut the unsourced facility counts, 72-hour threat, leaked-file details, June 3 statement, 1.7 million count, notification timeline and lawsuit report.

  242. · The paper card that made Key to NYC’s digital pass work

    Reworded an unsourced trend statement (“Banks and insurers increasingly accept digital proofs of identity”).

  243. · The paper card that made Key to NYC’s digital pass work

    Reworded as our view or as a possibility unsourced statements about what agencies and people typically or often do (for example, “People lose phones far more often than they lose wallets”). On 2026-11-15 replaced the NPR (GPB) article with the Mayor’s Office transcript of the August 3, 2021 announcement, reworded the dates and the “first” claim to what the mayor said, and cut the unsourced San Francisco and New Orleans sentence.

  244. · The control system map most operators did not have

    Reworded unsourced statements about what many organizations do or find hardest and dropped unsourced “widely” and “increasingly”.

  245. · The control system map most operators did not have

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “IT security teams often lack visibility of control systems”). Replaced the Industrial Cyber and ABC Action News sources on the 2021 Oldsmar incident with CISA advisory AA21-042A and Senator Warner’s February 2021 press release, reworded the account to what they state and cut the unsourced report that the former city manager blamed employee error.

  246. · Test tenants are production when their apps can reach production

    Reworded unsourced statements about how most organizations classify identities and how many organizations use Microsoft 365.

  247. · Test tenants are production when their apps can reach production

    Reworded as our view or as a possibility unsourced statements about what health systems, agencies and IT teams typically or often do (for example, “Health systems often exempt shared clinical workstation accounts”).

  248. · After the emergency, telehealth’s rules landed on clinicians one deadline at a time

    Removed or reworded unsourced statements about what most organizations and many states did (for example, “Most organizations now run calls through cloud telephony, softphones and mobile apps”).

  249. · After the emergency, telehealth’s rules landed on clinicians one deadline at a time

    Reworded as our view or as a possibility unsourced statements about what clinics, hospitals and telehealth companies typically or often do (for example, “A federally qualified health center or a rural clinic often had one administrator”). Replaced the K&L Gates and Mintz client alerts with Public Laws 119-37 and 119-75 on govinfo, reworded the January 2026 lapse to the dates in those laws and cut the unsourced statement that CMS told contractors to return telehealth claims. On 2026-11-15 an independent review (N-145) replaced the unsourced statement that CMS paid telehealth claims as if there had been no lapse with what Public Law 119-37 says (it moved the September 30, 2025 end date to January 30, 2026).

  250. · Telehealth’s three policy clocks all ran down in December, so virtual care needed an annual cycle

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “Patients who rely on audio-only care, often older or without reliable broadband”). On 2026-11-15 we replaced the Foley & Lardner, American Physical Therapy Association and Hooper, Lundy & Bookman sources with Public Laws 119-37 and 119-75 and the DEA and HHS fourth temporary extension in the Federal Register, added Public Laws 118-158 and 119-4 for the 2024 and 2025 extensions, corrected the date of the fourth DEA extension to December 31, 2025, stated each extension’s end date, and cut the unsourced shutdown framing and claims about how visits were converted, rescheduled or held for billing.

  251. · Systems contained, data exposed: why Columbus’s reassurance outran its evidence

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “Large incidents often set up a joint information center”). Replaced the Columbus Navigator, two BleepingComputer and WOSU sources with the city’s October 4, 2024 cybersecurity bulletin, the city attorney’s August 29 and September 11, 2024 statements, the Maine attorney general’s record of the city’s notice (500,000 people), and added the CISA Rhysida advisory and the city’s August 1 employee credit monitoring notice; cut the auction details (6.5 terabytes, 30 bitcoin, listing contents), the leak size, the mayor’s mid-August claim, the complaint details, the October dismissal, the notice data list and the unsourced MS-ISAC funding change, and added the city’s own October 2024 cost figures. On 2026-11-15 an independent review (N-143) removed the name of the security researcher, a private individual.

  252. · Synnovis put a price on pathology consolidation that no contract carried

    Removed unsourced statements about trends and how widely a figure was cited (for example, “increasingly the more important part”); where the point is our analysis, it now says so.

  253. · Synnovis put a price on pathology consolidation that no contract carried

    Reworded as our view or as a possibility unsourced statements about what health systems, suppliers, contracts and boards typically or often do (for example, “Exit clauses usually assume an orderly handover”). Sourced the July 2024 CrowdStrike outage to Microsoft’s estimate of 8.5 million affected devices. Replaced the Infosecurity Magazine source with the government’s written statement to Parliament of 12 November 2025 and the managed service providers factsheet with the critical suppliers factsheet that holds the Synnovis case study, replaced the unsourced NHS England tallies with the government’s figure of over 11,000 delayed appointments, and cut unsourced statements about the 190 million Change Healthcare figure, the HIPAA Security Rule proposal and incident-reporting deadlines.

  254. · SVB’s depositors learned their bank was an unassessed supplier

    Removed or reworded as our view unsourced statements about what many or most organizations and banks did or could do (for example, “Most organizations cannot draw this map on demand”).

  255. · SVB’s depositors learned their bank was an unassessed supplier

    Reworded as our view or as a possibility unsourced statements about what companies and their banks typically or often do (for example, “Third-party risk programs usually live in procurement, security or compliance”).

  256. · What a supply chain label on a U.S. AI vendor asked of agencies and contractors

    Removed or reworded as our view or a condition unsourced statements about how widely or how often organizations did something (for example, “Many organizations also hold Defense work”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “which tends to produce over-compliance”). Replaced the Nextgov/FCW article, the Civil Rights Litigation Clearinghouse summary, the CourtListener copy of the final relief order and the A&O Shearman and Miller & Chevalier alerts with the district court’s preliminary injunction and summary judgment opinions on govinfo and the D.C. Circuit’s own opinion; reworded the August 27 ruling to what the court’s opinion states and cut the law-firm report about SAM listings.

  257. · Supervisory correspondence: a bank’s most candid file, held in a system it cannot assess

    Removed an unsourced trend word (“increasingly”) from the description of what examiners look at.

  258. · Supervisory correspondence: a bank’s most candid file, held in a system it cannot assess

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “Banks often answer a request list by exporting whole reports”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “tends to have these in place.”). On 2026-11-15, replaced the Cornell Legal Information Institute copy of 12 CFR 4.36 with the eCFR.

  259. · Stryker’s wipe made a supplier’s admin console a hospital supply risk

    Removed or reworded as our view or a condition unsourced statements about how widely or how often organizations did something (for example, “many organizations had not switched them on”). Replaced the two MedTech Dive articles and the BleepingComputer report with Stryker’s March 12 and July 30 SEC filings and the Justice Department’s March 19 release on Handala; reworded the press account of the attack method to what CISA’s alert states, and cut the unsourced Mako, manual-ordering, ransom-demand and summer-backlog details. On 2026-11-15 an independent review (N-145) replaced a direct quotation of Stryker’s chief executive with a paraphrase of what the July 30 filing reports him saying.

  260. · Storm-0558’s post-mortem described three key failures every agency development team can repeat

    Reworded unsourced statements about what many agencies do and how often a control is skipped (for example, “Many agencies already track TLS certificates”).

  261. · Storm-0558’s post-mortem described three key failures every agency development team can repeat

    Reworded as a possibility unsourced statements about what organizations and vendors typically or often do (for example, “their documentation is often vague on exactly this point”).

  262. · Why a stolen DMV file weakened identity checks at agencies that were never breached

    Removed or reworded as our view unsourced statements about adoption and trends (for example, “Vendors and researchers increasingly reported attempts to defeat them” and “Most agencies buy identity verification as a service”).

  263. · Why a stolen DMV file weakened identity checks at agencies that were never breached

    Reworded as our view or as a possibility unsourced statements about what agencies, residents and fraudsters typically or often do (for example, “agencies rarely reissue numbers after a breach”). Sourced the NIST 2019 face recognition evaluation to NIST’s own release and described its findings as NIST does. Replaced the WWNO, teiss and The Record sources with Louisiana’s official breach notice and protection steps on NextSteps.La.Gov, Oregon DMV’s data breach page and CalPERS’s notice letter filed with the California Attorney General; reworded the Oregon, Louisiana and CalPERS details to what those notices state and cut the unsourced six million record count, the CalPERS data fields, the PBI client note, the $10 million reward, the Emsisoft tally and “issue dates” in the dek.

  264. · States could build Medicaid work requirements from the statute before the rule arrived

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “are often visible in data the state already holds”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “The scrambling state tends to make the same errors:”).

  265. · The 2026 state privacy laws split institutional exemptions from data exemptions

    Removed or reworded as our view or a condition unsourced statements about how widely or how often organizations did something (for example, “Most banks and health systems carry a short answer to state privacy laws”).

  266. · The 2026 state privacy laws split institutional exemptions from data exemptions

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “The contract point is often missed”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “tended to find the gap through”).

  267. · State AI law after the 99-to-1 vote: build for notice, explanation and human review

    Added to the hindsight that SR 26-2 superseded SR 11-7 on April 17, 2026, and that Colorado SB 26-189, signed on May 14, 2026, repealed and reenacted the AI Act before its June 30, 2026 date, with developer duties from January 1, 2027; put the description of SR 11-7 as current guidance in the past tense.

  268. · State AI law after the 99-to-1 vote: build for notice, explanation and human review

    Removed or reworded as our view or a condition unsourced statements about how widely or how often organizations did something (for example, “For most banks, health systems and agencies”). The model risk sentence now cites OCC Bulletin 2026-13, which records that the OCC, the Federal Reserve and the FDIC issued updated interagency guidance on April 17, 2026, rescinding the 2011 guidance (OCC Bulletin 2011-12 and SR 11-7).

  269. · State AI law after the 99-to-1 vote: build for notice, explanation and human review

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “An examiner or state attorney general investigating a complaint will usually ask for the same records”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “which customers rarely object to”).

  270. · Stablecoin rules late, statutory clock on time: the GENIUS Act’s awkward first year

    Removed or reworded as our view or a condition unsourced statements about how widely or how often organizations did something (for example, “the one many banks will meet through customers”).

  271. · Stable is a claim: what TerraUSD asked of bank front lines

    Removed unsourced statements about how many banks and credit unions held UST and which question customers asked most often (for example, “Most banks and credit unions had no direct exposure to UST”).

  272. · Stable is a claim: what TerraUSD asked of bank front lines

    Reworded as our view or as a possibility unsourced statements about what banks, customers and scammers typically or often do (for example, “Victims are often told to keep the process secret”).

  273. · Spring4Shell rewarded hospitals that could size a response in hours

    Removed or reworded as our view unsourced statements about how widely software is used and what many hospitals and organizations did (for example, “Spring4Shell, for most hospitals, belonged in the focused tier”).

  274. · Spring4Shell rewarded hospitals that could size a response in hours

    Reworded as our view or as a possibility unsourced statements about what hospitals and their vendors typically or often do (for example, “Vendors must often approve the fix”). Attributed the Mirai botnet finding to Trend Micro, reworded the claim about other Java servers to what Spring's advisory says (Payara and Glassfish), added Spring's CVE-2022-22968 advisory, the Cyber Safety Review Board's Log4j report, the FDA's cyber device page and the HIPAA Security Rule proposal as sources, and cut unsourced statements about HHS performance goals, the National Vulnerability Database backlog, the CVE program contract, Broadcom's acquisition of VMware and the end of Spring Framework 5.3 support.

  275. · Someone else’s lawsuit, your contracts: how the Times case reached regulated AI buyers

    Removed or reworded unsourced statements about what many organizations, credit unions and health systems did or usually do (for example, “Many organizations discovered that their most widely used AI features came through this route”).

  276. · Someone else’s lawsuit, your contracts: how the Times case reached regulated AI buyers

    Reworded as a possibility unsourced statements about what software vendors typically or often do (for example, “Vendors with many regulated customers often have such an addendum ready”). Replaced the Associated Press (via PBS), ChatGPT Is Eating the World and Kilpatrick Townsend sources with the Times’s complaint, the June 23, 2025 fair use order in Bartz v. Anthropic, OpenAI’s statement on the preservation order and the court-authorized Anthropic settlement website and notice; updated the settlement to its $1.5 billion fund and July 2026 final approval, reworded its terms to the notice, and cut the unsourced multidistrict proceeding, October 2025 hearing and 500,000-work count, and added OpenAI’s January 2024 response as the source for its statements.

  277. · SolarWinds and the three assumptions behind every update policy

    Removed or reworded as our view unsourced statements about how widely or how often organizations did something (for example, “Many agencies had not deployed endpoint detection and response tools”).

  278. · SolarWinds and the three assumptions behind every update policy

    Reworded as our view or as a possibility unsourced statements about what agencies, banks and their teams typically or often do (for example, “Agencies that made the changes stick usually gave the tools an explicit security owner”). Added CrowdStrike’s January 11, 2021 technical analysis as the source for the description of the tool used on SolarWinds’ build server. Replaced a law-firm blog (Covington & Burling’s Inside Privacy) with the joint stipulation dismissing the SEC’s SolarWinds case, published by the SEC, and reworded the account of the case to what it states: the July 2024 ruling granted the motion to dismiss in part and denied it in part, and the November 2025 dismissal was with prejudice. Removed the unsourced statements of what the SEC had alleged and that most of its claims did not survive. Replaced CrowdStrike’s SUNSPOT analysis with SolarWinds’ own January 11, 2021 update, which also supports the September 2019 and October 2019 timeline, reworded the build-tool description to what SolarWinds stated, and cut the unsourced description of FireEye’s second-stage dropper finding. On 2026-11-15 an independent review (N-145) reworded the statement that a developer reviewing the source would have seen nothing wrong to what SolarWinds said (the tool was designed not to arouse the suspicion of its development and build teams).

  279. · Snowflake’s stolen logins put the contractor’s laptop inside the bank’s perimeter

    Reworded unsourced statements about what most or many firms and organizations do (for example, “Most firms rely on outside talent for data work”) and removed “widely reported”.

  280. · Snowflake’s stolen logins put the contractor’s laptop inside the bank’s perimeter

    Reworded as our view or as a possibility unsourced statements about what firms, contractors and attackers typically or often do (for example, “The old password accounts often lingered, out of sight”). Attributed the findings on single-factor accounts and on Snowflake’s own environment to Mandiant’s published analysis, the source listed; the earlier text also attributed them to CrowdStrike and Snowflake without a source. Sourced Snowflake’s June 2, 2024 statement to the joint statement it posted with CrowdStrike and Mandiant (archived copy of Snowflake’s security hub, now listed) and described it as that statement does: a campaign aimed at users with single-factor authentication, no evidence of a vulnerability, misconfiguration or breach of Snowflake’s platform, and a former employee’s demonstration accounts reached because they were not behind Okta or multifactor authentication. The paragraph had given Mandiant’s findings in place of the statement it described. Sourced Santander’s May 2024 disclosure to the bank’s own statement of May 14, 2024, and replaced “customers in several countries and on staff” with what the statement says: customers of Santander Chile, Spain and Uruguay, and all current and some former group employees. Kept the Mandiant report for findings the text attributes to Mandiant, added the Justice Department’s August 2026 plea release for the arrests and the 165 affected customers, and cut unsourced statements naming Snowflake as AT&T’s platform and naming Advance Auto Parts, Neiman Marcus and QuoteWizard as victims; we also added the SEC’s Regulation S-P release for the compliance dates and cut an unsourced statement about the date New York’s MFA requirement took effect.

  281. · Small-dollar loans, alternative data and the governance attached

    Removed unsourced statements about what most or many institutions did (for example, “Many institutions also reduced or eliminated overdraft fees”) and an unsourced statement that cash-flow underwriting gained ground.

  282. · Small-dollar loans, alternative data and the governance attached

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “Vendors often resist sharing methodology”). Replaced the EveryCRSReport copy of CRS report IF13117 with the Congressional Research Service’s own copy.

  283. · For a small adviser, Regulation S-P compliance is bought before the breach

    Removed or reworded as our view or a condition unsourced statements about how widely or how often organizations did something (for example, “Most firms will find the items already exist”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “as compliance dates usually do”).

  284. · SitusAMC turned a mid-tier mortgage vendor into a top-tier bank exposure

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “Lower tiers get lighter checks, often little more than a questionnaire at onboarding”). On 2026-11-15, replaced the HousingWire article with an Internet Archive copy of SitusAMC’s own breach statement, and the Bloomberg Law and National Mortgage News articles with the court-authorized settlement notice and SitusAMC’s January 2026 notice template filed with the California Attorney General; cut the press-reported bank names and FBI statement, and reworded the settlement timing and the dates of the individual letters to what those documents show.

  285. · Shutdown plans counted people; agency systems depended on contracts and expiry dates

    Updated the text to say that BOD 22-01 applied at the time and that CISA revoked it on June 10, 2026, replacing it with BOD 26-04.

  286. · Shutdown plans counted people; agency systems depended on contracts and expiry dates

    Reworded unsourced statements about what most or many agencies did (for example, “many agencies filed their plans away”).

  287. · Shutdown plans counted people; agency systems depended on contracts and expiry dates

    Reworded as our view or as a possibility unsourced statements about what federal agencies typically or often do (for example, “Agencies often buy cloud computing in advance”). Replaced the EveryCRSReport mirror with the Congressional Research Service’s own copy of report R48874 on Congress.gov.

  288. · Shields Up had no end date, so vigilance needed a staffing plan

    Removed or reworded as our view unsourced statements about what many or most organizations did (for example, “Most organizations planned how to raise their posture”).

  289. · Shields Up had no end date, so vigilance needed a staffing plan

    Reworded as our view or as a possibility unsourced statements about what organizations and their providers typically or often do (for example, “Health systems often ran lean security teams”). Replaced ESET's HermeticWiper post with the UK government's May 10, 2022 attribution of the KA-SAT attack (the HermeticWiper disclosure is covered by CISA and FBI advisory AA22-057A), added Treasury's February 22, 2022 sanctions release, and reworded the German wind turbine claim to what the UK statement says (wind farms in central Europe were disrupted).

  290. · Section 524B gave hospitals a baseline to buy against

    Removed or reworded unsourced statements about what many hospitals had and about SBOMs becoming standard (for example, “SBOMs became a standard part of new cyber device submissions”, now stated as the Section 524B requirement).

  291. · Section 524B gave hospitals a baseline to buy against

    Reworded as our view or as a possibility unsourced statements about what device makers and hospitals typically or often do (for example, “Manufacturers often say that if a hospital installs its own updates, validation is void”).

  292. · Secrets in a public docket: the court filing breach and where the sensitive tier ends

    Removed or reworded as our view or a condition unsourced statements about how widely or how often organizations did something (for example, “Most organizations classify records by legal status”).

  293. · Secrets in a public docket: the court filing breach and where the sensitive tier ends

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “Those relying on legal labels usually cannot”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “The tiers that fail tend to share the opposite traits.”).

  294. · What a second CISA lapse in five months asked state and local security teams to own

    Removed or reworded as our view or a condition unsourced statements about how widely or how often organizations did something (for example, “Cyber insurers increasingly ask”). Replaced the UPI, BankInfoSecurity and Washington Examiner articles and the EveryCRSReport mirror with the Senate roll call record, the April 3 presidential memorandum and CRS reports R48874 and R49105 on congress.gov; corrected the lapse length to 76 days, reworded the mid-April “recall” to the pay directive the memorandum states, and cut the unsourced immigration-dispute detail, the 12:01 a.m. time and the reported loss of more than 1,000 CISA employees.

  295. · Under the SEC’s final cyber rule, the clock starts at a decision, so the decision needs a record

    Reworded as conditions or our view unsourced statements about what most or many companies do (for example, “Most companies keep the determination with management”).

  296. · Under the SEC’s final cyber rule, the clock starts at a decision, so the decision needs a record

    Reworded as our view or as a possibility unsourced statements about what companies, insurers and attackers typically or often do (for example, “Finance teams often want a numeric threshold”). Replaced a law-firm blog (Covington & Burling’s Inside Privacy) with the joint stipulation dismissing the SEC’s SolarWinds case, published by the SEC, and reworded the account to what it states: the July 2024 ruling granted the motion to dismiss in part and denied it in part (not “dismissed most of the claims”), and the November 2025 dismissal was agreed with the defendants and with prejudice.

  297. · Describe your board’s cyber oversight in a filing, and you have made a promise

    Removed or reworded as our view unsourced statements about what many or most companies did and about trends in due diligence (for example, “Many companies placed cyber oversight with the audit committee”).

  298. · Describe your board’s cyber oversight in a filing, and you have made a promise

    Reworded as our view or as a possibility unsourced statements about what companies and their staff typically or often do (for example, “Disclosure is usually drafted by legal, finance and investor relations staff”).

  299. · Searching by balance: how bribed bank insiders choose their targets

    Removed or reworded as our view or a condition unsourced statements about how widely or how often organizations did something (for example, “In many banks that is easy”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “rarely blames the criminal alone”).

  300. · Sea-Tac’s handwritten signs were a staffing plan in disguise

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “Public-sector ransomware recoveries have often run for weeks”). Replaced the two Seattle Times sources with the Port of Seattle’s cyberattack update archive and its December 2024 blog post on staff and volunteers (Internet Archive copies), and reworded the outage details to what the Port states: the list of affected services, ticketing and check-in handled manually at shared gates, staff using pen, paper and handwritten signs, arrival advice of two hours for domestic and three for international flights, displays showing every airline again on September 11 and website work still under way on September 13; cut handwritten boarding passes and Alaska Airlines staff sorting bags by hand, which the Port does not state. On 2026-11-15 an independent review (N-145) changed the title from handwritten boarding passes to handwritten signs, which is what the Port states.

  301. · Schrems II and the case for deciding where data lives first

    Reworded unsourced statements about what most or many organizations did (for example, “With Privacy Shield gone, most organizations moved to standard contractual clauses”) and removed unsourced “increasingly”.

  302. · Schrems II and the case for deciding where data lives first

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “Records of processing written for general privacy compliance often lacked the detail”). Replaced the American Journal of Transportation copy of Secretary Ross’s statement with an Internet Archive copy of the commerce.gov original and the PPC Land source with the General Court’s press release No 106/25, and reworded the challenger’s description to what the court states (a French citizen). On 2026-11-15 an independent review (N-145) removed the challenger’s name from the text, since the court describes him as bringing the case as a private citizen.

  303. · Saline exposed the risk that hides in a hospital’s cheapest line items

    Removed or reworded unsourced statements about what most hospitals and health systems do or received (for example, “most hospitals were receiving well under their normal supply”, now stated as Baxter’s allocation levels).

  304. · Saline exposed the risk that hides in a hospital’s cheapest line items

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “Space is often the binding constraint”). On 2026-11-15 we replaced the NPR source with CDC’s October 2024 health advisory and rewrote the conservation passages to what it recommends, added the FDA’s 2017 Hurricane Maria notice and the CMS fiscal year 2025 inpatient rule fact sheet, removed the February 17, 2025 Baxter update, and cut the unsourced American Hospital Association 60 percent figure, the Inova 55 percent figure, the 2022 contrast media and 2008 heparin examples, the January 28, 2025 restart date, the Civica Rx details, the 2023 antitrust policy withdrawal and statements that orders shifted to other makers and that nurses raised concerns. On 2026-11-15 an independent review (N-145) reworded as a possibility the list of other conservation options, which the CDC advisory does not state.

  305. · Safe harbor for researchers, homework for system owners

    Removed or reworded unsourced statements about what many or most agencies and states do and about trends in oversight (for example, “Auditors, legislators and journalists increasingly ask whether public bodies have disclosure policies”).

  306. · Safe harbor for researchers, homework for system owners

    Reworded as our view or as a possibility unsourced statements about what state and local agencies typically or often do (for example, “Separately elected officials often control their own systems”).

  307. · Russia’s sanctions tested banks’ ownership data more than their name lists

    Removed or reworded unsourced statements about what most or many institutions do (for example, “Most institutions buy their list data, screening software and much of their ownership data from vendors”).

  308. · Russia’s sanctions tested banks’ ownership data more than their name lists

    Reworded as a possibility unsourced statements about what banks and payment firms typically or often do (for example, “Fintechs and payment firms often depended on a sponsor bank”).

  309. · Rural health transformation money runs on three clocks, and only two of them come with funding

    An earlier version said CMS had yet to announce second-year allocations and that it had said they would come by the end of October. CMS announced $10 billion in second-year awards on November 9, 2026; the text now says so and no longer repeats the end-of-October timing, which we could not confirm on a CMS page.

  310. · Rural health transformation money runs on three clocks, and only two of them come with funding

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “For a small hospital this is often the only IT expertise it has”). Replaced the IdahoNews.com source with CMS’s funding notice and added CMS’s program FAQ; the budget-period dates, spending caps and redistribution rule now cite CMS, KFF is kept only for its own description of October 30 as the obligation deadline, and unsourced claims attributed to state summaries, advisory firms and press reporting about how states were meeting the deadline were cut or recast as possibilities. On 2026-11-15 an independent review (N-145) removed a second introduction of KFF and reworded as a possibility the statement that a state can meet the October 30 date by committing money to other state agencies, which the cited CMS documents do not address.

  311. · Rogers: the bank outage that started at someone else’s carrier

    Removed or reworded unsourced statements about what most or many banks do and about supervisory trends (for example, “Many banks had dual carriers for data centers but single carriers for smaller branches”).

  312. · Rogers: the bank outage that started at someone else’s carrier

    Reworded as our view or as a possibility unsourced statements about what banks and credit unions typically or often do (for example, “A credit union usually reaches the same networks through a shared service provider”). Replaced the CBC report with the CRTC's July 12, 2022 letter to Rogers, the Rogers MOU statement with the industry minister's statement, and the EIOPA DORA page with OSFI's Guideline B-13 letter, added the CRTC's independent assessment, the FCC's AT&T outage report and CISA's CrowdStrike alert, reworded the Interac, Rogers credit and network separation passages and the review findings to what those sources say, and cut unsourced details (the House of Commons hearing, redacted filings, the April 2021 outage, the number of MOU signatories, the Shaw deal, the cost of separating the cores, outage reporting rules, the Optus outage, OSFI E-21, US third-party guidance, DORA and the UK critical third parties regime).

  313. · Robinhood’s phone-call breach argues for support access sized to one customer

    Reworded unsourced statements about what most or many firms do (for example, “Most firms now use single sign-on”) as conditions or our view.

  314. · In the RIBridges breach, Rhode Island owned the outage and its vendor owned the evidence

    Marked an unsourced statement about which decision right is most often contested as our view.

  315. · In the RIBridges breach, Rhode Island owned the outage and its vendor owned the evidence

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “security monitoring, logs and alerts often sit entirely with the vendor”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “tend to arrive after an incident, and they ask”). Replaced the GovInfoSecurity, Cybersecurity Dive and Ocean State Media sources with the governor’s RIBridges releases of December 14 and 30, 2024 and February 4, 2025, the state’s RIBridges Alert page, the CrowdStrike investigation summary the state released, the governor’s UHIP report release and Public Law 119-21; replaced the 657,000 estimate with the final count of 644,401, reworded the UHIP history, the law enforcement role, the Deloitte statement, the leak-site details and the reopening of account sign-ups to what those sources state, and cut the unsourced terabyte, ransom-decision and LockBit details, the 1.1 million population figure, the Iowa and MCNA example, the Conduent and PowerSchool examples and the claim that January food and cash payments stayed on schedule. On 2026-11-15 an independent review (N-143) corrected “entered with Deloitte credentials” to what the investigation summary states (it found the intruder signed in to the VPN with an account that was not a State of Rhode Island account and could not determine how the credentials were obtained) and fixed a punctuation error.

  316. · Revoking the AI executive order could not revoke the AI inventory, because Congress had written it

    Marked an unsourced statement about governance at many agencies after the 2025 budget and staff reductions as our view.

  317. · Revoking the AI executive order could not revoke the AI inventory, because Congress had written it

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “An agency official doing the work day to day often could not say which layer a given task came from”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “tend to overspend on those about to disappear”).

  318. · One-time money, recurring bills: the Rescue Plan’s technology hangover

    Removed or reworded as our view unsourced statements about how widely or how often organizations did something (for example, “Many agencies used the money well”).

  319. · One-time money, recurring bills: the Rescue Plan’s technology hangover

    Reworded as our view or as a possibility unsourced statements about what governments, vendors and contracts typically or often do (for example, “Vendors on cooperative contracts often resist changes to standard terms”).

  320. · HIPAA’s reproductive health proposal asked records to know what they hold

    Reworded as our view unsourced statements about what most health systems and organizations do or could do (for example, “OCR was correct that most organizations could not segment records cleanly”).

  321. · HIPAA’s reproductive health proposal asked records to know what they hold

    Reworded as our view or as a possibility unsourced statements about what health systems typically or often do (for example, “An academic medical center usually has an informatics team”).

  322. · Under Regulation S-P, the firm that knows least about a breach tells the most customers

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “Data maps are usually drawn for applications”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “Each tends to fail in a familiar way.”). On 2026-11-15, replaced the Davis Wright Tremaine blog post with the SEC’s Small Entity Compliance Guide for the compliance dates, and cut the unsourced claim that both dates “held”.

  323. · The vendor clock: amended Regulation S-P rests on a 72-hour promise someone else makes

    Reworded as our view unsourced statements about what most firms found and which firms were better placed (for example, “Most firms found the third column the hardest to fill”).

  324. · The vendor clock: amended Regulation S-P rests on a 72-hour promise someone else makes

    Reworded as our view or as a possibility unsourced statements about what investors, vendors and IT providers typically or often do (for example, “Smaller specialist vendors were often willing to sign”). Replaced the Mandiant threat report with Snowflake’s own security updates on the 2024 campaign against its customers’ accounts.

  325. · Records over deference: after Loper Bright, an agency’s best defense sat in its files

    Removed unsourced statements about what many agencies do (for example, “Comment handling in many agencies runs on spreadsheets and email”).

  326. · Records over deference: after Loper Bright, an agency’s best defense sat in its files

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “often treat rulemaking support files as temporary”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “evidence tend to live in shared drives and email”).

  327. · Recordkeeping fails where the approved channel is slower than a text

    Replaced an unsourced statement that many firms agreed to similar undertakings with what the SEC’s September 2022 release says the settling firms agreed to, and reworded as our view two unsourced statements about most firms and executives.

  328. · Recordkeeping fails where the approved channel is slower than a text

    Reworded as our view or as a possibility unsourced statements about what firms and their staff usually or often did (for example, “Firms operating across jurisdictions usually needed different procedures”).

  329. · Rapid Reset sorted agency websites into three groups, and one of them had no owner

    Updated the text to say that BOD 22-01 applied at the time and that CISA revoked it on June 10, 2026, replacing it with BOD 26-04.

  330. · Rapid Reset sorted agency websites into three groups, and one of them had no owner

    Removed or reworded unsourced statements about how widely HTTP/2 and the fixes spread and what many agencies and organizations did (for example, “Rapid Reset was patched widely within weeks”).

  331. · Rapid Reset sorted agency websites into three groups, and one of them had no owner

    Reworded as our view or as a possibility unsourced statements about what state and local governments typically or often do (for example, “State agencies often buy through statewide contracts”).

  332. · Rackspace kept running old Exchange for clients, and kept its old risks

    Reworded unsourced statements about most organizations and about a trend in regulators’ statements (for example, “For most organizations, an email outage is closer to a business stoppage”).

  333. · Rackspace kept running old Exchange for clients, and kept its old risks

    Reworded as our view or as a possibility unsourced statements about what hosting providers, customers and attackers typically or often do (for example, “The customer often keeps its domain”).

  334. · Quantum risk is dated by how long your data must stay secret

    Reworded unsourced statements about what most agencies can do and how widely algorithms are used (for example, “Most agencies can assemble a first pass”).

  335. · Quantum risk is dated by how long your data must stay secret

    Reworded as our view or as a possibility unsourced statements about what agencies typically or often do (for example, “Network equipment is often replaced every five to seven years”).

  336. · The quantum law asked for a price tag agencies could only get from their vendors

    Removed or reworded as our view unsourced statements about how widely algorithms are used and what many agencies or organizations did (for example, “the most valuable early step for many agencies”).

  337. · The quantum law asked for a price tag agencies could only get from their vendors

    Reworded as our view or as a possibility unsourced statements about what agencies and their teams typically or often do (for example, “The security team usually owns the cryptographic inventory”).

  338. · A weekend of public red-teaming showed agencies that AI testing never finishes

    Reworded as our view an unsourced statement that prompt injection “became a standard item in security reviews of AI systems”.

  339. · A weekend of public red-teaming showed agencies that AI testing never finishes

    Reworded as our view or as a possibility unsourced statements about what agencies and their staff typically or often do (for example, “A county or a small state agency usually has none of these”).

  340. · ProxyLogon: the patch was the easy part

    Removed or reworded as our view unsourced statements about how widely or how often organizations did something (for example, “Widely reported estimates put the number of compromised organizations in the United States in the tens of thousands”).

  341. · ProxyLogon: the patch was the easy part

    Reworded as our view or as a possibility unsourced statements about what agencies, insurers and attackers typically or often did (for example, “A county, city, school district or court often had neither”).

  342. · The cyberattack on Prospect Medical ended up on the table in a hospital sale

    Reworded unsourced statements about what most or many hospitals keep for downtime and how ransomware groups were changing (for example, “Most hospitals keep downtime procedures”).

  343. · The cyberattack on Prospect Medical ended up on the table in a hospital sale

    Reworded as our view or as a possibility unsourced statements about what hospital operators, buyers and insurers typically or often do (for example, “A private equity buyer often plans to integrate quickly and resell”). Replaced the HFMA, GovInfoSecurity and CT Mirror sources with Prospect’s own breach notice filed with the California Attorney General, the archived HC3 Rhysida alert, the federal court’s August 2024 opinion in Roma v. Prospect Medical Holdings, Medical Properties Trust’s October 2025 results release and the Office of Health Strategy’s March 2024 statement; attributed the Rhysida claim to the plaintiffs’ allegations recited by the court, reworded the attack, sale, lawsuit and settlement details to what those sources state, and cut unsourced details including the 166 clinics, FBI and website-banner reports, site-by-site outage accounts, the $435 million price, Yale’s $80 million estimate and tax allegation, the grounds of the suit and countersuit, the 1.3 million count, the British Library attack, Yale’s February 2025 withdrawal, the $86.1 million bid and the Crozer closures.

  344. · Triage for a rule that might not survive: the SEC’s private fund adviser package

    Reworded unsourced statements about what many firms do or expected (for example, “The vacatur was wider than many firms expected”).

  345. · Triage for a rule that might not survive: the SEC’s private fund adviser package

    Reworded as our view or as a possibility unsourced statements about what fund advisers typically or often do (for example, “performance calculations, which usually live in yet another set of spreadsheets”).

  346. · Price transparency files: mandated, massive and hard to read

    Removed or reworded as our view unsourced statements about how widely or how often organizations did something (for example, “widely welcomed in principle” and “providers increasingly use them in contract talks”).

  347. · Price transparency files: mandated, massive and hard to read

    Reworded as our view or as a possibility unsourced statements about what employers and health systems typically or often do (for example, “Public employers often run benefits through small human resources teams”).

  348. · Why the Postal Service slowdown belonged on agency risk registers

    Removed or reworded unsourced statements about what most or many agencies do (for example, “the mail, which most agencies treat like water from the tap”) and an unsourced statement that channel resilience is widely accepted by 2026.

  349. · Why the Postal Service slowdown belonged on agency risk registers

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “A print-and-mail vendor usually has a contract with performance terms”). Replaced the Military Times (Associated Press) and KFF sources with the Senate Homeland Security Committee’s August 2020 release on veterans’ prescription delays and GAO report GAO-25-107413, updated the unwinding figures to GAO’s (26.8 million disenrolled, about 70 percent procedural), added CMS letter SHO# 23-002 for the returned-mail conditions, cut the unsourced statement on outdated addresses and reworded the change-of-address sentence to what the letter says.

  350. · Post-quantum signatures are still being chosen, so build PKI to switch twice

    Removed or reworded as our view or a condition unsourced statements about how widely or how often organizations did something (for example, “The world’s most widely used browser”). Replaced the Quantum Computing Report and PostQuantum.com sources with NIST’s round 3 page and TrustAsia’s own application on the Chromium issue tracker, cut the unsourced July 29 withdrawal date, the August 14 deadline and the “first applications” claim, and added NSA’s CNSA 2.0 advisory and the CA/Browser Forum ballot SC081v3 as sources for the signing and certificate-lifetime dates.

  351. · Post-quantum priority starts in the records retention schedule

    Removed or reworded unsourced statements about how widely technologies are used and what most or many organizations do (for example, “OpenSSL is one of the most widely used building blocks”, “a document most organizations already have”).

  352. · Post-quantum priority starts in the records retention schedule

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “senior attention is often the only thing that keeps it funded”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “Applied honestly, that ranking rarely matches”). Removed an unsourced statement that hybrid key exchange spread quickly through browsers and major cloud providers; the post now says only what OpenSSL’s own 3.5 release note states, that the release added ML-KEM, ML-DSA and SLH-DSA.

  353. · Persistence below the patch: what ED 25-03 asked agencies to prove about their firewalls

    Removed or reworded as our view or a condition unsourced statements about how widely or how often organizations did something (for example, “In many agencies the network team”).

  354. · Persistence below the patch: what ED 25-03 asked agencies to prove about their firewalls

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “Version tracking for appliances is often manual”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “That decision has costs agencies tend to underestimate.”).

  355. · Permission to donate cybersecurity arrived without the money to run it

    Reworded as our view or as a possibility unsourced statements about what hospitals, practices and attackers typically or often do (for example, “Donors usually need to renegotiate for third-party use”). Replaced the Health-ISAC (via AHA) and Alston & Bird sources with HHS’s cybersecurity performance goals page and the Unified Agenda entry for the HIPAA Security Rule (final action July 2027), sourced the 192.7 million figure to HHS’s Change Healthcare FAQ and the rural hospital program to Microsoft’s own announcement (no longer attributing it to the White House or Google), and cut the unsourced January 2024 date, “largest health data breach” claim and CMS accelerated-payments sentence.

  356. · Payer prior authorization APIs will only help the providers ready to call them

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “pharmacy and medical authorizations often run through different teams”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “Where readiness usually breaks”).

  357. · Paycheck Protection: capital was easy, intake was hard

    Reworded unsourced statements about what most banks and institutions do (for example, “Most institutions filled these roles informally”).

  358. · Paycheck Protection: capital was easy, intake was hard

    Reworded as our view or as a possibility unsourced statements about what lenders and their teams typically or often did (for example, “Non-bank lenders and fintechs often had the best online intake”). Replaced the Fortune and Journal of Accountancy sources with Treasury and SBA statements of April 17 and April 24, 2020, added the Paycheck Protection Program and Health Care Enhancement Act and the May 13, 2020 PPP FAQs, cut the unsourced reports of E-Tran problems in both rounds, the 60 percent forgiveness threshold, the program's closing dates and the Fed facility's end date, and corrected the date SBA announced reviews of loans over $2 million to April 29. On 2026-11-15 (N-146) the sentence on the PPP Flexibility Act was reworded to what the Act (Public Law 116-142, June 5, 2020) says and sourced to it, in place of the Federal Reserve’s April 6, 2020 announcement, whose content its April 9 release also covers. On 2026-11-15 (N-147) the Wells Fargo paragraph was sourced to the Federal Reserve Board’s April 8, 2020 release and the program terms to SBA’s interim final rule (85 FR 20811), which replace Treasury’s program overview and its April 24 statement; the sentence on companies returning their loans, the unsourced April 10 and April 27 dates, the zero risk weight, the bank lawsuits, the E-Tran outage reports, the forgiveness forms, the House subcommittee and academic findings and the name and date of the 2022 statute of limitations act were cut; the first-round results were reworded to Treasury and SBA’s April 17 statement, and unsourced statements about what lenders did were reworded as our view or as possibilities.

  359. · Patient-directed AI: where HIPAA ends, a provider’s duties change shape

    Removed or reworded as our view or a condition unsourced statements about how widely or how often organizations did something (for example, “Most hospitals and physician practices keep their records”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “a distinction patients rarely see”). Replaced the Fortune article with OpenAI’s own ChatGPT Health announcement (Internet Archive copy) and cut the unsourced detail tying Anthropic’s announcement to the J.P. Morgan Healthcare Conference.

  360. · Patient access is won or lost at the records counter

    Removed or reworded as our view unsourced statements about how widely or how often organizations did something (for example, “Many organizations treated the limit as the target” and “many providers moved in that direction”).

  361. · Patient access is won or lost at the records counter

    Reworded as our view or as a possibility unsourced statements about what health systems, providers and records teams typically or often do (for example, “Release-of-information teams are often small and measured on volume”). Replaced the Alston & Bird client alert with OCR’s Unified Agenda entry for RIN 0945-AA00, which lists the August 2026 final action date, and reworded the agenda reference to match.

  362. · Patch what attackers use: BOD 22-01 and the agency work queue

    Removed or reworded unsourced statements about how widely the catalog was referenced and what many agencies and critics said or did (for example, “one of the most widely referenced public sources in vulnerability management”).

  363. · Patch what attackers use: BOD 22-01 and the agency work queue

    Reworded as our view or as a possibility unsourced statements about what security teams, boards and vendors typically or often do (for example, “Boards often see vulnerability counts that rise and fall without meaning”).

  364. · Password spraying against research labs: an old attack on a new target

    Removed or reworded as our view unsourced statements about what most or many institutions did (for example, “In many institutions that number was large, and few knew it”).

  365. · Password spraying against research labs: an old attack on a new target

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “Labs often run instruments through shared logins”). Replaced the American Hospital Association copy of the May 13, 2020 FBI and CISA announcement with the FBI’s own copy on ic3.gov, and reworded its summary to what the announcement says.

  366. · Part 2’s single consent freed the recipients and bound the source

    Reworded unsourced statements about how the rule was widely summarized, how EHR vendors adopted labels and what most or many organizations do (for example, “most organizations rely on a mix of source-system identifiers”).

  367. · Part 2’s single consent freed the recipients and bound the source

    Reworded as a possibility unsourced statements about what health systems and treatment programs typically or often do (for example, “Health systems often kept Part 2 data in separate systems”). Replaced the CourtListener copy of the Purl judgment with the court’s June 18, 2025 opinion and order on govinfo. On 2026-11-15 (N-146) the description of the June 2025 Purl ruling was reworded to what the court’s opinion and order says (the April 2024 rule vacated except its changes to the notice of privacy practices requirement, made to reflect the CARES Act’s Part 2 changes, apart from three paragraphs), and the unsourced claim that organizations had paused and then resumed their notice updates was cut.

  368. · Why Part 2’s compliance date reached hospitals that never ran a treatment program

    Removed or reworded as our view or a condition unsourced statements about how widely or how often organizations did something (for example, “Many hospitals and health plans kept these records apart”). Replaced the Thomson Reuters (EBIA) and McDonald Hopkins articles with HHS’s February 13, 2026 press release (Internet Archive copy) and the 2024 HIPAA final rule that set the February 16, 2026 notice compliance date, and reworded the hindsight to what the release states.

  369. · Cl0p’s Oracle campaign: an attack on the systems security teams did not run

    Removed or reworded as our view or a condition unsourced statements about how widely or how often organizations did something (for example, “Many organizations found that October”).

  370. · Cl0p’s Oracle campaign: an attack on the systems security teams did not run

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “That design choice is often a decade old and rarely revisited”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “A few direct questions tend to reveal the gaps.”). On 2026-11-15, added Oracle’s security alerts for CVE-2025-61882 and CVE-2025-61884 (for the October 4 and October 11 fixes) and the CISA and FBI advisory AA23-158A on Cl0p’s MOVEit campaign, and attributed the August 9 exploitation date in the hindsight section to Google’s investigators.

  371. · Oracle bought Cerner, and Cerner customers inherited a cloud strategy

    Removed or reworded unsourced statements about trends in interoperability expectations and what many organizations chose for cloud hosting.

  372. · Oracle bought Cerner, and Cerner customers inherited a cloud strategy

    Reworded as our view or as a possibility unsourced statements about what health systems, vendors and customers typically or often do (for example, “Revenue typically dips while billing teams learn new workflows”).

  373. · OPM’s staffing-plan rule tucked a systems certification into a personnel regulation

    Removed or reworded as our view or a condition unsourced statements about how widely or how often organizations did something (for example, “most agencies met that duty by taking part in OPM’s Federal Employee Viewpoint Survey”). Also reworded further unsourced claims about how organizations or people behave (for example, “typically made that case”). Replaced the FEDweek, Government Executive, Nextgov/FCW, FedScoop, MeriTalk and CBS News sources with the final rule’s own comment summary, DDoSecrets’ own description of its publication, the OMB and OPM HR 2.0 memo of December 10, 2025 and OPM’s release on the Oracle award; cut the ACSI satisfaction figures and OPM headcount figure (ACSI’s own release could not be opened), Okta’s and DHS’s press-reported statements, the hiring-fair date, the press-reported June 10 award date and the CBS projection of House control, and the Nextgov/FCW comparison with earlier FBI and Defense Manpower Data Center breaches; the 21.5 million figure for the 2015 OPM breach now cites OPM’s own incidents page. On 2026-11-15 an independent review (N-145) replaced a leftover attribution of the first-wave agency list to MeriTalk with the HR 2.0 memo’s own list, changed “stop” to “pause” to match the memo’s wording, and softened an unsupported statement that the survey drew the most argument in the rulemaking. On 2026-11-15 (N-146) unsourced generalizations about how departments usually or often work (for example, “Payroll is often run by a shared provider” and “Many departments are some distance from this”) were reworded as possibilities or our view.

  374. · Why the useful response to OpenAI’s board crisis was a days-to-switch number

    Reworded as our view an unsourced statement that model gateways and evaluation tooling “became standard elements of enterprise AI platforms”, and two similar unsourced generalizations.

  375. · Why the useful response to OpenAI’s board crisis was a days-to-switch number

    Added to the hindsight that SR 11-7 and OCC Bulletin 2011-12 were superseded on April 17, 2026, by SR 26-2 and OCC Bulletin 2026-13, which leave generative and agentic AI models out of scope, and put descriptions of SR 11-7 as current guidance in the past tense.

  376. · Why the useful response to OpenAI’s board crisis was a days-to-switch number

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do when they change AI providers (for example, “Portability is usually lost in small ways”). Replaced the Associated Press (via NBC Chicago) and TechCrunch sources with OpenAI’s own November 17 and November 29, 2023 announcements and its October 2025 structure announcement; reworded the leadership sequence to those announcements and cut the unsourced employee letter, Microsoft hiring offer, Emmett Shear appointment, staff count, Ilya Sutskever’s regret, November 21 agreement and The Information’s report on customers contacting other vendors.

  377. · One region failed, many financial apps stalled: concentration risk sat in the dependencies

    Removed or reworded as our view or a condition unsourced statements about how widely or how often organizations did something (for example, “For most institutions, multi-region designs”).

  378. · One region failed, many financial apps stalled: concentration risk sat in the dependencies

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “Board reports, however, often describe cloud resilience as a property of the provider”).

  379. · One records request, two rulebooks: Korunda and Ciox

    Corrected the account of HHS’s May 2019 filing: as the Ciox opinion describes it, HHS told the court on May 24, 2019 that it had published a fact sheet on its website, rather than filing a fact sheet with the court; reworded as our view or as possibilities unsourced statements about what often or usually happens.

  380. · One door is not a service: the IRS selfie reversal

    Sourced the NIST 2019 face recognition study to NIST’s own release and described its findings as NIST does. Removed a listed Login.gov page that no longer shows the content it was cited for. Sourced Login.gov’s October 2024 IAL2 certification to GSA’s October 9, 2024 release, which replaced GSA’s April 2024 release among the sources (the October release also describes the April pilot), and described the April pilot and the in-person option as the October release does, without the earlier figure of more than 18,000 Postal Service locations.

  381. · One console, every server: what ESXiArgs exposed about the hypervisor

    Removed or reworded unsourced statements about how widely ESXi is used and what most or many organizations do (for example, “Many organizations patch guest operating systems monthly and hypervisors rarely”); the link to CVE-2021-21974 is now attributed to CERT-FR.

  382. · One console, every server: what ESXiArgs exposed about the hypervisor

    Reworded as our view or as a possibility unsourced statements about what IT teams and organizations typically or often do (for example, “Smaller sites often have neither”).

  383. · One alert, three threats: how local agencies should have read the June 2025 Iran warning

    Updated the text to say that M-21-31 applied at the time and that OMB rescinded it on May 22, 2026, with memorandum M-26-14, whose minimum retention baseline is now given.

  384. · One alert, three threats: how local agencies should have read the June 2025 Iran warning

    Removed or reworded as our view or a condition unsourced statements about how widely or how often organizations did something (for example, “Many agencies run a dozen or more public services”).

  385. · One alert, three threats: how local agencies should have read the June 2025 Iran warning

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “Departments often open accounts for parks, libraries or emergency management without telling IT”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “One that acts on the bulletin alone tends to do generic things.”).

  386. · Omicron’s scarcest resource was staff, and few hospitals could count them in real time

    Reworded unsourced statements about what many or most hospitals and health systems did (for example, “Many hospitals responded with workforce management platforms”) as options or conditions.

  387. · Omicron’s scarcest resource was staff, and few hospitals could count them in real time

    Reworded as our view or as a possibility unsourced statements about what hospitals and their staff typically or often do (for example, “The chief nursing officer usually owns the staffing view”).

  388. · How OMB’s first AI memo reached AI systems agencies already ran

    Reworded as our view an unsourced statement about how monitoring “fails most often”.

  389. · How OMB’s first AI memo reached AI systems agencies already ran

    Reworded as a possibility an unsourced statement about what vendors typically or often do (“A vendor asked whether its product uses AI will often reply with marketing language”).

  390. · Oldsmar’s unidentified intruder, undisputed weaknesses

    Removed or reworded as our view unsourced statements about how widely or how often organizations did something (for example, “Attackers routinely scan” and “cyber insurers have increasingly asked”).

  391. · Oldsmar’s unidentified intruder, undisputed weaknesses

    Reworded as our view or as a possibility unsourced statements about what utilities, vendors and insurers typically or often do (for example, “A controls integrator that built the plant’s SCADA system often keeps its own remote connection”). On 2026-11-15 replaced the BankInfoSecurity article with the archived Massachusetts notice to public water suppliers and reworded the plant details to what it and CISA advisory AA21-042A state (one of several computers had TeamViewer), cut the unsourced 11,100 ppm figure, 24-to-36-hour estimate, population, FBI notice, NBC News Bay Area case, Muleshoe and Arkansas City paragraph, the state lawsuit details and the March 2024 letter, sourced the Kansas case to the U.S. Attorney’s plea announcement (reworded to it) and the Dragos finding to Dragos’s own report.

  392. · Old ban, new deadline: Kaspersky’s exit reached the governments Washington’s 2017 order never covered

    Reworded unsourced statements about what most or many organizations do (for example, “most organizations run a central console”) as conditions.

  393. · Old ban, new deadline: Kaspersky’s exit reached the governments Washington’s 2017 order never covered

    Reworded as our view or as a possibility unsourced statements about what public bodies, budgets, vendors and insurers typically or often do (for example, “A third category is often left out”). Sourced the July 2024 CrowdStrike outage to Microsoft’s estimate and CrowdStrike’s own review, replaced an unsourced list of those disrupted (airlines, hospitals, emergency call centers) with Microsoft’s description, and described CrowdStrike’s changes as its review does. Replaced the TechCrunch source with Kaspersky’s own statement on its support forum, reworded the UltraAV passage to what that statement and the forum thread show, cut unsourced details about Pango, a VPN product and Kaspersky’s July announcement, and corrected “a month earlier” to “two months earlier” for the July 19 CrowdStrike outage.

  394. · A support engineer two contracts away: Okta, Lapsus$ and the hospital front door

    Removed or reworded as our view unsourced statements about what most or many hospitals and health systems do and about how widely practices spread (for example, “the arguments of March 2022 are routine in vendor reviews”). Replaced an unsourced report of help desk calls in the attack on MGM Resorts with the FBI and CISA’s November 2023 advisory on the Scattered Spider group.

  395. · How a troubleshooting file handed over an administrator’s session in the Okta breach

    Reworded as conditions or our view unsourced statements about what many organizations and health systems do and about trends in session token theft (for example, “attackers increasingly looked for ways to steal a signed-in session”).

  396. · How a troubleshooting file handed over an administrator’s session in the Okta breach

    Reworded as a possibility unsourced statements about what vendors and hospital IT teams typically or often do (for example, “Support platforms often keep attachments for as long as the case exists”). Reworded the BeyondTrust sentence to what Okta’s root cause report states (that BeyondTrust reported suspicious activity in early October) and cut the unsourced claim that it blocked the activity.

  397. · OAuth integrations make their vendors custodians of your credentials

    Removed or reworded as our view or a condition unsourced statements about how widely or how often organizations did something (for example, “most organizations never examine that environment”).

  398. · OAuth integrations make their vendors custodians of your credentials

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “Chat and marketing tools often run under an integration user with broad read access”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “The organizations caught out by campaigns like this tend to have made the same choices.”).

  399. · NYDFS’s final Part 500 deadline put the asset inventory underneath every other control

    Removed or reworded as our view or a condition unsourced statements about how widely or how often organizations did something (for example, “many firms had focused MFA there”).

  400. · NYDFS’s final Part 500 deadline put the asset inventory underneath every other control

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “Where gaps exist it is usually the safer choice”).

  401. · NYDFS wrote no AI rule, and made AI risk part of what the CEO certifies

    Reworded unsourced statements about what most institutions and many firms do (for example, “Most institutions use AI through vendors”) as conditions.

  402. · NYDFS wrote no AI rule, and made AI risk part of what the CEO certifies

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “Firms typically allow an approved enterprise AI service”). Replaced an unsourced report that 2023 intrusions, including the attack on MGM Resorts, began with help desk calls with the FBI and CISA’s November 2023 advisory on help desk calls by the Scattered Spider group. Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “Training copies and test datasets tend to outlive”).

  403. · Non-bank lenders got bank-grade security rules and a named person to answer for them

    Removed or reworded unsourced statements about what many or most firms did (for example, that multifactor authentication and encryption at rest “became standard features” vendors had to offer).

  404. · Non-bank lenders got bank-grade security rules and a named person to answer for them

    Reworded as our view or as a possibility unsourced statements about what lenders, dealers and their staff typically or often do (for example, “A fintech lender usually has the opposite profile”).

  405. · No patch yet: Follina and Confluence tested who may switch things off

    Updated the text to say that BOD 22-01 applied at the time and that CISA revoked it on June 10, 2026, replacing it with BOD 26-04.

  406. · No patch yet: Follina and Confluence tested who may switch things off

    Replaced an unsourced claim that the Known Exploited Vulnerabilities catalog became a standard input beyond federal agencies with what CISA's alert says: it "strongly urges all organizations" to prioritize remediation of catalog vulnerabilities.

  407. · No patch yet: Follina and Confluence tested who may switch things off

    Removed or reworded as our view unsourced statements about what many hospitals and health systems do or have done (for example, “By 2026 more health systems have written emergency authority into policy”).

  408. · No patch yet: Follina and Confluence tested who may switch things off

    Reworded as our view or as a possibility unsourced statements about what hospitals and research institutions typically or often do (for example, “Large organizations install patches on a schedule, typically monthly”).

  409. · What NIST’s zero trust definition required agencies to know about themselves

    Updated the hindsight to note that OMB rescinded M-21-31 on May 22, 2026, with memorandum M-26-14.

  410. · What NIST’s zero trust definition required agencies to know about themselves

    Removed or reworded unsourced statements about what most or many organizations and agencies did or had (for example, “In 2020 many agencies had none of them in that condition”) and dropped unsourced “widely” and “increasingly”.

  411. · What NIST’s zero trust definition required agencies to know about themselves

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “Agencies often pick the wrong first system”).

  412. · NIST’s bias study made face recognition a buyer’s problem

    Accounted for all 26 GAO-21-518 recommendations: besides 17 closed as implemented and five open or partially addressed, GAO closed four as “no longer valid” because the agencies were not using, or had no plans to use, non-federal face recognition technology; reworded as our view or as possibilities unsourced statements about what most agencies do or what often or usually happens.

  413. · Ninety days at a time: telehealth’s stack of temporary permissions

    Reworded as our view an unsourced statement that state licensure was “the layer most often misunderstood”.

  414. · Ninety days at a time: telehealth’s stack of temporary permissions

    Reworded as our view or as a possibility unsourced statements about what hospitals and practices typically or often do (for example, “Community hospitals generally did not”).

  415. · A new SEC chair rewrites the agenda, not the compliance calendar

    Marked unsourced characterizations (his agenda “widely described as lighter-touch”; Regulation S-P as the item most firms needed to watch) as our view.

  416. · A new SEC chair rewrites the agenda, not the compliance calendar

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “Smaller advisers and introducing brokers often rely on a handful of outsourced providers”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “Strong firms tend to share a few habits.”).

  417. · Necessary and proportionate: the ADPPA test that outlived the bill

    Removed or reworded as our view unsourced statements about what most organizations do and found (for example, “Most organizations found the hard part was evidence”).

  418. · Necessary and proportionate: the ADPPA test that outlived the bill

    Reworded as our view or as a possibility unsourced statements about what organizations and their vendors often or usually do (for example, “Marketing often buys its own tools”).

  419. · National Public Data turned the Social Security number into a lookup key

    Removed or reworded unsourced statements about how widely practices and guidance are used (for example, “a reference widely used by agencies and by many private organizations”, “examiners and auditors increasingly read it that way”).

  420. · National Public Data turned the Social Security number into a lookup key

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “Their contracts often pay by call volume or resolution rates”). Replaced an unsourced report that the September 2023 attack on MGM Resorts started with a help desk call with the FBI and CISA’s November 2023 advisory on help desk calls by the Scattered Spider group. Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “tends to let the old questions creep back”). Replaced the BleepingComputer and KrebsOnSecurity sources and the two CourtListener copies of court filings with National Public Data’s own breach notice (Internet Archive copy), a Southern District of Florida order in Hofmann v. Jerico Pictures on GovInfo, the California Privacy Protection Agency’s February 2025 announcement and the CFPB’s May 2025 withdrawal notice; cut the news-reported details of the April 2024 sale offer, the August 6 leak, the 272 million Social Security number count, the age profile of the records, the sister site’s exposed passwords, the August 19 filing date, the Chapter 11 date and the contents of the bankruptcy papers, said the bankruptcy court dismissed the petition, removed dates of birth from the list of leaked data, which the company’s notice does not list, described the CFPB proposal as its withdrawal notice does, and replaced unsourced DROP dates with the agency’s statement that the platform would be available in 2026. On 2026-11-15 an independent review (N-143) replaced the class action’s case name, which names a private individual, with a description.

  421. · Many MOVEit victims never ran MOVEit

    Removed or reworded as our view unsourced statements about what most or many organizations do and how often controls fail (for example, “Minimization has proved the most dependable control”).

  422. · Many MOVEit victims never ran MOVEit

    Reworded as our view or as a possibility unsourced statements about what organizations, vendors and attackers typically or often do (for example, “Vendors often ask for more data to improve matching accuracy”). Removed the Emsisoft source and its count of about 2,770 organizations and 96 million people (with “thousands” and “most” in the dek and title), reworded the Cleo sentence to CISA’s listing, and replaced the unsourced Clop extortion account of the Oracle E-Business Suite campaign with Oracle’s Security Alert for CVE-2025-61882. On 2026-11-15 (N-146) the sentence on the consolidated MOVEit lawsuits was sourced to the Massachusetts court’s December 2024 order in the multidistrict litigation and reworded to what that order shows.

  423. · Morgan Stanley and E*Trade: wealth scale is a client-data problem

    Removed or reworded as our view unsourced statements about what most or many firms and companies do (for example, “The handoff is where most firms lose clients”).

  424. · Morgan Stanley and E*Trade: wealth scale is a client-data problem

    Reworded as our view or as a possibility unsourced statements about what investment firms and their clients typically or often do (for example, “A credit union that offers investments often does so through a third-party broker-dealer”). Replaced the Banking Dive and WealthManagement.com sources with Morgan Stanley’s March 2025 Form 10-Q and the SEC’s January 2025 cash sweep press release, replaced the Eaton Vance announcement with Morgan Stanley at Work’s December 2023 release, added Morgan Stanley’s closing announcements for E*Trade and Eaton Vance and Schwab’s May 2024 update, and cut the press-reported anti-money-laundering and FINRA reviews, the unsourced Federal Reserve approval, 2023 custody migration details, sweep rate change, April 2024 date and $10 trillion target.

  425. · Microsoft and Nuance: the recording is the asset to govern

    Removed or reworded as our view unsourced statements about how widely or how often organizations did something (for example, “Physicians increasingly used Dragon Medical One” and “increasingly a feature of the platforms health systems already run”).

  426. · Microsoft and Nuance: the recording is the asset to govern

    Reworded as our view or as a possibility unsourced statements about what clinicians and vendors typically or often do (for example, “Clinicians who volunteer are often the ones most frustrated by documentation”). On 2026-11-15 replaced the Healthcare Dive article with Epic’s own AI Charting announcement and reworded the Epic sentence to it (cut the August 2025 preview and the Microsoft and Azure detail), added Nuance’s DAX Express release and Kaiser Permanente’s Abridge release, and reworded the unsourced press-coverage claims about DAX human reviewers to what the Nuance release states.

  427. · For banks, the MGM and Caesars intrusions were about the few accounts that run the identity platform

    Reworded as conditions unsourced statements about what most or many banks and institutions do (for example, “Today most institutions use a single identity provider”), and removed unsourced “widely” descriptions of the reporting.

  428. · For banks, the MGM and Caesars intrusions were about the few accounts that run the identity platform

    Reworded as our view or as a possibility unsourced statements about what institutions, help desk providers and insurers typically or often do (for example, “Insurers commonly ask applicants about multi-factor authentication”). Removed the account, which rested on press reporting, that MGM’s attackers got in through a call to its IT help desk, along with press reports of ALPHV’s leak-site claims, of the casino disruption and of ransom payments; the week now describes what MGM’s SEC filings and the FBI and CISA advisory AA23-320A (its November 2023 version now listed) say, and states that MGM’s filings did not say how the attackers got in. The hindsight now sources the 2025 activity to the advisory’s July 2025 update and the National Crime Agency, removed unsourced statements about retailers, insurers, airlines and an expected £300 million profit hit at Marks & Spencer, and corrects the update’s partners to agencies in Canada, Australia and the United Kingdom (it said four other countries). Sourced the October 2023 Okta incident to Okta’s own November 29, 2023 update (attributed as Okta’s statement) and the 2023 New York DFS amendment to the amendment text, reworded to what it states (effective November 1, 2023; multi-factor authentication for any individual accessing a covered entity’s information systems, with two years to comply). Within the eight-source limit, cut the unsourced paragraphs and sentences on the Cyber Safety Review Board’s Lapsus$ review, the late-2024 U.S. charges and 2025 charges, Microsoft’s Midnight Blizzard disclosure and FinCEN’s deepfake alert, and removed a duplicate archived copy of the CISA and FBI advisory, whose current page carries the same text and its version history.

  429. · Medusa showed that a clinic’s remote-support software is its ransomware attack surface

    Reworded unsourced statements about what many hospitals and underwriters do (for example, “Many hospitals drill for a single system outage”) as conditions.

  430. · Medusa showed that a clinic’s remote-support software is its ransomware attack surface

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “Management servers are often installed once”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “Hospitals tend to run older builds”).

  431. · Medicare’s negotiated prices would reach hospital pharmacies as refunds, and refunds have float

    Removed an unsourced “widely used” description of the selected drugs and reworded an unsourced statement about how many organizations identify 340B purchases.

  432. · Medicare’s negotiated prices would reach hospital pharmacies as refunds, and refunds have float

    Reworded as our view or as a possibility unsourced statements about what hospitals and pharmacies typically or often do (for example, “A busy pharmacy usually keeps one shelf of each drug”). Replaced the Healthcare Dive source with CMS’s fact sheet on the drugs selected for 2027, removed the ArentFox Schiff and Barnes & Thornburg (via Mondaq) alerts because HRSA’s August 2026 Federal Register notice states the court history, and reworded the February 2026 vacatur to that notice (after HHS withdrew the pilot, not at the parties’ joint request).

  433. · Medicaid’s frailty test asks for a code and proof of impairment, and clinicians hold both

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “Patients who lose Medicaid often remain patients”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “Where it tends to go wrong:”). Removed the KFF and Holland & Knight attributions and the KFF sources: the frailty test and attestation limits now cite the interim final rule itself, the Nebraska figures cite the minutes of Nebraska’s Medicaid Advisory Committee for September 17, 2026 (38.6% of renewal exemptions, 490 of 533 denials for non-response), and the lawsuit cites the Minnesota Attorney General’s release; the unsourced mention of prescriptions and medical equipment as frailty signals was cut.

  434. · Easy to grant, hard to defend: M-24-10 put every federal AI exception on the record

    Added to the hindsight that SR 11-7 and OCC Bulletin 2011-12 were superseded on April 17, 2026, by SR 26-2 and OCC Bulletin 2026-13, and put descriptions of SR 11-7 as current guidance in the past tense.

  435. · Easy to grant, hard to defend: M-24-10 put every federal AI exception on the record

    Removed or reworded as our view unsourced statements about what became standard in federal AI acquisition and what examiners, oversight bodies and many companies routinely do (for example, “the contract terms that later became standard in federal AI acquisition”).

  436. · Easy to grant, hard to defend: M-24-10 put every federal AI exception on the record

    Reworded as our view or as a possibility unsourced statements about what agencies, their staff and executives typically or often do (for example, “demographic data that agencies often do not collect”). Replaced the FedScoop source with an archived copy of the federal CIO Council’s inventory page, which states the 227 and 206 figures.

  437. · M-22-18 asked producers to sign; agencies first had to know who they were

    Removed or reworded as our view unsourced statements about what many agencies and organizations did and dropped unsourced “widely used” descriptions (for example, “the list was where many agencies stalled”).

  438. · M-22-18 asked producers to sign; agencies first had to know who they were

    Reworded as a possibility unsourced statements about how agencies usually or often organize and buy technology (for example, “The inventory usually sits with the CIO’s office”).

  439. · M-22-09 made the login phishing-proof and moved the weak point to enrollment and recovery

    Removed unsourced statements about what many agencies do and dropped unsourced “widely” descriptions (for example, “Many agencies outsource their help desk”).

  440. · Lower quantum estimates moved signatures up the post-quantum queue

    Removed or reworded as our view or a condition unsourced statements about how widely or how often organizations did something (for example, “Most agencies received that protection without a project”). Kept Google’s, Cloudflare’s and Oratomic’s own posts for their own research and targets, and added Oratomic’s and Google’s own announcements to source the Oratomic estimate and Google’s 2029 migration target.

  441. · Low for long: the rate forecast hidden in bank technology budgets

    Reworded unsourced statements about what most or many institutions do (for example, “Most institutions set technology budgets annually”).

  442. · Low for long: the rate forecast hidden in bank technology budgets

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “Early termination typically triggers fees”).

  443. · Louisiana’s ransomware outage was mostly its own decision

    Put the State and Local Cybersecurity Grant Program in the past tense and added that its section’s requirements ended on September 30, 2026, the date set by Pub. L. 119-75; corrected the account of the 2023 MOVEit breach, which reached Office of Motor Vehicles files on a MOVEit server the OMV ran (version 14.0.4), not a vendor’s service, and adjusted the related objection and takeaway; corrected the restoration timing to the release’s wording (services and email began returning the afternoon of the attack); reworded one unsourced statement as a possibility.

  444. · Log4Shell was a search problem before it was a patching problem

    Removed the unsourced statement that SBOMs are now routinely requested in regulated procurement, and reworded other unsourced statements about what most or many organizations did (for example, “Many banks, retailers and agencies impose change freezes in December”).

  445. · Log4Shell was a search problem before it was a patching problem

    Reworded as our view or as a possibility unsourced statements about what governments, banks and software teams typically or often do (for example, “Banks generally had larger security teams”).

  446. · Living-will rules keep moving; the systems map stays put

    Corrected the dek: targeted plans could leave out system descriptions only where the systems were materially unchanged; said the FDIC published its proposals on June 30, 2026 and in November 2026 (the Federal Register dates) rather than proposed on those dates; dropped an unsourced statement that new filing obligations often come with transition periods.

  447. · Lighter rules, heavier contracts: OMB’s April 2025 AI memos handed governance to the buyer

    Restated the September 2026 OneGov agreement with OpenAI as GSA announced it: GSA said the offer was expected to take effect on October 1, 2026, and its announcement does not confirm the start.

  448. · Lighter rules, heavier contracts: OMB’s April 2025 AI memos handed governance to the buyer

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “Large AI vendors sell on standard terms to millions of customers and often decline to negotiate”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “tend to show a few habits.”).

  449. · Lifespan’s stolen laptop and the home office risk analyses missed

    Reworded unsourced statements about what most organizations accept and what OCR routinely does, and dropped an unsourced “widely available”.

  450. · Lifespan’s stolen laptop and the home office risk analyses missed

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “Large systems often use commercial governance platforms”). Replaced the Alston & Bird client alert with the Unified Agenda entry for RIN 0945-AA22 and reworded the final-rule timing to what it lists (final action July 2027).

  451. · Legal to fly, hard to replace: the FCC drone listing and public-safety fleets

    Removed or reworded as our view or a condition unsourced statements about how widely or how often organizations did something (for example, “Many agencies found their drone records sat with individual units”).

  452. · Legal to fly, hard to replace: the FCC drone listing and public-safety fleets

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “One that waited for its fleet to fail would face an unfunded gap, often at the moment”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “A well-run response tends to share a few traits.”).

  453. · LastPass and the first-draft problem in vendor breach notices

    Removed or reworded as our view unsourced statements about what many or most organizations had done (for example, “Most organizations had never rehearsed that”).

  454. · LastPass and the first-draft problem in vendor breach notices

    Reworded as our view or as a possibility unsourced statements about what businesses, health systems and vendors often or usually do (for example, “Large vendors often resist custom terms”).

  455. · Kronos went down; the duty to pay public workers on time stayed up

    Reworded unsourced statements about what most organizations find and do (for example, “Auditors and insurers increasingly ask for evidence rather than assurances”) as our view or as possibilities.

  456. · Kaseya and the most privileged system nobody on site runs

    Reworded unsourced statements about how widely VSA was used and where most organizations find gaps (for example, “Most organizations find the gaps in contact lists and authority”).

  457. · Kaseya and the most privileged system nobody on site runs

    Reworded as our view or as a possibility unsourced statements about what clients, providers and their IT teams typically or often do (for example, “Clients often assumed the provider was responsible for security in general”). On 2026-11-15 replaced the Rapid7 blog with Kaseya’s own incident update, added the Justice Department’s arrest and sentencing announcements, reworded the decryptor sentence to Kaseya’s update, and cut the unsourced JBS payment, $70 million demand, Bloomberg victim count, security-firm detection details, REvil site reappearance and FSB arrests.

  458. · Juneteenth tested how many calendars a bank really runs

    Removed unsourced statements about how many banks stayed open in 2021 and how many institutions consolidated their holiday calendars afterward.

  459. · Juneteenth tested how many calendars a bank really runs

    Reworded as our view or as a possibility unsourced statements about what banks, vendors and their teams typically or often do (for example, “Holiday tables in those systems are often maintained separately”). On 2026-11-15 replaced the TheCorporateCounsel.net post with the NYSE’s Rule 7.2 filing in the Federal Register and reworded the exchange sentence to it, and removed the Fortune (Bloomberg) article with the floating-holiday report and the unsourced SEC office closure it supported.

  460. · July 1 in teaching hospitals: thousands of joiners, movers and leavers in one week

    Removed or reworded as our view or a condition unsourced statements about how widely or how often organizations did something (for example, “In many hospitals new permissions are added”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “it tends to get less attention because its failures are silent”).

  461. · Ivanti’s October zero-day was a directory incident that came in through the VPN

    Removed or reworded as our view or a condition unsourced statements about how widely or how often organizations did something (for example, “The account is also an orphan in most organizations”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “tend to find it never gets done”). Removed the two Hacker News sources and the claims that rested only on them (Defused’s decoy sightings from October 1, watchTowr’s comments and Previdian’s count of 105 attempts from 50 addresses); the exposure window now starts on October 3, the first activity Volexity reported, and the count of Connect Secure entries is checked against CISA’s catalog. On 2026-11-15 an independent review (N-145) cut a leftover reference to the mass exploitation researchers had expected, which rested on the removed press report, and a sentence on how end-of-October press coverage summarized the actor’s behavior, which no remaining source supports. On 2026-11-15 (N-146) the sentence saying Ivanti found part of the flaw itself, fixed it in a July release, 25.1.3.0, and was backporting the fix was replaced with Ivanti’s description of the flaw in the National Vulnerability Database (affects versions before 25.1.3.0, not 22.7R2.14 or earlier), and further general statements (“rarely”, “usually”, “often”, “many state security policies”) were reworded as possibilities or our view.

  462. · Ireland’s HSE attack was decided in the eight weeks before encryption

    Reworded unsourced statements about what many or most organizations do (for example, “many organizations now block macros”) as conditions or our view.

  463. · Ireland’s HSE attack was decided in the eight weeks before encryption

    Reworded as our view or as a possibility unsourced statements about what attackers, banks, health systems and boards typically or often do (for example, “A bank typically has a centrally managed fleet of standard desktops”).

  464. · Iran’s war tested banks’ decision rights more than their defenses

    Removed or reworded as our view or a condition unsourced statements about how widely or how often organizations did something (for example, “most banks had controls for all of them”). Also reworded further unsourced claims about how organizations or people behave (for example, “Large banks typically buy protection”). Replaced the Reuters, Oil & Gas Journal and Business Today articles with CRS report R48887 and EIA’s March and September 2026 Short-Term Energy Outlook releases, removed the ICBA item and cut the unsourced Treasury flash alert and the reported intelligence assessment on hacktivists, rewording the threat description to FINRA’s alert. Added the Justice Department’s March 19 release and CISA’s March 18 alert to source the Stryker attribution.

  465. · Iowa’s caucus app failed at rollout before it failed in code

    Reworded as our view two unsourced statements (“widely discussed as a warning”, “In most organizations, that list will contain”).

  466. · Iowa’s caucus app failed at rollout before it failed in code

    Reworded as our view or as a possibility unsourced statements about what callers, developers and organizations typically or often do (for example, “Callers who give up usually call again”). Replaced the NBC News, Motherboard, CBS News, Center Square and Bloomberg sources with the Iowa Democratic Party’s February 7 remarks and February 12 resignation letter, FEC disbursement records, the DNC’s calendar statement, two GAO reports and two Federal Student Aid announcements; cut the vendor name from the opening, the Motherboard and NBC anecdotes, the consultants and no-intrusion claims, the chair’s untested-app remark, Nevada dropping the app, the American Rescue Plan funding line and the hotline-disruption report, and reworded the 2024 calendar and FAFSA details to what those sources state.

  467. · ION’s outage exposed a vendor no board had on its critical list

    Removed or reworded unsourced statements about how many firms used ION and what most firms had (for example, “It is still more than most firms had in early 2023”).

  468. · ION’s outage exposed a vendor no board had on its critical list

    Reworded as our view or as a possibility unsourced statements about what firms, vendors and boards typically or often do (for example, “Most programs grade criticality by spend, data sensitivity or customer visibility”). Sourced Microsoft’s estimate of 8.5 million devices affected by the July 2024 CrowdStrike outage and removed an unsourced statement that it hit banks. Replaced the TechCrunch source with CFTC Commissioner Romero’s February 10, 2023 keynote, attributed the LockBit claim and the count of about 42 affected firms to the news reports she cited, and cut the unsourced leak-site deadline, February 6 restoration date, Treasury official’s remark, Futures Industry Association statement and the claim that LockBit also claimed the ICBC attack.

  469. · Interoperability rules sent patient data beyond HIPAA’s reach

    Dropped unsourced statements about how widely FHIR is used and how many consumer apps use intermediaries.

  470. · Interoperability rules sent patient data beyond HIPAA’s reach

    Reworded as our view or as a possibility unsourced statements about what health systems and their partners typically or often do (for example, “An ambulatory network built through acquisitions often runs several EHRs”).

  471. · Internet Explorer retired; its clinical applications did not

    Reworded as our view an unsourced statement about who leads this work “in most organizations”.

  472. · Internet Explorer retired; its clinical applications did not

    Reworded as our view or as a possibility unsourced statements about what health systems and their vendors typically or often do (for example, “What moved them was usually commercial”).

  473. · Information blocking compliance lived in EHR defaults

    Removed or reworded as our view unsourced statements about how widely or how often organizations did something (for example, “many organizations moved to releasing test results and notes as soon as they were finalized”).

  474. · Information blocking compliance lived in EHR defaults

    Reworded as our view or as a possibility unsourced statements about what health systems, patients and vendors typically or often do (for example, “Portal access is often shared”).

  475. · Inflation’s first casualty in bank IT was the change budget

    Removed or reworded unsourced statements about what most or many institutions did with budgets and contracts (for example, “Most institutions build the next year’s technology budget in the autumn”).

  476. · Inflation’s first casualty in bank IT was the change budget

    Reworded as our view or as a possibility unsourced statements about what banks, boards and vendors typically or often do (for example, “Contracts commonly run five to seven years”).

  477. · In a merged health system, the network decides which hospitals go to paper

    Reworded unsourced statements about how often ransomware crews do something (for example, “Increasingly, attackers also copy data out beforehand”) as descriptions of what attackers may do.

  478. · In a merged health system, the network decides which hospitals go to paper

    Reworded as our view or as a possibility unsourced statements about what attackers, health systems and their advisers usually or often do (for example, “The cyber insurer often requires the use of firms from its approved panel”). Replaced The HIPAA Journal and Healthcare Brew with CommonSpirit's own annual report for fiscal 2023 (about $160 million impact, notifications finished in April 2023) and HHS's performance goals page, added Ascension's 2024 financial statements and the UnitedHealth chief executive's Senate testimony, reworded the Ascension passage to what Ascension reported, and cut unsourced details (the $150 million early estimate, the 620,000 and 623,000 counts, notification letter contents, class actions, the Prospect Medical attack, the Ascension cause and count, the January 2024 date and the first OCR ransomware settlement).

  479. · If the CFPB’s funding fell, the statutes would still stand

    Removed unsourced statements about what most agencies and most institutions do (for example, “Most institutions do not build their own compliance software”).

  480. · If the CFPB’s funding fell, the statutes would still stand

    Reworded as our view or as a possibility unsourced statements about what lenders and regulators typically or often do (for example, “Small lenders often have one loan officer”).

  481. · Iberia’s blackout put payment resilience back at the shop counter

    Removed unsourced words about how widely something was reported and a trend (“increasingly, its own SIM card”).

  482. · Iberia’s blackout put payment resilience back at the shop counter

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “Banks usually measure payment resilience inside their own walls”).

  483. · Hurricane Ida and the IT dependencies that sit under the EHR

    Reworded unsourced statements about what most hospitals and many organizations did (for example, “Many organizations added them as backup”).

  484. · Hurricane Ida and the IT dependencies that sit under the EHR

    Reworded as our view or as a possibility unsourced statements about what hospitals, carriers and vendors typically or often do (for example, “Cooling is often the weakest point”).

  485. · For hospitals, HTI-1’s model cards covered only the EHR vendor’s own algorithms

    Updated the hindsight: the HTI-5 rule was finalized on October 28, 2026 (91 FR 67916), effective December 28, 2026. It removed the decision support source attribute (model card) requirements and the intervention risk management requirement. The earlier text said the rule had not been finalized. Reworded unsourced statements about trends and about how many organizations keep a model inventory (for example, “Many organizations cannot list every predictive model they run”).

  486. · For hospitals, HTI-1’s model cards covered only the EHR vendor’s own algorithms

    Reworded as a possibility unsourced statements about what organizations typically or often do (for example, “Internal teams often skip fairness and subgroup analysis”).

  487. · How Windows Recall put a possible public record where no records officer could reach it

    Reworded unsourced statements about what most or many agencies do and about trends in AI features (for example, “Over the previous decade most agencies had rebuilt their records programs around central platforms”).

  488. · How Windows Recall put a possible public record where no records officer could reach it

    Reworded as our view or as a possibility unsourced statements about what agencies, officials and knowledge workers typically or often do (for example, “Agencies typically preserve a departing employee’s mailbox and files by policy”).

  489. · How the No Surprises Act turned a medical bill into four data handoffs

    Removed or reworded as our view unsourced statements about how widely or how often organizations did something (for example, “Many organizations met the first requirement with templates and manual work”).

  490. · How the No Surprises Act turned a medical bill into four data handoffs

    Reworded as our view or as a possibility unsourced statements about what health systems, plans and employers typically or often do (for example, “Executives outside health care finance often miss this”). Replaced the Groom Law Group summary with the Unified Agenda entry for the advanced explanation of benefits rule (RIN 0938-AU98), and reworded the status to what it lists: a proposed rule planned for September 2026.

  491. · How the CVE contract scare exposed the public plumbing under every patching policy

    Updated the text to say that BOD 22-01 applied at the time and that CISA revoked it on June 10, 2026, replacing it with BOD 26-04.

  492. · How the CVE contract scare exposed the public plumbing under every patching policy

    Reworded unsourced statements about what most or many organizations and examiners do and about trends in CVE records (for example, “Inside most organizations, vulnerability management is split across teams”) as conditions.

  493. · How the CVE contract scare exposed the public plumbing under every patching policy

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “Auditors typically sample findings that the scanner rated critical”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “A large vendor with a mature product security team tends to publish”).

  494. · How the AI Act proposal tied risk to the use, whatever the model

    Removed or reworded as our view unsourced statements about how widely or how often organizations did something (for example, “Many organizations decided the feature was not worth the conversation, and turned it off”).

  495. · How the AI Act proposal tied risk to the use, whatever the model

    Added to the hindsight that SR 11-7 and OCC Bulletin 2011-12 were superseded on April 17, 2026, by SR 26-2 and OCC Bulletin 2026-13.

  496. · How the AI Act proposal tied risk to the use, whatever the model

    Reworded as our view or as a possibility unsourced statements about what organizations and their staff typically or often do (for example, “Human resources leaders were often the last to learn”).

  497. · How a fee question pulled open banking off the rulebook and onto the rate card

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “Complaints land on whoever the customer blames, which is usually their bank”).

  498. · How polyfill.io slipped past hospital tag reviews that checked each script only once

    Removed unsourced statements about how widely the Polyfill case was cited (“became a standard example”) and what many organizations did after March 31, 2025.

  499. · How polyfill.io slipped past hospital tag reviews that checked each script only once

    Reworded as our view or as a possibility unsourced statements about what hospitals and executives typically or often do (for example, “Most hospital incident plans assume an internal compromise”). Replaced the two CourtListener sources with the court’s June 20, 2024 opinion on govinfo and an archived copy of HHS’s tracking guidance page, cut the unsourced statement about HHS’s August 2024 notice of appeal, and kept the Sansec report for the findings the text attributes to Sansec.

  500. · How hospitals spent the OpenSSL week waiting for ‘not affected’

    Removed or reworded unsourced statements about how widely software is used and what most or many hospitals do (for example, “Most hospitals restrict changes to clinical systems”).

  501. · How hospitals spent the OpenSSL week waiting for ‘not affected’

    Reworded as our view or as a possibility unsourced statements about what hospitals and suppliers typically or often do (for example, “Medical device inventories often listed manufacturer and model”).

  502. · How the DOJ’s bulk data rule made reach, not storage, the health data test

    Removed or reworded as our view or a condition unsourced statements about how widely or how often organizations did something (for example, “arrangements that many organizations chose”).

  503. · How the DOJ’s bulk data rule made reach, not storage, the health data test

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “Privacy teams typically know which systems hold protected health information”).

  504. · How ConnectWise’s breach tested small practices’ business associate agreements

    Removed or reworded as our view or a condition unsourced statements about how widely or how often organizations did something (for example, “Cyber insurers increasingly ask”).

  505. · How ConnectWise’s breach tested small practices’ business associate agreements

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “Providers often run more than one, switch tools over time, and leave old agents installed”). Replaced The Hacker News and McDermott Will & Schulte sources with the NVD entry for CVE-2024-1709, the Fall 2025 Unified Agenda entry for the HIPAA Security Rule (final action projected July 2027) and CISA advisory AA25-163A, reworded the April patch to what ConnectWise’s own advisory says, and cut the unsourced claim about federal advisories in 2026.

  506. · How the lapse of a 2015 law put counsel in the threat-sharing loop

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “Government sharing often runs through a compliance or legal liaison”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “all three items tend to be treated like the third”).

  507. · How Change Healthcare’s customers decided whether to pull the plug, and when to plug back in

    Reworded unsourced statements about how most hospitals saw Change Healthcare and what many organizations found (for example, “Many organizations found these paths only when they tried to cut them”).

  508. · How Change Healthcare’s customers decided whether to pull the plug, and when to plug back in

    Reworded as a possibility unsourced statements about what attackers and health care organizations typically or often do (for example, “Modern ransomware groups often add a second threat”).

  509. · How the APRA draft moved privacy compliance to the customer’s side of the counter

    Removed unsourced “increasingly” trend claims about customers, health care algorithms and supervisors (for example, “Algorithms increasingly help decide care management outreach”).

  510. · How the APRA draft moved privacy compliance to the customer’s side of the counter

    Reworded as our view or as a possibility unsourced statements about what banks, hospitals, credit unions and privacy programs typically or often do (for example, “A program built for examiners usually has one owner”).

  511. · The August 2024 selloff and the brokerage capacity limit before the first trade

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “the security team usually owns them”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “Vendor contracts tend to promise availability”).

  512. · How a bed-count fine repriced hospital price secrecy

    Removed an unsourced description of a Danish price-transparency study as “widely cited”.

  513. · How a bed-count fine repriced hospital price secrecy

    Reworded as our view or as a possibility unsourced statements about what hospitals and their teams typically or often do (for example, “For a large system, building in-house often made more sense”).

  514. · The House budget vote signaled Medicaid churn, a cost hospitals pay at the front desk

    Removed or reworded unsourced statements about how the budget target was widely read, what many hospitals use, and how widely Georgia’s Pathways experience was cited.

  515. · The House budget vote signaled Medicaid churn, a cost hospitals pay at the front desk

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “Managed care plans often know them for their members”). On 2026-11-15, replaced the Georgetown Center for Children and Families post with an Internet Archive copy of CBO’s uninsured-estimate data for Public Law 119-21, added CMS’s September 21, 2023 press release for the reinstatements and reworded that passage to what CMS stated, and cut the unsourced KFF disenrollment count.

  516. · Hospitals without walls still had to say where the care happened

    Reworded as our view unsourced statements about what goes wrong most often (for example, “the part leaders most often underestimate”).

  517. · Hospitals without walls still had to say where the care happened

    Reworded as our view or as a possibility unsourced statements about what hospitals, their teams and regulators typically or often did (for example, “Teams that stood up a new site in days often cloned an existing department”). Replaced The HIPAA Journal, Foley & Lardner and Mintz sources with OCR’s April 2023 Federal Register notice, the Senate Finance Committee’s section-by-section summary, CMS’s telehealth FAQ and the Congress.gov record for H.R. 7148, added CMS’s CY 2026 fee schedule fact sheet, and reworded the telehealth lapse and behavioral health lines to what those sources state (one lapse from October 1, 2025; law signed February 3, 2026; the Consolidated Appropriations Act, 2021 change).

  518. · Hospital websites had a HIPAA problem because nobody owned the tags

    Removed or reworded unsourced statements about what most or many health systems could or could not do (for example, “Most health systems could not say which third-party scripts ran on which pages”).

  519. · Hospital websites had a HIPAA problem because nobody owned the tags

    Reworded as our view or as a possibility unsourced statements about what hospitals, health systems and vendors typically or often do (for example, “An academic medical center often runs dozens of web properties”). Replaced The Markup's report with Novant Health's own August 2022 notice and reworded that passage to what Novant said, added Kaiser Permanente's own privacy notice and reworded the Kaiser sentence to it, and cut unsourced details (The Markup's hospital counts, the wave of class actions, Advocate Aurora Health's notice, the million-patient counts and the 13.4 million figure). On 2026-11-15 (N-146) the unsourced statements that plaintiffs used the Wiretap Act against hospitals and apps and that pixel class actions continued under state law after the June 2024 ruling were reworded to what the law provides, with the Wiretap Act’s civil remedy sourced to 18 U.S.C. 2520.

  520. · Hospital price transparency began as a data lineage test

    Quoted the CY 2022 rule (86 FR 63458) in its own words, “blocking codes” such as NOINDEX and “rel canonical” tagging, instead of “noindex” tags; reworded as possibilities two unsourced statements about what hospitals would face.

  521. · Hospital device data rights arrive one purchase order at a time

    Removed or reworded as our view or a condition unsourced statements about how widely or how often organizations did something (for example, “Teaching hospitals and research institutes increasingly want”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “alternatives tend to improve terms”). Replaced the Matheson and Greenberg Traurig law firm summaries with the Data Act’s text in the Official Journal and the Council’s June 4, 2026 note on the Digital Omnibus; the design duty now reads as applying to products placed on the market after September 12, 2026, as Article 50 says, the unsourced line that commentators differ was reworded, and the unsourced description of Council compromise texts on emergencies and cloud switching was replaced with the trade secret debate the Council note records.

  522. · Why a hospital’s accessibility deadline now sits in its vendor contracts

    Removed or reworded as our view or a condition unsourced statements about how widely or how often organizations did something (for example, “an extra year gives most hospitals at least one renewal”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “and it usually holds the largest backlog”). Replaced the Seyfarth Shaw blog post with the National Federation of the Blind’s own complaint as filed in federal court.

  523. · Hive’s takedown removed a supplier, not the ransomware market

    Reworded unsourced statements about how many organizations were spared ransom payments and how widely MITRE ATT&CK is used.

  524. · Hive’s takedown removed a supplier, not the ransomware market

    Reworded as our view or as a possibility unsourced statements about what hospitals and attackers typically or often do (for example, “Hospitals often patch them slowly”).

  525. · The HIPAA Security Rule proposal’s hardest line was a 72-hour restore

    Replaced an unsourced statement that many organizations read “addressable” as permission to defer controls with what HHS said in the proposed rule (some regulated entities proceed as if addressable specifications are optional), and removed or reworded other unsourced statements about most or many hospitals and about cyber insurers.

  526. · The HIPAA Security Rule proposal’s hardest line was a 72-hour restore

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “small practices often run their own devices and local software”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “Entries without a target date tend to become permanent.”). Replaced the Feldesman, Health IT Answers, Alston & Bird and McDonald Hopkins sources with OCR’s February 19 and June 18, 2026 settlement releases, the CHIME-led February 17, 2025 letter, two Unified Agenda entries and UnitedHealth Group’s 2024 Form 10-K; corrected “at least a dozen actions by early 2026” to the 11th action in February 2026 and the 14th in June 2026, reworded the coalition’s request to the February 2025 letter, and cut the October 2024 first-action details, the business associate examples, “thousands of comments”, the “largest breach” claim and the unsourced Ascension and Kettering Health examples.

  527. · HIPAA’s reproductive health attestation put the burden of purpose on the requester

    Reworded an unsourced statement about how many hospitals use outside release-of-information companies.

  528. · HIPAA’s reproductive health attestation put the burden of purpose on the requester

    Reworded as our view or as a possibility unsourced statements about what hospitals, records staff and requesters typically or often do (for example, “most record systems do it poorly”).

  529. · HHS’s end of voluntary comment periods hit grantees hardest and Medicare providers least

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “state agencies often adjust within weeks”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “The organizations caught out tended to make the same errors”). On 2026-11-15, replaced the Cornell Legal Information Institute copy of 42 U.S.C. 1395hh with the govinfo United States Code and the Cardinal News article with the First Circuit’s January 5, 2026 opinion, added the Supreme Court’s Allina opinion, and cut the unsourced April 2025 date of the district court’s permanent injunction.

  530. · HHS could mandate hospital cybersecurity on its own; paying for it needed Congress

    Reworded as conditions unsourced statements about what most or many hospitals face or do (for example, “For many hospitals, the essential goals described controls their insurer was already requiring”).

  531. · HHS could mandate hospital cybersecurity on its own; paying for it needed Congress

    Reworded as our view or as a possibility unsourced statements about what hospitals typically or often do (for example, “Cybersecurity budgets often lose to new equipment or clinical staff”). Replaced the Alston & Bird client alert with the Spring and Fall 2025 Unified Agenda entries for the HIPAA Security Rule on Reginfo.gov, which show the final action target moving from May 2026 to July 2027.

  532. · Helene tested what continuity plans take for granted: staff, signal and signatures

    Removed an unsourced statement that most organizations now use multi-factor authentication.

  533. · Helene tested what continuity plans take for granted: staff, signal and signatures

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “They are often stale or unknown”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “Their weakness tends to be the local field office”).

  534. · Health systems inherit the patients that IAL2 proofing turns away

    Removed or reworded as our view or a condition unsourced statements about how widely or how often organizations did something (for example, “increasingly assume it does”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “seeing your own test results usually meant a separate username”).

  535. · HCA’s data on 11 million patients sat in an email-formatting store, outside the EHR’s controls

    Removed or reworded as our view unsourced statements about how widely a product was used and what many or most organizations do (for example, “as they now routinely do after large breaches”).

  536. · HCA’s data on 11 million patients sat in an email-formatting store, outside the EHR’s controls

    Reworded as our view or as a possibility unsourced statements about what health systems, health plans and their vendors typically or often do (for example, “Outreach systems usually belong to marketing”).

  537. · Hairpin traffic, distant data centers and the road to federal zero trust

    Updated the hindsight to note that OMB rescinded M-21-31 on May 22, 2026, with memorandum M-26-14.

  538. · Hairpin traffic, distant data centers and the road to federal zero trust

    Removed or reworded unsourced statements about what most or many agencies did (for example, “Most agencies that split their tunnels chose the narrower form”) and dropped unsourced “widely”.

  539. · Hairpin traffic, distant data centers and the road to federal zero trust

    Reworded as a possibility unsourced statements about what staff and help desks typically or often do (for example, “Home routers often ran old firmware with default passwords”). Replaced the FEDweek source with OMB memorandum M-20-16 itself, added CISA alert AA20-073A for the March 13 VPN guidance, reworded the memo’s telework and contractor instructions to its text, and cut the unsourced claim that earlier guidance had covered only the national capital region.

  540. · The governors’ water letter handed one problem to three state secretaries

    Removed an unsourced “increasingly” trend claim about computer control of water systems.

  541. · The governors’ water letter handed one problem to three state secretaries

    Reworded as our view or as a possibility unsourced statements about what water utilities, integrators and grant committees typically or often do (for example, “Integrators often installed them with remote access enabled”).

  542. · A lost zone is the failure banks plan for. Google’s London outage tested five layers of that plan

    Removed or reworded as our view or a condition unsourced statements about how widely or how often organizations did something (for example, “most firms will mix them”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “in ways an architecture review rarely sees”). Replaced The Register, Reuters (via Yahoo Finance), Euronews and City AM with the Bank of England and FCA joint letter to the Treasury Committee of November 4, 2026, the European Supervisory Authorities’ designation of critical ICT providers and its list, and AWS’s own summary of its October 2025 disruption; press-reported details on Revolut, named banks, the FCA’s and EBA’s comments, Google’s spokesperson and the committee’s reply deadlines were cut or replaced with what the regulators’ letter states. On 2026-11-15 (N-146) unsourced generalizations about how banks and cloud designs usually or often behave (for example, “Many cloud designs choose the second option” and “Financial services felt it most visibly”) were reworded as possibilities or our view.

  543. · Google Cloud’s June outage moved bank cloud diligence from uptime to change safety

    Removed or reworded as our view or a condition unsourced statements about how widely or how often organizations did something (for example, “Most banks rely heavily on independent audit reports”).

  544. · Google Cloud’s June outage moved bank cloud diligence from uptime to change safety

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “These firms often serve a few hundred financial institutions”).

  545. · GameStop’s buy button was switched off in the clearinghouse

    Removed or reworded as our view unsourced statements about how widely or how often organizations did something (for example, “Many firms reconcile positions overnight in batches” and “widely read as evasive”).

  546. · GameStop’s buy button was switched off in the clearinghouse

    Reworded as our view or as a possibility unsourced statements about what firms typically or often do (for example, “A fintech that offers accounts through a partner bank often has the least visibility”).

  547. · FTX’s favored account was a setting in the code, and banks have settings too

    Reworded as our view unsourced statements about what most firms find and about a trend in supervision (for example, “Regulators increasingly examine how firms govern the code”).

  548. · FTX’s favored account was a setting in the code, and banks have settings too

    Reworded as our view or as a possibility unsourced statements about what fintechs and their engineering teams typically or often do (for example, “The override path is usually the least documented part”).

  549. · After the FTC’s Log4j warning, the response record was the defense

    Removed unsourced statements that software bills of materials became a common request in procurement and that tracked vulnerability incidents are common practice in regulated firms; the latter is now stated as our view.

  550. · After the FTC’s Log4j warning, the response record was the defense

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “Tabletop exercises usually rehearse an intrusion”).

  551. · The FTC’s breach rule proposal drew the HIPAA line through the middle of a data flow

    Reworded as our view or as a possibility unsourced statements about what health and life sciences companies typically or often do (for example, “Testing often turns up flows no one designed”).

  552. · From crisis call to compliance record: OFAC’s ransomware advisory

    Removed or reworded as our view unsourced statements about how widely or how often organizations did something (for example, “blockchain analytics tools … became a standard part of their controls”).

  553. · From crisis call to compliance record: OFAC’s ransomware advisory

    Reworded as our view or as a possibility unsourced statements about what victims, banks and attackers typically or often do (for example, “The victim then usually brings in a specialist incident response firm”).

  554. · Four weeks on paper: what Scripps exposed about downtime plans

    Reworded unsourced statements about what most or many hospitals and organizations do (for example, “Most hospitals already have an incident command structure for disasters”) as conditions or our view.

  555. · Four weeks on paper: what Scripps exposed about downtime plans

    Reworded as our view or as a possibility unsourced statements about what attackers, insurers and health care organizations typically or often do (for example, “Attackers usually seize those services early”). Replaced five press sources (NBC 7 San Diego, KPBS, two HIPAA Journal articles, Healthcare Dive) with Scripps’s own notice to patients and financial disclosure, the 2023 study on PubMed Central, a CMS release and Ascension’s own financial reports. Reworded to what those sources state: Scripps restored all systems by May 26, 2021; the incident cost about $112.7 million, against which $20 million of insurance recoveries were accrued; Ascension became aware of its attack on May 8, 2024, restored EHR access in mid-June and had substantially completed notifications by December 31, 2024; CMS issued more than $2.55 billion in accelerated payments to over 4,200 Part A providers. Removed unsourced details: the hospital and facility counts, backup servers, the patient portal, named hospitals on diversion, the 147,000 and 5.6 million notification counts, the $91.6 million and $21.1 million split, the class actions and the 2023 settlement. On 2026-11-15 we sourced the Universal Health Services figure to its 2020 Form 10-K (reworded to its estimated aggregate unfavorable pre-tax impact of about $67 million) and the October 2020 joint advisory to CISA advisory AA20-302A, cut the Joint Commission alert paragraph (its site could not be opened), the unsourced Colonial Pipeline and Irish health service dates and the Ascension notification sentence, reworded the Change Healthcare paragraph to what CMS states, and replaced the UnitedHealth 8-K and 405(d) sources with the HIPAA Security Rule proposal in the Federal Register.

  556. · Four regulators, no new law: the AI statement put the buyers of models on the hook

    Added to the hindsight that the CFPB withdrew its 2022 and 2023 adverse action circulars as of May 12, 2025.

  557. · Four regulators, no new law: the AI statement put the buyers of models on the hook

    Removed or reworded unsourced statements about what most or many organizations do (for example, “Most banks, health systems, employers and agencies do not build the models they use” and “Leaders most often miss this part”). Updated the Colorado sentence: SB 26-189, signed May 14, 2026, repealed and reenacted SB 24-205, with developer duties from January 1, 2027; the earlier text described only the 2025 delay to June 2026. The tenant screening statement of interest is now described as the April 2023 joint statement describes it, which replaced a press release among the sources. Replaced an unsourced account of the tenant screening case’s late 2024 settlement (about $2.3 million) with the court’s July 2023 ruling letting the Fair Housing Act claims go forward, now a listed source; the 2022 circular remains described through the CFPB’s September 2023 release and its May 2025 withdrawal notice. Removed an unsourced account of rulings in Mobley v. Workday, a discrimination case against a hiring software vendor.

  558. · Forbearance on request: what the CARES Act asked of loan servicers

    Reworded an unsourced statement about what many institutions found (“Many institutions found that accommodation records lived in different systems”).

  559. · Forbearance on request: what the CARES Act asked of loan servicers

    Reworded as a possibility unsourced statements about what servicers, members and borrowers typically or often do (for example, “Members often called a branch, not a call center”).

  560. · For SNAP systems, paying less was harder than paying nothing

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “SNAP households often have little cushion”).

  561. · For many Medicare patients, telehealth meant a phone call

    Reworded unsourced statements about what many organizations could not do and dropped unsourced “increasingly”.

  562. · For many Medicare patients, telehealth meant a phone call

    Reworded as our view or as a possibility unsourced statements about what patients, health systems and auditors typically or often do (for example, “An adult child, a spouse or a paid caregiver often held the phone”).

  563. · For credit unions, the 1033 outline was a question for the core processor

    Reworded an unsourced statement that most institutions rely on a vendor’s independent audit reports.

  564. · For credit unions, the 1033 outline was a question for the core processor

    Reworded as our view or as a possibility unsourced statements about what vendors, institutions and members typically or often do (for example, “Vendor first releases are often immature”).

  565. · Flat caps, rising subscriptions: how the debt deal squeezed federal IT from the inside

    Removed the unsourced word “widely” from the description of how the negotiators’ informal understanding on IRS funding was reported.

  566. · Flat caps, rising subscriptions: how the debt deal squeezed federal IT from the inside

    Reworded as our view or as a possibility unsourced statements about what agencies, contracting officers and vendors typically or often do (for example, “A small independent agency often buys through a governmentwide vehicle at list-adjacent prices”). Replaced an unsourced report of an informal understanding to repurpose about $20 billion more of the IRS funding with the rescissions Congress enacted in Public Law 118-47 in March 2024 ($10 billion and $10.2 billion), a listed source. Sourced GAO’s estimate that about 80 percent of federal IT spending goes to operating and maintaining existing investments, and its 2019 review of critical legacy systems, to GAO-19-471 (the text had said GAO reported the figure “for years”); sourced the July 2025 $5 trillion debt limit increase to Public Law 119-21; described the autumn 2025 shutdown by the lapse in appropriations dates the Bureau of Labor Statistics gives (October 1 to November 12, 2025), removing unsourced statements that it lasted 43 days, was the longest on record and ended with a continuing resolution; and removed an unsourced statement that GSA closed 18F in March 2025. Sourced the 2025 workforce reduction and the Deferred Resignation Program to the Office of Personnel Management, which said more than 300,000 employees left government in 2025, about half through the program, and removed the unsourced statement that the administration canceled or cut many federal contracts. To stay within the eight-source limit, removed the sentence on the October 1 to November 12, 2025 lapse in appropriations together with its Bureau of Labor Statistics source.

  567. · Five regulators’ AI questions read like an exam plan

    Removed or reworded as our view unsourced statements about how widely or how often organizations did something (for example, “Many institutions assumed AI would bring heavier model validation for every tool” and “a voluntary structure many institutions adopted”).

  568. · Five regulators’ AI questions read like an exam plan

    Reworded as our view or as a possibility unsourced statements about what institutions, vendors and staff typically or often do (for example, “Vendors often treat model details as proprietary”).

  569. · Five principles, three committees: the AI blueprint inside a hospital

    Removed or reworded as our view unsourced statements about how many hospitals did something or how widely a model or study was used (for example, “Most hospitals already have the relevant bodies”).

  570. · Five principles, three committees: the AI blueprint inside a hospital

    Reworded as a possibility unsourced statements about what hospitals, vendors and contracts often do (for example, “Contracts often limit vendor liability”).

  571. · First Republic’s white-glove service had no answer for an uninsured balance

    Removed unsourced statements about what most banks lacked and did in spring 2023 (for example, “three things most banks lacked”).

  572. · First Republic’s white-glove service had no answer for an uninsured balance

    Reworded as our view or as a possibility unsourced statements about what banks and their clients typically or often do (for example, “relationship managers often could not tell a worried client”).

  573. · FinCEN’s ransomware analysis turned well-written SARs into threat intelligence

    Removed unsourced statements that structured cyber fields became more common at larger institutions and that joint fraud, anti-money laundering and security work is now a standard expectation; reworded statements about many and most banks.

  574. · FinCEN’s ransomware analysis turned well-written SARs into threat intelligence

    Reworded as our view or as a possibility unsourced statements about what banks, criminals and customers typically or often do (for example, “A large bank typically has a financial intelligence unit”). On 2026-11-15 replaced the CyberScoop article with Chainalysis’s own ransomware report and attributed the payment estimates to Chainalysis by name.

  575. · FinCEN’s deepfake alert was a job-design problem for three groups of staff

    Reworded unsourced statements about what most or many institutions do and what regulators increasingly expect (for example, “Most institutions buy identity verification from specialist providers”) as conditions or our view.

  576. · FinCEN’s deepfake alert was a job-design problem for three groups of staff

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “Reviewers are usually measured on throughput and backlog age”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “The loop also gives leaders something they rarely have:”). On 2026-11-15 we replaced the CNN source with the Hong Kong government’s Legislative Council reply on deepfake fraud and added Arup’s chief information officer’s World Economic Forum interview, the FBI’s December 2024 warning, NIST SP 800-63A-4 and Governor Barr’s April 2025 speech; reworded the account of the case to the official one (a phishing email first, a pre-recorded conference, about HK$200 million sent to five local bank accounts), and cut the unsourced February police briefing, May confirmation, July 2024 regulator reminder, June 2025 request for comment, TAKE IT DOWN Act sentence and claims about vendors and voice authentication. On 2026-11-15 (N-146) the May 2025 FBI warning was reworded to match the FBI’s public service announcement I-051525-PSA (text and AI-generated voice messages since April 2025, to establish rapport before gaining access to personal accounts). On 2026-11-15 (N-147) the unsourced statement that many contact centers enrolled customers in voice biometrics was reworded as a condition, and the unsourced claims that the case became a shorthand, that re-reviews followed other warning signs, that older customers are the main targets of these scams, that the controls held across later cases and that the alert’s categories remained where deepfakes caused trouble were reworded to what FinCEN, the FBI and Governor Barr said or as our view; other unsourced statements about what institutions, vendors and attackers typically do were reworded as possibilities.

  577. · For FinCEN’s beneficial ownership launch, the hardest design problem was shrinking

    Removed unsourced “widely” descriptions of NIST guidance and of how the penalties were publicized.

  578. · For FinCEN’s beneficial ownership launch, the hardest design problem was shrinking

    Reworded as our view or as a possibility unsourced statements about what filers and agencies typically or often do (for example, “Retention rules are usually written for a program that continues”).

  579. · Final and already in court: sorting open banking work by how much you would regret it

    Reworded unsourced statements about what most banks offered and did (for example, “most banks offered no interface”) as conditions or our view.

  580. · Final and already in court: sorting open banking work by how much you would regret it

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “which is also usually supplied by a vendor”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “The gap tended to sit in details:”). On 2026-11-15 we replaced the Banking Dive and Cooley sources with the Eastern District of Kentucky’s October 29, 2025 opinion in Forcht Bank v. CFPB, reworded the litigation timeline to what the court states (dropping the May 2025 date and the Bureau’s expected 2026 comment review), and cut the unsourced 13,900 comment count, JPMorgan Chase fee plans and claim that large banks had begun seeking fees.

  581. · Filing is not finding: FinCEN’s effectiveness question meets the FinCEN Files

    Removed or reworded as our view unsourced statements about how widely or how often organizations did something (for example, “many banks have invested in entity resolution and analytics”).

  582. · Filing is not finding: FinCEN’s effectiveness question meets the FinCEN Files

    Reworded as our view or as a possibility unsourced statements about what banks and their staff typically or often do (for example, “Subpoenas usually arrive at the legal department”). Added the Justice Department releases on the June 2021 sentencing of the former FinCEN adviser and the October 2024 TD Bank plea, cut the unsourced statement that BuzzFeed News confirmed its source, and reworded the TD Bank figures to what the Justice Department states (more than $1.8 billion in criminal penalties; about $18.3 trillion unmonitored from January 2018 to April 2024) in place of the unsourced $3 billion total and FinCEN record-penalty claim. On 2026-11-15 an independent review (N-145) changed “criminal penalties” to “penalties”, since the Justice Department’s $1.8 billion includes forfeiture as well as the criminal penalty.

  583. · Why a file-transfer server belongs on the list of systems that hold PHI

    Removed or reworded unsourced statements about how widely GoAnywhere was deployed and what most health systems and insurers did (for example, “file-transfer software most health systems saw as mere plumbing”).

  584. · Why a file-transfer server belongs on the list of systems that hold PHI

    Reworded as our view or as a possibility unsourced statements about what health systems, integration teams and investigators typically or often do (for example, “Integration teams often install file-transfer tools”). Removed the BleepingComputer source and attributed the claim of about 130 victims to the CISA and FBI advisory AA23-158A, which states it; cut the unsourced statements that Clop deployed no ransomware, claimed the Cleo campaign and ran an Oracle E-Business Suite campaign, and added CISA’s Known Exploited Vulnerabilities Catalog as the source for the GoAnywhere and Cleo listings. On 2026-11-15 an independent review (N-145) removed a journalist’s name and the press-only date the warning became public, and limited the “took data without encrypting anything” sentence to the GoAnywhere and MOVEit campaigns, since Microsoft linked the 2025 GoAnywhere exploitation to a ransomware operation. On 2026-11-15 (N-146) the consolidation of the MOVEit lawsuits in Massachusetts was sourced to the court’s December 2024 order in the multidistrict litigation. On 2026-11-15 (N-147) the unsourced claim that many MOVEit victims learned of their exposure from a vendor or partner was cut, and the scale and kinds of MOVEit victims were reworded to the court’s summary of the consolidated complaint; Fortra’s April 17, 2023 investigation summary, Microsoft’s October 2025 report on CVE-2025-10035, the SEC’s July 26, 2023 release and HHS’s January 2025 proposed Security Rule were added as sources; the press-only details of how the warning spread, the proof-of-concept code, the February 7 patch date, the Accellion victims, Hatch Bank and the other disclosures, the proposal’s comments and UnitedHealth Group’s 190 million figure were cut, the claim that many installations exposed the console was corrected to Fortra’s statement that those customers were a small minority, and unsourced statements about what organizations and products often do were reworded as our view or as possibilities.

  585. · Few banks held crypto. Many held crypto deposits.

    Reworded as our view unsourced statements about what many or most banks did and how coverage read the January 2023 statement (for example, “The third category was where most banks and credit unions actually sat”).

  586. · Few banks held crypto. Many held crypto deposits.

    Reworded as our view or as a possibility unsourced statements about what banks and examiners typically or often do (for example, “The treasurer usually owned the deposit analytics”).

  587. · Fedwire’s ISO 20022 switch gave banks rich payment data their core systems still truncate

    Removed or reworded as our view or a condition unsourced statements about how widely or how often organizations did something (for example, “many banks translated incoming ISO 20022 messages”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “budgets and people are often moved to whatever is due next”). Replaced the RedCompass Labs source with an Internet Archive copy of Swift’s own August 27, 2026 notice, and reworded the expected timing to Swift’s promise of an update by December at the latest.

  588. · The Federal Data Strategy’s hardest actions were about people

    Attributed the M-19-23 requirement for a data governance body by September 30, 2019 to the 2020 Action Plan, which states it; corrected “A fourth objection” to “A sixth objection”; kept to what GAO said about the Chief Data Officer Council’s authorization (that under the Evidence Act it would expire in December 2024, two years after GAO’s December 2022 report); tied the epidemiology example to the series OPM’s memo names; reworded as our view or as possibilities unsourced statements about what usually, often or most agencies or plans do.

  589. · Part 370’s exit moves the math to the FDIC, not the data work

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “changes to core deposit systems often travel in a vendor’s or the bank’s own release cycle”).

  590. · Once FDA read with AI, sponsors’ inconsistencies got cheaper to find

    Removed or reworded as our view or a condition unsourced statements about how widely or how often organizations did something (for example, “its staff adopted them widely”).

  591. · Once FDA read with AI, sponsors’ inconsistencies got cheaper to find

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “Large pharmaceutical companies usually have in-house regulatory operations”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “It will rarely be told whether a tool was involved.”). Removed the CNN source and the July 2025 claims it carried about Elsa inventing studies, and added FDA’s December 1, 2025 agentic AI announcement, the HHS March 2025 restructuring fact sheet and EMA’s 2024 reflection paper as sources for statements that had none.

  592. · Under FDA’s change-control model, the AI device a hospital validates will not stay the one it runs

    Reworded unsourced statements about how most or many hospitals run recalls and buy AI devices (for example, “Recall processes in most hospitals were designed for physical products”) as conditions.

  593. · Under FDA’s change-control model, the AI device a hospital validates will not stay the one it runs

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “Hospitals usually read FDA device guidance as the manufacturer’s concern”).

  594. · FDA’s decision support revision handed hospitals a classification question

    Removed or reworded as our view or a condition unsourced statements about how widely or how often organizations did something (for example, “or, increasingly, an AI model”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “extend features, often through automatic software updates”). Replaced the Latham & Watkins and Covington client alerts with the FDA docket on Regulations.gov and the transcript of FDA’s March 11, 2026 town hall, and cut the unsourced account of the commissioner’s video and trade-show promotion.

  595. · Banned from the market, still on the wall: the FCC’s equipment order and the installed base

    Removed or reworded as our view unsourced statements about how common practices are (for example, “Many agencies now buy video surveillance as a hosted service”).

  596. · Banned from the market, still on the wall: the FCC’s equipment order and the installed base

    Reworded as our view or as a possibility unsourced statements about what agencies, installers and vendors typically or often do (for example, “Installers often open a port on the agency’s firewall”).

  597. · Faster settlement, longer nights: what two years of T+1 tell Europe’s operations desks

    Removed or reworded as our view or a condition unsourced statements about how widely or how often organizations did something (for example, “Same-day matching failed most often on reference data”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “The weak ones tend to make the same errors:”).

  598. · Exempt institution, covered data: what Proposition 24 meant for banks and hospitals

    Removed or reworded as our view unsourced statements about how widely or how often organizations did something (for example, “Many organizations treated that window as a safety net”).

  599. · Exempt institution, covered data: what Proposition 24 meant for banks and hospitals

    Reworded as our view or as a possibility unsourced statements about what banks, credit unions and health systems typically or often do (for example, “Marketing teams often add those without involving compliance”). Replaced the Paul, Weiss client memo with the Virginia Code section on the Consumer Data Protection Act’s scope and exemptions, and cut the unsourced counts of states (“close to twenty”) and the claim that Virginia was the first.

  600. · Executive Order 14028 gave zero trust three testable demands

    Removed or reworded as our view unsourced statements about what many organizations and agencies did or lacked after SolarWinds (for example, “many agencies found their tools were not built for it”).

  601. · Executive Order 14028 gave zero trust three testable demands

    Reworded as our view or as a possibility unsourced statements about what agencies and attackers typically or often do (for example, “A state or local agency usually buys through cooperative contracts and resellers”).

  602. · Every unemployment fraud control had a cost to real claimants

    Reworded unsourced statements about what many state systems and agencies relied on (for example, “Many agencies bought identity verification as a service”).

  603. · Every unemployment fraud control had a cost to real claimants

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “People without bank accounts often use prepaid cards”). Replaced the KrebsOnSecurity, Associated Press and Journal of Accountancy sources with the Washington State Auditor’s April 2021 performance audit, Agari’s own May 2020 report and IRS release IR-2022-27, added the Labor Department inspector general’s May 26, 2020 alert memo, reworded the Secret Service alert, Agari findings, recoveries and IRS change to what those sources say, and cut the unsourced memo details (states named, first responders, potential losses), the Oklahoma bankers, the $550 million to $650 million estimate, the $333 million recovery figure and the Equifax example. On 2026-11-15 an independent review (N-145) said the stolen personal details had likely come from earlier data breaches, as the State Auditor’s report puts it.

  604. · Why Europe’s accessibility law turns every bank release into evidence

    Removed or reworded as our view or a condition unsourced statements about how widely or how often organizations did something (for example, “Many banks ran the Act as a project with an end date”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “the main journeys are usually in good shape”).

  605. · For EU consumer lenders, the credit-scoring deadline that mattered was never the AI Act’s

    Removed or reworded as our view or a condition unsourced statements about how widely or how often organizations did something (for example, “European law increasingly treats the lender”).

  606. · For EU consumer lenders, the credit-scoring deadline that mattered was never the AI Act’s

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “complaints are often what draw supervisors’ attention in the first place”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “tends to tell others”).

  607. · An escort who cannot read the command is not a security control

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “Routine operations are often automated”). Replaced the four ProPublica sources with Senator Tom Cotton’s July 17, 2025 letter, the Defense Department’s August 28, 2025 news story, section 1692 of the FY2026 defense authorization act and 10 U.S.C. 4872, and dropped the unsourced July 15 date, the description of escorts typing commands, the “sensitive but unclassified” detail and Microsoft’s statement; the September 2025 vendor ban now reads as what Hegseth and the law said.

  608. · CISA’s encryption advice and the SEC’s recordkeeping cases asked for the same channel

    Reworded unsourced statements about what many organizations, firms and institutions do and how widely the guidance was read (for example, “was read widely across industries”) as conditions or our view.

  609. · CISA’s encryption advice and the SEC’s recordkeeping cases asked for the same channel

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “Examiners and auditors rarely accept “the connector is on” as evidence”). Replaced an unsourced report that the 2023 attack on MGM Resorts began with a help desk call with the FBI and CISA’s November 2023 advisory on help desk calls by the Scattered Spider group. Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “A staged approach tends to work better than a single deadline.”).

  610. · Eligible but unreachable: Medicaid unwinding ran on contact data

    Reworded an unsourced statement that many hospitals can use presumptive eligibility.

  611. · Eligible but unreachable: Medicaid unwinding ran on contact data

    Reworded as our view or as a possibility unsourced statements about what states, enrollees and managed care organizations typically or often do (for example, “they often know where people are better than the state does”). Replaced the HFMA and KFF sources with CMS’s September 21, 2023 press release, MACPAC’s November 2024 brief on state-reported unwinding data, Public Law 119-21 and CMS’s monthly enrollment dataset, and reworded the reinstatement, disenrollment, ex parte, work requirement and June 2026 enrollment figures to what those sources state.

  612. · Revised advisories: in April 2024, the vendor’s first word on an edge device was rarely its last

    Reworded unsourced statements about what most organizations use at the network edge and what smaller agencies lack.

  613. · Revised advisories: in April 2024, the vendor’s first word on an edge device was rarely its last

    Reworded as our view or as a possibility unsourced statements about what vendors and attackers typically or often do (for example, “early advice is often a best guess”).

  614. · The easiest part of a card rate cap is cutting the rate

    Removed or reworded as our view or a condition unsourced statements about how widely or how often organizations did something (for example, “Most banks, especially community banks and credit unions, do not run their own card computer systems”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “remediation costs tend to concentrate”). Replaced the three Reuters reports with the President’s own Truth Social post (Internet Archive copy), the White House account of his January 21 Davos speech and CRS In Focus IF12861, and cut the unsourced bank share moves and the reported Bank of America and Citi 10% card plans.

  615. · Each Archegos lender already held enough data to act

    Removed or reworded as our view unsourced statements about how widely or how often organizations did something (for example, “Archegos is usually told as a story of bets hidden across many banks”).

  616. · Each Archegos lender already held enough data to act

    Reworded as our view or as a possibility unsourced statements about what banks, clients and examiners typically or often do (for example, “Professional clients often trade through several entities”).

  617. · DORA’s two-year runway, measured in contract renewals

    Removed or reworded unsourced statements about what many or most firms did under DORA (for example, “Most firms organized remediation in waves”).

  618. · DORA’s two-year runway, measured in contract renewals

    Reworded as our view or as a possibility unsourced statements about what financial firms and their ICT providers typically or often do (for example, “Older contracts rarely allowed a customer to commission simulated attacks”). Sourced the July 2024 CrowdStrike outage to CISA’s alert and Microsoft’s estimate of 8.5 million devices, and replaced an unsourced list of the financial firms affected with Microsoft’s description of those affected.

  619. · DORA’s register of information made every bank a data supplier to EU oversight of its vendors

    Reworded unsourced statements about what most or many firms found or did under DORA (for example, “contract terms … became standard requests”) as conditions or our view.

  620. · DORA’s register of information made every bank a data supplier to EU oversight of its vendors

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “Different vendors often rely on the same few cloud and infrastructure providers”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “Their registers tend to reveal old contracts”).

  621. · Major incident, by formula: DORA’s first standards moved the call from judgment to data

    Reworded unsourced statements about what most organizations and banks do and what many firms assumed (for example, “Most banks held their list of critical or important functions in a business impact analysis”).

  622. · Major incident, by formula: DORA’s first standards moved the call from judgment to data

    Reworded as our view or as a possibility unsourced statements about what banks and their incident teams typically or often do (for example, “The fix is mechanical but rarely done”). Sourced the July 2024 CrowdStrike outage to CISA’s alert and Microsoft’s estimate of 8.5 million devices, and replaced an unsourced list of sectors disrupted with Microsoft’s description of those affected.

  623. · The dollar AI deals ended in a meter, and meters need ceilings

    Removed or reworded as our view or a condition unsourced statements about how widely or how often organizations did something (for example, “so many agencies did”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “introductory pricing rarely lasts”). Replaced the two FedScoop sources with Internet Archive copies of GSA’s OneGov page from July 22 and October 13, 2026 (expiry dates of September 30, then October 31 and November 15), and cut the press-reported details on non-renewing subscriptions, per-user renewal pricing, the former federal CIO’s remarks and GSA’s renewal statement.

  624. · DOJ’s accessibility delay moved one date and put the budget at risk

    Removed or reworded as our view or a condition unsourced statements about how widely or how often organizations did something (for example, “Many agencies justified accessibility work”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “Agencies that measure where those calls come from often find”). Replaced the Seyfarth Shaw blog post with the National Federation of the Blind’s own complaint as filed in federal court.

  625. · Dobbs moved health privacy risk outside the medical record

    Removed unsourced statements about how widely tracking pixels spread and where most health systems found their work.

  626. · Dobbs moved health privacy risk outside the medical record

    Reworded as our view or as a possibility unsourced statements about what health systems and their vendors typically or often do (for example, “Marketing teams added them to measure campaigns and improve conversion, often without privacy review”).

  627. · Direct File’s exit made retirement part of service design

    Removed or reworded as our view or a condition unsourced statements about how widely or how often organizations did something (for example, “many companies face sooner or later”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “They rarely plan for the end.”). Replaced the CPA Practice Advisor and Nextgov/FCW reports with Treasury’s October 2025 report to Congress and CRS In Focus IF13314, rewording the return count and the suspension to what they state, and cut the unsourced November notice to states, the Bessent remark and the “no future launch date” statement.

  628. · A deleted file, a national ground stop, and the runbook nobody rehearsed

    Reworded unsourced statements about what many agencies and organizations do (for example, “Many organizations now use tools that issue administrative access only for a specific task”).

  629. · A deleted file, a national ground stop, and the runbook nobody rehearsed

    Reworded as our view or as a possibility unsourced statements about what agencies, IT teams and their vendors typically or often do (for example, “Legacy systems often lack some of these”). Sourced the July 2024 CrowdStrike outage to Microsoft’s estimate and CrowdStrike’s own root cause analysis, replaced an unsourced list of those disrupted (airlines, hospitals, emergency call centers) with Microsoft’s description, removed an unsourced statement that the update reached every customer at nearly the same time, and described CrowdStrike’s changes as its review does.

  630. · DeepSeek arrived in three forms in one week, and each needed a different control

    Added to the hindsight that SR 11-7 and OCC Bulletin 2011-12 were superseded on April 17, 2026, by SR 26-2 and OCC Bulletin 2026-13, which leave generative and agentic AI models out of scope, and put the description of SR 11-7 as current guidance in the past tense.

  631. · DeepSeek arrived in three forms in one week, and each needed a different control

    Removed an unsourced statement that enterprise AI platforms increasingly offered multi-model routing as a standard feature, and reworded other unsourced statements about what many organizations did (for example, “Many organizations responded with a single rule”).

  632. · DeepSeek arrived in three forms in one week, and each needed a different control

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “Credit unions and smaller institutions often adopt a lighter version of the same approach”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “something they rarely have with AI”). Replaced the Reuters report (via Korea JoongAng Daily) with NIST’s announcement of the CAISI evaluation of DeepSeek models, cut the unsourced Nvidia market-value figures, V3 training-cost figures, Navy, Texas, Cisco, Taiwan, Australia, South Korea and OMB details, and kept the Wiz source as Wiz’s own finding. On 2026-11-15 an independent review (N-145) reworded the claim that government restrictions on the app spread to what the Italian data protection authority’s January 30, 2025 order states, the only restriction the sources document. On 2026-11-15 (N-146) the unsourced details of V3’s technical report (the December 26 release date, the low cost of the final training run on Nvidia H800 chips and its exclusions) and the hindsight paragraph built on them were cut, and that paragraph now reports NIST’s September 2025 finding that DeepSeek models cost more to use than comparable U.S. models; V3’s December 2024 launch is now attributed to AWS’s announcement, the source cap leaving no room for the report itself. On 2026-11-15 (N-147) the unsourced statements that U.S. technology stocks fell on January 27 and the hindsight paragraph on the short-lived sell-off and AI infrastructure spending were cut, as were the App Store ranking, DeepSeek’s registration limit, the privacy policy’s server location, the SEC off-channel sweep, state device bans, the Cisco test results and the claim that the AI Action Plan encouraged open-weight AI; the app’s reach is now attributed to the Italian data protection authority, the Action Plan to NIST’s release, and other unsourced statements about prices, markets and what organizations did were reworded as our view or as possibilities.

  633. · Data stayed in China and still left: PIPL’s remote access problem

    Reworded an unsourced statement about many banks and insurers as a general consequence of the rule.

  634. · Data stayed in China and still left: PIPL’s remote access problem

    Reworded as possibilities unsourced statements about what global companies and their vendors typically or often do (for example, “Global companies typically set these systems up once”). On 2026-11-15 replaced the DigiChina (Stanford) translation with the official Chinese text of the law published by the Cyberspace Administration of China.

  635. · Cyclops Blink turned forgotten firewalls into someone else’s infrastructure

    Removed unsourced statements about what many organizations do (for example, “Many organizations block traffic from countries where they do no business”).

  636. · Cyclops Blink turned forgotten firewalls into someone else’s infrastructure

    Reworded as our view or as a possibility unsourced statements about what agencies and device owners typically or often do (for example, “Small agencies often skip this”).

  637. · Cybersecurity donations priced risk by the connection

    Separated the information blocking rule’s effective date (June 30, 2020) from the compliance date for part 171 that the rule set as published (November 2, 2020), and no longer say the security exception had to be met from the effective date; reworded as our view or as possibilities unsourced statements about what usually or often happens. Added that an interim final rule (85 FR 70064, November 4, 2020) moved the part 171 compliance date to April 5, 2021, and cited it in place of the archived HHS press release.

  638. · A cyber grant with a rising match is a sustainment test

    Removed or reworded unsourced statements about how incidents were reported and what most organizations can do (for example, “Security software is increasingly sold as a subscription”).

  639. · A cyber grant with a rising match is a sustainment test

    Reworded as our view or as a possibility unsourced statements about what governments, vendors and banks typically or often do (for example, “Renewal prices often rise after the first term”). On 2026-11-15 replaced the Cornell Legal Information Institute copy of 6 U.S.C. § 665g with the official United States Code on govinfo.gov.

  640. · CSF 2.0’s biggest addition was the one a security team could not deliver

    Removed or reworded unsourced statements about what most or many organizations and banks did (for example, “so most organizations responded the usual way”).

  641. · CSF 2.0’s biggest addition was the one a security team could not deliver

    Reworded as our view or as a possibility unsourced statements about what banks, hospitals, boards and examiners typically or often do (for example, “Security teams often rate vulnerabilities by technical severity”).

  642. · Crypto trust charters and community banks: the binding decision sits in the core

    Removed or reworded as our view or a condition unsourced statements about how widely or how often organizations did something (for example, “the decision most institutions underestimate”).

  643. · Crypto trust charters and community banks: the binding decision sits in the core

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “Boards are often surprised that the second rung, which feels modest, carries most of the compliance cost”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “Bank crypto questions tend to arrive disguised”).

  644. · A credit union’s promises in an outage are set by its architecture, years before the attack

    Reworded unsourced statements about what is standard or what many institutions do (for example, “it is standard practice”, “many institutions decide not to pay”).

  645. · A credit union’s promises in an outage are set by its architecture, years before the attack

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “Attackers typically get in unnoticed”). Sourced the July 2024 CrowdStrike outage to CISA’s alert and Microsoft’s estimate of 8.5 million devices, and removed an unsourced list of sectors disrupted (banks, hospitals, airlines). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “Forensic scope tends to widen like this”). Replaced the BleepingComputer and National Mortgage News sources with Patelco’s notice of data breach and the Maine attorney general’s record of its amended notice (1,009,472 people), cut the 726,000 first count, the RansomHub claim and advisory paragraph, the $7.25 million settlement and class action timing (sourced only to Pleasanton Weekly, now removed), the press-reported asset figure and the unsourced Evolve and CDK paragraph.

  646. · A credit union’s first report of a vendor breach may come from the attacker

    Reworded unsourced statements about how many banks, credit unions and institutions use particular software and identity checks.

  647. · A credit union’s first report of a vendor breach may come from the attacker

    Reworded as our view or as a possibility unsourced statements about what vendors, attackers and credit unions typically or often do (for example, “Vendors usually run at least two separate environments”). Replaced the CyberScoop and ABC7 sources with the Justice Department’s December 19, 2023 ALPHV announcement and the NCUA’s 2024 cybersecurity report to Congress, and cut the unsourced exit-scam account, the $22 million payment, the fake seizure notice and the Trellance and FedComp names.

  648. · Credit for security practice, payable only in arrears

    Removed or reworded as our view unsourced statements about how widely or how often organizations did something (for example, “Applications increasingly asked whether MFA protected remote access”).

  649. · Credit for security practice, payable only in arrears

    Reworded as our view or as a possibility unsourced statements about what organizations, counsel and investigators typically or often do (for example, “Health systems often use the 405(d) practices”). On 2026-11-15 replaced the Physicians Practice article with the Fall 2025 Unified Agenda entry for the Security Rule (RIN 0945-AA22), which lists the final action for July 2027.

  650. · Europe’s 24-hour vulnerability clock reports to regulators first and customers second

    Removed or reworded as our view or a condition unsourced statements about how widely or how often organizations did something (for example, “Most organizations now depend on technology”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “The failures tend to run the other way.”). Replaced the Hogan Lovells summary with the text of the Cyber Resilience Act (Regulation (EU) 2024/2847) in the Official Journal, which states the user-notice duty, the medical device exclusion and the application dates.

  651. · Convincing faces, unauthenticated seats: the Hong Kong deepfake was a meeting-identity failure

    Reworded unsourced statements about what most or many organizations, firms and banks do and about trends among clients and supervisors (for example, “a channel that most organizations treat as trusted by default”).

  652. · Convincing faces, unauthenticated seats: the Hong Kong deepfake was a meeting-identity failure

    Reworded as our view or as a possibility unsourced statements about what executives, their staff, smaller institutions and insurers typically or often do (for example, “Insurance often responds less fully than expected”). Replaced an unsourced report that the 2023 attackers of MGM Resorts started by calling its help desk with the FBI and CISA’s November 2023 advisory on help desk calls by the Scattered Spider group. Replaced the two CNN sources with the Hong Kong government’s Legislative Council reply on deepfake fraud and Arup’s chief information officer’s interview with the World Economic Forum, reworded the account of the case to the official one (a pre-recorded conference, transfers to five local bank accounts, a phishing email first), added the FBI’s December 2024 warning, and cut unsourced statements about 15 transfers, the May 2024 identification and attempts against WPP and Ferrari.

  653. · Congress regulated connected devices by deciding what agencies may buy

    Removed or reworded as our view unsourced statements about how widely or how often organizations did something (for example, “Examiners and auditors increasingly ask”; replaced “a standard expectation for federal suppliers” and an unsourced statement that many private buyers adopted it with what the IoT Cybersecurity Improvement Act provides).

  654. · Congress regulated connected devices by deciding what agencies may buy

    Reworded as our view or as a possibility unsourced statements about what device makers and buyers typically or often do (for example, “Connected devices are often bought outside the IT budget”).

  655. · Surveyors counted the people hospitals don’t employ: the CMS staff rule after the Supreme Court

    Removed or reworded unsourced statements about most or many hospitals’ revenue, staffing and practices (for example, “many hospitals were short of staff”).

  656. · Surveyors counted the people hospitals don’t employ: the CMS staff rule after the Supreme Court

    Reworded as our view or as a possibility unsourced statements about what hospitals and their teams typically or often do (for example, “Ownership is where these efforts usually stall”).

  657. · CMS would switch off a nursing home data feed but keep the switch

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “Someone produces a file, often from a report in the health record”).

  658. · Paused, not repealed: what CMMC’s suspension left defense contractors paying for

    An earlier version said the department froze later CMMC phases and told contracting offices to remove third-party and Level 3 requirements. DFARS Class Deviation 2026-O0025, Revision 3, says the July 13 memo suspended the November 2026 Phase 2 transition, still permitted Level 1 and Level 2 self-assessments, and had contracting officers remove or revise CMMC requirements; we have corrected the text to match.

  659. · Paused, not repealed: what CMMC’s suspension left defense contractors paying for

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “Someone, often the head of IT or a security manager”). Replaced the DefenseScoop and Secureframe sources with the CIO’s July 13, 2026 reform memo (Internet Archive copy), 32 CFR 170.3 and the DFARS CMMC rule effective November 10, 2025, and cut the press-reported figure of about 1,100 responses to a request for information and the CIO’s reported intention to publish the report. On 2026-11-15 (N-146) two unsourced generalizations (“many solicitations”, “many smaller suppliers budgeted for it”) were reworded to the rule’s intent and as a possibility.

  660. · CMMC’s first phase priced a signature, not a score

    DFARS Class Deviation 2026-O0025, Revision 3, names the Department of War CIO’s memorandum suspending the CMMC Phase 2 requirements as dated July 13, 2026; we have added the deviation to the sources.

  661. · CMMC’s first phase priced a signature, not a score

    Removed or reworded as our view or a condition unsourced statements about how widely or how often organizations did something (for example, “Many organizations drew their assessment boundaries for the first time”).

  662. · CMMC’s first phase priced a signature, not a score

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “this was often the first time the question reached leadership”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “Programs tend to fail in familiar ways.”). On 2026-11-15, added an Internet Archive copy of the Department of War’s July 13, 2026 announcement as the source for the Phase 2 suspension, task force and request for information, which the Cyber AB statements had been carrying, kept the Cyber AB’s suspension statement only for its own view, and removed its response to the request for information, which no text now relies on.

  663. · The client-certificate deadline that moved, and the certificate authorities that didn’t wait

    Removed or reworded as our view or a condition unsourced statements about how widely or how often organizations did something (for example, “places most organizations had never mapped”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “Responsibility is usually scattered.”).

  664. · Clearance, access and need-to-know: three controls the Discord leak pulled apart

    Reworded as our view unsourced statements about what most or many organizations have and about a trend in regulators’ expectations (for example, “Most organizations have some version of that arrangement today”).

  665. · Clearance, access and need-to-know: three controls the Discord leak pulled apart

    Reworded as a possibility unsourced statements about how organizations often run access controls (for example, “need-to-know is often enforced coarsely”).

  666. · Citrix gateways: the most exposed system in the hospital

    Removed or reworded as our view unsourced statements about what many hospitals and organizations did (for example, “Many organizations patched and moved on”) and dropped unsourced “widely”.

  667. · Citrix gateways: the most exposed system in the hospital

    Reworded as our view or as a possibility unsourced statements about what hospitals, staff and insurers typically or often do (for example, “IT administrators often use the same gateway”).

  668. · Citi’s orders put data lineage on the safety and soundness agenda

    Removed or reworded as our view unsourced statements about how widely or how often organizations did something (for example, “The definition is the part most often skipped and most often wrong”).

  669. · Citi’s orders put data lineage on the safety and soundness agenda

    Reworded as our view or as a possibility unsourced statements about what banks and their teams typically or often do (for example, “The result is often a simple diagram”). Replaced the Banking Dive source with the Second Circuit’s September 2022 opinion, reworded the Revlon passages to what the opinion states (about $385 million returned, roughly $500 million refused, judgment vacated and remanded rather than reversed), and cut the Financial Times $81 trillion near-miss account, the unsourced claim about loan-documentation changes and the unsourced statement about Citi’s 2026 filings.

  670. · Cisco’s Splunk deal and the case for owning your security logs outside the SIEM

    Reworded unsourced statements about how widely Splunk and MITRE ATT&CK were used and what many or most organizations do (for example, “Splunk was widely deployed in banks, health systems and government agencies”).

  671. · Cisco’s Splunk deal and the case for owning your security logs outside the SIEM

    Reworded as our view or as a possibility unsourced statements about what banks, agencies and security teams typically or often do (for example, “Federal buyers usually purchase through government-wide contract vehicles”).

  672. · Chip policy ran on a decade’s clock; IT backlogs ran on a quarter’s

    Removed or reworded as our view unsourced statements about what many organizations and most banks and health systems did (for example, “Provenance, which most banks and health systems did not consider in 2022”).

  673. · Chip policy ran on a decade’s clock; IT backlogs ran on a quarter’s

    Reworded as our view or as a possibility unsourced statements about what agencies, examiners and manufacturers often or usually do (for example, “Public agencies often buy through cooperative contracts”).

  674. · Cheap to license, slow to permit: federal AI’s bottleneck moved to the CISO’s desk

    Restated the September 2026 OneGov agreement with OpenAI as GSA announced it: GSA said the offer was expected to take effect on October 1, 2026, and its announcement does not confirm the start.

  675. · Cheap to license, slow to permit: federal AI’s bottleneck moved to the CISO’s desk

    Removed or reworded as our view or a condition unsourced statements about how widely or how often organizations did something (for example, “The workable path for most agencies”).

  676. · Cheap to license, slow to permit: federal AI’s bottleneck moved to the CISO’s desk

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “Federal software purchases usually stall on money”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “In most large organizations, file permissions have drifted for years”).

  677. · Cheap contracts, valuable access: the market behind Coinbase’s bribed agents

    Removed or reworded as our view or a condition unsourced statements about how widely or how often organizations did something (for example, “Most institutions never set a wage at their outsourcing provider”).

  678. · Cheap contracts, valuable access: the market behind Coinbase’s bribed agents

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “Outsourcing contracts often cap the provider’s liability”).

  679. · A chatbot’s history sidebar is a records system with someone else’s retention policy

    Removed or reworded as our view unsourced statements about industry practice and adoption (for example, “The episode became a standard example in corporate AI policies” and “Excluding data from training is now standard in enterprise terms”). Replaced the BleepingComputer source with OpenAI’s own account of the March 20 outage, and reworded the outage sentence to match it. On 2026-11-15 (N-146) the press-only report that several big banks, JPMorgan Chase among them, had limited employee use of ChatGPT was cut, along with the unsourced statements that some large employers had restricted use and that health systems were mostly further behind; the December 2022 HHS tracking-technology bulletin is now sourced to an Internet Archive copy of HHS’s page. On 2026-11-15 (N-147) the press-only Samsung example and the mid-2025 withdrawal of search indexing for shared conversations were cut, the latter replaced by our view on sharing links; OpenAI’s April 25, 2023 and August 28, 2023 announcements and its statement on the New York Times preservation order were added as sources, and the order is now described as OpenAI states it; the unsourced Rome court ruling, the March 2023 launch dates of GPT-4, Microsoft 365 Copilot, Bard and plugins, the March 1 API policy date, Microsoft 365 Copilot’s general availability, the HTI-1, Section 1557, AB 3030 and NIST profile details and the spread of ambient documentation tools were cut, and unsourced statements about what staff, vendors and organizations commonly did were reworded as our view or as possibilities.

  680. · Channel File 291 measured every recovery plan in hands per device

    Removed or reworded unsourced statements about what most or many organizations did or found during the July 19, 2024 outage (for example, “Many organizations found after July 19 that this step took longer than the recovery itself”).

  681. · Channel File 291 measured every recovery plan in hands per device

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “Software license terms commonly cap a vendor’s liability, often at the fees paid”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “Procedures written by experts tend to skip steps”). Added CISA’s CrowdStrike outage alert and Delta’s September 2024 Form 10-Q; reworded the Delta disruption to Delta’s own figures (about 7,000 cancellations over five days, $380 million revenue impact, $170 million extra costs) and the fake-fix warning to what CISA reported; cut the unsourced ground stops, the Department of Transportation investigation, the Parametrix loss estimate, the September 2024 hearing and Microsoft summit sentences, CrowdStrike’s own suit against Delta, and the unsourced crew tracking details.

  682. · Days of cash on hand was the resilience metric that mattered in the Change Healthcare outage

    Reworded as our view unsourced statements about what many organizations found in their insurance after the outage (for example, “For many organizations, the outage was the first time they had read that part of their policy closely”).

  683. · Days of cash on hand was the resilience metric that mattered in the Change Healthcare outage

    Reworded as our view or as a possibility unsourced statements about what providers, lenders and vendors typically or often do (for example, “Large health systems often had a second clearinghouse relationship”).

  684. · The CFPB reached for payment apps while the customer’s money sat at partner banks

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “Firms that had grown fast under lighter scrutiny often have reasonable outcomes”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “A customer who has lost savings to a scam rarely cares”).

  685. · With the CFPB paused, banks lost the outside signals their customer programs relied on

    Reworded an unsourced statement about many institutions (“for many institutions the clock never fully stopped”) as a condition.

  686. · With the CFPB paused, banks lost the outside signals their customer programs relied on

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “A spike in complaints about a fee, a disclosure or a digital journey usually points to a design flaw”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “compete with every other project and tend to slip”). On 2026-11-15, replaced the Associated Press report (via PBS), the Orrick-hosted court filing and the Troutman Pepper Locke post with the D.C. district court’s March 28 and December 30, 2025 opinions in NTEU v. Vought and the CFPB’s May 12, 2025 Federal Register withdrawal of guidance; reworded Vought’s directives, the funding letter and the February 14 consent order to what the court records quote, and cut the unsourced claim that the Bureau dropped pending enforcement actions.

  687. · Why the CFPB’s dormant authority put fintech partners on the exam calendar

    Removed or reworded as our view unsourced statements about investor trends and what many firms faced (for example, “Venture and growth investors increasingly ask the same questions examiners do”).

  688. · Why the CFPB’s dormant authority put fintech partners on the exam calendar

    Reworded as our view or as a possibility unsourced statements about what fintechs and their partner banks typically or often do (for example, “Customer support usually owns the queue”).

  689. · The CFPB’s data broker proposal exposed a provenance gap that AI programs inherit

    Reworded unsourced statements about what many organizations and firms do (for example, “Many organizations already run data catalogs and lineage tools”) as conditions.

  690. · The CFPB’s data broker proposal exposed a provenance gap that AI programs inherit

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “a question most outbound reviews had never asked”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “attempts at completeness tend to stall”).

  691. · Free, measured and always on: the open banking interface the CFPB proposed and banks could not price

    Reworded as a possibility unsourced statements about what customers and apps typically or often do (for example, “People who link their accounts to apps are often among an institution’s most engaged”).

  692. · The CAT’s retirement freed the framework and orphaned the risk profile

    Removed unsourced statements about what most or many banks did after the Cybersecurity Assessment Tool was retired (including the summary line “Most banks quickly picked a new framework”) and about which frameworks institutions presented to examiners; where the point is our analysis, it now says so.

  693. · The CAT’s retirement freed the framework and orphaned the risk profile

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “the gap only appears later, often in an incident review”).

  694. · Cash-flow underwriting got a blessing and no plumbing

    Added the October 29, 2025 injunction in Forcht Bank, N.A. v. CFPB barring enforcement of the personal financial data rights rule until the CFPB completes its reconsideration, corrected the account of the court’s July 2025 stay and the 90-day deadline extension, and updated the hindsight and a takeaway to match; added that SR 26-2 superseded SR 11-7 on April 17, 2026; replaced “a lender has to test … less discriminatory alternatives” with our view and what the April 2026 Regulation B amendments did to the effects test; attributed “credit unions” to the agencies’ press release, since the statement itself names bank and non-bank firms; reworded as our view or as possibilities unsourced statements about what lenders usually or often do.

  695. · Capital One’s cloud penalty was a verdict on sequencing

    Removed or reworded unsourced statements about what many banks were doing (for example, “By August, many banks were also moving faster than planned”) and an unsourced “widely reported”.

  696. · Capital One’s cloud penalty was a verdict on sequencing

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “Outside reviewers are often engaged to test the work”). Replaced the Cybersecurity Dive and Banking Dive sources with Capital One’s September 2022 Form 10-Q and the Federal Reserve’s July 2023 termination notice, added the Justice Department’s October 2022 sentencing release, and cut the unsourced $190 million settlement figure, “without admitting liability” and the quarterly-reporting detail. On 2026-11-15 an independent review (N-145) cut the statement that the intruder was acquitted of some other charges, which the Justice Department’s sentencing release does not state. On 2026-11-15 (N-146) the description of the cease-and-desist order and the OCC’s findings, which had rested on law firms’ summaries, was reworded to the order itself, which replaces the civil money penalty order as a source (the OCC’s news release covers the penalty, and the cease-and-desist order states the same findings as the penalty order).

  697. · Bybit’s signers approved what their screens showed, which was not what they signed

    Removed unsourced statements about how widely the theft was reported and how widely products are used, and reworded statements about most banks and trends in vendor software (for example, “Bank approval screens are increasingly delivered by vendors through browsers”) as conditions.

  698. · Bybit’s signers approved what their screens showed, which was not what they signed

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “A community bank or credit union usually approves wires inside a portal”). Replaced The Hacker News source with Safe’s own March 6, 2025 investigation update and added Bybit’s February 21 incident notice, its chief executive’s March 4 summary, the FBI’s DMM Bitcoin release and the Federal Reserve’s joint crypto-safekeeping statement; reworded the forensic detail (cloud storage, activation conditions, contract swap, timing), Bybit’s solvency statement and the Mandiant findings to what Safe and Bybit stated; cut the unsourced Radiant Capital, chalk and debug, Fedwire ISO 20022 and EU Instant Payments Regulation details.

  699. · Buildings intact, workforce gone: the scenario continuity plans skipped

    Removed or reworded as our view unsourced statements about what most or many organizations did or found during and after the pandemic, including that scenario-based, people-centric testing is now a more standard part of continuity programs, and that most office-based staff were working from home within three weeks. Sourced the off-channel recordkeeping penalties to the SEC’s September 2022 release (more than $1.1 billion from sixteen firms) in place of an unsourced total “well over a billion dollars” and an unsourced reference to CFTC cases; added sources for the Basel Committee’s operational resilience principles, DORA’s application date and Microsoft’s 8.5 million device estimate, and replaced an unsourced list of affected sectors with Microsoft’s own description. Also reworded as possibilities or our view unsourced statements about how continuity programs usually work (for example, “Continuity tests are usually short and site-based”). Replaced the UPI market report with the Federal Reserve’s February 28, 2020 statement and cut the unsourced market figures (worst week since 2008, the Dow’s points and percentage falls, the S&P 500 fall, the record-low Treasury yield), the details of the Italian, South Korean and Iranian outbreaks, and the unsourced Pence, WHO and Washington State lines, and added the CDC’s February 25 description of community spread abroad. On 2026-11-15 (N-146) the remaining unsourced statements that US stock markets fell sharply that week and that investors were pricing in the risk were cut; the dek and opening now rest on the Federal Reserve chair’s February 28 statement and the CDC’s February 25 briefing.

  700. · BlueLeaks: one small web host, hundreds of agencies’ files

    Dropped unsourced statements about how widely products, catalogs and credentials are used or trusted.

  701. · BlueLeaks: one small web host, hundreds of agencies’ files

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “Records officers often resist this work”). Replaced the KrebsOnSecurity, Associated Press (via Claims Journal) and CyberScoop sources with Distributed Denial of Secrets’ own BlueLeaks page and the Maine State Police statement of June 26, 2020, reworded the archive, Netsential, Twitter and server-seizure details to what those sources state, and cut the National Fusion Center Association’s account of how the intrusion happened and what the files contained.

  702. · Blue Yonder put process-running vendors at the top of the risk register

    Reworded unsourced trend statements and statements about most or many organizations (for example, “Increasingly, gangs also steal copies of data first”) as conditions or our view.

  703. · Blue Yonder put process-running vendors at the top of the risk register

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “Large customers often find they are not first”). Sourced the July 2024 CrowdStrike outage to Microsoft’s estimate of 8.5 million devices, and replaced an unsourced list of what was disrupted (flights, hospitals, banks) with Microsoft’s description of those affected. Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “tend to ask about what is easy to measure”). Replaced the TechCrunch, Cybersecurity Dive, CFO.com, SHRM and ABC News sources with Blue Yonder’s own incident update page and acquisition release, UnitedHealth Group’s 2024 Form 10-K and United Natural Foods’ June 2025 Form 8-K; reworded the Change Healthcare, Collins Aerospace and United Natural Foods passages to what those filings say, and cut the press-reported customer count and names, the Starbucks, Morrisons and Sainsbury’s details, the Termite, 680 gigabyte and Babuk details, the CDK Global examples, the UKG restoration date and Franciscan Health example, the ransom payment, the airport names and the Salesloft Drift example, and reworded the summary line to match. On 2026-11-15 an independent review (N-143) fixed a missing space.

  704. · BlackMatter’s reach was set by the directory, not the malware

    Removed or reworded unsourced statements about what most or many organizations use and do (for example, “Encryption of virtualization hosts became a common feature of major ransomware families”).

  705. · BlackMatter’s reach was set by the directory, not the malware

    Reworded as our view or as a possibility unsourced statements about what attackers, banks and IT teams typically or often do (for example, “Organizations that tried to tier everything at once often stalled”). On 2026-11-15 replaced The Record article with the Justice Department’s December 2023 ALPHV disruption announcement, the AHA reproduction of FBI FLASH CU-000167-MW with the FBI’s own copy, and The Register article with UnitedHealth Group’s written Senate testimony (reworded the Change Healthcare sentence to it), and cut the unsourced Reuters, Emsisoft and BlackMatter shutdown sentences. On 2026-11-15 an independent review (N-145) cut the press-only claim linking BlackMatter to the NEW Cooperative attack and added the advisory’s note that the actors kept access through legitimate remote monitoring and remote desktop software.

  706. · Blackbaud’s breach exposed patient data that fundraising never needed

    Reworded as our view unsourced statements about what is most often missed or offered, and dropped unsourced “widely used” and “increasingly”.

  707. · Blackbaud’s breach exposed patient data that fundraising never needed

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “Training extracts often land in data science environments”). Replaced the Cornell Legal Information Institute copy of 45 CFR 164.514 with the eCFR text and added the January 2013 HIPAA final rule (78 FR 5566) for the earlier fundraising limits and HHS’s explanation of outcome information.

  708. · Bitfinex’s six-year trace ran through records that banks keep

    Removed or reworded as our view unsourced statements about what many or most banks do (for example, “Many banks in early 2022 could not say which customers transacted regularly with crypto platforms”).

  709. · Bitfinex’s six-year trace ran through records that banks keep

    Reworded as our view or as a possibility unsourced statements about what banks and their staff typically or often do (for example, “A credit union or community bank usually has a smaller compliance team”). Replaced the Cornell Legal Information Institute copy of 31 CFR 1010.430 with the eCFR text.

  710. · BetterHelp’s intake form was a privacy promise the ad stack broke

    Removed or reworded unsourced statements about what most or many organizations do with tracking tags (for example, “In most hospitals and health plans, the public website and patient app have several owners at once”).

  711. · BetterHelp’s intake form was a privacy promise the ad stack broke

    Reworded as our view or as a possibility unsourced statements about what hospitals, agencies and vendors typically or often do (for example, “A community hospital often has one web manager”).

  712. · Before the bias audit, the inventory: what New York City’s hiring-tool law asked of employers

    Removed or reworded as our view unsourced statements about how laws and cases were widely described and about what many organizations know or do (for example, “The law was widely described as the first of its kind”). The EU AI Act is now cited from the Official Journal text of Regulation (EU) 2024/1689 instead of a non-official website, and described by its publication date and Annex III rather than an entry-into-force month we had worked out.

  713. · Before the bias audit, the inventory: what New York City’s hiring-tool law asked of employers

    Added that Colorado SB 26-189, signed on May 14, 2026, repealed and reenacted the AI law before its June 30, 2026 date, and that the EU delay shown as a proposal was adopted in Regulation (EU) 2026/1744, in force since July 27, 2026, with Annex III high-risk rules from December 2, 2027.

  714. · Before the bias audit, the inventory: what New York City’s hiring-tool law asked of employers

    Reworded as a possibility unsourced statements about what employers, agencies and practitioners typically or often do (for example, “Small assessment subscriptions are often paid on corporate cards”).

  715. · Before the 36-hour clock: deciding which bank incidents count

    Removed or reworded as our view unsourced statements about how widely or how often organizations did something (for example, “questions that most banks had never answered in writing”).

  716. · Before the 36-hour clock: deciding which bank incidents count

    Reworded as our view or as a possibility unsourced statements about what banks, providers and their teams typically or often do (for example, “Large providers often resist bespoke terms”). Sourced the July 2024 CrowdStrike outage to CISA’s alert and Microsoft’s estimate of 8.5 million devices, and replaced an unsourced statement that it hit financial institutions with Microsoft’s description of those affected. Replaced a law-firm blog (Hunton Andrews Kurth) with CISA’s own CIRCIA page, and replaced the statement that CISA targeted September 2026 for the final rule with what that page said on November 14, 2026: CISA was still working on the final rule after funding lapses affected the rulemaking.

  717. · ChatGPT reached bank desks; recordkeeping set the longer limit

    Reworded unsourced statements about how the restrictions were widely read and what most companies think about.

  718. · ChatGPT reached bank desks; recordkeeping set the longer limit

    Added to the hindsight that SR 11-7 and OCC Bulletin 2011-12 were superseded on April 17, 2026, by SR 26-2 and OCC Bulletin 2026-13, which leave generative and agentic AI models out of scope, and put descriptions of SR 11-7 as current guidance in the past tense.

  719. · ChatGPT reached bank desks; recordkeeping set the longer limit

    Reworded as our view or as a possibility unsourced statements about what community banks and credit unions typically or often do (for example, “A community bank or credit union usually has a much smaller program”).

  720. · Bank cyber gaps now arrive as observations the board never has to see

    An earlier version said the rule “takes effect” on November 2, 2026; that date has passed, and the text now says the rule took effect then and dates the status of the OCC’s separate proposal on violations of law.

  721. · Bank cyber gaps now arrive as observations the board never has to see

    Removed or reworded as our view or a condition unsourced statements about how widely or how often organizations did something (for example, “NIST CSF 2.0 is the widely used cybersecurity framework”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “are rarely about how an examiner labeled a finding”). Replaced the Skadden law firm summary with Vice Chair for Supervision Bowman’s January 7, 2026 speech, and reworded the Federal Reserve’s position to what the rule and that speech show: the rule was issued by the OCC and FDIC only, and the speech calls for supervision focused on core and material financial risks.

  722. · Backups could not answer the D.C. police data leak

    Removed or reworded as our view unsourced statements about how widely or how often organizations did something (for example, “became standard criminal practice” and “Many agencies improved backup and recovery after 2021”).

  723. · Backups could not answer the D.C. police data leak

    Reworded as our view or as a possibility unsourced statements about what agencies, insurers and attackers typically or often do (for example, “Groups typically post a victim’s name with a countdown”). On 2026-11-15 replaced the BleepingComputer article with the Oregon Department of Transportation and Louisiana Office of Motor Vehicles notices (reworded to what they state) and added the Justice Department’s May 2023 Matveev announcement for the charges, sanctions and reward.

  724. · Bigger network, thinner safety net: Ascension’s outage hit every sister hospital at once

    Reworded as our view or as a possibility unsourced statements about what multi-hospital systems and their downtime plans typically or often do (for example, “a large system typically runs one of each, centrally”).

  725. · Ardent took one network offline, and emergency departments in six states had to answer for it

    Reworded unsourced statements about how many hospitals in multi-state systems are joint ventures and about federal agencies “increasingly” expecting notice.

  726. · Ardent took one network offline, and emergency departments in six states had to answer for it

    Reworded as our view or as a possibility unsourced statements about what hospital operators and attackers typically or often do (for example, “A multi-state hospital operator usually runs much of its technology centrally”). Replaced The Record and Healthcare Dive sources with Ardent’s own November 27, 2023 statement and Ascension’s cybersecurity event updates (Internet Archive copies), removed the NBC News source because Ardent’s prospectus states the diversions, and reworded the facility list, the market-by-market recovery and the Ascension outage to what those sources state, cutting the unsourced Ascension diversions.

  727. · Approval is easy, monitoring is hard: the Joint Commission’s AI guidance and the work after go-live

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “That role often goes unfunded”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “By 2025 most large health systems had an AI committee.”).

  728. · Why Apple Card’s lawful credit limits still broke trust

    Quoted the Regulation B official interpretation exactly (“does not provide for the prohibition of practices that are facially neutral as to prohibited bases …”) instead of paraphrasing it as “does not prohibit”; attributed to DFS its findings on couples’ credit profiles and authorized users, and reworded as our view or as possibilities unsourced statements about what usually or often happens.

  729. · Antitrust moves in years; vendor dependency is set at signing

    Removed or reworded as our view unsourced statements about how widely or how often organizations did something (for example, “Many institutions made their most consequential platform choices by default”).

  730. · Antitrust moves in years; vendor dependency is set at signing

    Reworded as our view or as a possibility unsourced statements about what buyers, finance teams and providers typically or often do (for example, “Major technology contracts commonly run for three to five years”). Sourced the July 2024 CrowdStrike outage to Microsoft’s estimate of 8.5 million devices, and replaced unsourced lists of the sectors disrupted with Microsoft’s description of those affected. Replaced an NPR story (via KPBS) on the September 2025 search remedies with the court’s December 5, 2025 memorandum opinion, published by the Justice Department, and reworded the description of the remedies to match it: the court rejected the more severe proposals, such as a divestiture of Chrome. Attributed the hindsight statement about the CrowdStrike outage to Microsoft and cut the unsourced Change Healthcare disruption claim.

  731. · An acquisition announcement is a free option on your exit plan

    Removed or reworded as our view unsourced statements about what many institutions held and about regulatory trends (for example, “Regulators in banking and healthcare increasingly expect organizations to understand their dependence on critical third parties”).

  732. · An acquisition announcement is a free option on your exit plan

    Reworded as our view or as a possibility unsourced statements about what organizations and their suppliers typically or often do (for example, “Enterprise agreements often priced the whole portfolio as one deal”).

  733. · At American Water, containment was the part customers saw

    Reworded unsourced trend statements (for example, “Attackers increasingly also steal data first”) as conditions or our view.

  734. · At American Water, containment was the part customers saw

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “Silence gets filled by others, often inaccurately”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “tend to suggest the worst”).

  735. · Europe’s AI treaty attached its duties to the public function, not the payroll

    Reworded an unsourced statement about what many agencies collect (“Many agencies do not collect race, ethnicity or disability status”) as a condition.

  736. · Europe’s AI treaty attached its duties to the public function, not the payroll

    Added that the delay to the AI Act’s high-risk obligations, described as a proposal, was adopted in Regulation (EU) 2026/1744, in force since July 27, 2026, with Annex III high-risk obligations from December 2, 2027.

  737. · Europe’s AI treaty attached its duties to the public function, not the payroll

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “Ownership is where in-house programs often stall”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “The output rarely arrives labeled as”). Replaced the Center for AI and Digital Policy tracker with the Council of Europe treaty office’s chart of signatures and ratifications and added the Council of Europe’s page on the convention (Internet Archive copies); corrected the signatory count from 47, with EU member states among them, to the 21 the treaty office listed on November 7, 2026, added the European Union’s May 2026 and Bosnia and Herzegovina’s October 2026 ratifications, and cut the unsourced May 17, 2024 adoption date, the description of the private-sector clause as the hardest compromise, Norway’s signing statement, the requirement for independent oversight mechanisms and the paragraph on Texas’s AI law. On 2026-11-15 an independent review (N-145) fixed a missing word in the description of the Council of Europe (“and is best known for”).

  738. · Article 50 kept its date, and it lands on the chat window

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “Many digital teams have done exactly that, often quickly and with enthusiasm”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “Voice is where gaps tend to hide.”).

  739. · Agency certificates now expire faster than agency budgets turn over

    Removed a date we had worked out ourselves (that a certificate issued on March 15, 2026 for the full 200 days expires on October 1, 2026) and the statements built on it, including a second worked-out date in the hindsight; the cap is now stated as CA/Browser Forum ballot SC-081 states it, a maximum validity period of 200 days for certificates issued on or after March 15, 2026 and before March 15, 2027. Also reworded unsourced statements about how many agencies and certificate authorities work a certain way as our view or as conditions.

  740. · Agency certificates now expire faster than agency budgets turn over

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “the old arrangements stop working, usually before anyone has noticed”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “Annual renewals tended to cluster in predictable months”). Replaced the AAMC summary with Public Law 119-103 (signed September 2, 2026, funding through December 11) and the BleepingComputer report with an Internet Archive copy of Netcraft’s own January 2019 article, and dated the stopgap law to September 2.

  741. · Agencies buy a cloud provider’s security culture whether or not the contract mentions it

    Reworded unsourced statements about how many agencies, banks and hospitals share providers and what outside parties and insurers routinely ask (for example, “Outside parties increasingly ask the same things”).

  742. · Agencies buy a cloud provider’s security culture whether or not the contract mentions it

    Reworded as our view or as a possibility unsourced statements about what agencies, credit unions and procurement teams typically or often do (for example, “Smaller organizations often buy through someone else’s contract”). Replaced the TechCrunch source with the senators’ May 2025 press release and letter on the Cyber Safety Review Board, and reworded the January 2025 dismissal to what that release states, cutting the unsourced statement that all DHS advisory committee memberships were terminated.

  743. · After Van Buren, insider snooping is an access design problem

    Reworded an unsourced statement about many agencies (“Many agencies do not control the design of the systems their staff use”) as a condition.

  744. · After Van Buren, insider snooping is an access design problem

    Reworded as our view or as a possibility unsourced statements about what agencies, employees and insiders typically or often do (for example, “Employees who move between units often keep their old permissions”). On 2026-11-15 replaced the two Cornell Legal Information Institute copies of 26 U.S.C. § 7213A and 18 U.S.C. § 2724 with the official United States Code on govinfo.gov.

  745. · After the 2024 election, a rule’s legal form predicted its survival better than its topic

    Marked a statement about what would have been enough for most organizations as our view.

  746. · After the 2024 election, a rule’s legal form predicted its survival better than its topic

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “state regulators and attorneys general often step forward”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “tend to lose momentum on everything”).

  747. · After Moody’s downgrades, regional bank technology had to argue in unit costs

    Reworded as conditions or our view unsourced statements about what many banks did or budgeted for (for example, “Many banks keep contracts in procurement folders”).

  748. · After Moody’s downgrades, regional bank technology had to argue in unit costs

    Reworded as a possibility unsourced statements about what banks and their core processors typically or often do (for example, “Banks often signed them in a different rate environment”). Replaced the Reuters (via Investing.com) source with Moody’s own Q2 2023 US banks update, which lists the August 7 rating actions; reworded Moody’s reasons to what that document states, corrected “Prosperity Bank” to Prosperity Bancshares, and cut the unsourced recession forecast, loss-of-confidence warning, office detail and S&P downgrades, together with the hindsight line about that recession forecast.

  749. · Accellion and the file transfer server nobody owned

    Updated the text to say that CISA revoked BOD 22-01 on June 10, 2026 and replaced it with BOD 26-04.

  750. · Accellion and the file transfer server nobody owned

    Removed an unsourced claim that many security teams use the Known Exploited Vulnerabilities catalog as their priority list.

  751. · Accellion and the file transfer server nobody owned

    Removed or reworded as our view unsourced statements about how widely or how often organizations did something (for example, “became common” and “widely recognized as high-value infrastructure”).

  752. · Accellion and the file transfer server nobody owned

    Reworded as our view or as a possibility unsourced statements about what organizations, agencies and attackers typically or often do (for example, “File transfer tools are usually bought to solve one exchange”). On 2026-11-15 attributed the Clop leak-site detail to Mandiant, cut the unsourced list of victim types and the “thousands of organizations” count, and sourced the Oregon and Louisiana MOVEit disclosures to the Oregon Department of Transportation and Louisiana Office of Motor Vehicles notices, reworded to what they state. On 2026-11-15 an independent review (N-145) cut the remaining unsourced list of MOVEit victim types (federal agencies, universities, health systems, banks and service providers), keeping the state agencies the Oregon and Louisiana notices show.

  753. · A rule’s survival odds belong in the compliance plan

    Reworded unsourced statements about what many agencies do and what has proved durable (for example, “Conditions of participation in Medicare and Medicaid have proved relatively durable”).

  754. · A rule’s survival odds belong in the compliance plan

    Reworded as our view or as a possibility unsourced statements about what agencies and regulated institutions typically or often do (for example, “Agencies often stretch those older words to cover new situations”).

  755. · A permanent telehealth benefit with an in-person clock attached

    Reworded as our view or as a possibility unsourced statements about what practices and their staff typically or often do (for example, “Credentialing teams often hold that list in a spreadsheet”). On 2026-11-15 replaced the K&L Gates client alert with the enrolled text of H.R. 5371, which moved the telehealth and in-person dates from September 30, 2025 to January 30, 2026, and reworded the lapse sentence to what the two laws show.

  756. · A hallucination rate is a sales claim, and Texas enforced it like one

    Reworded an unsourced trend statement (“the practical rulebook for AI is increasingly a patchwork”) as our view.

  757. · A hallucination rate is a sales claim, and Texas enforced it like one

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “the pitch often came with a reassuring number”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “the less closely its drafts tend to be reviewed”).

  758. · A few hours without Fedwire, and the bank promises with no fallback

    Removed or reworded as our view unsourced statements about how widely or how often organizations did something (for example, “Many banks still found, during those hours, that they could not quickly say which customer commitments were now at risk”).

  759. · A few hours without Fedwire, and the bank promises with no fallback

    Reworded as our view or as a possibility unsourced statements about what banks, credit unions, agencies and their teams typically or often do (for example, “Payment rails run by a central bank are usually treated as a utility”). Sourced the July 2024 CrowdStrike outage to Microsoft’s estimate of 8.5 million devices and replaced an unsourced statement that it hit banks with Microsoft’s description of those affected. Replaced a Reuters story (via Al Jazeera) with the Federal Reserve Banks’ own service status alert for February 24, 2021 (an Internet Archive copy captured February 25, 2021) and the Fedwire Funds Service monthly statistics. Rewrote the timeline to match the alert: staff became aware of a disruption to all services around 11:15 a.m., not in the early afternoon, and the status page dates when each service resumed. Removed the statement that the Fed ruled out a cyberattack, which the alert does not say. On 2026-11-15 added Nacha’s Same Day ACH page and reworded the Same Day ACH sentence to what it states (two more hours in 2021; limit raised from $100,000 to $1 million in 2022), and cut the unsourced Synapse and 2023 third-party guidance sentences.

  760. · A breach with no attacker: the FTC’s warning to health apps

    Reworded unsourced statements about what most or many organizations think and do (for example, “Many organizations concluded … that the answer for health screens was no”) as general points.

  761. · A breach with no attacker: the FTC’s warning to health apps

    Reworded as our view or as a possibility unsourced statements about what health apps and the organizations behind them typically or often do (for example, “Consent is often designed as a screen and stored nowhere”).

  762. · A 90-day declaration that ran for three years

    Reworded as our view two unsourced statements (“widely read as a precaution”, “the one most often skimped”).

  763. · A 90-day declaration that ran for three years

    Reworded as a possibility unsourced statements about how state agencies and their vendors typically or often work (for example, “Changes to these systems are usually made by an outside vendor”).

  764. · 988 launched without 911’s plumbing: location, dispatch and a fee

    Removed or reworded as our view unsourced statements about trends and awareness (for example, “By 2026 the number is widely known”).

  765. · 988 launched without 911’s plumbing: location, dispatch and a fee

    Reworded as a possibility unsourced statements about what crisis providers and responders often do or lack (for example, “Small community providers often lack those systems”).

  766. · Fourteen thousand accounts, 6.9 million people: the 23andMe ratio every health data platform should measure

    Removed or reworded unsourced statements about what most or many organizations and boards do (for example, “Most organizations already treat their employees’ access this way”).

  767. · Fourteen thousand accounts, 6.9 million people: the 23andMe ratio every health data platform should measure

    Reworded as our view or as a possibility unsourced statements about what health systems, payers and patients typically or often do (for example, “An adult child granted access during a parent’s illness often keeps it”).

  768. · 23andMe’s bankruptcy turned a privacy policy into a term of sale

    Reworded unsourced statements about what most or many organizations do (for example, “Many organizations store consent as a scanned form”) as conditions.

  769. · 23andMe’s bankruptcy turned a privacy policy into a term of sale

    Reworded as our view or as a possibility unsourced statements about what organizations typically or often do (for example, “analysts often download extracts for convenience”). Also reworded as our view or a possibility further unsourced claims about how organizations or people behave (for example, “They rarely read the privacy policy, but they assume”).

  770. · Two privacy laws on, one rulebook paused: compliance by capability map

    We corrected a statement that state privacy exemptions mostly attach to data rather than institutions: Connecticut, like Virginia, exempts GLBA financial institutions and HIPAA covered entities outright, while California exempts only the data. The worked request example now uses a California customer accordingly.

  771. · TransUnion won Ramirez, and name-only matching still lost

    We corrected a statement that TransUnion flagged consumers whose names resembled a listed name; according to the Court’s opinions, it compared first and last names only, and the dissent said it required those names to match exactly.

  772. · Why a stolen DMV file weakened identity checks at agencies that were never breached

    We added that Louisiana's advice to residents covered IRS Identity Protection PINs and my Social Security accounts as well as credit monitoring and freezes, and that the exposed Louisiana records included Social Security numbers.

  773. · M-22-09 made the login phishing-proof and moved the weak point to enrollment and recovery

    Clarified that M-22-09 did address account recovery, in one paragraph calling it a potential bypass and asking for high-friction methods such as in-person or live video checks, though without a deadline or measure. Earlier text said the memo left recovery largely unaddressed.

  774. · Your carrier’s routers belong in your threat model

    Corrected the description of the 2024 telecommunications intrusions to match the FBI and CISA statement, which described copying of information subject to court-ordered law enforcement requests, and clarified what CISA's December 2024 guidance covered.

  775. · Why valid when made left bank-fintech lenders two open questions

    Corrected the description of the 2022 Blue Ridge Bank action, which was an OCC formal agreement rather than a consent order, and named the agency behind each enforcement action.

  776. · Why the Signal group chat was a channel design failure before it was a leak

    The hindsight section said the inspector general found the messages were not retained as records law requires; reporting on the report says it noted that unapproved apps make records retention harder, and we removed an unconfirmed claim about a June 2025 ruling in the records case.

  777. · Why the IRS’s ten-year budget needed a one-year payoff

    Softened hindsight claims about the 2023 phone service figures, the 2025 IRS workforce reduction and the end of Direct File, which could not be confirmed against primary sources.

  778. · Why the CMS patient app pledge depends on the registration desk

    Removed an unverified statement that several companies announced they had reached production as CMS Aligned Networks during 2026.

  779. · Why the air traffic control rebuild started with the wires

    The estimate that about $20 billion more would be needed came from Transportation Secretary Sean Duffy, not the FAA administrator, and we removed an unconfirmed date for the FAA’s integrator solicitation.

  780. · Why the AI Act’s obligations follow your role, not your sector

    Replaced an unverified May 2026 provisional agreement with the AI Omnibus's entry into force on July 27, 2026, which set the new high-risk dates of December 2, 2027, and August 2, 2028.

  781. · Why the SEC’s hijacked account was most valuable the day before a decision

    Removed an unverified statement that members of Congress pressed the SEC over the multi-factor authentication lapse.

  782. · Why Scattered Spider’s turn to insurers should have set a deadline for the rest of finance

    Removed details we could not confirm from primary sources (a June 9 disconnection at Philadelphia Insurance Companies, an outage reported in Erie’s filing, and an FBI warning about airlines), and corrected the source of Aflac’s 22.65 million figure to its annual report, which does not attribute the attack.

  783. · Why one phone call beat Twitter’s login controls

    Corrected the description of the attack: per the DFS report, the attackers replayed captured credentials and some employees approved the resulting multifactor prompt, rather than the attackers capturing one-time codes; also stated that Twitter had lacked a CISO since December 2019.

  784. · Why o1’s reasoning summaries added work for clinical AI committees

    Removed an unverified statement that the HTI-5 proposed rule had not been finalized as of this writing.

  785. · Why hospitals could prepare for CIRCIA before CISA wrote its rule

    Stated the proposed rule’s hospital criteria precisely (100 or more beds, or critical access hospitals) and removed an unsourced reference to missed internal targets for the final rule.

  786. · Why good-faith estimates weighed most on the therapist’s office

    Removed unverified claims that the patient dispute process was little used and that deferred provisions remained unfinished, replaced a claim of heavy litigation with CMS dispute volume data, and restated the six-year record rule as the regulation words it.

  787. · Why CISA’s Ivanti disconnect order was decided by people, before it was issued

    We removed a statement that CISA urged state and local governments to take the same steps, because CISA’s directive and supplemental direction were addressed only to federal agencies and we could not confirm such a recommendation.

  788. · Why buying the same software as your neighbors removes your fallback

    Removed an unverified statement that Advanced confirmed LockBit involvement, corrected the description of who the UK regulator fined, and removed an unsupported claim that it was the first such fine against a data processor.

  789. · Why business email compromise belongs to the payments team

    Clarified the description of UCC Article 4A: an order the customer authorized is binding on the customer regardless of security procedures, while the agreed security procedure matters for orders the customer disputes.

  790. · Why bank change control never saw the npm hijack

    Removed an unverified start date and victim description for the Shai-Hulud 2.0 wave, clarified that GitHub's September 2025 npm changes were announced plans, and replaced a general claim about release-age delays with GitHub's July 2026 Dependabot default.

  791. · Why banking-as-a-service margins never covered the cost of knowing whose money it was

    We now cite the CFPB’s own records for the Synapse shortfall ($60 million to $90 million) and its Civil Penalty Fund allocations, and removed an aside about an Evolve data breach that we could not confirm from a primary source.

  792. · Why the AI preemption order barely reached health care’s own AI rules

    Removed unverified statements that Colorado repealed and replaced its AI Act in May 2026 and that enforcement was paused, and dated the Justice Department task force to the Attorney General’s January 9, 2026 memorandum.

  793. · No key to buy: WhisperGate and the agency recovery plan

    Removed unsupported claims that cyber insurers and state oversight bodies made backup testing a standard question and that shared programs extended forensic support, and softened an unverified date and count for the Ukrainian website defacements.

  794. · When the FBI offers a decryptor: what ALPHV’s takedown asked of public agencies

    Removed a statement about State Department rewards for information on ALPHV’s leaders, which we could not confirm from a primary source at the time of review.

  795. · When AI made flaws cheap to find, banks’ patch queues set the pace

    An earlier version stated that euro-area banks had no access to the model; we could not verify that and have removed it.

  796. · When a hospital diverts, the whole region absorbs the attack

    An earlier version said Germany’s federal cybersecurity agency confirmed the attack exploited a Citrix vulnerability; the agency warned about that vulnerability in connection with the attack but did not confirm it as the entry point, and the text now says so.

  797. · What a stolen license number proves, and what banks treated it as proving

    The number of people affected by the Optus breach now cites the Australian Information Commissioner’s figure of about 9.5 million, replacing the earlier 9.8 million estimate.

  798. · Vendors repriced in a day, contracts run for years: the buyer’s side of the software selloff

    An earlier version said July market commentary described software stocks as well below their January level while infrastructure names recovered faster; we could not verify that, and the passage now cites end-of-March commentary instead.

  799. · In the Treasury payment access dispute, “read-only” was a claim until the records proved it

    Replaced an unverified reference to inspectors general opening reviews with the verified June 2025 Supreme Court stay in the Social Security records case, and aligned the description of Treasury’s log review with the sworn declaration.

  800. · TraderTraitor aimed fake job offers at the engineers who hold the keys

    Reworded the description of action against North Korean remote IT worker schemes to match what the FBI’s published warnings confirm.

  801. · ToolShell made patching the easy part of a SharePoint emergency

    Corrected the account of the vulnerability: later analysis by Eye Security and CISA found the exploitation wave used the flaws patched on July 8, with CVE-2025-53770 and CVE-2025-53771 covering patch bypasses not known to be exploited, so the article no longer says July 8-patched servers were exposed.

  802. · Three things a delayed federal transition moved at once

    Corrected the description of who criticized the delayed ascertainment and why: critics cited the pandemic response, and the claim that they cited vaccine distribution was not supported.

  803. · The tool that checked for supply-chain risk was the supply-chain risk

    An earlier version said the KICS action was poisoned with tokens from compromised pipelines and that LiteLLM’s releases were published with credentials stolen from such a pipeline; the article now attributes KICS to a compromised publishing account and reports LiteLLM’s own finding that its incident was likely linked to the scanner in its pipeline.

  804. · The scammers’ window: patient communication when a hospital goes dark

    The hindsight section said the July 2025 joint advisory on Interlock described its targeting of healthcare; the advisory describes victims across business and critical infrastructure and includes guidance for healthcare organizations, and the text now says so.

  805. · The control system map most operators did not have

    Corrected the description of the FBI's position on the 2021 Oldsmar incident: the FBI said it could not confirm the incident was initiated by a cyber intrusion, not that it found no evidence of a cyberattack.

  806. · Systems contained, data exposed: why Columbus’s reassurance outran its evidence

    We removed an unconfirmed statement that the city never received a ransom demand and no longer give a specific date for the mayor’s statement that the leaked data was encrypted or corrupted, since contemporary reports differ.

  807. · Synnovis put a price on pathology consolidation that no contract carried

    We corrected the source and date of the attack’s cost estimate (£32.7 million, cited by the UK government in April 2025, not a January 2025 Synnovis statement) and removed a claim about the contract’s length that we could not confirm.

  808. · What a supply chain label on a U.S. AI vendor asked of agencies and contractors

    An earlier version said the D.C. Circuit briefly stayed its September 25 judgment for a rehearing petition and that Defense officials publicly disputed the August 27 ruling; we could not verify either and have removed them, and the description of the August 27 relief now follows the court’s order.

  809. · Supervisory correspondence: a bank’s most candid file, held in a system it cannot assess

    The OCC did not itself give a count of compromised accounts; the figure of about 100 is now attributed to press reports, and we removed unconfirmed hindsight claims about congressional follow-up, examiner access and agency compromises in the July 2025 SharePoint campaign.

  810. · Storm-0558’s post-mortem described three key failures every agency development team can repeat

    We changed the title and qualified the body, which presented the crash dump as the established path for the key; Microsoft said in March 2024 that it had not found a crash dump containing the key.

  811. · Why a stolen DMV file weakened identity checks at agencies that were never breached

    We replaced an unsourced statement that CISA had confirmed federal agencies were affected with a reference to the June 7 CISA and FBI advisory, and removed an unverified date and assurance-level detail about Login.gov's selfie check.

  812. · States could build Medicaid work requirements from the statute before the rule arrived

    An earlier version said the interim final rule left states to define medically frail conditions themselves; the rule sets a federal definition based on the five statutory categories and does not let states add to it.

  813. · States could build Medicaid work requirements from the statute before the rule arrived

    An earlier version said members could attest to an exemption for 2027 with documentation required from 2028; the rule lets states accept other information before January 1, 2028 and requires documentation, where reasonably available, from that date.

  814. · State AI law after the 99-to-1 vote: build for notice, explanation and human review

    Removed hindsight statements we could not verify about a May 2026 Colorado law repealing and replacing the AI Act; the verified August 2025 delay to June 30, 2026 remains.

  815. · Stablecoin rules late, statutory clock on time: the GENIUS Act’s awkward first year

    An earlier version said the OCC planned to finalize its rule after revising the proposal in light of comments and aimed to take issuer applications in early 2027; the OCC’s August 19 release supports only the November target, so the other details were removed.

  816. · Stable is a claim: what TerraUSD asked of bank front lines

    Restated Secretary Yellen’s May 10, 2022 testimony to match the published record, removed an unverified claim about another stablecoin’s price on May 12, and removed details of the Terraform founder’s plea and sentence that we could not confirm against a primary source.

  817. · Someone else’s lawsuit, your contracts: how the Times case reached regulated AI buyers

    Removed two statements we could not verify from available sources: that the judge allowed the Times’s core claims to proceed in April 2025, and that the May 2025 preservation order was later narrowed; clarified that the Anthropic settlement was agreed and preliminarily approved in 2025.

  818. · Snowflake’s stolen logins put the contractor’s laptop inside the bank’s perimeter

    Corrected the account of Snowflake’s MFA changes: removed unverified claims that MFA became the default for new accounts in October 2024 and that the schedule was revised in October 2025, and stated the published final-phase timeline; also clarified that AT&T’s filing described a third-party cloud platform without naming Snowflake.

  819. · Small-dollar loans, alternative data and the governance attached

    Added that the CFPB withdrew its 2022 circular on adverse action reasons for complex credit models in May 2025.

  820. · Section 524B gave hospitals a baseline to buy against

    The hindsight section now describes FDA’s October 1, 2023 milestone as the expiry of its transitional refuse-to-accept policy, adds the June 2025 guidance update, and drops unverified claims that manufacturers commonly shared SBOMs with customers and that legacy devices remain a common assessment finding in 2026.

  821. · Secrets in a public docket: the court filing breach and where the sensitive tier ends

    Replaced an unverified statement about the content of the judiciary's June 2025 congressional testimony with what the judiciary's August 2025 notice itself said about legacy systems.

  822. · What a second CISA lapse in five months asked state and local security teams to own

    An earlier version implied CISA’s proactive support stayed reduced for the whole lapse and cited unspecified reporting of a slow recovery; it now notes that DHS recalled furloughed staff in mid-April and that CISA reported losing more than 1,000 employees during the shutdown.

  823. · Describe your board’s cyber oversight in a filing, and you have made a promise

    Removed specific statements about how the SEC’s case against SolarWinds was later resolved, which we could not confirm against a primary source.

  824. · Sea-Tac’s handwritten signs were a staffing plan in disguise

    Changed “handwritten bag tags” to handwritten boarding passes and manual bag sorting, which is what contemporaneous reporting documents; the title was updated to match.

  825. · Sea-Tac’s handwritten signs were a staffing plan in disguise

    Corrected the restoration timeline: flight information displays returned only in mid-September and the airport website and app were still down three weeks after the attack.

  826. · Sea-Tac’s handwritten signs were a staffing plan in disguise

    Removed an unverified count of about 90,000 people notified and an unverified description of the systems involved; the Port’s April 3, 2025 notice says the data mostly concerned current and former Port and airport employees and contractors.

  827. · Sea-Tac’s handwritten signs were a staffing plan in disguise

    Replaced an unverified statement that Rhysida listed the Port and offered its data for sale with the Port’s own September 2024 warning that the group might publish stolen data.

  828. · Saline exposed the risk that hides in a hospital’s cheapest line items

    Attributed the 60 percent figure to the American Hospital Association only, and replaced a vague allocation description with Baxter’s published October 2024 allocation levels.

  829. · Saline exposed the risk that hides in a hospital’s cheapest line items

    Removed unverified statements that some hospitals postponed elective procedures and that HHS arranged expanded output from other suppliers.

  830. · Saline exposed the risk that hides in a hospital’s cheapest line items

    Corrected the hindsight timeline: Baxter’s stated goal was 100 percent allocation for most critical IV product groups by the end of 2024, not a January 2025 milestone for sodium chloride, and removed an unverified statement that the FDA declared the saline shortage over in August 2025.

  831. · Russia’s sanctions tested banks’ ownership data more than their name lists

    Removed an unsourced statement that later enforcement actions often cited failures to identify ownership and control or to detect evasion.

  832. · Rural health transformation money runs on three clocks, and only two of them come with funding

    An earlier version said states had already reached or met the October 30 obligation deadline; that deadline falls after publication, and the text now describes how states were approaching it.

  833. · Robinhood’s phone-call breach argues for support access sized to one customer

    Removed an unsourced reference to 2025 attacks on UK retailers and an unsupported claim about routine regulator questioning, and restated the 2023 casino and 2025 cryptocurrency exchange incidents to match the companies’ SEC filings.

  834. · In the RIBridges breach, Rhode Island owned the outage and its vendor owned the evidence

    Removed an unverified statement that the state never published a full accounting of its response costs; the article now says only that no breakdown was given when the $5 million payment was announced.

  835. · Revoking the AI executive order could not revoke the AI inventory, because Congress had written it

    Corrected the description of the Advancing American AI Act’s inventory exclusions: the statute exempts the Department of Defense and the intelligence community, not research uses or national security systems generally.

  836. · Revoking the AI executive order could not revoke the AI inventory, because Congress had written it

    Replaced an unverified claim about OMB’s 2025 inventory reporting guidance with what OMB Memorandum M-25-21 itself says about the Act and inventories.

  837. · Recordkeeping fails where the approved channel is slower than a text

    Unverified statements that SEC commissioners criticized the penalties and that new off-channel cases slowed in 2025 were removed, and SEC settlement figures from 2024 were added.

  838. · Rapid Reset sorted agency websites into three groups, and one of them had no owner

    We removed an unsupported statement that the attack sizes Rapid Reset produced were soon overtaken; later records were for volumetric attacks, not the request rates Rapid Reset set.

  839. · Rackspace kept running old Exchange for clients, and kept its old risks

    The account of the root cause now reflects what Rackspace said (a zero-day exploit tied to CVE-2022-41080, with OWASSRF being CrowdStrike’s name for the technique), and an unverified reference to customer lawsuits was removed.

  840. · The quantum law asked for a price tag agencies could only get from their vendors

    The article previously said the law added funding estimates that M-23-02 had not required; the memo had already required agency funding assessments, and the law added a statutory report to Congress. The description of the July 2024 OMB cost estimate and of the law’s progress-report timing was also made precise.

  841. · A weekend of public red-teaming showed agencies that AI testing never finishes

    We removed an unsourced statement about 2025 cuts to federal technology teams, including 18F, and replaced an unverified description of White House support for the DEF CON exercise with the White House's May 2023 announcement.

  842. · The cyberattack on Prospect Medical ended up on the table in a hospital sale

    We corrected the account of the Yale New Haven Health deal: the $80 million figure was Yale's estimate of cyber repair costs, not a documented request for state funding; Connecticut agreed approval terms in October 2023 rather than March 2024; and Yale sued to exit in May 2024, citing the attack as evidence of inadequate cybersecurity.

  843. · Triage for a rule that might not survive: the SEC’s private fund adviser package

    We removed unverified details about the timing and contents of ILPA's 2025 templates and an unsourced statement about SEC examination themes.

  844. · Post-quantum priority starts in the records retention schedule

    Corrected the description of NIST’s draft transition plan (IR 8547): it proposed disallowing quantum-vulnerable public-key algorithms after 2035 and deprecating only their weaker 112-bit versions after 2030, not deprecating all of them after 2030.

  845. · Persistence below the patch: what ED 25-03 asked agencies to prove about their firewalls

    Removed an unverified statement that CISA was tracking exploitation of mislabeled devices in federal agencies, and replaced a general claim about 2026 targeting with CISA's April 2026 update to the directive.

  846. · Paycheck Protection: capital was easy, intake was hard

    Revised the description of E-Tran problems in the program’s first weeks to say lenders reported intermittent access problems while SBA denied there was an outage.

  847. · Patient access is won or lost at the records counter

    Replaced an unsupported statement that the patient access deadline would be handled in a separate rulemaking with the verified status of the proposal: a January 2026 tribal consultation and an August 2026 target date in OCR’s regulatory agenda.

  848. · Patch what attackers use: BOD 22-01 and the agency work queue

    Updated the hindsight to note that CISA revoked BOD 22-01 on June 10, 2026 and replaced it with BOD 26-04, and removed unsupported claims about insurer, auditor and state adoption of the catalog.

  849. · Part 2’s single consent freed the recipients and bound the source

    We replaced an unconfirmed statement that HHS’s Office for Civil Rights began accepting Part 2 complaints and breach reports on February 16, 2026 with a description of what the rule itself made enforceable from that date.

  850. · Why Part 2’s compliance date reached hospitals that never ran a treatment program

    An earlier version attributed the requirement to update notices of privacy practices to the 2024 Part 2 rule; that requirement came from a separate 2024 HIPAA rule whose Part 2 notice provisions survived a 2025 court decision.

  851. · Cl0p’s Oracle campaign: an attack on the systems security teams did not run

    We removed an unsourced statement that universities, companies and media organizations confirmed they were affected and that breach notifications continued into 2026, and gave the exact dates Oracle and CISA acted on the second flaw.

  852. · Oracle bought Cerner, and Cerner customers inherited a cloud strategy

    Removed unverified hindsight statements about a 2024 Oracle platform announcement, inspector general findings and health systems leaving Cerner, and restated the VA deployment history to match the VA's own announcements.

  853. · One region failed, many financial apps stalled: concentration risk sat in the dependencies

    We removed unsourced claims about specific U.S. apps and UK banks affected, corrected our description of the 2023 U.S. interagency third-party guidance, named the cloud providers on the EU critical-provider list, and softened unverified statements about how institutions responded.

  854. · One door is not a service: the IRS selfie reversal

    Dated the IRS's non-biometric option to its February 21, 2022 statement, attributed selfie deletion to the IRS rather than the provider, and removed an unverified description of a 2023 inspector general finding on Login.gov.

  855. · One alert, three threats: how local agencies should have read the June 2025 Iran warning

    Removed an unverified statement about U.S. and Israeli strikes on Iran in February 2026 from the hindsight section.

  856. · Omicron’s scarcest resource was staff, and few hospitals could count them in real time

    Softened unsupported hindsight claims that contract labor spending was among the leading causes of hospital financial strain and that staffing effects lasted specifically into 2023.

  857. · A support engineer two contracts away: Okta, Lapsus$ and the hospital front door

    Added Okta’s statement at the time that customers of its HIPAA and FedRAMP offerings were not affected, and removed an unsourced claim about prosecutions of Lapsus$ members.

  858. · OAuth integrations make their vendors custodians of your credentials

    Removed unverified details about an extortion leak site, a Salesforce refusal to pay and an attribution of the Gainsight activity, and restated the hindsight using Salesloft's, Salesforce's and Gainsight's own statements.

  859. · NYDFS’s final Part 500 deadline put the asset inventory underneath every other control

    We removed an unverified statement that DFS published MFA FAQs in December 2025 and revised them in early 2026, replaced it with DFS guidance we could confirm, and noted the small-company exemption from universal MFA.

  860. · NYDFS wrote no AI rule, and made AI risk part of what the CEO certifies

    Restated the January 2025 PayPal action as DFS described it: a $2 million settlement after criminals used compromised credentials to reach unredacted tax forms, including a finding that PayPal had not required multi-factor authentication.

  861. · Ninety days at a time: telehealth’s stack of temporary permissions

    Removed unconfirmed details about the sequence of short Medicare telehealth extensions in late 2025 and early 2026; the article now states only the October 2025 lapse, its retroactive cure and the current December 31, 2027 end date, as published by CMS.

  862. · Necessary and proportionate: the ADPPA test that outlived the bill

    Softened the count of state comprehensive privacy laws and removed an unverified claim that several states narrowed financial-institution exemptions.

  863. · National Public Data turned the Social Security number into a lookup key

    Corrected the bankruptcy filer: Jerico Pictures, Inc. was the company doing business as National Public Data, not its parent.

  864. · National Public Data turned the Social Security number into a lookup key

    Removed an unverified figure for the number of people listed in the company’s notice to the Maine attorney general.

  865. · National Public Data turned the Social Security number into a lookup key

    Replaced an unverified statement that the bankruptcy filing listed attorneys general from nearly every state as creditors with what the company’s own bankruptcy filing states.

  866. · Many MOVEit victims never ran MOVEit

    Replaced a November 2023 victim count that could not be verified with Emsisoft's published mid-2024 tally, softened 'most' victims exposed through service providers to 'many', and clarified that Regulation S-P requires covered firms to ensure service providers notify them within 72 hours.

  867. · Microsoft and Nuance: the recording is the asset to govern

    Softened unverified hindsight claims about how fast ambient documentation was adopted and how standard its governance practices became, and named Epic's 2026 AI charting launch specifically.

  868. · Medusa showed that a clinic’s remote-support software is its ransomware attack surface

    The evasion section attributed two techniques, disabling Defender through local Group Policy and hiding tools in antivirus-excluded folders, to the March 2025 advisory; they were added in CISA’s August 2026 update, and the text now says so.

  869. · Medicare’s negotiated prices would reach hospital pharmacies as refunds, and refunds have float

    We corrected the account of the 340B rebate pilot: the court vacated it in February 2026 at the parties’ joint request rather than HHS withdrawing it, and HRSA has since published a revised pilot set to start in January 2027.

  870. · Medicaid’s frailty test asks for a code and proof of impairment, and clinicians hold both

    An earlier version said CMS projected 2.3 million coverage losses in 2027 and that Congressional Budget Office estimates were higher; the CMS figure applies to fiscal 2027, and the unverified CBO comparison has been removed.

  871. · Easy to grant, hard to defend: M-24-10 put every federal AI exception on the record

    Removed an unsupported statement that the plans behind the late-2024 extensions carried over into the April 2025 OMB memos.

  872. · M-22-09 made the login phishing-proof and moved the weak point to enrollment and recovery

    Removed unsupported statements about agency progress against the 2024 deadline and about what regulators and insurers ask, and tied the help desk attack claims to Caesars Entertainment's SEC filing and CISA's Scattered Spider advisory.

  873. · Lower quantum estimates moved signatures up the post-quantum queue

    An earlier version dated Google’s elliptic-curve resource estimate to March 30, 2026; Google published it on March 31.

  874. · Lighter rules, heavier contracts: OMB’s April 2025 AI memos handed governance to the buyer

    We removed hindsight claims about a March 2026 GSA standard AI clause and an April 2026 GAO report that we could not confirm in primary sources, and corrected the M-25-22 applicability date to the end of September 2025.

  875. · Legal to fly, hard to replace: the FCC drone listing and public-safety fleets

    Removed unverified statements about a DJI reconsideration petition, a Ninth Circuit challenge and FCC revocation of DJI and Autel authorizations, and restated the January 2026 exemptions, the equipment waivers and the FCC’s July 2026 proposal to match FCC documents.

  876. · LastPass and the first-draft problem in vendor breach notices

    Corrected the timing and method of the second LastPass intrusion to match the company's own disclosures and removed an unverified claim about a December 2025 UK regulatory fine.

  877. · Kronos went down; the duty to pay public workers on time stayed up

    Replaced statements that lawsuits followed the outage with the contemporaneous warnings of wage claims, removed an unsupported claim that many affected public employers revised their continuity plans, and dropped an unsourced reference to the CDK Global attack.

  878. · Juneteenth tested how many calendars a bank really runs

    We removed a statement that the Federal Reserve announced in June 2021 that it would begin observing Juneteenth in 2022; it said only that it would decide later how to adjust its schedule, and it first observed the holiday in 2022.

  879. · Juneteenth tested how many calendars a bank really runs

    We corrected a statement that Regulation CC defines business days by reference to Federal Reserve holidays; it uses its own list of holidays, which as codified in 2024 did not include June 19.

  880. · ION’s outage exposed a vendor no board had on its critical list

    Corrected the CFTC timeline: staff announced the Commitments of Traders delay on February 2, 2023, and publication resumed on February 24, not in March.

  881. · Iberia’s blackout put payment resilience back at the shop counter

    We removed attributions to a Bank of Spain account of ATMs on the day, a September 2025 ECB paper and an April 2026 Bank of Spain article, none of which we could confirm, and corrected the description of ENTSO-E’s final report to match its own wording.

  882. · For hospitals, HTI-1’s model cards covered only the EHR vendor’s own algorithms

    Narrowed the description of the HTI-5 proposal to what ASTP/ONC has published, removal of the AI model card (source attribute) requirements, and dropped an unverified statement that it would also remove the risk management requirements.

  883. · How the CVE contract scare exposed the public plumbing under every patching policy

    We removed an unconfirmed length for CISA’s April 2025 contract extension and an unconfirmed March 2026 report that the contract had been renegotiated, and replaced them with CISA’s own published statements.

  884. · How polyfill.io slipped past hospital tag reviews that checked each script only once

    We replaced a statement that HHS withdrew its appeal of the Texas tracking-technology ruling in August 2024; HHS filed a notice of appeal that month, and we could not confirm the date it was dropped.

  885. · How the DOJ’s bulk data rule made reach, not storage, the health data test

    Removed unverified hindsight details about the BIOSECURE Act’s enactment in the December 2025 defense authorization act and its designation deadline.

  886. · How the lapse of a 2015 law put counsel in the threat-sharing loop

    Corrected the hindsight to reflect CISA's February 2026 guidance that sharing during the lapses is covered, added the January to February 2026 lapse, and removed unverified claims about a December 2026 extension and the positions of the White House and a Senate committee chairman.

  887. · How Change Healthcare’s customers decided whether to pull the plug, and when to plug back in

    We removed an unconfirmed statement that final action on the proposed HIPAA Security Rule update had been moved to 2027 on the federal regulatory agenda; the verifiable point is that no final rule had been published by October 2026.

  888. · Hospital websites had a HIPAA problem because nobody owned the tags

    The description of The Markup’s 2022 findings was made precise (a third of the top 100 hospital websites and seven health systems’ patient portals), and unverified statements that HHS dropped its appeal in August 2024 and that several health systems settled pixel class actions were removed.

  889. · Hospital device data rights arrive one purchase order at a time

    An earlier version attributed to a law firm survey a finding that only six member states, including Germany and the Netherlands, had fully operational Data Act authorities; the September benchmark was by Cullen International, found that six of 21 surveyed states had designated authorities, and did not name them.

  890. · Hive’s takedown removed a supplier, not the ransomware market

    The hindsight section no longer gives a count of people affected by the Change Healthcare breach, which we could not confirm against a primary source; it now cites UnitedHealth’s April 2024 statement, and the account of ALPHV’s exit is attributed to reports.

  891. · HIPAA’s reproductive health attestation put the burden of purpose on the requester

    Removed an unverified statement that HHS declined to appeal the vacatur and that the Fifth Circuit dismissed a related appeal in September 2025, and clarified which notice of privacy practices changes the court left standing.

  892. · HHS could mandate hospital cybersecurity on its own; paying for it needed Congress

    Softened two unverifiable statements, that CMS had not proposed cybersecurity conditions of participation by the end of 2025 and that no incentive program was enacted, to statements of what we can find.

  893. · Helene tested what continuity plans take for granted: staff, signal and signatures

    Updated the death toll to the National Hurricane Center’s final count of at least 250 U.S. deaths.

  894. · Helene tested what continuity plans take for granted: staff, signal and signatures

    Removed unverified statements about satellite internet terminals being used to restore communications and later added to agency continuity kits.

  895. · HCA’s data on 11 million patients sat in an email-formatting store, outside the EHR’s controls

    We corrected the list of exposed fields to match HCA's disclosure (city, state and ZIP code rather than full addresses) and removed an unsourced row count.

  896. · The governors’ water letter handed one problem to three state secretaries

    We removed unconfirmed specifics: the March 21 date of the meeting with state secretaries, and the dates, finalization and 24-hour reporting term we had given for New York’s water cybersecurity rules.

  897. · FTX’s favored account was a setting in the code, and banks have settings too

    The description of FTX’s record-keeping failures now matches the bankruptcy chief executive’s House testimony, the trial-testimony reference was replaced with the CFTC complaint’s description of the “allow negative” code flag, and unverified statements about 2025 creditor repayments and later examiner focus were removed.

  898. · The FTC’s breach rule proposal drew the HIPAA line through the middle of a data flow

    Removed an unverified statement that CMS gathered pledges from technology companies in July 2025.

  899. · From crisis call to compliance record: OFAC’s ransomware advisory

    An earlier version said North Carolina barred public entities from paying ransoms in 2022; the North Carolina law was enacted in late 2021 as part of that year’s budget act.

  900. · Four weeks on paper: what Scripps exposed about downtime plans

    Removed an unverified claim that health systems broadly expanded multi-week downtime planning after 2021; the hindsight now presents it as the case those later incidents made.

  901. · Four regulators, no new law: the AI statement put the buyers of models on the hook

    Replaced an unverified claim that Colorado moved in 2026 to narrow its AI law with the verified 2025 delay of its start date to June 2026.

  902. · Forbearance on request: what the CARES Act asked of loan servicers

    Removed an unsupported claim that credit reporting of accommodated accounts remained a supervisory focus after the emergency, and restated forbearance exit outcomes to match CFPB servicer data.

  903. · For SNAP systems, paying less was harder than paying nothing

    We corrected the timeline of USDA’s partial-payment decisions to match its court filings, replaced an unverified claim that USDA told states on November 8 to undo full issuances with what the government’s filings and a November 10 court order show, replaced an unsourced claim about state recalculation times with USDA’s own statement to the court, and removed an unverified statement about how quickly full November benefits were issued.

  904. · For credit unions, the 1033 outline was a question for the core processor

    The October 2025 court action is now described accurately as a stay of the rule’s compliance dates, rather than an order barring enforcement until reconsideration is complete.

  905. · Five regulators’ AI questions read like an exam plan

    Updated the hindsight to note that in April 2026 the banking agencies replaced SR 11-7 with revised model risk guidance that excludes generative and agentic AI.

  906. · First Republic’s white-glove service had no answer for an uninsured balance

    Removed an unverified figure for the liquidity First Republic announced on March 12, 2023, and removed unverified statements about later deposit insurance bills and growth in reciprocal deposit programs.

  907. · FinCEN’s ransomware analysis turned well-written SARs into threat intelligence

    Corrected the advisory that asked filers for cyber indicators: it was FinCEN’s October 2020 ransomware advisory (updated on November 8, 2021), not a FinCEN advisory of September 21, 2021, which was the date of OFAC’s updated sanctions advisory.

  908. · Few banks held crypto. Many held crypto deposits.

    The January 3, 2023 statement’s concentration warning is now described as written (business models concentrated in crypto-asset activities or exposures); deposit concentration was the subject of the February 23, 2023 liquidity statement.

  909. · Under FDA’s change-control model, the AI device a hospital validates will not stay the one it runs

    Removed two unverified hindsight claims: that FDA had listed the January 2025 draft for finalization in fiscal 2026, and that a Congressional Research Service report characterized FDA’s 2026 guidance updates as deregulatory.

  910. · FDA’s decision support revision handed hospitals a classification question

    An earlier version said wellness wearables qualified only if their readings did not prompt clinical action, although the guidance allows them to suggest seeing a clinician; it also said FDA had signaled work on an AI framework, which we could not verify and have removed.

  911. · Faster settlement, longer nights: what two years of T+1 tell Europe’s operations desks

    An earlier version said EU and UK industry committees were working toward a testing approach shared with Switzerland; we could not verify that, and the article now says the Swiss post-trade council recommended the same date with a joint migration as its preferred outcome.

  912. · Executive Order 14028 gave zero trust three testable demands

    We reworded a statement that the June 2025 executive order softened software attestation requirements; the order struck several software security provisions of the January 2025 order, and we could not confirm a specific change to attestation.

  913. · Why Europe’s accessibility law turns every bank release into evidence

    An earlier version said published accounts described first-year enforcement as complaint-driven with corrective orders before penalties, which we could not verify; it now reports how Germany’s joint authority describes its own work.

  914. · Why Europe’s accessibility law turns every bank release into evidence

    An earlier version said work on revising the European accessibility standard was continuing; the revised standard, EN 301 549 V4.1.1, was in fact published in September 2026.

  915. · For EU consumer lenders, the credit-scoring deadline that mattered was never the AI Act’s

    We removed specific dates for the provisional agreement, Parliament vote and Council adoption of the AI Omnibus that we could not confirm, stated its confirmed July 27, 2026 entry into force, and removed an unverified claim that some member states were late transposing the Consumer Credit Directive.

  916. · An escort who cannot read the command is not a security control

    Removed an unsupported statement that the Pentagon would examine whether other providers had similar arrangements, clarified that the code review was a separate investigation, and added the September 2025 vendor ban and December 2025 law.

  917. · DORA’s two-year runway, measured in contract renewals

    The hindsight section no longer states details we could not confirm against primary sources: the number and date of the first critical-provider designations, the specific article removed from the subcontracting standard, and how far firms’ contract amendments ran into 2025.

  918. · DOJ’s accessibility delay moved one date and put the budget at risk

    An earlier version said DOJ was considering a separate rulemaking that could revise requirements for K-12 schools; the interim final rule says DOJ plans future rulemaking on the 2024 rule’s substantive requirements generally.

  919. · A deleted file, a national ground stop, and the runbook nobody rehearsed

    Unverified details were removed: that the ground stop was the first since September 2001, specific delay and cancellation counts, and hindsight claims about the NOTAM Improvement Act deadline, an April 2025 senators’ letter, a May 2025 contract award and a 2026 milestone; the hindsight now cites the FAA Reauthorization Act of 2024.

  920. · Cyclops Blink turned forgotten firewalls into someone else’s infrastructure

    Clarified that BOD 23-02 also allows zero trust access controls in place of removing internet exposure, and replaced descriptions of 2024 botnet operations with what US agency publications confirm.

  921. · A cyber grant with a rising match is a sustainment test

    Replaced unverified statements about a November 2025 extension, House passage of a reauthorization and how states spent the money with the program’s documented funding schedule and its February 2026 extension to September 30, 2026.

  922. · Crypto trust charters and community banks: the binding decision sits in the core

    Replaced unverified statements that the five charters stayed conditional through spring 2026 and that Circle’s was the first to receive final approval with Circle’s own account of its July 2026 final approval and opening, and removed an unsupported claim about bank trade groups’ continuing objections.

  923. · A credit union’s first report of a vendor breach may come from the attacker

    Removed an unverified statement that MeridianLink identified the incident around November 10, 2023; its public statement gave no date.

  924. · Convincing faces, unauthenticated seats: the Hong Kong deepfake was a meeting-identity failure

    We removed an unconfirmed detail that the funds went to five local bank accounts; the police account we could verify gives the amount and the number of transfers only.

  925. · Paused, not repealed: what CMMC’s suspension left defense contractors paying for

    An earlier version said the task force’s report was due on September 11; that was when the 60-day review closed, with the report expected afterward.

  926. · CMMC’s first phase priced a signature, not a score

    We removed an unverified statement of the Department of War’s reasons for suspending CMMC Phase 2 and an exact suspension date we could not confirm from a primary source, and described what stayed in force as reported by the Cyber AB.

  927. · Clearance, access and need-to-know: three controls the Discord leak pulled apart

    Removed an unverified statement that the Defense Department tightened intelligence distribution and expanded continuous vetting after the leak, and replaced it with findings from the Air Force inspector general's report.

  928. · Citrix gateways: the most exposed system in the hospital

    Corrected the account of the BSI’s September 2020 statement on the Düsseldorf University Hospital attack: the BSI linked the attack to the Citrix flaw and warned that systems could have been compromised before patching, but did not say backdoors were installed at that hospital.

  929. · Cheap to license, slow to permit: federal AI’s bottleneck moved to the CISO’s desk

    Corrected the FedRAMP timeline: FedRAMP published its AI prioritization criteria in mid-August 2025 and added individual services in the following weeks, and the Low impact level reflected what 20x offered at the time rather than a stated limit on those services.

  930. · Cheap contracts, valuable access: the market behind Coinbase’s bribed agents

    We removed hindsight claims naming the outsourcing provider, a customer notification count and the timing of lawsuits, which we could not confirm in primary sources, and replaced them with Coinbase’s own account of scope.

  931. · A chatbot’s history sidebar is a records system with someone else’s retention policy

    Updated the account of Italy’s €15 million fine against OpenAI: a Rome court upheld OpenAI’s challenge to the decision in March 2026.

  932. · Channel File 291 measured every recovery plan in hands per device

    We replaced statements about the release date of a Microsoft USB recovery tool and the 2025 Windows 11 release of quick machine recovery with descriptions we could confirm from Microsoft’s own posts.

  933. · Days of cash on hand was the resilience metric that mattered in the Change Healthcare outage

    We replaced an unconfirmed total of about $9 billion in provider advances, and an unconfirmed account of 2025 repayment demands, with the figure UnitedHealth gave Congress: more than $6.5 billion advanced by late April 2024.

  934. · The CFPB reached for payment apps while the customer’s money sat at partner banks

    Corrected the description of the CFPB’s Civil Penalty Fund payments to Synapse users: about $46 million was allocated in November 2025 and about $9 million more in May 2026, against an estimated shortfall of $60 million to $90 million, rather than “roughly half” of the shortfall.

  935. · With the CFPB paused, banks lost the outside signals their customer programs relied on

    Corrected the number of CFPB rules overturned under the Congressional Review Act in 2025 from “several” to two, and named them.

  936. · Free, measured and always on: the open banking interface the CFPB proposed and banks could not price

    We revised the account of the 2025 litigation to match the bureau’s own record, which says it would reexamine the rule and the court stayed the case in July 2025, and softened an unsourced statement about a bank charging aggregators.

  937. · The CAT’s retirement freed the framework and orphaned the risk profile

    Replaced a statement that supervisors stressed expectations were unchanged, and an unverified NCUA commitment to align its toolbox with newer frameworks, with what the Federal Reserve and NCUA actually published.

  938. · Bybit’s signers approved what their screens showed, which was not what they signed

    Corrected the description of business email compromise: it is one of the costliest fraud categories in the FBI’s annual reports, not the costliest, since investment fraud has reported larger losses in recent years.

  939. · BlackMatter’s reach was set by the directory, not the malware

    Attributed the link between BlackMatter and ALPHV to the FBI, and softened an unsupported claim that help desk social engineering is one of the dominant routes into large environments.

  940. · Bitfinex’s six-year trace ran through records that banks keep

    Removed unverified statements about the defendants' pleas and sentencing and a 2025 ruling on returning the bitcoin, and restated the Tornado Cash sanctions history to match Treasury's announcements.

  941. · Before the bias audit, the inventory: what New York City’s hiring-tool law asked of employers

    We removed an unverified statement that Colorado replaced its AI law in May 2026 and an unsourced reference to research on published audits, and described the Comptroller's December 2025 findings more precisely.

  942. · Bank cyber gaps now arrive as observations the board never has to see

    An earlier version listed slow patching among findings likely to fall below the MRA threshold; the final rule’s preamble cites unsupported operating systems and patch management as weaknesses that can cause material financial harm, and the text now says so.

  943. · Bank cyber gaps now arrive as observations the board never has to see

    An earlier version said observations could support management and IT ratings specifically and that the Federal Reserve was pursuing the same approach through internal policy; the rule says only that observations can support assigned ratings, and the Federal Reserve’s position is now described as not joining the rule.

  944. · Ardent took one network offline, and emergency departments in six states had to answer for it

    Replaced an unverified statement that all Ardent emergency departments were accepting ambulances by November 30, 2023 with Ardent’s own later account that diversions lasted a few days, and removed an unsupported claim that holiday and weekend timing remained common in hospital ransomware attacks.

  945. · Approval is easy, monitoring is hard: the Joint Commission’s AI guidance and the work after go-live

    Removed unverified statements that the Joint Commission launched its AI certification in early June 2026 and about that certification's standards; the playbook topics now match CHAI's published list.

  946. · An acquisition announcement is a free option on your exit plan

    Generalized a statement about a specific customer lawsuit and regulatory complaints over VMware renewal terms, which we could not confirm against primary sources.

  947. · At American Water, containment was the part customers saw

    Removed an unverified reference to a September 2024 cyberattack on the Arkansas City, Kansas, water plant.

  948. · Europe’s AI treaty attached its duties to the public function, not the payroll

    Removed an unverified statement that the European Union ratified the convention in May 2026 and that the treaty had not yet entered into force.

  949. · Article 50 kept its date, and it lands on the chat window

    An earlier version said final Commission guidance on Article 50 was still to come; the Commission adopted its final Article 50 guidelines on July 20, 2026, and the text now says so.

  950. · Agency certificates now expire faster than agency budgets turn over

    An earlier version placed the December 11 appropriations deadline inside the first 100-day certificate cycle; under CA/Browser Forum ballot SC-081 the 100-day cap applies only to certificates issued from March 15, 2027, so December 11 falls within the second 200-day cycle, and the sequence now distinguishes the 200-day and 100-day cycles.

  951. · A hallucination rate is a sales claim, and Texas enforced it like one

    Corrected the description of Texas SB 1188: it requires practitioners who use AI for diagnostic purposes to review the records it creates and to disclose that use, rather than requiring review of all AI-generated records and recommendations.

  952. · A hallucination rate is a sales claim, and Texas enforced it like one

    Removed a statement about California AB 3030 that we could not verify against a primary source for this update.

  953. · A 90-day declaration that ran for three years

    Clarified that CMS’s figures of 30 affected states and nearly 500,000 people to be reinstated were reported in September 2023, after its August 30 letter to states, rather than found in August.

  954. · Fourteen thousand accounts, 6.9 million people: the 23andMe ratio every health data platform should measure

    We corrected the attribution of the breach figures: 23andMe’s December 2023 SEC filing gave the 0.1 percent share of accounts, while the counts of about 14,000 accounts and 6.9 million profiles came from the company’s own published update.

  955. · 23andMe’s bankruptcy turned a privacy policy into a term of sale

    The hindsight section said bidding reopened because of the privacy ombudsman’s concerns; company filings show it reopened after TTAM’s higher bid, and we removed a deletion-request figure and a claim about Wojcicki’s bidding plans that we could not confirm in primary records.