Securing email after a password reset
A password reset can leave other email access in place. Check sessions, forwarding, connected apps and recovery methods after an account compromise.

You changed the password after a suspicious sign-in. Then a customer receives another payment request from your account. The new password may be working, but someone could still have another way to read or send your email.
Report the incident to your email administrator or IT provider immediately. Use a known phone number or another trusted channel. Don’t coordinate the recovery through the mailbox you’re trying to secure.
Stop access and check the device
Follow your provider’s account-compromise process. An administrator may need to suspend the account, reset its password and revoke sessions. These steps can interrupt the employee’s work, so arrange a separate way to contact them.
Microsoft’s recovery guidance calls for disabling the affected account during investigation and revoking active sessions. It also warns that a password reset doesn’t revoke separate app passwords. Ask your administrator to check those too.
Google Workspace’s checklist includes suspension, a password reset and revoking application tokens. Controls and their effects differ between providers. Don’t assume a button labelled “sign out” closes every kind of access immediately.
If malware or a stolen session is suspected, have the employee’s device checked. Use a trusted device for recovery and keep the replacement password out of the affected inbox.
Find rules that copy or hide messages
A forwarding setting can send new messages to another address without anyone signing in again. An inbox rule can also move replies or warnings out of sight.
Have the administrator check mailbox forwarding and all inbox rules. Microsoft’s guidance explicitly includes hidden rules, which an employee may not see in Outlook. Record suspicious settings before removing them so the investigation retains evidence of what changed.
Ask the employee about expected rules. Sending invoices to an accounts folder may be normal; copying them to an unknown external address needs investigation. Check both the destination and the messages the rule selects.
Review apps and other people’s permissions
A scheduling or customer-management tool may have permission to use email without storing the employee’s password. That permission needs its own review.
Microsoft’s app-consent investigation guide describes how malicious applications can retain access through permissions granted by a user or administrator. Check the application’s publisher, permissions and consent history. Remove any grant the business can’t account for, and check whether an administrator’s consent exposed other accounts as well.
Mailbox delegation is another separate route. In Exchange Online, reading and sending permissions are distinct. A person may have Full Access, Send As or Send on Behalf permissions. Confirm each assignment with the business. Resetting the owner’s password doesn’t remove someone else’s delegated permission.
Check sign-in and recovery methods
Compare the account’s registered authentication methods with the employee’s own devices and keys. Microsoft’s checklist calls for removing unfamiliar MFA methods. Google also recommends checking recovery options.
Don’t leave a phone number, recovery address or authentication method in place just because the account now accepts the new password. Record what you can’t explain and have the administrator resolve it before returning access.
Work out what the account was used for
Ask the administrator to preserve available sign-in, audit and mail-delivery records promptly. Google Workspace provides logs for investigating account activity and message delivery; available features depend on the service edition.
Build a timeline with the employee: the first warning, unusual messages, changes to payment instructions and any password-reset requests for other business services. Check the Sent, Deleted and Archive folders for messages the employee didn’t write. Start the search before the first known warning, since the compromise may have begun earlier. Keep the evidence in a restricted incident record.
If fraudulent instructions were sent, contact recipients through a channel you already trust. Identify the messages they should disregard. If a payment may have been redirected, contact your financial institution immediately and report the incident to local police and the Canadian Anti-Fraud Centre, as the Centre advises.
If personal information may have been exposed, involve the person responsible for privacy. The Privacy Commissioner’s breach guidance explains assessment, reporting, notification and record keeping under PIPEDA. Provincial privacy laws and client contracts can add their own notice rules.
Confirm recovery before closing the incident
Have the administrator confirm that the attacker’s access and settings were removed, the device is safe to use, and the employee can sign in with their own MFA method. Test email delivery and any legitimate integrations that were interrupted during recovery.
The Cyber Centre’s email-security guidance recommends MFA and staff training on phishing and business email compromise. Include unexpected MFA prompts and unexplained mailbox changes in the signs employees should report. Ask whether automatic forwarding to outside addresses is blocked, and allow it only where there’s a business reason. Assign an owner and a date to any remaining fixes.


