Key takeaways

  • Japan's Digital Agency said on November 20 that files in the file sharing service of GSS, the shared IT platform it runs for government ministries, may have leaked. The service is used to exchange large files such as meeting materials, between officials and with outside businesses.
  • Someone other than the intended recipients accessed files from July 30 to November 12, about three and a half months. The agency detected it on November 12 and stopped the service that day.
  • It is the second GSS breach made public this year. The first, disclosed in September, came through a VPN vulnerability and exposed data on about 246,000 people. That intrusion was confirmed and cut off on July 9. The new access began three weeks later.
  • File sharing and transfer services are a favorite target. Two Cabinet Office file servers running FileZen were broken into through vulnerabilities, in 2021 and in January 2026, and the Cl0p extortion group has stolen data from hundreds of organizations at a time through Accellion, GoAnywhere, MOVEit and Cleo. This time, the service may also be a cloud service, which would point to different weaknesses.
  • The agency has not said how the access happened, how many files were involved, which ministries they belonged to, or whether the two cases are related. In our view, those are the questions it now has to answer, and quickly: the platform is the government's model for how ministries should work.

What the agency said#

According to the Digital Agency's notice:

Date (2026) Event
Jul 30 Earliest access by someone other than the legitimate sharing partners found so far
Nov 12 The agency detects possible access to files by someone other than the sharing partners, starts investigating, stops the service and cuts its communication with the outside
Nov 12 onward Investigation with the police and outside specialists; report to the Personal Information Protection Commission
Nov 20 Public notice

Part of the uploaded files may have leaked. The agency publishes the case because those files are assumed to include personal data. It says no secondary harm has been confirmed, and that the exact period of access is still being investigated.

The notice does not say:

  • How the access happened: a stolen account, shared links, a misconfiguration or a vulnerability
  • Which product the service runs on
  • How many files were accessed, and what they contained
  • Which ministries and outside parties used the affected shares
  • How it was finally detected
  • Whether it is related to the September breach

The second breach this year#

First breach (disclosed Sep 11) Second breach (disclosed Nov 20)
What GSS network, through a VPN device GSS file sharing service
Route A known VPN vulnerability, then a maintenance account used to read large numbers of files Not stated
Access Believed to have begun in May; cut off on July 9 July 30 to November 12
Detected June 25, mass file access by a maintenance account November 12
Disclosed 11 weeks after detection 8 days after detection
Data About 246,000 records on officials and outside contacts Unknown; files assumed to include personal data

Details of the first breach are in our September article. There, the agency took two weeks after detection to confirm the way in, and named neither the product nor the vulnerability. Japanese researchers pointed to a flaw in Palo Alto Networks' GlobalProtect VPN.

The Digital Agency has had a third incident in between. In October, data from its website's inquiry forms, up to about 13,323 records, may have leaked through the website builder Studio, which it used to run part of its site.

Why the dates matter#

The first intrusion was confirmed and cut off on July 9. The agency then spent the summer establishing who was affected, and disclosed it on September 11. The new access began on July 30, in the middle of that work, and went on for three months after the September announcement.

There are two possible readings, and the agency has not said which is right:

  • The cases are related. Something taken or learned in the first intrusion, such as account details, file links or knowledge of the environment, made the second possible. That would mean the first investigation did not find everything.
  • The cases are separate. A second, unrelated weakness existed in the same platform, and it was not caught for three and a half months, during a period when the agency was investigating an earlier breach of the same platform and should have been watching it most closely.

Either way, the length is the issue. A file sharing service is built to be reached from outside the government, so access by outsiders is its normal state. That makes abnormal access harder to spot, and it is why such services need logs of who opened which file, alerts on unusual volume or unknown recipients, and someone reading them.

A favorite target#

File sharing and transfer services hold exactly what attackers want: documents from many people and organizations, collected in one place and reachable from the internet by design. They are not attacked as often as VPN devices, but when they are, the damage tends to be wide.

The Japanese government has been here before. Two Cabinet Office file servers have been breached through the same product, Soliton Systems' FileZen:

When Whose service Cause Exposed
Detected January 2021, disclosed April 22, 2021 File sharing storage used by staff of the Cabinet Office, Cabinet Secretariat, Reconstruction Agency and the Personal Information Protection Commission Vulnerabilities in FileZen Personal data of 231 people. With no access logs, the agency could not tell whether files were taken, according to ScanNetSecurity
January 2026, disclosed April 28 File transfer server of the Cabinet Office's Okinawa General Bureau A vulnerability in FileZen Up to 15,091 people, mostly from old files left on the server: land registers, participant lists and photos from events held from 2024 to 2025, ferry refund records
July 30 to November 12, 2026 GSS file sharing service Not stated Not stated

