Osegi
Security·2 min read

Rakuten Securities data leak: why real customer data sat in a test system

Rakuten Securities says up to 11.25 million account IDs may have leaked from a test system. The odd part: that system held real customer data.

A bank-style login screen on a laptop with a warning symbol, representing a brokerage customer data leak.
Image: ITmedia NEWS

Rakuten Securities has a data leak on its hands, and the strange part is where it happened. The data was not in the live trading system but in a test environment, a sandbox where engineers try out software changes. Real customer records are not supposed to live there.

On November 17 the company said an unauthorised third party may have taken data on up to about 11.25 million accounts. The firm detected suspicious access to some systems on November 16 and cut off the affected areas. Its investigation later showed that some information held in the test environment may have been exposed on November 11.

The exposed data for up to 11.25 million accounts includes branch codes, customer codes and login IDs. For up to about 4.47 million accounts, the list is longer: name, date of birth, address, phone number, email address, employer and withdrawal account details, self-declared annual income and financial assets, holdings by product, and last login date. Former customers are included. The login ID is different from a Rakuten ID.

Why was customer data in a test environment?

Rakuten Securities told ITmedia NEWS that during an internal system upgrade, some functions had to be checked against production data. It copied part of its customer information to a test server for a set period. The company says this was an exception, approved through formal internal procedures and not the decision of one employee. Normally, it says, test systems hold only dummy data. Asked whether it had done this before, it said "not zero, perhaps, but almost never."

Security experts are not impressed. Hiroaki Kuramochi, CTO at security firm LAC, says the basic rule is to use test data in test environments. If production data is reused, it should be properly masked, meaning sensitive fields are hidden or scrambled. He suspects the team wanted real data because building test cases that cover every kind of customer registration is hard work. That, he says, is still no excuse.

What it means for customers

The article's source does not say what customers should do, so there is no official checklist here. One side effect is already visible: the company has said one-time keys, needed for withdrawals and for changing login passwords, are taking a while to be issued.

Apps worth a look

SUMO: the number puzzle

Tap the right tiles, add them up, hit the target. Easy to learn, hard to master. Free, for all ages.

Tags:rakuten securitiesdata breachtest environmentjapancybersecurity

More from this day

See all →

More in: Security

See all →