"HIPAA requires you to keep audit logs for six years."
What the HIPAA Security Rule asks of your audit logs: record and examine activity in systems with ePHI, and review it regularly. It sets no log retention period; six years applies to documentation. nano runs in your environment, so logs that carry PHI never reach nano.
The regulation's own words, what they mean in practice, and where nano fits.
Binding on covered entities and business associates.
| Ref | What the rule says | In plain English | How nano helps |
|---|---|---|---|
| 164.312(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." ecfr.gov · 45 CFR 164 | Record what happens in systems that hold ePHI, and look at it. The rule does not list which events or how long to keep them. | Collects activity logs from the systems you choose (EHR, identity, endpoints, network) into one store in your environment, and runs detections on them as they arrive. |
| 164.308(a)(1)(ii)(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." ecfr.gov · 45 CFR 164 | Review audit logs and access reports regularly. How often is for your risk analysis to decide. | Turn the review into scheduled reports and saved searches, and keep findings as cases with their evidence. |
| 164.308(a)(5)(ii)(C) | "Log-in monitoring (Addressable)." ecfr.gov · 45 CFR 164 | Monitor log-in attempts. The rule marks this specification addressable. | Sign-in events from your identity provider, VPN and servers in one place, with detections for the patterns you care about. |
| 164.316(b)(2)(i) | "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." ecfr.gov · 45 CFR 164 | Six years for documentation: your policies, procedures and records of required actions. Not a retention period for raw logs. | Keep the records that document your reviews (reports, case notes) for as long as your documentation rule says. Raw log retention is your setting. |
| Ref | What the rule says | In plain English | How nano helps |
|---|---|---|---|
| 164.404(b), 164.410(b) | "…without unreasonable delay and in no case later than 60 calendar days after discovery of a breach." ecfr.gov · 45 CFR 164 | Individuals hear from the covered entity within 60 days of discovery. A business associate owes the covered entity notice on the same clock. | Logs show what was accessed, by whom and when, which is what the notice draws on. Notification stays with you. |
Run activity reviews with scheduled reports, keep findings and evidence in case management, and set retention in storage and retention.
Many guides say HIPAA requires audit logs to be kept for six years, citing 164.316(b)(2). That section is about documentation.
"HIPAA requires you to keep audit logs for six years."
"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."
"Implement hardware, software, and/or procedural mechanisms that record and examine activity in information systems that contain or use electronic protected health information." No log retention period is set.
Base log retention on your risk analysis, how far back investigations and breach assessments need to look, and any state or contract rules. Write it down.
One defensible design: the reports and case notes that document required actions, such as activity reviews, are kept for as long as the documentation itself.
Event retention defaults to 365 days and you can set it longer. Tier older events to your own object storage, where they stay searchable. Storage and retention
Security logs can contain ePHI, such as patient names or record numbers in file paths, queries and email subjects. A SaaS SIEM that ingests them is a business associate. A SIEM you run yourself is not acting as one for that data.
Your data center, your own cloud account, or an air-gapped network
Never receives your logs.
The clock starts at discovery. Working out what was accessed, and whose records, depends on the logs you already keep.
The day the breach is discovered starts the clock.
Notification is due without unreasonable delay; 60 days is the outer limit, not a target.
In no case later than 60 calendar days after discovery. Business associates owe the covered entity notice on the same clock.
HHS has proposed a stronger Security Rule. As of November 2026 it is a proposal only: no final rule, and no withdrawal.
HHS proposes a stronger Security Rule (RIN 0945-AA22, Federal Register 2024-30983).
federalregister.gov · 2024-30983 ↗No final rule and no withdrawal as of November 2026.
federalregister.gov · 2024-30983 ↗The Unified Agenda lists it under Long-Term Actions, with final action targeted for July 2027. Until then, the current Security Rule applies.
federalregister.gov · 2024-30983 ↗Section 164.312(b), the audit controls standard of the HIPAA Security Rule, requires covered entities and business associates to "Implement hardware, software, and/or procedural mechanisms that record and examine activity in information systems that contain or use electronic protected health information." Section 164.308(a)(1)(ii)(D) adds a required procedure to regularly review records of information system activity, such as audit logs and access reports.
No. The six-year rule is 164.316(b)(2)(i), which requires the documentation required by 164.316(b)(1), such as policies, procedures and records of required actions, to be kept for 6 years from creation or from when it was last in effect. It is not a retention period for raw audit logs, and the Security Rule sets none.
Long enough to support your risk analysis, investigations and breach assessments, as set in your own policy. One defensible approach: keep the logs and reports that document required actions, such as your activity reviews, for as long as the documentation itself (six years), and keep raw logs for a period your policy sets and justifies. With nano, retention is a setting on storage you own, and older data can be tiered to your own object storage.
The Security Rule says to review records of information system activity "regularly" and does not set a frequency. Pick one that fits your risk analysis, write it down, and keep evidence that the reviews happen.
No. HHS published a proposed rule on 6 January 2025 (RIN 0945-AA22), and comments closed on 7 March 2025. There is no final rule and no withdrawal; the Unified Agenda targets final action for July 2027. Until a final rule is published and takes effect, the current Security Rule applies.
A SaaS SIEM that ingests logs containing ePHI is a business associate of the covered entity, with a business associate agreement, its own Security Rule duties and a breach notice duty back to the covered entity under 164.410. Security logs can contain ePHI, such as patient names or record numbers in file paths, queries and email subjects.
For log data, nano is not acting as your business associate. You run nano in your own environment, so nano does not create, receive, maintain or transmit PHI in your logs, and nano has no standing access to your install. Support sees only what you choose to share. A connected install sends nano a daily license check-in and one usage number per day; air-gapped installs send nothing. AI is off by default and, when on, calls your own model endpoint, never nano. If your support cases may include PHI, nano will sign a business associate agreement.
No. nano holds no HIPAA certification (there is none), and no product makes you compliant with HIPAA. It is the SIEM you run to record and examine activity in your systems, as 164.312(b) asks, with the evidence kept in your environment.
Last reviewed 13 November 2026. Regulations and guidance change, so read the current version at the source.
From US$149/month at 5 GB/day, US$279/month at 10 GB/day (list price, billed monthly; 10% off billed annually). Every feature in one license, and one license covers two installs.