Passwords are one of those things everyone knows they should take seriously — and few organizations handle as well as they think they do. Poor credential hygiene remains one of the most common ways businesses end up compromised, and following password best practices doesn’t require complexity. It requires consistency.
According to Verizon’s 2025 Data Breach Investigations Report, stolen credentials were the way in for 22% of the breaches reviewed.
The problem isn’t what people think
Most people picture a weak password as something like “password123” — obvious and easy to guess. But the real risk is subtler than that.
It’s the employee who uses the same strong-looking password across multiple systems, so that one breach exposes all of them. It’s the contractor account that still exists six months after the engagement ended. It’s the admin credential shared among three people for convenience. It’s the password nobody changed when a former employee with access left on bad terms.
None of these are careless mistakes. They’re practical decisions made under time pressure, without a clear policy to follow. And together, they create real exposure.
What changed in password guidance
Some long-standing password rules have quietly been retired. In 2025, the U.S. National Institute of Standards and Technology (NIST) — whose guidance shapes many organizations’ security policies — updated its recommendations:
- Length matters more than complexity. Where a password is the only line of defence, NIST now calls for at least 15 characters, and drops forced rules like “must include a symbol.”
- No more scheduled password changes. Forcing everyone to change passwords every 90 days tends to produce weaker, predictable passwords. Change them when there’s a reason — a suspected compromise, or someone with access leaving.
- Check against known breached passwords. New passwords should be screened against lists of credentials already exposed in previous breaches.
Many businesses are also starting to use passkeys, which replace passwords with a sign-in tied to a trusted device. They’re worth considering where your key systems support them.
Password best practices every business should follow
- Length and uniqueness. A long passphrase is typically more secure and easier to remember than a short, complex password. More importantly, each account should use a different password. If one is compromised, the others remain intact.
- A business password manager. When everyone is expected to maintain unique, strong credentials across dozens of systems, memory isn’t a realistic strategy. A password manager controlled by the organization solves this and gives administrators visibility into what’s being used and where.
- Multi-factor authentication. Even a strong password can be stolen. MFA adds a second layer of verification so that a compromised credential alone isn’t enough to gain access. For systems containing client data, financial information, or administrative controls, this is a baseline requirement — not an optional extra.
- Regular access reviews. Credentials that are no longer in use are a risk. Former employees, contractors, and service accounts should be deactivated promptly and reviewed on a schedule. This is often where businesses find the most overlooked exposure.
Privacy obligations in Canada and Bermuda
Private-sector organizations handling personal information in Nova Scotia fall under Canada’s PIPEDA; some other provinces have their own equivalent legislation. In Bermuda, the Personal Information Protection Act (PIPA) applies. Both frameworks require appropriate safeguards to protect personal data.
Poor credential management isn’t just a technical risk — it’s a compliance one. And because small businesses are frequent targets, it isn’t a risk only large organizations face. When a breach occurs because an old account wasn’t deactivated or credentials were shared, that has implications well beyond the operational disruption.
Where to start: a quick password security check
A few questions that give you a quick read on where things stand:
- Do all staff use unique passwords for work systems, or is reuse common?
- Is there an organizational password manager in place — one the business controls, not just personal tools?
- Is MFA enforced on email, remote access, and key business applications?
- When someone leaves the organization, how quickly are their accounts deactivated?
- When was the last time access permissions across your systems were reviewed?
If the answers are unclear, that’s useful information. It points directly to where the most straightforward improvements are.
We work with organizations across Nova Scotia and Bermuda to get these fundamentals right. If you’d like to understand where your current setup has gaps, let’s have a conversation.

