A forced password change at the end of a quarter can fill the helpdesk with tickets about locked accounts while doing nothing to strengthen the password itself. Some people set a new password and a few days later can no longer remember it. Others remember it perfectly well, because they turned “Company2026!” into “Company2026!!”, and in three months they will add a third exclamation mark. The password policy is satisfied, the audit report will be clean, and the password has not become any harder to guess.
A forced change every quarter, eight characters and a mandatory digit form one of the most persistent legends of corporate cybersecurity. In its SP 800-63B guidelines of July 2025, the US National Institute of Standards and Technology (NIST) prohibits both periodic changes and password composition rules, and CERT Polska, the Polish national CSIRT, has advised against them in its recommendations since 2022. A password policy can ask less of the user and more of the system that checks passwords: length, a blocklist, attempt limits and a response to breaches.
Where did the 30-day password change come from in Polish companies?
In Poland, the monthly change and the mix of character types have a specific legal origin that is no longer in force. The Polish Interior Ministry regulation of 29 April 2004 (in Polish) on personal data processing documentation required, at the basic security level, that a password be changed “no less often than every 30 days” and have at least 6 characters. At the elevated level, the same regulation demanded at least 8 characters, lower- and upper-case letters, and digits or special characters.
For years, this set of rules made its way into IT system management instructions, then into policy templates, and from templates into Active Directory and application settings. According to the Polish Parliament’s legal acts database, the regulation has the status “deemed repealed”, and the database gives 6 February 2019 as the date of repeal. System configuration can outlive the rule that once justified it.
Since 25 May 2018, personal data protection has been governed by the GDPR, which sets no password parameters at all. Article 32(1) requires controllers and processors to implement technical and organisational measures that ensure a level of security appropriate to the risk. How long passwords should be, and whether they should expire, is therefore the organisation’s choice, and the organisation must be able to justify it. Legal status as of 21 October 2026. Outside Poland, local law or sector regulation may add its own requirements, so check them before you rewrite the policy.
What does NIST SP 800-63B Revision 4 change?
Revision 4 shifts the weight of password policy from rules for the user to obligations for the system that accepts and checks passwords. According to the publication page on CSRC, NIST SP 800-63B-4 was published in final form on 31 July 2025 and superseded the previous SP 800-63B edition of 2 March 2020. The page lists no document that supersedes Revision 4.
The document covers authentication in US federal government systems, but the publication itself notes that non-governmental organisations may use it on a voluntary basis. For a European company it is therefore a reference point, not a regulation. That is enough, because a policy is easier to justify to an auditor or a board on the basis of a recognised standard than on the basis of habit.
The password requirements are gathered in Section 3.1.1.2. NIST uses two levels there: “SHALL” means a requirement and “SHOULD” a recommendation. It is worth carrying that distinction into your own policy, because otherwise every recommendation starts to sound like a hard prohibition.
How long should a password be under NIST?
A password that is the only login factor must be at least 15 characters long. That is the first item of Section 3.1.1.2: verifiers and credential service providers “SHALL” require that length for passwords used as a single-factor authentication mechanism. A password used only as part of multi-factor authentication may be shorter, but it must still have at least 8 characters.
The upper limit works the other way round. NIST recommends that systems accept passwords of at least 64 characters, all printing ASCII characters and the space character, as well as Unicode characters, with each Unicode code point counted as a single character. In practice, this means allowing passphrases, national characters and long random strings from a password manager.
When you define what a password is in the policy, separate two categories of account straight away. An account that signs in with a password alone, such as an old application without a second factor, needs a different minimum from an account protected by MFA. A single number for the whole organisation is easier to communicate, but it either inflates the requirement for accounts with MFA or understates it for those without.
Why does NIST prohibit periodic password changes?
NIST forbids forcing password changes on a calendar and instead requires a change when the password may have been compromised. The sixth item of Section 3.1.1.2 says it plainly: verifiers “SHALL NOT” require subscribers to change passwords periodically, but they “SHALL” force a change if there is evidence that the authenticator has been compromised.
The logic is simple. A password that has not leaked does not grow weaker with time. A password that has leaked is dangerous from day one, and a calendar-driven change may come weeks later. Quarterly rotation therefore fails to protect against what it was meant to protect against, while teaching people to make small modifications such as an added character or the next year’s digit.
Dropping rotation does not mean a password lives forever without oversight. The policy must describe what counts as a sign of compromise and who responds: an account found in a breach, a user reporting that they entered the password on a fake page, unusual sign-ins. Without such a procedure, removing expiry really does leave a gap.
What replaces the requirement for capitals, digits and special characters?
Composition rules are replaced by a blocklist of banned passwords. The fifth item of Section 3.1.1.2 prohibits other composition rules, for example requiring a mixture of character types. Instead, when a password is set or changed, the verifier “SHALL” compare it against a list of popular, expected or compromised passwords, checking the entire password rather than fragments or words within it.
NIST gives examples of what such a list may contain: passwords from previous breaches, dictionary words and context-specific words, meaning the name of the service, the username and their derivatives. If a password is on the list, the system must require a different one and give the reason for rejection, and it must also help the user choose a stronger password. NIST also notes that very large blocklists add little security, because online guessing is already limited by the throttling requirements.
For systems used by Polish speakers, Polish words and patterns matter. CERT Polska publishes a dictionary of Polish passwords built from an analysis of breaches and points administrators to it as material for exactly this kind of list. Outside Poland, the same principle applies to your own language. Add the names of your company, brands and locations, which are context-specific words in NIST’s sense.
Key points:
- Password as the only factor: at least 15 characters; password used only within MFA: at least 8 characters.
- No periodic changes and no composition rules; a change is mandatory after a sign of compromise.
- A blocklist checked every time a password is set, with the reason for rejection shown to the user.
What other requirements does NIST place on the system that checks passwords?
Section 3.1.1.2 also lists obligations that remove familiar obstacles for users and add protection on the server side. The system must not allow hints that are accessible before sign-in, nor prompt for security questions such as the name of your first pet. It must request the whole password, not selected characters, and verify all of it, without truncation.
The verifier “SHALL” allow password managers and autofill, and “SHOULD” permit paste where autofill does not work. NIST also recommends an option to display the password as it is typed instead of dots. Password managers and vaults, which make long and unique passwords practical, are covered in a separate article on passwordless authentication and password vaults.
Protection against guessing rests with the system. Under Section 3.2.2 of the publication, the verifier limits consecutive failed attempts with one authenticator on a given account to no more than 100, and NIST calls this figure an upper bound that may be lowered. Passwords must be stored as salted hashes, with a salt of at least 32 bits, and NIST recommends raising the computational cost of the hashing scheme over time.
How do the CERT Polska recommendations differ from NIST?
CERT Polska says the same as NIST on the essentials and differs mainly on minimum length. In its recommendations of 10 January 2022, updated in June 2025, the team advises that systems should not force periodic password changes, should not require additional complexity criteria and should not block the paste function. CERT sets the minimum length at no fewer than 14 characters, and a note to the recommendations explains that in June 2025 it raised this from 12 to 14 characters.
The two organisations agree on the maximum (at least 64 characters), checking against a list of weak passwords, giving the reason for rejection and requiring a change after a confirmed or suspected compromise. CERT adds a ban on predictable elements such as the company or service name, and recommends showing a strength meter for the new password. It also names hashing functions for storing passwords: Argon2, bcrypt, PBKDF2 and scrypt.
The one-character difference matters only for passwords without a second factor. An organisation that writes 15 characters into its policy for such accounts satisfies both documents at once. CERT does not set a separate threshold for passwords used within MFA, and simply recommends support for two-factor authentication.
How does a password policy connect with MFA and protection against password spraying?
A password policy and MFA are two parts of one decision, because the second factor determines how short a password NIST allows at all. According to Section 2.2, the AAL2 level requires proof of possession and control of two distinct authentication factors through secure authentication protocols. The 8-character threshold applies only to passwords used solely in such a combination.
An attempt limit protects an individual account, but not always the whole organisation. A password spraying attack tries one popular password across many accounts at once, so on none of them does the failed sign-in counter need to come close to the limit. A blocklist adds protection against such an attack: if the most popular passwords cannot be set, the attacker has nothing to spray.
The password also remains the weakest point wherever there is no second factor: in legacy applications, service accounts and network devices. For these, the policy should name an owner, require the full 15-character length and set out a plan for adding MFA or another form of access control.
How do you rewrite your organisation’s password policy step by step?
Start the change with an inventory of the places where passwords are actually checked, and write the new rules only after that. The Active Directory domain, VPN, email, business applications, device admin panels and cloud services may have separate settings, while the policy document describes only some of them.
The second step is to split accounts into those that sign in with a password alone and those protected by a second factor. This determines the length threshold: 15 or 8 characters. The third step is to switch off expiry and composition rules and switch on the blocklist wherever the system supports it. If a system does not support it, the policy should record that as a risk with an owner and a deadline.
The fourth step is the post-compromise change procedure: where the signals come from, who decides on a reset and how the user is informed. The fifth is a password manager for employees and administrators, because without one, long and unique passwords quickly end up on sticky notes. The sixth is communication: users should hear that passwords no longer expire, but must be longer and must not come from the blocklist.
How can you check whether your current password policy is aligned with NIST?
The quickest way to assess your current policy is to set its provisions against the requirements of both documents and record an action straight away.
| Provision in the old policy | NIST SP 800-63B-4 | CERT Polska | What to do |
|---|---|---|---|
| Password change every month or quarter | Periodic changes prohibited (3.1.1.2 item 6) | Do not force periodic changes | Switch off expiry, describe the post-compromise change |
| Minimum 8 characters for everyone | 15 characters without MFA, 8 only within MFA (item 1) | At least 14 characters | Split thresholds by account type |
| Capitals, a digit, a special character | Composition rules prohibited (item 5) | No additional complexity criteria | Remove the rules, implement a blocklist |
| No blocklist of banned passwords | Checking the entire password required | Reject weak and predictable passwords | Build a list with breaches, dictionary words and company names |
| Security questions for resets | Security questions prohibited (item 8) | Not addressed | Replace with a reset using a second factor |
| Paste blocked in the password field | Password managers mandatory, paste recommended | Do not block paste | Unblock paste, provide a password manager |
| Account lockout after a few attempts with no further rules | Up to 100 consecutive failed attempts (3.2.2) | Not addressed | Set a limit and an unlock procedure |
Any row that the organisation cannot change immediately, for example because of the limitations of a legacy application, should go into the risk register with a justification and a review date. That way, a deviation is a conscious decision rather than an oversight.
How can nFlo help you prepare a password policy?
Within its “Governance, Risk and Compliance” area, nFlo prepares security documentation tailored to a specific organisation. The Security Policy Development service covers a password and MFA policy within the set of detailed policies, technical standards with concrete parameters such as minimum password length, a RACI responsibility matrix, and training on the new rules for the board and employees.
Some of the rules also need a tool. One Identity Password Manager lets users reset their own passwords and unlock their accounts, extends password policies beyond native Active Directory controls, and supports multiple domains and two-factor authentication. nFlo implements it as a project, from requirements analysis to configuration and team training.
If you want to check which provisions of your password policy are worth changing, contact us.
What else is worth knowing about password policy?
Will dropping periodic password changes weaken security?
Not if, in the same step, the organisation introduces what NIST puts in place of rotation: a longer minimum length, checking passwords against a blocklist, a limit on failed attempts and a forced change after every sign of compromise. Removing expiry alone, without those elements, really would leave a gap.
Is NIST SP 800-63B mandatory for a company in Poland or the EU?
No. The guidelines bind US federal agencies, and the publication states explicitly that non-governmental organisations may use them on a voluntary basis. In Poland, neither the GDPR nor the repealed Interior Ministry regulation sets password parameters, so NIST and the CERT Polska recommendations serve as a recognised reference point in risk assessments and audits. Outside Poland, check whether local law or sector rules set their own requirements.
What minimum length should the policy state: 14 or 15 characters?
For passwords that are the only login factor, 15 characters is the safer choice, because it meets both the NIST requirement and the CERT Polska recommendation (at least 14). For passwords used only together with a second factor, NIST allows a minimum of 8 characters.
When must a password change be forced?
Whenever there is evidence or a reasonable suspicion that the password has been compromised or disclosed: it appeared in a breach, the user typed it into a fake page, or the account shows sign-ins from unknown locations. The policy should state who makes that decision and how quickly the user sets a new password.
Is blocking paste in a login form good practice?
No. NIST requires verifiers to allow password managers and autofill and recommends permitting paste, and CERT Polska explicitly advises against blocking the paste function. Blocking paste discourages password managers, which are precisely the tools that make long, unique passwords practical.
