Updated November 17, 2026: The HIPAA Security Rule update is still a proposal, not a finalized December 2026 mandate. HHS published the Notice of Proposed Rulemaking (NPRM) in December 2024; the current Security Rule remains in effect while the rulemaking proceeds. Current reporting on the federal regulatory agenda places final action no earlier than July 2027, not December 2026. This guide distinguishes today’s duties from proposed controls so your practice can improve security without relying on a false deadline.

Current duties versus proposed changes
The existing Security Rule requires administrative, physical, and technical safeguards appropriate to your risks. The proposal would make implementation specifications required with limited exceptions, add more detailed documentation, and specify additional control and testing cadences. The examples below are a practical comparison, not an exhaustive legal checklist.
| Area | Current Security Rule | What the NPRM proposes |
|---|---|---|
| Multi-factor authentication | Access controls, identification, and authentication apply; MFA is not expressly named. | Require MFA with limited exceptions. |
| Encryption | Encryption is an addressable implementation specification, with required documentation of the chosen approach. | Require encryption of ePHI at rest and in transit, with limited exceptions. |
| Vulnerability scanning | Risk analysis, risk management, and technical evaluation duties apply; no six-month scanning cadence is specified. | Require vulnerability scanning at least every six months. |
| Penetration testing | No annual penetration-test cadence is specified. | Require penetration testing at least once every 12 months. |
| Network segmentation | Current safeguards are risk-based; segmentation is not expressly prescribed. | Require network segmentation. |
| Asset inventory | Risk analysis obligations already apply; an express technology asset inventory and network map are not specified. | Maintain a technology asset inventory and network map, with at least annual revisions and updates for relevant changes. |
| Incident response | Security incident procedures and contingency planning are required. | Add written response plans and procedures, testing and revision procedures, and more specific restoration requirements. |
| Compliance review | Audit controls and periodic technical and nontechnical evaluations apply. | Require a compliance audit at least once every 12 months and greater testing specificity. |
Practical safeguards to prioritize now

You do not need a final rule to address known security gaps. Prioritize controls based on your documented risk analysis, systems, vendors, and operational needs. The following recommendations deliberately avoid presenting proposed cadences as current legal mandates:
- Identity and access. Assign unique accounts, enforce MFA where appropriate, and promptly remove access when roles change.
- Encryption. Assess and document encryption for ePHI at rest and in transit, including backups and portable devices.
- Vulnerability and patch management. Set risk-based scanning and remediation schedules; a critical-14-day or high-30-day target is a policy choice, not a universal current HIPAA deadline.
- Independent testing. Consider annual penetration testing as a good security practice and preparation for the proposed requirement.
- Asset and data visibility. Inventory systems that handle ePHI and document how information moves between them and your vendors.
- Network boundaries. Use segmentation and access restrictions appropriate to your environment.
- Resilience. Protect backups, test restores, and rehearse incident and downtime procedures. A 3-2-1-1-0 backup design is a recommended architecture, not a HIPAA-mandated formula.
Evidence to maintain

- Current, documented security risk analysis and risk-management actions
- Identity and MFA coverage reports appropriate to your environment
- Endpoint-protection and asset-inventory records
- Restore-test results with dates, scope, and remediation
- Vulnerability-scan and patch-remediation records
- Independent security-test and incident-exercise findings, when performed
- Written policies and evidence that workforce responsibilities are understood
- Business Associate Agreements and vendor-scope records
- Audit logging, retention, and review procedures
A practical 90-day security review
- Days 1–14: Inventory ePHI systems and access; review the current risk analysis.
- Days 15–45: Address identity and access-control gaps based on risk.
- Days 30–60: Verify encryption and remediate unprotected data paths.
- Days 45–75: Review vulnerabilities, patch priorities, and vendor responsibilities.
- Days 60–90: Test recovery and incident procedures; document decisions and remaining work.
Bottom line
There is no universal December 2026 HIPAA Security Rule compliance deadline. Keep complying with the existing rule, use a documented risk analysis to guide improvements, and monitor the official rulemaking before treating a proposal as an obligation. A 90-day review can help organize that work; it does not certify compliance.
Sources
- HHS OCR: HIPAA Security Rule NPRM fact sheet — the proposal and confirmation that the current rule remains in effect.
- GovInfoSecurity, July 8, 2026 — reporting on the federal agenda’s revised timing of no earlier than July 2027.
Need help organizing a HIPAA-aligned security review? ACS provides managed IT and cybersecurity support for healthcare organizations. Contact us to discuss your environment.



