Colour theme
Book a consultation

Seven overlooked routes into business accounts

Review seven overlooked account access routes, including sessions, phone numbers, recovery inboxes, connected apps and support requests.

A person typing on a laptop with green code displayed on its screen.

An account review needs to cover more than its password box. A phone number, recovery inbox, connected application or support process can provide another route to access.

Use these seven checks with IT and the people who own important business accounts. The business-login review covers your account inventory and central sign-in controls; this guide looks at paths that can be missed.

1. A stolen signed-in session

Some services use session cookies or tokens to keep you signed in. Malware or a phishing relay may steal that session and let someone reuse it within the service’s controls.

Microsoft’s AiTM research describes attacks that captured session cookies after authentication. Completing MFA doesn’t make every subsequent session safe.

Check managed browsers, device protection and the service’s session-revocation procedure. Use the email-recovery guide if you suspect someone retained access after a password change.

2. A transferred mobile number

A fraudulent SIM replacement or number transfer can redirect calls and texts used for account recovery. The attacker doesn’t necessarily need the physical phone.

The Cyber Centre’s SIM guidance recommends asking your carrier about additional account verification and available port protection. Check whose requests your carrier will accept for changes to company mobile accounts.

Review where the number is used for sign-in or recovery. Prefer supported phishing-resistant methods for important accounts, with a tested backup route. Unexpected cellular-service loss needs prompt checking with the carrier through a known contact; it can also have an ordinary service cause.

3. An unprotected recovery inbox

A recovery address can receive reset links for a more important account. An old personal mailbox or former employee’s address can leave the business dependent on access it doesn’t control.

Record recovery addresses, who owns them and how they’re protected. Review them during staff and supplier changes. Use the credential-handling guide to document recovery without exposing backup codes.

4. Permission granted to a connected app

A consent screen can give an application permission to read files, email or contacts. That can give the application continuing access through its permissions, without anyone learning the user’s password.

Microsoft’s illicit-consent guidance explains why password resets alone don’t remove these grants.

Have IT review unexpected consent, what each app can reach and whether to revoke or restrict it. A familiar logo doesn’t make an app safe to allow. The SaaS integration guide covers routine application review.

5. Malware on a trusted device

Malware can capture typed credentials or other authentication material. A stronger password won’t fix a device that’s still compromised.

Install software only from sources IT has set up, keep devices updated and use managed endpoint protection. Report suspicious downloads and device alerts through the known support route. Let the response team investigate and contain the device; avoid resetting credentials on a device suspected of recording them.

6. A support request that bypasses verification

Someone impersonating a colleague may ask support to reset MFA or change a recovery method. Voice cloning, caller display and messages from a compromised mailbox can make that request sound credible.

Agree independent identity checks and an escalation route before a reset is needed. Staff should never send a current password or MFA code to get help. An urgent request still goes through the same checks.

7. A convincing fake sign-in or MFA prompt

A polished message can direct someone to a fake login, a phishing relay or an unexpected authentication request. Poor spelling has never been a dependable way to rule these out.

Open the service through a known bookmark or the official app. Verify unexpected requests through an established contact route and report unwanted MFA prompts without approving them. The MFA-method guide explains the protection different methods provide.

Give findings an owner and a next action. If access is already suspected, follow your incident process and preserve relevant records; changing one password may leave other routes open.


Featured Image Credit