theDocumentId => 747399 HSBC Data Breach Shows Failure to Protect Passwords ...

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.

Operational Security

11/8/2018
09:35 AM
Scott Ferguson
Scott Ferguson
News Analysis-Security Now
50%
50%

HSBC Data Breach Shows Failure to Protect Passwords & Access Controls

This week, HSBC disclosed a data breach to customers that seems to show the bank failed to properly protect passwords and access controls that secured personal data.

Global banking giant HSBC disclosed this week that the company's networks appeared to have been breached in October, with large amounts of customer data possible exposed and stolen.

In a November 2 letter sent to customers, HSBC noted that the bank's security team noticed that "unauthorized users" began access online accounts sometime between October 4 and 14. Those accounts were deactivated, and customers asked to reset their passwords

It's not clear from the notification how large the breach was, but it appears that whoever was behind it was able to access a treasure-trove of personal data from the bank's customers, including full name, mailing address, phone number, email address, date of birth, account numbers, account types, account balances, transaction history, payee account information, as well as statement history where these were available.

(Source: HSBC)\r\n
(Source: HSBC)\r\n

While HSBC did not release specific information about what happened, security experts believe that the few details offered point to a credential stuffing attack, a brute-force method used to guess at passwords. Some cybercriminals will use passwords leaked in other breaches, guess that users reused similar passwords.

Whatever the cause of the attack, it appears that HSBC failed to properly protect passwords, as well as the access controls of its network to protect customer data.

"Credential stuffing is a pervasive security issue caused by the complexity of today's authentication mechanisms that still rely on a password. Users today have access to hundreds of services each requiring a password and as such credential re-use if often common," Fausto Oliveira, the principal security architect at Acceptto, which makes multi-factor authentication tools, noted in an email to Security Now.

"So, what does this mean in reality?" Oliveira added. "Once a hacker has gained access to one of the services they can try to attack other services by re-using the password and gain access to further information for example by hacking the user's email, internet provider accounts, etc."

Joseph Carson, chief security scientist at Thycotic, a provider of privileged access management (PAM) platforms, admonished the bank for its lax security, especially the controls used to protect customer data.

"It’s clear that HSBC is not following security best practices when it comes to the de-risking of sensitive data and strong privileged access controls that limit the data an individual can access at once," Carson wrote in an email. "HSBC needs to have a serious review on how they store sensitive personal data and ensure they prioritize de-risking of data into separate data vaults, as well as enforcing privileged access management strategies."

Mukul Kumar, CISO and vice president at Cavirin, which focuses on hybrid cloud security, noted that better multifactor authentication could have prevented this type of data breach.

"The breach, albeit limited, reinforces the need for individuals to better manage their passwords and for financial institutions to mandate multi-factor authentication. It should no longer be optional," Kumar wrote to Security Now. "On the HSBC side, given their prior history of breaches, must maintain better visibility into their cyber posture by continually assessing against new threats and remediating as required."

The bank's history includes a number of other data breaches, including ones in 2014 and 2015.

Related posts:

— Scott Ferguson is the managing editor of Light Reading and the editor of Security Now. Follow him on Twitter @sferguson_LR.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
The State of Cybersecurity Incident Response
In this report learn how enterprises are building their incident response teams and processes, how they research potential compromises, how they respond to new breaches, and what tools and processes they use to remediate problems and improve their cyber defenses for the future.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-32794
PUBLISHED: 2021-07-26
ArchiSteamFarm is a C# application with primary purpose of idling Steam cards from multiple accounts simultaneously. Due to a bug in ASF code `POST /Api/ASF` ASF API endpoint responsible for updating global ASF config incorrectly removed `IPCPassword` from the resulting config when the caller did no...
CVE-2021-36563
PUBLISHED: 2021-07-26
The CheckMK management web console (versions 1.5.0 to 2.0.0) does not sanitise user input in various parameters of the WATO module. This allows an attacker to open a backdoor on the device with HTML content and interpreted by the browser (such as JavaScript or other client-side scripts), the XSS pay...
CVE-2021-37392
PUBLISHED: 2021-07-26
In RPCMS v1.8 and below, the "nickname" variable is not properly sanitized before being displayed on page. When the API functions are enabled, the attacker can use API to update user nickname with XSS payload and achieve stored XSS. Users who view the articles published by the injected use...
CVE-2021-37393
PUBLISHED: 2021-07-26
In RPCMS v1.8 and below, the "nickname" variable is not properly sanitized before being displayed on page. Attacker can use "update password" function to inject XSS payloads into nickname variable, and achieve stored XSS. Users who view the articles published by the injected user...
CVE-2021-37394
PUBLISHED: 2021-07-26
In RPCMS v1.8 and below, attackers can interact with API and change variable "role" to "admin" to achieve admin user registration.