Share this
HIPAA Security Rule Proposal: What Healthcare Teams Can Prepare Now
by Charlie Treadwell on Apr 18, 2026, 3:00:04 PM
Healthcare security teams can prepare for stronger cybersecurity requirements without treating a proposed rule as an active compliance deadline. HHS’s January 2025 HIPAA Security Rule proposal would expand requirements for protecting electronic protected health information (ePHI), including asset inventories, network maps and segmentation. The proposal does not itself replace the current Security Rule.
Separate current obligations from proposed changes
The current HIPAA Security Rule remains the applicable baseline while HHS considers the proposal. Covered entities and business associates should continue their required risk analysis, risk management and safeguards. The current distinction between required and addressable implementation specifications does not make an addressable safeguard optional without analysis and documentation.
What the proposal would change
HHS proposes more explicit requirements for maintaining an inventory of technology assets and a network map, strengthening risk analysis, and documenting security policies and procedures. It also proposes changes involving multi-factor authentication, encryption and network segmentation. These are proposed provisions. Their final wording, exceptions, scope and compliance dates must be checked against any eventual final rule.
Prepare the evidence your team needs
Start with the assets and communication paths that support ePHI. Identify ownership, clinical function, business dependencies and the network infrastructure that can enforce policy. Bring clinical engineering, IT, security and application owners into the review. Document assets with operational constraints and the risk-management decisions associated with them.
Review segmentation before enforcement
Define the communication each asset group needs. Use observed traffic and operational knowledge to review proposed access policies, then simulate changes and resolve questions with the teams responsible for clinical services. Administrators decide which policies move to enforcement. Roll out reviewed changes in phases and retain evidence of the decisions and results.
Where Elisity fits
Elisity IdentityGraph correlates network observations with identity, endpoint, CMDB, IoT and cloud context. Teams use that context to build policy around users, devices and workloads. Elisity simulates policies against observed traffic and enforces approved access restrictions through supported network infrastructure, without installing an Elisity software agent on protected assets. These capabilities can support a healthcare security program; they do not establish HIPAA compliance or replace required encryption, authentication, risk analysis or legal review.
Keep the implementation plan separate from the legal deadline
A phased preparation plan is useful today, but it should be driven by clinical risk and operational readiness. Track the HHS rulemaking and reassess the plan when a final rule and its effective and compliance dates are published. Avoid promising that one technology satisfies a fixed number of regulatory controls.
Frequently asked questions
Is the proposed HIPAA Security Rule already in effect?
No. The HHS cybersecurity update discussed here remains a proposal as of October 11, 2026. The current Security Rule remains applicable. A proposed rule and an agency agenda target do not themselves create new compliance obligations.
Do healthcare organizations have 240 days to comply now?
There is no active 240-day countdown created by this proposal. Any final implementation period must be confirmed from a published final rule. Do not calculate a deadline from the January 2025 proposal or an expected publication date.
Does HIPAA currently require network segmentation?
The current rule requires appropriate safeguards based on the applicable requirements and risk analysis; it does not use the explicit segmentation provision proposed in the January 2025 update. HHS proposes a more explicit segmentation requirement. Evaluate segmentation against your current risks and obligations rather than presenting the proposal as current law.
Does microsegmentation make an organization HIPAA compliant?
No. Microsegmentation can help restrict unnecessary network access and provide policy evidence. HIPAA compliance also depends on the organization’s applicable safeguards, risk analysis, processes, documentation and other controls.
What can healthcare security teams do before a final rule?
Maintain asset and communication visibility, identify high-risk access, review policies with clinical and application owners, simulate proposed changes, and retain evidence. Continue meeting current obligations and track HHS for the final rule and its actual dates.
Primary sources
Share this
- November 2026 (2)
- October 2026 (4)
- August 2026 (3)
- July 2026 (8)
- June 2026 (4)
- May 2026 (5)
- April 2026 (10)
- March 2026 (6)
- February 2026 (13)
- January 2026 (4)
- December 2025 (4)
- November 2025 (2)
- October 2025 (4)
- September 2025 (3)
- August 2025 (5)
- July 2025 (5)
- June 2025 (5)
- May 2025 (4)
- April 2025 (5)
- March 2025 (6)
- February 2025 (3)
- January 2025 (5)
- December 2024 (4)
- November 2024 (5)
- October 2024 (6)
- September 2024 (5)
- August 2024 (3)
- July 2024 (4)
- June 2024 (2)
- April 2024 (3)
- March 2024 (2)
- February 2024 (1)
- January 2024 (3)
- December 2023 (1)
- November 2023 (1)
- October 2023 (2)
- September 2023 (3)
- June 2023 (1)
- May 2023 (3)
- April 2023 (1)
- March 2023 (6)
- February 2023 (4)
- January 2023 (3)
- December 2022 (7)
- November 2022 (3)
- October 2022 (1)
- July 2022 (1)
- May 2022 (1)
- November 2021 (1)
- August 2021 (1)
- May 2021 (2)
- April 2021 (2)
- March 2021 (3)
- February 2021 (1)
- November 2020 (1)
- September 2020 (1)
- August 2020 (2)

No Comments Yet
Let us know what you think