Cross-Silo De-Anonymization Under Local Differential Privacy: Threat Model, Phase Transition, and Coordination Necessity
Source published ·Modelwire updated
Original coverage: arXiv cs.LG ↗·How Modelwire adds context

The development
Researchers formalize a critical gap in federated learning privacy guarantees: standard differential privacy composition bounds assume worst-case leakage but don't predict when adversaries can actually re-identify individuals across multiple data silos. This work introduces cross-silo person-level DP and proves de-anonymization exhibits a sharp phase transition, meaning privacy degrades catastrophically once a person's records exceed a threshold number of independent sources. The finding matters for any multi-party ML system (healthcare networks, financial consortia, research collaboratives) where individuals appear in k separate datasets, each independently protected. It reframes privacy risk from theoretical composition arithmetic to empirical identifiability, forcing practitioners to rethink safe k values in real deployments.
Modelwire’s AI-generated summary of coverage from arXiv cs.LG.
Modelwire analysis
ExplainerOur AI-generated reading of the wider context and the next developments to watch.
The sharp phase transition finding is the part worth slowing down on: this isn't a gradual privacy erosion as k increases, it's a cliff. Below a threshold number of data sources, re-identification is practically infeasible; above it, it becomes nearly certain. That distinction changes how you set policy, because a 'safe enough' k today can become catastrophically unsafe with one new data-sharing agreement.
This paper lands alongside the federated learning taxonomy piece ('Beyond Weights and Gradients') published the same day, which documented how FL infrastructure is already fragmenting into domain-specific protocols with distinct privacy-utility trade-offs. That taxonomy work identified the architectural choices practitioners face; this paper now quantifies one of the failure modes those choices can trigger. Together they sketch a more complete picture of where federated deployments actually break. The synthetic data auditing paper ('Phantoms and Disclosures') is also adjacent, since both works push toward empirical identifiability as the operative privacy metric rather than theoretical composition bounds.
Watch whether healthcare or financial consortium deployments begin publishing explicit k-threshold analyses in their privacy impact assessments within the next 12 to 18 months. Adoption of that specific framing in regulatory filings would signal this formalism is crossing from academic to operational use.
This interpretation is generated from the summary above and the archive coverage cited below. Our methodology · Report an error
Coverage behind this analysis
These archive entries ground the connection in our analysis. They are ordered by source publication date, with links to our coverage and the original sources.
·arXiv cs.LG
Beyond Weights and Gradients: A Taxonomy of Federated Learning Messages
Federated learning infrastructure is fragmenting beyond weight-sharing into synthetic data, analytics, and hybrid payloads, but the field lacks unified terminology for these exchanges. This paper formalizes a taxonomy across three message types, mapping their computational, bandwidth, and privacy trade-offs against 202 recent publications. The shift signals that decentralized training is maturing into domain-specific protocols, forcing…
MentionsDifferential Privacy · Federated Learning · Pufferfish Privacy · Cross-Silo Person-Level DP
How this coverage is produced
Modelwire uses AI to generate summaries and context from source headlines, snippets, and selected archive coverage. Automated checks do not verify every claim, and items are not routinely reviewed by a person before publication. Zacaria Solis operates the site. Read the linked source for the full evidence and report errors through our corrections process.
Modelwire summarizes, we don’t republish. The full content lives on arxiv.org. If you’re a publisher and want a different summarization policy for your work, see our takedown page.