BPO and contact-centre teams

Preventing employee credential phishing at BPOs and call centres

BPO agents sign in to many client platforms, often under time pressure, which makes them a frequent phishing target. Where client and internal platforms support FIDO2/WebAuthn, named-user security keys remove the code an attacker would otherwise trick an agent into handing over. Client contracts and platform support must be confirmed first.

Why this happens

  • Agents handle many logins and links a day, making a convincing fake page easy to miss.
  • Shift work and shared desks encourage shared credentials or written-down codes.
  • A single compromised agent or supervisor can expose client data and contractual obligations.

What to do, in order

  1. List internal and client platforms and confirm which support security keys.
  2. Assign keys to named people, not desks or shifts.
  3. Decide on connectors for thin clients and desktops (USB-A or USB-C) and whether NFC phones are used.
  4. Plan spares, joiner/leaver handling and lost-key procedures with HR and IT.
  5. Combine with network segmentation, endpoint controls and awareness training.

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.

Security keys suit shared-desk environments because the credential travels with the person rather than the PC. Supervisors and workforce-management administrators are a sensible first group.

TKWIT already supports BPO and contact-centre network, Wi-Fi and cabling work in Sri Lanka and can add YubiKey supply and enrolment planning for sites in Colombo, Port City Colombo and elsewhere in the country.

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 client platforms allow security keys?
Some do and some do not; client identity policies may also control what agents can use. Confirm with each client before rollout.
Which model suits agents?
It depends on the computers' ports and whether phones are used. YubiKey 5 NFC (USB-A) and 5C NFC (USB-C) cover most cases; Bio FIDO Edition adds a fingerprint but is FIDO-only.
What happens when an agent leaves?
Remove the key from their accounts in each platform and recover or reissue the hardware under your joiner/leaver procedure.

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