Abroad, one group has made a business of it. The Cl0p extortion group has repeatedly found flaws in file transfer products and used them to steal data from many organizations at once, then demanded payment not to publish it:

When Product Scale
2020–2021 Accellion FTA Zero-day exploits and a web shell on internet-facing servers, according to CISA and the FBI
Early 2023 Fortra GoAnywhere MFT About 130 victims claimed
From May 27, 2023 Progress MOVEit Transfer Thousands of organizations worldwide
December 2024 Cleo file transfer products Cl0p claimed the attacks

This time it may be different. The Digital Agency has not said what the GSS service runs on. GSS is built on cloud services; the minister confirmed on November 17 that its email runs on Microsoft 365. If the file sharing service is a cloud service, a product vulnerability on a government-run server, the FileZen and Cl0p pattern, is less likely. The usual weaknesses in cloud file sharing are elsewhere: links that anyone holding them can open, accounts of senders or recipients taken over, tokens or keys that let an application read files, and sharing settings that are broader than intended. The wording of the notice, access "by someone other than the legitimate sharing partners", would fit several of these. Until the agency says which, the right response for users is the same: assume anything shared in the period may have been read.

Our view#

Detection is the question, again. The first breach was found through mass file access by a maintenance account. This one ran for three and a half months before it was noticed. The emergency package the government adopted on November 6 asks companies and their contractors to get the basics right and to hunt for intrusions actively. The agency that runs the government's own platform now needs to show how its monitoring missed this, and what will change.

The disclosure was faster this time, and that deserves credit. Eight days from detection to a public notice is a real improvement on eleven weeks. But speed is half of it. As in September, the notice gives nothing another organization could act on: no product, no route, no indicators. Ministries and businesses that exchanged files through the service cannot yet tell whether their documents were among those accessed. The government is building a Japanese list of exploited vulnerabilities and promising to publish attacker infrastructure. Its own incidents are the first place to apply that.

Say whether the two breaches are connected. This is the question every security team reading the notice will ask first, and only the agency can answer it. If the second access used something taken in the first, the September investigation was incomplete, and the scope of both may need revisiting. If it did not, the platform had two separate weaknesses at once. Either answer matters to the ministries now moving onto GSS.

Files should not outlive the exchange. A file sharing service is meant for moving documents, not keeping them. But at the Okinawa bureau, participant lists and photos from events up to two years old were still on the transfer server when it was breached. Whatever the GSS service runs on, shared files should expire automatically once the exchange is done, and the agency should say how long files were kept. It is the same lesson as this month's data deletions: what has been deleted cannot be taken.

The government asks a lot of companies this autumn. It has told them to patch, to watch their systems and their contractors, and to tell people quickly. On October 6, the digital minister also asked the public to protect their own information. Holding its own platform to the same standard, in public, is the most convincing way to make that case.

What this means for practitioners#

  • If your organization exchanged files with a Japanese ministry through GSS file sharing between late July and November, assume the files may have been accessed. Review what you sent, and watch for phishing or fraud that uses details from those documents.
  • If you run a file transfer appliance or server (FileZen, MOVEit, GoAnywhere and the like), treat it like a VPN device: keep it off the open internet where you can, patch it first when a fix appears, and watch the vendor's advisories and CISA's exploited-vulnerability list.
  • If you run a file sharing service, log every file access with the identity of the person, alert on access from unexpected recipients and on unusual volumes, set expiry dates on shares and delete files automatically after the exchange, and require recipients to authenticate rather than relying on links alone.
  • After any breach, check what the attackers could have taken that opens other doors: accounts, tokens, shared links, configuration. Rotate and re-check them, and keep watching the same platform closely for months, not weeks.

Japanese terms at a glance#

Japanese Reading Meaning
ガバメントソリューションサービス(GSS) gabamento soryūshon sābisu Government Solution Service, the shared IT platform for ministries
ファイル共有サービス fairu kyōyū sābisu File sharing service
正規の共有相手先 seiki no kyōyū aitesaki Legitimate sharing partner
外部との通信を遮断 gaibu to no tsūshin o shadan Cut communication with the outside
二次被害 niji higai Secondary harm
保守運用担当者 hoshu un'yō tantōsha Maintenance and operations staff member