What HIPAA requires for passwords
HIPAA asks for password procedures but sets no length, character rule or change schedule. NIST SP 800-63B-4 asks for 15 characters, or 8 with MFA.
HIPAA’s Security Rule asks you to have procedures for creating, changing and safeguarding passwords. It doesn’t say how long a password must be, which characters it needs, or how often to change it. Those numbers go in your own policy. The most detailed federal guidance, NIST SP 800-63B-4, asks for at least 15 characters when the password is the only check. It allows 8 when the sign-in also uses multi-factor authentication (MFA: a second check after the password, such as an app code). See What is two-step verification? for how the second check works.
What the Security Rule says
The rule is Subpart C of 45 CFR Part 164. The word “password” appears in only two of its sections. Section 164.304 defines it as confidential authentication information made of a string of characters. The other is 164.308(a)(5)(ii)(D), “Password management (Addressable),” which calls for “Procedures for creating, changing, and safeguarding passwords.”
That specification sits under 164.308(a)(5), security awareness and training. So the rule treats passwords mainly as something your staff are trained to handle. OCR’s audit protocol shows what an auditor may look for here. The list covers staff roles in handling passwords, how passwords should be created, changed and safeguarded, and what to do when one is compromised. Auditors also check that the right people were trained.
Addressable doesn’t mean optional. Under 164.306(d)(3), you assess whether the specification is reasonable and appropriate for your practice. If it is, you implement it. If it isn’t, you document why and implement an equivalent alternative where that is reasonable and appropriate. More on the labels is in What is the HIPAA Security Rule?
Other rules that shape how passwords are used
Three more provisions affect passwords without using the word.
| Provision | Label | What it means for passwords |
|---|---|---|
| 164.312(a)(2)(i) Unique user identification | Required | Each user gets their own name or number, so one password per person, not per team |
| 164.312(d) Person or entity authentication | Standard, no method named | You verify that whoever signs in is who they claim to be; a password is one way |
| 164.308(a)(5)(ii)(C) Log-in monitoring | Addressable | Procedures for watching sign-in attempts and reporting problems |
NIST SP 800-66r2 is NIST’s resource guide to the Security Rule. Under person or entity authentication, it asks whether passwords are unique to the individual. It also asks whether they’re long and strong enough to protect ePHI (patient health information kept electronically), and whether technical settings enforce that. Under training, it asks whether your policies prohibit staff from sharing passwords.
Where the numbers come from
Since HIPAA gives no figures, you take them from guidance. NIST SP 800-63B-4, finalized in July 2025, gives the most detail. Its scope is people signing in to government systems, so it doesn’t bind a private practice. NIST’s HIPAA resource guide points to SP 800-63B for authentication, though it cites the edition before -4. Section 3.1.1.2 of SP 800-63B-4 sets these rules for the system that checks passwords:
- At least 15 characters when the password is the only factor, and at least 8 when it’s part of MFA.
- Allowing passwords of at least 64 characters is recommended, not required.
- No composition rules, such as requiring a mix of letters, numbers and symbols.
- Check each new password against a blocklist of common or breached passwords.
HICP is a set of recommended practices for health care that HHS publishes with industry through its 405(d) program. The 2023 volume for small practices says to give each user a separate account, remind staff not to share passwords, and use work passwords that differ from personal ones. The volume for larger organizations recommends passphrases with a minimum of 8 characters and up to 64 allowed. It also recommends denylists and limits on how fast someone can retry. That volume cites NIST’s June 2017 edition, which came before the 15-character minimum for passwords used alone. A side-by-side of NIST, CISA and PCI DSS numbers is in How long should a password be?
Scheduled changes
The rule asks for procedures for “changing” passwords. That word sets no schedule. A 90-day rule in your policy is your choice, not HIPAA’s. NIST SP 800-63B-4 says verifiers shall not require periodic changes, and shall force a change when there’s evidence of compromise. OCR’s audit protocol also asks what you do when a password is compromised. So a written answer to “what triggers a change?” covers both. The reasoning behind dropping scheduled changes is in Do passwords still need to be changed every 90 days?
What HHS has proposed
In January 2025, HHS proposed amendments to the Security Rule (90 FR 898). Proposed 164.312(f)(2)(i) would require technical controls that make users adopt unique passwords “consistent with the current recommendations of authoritative sources.” The same proposal would require MFA at proposed 164.312(f)(2)(ii). It hasn’t been finalized. The federal regulatory agenda lists a projected final action date of July 2027. Unless a final rule is published, password management stays addressable, with no figures in the rule.
Passwords on shared logins
The figures above assume one password belongs to one person. On a login several staff share, a 15-character password is known to all of them. When one leaves, they still know it, so you change it and give the new one to everyone else. Each change means every remaining person learns a new long password. Unique user identification is the required piece, and a shared login can’t meet it (Can staff share an EHR login?). What else to close when someone leaves is in Which accounts to close when someone leaves a medical practice, and how fast.
Frequently asked questions
Does HIPAA require changing passwords every 90 days?
No. The rule asks for procedures for changing passwords but sets no schedule. NIST SP 800-63B-4 says not to force scheduled changes, and to require a change when there's evidence a password was compromised.
How long does a password have to be under HIPAA?
The rule gives no length. NIST SP 800-63B-4 asks for at least 15 characters when the password is the only factor, and 8 when a second factor is used.
Is password management optional because it's addressable?
No. You assess whether it fits your practice. If it does, you implement it. If not, you document why and use an equivalent measure where that is reasonable.
Can staff share one login if the password is strong?
Strength doesn't fix sharing. Unique user identification is required, so each user needs their own name or number. A shared login can't show which person used it.
How Junify handles this
- Doing this by hand
- You give every clinician and staff member their own login, open and close access for each per-diem shift and vendor staff change, and keep a record of who used which system and when for someone to review.
- With Junify
- When several staff share an EHR or portal login, every departure means a new long password that everyone who stays has to learn. With Junify, your admin changes the password once and adds it to Junify. Staff verify on their own phone and click to sign in, and Junify fills in the password, so nobody has to remember or type it. When someone leaves, the admin removes their assignment instead of changing the password.
Sources
- eCFR: 45 CFR Part 164, Subpart C, Security Standards for the Protection of Electronic Protected Health Information
- eCFR: 45 CFR 164.308, Administrative safeguards
- eCFR: 45 CFR 164.306, Security standards: General rules
- eCFR: 45 CFR 164.312, Technical safeguards
- HHS OCR: Audit Protocol (updated July 2018)
- NIST SP 800-66r2, Implementing the HIPAA Security Rule: A Cybersecurity Resource Guide (February 2024)
- NIST SP 800-63B-4, Digital Identity Guidelines: Authentication and Authenticator Management, section 3 (Authenticator and verifier requirements)
- NIST CSRC: SP 800-63B-4 (final), publication details
- HHS 405(d): HICP Technical Volume 1, Cybersecurity Practices for Small Healthcare Organizations (2023 Edition)
- HHS 405(d): HICP Technical Volume 2, Cybersecurity Practices for Medium and Large Healthcare Organizations (2023 Edition)
- Federal Register: HIPAA Security Rule To Strengthen the Cybersecurity of Electronic Protected Health Information (proposed rule, 90 FR 898, January 6, 2025)
- Reginfo.gov: Unified Agenda entry for RIN 0945-AA22
-
Can staff use personal devices to access clinical systems?
HIPAA allows it with safeguards. Treat each personal laptop or phone as a workstation, write a device policy, and protect both the device and the login.
-
Who is responsible for user accounts in your practice's cloud software?
The vendor secures its service. Your practice decides who gets a login and removes it when they leave. HHS says to sign a BAA and put the split in writing.
-
The HHS cybersecurity performance goals for accounts and logins
Four of HHS's 10 essential goals cover logins: MFA, revoking departing staff's access, unique credentials and separate admin accounts. HHS calls them voluntary.