Enterprise Password Policy: Dos and Don'ts for IT Teams

Bravura Security Editorial Team

February 16, 2023

Strong enterprise password policy comes down to five rules: length over complexity, no reuse across systems, multi-factor authentication on privileged accounts, rotation driven by risk rather than the calendar, and self-service reset so policy does not become a helpdesk queue. Bravura Pass applies these rules across the systems it connects.

Passwords are still the credential on the systems that matter most in your environment: legacy applications, service accounts, and anything that sits outside single sign-on. A policy that works for cloud apps and fails on the mainframe is not a policy. It is a gap.

This guide gives you the rules that hold up in an enterprise, the ones that create helpdesk tickets, and a table you can hand to your team. It is written for IT and security teams, not for consumers choosing a Netflix password.

Key Takeaway

Password policy fails where it is hardest to enforce, not where it is written. Length, uniqueness, multi-factor authentication on privileged accounts, and risk-based rotation are the rules. Self-service reset with identity verification is what keeps those rules from flooding your helpdesk. Coverage of your legacy systems is what makes them real.

Why Does Password Policy Still Matter in 2026?

Passwordless authentication is the direction, and your policy should move toward it. It is not the whole picture yet. Legacy applications, service accounts, mainframe and AS/400 systems, and non-SSO tools still run on passwords, and they will for years. Credential-based attacks keep targeting those systems because they are the softest entry point. A password policy that covers them is still one of the highest-value controls you own.

Which Attacks Does a Password Policy Have to Stop?

Your policy exists to make these seven attacks fail. Each one targets a different weakness.

  • Brute force: an attacker tries many password combinations until one works. Length defeats it.
  • Dictionary attacks: an attacker tests real words and common phrases. Passphrases built from unrelated words defeat it.
  • Keylogging: malware records what your users type. Multi-factor authentication limits the damage.
  • Password spraying: an attacker tries a few common passwords against many accounts. Banning common passwords defeats it.
  • Credential stuffing: an attacker reuses passwords leaked from another breach. Unique passwords per system defeat it.
  • Phishing: an attacker tricks a user into handing over a password. Multi-factor authentication and rapid reset limit the damage.
  • Insider misuse: a user shares or abuses a credential they already hold. Audit trails and no shared admin passwords limit it.

Enterprise Password Dos

These six rules do the work. Each one comes with the reason it matters, so your team can defend it when someone asks for an exception.

  • Do require 14 or more characters. Length raises the cost of a brute force attack faster than symbol rules do, and users can remember it.
  • Do encourage passphrases. Three or four unrelated words beat a short string of substitutions, and they resist dictionary attacks.
  • Do enforce one password per system. Credential stuffing works because people reuse passwords. Enforcement, not guidance, closes it.
  • Do require multi-factor authentication on privileged accounts. Admin and service accounts are the target. A second factor turns a stolen password into a dead end.
  • Do rotate on risk signals. Reset after a suspected compromise, a role change, or a breach notice. NIST SP 800-63B-4 moved away from fixed-calendar expiry for this reason.
  • Do offer self-service reset with identity verification. A user who can reset securely without calling the helpdesk follows the policy. One who cannot writes the password down.

03-Do-Use-Two-Factor-Authentication

Enterprise Password Don'ts

These six habits look harmless and cause most of the tickets and most of the breaches.

  • Don't share admin passwords. A shared credential has no owner, no audit trail, and no way to revoke one person's access.
  • Don't put passwords in tickets, chat, or email. Those systems are searchable, retained, and often exported. Use a governed vault.
  • Don't expire on the calendar alone. Forced 90-day changes push users toward predictable patterns such as Summer2026!.
  • Don't require symbol rules that force predictable substitutions. P@ssw0rd is in the dictionary attackers use. Length is the stronger control.
  • Don't exempt executives. Senior accounts carry the broadest access and attract the most targeted phishing.
  • Don't reset by phone on a caller's say-so. Helpdesk social engineering starts with a friendly voice. Verify identity before each reset.

04-Dont-Send-Passwords-to-Shared-Sites

Dos and Don'ts at a Glance

Rule Do Don't
Length Require 14 or more characters Require symbols that force predictable substitutions
Reuse One password per system, enforced Let users sync the same password across systems by hand
Rotation Rotate on risk signals and after incidents Expire on a fixed calendar alone
Privileged accounts Multi-factor authentication on each one Share admin credentials in a spreadsheet
Resets Self-service with identity verification Reset by phone on a caller's say-so
Storage Governed vault with an audit trail Passwords in tickets, chat, or email

Where Bravura Pass and Bravura Safe Fit

A written policy sets the rules. Software is what makes them hold across the systems your directory does not reach. Bravura Pass gives your users self-service password reset with identity verification, enforces your policy on each connected system, and synchronizes passwords across them, including legacy platforms such as mainframe and AS/400. Bravura Safe is enterprise password management for the credentials no directory governs: shared accounts, vendor logins, and team secrets, stored in a zero-knowledge vault with an audit trail. Together they cover governed and ungoverned passwords with one policy.

When a breach calls for a company-wide reset, the Mass Password Reset capability in Bravura Pass coordinates the reset and confirms completion. Secure delivery of the new credentials requires Bravura Safe, so plan for both.

Request a demo to see how the policy above runs across your environment.

05-Protect-Your-Passwords-With-Bravura-Security

Frequently Asked Questions About Enterprise Password Policy

Which enterprise password management software reduces helpdesk password reset tickets?

Software with self-service reset and identity verification removes the reset call itself. Users prove who they are through a second factor or security questions, reset their own password, and the change synchronizes to connected systems. Bravura Pass does this across cloud, on-premises, and legacy systems, so the reset works on the systems that generate most of the tickets.

How often should enterprise passwords be changed?

Change them when risk changes, not on a fixed calendar. Reset after a suspected compromise, a breach notice, a role change, or a departure. NIST SP 800-63B-4 moved away from routine expiry because forced changes push users toward predictable patterns. Pair risk-based rotation with multi-factor authentication and length requirements.

What is the difference between a password manager and enterprise password management?

A password manager stores one person's passwords. Enterprise password management governs credentials for the whole organization: shared accounts, vendor logins, and team secrets, with policy, access control, and an audit trail. Bravura Safe is enterprise password management. It adds zero-knowledge encryption, so we cannot read your stored credentials, and it works alongside Bravura Pass for the accounts your directory governs.

Should executives be exempt from password policy?

No. Executive accounts hold the broadest access and receive the most targeted phishing. An exemption creates the exact account an attacker wants. Apply the same length, multi-factor, and reset rules, and give executives a fast self-service path so the policy does not feel like friction.

How do you reset every password in the company after a breach?

Use a mass password reset capability that forces the reset across connected systems at once, verifies each user's identity, and confirms completion. In Bravura Pass, Mass Password Reset coordinates that action. Secure delivery of the new credentials to users requires Bravura Safe, so confirm both are in scope before an incident, not during one.