Devices & Accounts

Information Held for Another Company Was Leaked — Unauthorized Access at Sony Life, and How to Protect Information Entrusted by Others

Security Lab — kurashiki-bouzu

Hello, I am Kurashiki Bouzu (kurashiki-bouzu), born in 1971. I am a former funeral director, and I now live in an old house in Kurashiki, Okayama, working together with my AI butler, Moka.

This time, the story is about unauthorized access at an insurance company. However, the information first confirmed to have leaked was not that company’s own customer information, but policy information it had been entrusted with by another insurance company. It is an incident that raised the question of the work itself: how to protect information held for someone else.

The result first

Here is the conclusion, up front.

What happened — what the announcements confirmed

First, Sony Life’s initial announcement (October 28, 2026, “Apology Regarding the Occurrence of Unauthorized Access to Our Systems and Information Leak”).

On the same day, October 28, a notice of service suspension was also issued. From 8 a.m. on October 28, 2026, Customer WEB Service, the Sony Life App, the Direct Claim Service, the Application Details Copy WEB, the Document Confirmation WEB, and the Foreign Exchange Rate Inquiry System were temporarily suspended as emergency maintenance. The time of restoration was undecided at that point. For urgent procedures, customers were directed to their representative or the customer center.

Then, on November 9, 2026, Sony Life issued an “Apology and Notice (Second Report).” As a result of continuing the investigation, it said, the occurrence of an information leak arising from the unauthorized access announced on October 28 had been newly confirmed. The newly confirmed scope is set out separately in a later section.

What leaked first was “information held for another company” — the contents of the about 385,000 items

The personal information confirmed to have leaked in the October 28 announcement was as follows.

This is the most distinctive feature of this incident. What leaked was not information about Sony Life’s own insurance, but policy information of another insurance company, Medicare Life. Medicare Life had entrusted the work of selling insurance (insurance agency work) to Sony Life. For that work, information about policyholders and insured persons had been placed within Sony Life’s systems.

From the side that entrusted the information, even if its own company’s systems are unharmed, if information leaks at the place it was entrusted to, its own customers’ information has gone out. Conversely, from the side that was entrusted with it, any looseness on the grounds that “this is another company’s information” is not acceptable. Information held for another company is, for that company’s customers, their own important information itself.

The announcement from the side that entrusted it — Medicare Life’s explanation

Medicare Life, the side that entrusted the information, also issued an announcement on October 28, 2026, “Regarding the Leak of Customer Information Due to Unauthorized Access to an Insurance Agent’s System.”

What matters in the announcement from the side that entrusted the information is the line it draws: “other than policies solicited by Sony Life, there is no fact of a leak.” Even among Medicare Life policyholders, the information of people who joined through a different channel did not go out. That is because how information is placed differs for each place it is entrusted to. It can also be read as showing that the side entrusting information needs, in ordinary times, to keep count of which information it entrusts to which counterpart, and to what extent.

The scope widened in the follow-up report — about 2.9 million items of its own policies as well

In the second report of November 9, 2026, the following three were newly confirmed to have leaked.

In other words, what came to light first was “information held for another company,” and in the later investigation it was found that “its own information” had also leaked — that was the order. As of November 9 as well, it is stated that no fact had been confirmed of customer information having been misused. Regarding the time for resuming services, it was expected to take time, because a judgment would be made based on an evaluation of safety in addition to responding to the cause.

Some people must have taken the first report to mean “our own policies are not affected.” That reading changed with the second report. An announcement made in the middle of an investigation is only a line drawn at that point in time. I think reading through to the follow-up reports matters for both the side that entrusted information and the side that was entrusted with it.

The responsibility for protecting information held for others — a story that also connects to the funeral field

From here, this is my view as a former funeral director.

In the funeral field as well, there are ordinary occasions when information belonging to another company is held. When helping with claim procedures for insurance the deceased’s family held, when introducing a mutual aid association or funeral insurance, information such as the family’s names, addresses, and contact details, and whether or not a policy exists, may be held for exchanges with another company.

For a funeral company, that information may be “information for procedures,” but for the family, it is their life itself. And from the company that entrusted it (an insurance company or mutual aid association), it is information about its own customers. If the side holding it treats it loosely, the ones troubled when it leaks are both the company that entrusted it and its customers.

I think it is symbolic that, in this incident, the leak first confirmed was of information held for another company. Even if a company builds shelves and puts locks on them for its own information, information held for others can be left outside the shelves, in any line of work. Put information held for others on the same shelf as your own information, and put the same lock on it. I think that is the basis of work that handles another company’s information.

Preparing as a reader — for those who may be affected

The leaked items include policy numbers and policy details. That is the key point for preparing in this incident.

The methods of contacts impersonating a company are also summarized in the glossary as impersonation and phishing.

Lessons for the side holding information — for work that handles another company’s information

Where the line is — what is not yet known

The bigger the stir, the more the line matters. As of this article, I will honestly list what has not been made public.

The fact that information held for another company leaked is a heavy one. Even so, I think the way things proceeded — both companies issuing announcements on the same day, and the side that entrusted the information showing the line that “other than the policies it solicited, there was no leak” — is worth leaving as a record of work that holds information for others. And to protect information held for others on the same shelf as your own information. Making that obvious thing into a form is what can be brought back from this incident.

Sources


Entrance (other languages)

日本語 中文 Español 한국어 Français Deutsch हिन्दी العربية

Devices & Accounts / Back to the English top