What session timeout do HIPAA and NIST require? Neither names a number
A session timeout is the single most commonly cited HIPAA number, and the rule does not contain it. What the rule requires is a procedure that ends a session after a predetermined time of inactivity: predetermined by you, written down, and defensible. NIST's controls are built the same way — the period is an organisation-defined value, printed in brackets in the catalogue's own rendering.
The answer, in the publisher's own words
The HIPAA provision, in full. It is an Addressable implementation specification of the access control standard.
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.
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-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.
The NIST controls people reach for when they want something more specific. They are not more specific about the number; they are more specific about what you have to decide.
AC-11a — NIST SP 800-53 Rev 5.2.0 — Device Lock.
As the catalogue's own rendering reads, with each value the organisation defines in square brackets:
Prevent further access to the system by [Selection (one or more): initiating a device lock after [Assignment: organization-defined time period] of inactivity; requiring the user to initiate a device lock before leaving the system unattended] ; and
The same provision in the publisher's machine-readable text, which is this record's evidence and prints a placeholder where that value goes:
Prevent further access to the system by {{ insert: param, ac-11_odp.01 }} ; and
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": "ac-11", "class": "SP800-53", "title": "Device Lock",
"id": "ac", "class": "family", "title": "Access Control",
Our record: /security-compliance-controls/ac-11a/. 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.
AC-11b — NIST SP 800-53 Rev 5.2.0 — Device Lock.
Retain the device lock until the user reestablishes access using established identification and authentication procedures.
Our record: /security-compliance-controls/ac-11b/. 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.
AC-12 — NIST SP 800-53 Rev 5.2.0 — Session Termination.
As the catalogue's own rendering reads, with each value the organisation defines in square brackets:
Automatically terminate a user session after [Assignment: organization-defined conditions or trigger events].
The same provision in the publisher's machine-readable text, which is this record's evidence and prints a placeholder where that value goes:
Automatically terminate a user session after {{ insert: param, ac-12_odp }}.
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": "ac-12", "class": "SP800-53", "title": "Session Termination",
"id": "ac", "class": "family", "title": "Access Control",
Our record: /security-compliance-controls/ac-12/. 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.
AC-12(1) — NIST SP 800-53 Rev 5.2.0 — User-initiated Logouts.
As the catalogue's own rendering reads, with each value the organisation defines in square brackets:
Provide a logout capability for user-initiated communications sessions whenever authentication is used to gain access to [Assignment: organization-defined information resources].
The same provision in the publisher's machine-readable text, which is this record's evidence and prints a placeholder where that value goes:
Provide a logout capability for user-initiated communications sessions whenever authentication is used to gain access to {{ insert: param, ac-12.01_odp }}.
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": "ac-12.1", "class": "SP800-53-enhancement", "title": "User-initiated Logouts",
"id": "ac", "class": "family", "title": "Access Control",
Our record: /security-compliance-controls/ac-12-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.
AC-12(3) — NIST SP 800-53 Rev 5.2.0 — Timeout Warning Message.
As the catalogue's own rendering reads, with each value the organisation defines in square brackets:
Display an explicit message to users indicating that the session will end in [Assignment: organization-defined time].
The same provision in the publisher's machine-readable text, which is this record's evidence and prints a placeholder where that value goes:
Display an explicit message to users indicating that the session will end in {{ insert: param, ac-12.03_odp }}.
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": "ac-12.3", "class": "SP800-53-enhancement", "title": "Timeout Warning Message",
"id": "ac", "class": "family", "title": "Access Control",
Our record: /security-compliance-controls/ac-12-3/. 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.
Read those bracketed phrases carefully, because they are the answer: the catalogue prints a placeholder where the value is the organisation's to set, and we print the same sentence with the catalogue's own label for that placeholder in square brackets. A session timeout is a decision you make and record, not a figure you can look up.
What neither rule says
Neither the HIPAA Security Rule nor the session controls of NIST SP 800-53 names a period of time. The words minutes, hours and seconds appear in none of them.
Checked, not asserted: none of minutes, minute, hours, seconds, idle timeout appears anywhere in the twenty provisions we hold of the HIPAA technical safeguards and the NIST session controls. 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.
So where does the familiar figure come from? Usually from a vendor's default, from a trade article, or from a different document borrowed for the purpose. If an auditor asks for your timeout, the thing they can hold you to is that you set one deliberately and wrote down why.
The same answer for a machine
- Authentication and session provisions by component — the provisions bearing on sign-in and sessions, in one call.
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 must I log for HIPAA, and how long must records be kept?, 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.