In the interests of being able to comply with GDPR, it might be useful to be able to filter or process the data prior to the backup file being stored.

Comments

DamienMcKenna created an issue. See original summary.

DamienMcKenna’s picture

DamienMcKenna
Location NH, USA
CreditAttribution: DamienMcKenna at Mediacurrent commented
Title: Provide optional processing / filtering on the backed data » Provide optional processing / filtering on the data prior to storage
Alex Andrascu’s picture

Alex Andrascu CreditAttribution: Alex Andrascu at Intellix commented

This would be an interesting feature to have. What do you have in mind ? Which data do you reckon we should be filtering ?

DamienMcKenna’s picture

DamienMcKenna
Location NH, USA
CreditAttribution: DamienMcKenna at Mediacurrent commented

Drush has some code for sanitizing the output, maybe borrow some ideas from it?
https://github.com/drush-ops/drush/blob/45149a4ddcb4b46cf155e7885c7e3dde...

Maybe add an API for altering the output, then add implementations for altering the output that can be toggled on the profile?

In effect, would this just be more filters?

mgifford’s picture

mgifford
he/him
Primary language English
CreditAttribution: mgifford at OpenConcept Consulting Inc. commented

No idea how you'd scrub this from your backups... I'm curious if some of this should be dealt with in Core, or at least be managed with other modules https://www.drupal.org/project/drupal/issues/2848974

Alex Andrascu’s picture

Alex Andrascu CreditAttribution: Alex Andrascu at Intellix commented

I'm a lagging a bit behind with the research on this but planning to tackle it in the next couple of weeks and will revert then. I still hope we can make this module GDPR compliant by mid May.

mgifford’s picture

mgifford
he/him
Primary language English
CreditAttribution: mgifford at OpenConcept Consulting Inc. commented
Parent issue: » #2971800: Pseudonymisation - Separating PII data from non-PII data

Just happened to check this in the middle of May (almost exactly), how is it going @Alex Andrascu

I wanted to add a related issue to deal with dealing with PII.

Alex Andrascu’s picture

Alex Andrascu CreditAttribution: Alex Andrascu at Intellix commented

@mgifford we're currently working on encrypting the backups and should have a patch ready for review by tomorrow. We'll follow up on pseudonymisation / sanitization after we've sorted encryption. I'm keen to hear your thoughts on how shall we tackle this.

Currently @DamienMcKenna suggestion in #4 is the only candidate.

mgifford’s picture

mgifford
he/him
Primary language English
CreditAttribution: mgifford at OpenConcept Consulting Inc. commented

Thanks @Alex Andrascu!

I don't have much to add but will bring this to @gisle and others in the Rocket.Chat group.

DamienMcKenna’s picture

DamienMcKenna
Location NH, USA
CreditAttribution: DamienMcKenna at Mediacurrent commented
Version: 8.x-4.x-dev » 5.0.x-dev

Moving 8.x-4.x issues to 5.0.x because the older branch is no longer supported.