Security

Legitimate Access

On 5 October, Danish authorities disclosed a breach of the Central Person Register (CPR), the national register behind every Danish personal identification number. Personal data for around 8.8 million records was extracted. That’s most of the register, which also includes deceased people and people who have emigrated. The data included names, addresses and CPR numbers.

What’s striking is how it happened. This wasn’t a break-in through a firewall. It came through the lawful query access of a private company that was legitimately allowed to look people up in the register. Over around ten days in September, that access was used to run automated searches at a scale far beyond normal use. The activity was detected on the evening of 2 October, the company’s access was cut off, and the Danish Data Protection Agency was notified.

According to the ministry, the attackers stayed within the limits of what private companies are allowed to retrieve. Officials have said it’s too soon to say whether new CPR numbers will be issued. For a national identifier, that would be a huge undertaking.

The Problem With “Legitimate”

We spend a lot of effort keeping attackers out. Much less goes into watching what authorised partners do with access they’re entitled to. It’s a theme on this blog: OAuth tokens for a SaaS integration, an outsourced help desk, and now a partner’s API access to a national register.

What I’d look at, especially if you expose data to partners through APIs:

  1. Baseline normal behaviour for every partner, and alert on big deviations: volume, time of day, query patterns. A partner that normally looks up hundreds of records a day shouldn’t be able to look up millions without anyone noticing.
  2. Rate limits and quotas that reflect the business purpose, not just technical capacity.
  3. Purpose-bound access. Can a partner only query the records it has a legitimate reason to see?
  4. Reconsider identifiers that work as secrets. If a number is used both to identify people and to authenticate them, losing it is a much bigger problem.

More Information