Encryption at rest protects stored data, such as databases, laptops, backups, and imaging archives. Encryption in transit protects data moving across a network, such as telehealth sessions, API calls, and records sent to a vendor. The HIPAA Security Rule treats them as two separate specifications: encryption and decryption under the access control standard, and encryption under the transmission security standard. Both are addressable today, which means an organization must assess each one, implement it when reasonable and appropriate, and document its reasoning when it chooses something else [1][2]. HHS points to NIST publications for each state of data: SP 800-111 for stored data, and SP 800-52, SP 800-77, and SP 800-113 for data in motion [3]. A proposal HHS issued in December 2024 would require encryption at rest and in transit, with limited exceptions, and it was still proposed and not final in the latest sources reviewed [5][7][8].
The table below compares the two at a glance. The sections after it explain what each one does, how the Security Rule and NIST treat it, what the breach notification safe harbor means, how cloud providers change the picture, and what Censinet benchmark data show about data protection coverage.
What Is Encryption at Rest?
Encryption at rest converts stored data into unreadable text, so the data stays protected if the device or storage system holding it is lost, stolen, or accessed without authorization. HHS describes encryption as the use of an algorithmic process to convert data into a form that has no meaning without a key, and it applies that definition in its guidance on unsecured protected health information (PHI) [3].
Key Features of Encryption at Rest
NIST SP 800-111, published in November 2007, explains the basics of storage encryption and describes three types of solutions: full disk encryption, volume and virtual disk encryption, and file and folder encryption [9]. The Advanced Encryption Standard (AES), published by NIST as FIPS 197 in November 2001, can use keys of 128, 192, and 256 bits and encrypts data in blocks of 128 bits [12]. HHS's guidance does not name AES or any other algorithm. It names the NIST publication for data at rest and conditions on how keys are handled: the decryption key or process must not have been breached, and decryption tools should be stored separately from the data they encrypt and decrypt [3].
Healthcare Applications
Stored ePHI sits in more places than most inventories list: electronic health record databases, imaging archives, laptops, tablets, phones, removable media, and backups. HealthIT.gov's mobile device tips include installing and enabling encryption and deleting all stored health information before discarding a device [14]. For retired media, HHS's guidance sets a separate standard: electronic media is cleared, purged, or destroyed consistent with NIST SP 800-88, and paper is shredded or destroyed [3].
Encryption at rest has a limit that matters during an attack. HHS notes that full disk encryption can leave files readable once a user is logged in, and that ransomware running as that user can then encrypt them. In that case a breach is presumed [4]. Encryption at rest protects against loss of the device or media, but it does not stop an authenticated session from reading the data.
What Is Encryption in Transit?
Encryption in transit, also called data in motion encryption, protects ePHI as it moves between systems, devices, and organizations. HHS's guidance describes valid processes for data in motion as those that comply, as appropriate, with NIST SP 800-52 for Transport Layer Security (TLS), SP 800-77 for IPsec virtual private networks (VPNs), or SP 800-113 for SSL VPNs, or others that are validated under Federal Information Processing Standard (FIPS) 140-2 [3].
Key Features of Encryption in Transit
NIST SP 800-52 Revision 2, published in August 2019, requires TLS 1.2 as the minimum appropriate secure transport protocol for federal information and requires support for TLS 1.3 by January 1, 2024 [10]. Those dates apply to federal systems. HHS's guidance names SP 800-52 as the TLS reference, so confirm the current revision with your security team when you set standards. The Security Rule adds two related specifications under transmission security. Integrity controls address whether ePHI is altered in transit, and encryption addresses whether it can be read [2].
Healthcare Applications
Data in motion covers telehealth video and audio, calls between a pharmacy system and an electronic health record, remote access by clinicians working from home, and records shared with billing vendors, insurers, and diagnostic services. Each exchange crosses a boundary where the organization does not control the network, so the encryption settings, and the agreement with the receiving party, are the controls that apply. HealthIT.gov's tips also call for adequate security when sending or receiving health information over public Wi-Fi networks [14].
Key Differences Between Encryption at Rest and Encryption in Transit
Encryption at rest and encryption in transit are separate controls, and HIPAA treats them as separate specifications. They protect against different events. Encryption at rest covers the loss or theft of a device or storage medium. Encryption in transit covers interception while data crosses a network. A stored record can be well encrypted and still be exposed when it is sent in clear text, and a connection can be well encrypted while the database behind it is not. The table below shows where each sits in the Security Rule.
What HIPAA Requires Today and What Is Proposed
The Current Rule
Encryption is addressable today, which means a documented decision and not a free choice. HHS's summary of the Security Rule explains that addressable does not mean optional: the entity decides whether the specification is reasonable and appropriate, and if it is not, documents why and adopts an alternative that serves the same purpose [1]. The risk analysis is where that decision gets made, because it shows where ePHI sits and moves and which protections already exist. HHS's summary adds that required documentation is kept for six years [1].
The Breach Notification Safe Harbor
HHS's guidance on unsecured PHI sets the second reason to encrypt. PHI that is encrypted consistent with the NIST publications HHS names, and whose decryption key was not breached, is not unsecured PHI, so the Breach Notification Rule does not require notification when it is lost [3]. The safe harbor is narrow. HHS's ransomware fact sheet explains that when ransomware encrypts ePHI that was already protected only by disk-level encryption and a logged-in user session, a breach is presumed unless the entity shows a low probability that the PHI has been compromised [4].
The Proposed Rule
In December 2024, HHS issued a notice of proposed rulemaking that would require encryption of ePHI at rest and in transit, with limited exceptions, and would remove the distinction between required and addressable implementation specifications [5]. The notice was published in the Federal Register on January 6, 2025 [6]. A proposed rule is not a requirement, and the current Security Rule remains in effect until HHS finalizes a change. HHS says so on its own fact sheet [5]. HIPAA Journal's July 2026 update reports that OMB's 2026 Regulatory Agenda lists a final rule by July 2027 [7], and Compliancy Group's tracker, last updated September 20, 2026, still lists the rule as proposed and not final [8].
Plan for the proposal without treating it as law. Where a system already holds encrypted data at rest and in transit, the proposal changes little. Where it does not, the gap list from your risk analysis also shows which systems the proposal would affect.
FIPS 140-2 and Choosing Validated Modules
HHS's guidance refers to FIPS 140-2 validated modules and was last reviewed in 2013 [3]. NIST's transition page says FIPS 140-2 modules can stay active for five years after validation or until September 21, 2026, when FIPS 140-2 validations move to the historical list. It adds that NIST's validation program continues to support the purchase and use of those modules for existing systems [11]. When you buy or renew a product, ask which validation its cryptographic module carries and when it expires, and confirm current NIST references with your security team.
Use Cases and Implementation Guidelines
Encryption at Rest Use Cases
Start where loss is most common and most visible: laptops, tablets, phones, and removable media that leave the building, then backups and archives, then servers and databases. Document the standard in plain language, name an owner for keys, and record what you decided about each system, since a decision not to encrypt needs a written alternative under the addressable rules [1].
Encryption in Transit Use Cases
Start with every path that crosses a network you do not control: remote access, telehealth, interfaces to vendors and payers, and application programming interface calls. Use TLS at the versions NIST SP 800-52 Revision 2 describes, use IPsec or SSL VPNs consistent with the NIST publications HHS names, and test connections after each change, because one misconfigured interface can send data in clear text [3][10].
Cloud Providers and Business Associates
A cloud provider that holds only encrypted data and no key is still a business associate. HHS's cloud computing guidance says lacking an encryption key does not exempt a cloud service provider from business associate status, so a business associate agreement is required either way. The provider is contractually liable under the agreement and directly liable under the HIPAA Rules. The same guidance adds that encryption alone does not cover integrity, availability, or the other safeguards the Security Rule requires [13]. For a healthcare organization, that means a vendor's encryption claims belong in the vendor file next to the agreement, the security review, and the incident reporting terms.
Implementation Guidelines
Work in a fixed order. Inventory where ePHI is stored and where it travels, using the risk analysis. Decide the standard for each state of data. Select modules and settings that match the NIST publications HHS names. Store decryption tools apart from the data they decrypt [3]. Test restoration of encrypted backups, since an encrypted backup that cannot be decrypted is a loss. Review the settings after any major system change and record the date.
When to Use Each Encryption Method
When to Prioritize Encryption at Rest
Prioritize encryption at rest for anything that can be lost or stolen, which means portable devices and media first, and for backups and archives, because those are the copies that outlive a system. It also supports the breach safe harbor when a device goes missing [3].
When to Prioritize Encryption in Transit
Prioritize encryption in transit where data leaves your control: remote access, telehealth, vendor and payer interfaces, and cloud connections. It protects against interception on networks the organization does not manage [3].
Using Both Methods Together
Use both, and verify both. A team that encrypts storage but leaves a vendor interface open has protected one path and exposed another. Layer access control, monitoring, and tested backups on top, since encryption by itself does not answer every incident [4].
What the Benchmark Data Show About Coverage
Censinet's 2025 Healthcare Cybersecurity Benchmarking Study surveyed 69 healthcare and payer organizations from September to December 2024, and the answers are self-reported and not audited [15]. The HHS Essential Goals averaged 78% coverage (n=69), and the HICP practices averaged 70% (n=32). The study does not report a score for encryption alone. The closest measure is the HICP practice for Data Protection and Loss Prevention, which averaged 58% (n=32). The HHS Cybersecurity Performance Goals include Strong Encryption as an Essential Goal. Vendor and Supplier Cybersecurity Requirements averaged 65% (n=69), and the other nine Essential Goals ranged from 74% to 83% (n=69). Strong Encryption is one of those nine, but the study does not give it its own score [15].
These scores show where peers report thinner coverage. They do not test whether any organization meets the Security Rule, and the HICP section used 32 organizations while the HHS goals used all 69, so the two should not be blended [15].
Using Technology for Encryption Governance
Encryption decisions generate records: the standard for each system, the reasoning behind each addressable decision, vendor evidence, and the findings that come out of testing. Censinet's enterprise risk capability consolidates findings in the Censinet Risk Register with defined ownership, status tracking, and longitudinal history [17]. Its third-party risk capability keeps a centralized vendor and product inventory, adds automated rapid inherent risk scoring, sends breach and ransomware notifications focused on the vendors in that inventory, and routes events through an incident review workflow into the Risk Register and a remediation workflow. It also automates corrective action plans, tracks remediation progress, and keeps an audit-ready history, and people make every final risk decision [16].
Conclusion
Key points
Encryption at rest and encryption in transit are separate Security Rule specifications, and both are addressable today. HHS points to NIST SP 800-111 for stored data and to SP 800-52, SP 800-77, and SP 800-113 for data in motion. Encryption that meets that standard can remove the breach notification duty, but it does not protect data from an authenticated session. The December 2024 proposal would require both with limited exceptions and was still proposed in the latest sources reviewed.
Next steps
List where ePHI is stored and where it travels, record the encryption decision for each system, and confirm each vendor's encryption terms are in its agreement. Then check which validation each cryptographic module carries.
References
- U.S. Department of Health and Human Services. Summary of the HIPAA Security Rule (content last reviewed August 7, 2026). https://www.hhs.gov/ocr/privacy/hipaa/understanding/srsummary.html
[2] Electronic Code of Federal Regulations. 45 CFR 164.312, Technical safeguards (Title 45 up to date as of July 9, 2026). https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-C/part-164/subpart-C/section-164.312
[3] U.S. Department of Health and Human Services. Guidance to Render Unsecured Protected Health Information Unusable, Unreadable, or Indecipherable to Unauthorized Individuals (content last reviewed July 26, 2013). https://www.hhs.gov/hipaa/for-professionals/breach-notification/guidance/
[4] U.S. Department of Health and Human Services, Office for Civil Rights. Fact Sheet: Ransomware and HIPAA (content last reviewed September 20, 2021). https://www.hhs.gov/hipaa/for-professionals/security/guidance/cybersecurity/ransomware-fact-sheet/index.html
[5] U.S. Department of Health and Human Services. HIPAA Security Rule Notice of Proposed Rulemaking to Strengthen the Cybersecurity of Electronic Protected Health Information, fact sheet (issued December 27, 2024). https://www.hhs.gov/hipaa/for-professionals/security/hipaa-security-rule-nprm/factsheet/index.html
[6] U.S. Department of Health and Human Services. HIPAA Security Rule To Strengthen the Cybersecurity of Electronic Protected Health Information, notice of proposed rulemaking, RIN 0945-AA22, Federal Register (January 6, 2025). https://govinfo.gov/content/pkg/FR-2025-01-06/pdf/2024-30983.pdf
[7] HIPAA Journal. Final Rule Implementing HIPAA Security Rule Updates Edges Closer (posted March 20, 2026; July 2026 update). https://www.hipaajournal.com/final-rule-implementing-hipaa-security-rule-updates-edges-closer/
[8] Compliancy Group. The Proposed HIPAA Security Rule Update (page updated September 20, 2026). https://compliancy-group.com/proposed-hipaa-security-rule-update-2026/
[9] National Institute of Standards and Technology. Guide to Storage Encryption Technologies for End User Devices, SP 800-111 (November 2007). https://csrc.nist.gov/publications/detail/sp/800-111/final
[10] National Institute of Standards and Technology. Guidelines for the Selection, Configuration, and Use of Transport Layer Security (TLS) Implementations, SP 800-52 Revision 2 (August 2019). https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-52r2.pdf
[11] National Institute of Standards and Technology. FIPS 140-3 Transition Effort (page updated April 13, 2026). https://csrc.nist.gov/Projects/fips-140-3-transition-effort
[12] National Institute of Standards and Technology. Advanced Encryption Standard (AES), FIPS 197 (published November 26, 2001; page updated July 25, 2024). https://www.nist.gov/publications/advanced-encryption-standard-aes
[13] U.S. Department of Health and Human Services. Guidance on HIPAA and Cloud Computing (published October 6, 2016; modified December 23, 2022). https://www.hhs.gov/hipaa/for-professionals/special-topics/cloud-computing
[14] HealthIT.gov. 10 Tips to Protect Health Information on a Mobile Device (postcard; no date shown). https://www.healthit.gov/sites/default/files/postcard-10-tips-protect-health-information-on-a-mobile-device.pdf
[15] Censinet. 10 Insights from the 2025 Healthcare Cybersecurity Benchmarking Study (published April 4, 2025). https://censinet.com/perspectives/10-insights-from-cybersecurity-benchmarking-studies
[16] Censinet. Third-Party Risk. https://censinet.com/capabilities/third-party-risk
[17] Censinet. Enterprise Risk. https://censinet.com/capabilities/enterprise-risk