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
- List internal and client platforms and confirm which support security keys.
- Assign keys to named people, not desks or shifts.
- Decide on connectors for thin clients and desktops (USB-A or USB-C) and whether NFC phones are used.
- Plan spares, joiner/leaver handling and lost-key procedures with HR and IT.
- 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
Microsoft 365, Outlook and Gmail
How to stop your email account being hackedPractical steps to protect Microsoft 365, Outlook and Gmail accounts from phishing and takeover, and where a FIDO2 security key fits. Advice for Sri Lanka.
Choosing a second factor
Phishing-resistant MFA versus SMS one-time codesWhy SMS OTP and push approvals can still be phished, how FIDO2/WebAuthn security keys and passkeys differ, and how to move users over safely in Sri Lanka.
For organisations of every size
How to prevent business account takeoverReduce business account takeover risk with phishing-resistant MFA, named-user security keys, backup keys and recovery planning. Guidance for Sri Lankan firms.
High-value accounts
Protecting finance, banking and cryptocurrency account accessHow to protect finance approvals, banking, stockbroking and crypto exchange logins from phishing, where FIDO2 security keys are supported, and what they cannot stop.
Admins, executives and remote workers
Securing privileged administrators and remote employeesProtect IT administrators, executives and remote staff in Sri Lanka with phishing-resistant MFA, backup keys and careful recovery, plus its limits.
FIDO2, WebAuthn and passkeys
Passkeys and passwordless sign-in for businessesWhat passkeys, FIDO2 and WebAuthn mean for business sign-in, when a hardware security key is a better home for a passkey, and how to roll out in Sri Lanka.
Biometric authentication
Fingerprint security keys and biometric sign-inHow fingerprint security keys work, which YubiKey models have a fingerprint sensor, and what biometric sign-in can and cannot protect, for buyers in Sri Lanka.
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.
