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.
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.
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.
Your policy exists to make these seven attacks fail. Each one targets a different weakness.
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.
These six habits look harmless and cause most of the tickets and most of the breaches.
| 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 |
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.
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.
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.
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.
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.
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.