Reference Source

What must I log for HIPAA, and how long must records be kept?

Published .

Two different questions get mixed together here, and the answers come from different sections. What to log is the audit controls standard and the activity review specification. How long to keep records is the documentation section, and the thing it puts a clock on is not your logs.

The answer, in the publisher's own words

What the rule says about logging. Note what it requires: mechanisms that record and examine activity. It does not enumerate events.

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.

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-b/. Quoted from <https://www.ecfr.gov/api/versioner/v1/full/2026-11-01/title-45.xml?part=164&section=164.312>, last checked 2026-11-15, due to be re-checked by 2026-12-15.

164.308(a)(1)(ii)(D) — HIPAA Security Rule (45 CFR part 164, subpart C) — Administrative safeguards.

(D) Information system activity review (Required). Implement procedures to regularly review records of information system activity, such as audit logs, access reports, and security incident tracking reports.

The same source names the document and the control this provision sits in, which is how the citation above is put together:

§ 164.308 Administrative safeguards.

Our record: /security-compliance-controls/164-308-a-1-ii-d/. Quoted from <https://www.ecfr.gov/api/versioner/v1/full/2026-11-01/title-45.xml?part=164&section=164.308>, last checked 2026-11-15, due to be re-checked by 2026-12-15.

The retention period everybody quotes is here, and it binds the documentation the subpart requires: policies, procedures, and records of actions, activities and assessments.

164.316(b)(1) — HIPAA Security Rule (45 CFR part 164, subpart C) — Policies and procedures and documentation requirements.

(b)(1) Standard: Documentation. (i) Maintain the policies and procedures implemented to comply with this subpart in written (which may be electronic) form; and

The same source names the document and the control this provision sits in, which is how the citation above is put together:

§ 164.316 Policies and procedures and documentation requirements.

Our record: /security-compliance-controls/164-316-b-1/. Quoted from <https://www.ecfr.gov/api/versioner/v1/full/2026-11-01/title-45.xml?part=164&section=164.316>, last checked 2026-11-15, due to be re-checked by 2026-12-15.

164.316(b)(1)(ii) — HIPAA Security Rule (45 CFR part 164, subpart C) — Policies and procedures and documentation requirements.

(ii) If an action, activity or assessment is required by this subpart to be documented, maintain a written (which may be electronic) record of the action, activity, or assessment.

Our record: /security-compliance-controls/164-316-b-1-ii/. Quoted from <https://www.ecfr.gov/api/versioner/v1/full/2026-11-01/title-45.xml?part=164&section=164.316>, last checked 2026-11-15, due to be re-checked by 2026-12-15.

164.316(b)(2)(i) — HIPAA Security Rule (45 CFR part 164, subpart C) — Policies and procedures and documentation requirements.

(i) Time limit (Required). Retain the documentation required by paragraph (b)(1) of this section for 6 years from the date of its creation or the date when it last was in effect, whichever is later.

Our record: /security-compliance-controls/164-316-b-2-i/. Quoted from <https://www.ecfr.gov/api/versioner/v1/full/2026-11-01/title-45.xml?part=164&section=164.316>, last checked 2026-11-15, due to be re-checked by 2026-12-15.

The same obligation read as a retention rule, in our record of federal retention periods, which states what starts the clock.

45 CFR 164.316.

(i) Maintain the policies and procedures implemented to comply with this subpart in written (which may be electronic) form; and (ii) If an action, activity or assessment is required by this subpart to be documented, maintain a written (which may be electronic) record of the action, activity, or assessment. (2) Implementation specifications: (i) Time limit (Required). Retain the documentation required by paragraph (b)(1) of this section for 6 years from the date of its creation or the date when it last was in effect, whichever is later.

Our record: /record-retention-periods-federal/policies-and-procedures-implemented-to-comply-with-this-subpart-and-written-reco/. Quoted from <https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-C/part-164/subpart-C/section-164.316>, last checked 2026-11-15, due to be re-checked by 2027-11-15.

If you want a published control that tells you to decide an event list and a retention period deliberately, that is NIST SP 800-53. The bracketed words are the values the catalogue says the organisation defines — which is to say, the number is yours to set and to be able to defend.

AU-2a — NIST SP 800-53 Rev 5.2.0 — Event Logging.

As the catalogue's own rendering reads, with each value the organisation defines in square brackets:

Identify the types of events that the system is capable of logging in support of the audit function: [Assignment: organization-defined event types];

The same provision in the publisher's machine-readable text, which is this record's evidence and prints a placeholder where that value goes:

Identify the types of events that the system is capable of logging in support of the audit function: {{ insert: param, au-02_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": "au-2", "class": "SP800-53", "title": "Event Logging",

"id": "au", "class": "family", "title": "Audit and Accountability",

Our record: /security-compliance-controls/au-2a/. 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.

AU-6a — NIST SP 800-53 Rev 5.2.0 — Audit Record Review, Analysis, and Reporting.

As the catalogue's own rendering reads, with each value the organisation defines in square brackets:

Review and analyze system audit records [Assignment: organization-defined frequency] for indications of [Assignment: organization-defined inappropriate or unusual activity] and the potential impact of the inappropriate or unusual activity;

The same provision in the publisher's machine-readable text, which is this record's evidence and prints a placeholder where that value goes:

Review and analyze system audit records {{ insert: param, au-06_odp.01 }} for indications of {{ insert: param, au-06_odp.02 }} and the potential impact of the inappropriate or unusual activity;

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": "au-6", "class": "SP800-53", "title": "Audit Record Review, Analysis, and Reporting",

"id": "au", "class": "family", "title": "Audit and Accountability",

Our record: /security-compliance-controls/au-6a/. 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.

AU-11 — NIST SP 800-53 Rev 5.2.0 — Audit Record Retention.

As the catalogue's own rendering reads, with each value the organisation defines in square brackets:

Retain audit records for [Assignment: organization-defined time period] to provide support for after-the-fact investigations of incidents and to meet regulatory and organizational information retention requirements.

The same provision in the publisher's machine-readable text, which is this record's evidence and prints a placeholder where that value goes:

Retain audit records for {{ insert: param, au-11_odp }} to provide support for after-the-fact investigations of incidents and to meet regulatory and organizational information retention requirements.

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": "au-11", "class": "SP800-53", "title": "Audit Record Retention",

"id": "au", "class": "family", "title": "Audit and Accountability",

Our record: /security-compliance-controls/au-11/. 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 technical safeguards set no retention period for audit logs, name no events that must be logged, and set no review frequency.

Checked, not asserted: none of retain, retention, years, daily, weekly, monthly 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.

A log retention figure in a vendor's HIPAA checklist is either that vendor's choice, a borrowing from NIST, or a conflation with the documentation clock quoted above. All three are reasonable things to do and none of them is the rule.

The same answer for a machine

The other questions answered here

Does HIPAA apply to my app?, What does HIPAA require software to do?, Does HIPAA require encryption at rest, and which algorithm?, 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.