WRITE-UP · 4 MIN · 10 NOV 2026 · BY T. AL-RUB

Passwords and MFA: the small-business baseline

Most account takeovers we see described in public incident write-ups start the same way: a reused password, a stolen session or a login page that asked for nothing more than a password. The good news is that the fix is cheap, and a small team can finish it in a week.

This post sets out a baseline for passwords and multi-factor authentication (MFA) that suits an Omani SME or a small IT team. It is deliberately modest. Do these things first, then build on them.

## Start with length, not complexity

For years people were told to add a capital letter, a number and a symbol. The result was passwords like `Muscat2026!` that are easy to guess and annoying to type. Current guidance from national bodies favours length and uniqueness instead.

- Aim for at least 14 characters for anything staff type by hand.

- A passphrase of four or five unrelated words is easier to remember than a mangled word and is harder to guess.

- Do not force routine expiry. Change a password when you have a reason to think it was exposed, not every 90 days.

- Block the obvious: the company name, the year, "password", and anything that appears in a published breach list.

## Give everyone a password manager

The real enemy is reuse. If one staff member uses the same password for a shop loyalty site and the company mailbox, an unrelated breach becomes your breach. Nobody can remember fifty unique passwords, so do not ask them to.

Pick one password manager for the whole organisation, and make it part of joining the company. Staff then need to remember one strong passphrase for the manager and one for their device. Shared accounts, such as a social media login or a supplier portal, should live in a shared vault with named access, not in a spreadsheet or a chat thread.

## Turn on MFA where it matters most

You do not need to enrol everything on day one. Rank your accounts by what an attacker would gain, and work down the list:

1. Email and your identity provider (Microsoft 365, Google Workspace or similar). Email is the master key, because password resets go there.

2. Administrator accounts of any kind: cloud consoles, domain registrar, hosting panel, firewall management.

3. Remote access: VPN, remote desktop gateways and anything exposed to the internet.

4. Finance: banking portals and accounting software.

5. Everything else, as time allows.

## Choose the stronger factors

Not every second factor is equal. A rough order, strongest first:

- Hardware security keys or passkeys. These resist phishing because they only answer the real site.

- Authenticator apps that generate a time-based code, or approve with number matching.

- Text message codes. Better than nothing, but they can be intercepted or diverted through a SIM swap.

Use the strongest option each service offers, and keep SMS only as a fallback. For administrators and finance staff, a hardware key is worth the modest cost.

Watch out for "push fatigue": an attacker who already has a password can send repeated approval prompts hoping someone taps Approve to make them stop. Turn on number matching where it exists, and tell staff plainly that an approval prompt they did not trigger is a reason to report it, not to tap.

## Plan for the day someone loses their phone

MFA rollouts fail at the help desk. Decide now how a locked-out person proves who they are. Print or store recovery codes for administrators in a sealed envelope or a secured vault. Require a call-back on a number you already hold, or a manager's confirmation, before resetting anyone's factor. An attacker will happily phone your help desk and sound stressed.

## Know what you cannot see

Ask your email provider to show sign-in logs and set alerts for logins from unexpected countries and for new forwarding rules. A quiet forwarding rule is a favourite way to keep reading a mailbox after the password has been changed.

## A one-week rollout

- Day 1: list your critical accounts and who owns each.

- Day 2: choose and deploy the password manager; start with IT and finance.

- Day 3: enforce MFA on email and the identity provider for administrators.

- Day 4: extend MFA to every staff mailbox.

- Day 5: cover remote access and the domain registrar; store recovery codes.

- Day 6: write the one-page lost-phone procedure.

- Day 7: run a short briefing and answer questions.

## Checklist

- [ ] Passphrases of 14 or more characters; no routine expiry

- [ ] One company password manager, with a shared vault for shared accounts

- [ ] MFA on email, admin accounts, remote access and finance

- [ ] Number matching on, hardware keys for administrators

- [ ] Recovery codes stored safely; written lost-phone procedure

- [ ] Sign-in alerts and forwarding-rule checks enabled

If you want a second pair of eyes on your set-up, or have questions about any step, write to us at info@vulnera.om.

## Further reading

- [Password guidance for system owners](https://www.ncsc.gov.uk/collection/passwords), NCSC UK: a clear, plain-language case for length over complexity.

- [Multi-factor authentication for online services](https://www.ncsc.gov.uk/guidance/multi-factor-authentication-online-services), NCSC UK: explains the factor types and when to use each.

- [Authentication Cheat Sheet](https://cheatsheetseries.owasp.org/cheatsheets/Authentication_Cheat_Sheet.html), OWASP: a developer's checklist if you build login pages yourself.

tipspasswordsmfasme
// NEXT

Want this checked on your estate?

One business day to first reply. No sales script.