News
Segment first: the migration rule HHS wants to make mandatory
November 9, 2026 · PenDraco
Large health data breaches went from 302 in 2018 to 626 in 2022, and the people affected from 12 million to 42 million. HHS has proposed to make network segmentation a required safeguard. One hospital migration for 92,000 users ran on that rule before it was written down.
Two tables describe the problem. The Department of Health and Human Services counts large breaches of protected health information, the ones that affect 500 or more people. There were 302 in 2018 and 626 in 2022. The people affected went from 12.2 million to 41.7 million in the same four years. IBM's 2026 Cost of a Data Breach study puts the average cost of a breach in the United States at 11.5 million dollars, and reports that one in four malicious breaches was AI-enabled, a 56 percent increase.
The regulator's answer arrived in January 2025. This article is about what it asks for, why the hardest place to deliver it is a migration, and one migration that delivered it.
What HHS proposed
On January 6, 2025, HHS published a proposed rule to strengthen the HIPAA Security Rule (90 FR 898). Three changes matter to anyone who runs health data systems.
First, network segmentation becomes a requirement. The proposed rule would require a regulated entity to deploy technical controls that segment its electronic information systems, and to keep written policies that limit access to protected health information to authorized workstations. The text explains why with one scenario: an intruder who compromises a point-of-sale system and moves laterally to the electronic health record, because nothing on the network stopped the movement.
Second, the proposal removes the distinction between "required" and "addressable" safeguards. Since 2003, many safeguards have been addressable, which meant an entity assessed whether each one was reasonable and appropriate for it and documented the decision. Under the proposal, with limited exceptions, every implementation specification becomes mandatory.
Third, every regulated entity would keep a technology asset inventory and a network map that shows how protected health information moves through its systems.
As of this writing, the Federal Register carries no final rule under this proposal. The direction is not in doubt. The three changes describe how a careful engineer already builds.
Why migrations decide it
Segmentation is easy to draw and hard to keep. The place it fails is a migration, because a migration recreates every boundary at once. Teams copy the data. They rebuild identities and permissions on a new platform. Network paths that took years to tighten are opened for the move. The people who know the old system are busy learning the new one. A boundary that holds on the diagram can quietly stop holding in the second week of the cutover.
So the team must answer the design question before the first byte moves: where will protected health information live on the new platform, and who can reach it there? Then the harder one: how will we prove that at every step? If the answer comes after the move, the move decides it for you.
The engagement
Tampa General Hospital describes itself as a private not-for-profit hospital and one of the most comprehensive medical facilities in West Central Florida, serving a population of more than 6 million. PenDraco's founder, Steve Onoja, led an analytics migration there to self-managed Azure, serving roughly 92,000 users. The working rule was segmentation. Protected health information stayed inside its own boundary through every stage of the move.
"Self-managed" is the other half of the story. When the organization operates the platform itself, the boundary belongs to the organization. The people responsible for it can inspect it and test it, with no provider between them and their own network map.
The point is not that one migration anticipated a rule. It is that the rule and the engineering come from the same source: what failed last time. The HHS text and the migration plan both start with the same drawing.
What this means for a leader
Treat segmentation as an input to the migration design, not a finding after it. The network map HHS now asks for is the migration's first deliverable.
Read the breach numbers as a rate, not a total. Twice the large breaches and three times the people affected, in four years, is the trend the proposal responds to. Your own estate sits on the same curve unless you engineer the boundaries.
Keep the boundary in your own hands. A platform you operate is a platform you can prove.
That is the work PenDraco's embedded engineering line does: a senior engineer inside your team, on a fixed scope, who draws the boundary first and ships the migration around it. If you have a move coming and the map is not drawn, get in touch.
Sources
- U.S. Department of Health and Human Services, Office for Civil Rights, HIPAA Security Rule To Strengthen the Cybersecurity of Electronic Protected Health Information, proposed rule, 90 FR 898, January 6, 2025: proposed 45 CFR 164.312(a)(2)(vi) and 164.308(a)(10)(ii)(E) (network segmentation), the removal of the addressable category, the technology asset inventory and network map, and Table 5 (breaches of PHI, 2018 to 2022). Federal Register document list for RIN 0945-AA22 checked November 9, 2026: no final rule published.
- IBM and Ponemon Institute, Cost of a Data Breach Report 2026, July 2026: United States average breach cost 11.5 million dollars; one in four malicious breaches AI-enabled, up 56 percent.
- Tampa General Hospital, About TGH, accessed November 9, 2026 (the hospital's own description).
- The engagement is described from the public record and the founder's own delivery history; no client material is published.