securityprivacy

When Governments Leak Your Identity: 8.8 Million Lessons

Denmark's Central Register exposed 8.8 million citizens via a third-party access breach. Here's what that means for personal identity data storage.

The Most Complete Dataset About You

Denmark’s Central Person Register — known as CPR — holds the official identity record for every Danish citizen: name, address, national identification number, family relationships, and citizenship status.

Recently, 8.8 million records from the CPR were exposed through unauthorized third-party access. That’s effectively the entire country.

No organization stored more complete personal identity data about Danish citizens than the government. No single breach could have been more comprehensive.

This isn’t a uniquely Danish problem.

Why Centralized Identity Databases Are a Structural Target

National identity databases are a natural consequence of modern government administration. Benefits systems, tax collection, voter registration, healthcare, immigration records — all require governments to maintain authoritative records about their citizens.

The same properties that make these databases useful for administration make them extraordinarily valuable to attackers:

Completeness. A corporate breach might expose a subset of customers in a specific product. A national identity database is designed to be comprehensive by definition.

Linkability. A national ID number or social security number is a key that unlocks records across dozens of other systems. Stealing the number alone — even without the name or address — creates meaningful exposure.

Longevity. You can change a password or a credit card number. You cannot change your national identification number.

High confidence data. A criminal’s random email list has errors and stale records. A government identity database is authoritative, regularly updated, and legally accurate.

For a data broker, an identity thief, or a state actor, government identity databases are a tier above anything a private company holds.

How Third-Party Access Creates the Exposure

Modern government IT is not monolithic. The same agencies that hold national identity databases also depend on contractors, software vendors, managed service providers, and cloud infrastructure. Each of these third parties represents a potential entry point.

The Danish breach occurred via third-party access — not through a direct attack on the government’s own systems, but through a vendor or partner with authorized access to the data.

This pattern recurs across major government breaches:

  • The US Office of Personnel Management breach exposed 21 million federal employee records through a contractor’s compromised credentials
  • NHS supplier breaches in the UK repeatedly exposed patient data through vendors rather than the NHS itself
  • Brazil’s national CPF database exposure was traced back to a government API with inadequate authentication controls

Third-party access is not an inherent flaw. It’s an inherent property of how complex organizations work. The flaw is when third-party access is not scoped, monitored, and audited with the same rigor as direct access.

What This Means for the Data You Don’t Control

The uncomfortable reality is that most national identity data is not under your control. You didn’t choose to have your records stored in Denmark’s CPR, the US Social Security Administration’s database, India’s Aadhaar system, or your country’s equivalent. Participation in modern society requires being in these systems.

What you do control is:

What you expose beyond the minimum. When a website or app asks for your national ID number, ask why. Many services ask for it out of habit rather than legal necessity. Providing it to a third party is an additional point of exposure.

Where you store copies of identity documents. Your physical passport, ID cards, birth certificate, and tax documents exist on paper. Photographed versions exist on your phone. Uploaded versions exist in whatever apps and services you’ve used to scan or verify your identity. Each copy is a potential exposure point.

Which services you’ve linked to identity verification. Many apps now require identity verification through third-party services. That verification data — often including a photo of your ID and a selfie — is stored by those vendors, subject to their own security practices.

The Identity Theft Pipeline After a Government Breach

When a government identity database is compromised, the data doesn’t sit still. Here’s the typical lifecycle:

Initial sale on dark web markets. Fresh government identity records are sold within days or weeks of a breach, often in bulk. The price depends on the country, the completeness of the records, and how recently the data was validated.

Credential stuffing and account takeover. National ID numbers are used to verify identity on bank websites, government portals, and insurance systems. With the full record, attackers can pass identity verification checks.

Synthetic identity fraud. A criminal combines a real national ID number with a fabricated name and address to create a “synthetic identity” — real enough to pass automated checks, fictional enough to avoid detection for months.

Targeted phishing. With name, address, and ID number, attackers can craft phishing messages that appear legitimate because they already know accurate personal details about the target.

Long-tail exploitation. Government identity data doesn’t expire the way stolen passwords do. Records from a breach this year may be used for fraud years later.

Minimizing Your Identity Exposure

You can’t opt out of government databases. You can limit what else you expose:

Audit which apps hold copies of your identity documents. Before uploading a photo of your ID to any service, understand where it’s stored, how it’s protected, and what happens to it when you close your account.

Use purpose-built secure storage for sensitive documents. Copies of your passport, national ID, birth certificate, and tax documents warrant more care than a note in a free app. Use a service that explicitly addresses how it protects sensitive files, keeps them encrypted at rest, and doesn’t use your content to show ads or train AI systems.

Daftei stores files with AES-256 encryption at rest and TLS 1.3 in transit, never shows ads, and doesn’t sell user data or use stored content to train external AI models. For documents you’d classify as genuinely sensitive, the difference between a service with those commitments and a general-purpose tool matters.

Enable the strongest authentication on your bank and government portals. When government identity data is compromised, the subsequent attacks typically target banking and government service accounts. Passkeys, hardware security keys, or authenticator apps are significantly more resistant to identity-based fraud than SMS verification.

Monitor for unusual activity. Many countries now offer some form of credit monitoring or identity alert service. Knowing quickly that something is wrong limits the damage.

Keep identity document copies out of consumer cloud services. A scan of your passport stored in a general-purpose cloud folder has different risk exposure than the same scan stored in a service designed for sensitive personal documents, with appropriate access controls and no third-party advertising integrations.

The Principle of Data Minimization

The Danish breach raises a question governments and their regulators should answer more urgently: what is the minimum data footprint for each function?

A government service that needs to verify you’re eligible for a benefit doesn’t necessarily need to retain the verification document indefinitely. A contractor that needs to query a database to process a transaction doesn’t necessarily need direct access to the underlying records.

Data minimization, vendor access auditing, and shorter retention windows are all well-understood practices in data protection frameworks like GDPR. They’re also practices that require institutional will to implement consistently.

The 8.8 million people whose records were exposed didn’t choose the architecture of the system that held their data. That asymmetry — between people whose data is at risk and institutions making design decisions — is worth keeping visible.

What You Can Do Right Now

The data the government holds about you is largely fixed. The data you generate yourself — the files, photos, notes, and records that constitute your personal history — is under your control.

Three concrete steps worth taking this week:

1. Inventory where copies of your identity documents live. Phone camera roll, email attachments, app uploads, cloud folders — go through each one and decide whether each location is appropriate for how sensitive that document is.

2. Enable two-factor authentication on your government service portals. Most countries now offer app-based or hardware-based second factors for tax, benefits, and healthcare portals. Use them.

3. Freeze your credit if you haven’t already. A credit freeze prevents new accounts from being opened in your name even if someone has your full identity record. In the US, it’s free and reversible at all three major bureaus.

These don’t address what governments store about you. They do limit what an attacker can do with it.

Your memories deserve better than an ad platform.

Try daftei free →
← All posts