Does HIPAA require encryption at rest, and which algorithm? What the rule actually says
The short answer is that the rule requires a mechanism to encrypt and decrypt, marks it Addressable, and names no algorithm, no key length and no mode. Both halves of that matter, and almost everything written about it gets one of them wrong: people read Addressable as optional, or they read the requirement as if it specified a cipher.
The answer, in the publisher's own words
Encryption at rest, in the rule's own words. It is an implementation specification of the access control standard.
164.312(a)(2)(iv) — HIPAA Security Rule (45 CFR part 164, subpart C) — Technical safeguards.
(iv) Encryption and decryption (Addressable). Implement a mechanism to encrypt and decrypt electronic protected health information.
The same source names the document and the control this provision sits in, which is how the citation above is put together:
§ 164.312 Technical safeguards.
Our record: /security-compliance-controls/164-312-a-2-iv/. Quoted from <https://www.ecfr.gov/api/versioner/v1/full/2026-11-01/title-45.xml?part=164§ion=164.312>, last checked 2026-11-15, due to be re-checked by 2026-12-15.
Encryption in transit is a separate provision, under transmission security, and is worded differently again.
164.312(e)(1) — HIPAA Security Rule (45 CFR part 164, subpart C) — Technical safeguards.
(e)(1) Standard: Transmission security. Implement technical security measures to guard against unauthorized access to electronic protected health information that is being transmitted over an electronic communications network.
Our record: /security-compliance-controls/164-312-e-1/. Quoted from <https://www.ecfr.gov/api/versioner/v1/full/2026-11-01/title-45.xml?part=164§ion=164.312>, last checked 2026-11-15, due to be re-checked by 2026-12-15.
164.312(e)(2)(ii) — HIPAA Security Rule (45 CFR part 164, subpart C) — Technical safeguards.
(ii) Encryption (Addressable). Implement a mechanism to encrypt electronic protected health information whenever deemed appropriate.
Our record: /security-compliance-controls/164-312-e-2-ii/. Quoted from <https://www.ecfr.gov/api/versioner/v1/full/2026-11-01/title-45.xml?part=164§ion=164.312>, last checked 2026-11-15, due to be re-checked by 2026-12-15.
What Addressable means is not a matter of opinion: the rule defines it, and the definition is an obligation with three branches, not permission to skip.
164.306(d)(1) — HIPAA Security Rule (45 CFR part 164, subpart C) — Security standards: General rules.
(1) Implementation specifications are required or addressable. If an implementation specification is required, the word “Required” appears in parentheses after the title of the implementation specification. If an implementation specification is addressable, the word “Addressable” appears in parentheses after the title of the implementation specification.
The same source names the document and the control this provision sits in, which is how the citation above is put together:
§ 164.306 Security standards: General rules.
Our record: /security-compliance-controls/164-306-d-1/. Quoted from <https://www.ecfr.gov/api/versioner/v1/full/2026-11-01/title-45.xml?part=164§ion=164.306>, last checked 2026-11-15, due to be re-checked by 2026-12-15.
164.306(d)(3) — HIPAA Security Rule (45 CFR part 164, subpart C) — Security standards: General rules.
(3) When a standard adopted in § 164.308, § 164.310, § 164.312, § 164.314, or § 164.316 includes addressable implementation specifications, a covered entity or business associate must—
Our record: /security-compliance-controls/164-306-d-3/. Quoted from <https://www.ecfr.gov/api/versioner/v1/full/2026-11-01/title-45.xml?part=164§ion=164.306>, last checked 2026-11-15, due to be re-checked by 2026-12-15.
164.306(d)(3)(i) — HIPAA Security Rule (45 CFR part 164, subpart C) — Security standards: General rules.
(i) Assess whether each implementation specification is a reasonable and appropriate safeguard in its environment, when analyzed with reference to the likely contribution to protecting electronic protected health information; and
Our record: /security-compliance-controls/164-306-d-3-i/. Quoted from <https://www.ecfr.gov/api/versioner/v1/full/2026-11-01/title-45.xml?part=164§ion=164.306>, last checked 2026-11-15, due to be re-checked by 2026-12-15.
164.306(d)(3)(ii)(A) — HIPAA Security Rule (45 CFR part 164, subpart C) — Security standards: General rules.
(A) Implement the implementation specification if reasonable and appropriate; or
Our record: /security-compliance-controls/164-306-d-3-ii-a/. Quoted from <https://www.ecfr.gov/api/versioner/v1/full/2026-11-01/title-45.xml?part=164§ion=164.306>, last checked 2026-11-15, due to be re-checked by 2026-12-15.
164.306(d)(3)(ii)(B) — HIPAA Security Rule (45 CFR part 164, subpart C) — Security standards: General rules.
(B) If implementing the implementation specification is not reasonable and appropriate—
Our record: /security-compliance-controls/164-306-d-3-ii-b/. Quoted from <https://www.ecfr.gov/api/versioner/v1/full/2026-11-01/title-45.xml?part=164§ion=164.306>, last checked 2026-11-15, due to be re-checked by 2026-12-15.
So an Addressable specification you decide not to implement leaves you with a documented assessment of why it was not reasonable and appropriate, and with whatever equivalent measure you put in its place. That is more work than implementing encryption, which is the practical reason almost everybody implements it.
If you want a published control that does talk about cryptographic mechanisms, it is NIST's, not the regulator's. These are the two provisions of SP 800-53 that bear on information at rest, and they leave the specifics to you as well — the bracketed words are values the catalogue says the organisation defines.
SC-28 — NIST SP 800-53 Rev 5.2.0 — Protection of Information at Rest.
As the catalogue's own rendering reads, with each value the organisation defines in square brackets:
Protect the [Selection (one or more): confidentiality; integrity] of the following information at rest: [Assignment: organization-defined information at rest].
The same provision in the publisher's machine-readable text, which is this record's evidence and prints a placeholder where that value goes:
Protect the {{ insert: param, sc-28_odp.01 }} of the following information at rest: {{ insert: param, sc-28_odp.02 }}.
The same source names the document and the control this provision sits in, which is how the citation above is put together:
"title": "Electronic (OSCAL) Version of NIST SP 800-53 Rev 5.2.0 Controls and SP 800-53A Rev 5.2.0 Assessment Procedures",
"id": "sc-28", "class": "SP800-53", "title": "Protection of Information at Rest",
"id": "sc", "class": "family", "title": "System and Communications Protection",
Our record: /security-compliance-controls/sc-28/. Quoted from <https://raw.githubusercontent.com/usnistgov/oscal-content/main/nist.gov/SP800-53/rev5/json/NIST_SP-800-53_rev5_catalog.json>, last checked 2026-11-15, due to be re-checked by 2026-12-15.
SC-28(1) — NIST SP 800-53 Rev 5.2.0 — Cryptographic Protection.
As the catalogue's own rendering reads, with each value the organisation defines in square brackets:
Implement cryptographic mechanisms to prevent unauthorized disclosure and modification of the following information at rest on [Assignment: organization-defined system components or media]: [Assignment: organization-defined information].
The same provision in the publisher's machine-readable text, which is this record's evidence and prints a placeholder where that value goes:
Implement cryptographic mechanisms to prevent unauthorized disclosure and modification of the following information at rest on {{ insert: param, sc-28.01_odp.02 }}: {{ insert: param, sc-28.01_odp.01 }}.
The same source names the document and the control this provision sits in, which is how the citation above is put together:
"title": "Electronic (OSCAL) Version of NIST SP 800-53 Rev 5.2.0 Controls and SP 800-53A Rev 5.2.0 Assessment Procedures",
"id": "sc-28.1", "class": "SP800-53-enhancement", "title": "Cryptographic Protection",
"id": "sc", "class": "family", "title": "System and Communications Protection",
Our record: /security-compliance-controls/sc-28-1/. Quoted from <https://raw.githubusercontent.com/usnistgov/oscal-content/main/nist.gov/SP800-53/rev5/json/NIST_SP-800-53_rev5_catalog.json>, last checked 2026-11-15, due to be re-checked by 2026-12-15.
SC-13b — NIST SP 800-53 Rev 5.2.0 — Cryptographic Protection.
As the catalogue's own rendering reads, with each value the organisation defines in square brackets:
Implement the following types of cryptography required for each specified cryptographic use: [Assignment: organization-defined types of cryptography].
The same provision in the publisher's machine-readable text, which is this record's evidence and prints a placeholder where that value goes:
Implement the following types of cryptography required for each specified cryptographic use: {{ insert: param, sc-13_odp.02 }}.
The same source names the document and the control this provision sits in, which is how the citation above is put together:
"title": "Electronic (OSCAL) Version of NIST SP 800-53 Rev 5.2.0 Controls and SP 800-53A Rev 5.2.0 Assessment Procedures",
"id": "sc-13", "class": "SP800-53", "title": "Cryptographic Protection",
"id": "sc", "class": "family", "title": "System and Communications Protection",
Our record: /security-compliance-controls/sc-13b/. Quoted from <https://raw.githubusercontent.com/usnistgov/oscal-content/main/nist.gov/SP800-53/rev5/json/NIST_SP-800-53_rev5_catalog.json>, last checked 2026-11-15, due to be re-checked by 2026-12-15.
What the rule does not say
The Security Rule names no algorithm, no key length, no cipher mode and no validation programme. There is no HIPAA-approved algorithm.
Checked, not asserted: none of AES, SHA, RSA, key length, cipher, FIPS, bit appears anywhere in the 105 provisions we hold of the whole HIPAA Security Rule. That is a search of the publisher's own words, and it is what the gate on this page tests; if one of those words turned up, this page would stop being built.
Where an organisation wants a named algorithm, the usual route is to adopt one of NIST's documents by choice. We hold two things that help: the status of each algorithm on NIST's own transition schedule, and which cryptographic modules hold a current FIPS 140 validation certificate. Neither of those is HIPAA telling you what to use.
The same answer for a machine
- FIPS 140 module validation status — is the module you are relying on still validated, and when does its certificate sunset.
- NIST algorithm status and transitions — what is approved, deprecated and disallowed, with the replacement named.
The other questions answered here
Does HIPAA apply to my app?, What does HIPAA require software to do?, What must I log for HIPAA, and how long must records be kept?, What session timeout do HIPAA and NIST require?, What password rules does NIST state?, Do I need multi-factor sign-in, and under which rule?, How fast must I report a breach, by law and by state?, Which state privacy laws apply to my app, by revenue and number of consumers?, Which NIST 800-53 controls bear on a database, on object storage, on logs and on backups?, What is SOC 2, and what in it can and cannot be quoted for free?, Which cryptographic algorithms and TLS certificate lifetimes stop being acceptable, and when?.
All of them are listed on the question list.
What this page is
This page is assembled automatically out of the records named on it. No sentence of a rule on it is ours: every one is quoted from the publisher that wrote it, with a link to the page it was quoted from and the date we last checked that page.
SOC 2, ISO/IEC 27001 and PCI DSS are not quoted anywhere on these pages. The bodies that write those documents sell the text, and our position, written down in our constitution, is that facts plus a short attributed quote with a link are fine but republishing licensed text is not. So nothing here quotes a trust services criterion or an ISO clause. What can be quoted is the rules the public bodies publish — the HIPAA Security Rule, NIST SP 800-53, federal retention regulations, state statutes and the CA/Browser Forum's requirements — and that is what every answer here is built out of.
This is not legal advice and it is not a statement that any system complies with anything. A provision quoted here is a sentence from a published document, not a finding about your software. Who decides: your own counsel, your auditor, and the regulator.