Colour theme
Book a consultation

Reviewing the protection around a work account

Review account ownership, sign-in, recovery methods, app connections and signed-in devices as one practical work-account security check.

A blue padlock at the centre of a circular digital security graphic

A work account can be exposed through its password, its recovery options, a connected app or a device that’s already signed in. Check all four.

Choose an important service and work through its supported security settings with the account owner or administrator.

Confirm ownership and recovery

Record who needs the account and whether it belongs to the organization. Prefer named access and supported delegation over a password shared by a team.

Check recovery email addresses, phone numbers and backup codes. Remove outdated options after verifying that a supported replacement works.

A stronger sign-in method provides less benefit if an old personal email account can reset access. Keep administrator and emergency recovery documented without spreading secrets through a support ticket.

Use the strongest supported sign-in method

Turn on MFA, and use a phishing-resistant method such as a passkey or security key if the service supports one. The Cyber Centre’s MFA guidance explains why methods differ.

For services that still require passwords, use unique credentials stored in the business password manager. Protect the manager and its recovery path as well.

Test access before removing an existing method. Don’t assume an enabled setting means every sign-in path is covered.

Review connected apps and delegation

Look for third-party applications, connected integrations, forwarding rules and delegated access. Confirm each has an owner and a continuing purpose.

An application grant may allow access without repeatedly asking for the user’s password. Removing a password or changing it doesn’t necessarily remove that grant.

Follow the service’s supported removal process and check business dependencies before revoking a legitimate integration.

Check devices and active sessions

Review registered devices and available session information. Investigate unfamiliar entries, bearing in mind that a sign-in’s location is often approximate and device names can be vague.

If something looks wrong, use the service’s control for signing out every session. Ending a session doesn’t take back files that were already downloaded.

Keep the devices that sign in updated and managed. A stolen session or compromised endpoint can remain a problem even with strong authentication.

Handle alerts through a known route

A leaked-password alert or suspicious-sign-in message needs verification. Don’t follow a link in an unexpected email. Open the service from your usual bookmark and check its own security page.

Note what the alert tells you and what it doesn’t. Leak monitoring won’t catch every exposed password, or catch it straight away.

If compromise is suspected, use the incident process and review account activity before returning to ordinary work. Keep this review as a repeatable record of the account’s access and recovery state.


Featured Image Credit