Rakuten Securities breach exposes 15.7 million accounts

Japanese brokerage Rakuten Securities (Translation) has disclosed unauthorized access to an internal test environment that may have exposed customer information associated with up to 15.72 million accounts.

The company detected suspicious activity on November 16 and traced the potential data exposure to November 11.

The incident potentially affected 11.25 million accounts containing login IDs and customer codes, along with another 4.47 million accounts containing more sensitive information, including names, addresses, bank account details, annual income and financial assets.

Of particular concern, Rakuten acknowledged that it had temporarily copied real, unmasked customer data into its test environment to verify an internal system upgrade.

Ryan McCurdy, Vice President of Marketing, Liquibase

“Rakuten approved an exception to its normal security procedures and moved unmasked customer data into a test environment. The company had a legitimate reason to test a system upgrade, but that decision exposed sensitive information to unnecessary risk.

“Organizations must test changes before deploying them to production, but they shouldn’t have to put real customer information at risk to do it. Enterprises should mask sensitive data, restrict access to test environments, and enforce security policies that limit unnecessary exposure.

“This also raises a bigger question about how enterprises govern their database environments. An approval doesn’t automatically make an action safe. Organizations need to enforce consistent policies, control exceptions, and maintain audit evidence showing who authorized the exception, what data moved, and which safeguards were applied.”

ㅤ

John Strand, Owner, Black Hills Information Security

“Wow, what I find interesting about this incident is just how blunt the Japanese brokerage firm has been in describing what actually caused the problem and what they’re going to do moving forward. That’s refreshing. But once again, this really highlights the importance of basic security standards and practices.

“You do not use production data in test environments. Ever. Full stop. This isn’t some advanced security concept or something that requires sophisticated technology to address. It’s one of the most fundamental rules of protecting sensitive information. And yet, we continue to see organizations make these mistakes.

“The proper way to do this is to have separate development, testing, and staging environments, each with clearly defined security controls. Staging should closely mirror production in terms of configuration, infrastructure, access restrictions, and security protections, allowing teams to validate changes before deployment. But that doesn’t mean you should introduce live production data into staging. The standard practice is to use synthetic, masked, or properly anonymized data that accurately represents production conditions without exposing sensitive information. If real production data is absolutely necessary for a specific validation, that should be a tightly controlled exception, subject to formal approval, strict access controls, encryption, retention limits, and the same security protections required in production.

“There is a process for this. These development and testing practices have existed for well over a decade and a half. We’re not talking about inventing new security standards here. We’re talking about following established processes that companies should already have in place.

“And I think that’s what makes this incident so frustrating. These are basic security practices that need to be repeated again and again to development and testing teams. But I will give the brokerage firm credit for one thing. I’m very happy they were honest about what happened, acknowledged the problem, and explained what they’re going to do to fix it. We need more of that kind of transparency when security incidents occur.”

ㅤOrganizations need to adopt these things to protest themselves. Otherwise it will end badly.

Leave a Reply