Reference Source

What password rules does NIST state? IA-5(1) in full

Published .

The catalogue's password control is short, specific and surprising to anyone whose policy still turns on special characters. It is printed in full below, one lettered statement at a time, exactly as the catalogue states it.

The answer, in the publisher's own words

Password-based authentication, every statement of it.

IA-5(1)(a) — NIST SP 800-53 Rev 5.2.0 — Password-based Authentication.

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

Maintain a list of commonly-used, expected, or compromised passwords and update the list [Assignment: organization-defined frequency] and when organizational passwords are suspected to have been compromised directly or indirectly;

The same provision in the publisher's machine-readable text, which is this record's evidence and prints a placeholder where that value goes:

Maintain a list of commonly-used, expected, or compromised passwords and update the list {{ insert: param, ia-05.01_odp.01 }} and when organizational passwords are suspected to have been compromised directly or indirectly;

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-5.1", "class": "SP800-53-enhancement", "title": "Password-based Authentication",

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

Our record: /security-compliance-controls/ia-5-1-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-5(1)(b) — NIST SP 800-53 Rev 5.2.0 — Password-based Authentication.

Verify, when users create or update passwords, that the passwords are not found on the list of commonly-used, expected, or compromised passwords in IA-5(1)(a);

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

IA-5(1)(c) — NIST SP 800-53 Rev 5.2.0 — Password-based Authentication.

Transmit passwords only over cryptographically-protected channels;

Our record: /security-compliance-controls/ia-5-1-c/. 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-5(1)(d) — NIST SP 800-53 Rev 5.2.0 — Password-based Authentication.

Store passwords using an approved salted key derivation function, preferably using a keyed hash;

Our record: /security-compliance-controls/ia-5-1-d/. 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-5(1)(e) — NIST SP 800-53 Rev 5.2.0 — Password-based Authentication.

Require immediate selection of a new password upon account recovery;

Our record: /security-compliance-controls/ia-5-1-e/. 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-5(1)(f) — NIST SP 800-53 Rev 5.2.0 — Password-based Authentication.

Allow user selection of long passwords and passphrases, including spaces and all printable characters;

Our record: /security-compliance-controls/ia-5-1-f/. 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-5(1)(g) — NIST SP 800-53 Rev 5.2.0 — Password-based Authentication.

Employ automated tools to assist the user in selecting strong password authenticators; and

Our record: /security-compliance-controls/ia-5-1-g/. 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-5(1)(h) — NIST SP 800-53 Rev 5.2.0 — Password-based Authentication.

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

Enforce the following composition and complexity rules: [Assignment: organization-defined composition and complexity rules].

The same provision in the publisher's machine-readable text, which is this record's evidence and prints a placeholder where that value goes:

Enforce the following composition and complexity rules: {{ insert: param, ia-05.01_odp.02 }}.

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

The shape of it is worth noticing: the control asks you to check new passwords against a list of known-bad ones, to store them with a salted key derivation function, and to let people choose long passphrases including spaces. Composition and complexity rules are left to the organisation to state, in brackets, rather than specified.

What the control does not say

This control sets no expiry interval and no complexity recipe. It does not say passwords must change every so often, and it names no character classes.

Checked, not asserted: none of expire, expiration, expiry, uppercase, special character, days appears anywhere in the nine provisions we hold of the password-based authentication control. 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.

Where a maximum lifetime exists in the catalogue at all, it is an organisation-defined value on the parent control rather than a figure NIST sets. A ninety-day rotation policy is a choice somebody in your organisation made, and the catalogue neither requires nor forbids it.

What we have not read

NIST's better-known password guidance is SP 800-63B, the digital identity guidelines, and we do not hold it: these records are SP 800-53, the control catalogue. If a claim about NIST and passwords turns on screening against breach corpora, on password length minimums or on hints, check it against 800-63B at its source rather than against this page.

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