Reporting: Analytics and Audit Data Logging for External Reporting (UXPROD-330)

[UXPROD-336] Flag User Personal Data (GDPR) Created: 05/Mar/18  Updated: 13/Dec/18  Resolved: 13/Dec/18

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Reporting: Analytics and Audit Data Logging for External Reporting

Type: Story Priority: P3
Reporter: VBar Assignee: Matt Reno
Resolution: Done Votes: 0
Labels: analytics, transactdata
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to UXPROD-331 Okapi Transactional Data Extraction Closed
Epic Link: Reporting: Analytics and Audit Data Logging for External Reporting
Front End Estimator: VBar
Back End Estimate: Medium < 5 days
Back End Estimator: VBar
Development Team: EBSCO - FSE

 Description   

Identify any transaction data that could later require retrieving under the requirements of GDPR.

In particular, any transactions containing user identifiable personal data will recognized in order to allow it to potentially be located in compliance with GDPR requests. (right to be forgotten, right to access, right to data portability).

It is sufficient to decorate the transaction with metadata that identifies it as subject to GDPR.

A possible solution is to use JSONPath to define patterns that can be used to locate the presence of user sensitive in the payload. Transactions matching any of these patters will be flagged, message metadata, as candidates for potential cleanup later due to GDPR requests.


Generated at Fri Feb 09 00:07:25 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.