TCL Portal

When Your Partner's Staff Are Inside: Japan's Secondment (出向) Risk and the Toyota Insurer Leak

Published:
  • #Japan
  • #Insider Threat
  • #Governance
  • #Secondment
  • #Case Study

Part of our guide to Japan’s cybersecurity landscape. For the regulatory map behind it, see Japan’s Cybersecurity Laws & Guidelines.

In April 2026, three of Japan’s largest non-life insurers disclosed that employees they had seconded to Toyota Motor had improperly taken Toyota’s internal information and the personal data of Toyota employees, reportedly over several years (Nikkei). To a foreign reader this sounds like an ordinary insider leak. It isn’t — and the reason why is a feature of Japanese business that most overseas security teams have never had to threat-model: 出向 (shukkō), the secondment of staff between companies.

I work in information security at a Japanese enterprise. I want to use this case not to pile on, but to explain a structural blind spot that foreign companies with Japanese partners, joint ventures, or keiretsu ties quietly inherit.

What was reported

According to reporting, employees seconded from Tokio Marine & Nichido, Mitsui Sumitomo Insurance, and Aioi Nissay Dowa Insurance to Toyota took internal materials — such as meeting minutes and organizational information — and personal information on Toyota employees, without authorization (Nikkei; Toyo Keizai). Coverage described the conduct as effectively gathering competitive intelligence — rival insurers’ terms, competing quote prices, renewal timing — for the seconding insurers’ sales benefit.

As this disclosure is recent and still developing, I’ll treat the specific figures cited in reporting as provisional and focus on the structural mechanics, which are already clear enough to learn from.

This did not emerge in a vacuum. It follows the broader reckoning in Japan’s non-life insurance sector — the BigMotor fraudulent-claims scandal and the resulting scrutiny of seconded staff — which prompted the Financial Services Agency’s 2024 report on structural problems in the industry, flagging the appropriateness of secondments to agents and partners as a core issue (FSA report, June 2024).

What is 出向 (secondment), and why it’s a blind spot

Here is the context a foreign security team lacks. Under 出向, an employee of Company A is sent to work inside Company B — embedded in B’s offices, on B’s org chart, often for years — while their employment relationship with A continues. It is a normal, trust-based feature of Japanese corporate relationships, used to deepen partnerships, transfer know-how, and cement keiretsu and supplier ties.

For an insider-threat model, secondment creates a person who is:

That is a structurally awkward combination. The seconded employee has an insider’s reach and an outsider’s incentives, wrapped in a relationship whose whole premise is not to treat them with suspicion. A Western “third-party risk” or “contractor offboarding” program doesn’t cleanly capture this, because 出向 staff are not contractors and not quite employees — they are trusted partners sitting at an insider’s desk.

The structural reading — attack the system, not the person

The instinct is to frame this as individuals behaving badly. I think that misses the more useful, and more uncomfortable, point: the system was arranged so that this behavior was almost rational.

When a seconded employee’s home-company evaluation rewards the intelligence and relationship value they bring back, and the host grants insider access on the assumption of partnership goodwill, you have built an incentive to gather information and removed the controls that would catch it. That is not a story about bad apples; it is a story about an environment that quietly asked for the fruit.

The governance principles are the same ones I apply to any access decision:

Blaming the individuals lets the structure off the hook, and the structure is the part you can actually fix.

Lessons for foreign companies with Japanese partners

If you operate in Japan through joint ventures, keiretsu relationships, or partner secondments — or you host seconded staff from a Japanese partner — this is your threat model too:

For the Japanese data-protection obligations triggered when employee personal data is involved, see the APPI guide.

The bottom line

The Toyota insurer case is not really about three insurers, and definitely not about a few individuals. It is about a trusted business structure — secondment — that grants insider access on the strength of a relationship, without the measurement that would catch abuse. Foreign companies tend to threat-model contractors and employees; in Japan, the trusted person at the next desk may belong to someone else entirely. Model that, or inherit the blind spot.

Start from the pillar guide for the full map of Japan’s regime.

References

FAQ

What is shukko (secondment) in Japan?

A Japanese practice in which an employee of one company is sent to work inside another company, embedded in its organization for an extended period, while their employment relationship with the original company continues.

Why is secondment an insider-threat risk?

A seconded employee has an insider's access inside the host company but ultimate loyalty to a different employer, all wrapped in a trust-based relationship that discourages treating them with the scrutiny applied to other privileged users.

What was reported in the Toyota insurer case?

Employees seconded from three major Japanese non-life insurers to Toyota were reported to have improperly taken Toyota internal information and employee personal data over a period of years, disclosed in April 2026.

What should foreign companies do about secondment risk?

Treat seconded staff as privileged insiders: inventory their access, apply least privilege by function, log and review their access to sensitive data, and set clear data-handling terms in the secondment agreement.

About the authors

Sekiko Jo

CISSPCCSP

CISSP and CCSP-certified security specialist focused on cloud threat modeling and security governance. A Registered Information Security Specialist (情報処理安全確保支援士) in Japan, she writes from hands-on incident-response experience inside a Japanese enterprise.

Hiroto Yuki

CISSPCCSP

CISSP and CCSP-certified. Writes from red-team and SOC operational experience about defenses that actually hold up.