Skip to content
gluon

Logboek Dataverwerkingen

The standard for how government organisations log what they do with personal data, so a processing can be followed from one system to the next without anyone sharing data. Gluon logs every answer and every action to it.

Read the framework itself

What it asks

The Dutch government standard for logging data processing, managed by Logius.

  1. Log every processing step, so what happened to someone’s data can be traced.

    Every answer and every action is logged as a processing step, beside the hash-chained audit trail.

    Evidence Engine05 Prove
  2. Link each entry to its processing activity, and record a person only by a pseudonym.

    Each entry names the processing activity it belongs to, and a person appears only under a pseudonym.

    Evidence Engine05 Prove
  3. Keep the chain traceable when one system calls another, without sharing the data itself.

    The trace is passed on to every system Gluon calls, so the chain can be followed from both ends.

    Gluon Tools03 Decide

Evidence reused

The parts of Gluon that answer Logboek Dataverwerkingen answer requirements of these frameworks as well, counted requirement by requirement from the mapping on this site.

You interpret

  • Keep your register of processing activities.

    Every entry points to a processing activity in it, with its purpose and legal basis. The register is yours, as the GDPR asks.

  • Decide who may read the logbook, and for how long.

    The logbook stays in your own environment, under your own retention rules.

  • Agree with your chain partners to pass the trace on.

    A chain can be followed only as far as every system passes the trace along.

Questions

Is Gluon certified for Logboek Dataverwerkingen?

No. Gluon is designed around Logboek Dataverwerkingen. Gluon holds none of these certificates. Your organisation is audited; Gluon supplies the controls and the evidence.

Does Gluon replace our own logbook?

No. Gluon logs its own steps as the standard describes, beside those of your other systems. The shared trace links them.

Do our chain partners see our data?

No. Only the trace identifiers travel with a call. Every organisation logs its own steps, in its own logbook.

Is Logboek Dataverwerkingen mandatory?

Version 1.0 is adopted and submitted to Forum Standaardisatie for its list of recommended standards. Following it now means not having to change your logging later.

Where does the evidence live?

In the environment where Gluon runs, your own or ours in Europe. Questions, documents and decision trails stay there, and the audit log streams to your SIEM.

How is the framework mapping counted?

For every framework on this site, each requirement names the part of Gluon that answers it. The mapping counts how many of another framework’s requirements are answered by the parts that answer Logboek Dataverwerkingen. It shows reuse in the architecture, not an audit outcome.

Get started

Send us your questionnaire or the requirement you answer to. The people who build Gluon reply.