Colour theme
Book a consultation

Safer password handling and account recovery

Help staff use unique passwords, protect recovery methods and verify reset requests, with a tested process for lost devices or exposed credentials.

An illustration of a hooded figure using a laptop.

A strong sign-in process also needs a safe way to handle lost devices, forgotten passwords and requests for help. If a reset request can bypass identity checks, better authentication at the normal login screen won’t fix that gap.

Give staff clear instructions for storing credentials and getting access restored. Use the business-login review to check account coverage and administrator access. Here, the focus is everyday credential handling and the recovery process.

Make unique passwords practical

For accounts that still use passwords, use a long, unique password for each service. The password manager your business uses can generate and store them. Check that it works with the devices, browsers and accessibility tools your team uses.

Set up individual staff access and restrict shared vault items to the people who need them. Avoid sending passwords through ordinary email or chat. Protect the password manager itself with supported strong authentication and a recovery process your business understands.

NIST’s current password guidance calls for blocking common or compromised values, allowing password managers and avoiding arbitrary composition rules and routine password changes. It requires a change when there’s evidence of compromise. Those are design requirements for services applying NIST’s standard; check what your own provider supports before changing your business policy.

Don’t enter a business password into an unfamiliar website that offers to check it. Use your administrator tools or the password manager’s built-in checks, and investigate any exposure report.

Review recovery routes alongside MFA

Record how staff regain access if their phone or security key is lost. Check backup authenticators, recovery codes, recovery email addresses and who can change those settings. Keep codes somewhere protected, where only the people responsible for that account can open them.

Use the MFA-method guide to select authentication. Then verify recovery separately. A second method helps only if it’s supported for the action the user needs and remains available when the primary one is lost.

Microsoft’s authentication-method table distinguishes sign-in, MFA and password-reset support. A method that works for sign-in isn’t automatically a password-reset method. Confirm your tenant’s current settings and licences, and test the complete recovery path.

Verify a reset request before changing access

Document how the support team establishes the requester’s identity. Use a route agreed in advance, with independent checks suitable for the account. Don’t rely on a familiar voice, caller display or a message from the affected mailbox on its own.

Give administrators a clear escalation route when verification fails. Don’t skip a check because someone says it’s urgent. For privileged accounts, consider having a second named person review the request, and record the decision.

Staff should never need to send their password or a current MFA code to a colleague to obtain help. Explain how to report an unexpected reset message or authentication prompt without approving it.

Practise recovery before someone needs it

Use a designated test account to try the lost-device scenario. Confirm that the right person receives the request, verifies it, restores access and removes the lost authentication method from the account.

Test the password manager’s recovery arrangements too. A procedure stored only inside the locked vault won’t be available when it’s needed. Check the controlled instructions and responsible contacts during staff changes.

Record the test result and unresolved problems. Don’t disable MFA to make a recovery exercise pass; fix the recovery route.

Treat suspected theft as an incident

An exposed password or unexpected authentication-method change needs investigation, even if access is restored. Reach the administrator through the known support route, preserve relevant evidence and follow the service’s containment procedure.

Changing a password may leave active sessions, application access or a compromised device in place. The email-recovery guide explains the additional checks. Recovery from a lost phone and response to suspected account theft need different handling.

Talk to us if you need help documenting credential handling or testing how staff regain access safely.


Featured Image Credit