Borrowed Debt
When you borrow a supplier's software or a platform, you pledge your data. The Publica breach and the end of Swiss Post's patient record show who repays when the loan is called.
For CDOs, CIOs and heads of data governance in Switzerland
- Organisations borrow capabilities every day: a supplier's software, a vendor's platform, a partner's service. The price is that part of their data, or a critical process, now sits with someone else. That is borrowed debt.
- Two Swiss cases from 2026 show the debt being called. Swiss Post is closing its patient record platform, and around 70,000 dossiers must move elsewhere. A breach at PK Softech AG, a software supplier to pension funds, exposed personal data of Publica's insured members.
- In both cases the client could not stop the event. What the client controls, long before, is the size of the debt: how much data was pledged, why, for how long, and how it comes back.
For your steering committee: ask which suppliers hold a copy of your critical data today, and when each copy will be deleted.
Data debt is usually described as something you create yourself: the undocumented table, the manual fix that became permanent, the definition nobody agreed. There is another kind, and it builds up through good decisions. Every time you borrow someone else's capability, you pay with your data. The loan is visible. The debt is not.
A Debt You Take On by Borrowing
Buying software instead of building it is borrowing. So is running a process on a vendor's platform, or letting a supplier test its system with your data. You gain speed and capability. In exchange you hand over copies of your data, access to it, or dependence on a service you do not run.
That exchange follows the logic of a loan.
A reading frame proposed by DataEdgePro. The financial terms are used as an analogy.
Borrowing is not the problem. Borrowing without knowing what was pledged is. In 2026, two Swiss cases showed what happens when the debt is called.
- Swiss Post announces the end of its patient record platformAround 70,000 dossiers must be migrated by the end of the year.1
- The Federal Office of Public Health sets its expectationAll data to be transferred to the provider CARA, at Post Sanela's cost.2
- A parliamentary health committee asks for migration at no cost to patientsCommittee for Social Security and Health of the National Council.2
- Attack on PK Softech AGA software supplier to several Swiss pension funds, based in Reinach.3
- The Confederation confirms a data leak affecting PublicaThe scope of the affected data is still being determined.4
- The City of Zurich pension fund reports its members' data stolenIt had sent data to the supplier to prepare a system change planned for 2027.5
- The FDPIC opens a formal investigation into PK SoftechThe investigation is ongoing.6
- Deadline for Swiss Post users to chooseTransfer, move to the Swiss Post app, or download.7
- The platform closesAbout six months after the announcement.1
When the Lender Leaves: Swiss Post
A borrowed debt does not need an incident to fall due. Swiss Post is closing its electronic patient record platform at the end of 2026, citing falling demand.1 Users can transfer their dossier to another certified provider, move documents to the Swiss Post app, or download them, in which case Swiss Post warns that they carry full responsibility for protecting the data.7
Here the public side stepped in. The Federal Office of Public Health stated that dossier holders are entitled to keep their data available, and expects Post Sanela to transfer it all to CARA at its own cost.2
When the Lender Is Breached: Publica
At the end of September 2026, attackers broke into the systems of PK Softech AG, a software supplier to several Swiss pension funds.3 On 8 October, the Confederation confirmed a data leak affecting Publica, the pension fund of the federal administration.4 According to Publica, the data that may have been taken includes names, dates of birth, AHV numbers, addresses, salary and pension data, and information on partners.8
The pension funds were not attacked themselves. PK Softech states that the attack targeted its own infrastructure, not its clients' systems.9 The data concerned was data held at the supplier.
Generic illustration, based on PK Softech's statement that the attack targeted its own infrastructure.9 It does not describe which data any client had sent.
Why the data was there has not been fully published. Speaking in general terms, an expert interviewed by SRF explains that vendors often host the software for their clients, or need real data to test a system or fix a fault.10 The City of Zurich pension fund had sent data to prepare a system change planned for 2027.5 Holding client data is part of what such suppliers do. That is why the case is useful: it shows where borrowed debt sits.
Outside the client's control
- The attackWhether, and when, a supplier is breached.
- The closureWhether a provider keeps a service running.
- The timingThe due date of the debt.
The client's decision
- How muchWhich data sits with the supplier, real or pseudonymised.
- How longWhether each copy has an end date.
- How it comes backExit and deletion terms, written before signing.
The Debt Stays Yours
Swiss law is consistent on who repays.
Security is shared
Controller and processor must both ensure security appropriate to the risk.11
You must satisfy yourself
The controller must check that the processor can guarantee data security. Subcontractors need its prior approval.11
Responsibility stays
The institution keeps the same responsibility as if it did the work itself, and must weigh a change of provider at selection.12
Know your critical data
Critical data must be identified and managed throughout its lifecycle.13
For finance the risk is concrete: according to FINMA's Risk Monitor 2025, as summarised by the law firm MME, almost half of cyber attacks on financial institutions go through third parties.14 In the language of debt: you may borrow, but you remain the debtor.
The Four Questions You Will Be Asked
When a borrowed debt is called, the first questions are not about firewalls. According to reporting on the FDPIC investigation, it wants to establish four things.15 Whatever its outcome, these are the questions any organisation would face after an incident at a supplier.
What data was entrusted?
Which personal data the pension funds had handed to the supplier.
Answered by a register of copies, not a list of vendors.
On what basis?
The legal basis for each transfer.
Answered by a documented purpose for every copy.
How was it done?
How the parties actually carried out the transfers.
Answered by knowing the channel, the format and who approved it.
What actually left?
Which information leaked, and in what quantity.
Answered only if you knew what was there before the incident.
All four are data governance questions. A security team protects systems. Knowing which data sits where, why, and since when is a different job, and often the missing one.
2026 figure to late October. Galaxus notes that most reports are attributed to human error.15
Keeping the Debt Small
You cannot avoid borrowed debt. You can keep it small, visible and short. Follow one pledged copy through its life to see where each step can be controlled.
An illustration, not a description of any specific case. Real steps depend on the supplier and the contract.
Keep a register of what you pledged
Not a vendor list: a list of copies. Which data, held by whom, why, since when, until when.
Pledge less
Use pseudonymised data for tests where possible, as the SRF expert recommends, and send only the fields needed.10
Give every copy a due date
Write the end date and the deletion duty into the agreement. A copy without an end date is a loan without a maturity.
Keep the right to look
Secure audit rights in the contract. It is how you satisfy yourself, as article 9 FADP requires.10
Agree the exit before you sign
How the data comes back, in what format, how fast, who pays and who decides.
Make the data owner sign the loan
Sending data to a supplier is a data decision, not only a procurement or IT one.
Your First Questions
Every organisation borrows in different ways. Tick the forms of borrowing that exist in your organisation. The list of questions adapts.
For the next ninety days, three moves deliver most of the value. First, build the register of pledged copies for critical data, starting with suppliers that hold full extracts. Second, put an end date on every copy made for a project, and ask for deletion confirmation for projects already closed. Third, check that contracts for critical platforms state how the data comes back.
Borrow, but Know What You Owe
Borrowed debt is not a reason to stop buying software or using platforms. It is a reason to keep the books. The organisations in these two cases did not choose when the debt would be called. What every organisation can choose is how much it pledged, for how long, and whether it can answer the four questions when they come.
Borrowed debt is only one form of data debt. In coming briefings, I will look at the others: how organisations take them on, why they stay invisible, and how they are repaid.
Sources & references
- Netzwoche, Ende 2026 ist Schluss mit der EPD-Plattform der Post, 25 June 2026. netzwoche.ch
- Federal Office of Public Health, E-GD: Meilensteine und Aktuelles, entry of 25 June 2026 on the Post Sanela exit. bag.admin.ch
- blue News, Hackers steal data and blackmail Switzerland, 20 October 2026, citing Tages-Anzeiger. bluewin.ch
- Swiss Confederation, Cyber attack on Publica software supplier: data leak confirmed, press release, 8 October 2026. admin.ch
- finews.com, Hacker Attack on IT Service Provider Widens Its Reach, 16 October 2026, quoting the pension fund of the City of Zurich (PKZH). finews.com
- Digital Policy Alert, FDPIC opened investigation into PK Softech AG, 22 October 2026, referencing the FDPIC's official communication. digitalpolicyalert.org
- IamExpat, Swiss Post to scrap electronic patient record service for 70.000 users, 14 October 2026. iamexpat.ch
- SRF, Pensionskasse des Bundes: Name, AHV-Nummer, Lohn. Angreifer erbeuten sensible Daten, October 2026, quoting Publica's information to its insured members. srf.ch
- blue News, Tens of thousands of pension fund records stolen: here's what you need to do now, October 2026. bluewin.ch
- SRF, Pensionskasse des Bundes: Wie konnten heikle Daten bei externer Softwarefirma landen?, October 2026, interview with cybersecurity expert Marc Ruef. srf.ch
- Federal Act on Data Protection of 25 September 2020 (SR 235.1), articles 8 and 9. fedlex.admin.ch
- FINMA, Circular 2018/3 "Outsourcing", in force 1 April 2018, last amended 4 November 2020, chapter V on requirements for outsourcing companies, including responsibility and the selection of the service provider. finma.ch
- FINMA, Circular 2023/1 "Operational risks and resilience: banks", in force 1 January 2024, chapter IV.D on critical data. finma.ch
- MME, Cloud services at banks and securities firms, part 1, 3 December 2025, summarising FINMA's Risk Monitor 2025 of 17 November 2025. mme.ch · finma.ch
- Galaxus, After the pension fund hack: what happens now?, 27 October 2026. galaxus.ch



