Password Management: Password management under current NIST guidance

Auditors ask about password management early, because the answer tells them how the rest of the program is likely to look. The requirement is 45 CFR 164.308(a)(5)(ii)(D).

What the rule says

Password management (Addressable). Procedures for creating, changing, and safeguarding passwords.

That is the text of 45 CFR 164.308(a)(5)(ii)(D). Read it closely: it describes an outcome to achieve, not a product to buy, which is why two practices of the same size can satisfy it in different ways and both be right.

This is an addressable implementation specification, and addressable does not mean optional. Under 45 CFR 164.306(d)(3) you assess whether the specification is reasonable and appropriate in your environment, and then either implement it or, if implementing it is not reasonable and appropriate, document why and implement an equivalent alternative measure if that is reasonable and appropriate. The documented reasoning is itself part of the requirement, so an undocumented decision to skip it is the finding.

The Security Rule sets no password length or rotation rule; § 164.308(a)(5)(ii)(D) asks for "Procedures for creating, changing, and safeguarding passwords." The settings below are NIST SP 800-63B-4's, voluntary guidance.

What this looks like in practice

In an assessment, 45 CFR 164.308(a)(5)(ii)(D) is not one question. It resolves into several, and each one is really asking for different evidence. These are among the questions asked about it:

• Do the organization's directory services and applications enforce long passwords (at least 15 characters where a password is the only factor), block known-breached passwords, and drop forced periodic password changes?
• Does the organization govern the allocation, storage, and handling of authentication information such as passwords, keys, and tokens, or, where it has determined that this safeguard is not reasonable and appropriate, documented that determination and implemented an equivalent alternative measure (45 CFR 164.306(d)(3))?
• Does the organization change or disable default accounts and default credentials on its assets and software?

Ownership usually sits with the IT or security team, though the evidence is often produced by someone else, which is where the trail breaks. A control that works but has no owner tends to stop working the month the person who quietly maintained it changes roles.

Who this applies to

Every covered entity and every business associate, at any size. 45 CFR 164.306(b) allows flexibility of approach, so a two-provider practice and a hospital system may implement this differently and both comply. What flexibility does not allow is skipping the decision: the smaller the organization, the more the written reasoning carries the weight, because there is no scale of operation to make the control self-evident.

Building it, in order

These steps are one way to meet it, drawn from our question bank. Unless a step names a provision, the Security Rule does not require that particular measure: 45 CFR 164.306(b)(1) lets you use any security measures that allow you to reasonably and appropriately implement the standards and implementation specifications, chosen with the factors in 45 CFR 164.306(b)(2).

The sequence below is the order that produces evidence as a by-product rather than as a separate documentation exercise:

1. Set a minimum password length of at least 15 characters where a password is the only factor and at least 8 where it is one factor of multi-factor authentication (NIST SP 800-63B-4), and favor longer passphrases.
2. Screen new and changed passwords against known-breached-password lists and block matches.
3. Remove mandatory periodic rotation, requiring a reset only when compromise is detected.
4. Apply these settings consistently across directory services and application authentication systems. Record how the measure chosen meets the cited provision. 45 CFR 164.306(b)(1) lets the organization use any security measures that allow it to reasonably and appropriately implement the standards and implementation specifications, and the Security Rule does not name this practice. The cited standard and any Required implementation specification must be met. An Addressable one must be implemented, or the organization documents why it is not reasonable and appropriate and implements an equivalent alternative measure if that is reasonable and appropriate (45 CFR 164.306(d)(3)). Choose the measure with the factors in 45 CFR 164.306(b)(2) and document it with the risk analysis.
5. Define how authentication secrets are issued, distributed, stored, rotated, and revoked.
6. Require secrets to be stored using approved protection such as hashing or a managed secrets vault.

Where else this maps

The questions behind 45 CFR 164.308(a)(5)(ii)(D) also map to HHS 405(d) HICP (2023 Edition) CSP 2, CSP 3, CSP 4 and NIST SP 800-66 Rev. 2 5.1.5, 5.2.4, 5.3.1, which are voluntary guidance rather than law; following them does not by itself establish compliance with any law. That matters for scoping: the same evidence can be written once and referenced from each, rather than rewritten per framework.

Evidence an assessor asks for

For this requirement the evidence types that satisfy it are configuration, inventory, policy, and report. The distinction matters more than it looks: a policy states what you intend to do, a procedure states how, and a record proves it happened on a date. Auditors ask for all three, and a practice that has written the first two often has nothing for the third.

Date every document and keep the superseded versions. 45 CFR 164.316(b)(2)(i) requires the documentation 164.316(b)(1) calls for (the Security Rule policies and procedures, and the written record of any action, activity or assessment the Security Rule requires to be documented) to be retained for six years from the date of its creation or the date when it last was in effect, whichever is later, so a policy you replaced two years ago is still part of the record.

Where this usually goes wrong

The most common failure here is treating addressable as optional. A practice decides the specification does not fit, implements nothing, and writes nothing down. At assessment the answer to "why not" is a verbal explanation, which is not evidence. The second most common failure is the opposite: implementing an alternative that works, and still not recording the reasoning, so the control looks accidental.

What to do about it

• Produce the evidence, not the intention. For 45 CFR 164.308(a)(5)(ii)(D) that means a configuration export or screenshot showing the setting live, dated, an inventory with an owner and a last-reviewed date on every row, a signed, dated policy with a named owner and a review date, and a dated report with the period it covers and who reviewed it. If the only evidence is that someone knows how this works, you have a practice and not a record.
• Put a name on it. Whoever administers the systems should be recorded as the owner. Where the work is done by someone else, say so in the document: the split between who owns it and who performs it is where the trail usually breaks. A control with no owner stops working the month the person who quietly maintained it changes roles, and nobody notices.
• Set a review cadence and keep the evidence of each review. An annual date with a dated output is a common floor; what fails an assessment is a control implemented once and never re-checked against a changed environment.
• If you decide not to implement it, write the decision down. Addressable is not optional: under 45 CFR 164.306(d)(3) the documented assessment IS part of the requirement, so an undocumented decision to skip it is the finding, and a working alternative with no recorded reasoning looks accidental.

The practical test for 45 CFR 164.308(a)(5)(ii)(D) is whether someone unfamiliar with your organization could read your documentation and tell what you do, who does it, and when it last happened. If they can, the documentation will hold up; whether the requirement is met is a judgment about what it shows, and your counsel owns that conclusion. If they need you in the room to explain it, it will not.

Related requirements

• Log-in Monitoring: Log-in monitoring and reporting discrepancies
• Security Incident Procedures: Incident procedures before you need them
• Protection from Malicious Software: Malware protection on clinical endpoints

References

• 45 CFR 164.308(a)(5)(ii)(D), in 45 CFR 164.308 on eCFR. Quoted text verified against the eCFR text current as of 2026-10-06.
• The Required and Addressable designations are defined at 45 CFR 164.306(d).
• Crosswalk references in this post are the mappings in our question bank, and are not verified against the published text of those standards.
• This post describes what a requirement asks for and what evidence documents it. It is not legal advice, and your counsel owns the conclusion. State law may impose additional obligations; HIPAA preempts a State law only where it is contrary to HIPAA (45 CFR 160.202, 160.203).