For organisations of every size

How to prevent business account takeover

Business account takeover usually begins with one phished employee login. Reduce the risk by giving every user a unique sign-in, enforcing phishing-resistant MFA on supported identity platforms, starting with high-privilege staff, and designing a recovery process that attackers cannot easily abuse.

Why this happens

  • Shared team logins make it impossible to know who signed in and easy for one leak to expose everyone.
  • A single compromised mailbox can be used to send convincing fraud requests to customers and suppliers.
  • Help-desk password and MFA resets are a common target for social engineering.

What to do, in order

  1. Inventory critical systems: email and identity, finance, client platforms, password vaults and admin consoles.
  2. Replace shared accounts with named users wherever the platform permits.
  3. Pilot FIDO2 security keys with administrators and finance staff, then expand by risk.
  4. Issue a backup key or alternate strong method and record who holds which key.
  5. Tighten help-desk identity checks for resets and review sign-in alerts.

Where a FIDO2 security key such as YubiKey fits

FIDO2/WebAuthn is an open sign-in standard supported by major browsers and many online services. When you register a security key, it creates a key pair tied to that service's real web address. At sign-in the key only answers for the genuine site, so a look-alike phishing page cannot obtain a usable response, and there is no code for someone to read out or forward. A YubiKey, manufactured by Yubico, is one widely used hardware security key that supports these standards.

Identity platforms such as Microsoft Entra ID and Google Workspace can require security keys for selected users when configured by an administrator. Hardware alone does not change policy; the platform settings must be planned and tested.

TKWIT supplies compatible YubiKeys and assists with selection and enrolment planning for companies in Colombo, Port City Colombo and across Sri Lanka, including teams procured from overseas head offices.

What a security key cannot do

  • A security key cannot remove malware already running on a computer or phone. Malware can act inside a session after a legitimate sign-in.
  • It does not stop session-cookie or token theft once a session exists; short session lifetimes, device security and sign-in monitoring still matter.
  • Protection only applies to services and sign-in flows that support FIDO2/WebAuthn or FIDO U2F and where weaker fallback methods are restricted.
  • One-time-code (OTP) modes on a key are not phishing-resistant in the same way as FIDO authentication.
  • Only biometric models such as YubiKey Bio FIDO Edition have a fingerprint sensor; other models use a touch and, where required, a PIN.
  • No single control stops every cyberattack. A key is one layer alongside updates, backups, endpoint protection and staff awareness.

Frequently asked questions

Do we need a key for every employee?
Ideally every user of a protected account has their own key plus a backup. Many organisations start with privileged and finance users.
Can one key be shared by a team?
Sharing defeats accountability and recovery. Keys should be registered to named individuals.
Does this make us compliant with a standard?
Hardware alone does not make an organisation compliant. It can support a broader control set your auditors or policies define.

Related pages

More account security guides

Next step

Get help choosing and enrolling security keys

Share the accounts you want to protect, device connectors and number of users. TKWIT will confirm compatibility, availability and setup assistance in a quotation.

WhatsApp Call UsGet a Quote