Stop Blaming Your Agents for Call Center Breaches

CSR working on a laptop

No matter what the industry, consumers trust organizations to look after their data. No more so when dealing with agents and customer service representatives who have access to vast amounts of sensitive data.

This trusted access for employees to cardholder data, personal details or medical records helps ensure the best customer experience. However, it also makes the call center a prime target for a security breach.

The Insider Threat

Whilst it’s commonly understood that the greatest risk of a breach comes from the employee, blaming your agents is never the right route to take. Call center agents are human. They are careless, flawed and often exploited. In fact, attackers love exploiting the naivety of your employees because it’s so easy.

All it takes is one successful phishing email to persuade just one user to hand over their organizations login details. Once that hacker gains entry to your systems, you’re not going to find out until it’s too late — your anti-virus and perimeter systems aren’t programmed to pick up on access using legitimate login details, giving snoopers all the time in the world to, well, snoop.

And also keep in mind that almost every external attack eventually looks like an insider threat. The use of compromised internal credentials by an external attacker is the most common threat action in data breaches (Verizon, Data Breach Investigations Report 2018).

So, how are you supposed to spot inappropriate employee access when it’s already been defined as appropriate?

Spotting the threat

Security must be there to protect against both careless and malicious employee behavior and to protect against outsiders trying to gain access by pretending to be employees.

When you boil it down, the only way to really tell if someone is a malicious insider or an intent external threat actor is by allowing them to perform actions (such as launching applications, authenticating to systems, accessing data, etc.) and determine whether the actions are inappropriate.

But given the majority of your employees don’t act the same way everyday – let alone the next week or month – it makes more sense to spot the threat actor by looking at leading indicators of threat activity, rather than waiting for the threat activity itself.

One of the most accurate leading indicators is one no malicious insider or external threat actor can get around – the logon (local, remote, via SMB, via RPC, etc.). Endpoints require logons for access, lateral movement of any type requires authentication to access a target endpoint, and access to data first requires an authenticated connection.

No patch for employees but you can enhance access security

The leveraging of logon management solutions provides organizations with not only the ability to monitor logons and identify suspicious logon activity, but to also craft logon policies to limit the scope of account use and automatically shut down access based on inappropriate logon behavior. By using the contextual information around a user’s logon (origin, time, session type, number of access points, etc.) genuine logins become useless to would-be attackers.

So, while there might not be a patch for the employee quite yet, keep in mind that you do have a foolproof way to make sure call center staff are who they say they are, identify any ‘risky’ user behavior and put a stop to it before it ends up costing you capital, customers and your company’s reputation.

Learn more about how call centers can verify access to the network and the data within.

About the Author

François AmigorenaFrançois Amigorena is the founder and CEO of IS Decisions, and an expert commentator on cybersecurity issues.

IS Decisions is a provider of infrastructure and security management software solutions for Microsoft Windows and Active Directory. The company offers solutions for user-access control, file auditing, server and desktop reporting, and remote installations.

Its customers include the FBI, the US Air Force, the United Nations and Barclays — each of which rely on IS Decisions to prevent security breaches; ensure compliance with major regulations, such as SOX and FISMA; quickly respond to IT emergencies; and save time and money for the IT department.

Related Articles

Leave a Comment

Solve : *
21 ⁄ 3 =