What does HIPAA require software to do? The technical safeguards, one provision at a time
The part of the HIPAA Security Rule that bears on software is one section: the technical safeguards at 45 CFR 164.312. It is short enough to read in full, and it is printed in full below, each provision exactly as the Code of Federal Regulations prints it. Where a provision is marked Addressable rather than Required, the rule's own words say what that means, and it does not mean optional.
The answer, in the publisher's own words
Every provision of the technical safeguards, in the order the regulation prints them.
164.312 — HIPAA Security Rule (45 CFR part 164, subpart C) — Technical safeguards.
A covered entity or business associate must, in accordance with § 164.306:
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/. 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(a)(1) — HIPAA Security Rule (45 CFR part 164, subpart C) — Technical safeguards.
(a)(1) Standard: Access control. Implement technical policies and procedures for electronic information systems that maintain electronic protected health information to allow access only to those persons or software programs that have been granted access rights as specified in § 164.308(a)(4).
Our record: /security-compliance-controls/164-312-a-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(a)(2)(i) — HIPAA Security Rule (45 CFR part 164, subpart C) — Technical safeguards.
(i) Unique user identification (Required). Assign a unique name and/or number for identifying and tracking user identity.
Our record: /security-compliance-controls/164-312-a-2-i/. 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(a)(2)(ii) — HIPAA Security Rule (45 CFR part 164, subpart C) — Technical safeguards.
(ii) Emergency access procedure (Required). Establish (and implement as needed) procedures for obtaining necessary electronic protected health information during an emergency.
Our record: /security-compliance-controls/164-312-a-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.
164.312(a)(2)(iii) — HIPAA Security Rule (45 CFR part 164, subpart C) — Technical safeguards.
(iii) Automatic logoff (Addressable). Implement electronic procedures that terminate an electronic session after a predetermined time of inactivity.
Our record: /security-compliance-controls/164-312-a-2-iii/. 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(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.
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.
164.312(b) — HIPAA Security Rule (45 CFR part 164, subpart C) — Technical safeguards.
(b) Standard: Audit controls. Implement hardware, software, and/or procedural mechanisms that record and examine activity in information systems that contain or use electronic protected health information.
Our record: /security-compliance-controls/164-312-b/. 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(c)(1) — HIPAA Security Rule (45 CFR part 164, subpart C) — Technical safeguards.
(c)(1) Standard: Integrity. Implement policies and procedures to protect electronic protected health information from improper alteration or destruction.
Our record: /security-compliance-controls/164-312-c-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(c)(2) — HIPAA Security Rule (45 CFR part 164, subpart C) — Technical safeguards.
(2) Implementation specification: Mechanism to authenticate electronic protected health information (Addressable). Implement electronic mechanisms to corroborate that electronic protected health information has not been altered or destroyed in an unauthorized manner.
Our record: /security-compliance-controls/164-312-c-2/. 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(d) — HIPAA Security Rule (45 CFR part 164, subpart C) — Technical safeguards.
(d) Standard: Person or entity authentication. Implement procedures to verify that a person or entity seeking access to electronic protected health information is the one claimed.
Our record: /security-compliance-controls/164-312-d/. 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)(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)(i) — HIPAA Security Rule (45 CFR part 164, subpart C) — Technical safeguards.
(i) Integrity controls (Addressable). Implement security measures to ensure that electronically transmitted electronic protected health information is not improperly modified without detection until disposed of.
Our record: /security-compliance-controls/164-312-e-2-i/. 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.
That is the whole of it. Every list of HIPAA software requirements longer than this is somebody's interpretation of these sentences, which may be good advice and is not the rule.
What the rule does not say
Not one of these provisions names a technology, an algorithm, a key length, a timeout, a password rule or a product.
Checked, not asserted: none of AES, SHA, TLS, HTTPS, password, minutes, key length, multi-factor appears anywhere in the thirteen provisions we hold of the technical safeguards. 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.
That is deliberate on the regulator's part: the section is written to outlast the technology. It is also why a developer who asks "what does HIPAA require" and gets an answer full of cipher suites is being told about somebody's implementation, not about the rule. Where a number is genuinely needed, the usual source is NIST SP 800-53, which we also hold, and the choice to use it is yours and not the rule's.
The technical safeguards set no retention period for anything.
Checked, not asserted: none of retain, retention, years appears anywhere in the thirteen provisions we hold of the technical safeguards. 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.
The six-year clock people attach to HIPAA is in a different section, and it runs on documentation the subpart requires rather than on system logs. It is quoted on the logging page.
The same answer for a machine
- Each provision as a record — the same sentences as data, each with its own page and quote.
- Ask by component instead — the provisions bearing on a database, a log store, a login screen or a backup.
The other questions answered here
Does HIPAA apply to my app?, Does HIPAA require encryption at rest, and which algorithm?, 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.