Privacy Breach Detector

Could we create a mechanism to prevent privacy breaches, when releasing new open data in an existing data field in compliance with GDPR?

THE CHALLENGE

Governments have a lot of data, which they want to share with everyone, as basically everyone paid for the collection of this data through taxes. When making datasets available, governmental organizations are afraid of revealing personal data because large amounts of data can be combined.

In order to test whether this is the case, a ‘privacy breach detector’ could be developed that gives an alarm signal (‘privacy breach!’) when the dataset that the organization wants to unlock is added to the detector. This detection is a reason for the organization not to make the dataset available, or to make it available in an adapted form.

DOMAIN EXPERTS PRESENT AT THE HACKATHON

CBS (National Dutch Statistics Bureau)
Algemene Rekenkamer (Dutch Court of Audit, TBC)

 

TOOLBOX

Based on your questions and requests we will enrich the toolbox.

TYPE OF TEAM ELIGIBLE TO APPLY

Pre-Startup
Startup
Mature SME
Corporate
The idea of a privacy breach detector can be developed by various types of teams. For a pre-startup or startup it might be there startup product or service, for a mature SME is might be a solution in their portfolio for a corporate it can be a way to develop skills and have a contribution to software for good.

 

PROTOCOL OR
APPLICATION SOLUTION?

The most likely solution for a privacy breach detector is an app. However, the privacy breach detector can also be an online service or a code library to be used in programming environments.

OPEN SOURCE OR PROPRIETARY

Open Source.
The privacy breach detector is an instrument to built trust. Trust in the fact that the data to-be-published can be published safely. To gain trust instruments needs to be controllable by review of the source code where open source is the way to go. Furthermore, future community driven development and extensions to the privacy breach detector must be possible.

Motivation

One of the objections in publishing open data is the risk of releasing datasets which accidently uncover privacy related information. By checking this to-be-published data with the privacy breach detector it can be proven that it is safe to release the open data with regards to privacy

Ambition and goals

Building trust in publishing open data.

Track record in innovation and working to accelerate with teams/companies

A large experience in publishing open data is available.

CONSORTIUM

Current consortium. The consortium is under construction, and will consist of relevant (public) parties aimed at accelerating your solution.

 

Welcoming. Coming soon.

 

INCUBATION

 

What does the partner offer. The Ministry will be accelerating the best team(s) based on their needs.

 

What do consortium partners offer. Coming soon.

 

CONTENT

Coming soon.

 

MAIN CONTACT

Paul Suijkerbuik – Open Data Expert – Dutch Ministry for the Interior

 

Any questions? Please approach Paul and the entire Track through the community 21st Century Digital Citizenship group: 

Odyssey hackathon 2019

Pre-registration is open

Pre-register now and get the early applicant advantage