Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.


02:00 PM
Scott Straub
Scott Straub
Connect Directly
E-Mail vvv

The Data Privacy Loophole Federal Agencies Are Still Missing

Why knowledge-based authentication is leaving federal contact centers vulnerable to an increasingly sophisticated hacker community.

The eyes of the general public are firmly trained on data privacy issues. From fears over the security of the social media giants right through to daily call center interactions, data privacy — or lack thereof — is the defining vulnerability that hangs over many federal agencies as they look for ways to secure customers' data. While customers have grown accustomed to seeing headlines about the latest social media or corporate data breach, sensitive and personal information contained within federal government agency databases may be the most vulnerable.

Privacy regulations, largely on the state level, have been focused on preventing future data breaches, limiting how customer data is collected and used, and, more recently, inviting customers to request their personal data be returned to them — with the California Consumer Privacy Act (CCPA) leading the charge. On the federal level, the IRS has led in addressing identity-based tax refund fraud while the Department of Veterans Affairs has begun prioritizing the "veteran experience" by more efficiently managing its trove of personal data.

These good intentions miss half the battle. With a deep trove of breached personal information already exposed and available to bad actors, the genie can't be put back into the bottle, as revealed last fall by a Pew study of public concerns about the widespread availability of this information.

The solution is to deweaponize personal information — make all breached personally identifiable information (PII) useless for gaining account access anywhere. Why then, are so many government agencies, as noted in this 2019 US Senate report, still authenticating customers for account access with the very information that's already compromised?

Ever since the global phone network connected to the Internet in 2003, criminals have been spoofing phone numbers and impersonating customers. In response, call centers started to challenge callers with knowledge-based authentication (KBA), relying on personalized questions to protected customer data and allowing them to be identified in a relatively straightforward and efficient manner. However, years of data hacks and customers readily divulging private details has made this information public and no longer sufficient for authenticating an identity.

Increased Government KBA means Frustrated Callers
One of the most immediate risks to customer data privacy on the federal level lies in an over-reliance on knowledge-based authentication across a number of government agencies. [Editor's note: The author's company provides inbound authentication solutions that address the challenges/risks associated with KBA, as do other vendors.] Fraudsters are increasingly targeting federal agencies, looking for customer PII that can later help them gain fraudulent access to victims' financial, healthcare, or government accounts. While confidence in KBA is waning every day in the private sector, the response some major government agencies are taking is to simply increase the number of questions, along with their complexity and intrusiveness. The result is frustrated callers. When it comes to authentication, it's time for an upgrade in the federal technology space.

Authentication should be performed using multiple factors without overreliance on the asking of questions. That means using factors such as ownership and possession of a unique device (such as a trusted phone) or identification cards combined with a biometric factor such as a voiceprint or fingerprint. New technologies — including ones that use customers' smartphones as physical ownership-based authentication tokens — can achieve significantly more accurate authentication and improve the effectiveness of fraud-fighting efforts. Modern authentication approaches offer agencies improved customer satisfaction, faster call resolution, increased interactive voice response (IVR) containment, and reduced fraud risk.

To achieve a call experience on par with the private sector — seamless caller authentication, even before the call is answered and with no identity interrogation — an organization must reduce fraud attempts targeting the contact center and allow resource reprioritization where the customer spends more time within the interactive voice-response software, allowing the agency to shift resources from low-value to high-value work. As a result, operational efficiencies and cost savings are enhanced because the call can be better routed to the best customer service and overall handle times will decrease. The benefits are apparent. The challenge lies in the tendencies of customer-service federal agencies to stagnate and lag when it comes to tech adoption.

Regardless of which road a federal agency takes in 2020 when it comes to data privacy, it's become clear in the fed tech community that KBA is a relic, one that leaves contact centers vulnerable to an increasingly sophisticated hacker community. Let's leave behind our loophole-riddled systems of the past and equip the federal government with the best methods available to protect the data of federal customers. Criminals are constantly evolving their tactics; the institutions protecting customer accounts should too.

Related Content:



Register now for this year's fully virtual Black Hat USA, scheduled to take place August 1–6, and get more information about the event on the Black Hat website. Click for details on conference information and to register.

Scott is responsible for developing data-driven solutions for governments in their fraud, waste and abuse prevention programs. Prior to joining Neustar, Scott was the Director of Federal Market Strategy at LexisNexis Risk Solutions where he invented several identity-based ... View Full Bio

Recommended Reading:

Comment  | 
Print  | 
More Insights
Newest First  |  Oldest First  |  Threaded View
When It Comes To Security Tools, More Isn't More
Lamont Orange, Chief Information Security Officer at Netskope,  1/11/2021
US Capitol Attack a Wake-up Call for the Integration of Physical & IT Security
Seth Rosenblatt, Contributing Writer,  1/11/2021
IoT Vendor Ubiquiti Suffers Data Breach
Dark Reading Staff 1/11/2021
Register for Dark Reading Newsletters
White Papers
Current Issue
2020: The Year in Security
Download this Tech Digest for a look at the biggest security stories that - so far - have shaped a very strange and stressful year.
Flash Poll
Assessing Cybersecurity Risk in Today's Enterprises
Assessing Cybersecurity Risk in Today's Enterprises
COVID-19 has created a new IT paradigm in the enterprise -- and a new level of cybersecurity risk. This report offers a look at how enterprises are assessing and managing cyber-risk under the new normal.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2021-01-15
An issue was discovered in Malwarebytes before 4.0 on macOS. A malicious application was able to perform a privileged action within the Malwarebytes launch daemon. The privileged service improperly validated XPC connections by relying on the PID instead of the audit token. An attacker can construct ...
PUBLISHED: 2021-01-15
Docker Desktop Community before on macOS mishandles certificate checking, leading to local privilege escalation.
PUBLISHED: 2021-01-15
OneDev is an all-in-one devops platform. In OneDev before version 4.0.3, there is a critical vulnerability which can lead to pre-auth remote code execution. AttachmentUploadServlet deserializes untrusted data from the `Attachment-Support` header. This Servlet does not enforce any authentication or a...
PUBLISHED: 2021-01-15
OneDev is an all-in-one devops platform. In OneDev before version 4.0.3, AttachmentUploadServlet also saves user controlled data (`request.getInputStream()`) to a user specified location (`request.getHeader("File-Name")`). This issue may lead to arbitrary file upload which can be used to u...
PUBLISHED: 2021-01-15
OneDev is an all-in-one devops platform. In OneDev before version 4.0.3, the REST UserResource endpoint performs a security check to make sure that only administrators can list user details. However for the `/users/` endpoint there are no security checks enforced so it is possible to retrieve ar...