Colour theme
Book a consultation

Reviewing your business password policy

Review password rules, sign-in routes and application safeguards against current guidance, with usable controls and documented exceptions.

An illustration of a person drawing an unlock pattern on a large phone beside a shield.

Staff can follow careful password-handling instructions and still face a service that limits password length, blocks their password manager or leaves an older login route outside MFA.

Review the rules your business services enforce in practice. If you’re commissioning an application, include those rules in its acceptance requirements. Our password-handling and recovery guide covers what staff do day to day; this review concerns the sign-in service.

Use a current policy benchmark

NIST’s digital identity guidance provides a useful technical benchmark. Its current requirements distinguish a password used alone from one used only within MFA:

  • At least 15 characters for single-factor passwords.
  • At least eight characters when the password is used only as part of MFA.
  • Support for a maximum length of at least 64 characters is recommended.
  • Check new passwords against common, expected or compromised values.
  • Allow password managers and autofill.
  • Avoid mandatory character mixtures and arbitrary periodic changes.
  • Require a change when there’s evidence of compromise.

These are requirements and recommendations for implementations applying that standard. They aren’t a Canadian legal password rule. Don’t shorten a longer unique password just because MFA allows eight characters.

Ask the provider which settings you can control and what it enforces centrally. Don’t claim that a policy meets a standard based on length alone.

List every way into each service

List the web, desktop, mobile and integration routes for each important service. Identify local accounts that bypass the main identity provider and any exceptions to MFA.

Use designated accounts to verify that the intended restrictions apply. Someone can register a method and still sign in through a route that doesn’t ask for it. The MFA rollout guide covers that broader deployment.

Review the available methods with IT. One-time codes and number matching aren’t phishing-resistant. A hardware token is only phishing-resistant when its authentication protocol provides that protection; the fact that it’s a physical device isn’t enough.

Make the rules usable

Try the sign-in and password-change screens with the password manager your staff use, keyboard navigation and staff accessibility tools. Check whether long generated passwords are accepted and whether the service verifies the complete value.

A memorable passphrase can contain words. Banning every dictionary word within a longer phrase is different from blocking a common weak password. Clear rejection messages should help people choose a different value without revealing account secrets.

Avoid routine rotation that encourages predictable variations. Change an exposed credential promptly and investigate how it was exposed. If a supplier enforces a rule you can’t change, document the limitation and the available additional controls.

Include application safeguards in acceptance

For a new business application, ask the developer to demonstrate rate limiting, protected password storage and safe reset handling. Use a maintained identity platform or established authentication components that suit the project.

OWASP’s authentication guidance covers protections such as login throttling and responses that avoid unnecessarily revealing whether an account exists. Ask how these protections interact with legitimate users and support.

Passwords shouldn’t be stored in readable form or written to logs. Have the developer explain the supported password-hashing approach, secret management and how security updates will be maintained. Agree the evidence and testing needed before launch.

Record exceptions and ownership

Give each service an owner, record its enforced rules and assign gaps for follow-up. Include administrator accounts and the password manager itself. Keep test records free of live credentials.

Use the password-spraying guide to review guessing attacks and alert handling. Recovery requests and suspected account theft need their own procedures alongside the written policy.

Talk to us if you need help reviewing supplier controls or defining sign-in requirements for an application.


Featured Image Credit