Reference Source

Do I need multi-factor sign-in, and under which rule?

Published .

If multi-factor sign-in has been described to you as a HIPAA requirement, the rule does not contain the words. What it requires is a procedure to verify that whoever is asking for the data is who they claim to be. The requirement that does name multi-factor authentication is NIST's, and it names it twice, for two different classes of account.

The answer, in the publisher's own words

What HIPAA requires about authentication, in full. One standard, no implementation specifications under it.

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.

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-d/. 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.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&section=164.312>, last checked 2026-11-15, due to be re-checked by 2026-12-15.

The nearest the rule comes to a second factor is an Addressable administrative specification about watching sign-ins.

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

(C) Log-in monitoring (Addressable). Procedures for monitoring log-in attempts and reporting discrepancies.

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-5-ii-c/. 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.

NIST SP 800-53 is where the requirement is explicit, and it is split by account type — which is the distinction that decides what you actually have to build.

IA-2(1) — NIST SP 800-53 Rev 5.2.0 — Multi-factor Authentication to Privileged Accounts.

Implement multi-factor authentication for access to privileged accounts.

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": "ia-2.1", "class": "SP800-53-enhancement", "title": "Multi-factor Authentication to Privileged Accounts",

"id": "ia", "class": "family", "title": "Identification and Authentication",

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

IA-2(2) — NIST SP 800-53 Rev 5.2.0 — Multi-factor Authentication to Non-privileged Accounts.

Implement multi-factor authentication for access to non-privileged accounts.

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": "ia-2.2", "class": "SP800-53-enhancement", "title": "Multi-factor Authentication to Non-privileged Accounts",

"id": "ia", "class": "family", "title": "Identification and Authentication",

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

IA-2(6)(a) — NIST SP 800-53 Rev 5.2.0 — Access to Accounts —separate Device.

One of the factors is provided by a device separate from the system gaining access; 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": "ia-2.6", "class": "SP800-53-enhancement", "title": "Access to Accounts —separate Device",

"id": "ia", "class": "family", "title": "Identification and Authentication",

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

IA-2(6)(b) — NIST SP 800-53 Rev 5.2.0 — Access to Accounts —separate Device.

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

The device meets [Assignment: organization-defined strength of mechanism 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:

The device meets {{ insert: param, ia-02.06_odp.03 }}.

Our record: /security-compliance-controls/ia-2-6-b/. 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.

Those are control enhancements, which means they apply when a baseline or a contract selects them. The catalogue states the obligation; what selects it for your system is your own control baseline, a customer's contract, or a framework somebody has committed you to.

What the rule does not say

The HIPAA Security Rule never says multi-factor, two-factor, MFA, or one-time code. Not once, in any provision we hold.

Checked, not asserted: none of multi-factor, multifactor, two-factor, MFA, one-time, second factor, authenticator app 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.

This is not an argument against multi-factor sign-in, which is among the cheapest real improvements available to most applications. It is an argument against citing the wrong authority for it: if you tell a customer HIPAA requires it and they read the rule, you have spent credibility you did not need to spend. NIST's control, quoted above, is the citation that holds up.

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 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?, 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.