Log personnal data access

[erichard]

One requirement of GDPR is the ability to provide a report of who and when someone get access to a personal data. Have you plan something for this ?

Some ideas :

• Use a monolog channel to allow manual recording
• Annotation in controller action to tell this action will display personal data, so log who/when (and maybe what)

[mogilvie]

"someone" could be a user of the app, or could be a db admin outside of the php framework. The bundle can't monitor all edge cases. However, if we fire an event on the kernal loader then we could at least allow a subscriber to log that event. I will include that on next update. Thanks.

…

-----Original Message----- From: "Ξrwᴧn Richᴧrd" <notifications@github.com> To: mogilvie/GdprBundle <GdprBundle@noreply.github.com> Cc: Subscribed <subscribed@noreply.github.com> Sent: Wed, 23 May 2018 10:57 PM Subject: [mogilvie/GdprBundle] Log personnal data access (#10) One requirement of GDPR is the ability to provide a report of who and when someone get access to a personal data. Have you plan something for this ? Some ideas : * Use a monolog channel to allow manual recording * Annotation in controller action to tell this action will display personal data, so log who/when (and maybe what)

-- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: #10

[mogilvie]

I've added an event dispatcher to the subscriber for load and update events to allow people to implement their own solution immediately.
Longterm the history entity will be used to record transactions against personal data fields. The difficulty is that recording the name of the individual who made the transaction is storing more personal_data again. The history entity will store an fk and we will map that to the user entities via config.