SchengenDB: A Data Protection Database Proposal
© 2019, Springer Nature Switzerland AG. GDPR in Europe and similar regulations, such as the California CCPA, require new levels of privacy support for consumers. Most challenging to IT departments is the “right to be forgotten”. Hence, an enterprise must ensure that ALL information about a specific...
| Main Authors: | , , , , |
|---|---|
| Format: | Article |
| Language: | English |
| Published: |
Springer International Publishing
2021
|
| Online Access: | https://hdl.handle.net/1721.1/132280 |
| _version_ | 1826195882707517440 |
|---|---|
| author | Kraska, Tim Stonebraker, Michael Brodie, Michael Servan-Schreiber, Sacha Weitzner, Daniel |
| author_facet | Kraska, Tim Stonebraker, Michael Brodie, Michael Servan-Schreiber, Sacha Weitzner, Daniel |
| author_sort | Kraska, Tim |
| collection | MIT |
| description | © 2019, Springer Nature Switzerland AG. GDPR in Europe and similar regulations, such as the California CCPA, require new levels of privacy support for consumers. Most challenging to IT departments is the “right to be forgotten”. Hence, an enterprise must ensure that ALL information about a specific consumer be deleted from enterprise storage, when requested. Since enterprises are internally heavily “siloed”, sharing of information is usually accomplished by copying data between systems. This makes finding and deleting all copies of data on a particular consumer difficult. GDPR also requires the notion of purposes, which is an access control model orthogonal to the one customarily in SQL. Herein, we sketch an implementation of purposes and show how it fits within a conventional access control framework. We then propose two solutions to supporting GDPR in a DBMS. When a “green field” environment is present, we propose a solution which directly supports the process of ensuring GDPR compliance at enterprise-scale. Specifically, it is designed to store every fact about a consumer exactly once. Therefore, the right to be forgotten is readily supported by deleting that fact. On the other hand, when dealing with legacy systems in the enterprise, we propose a second solution which tracks all copies of personal information, so they can be deleted on request. Of course, this solution entails additional overhead in the DBMS. Once data leaves the DBMS, it is in some application. We propose “sandboxing” applications in a novel way that will prevent them from leaking data to the outside world when inappropriate. Lastly, we discuss the challenges associated with auditing and logging of data. This paper sketches the design of the above GDPR compliant facilities, which we collectively term SchengenDB. |
| first_indexed | 2024-09-23T10:17:15Z |
| format | Article |
| id | mit-1721.1/132280 |
| institution | Massachusetts Institute of Technology |
| language | English |
| last_indexed | 2024-09-23T10:17:15Z |
| publishDate | 2021 |
| publisher | Springer International Publishing |
| record_format | dspace |
| spelling | mit-1721.1/1322802021-09-21T03:51:16Z SchengenDB: A Data Protection Database Proposal Kraska, Tim Stonebraker, Michael Brodie, Michael Servan-Schreiber, Sacha Weitzner, Daniel © 2019, Springer Nature Switzerland AG. GDPR in Europe and similar regulations, such as the California CCPA, require new levels of privacy support for consumers. Most challenging to IT departments is the “right to be forgotten”. Hence, an enterprise must ensure that ALL information about a specific consumer be deleted from enterprise storage, when requested. Since enterprises are internally heavily “siloed”, sharing of information is usually accomplished by copying data between systems. This makes finding and deleting all copies of data on a particular consumer difficult. GDPR also requires the notion of purposes, which is an access control model orthogonal to the one customarily in SQL. Herein, we sketch an implementation of purposes and show how it fits within a conventional access control framework. We then propose two solutions to supporting GDPR in a DBMS. When a “green field” environment is present, we propose a solution which directly supports the process of ensuring GDPR compliance at enterprise-scale. Specifically, it is designed to store every fact about a consumer exactly once. Therefore, the right to be forgotten is readily supported by deleting that fact. On the other hand, when dealing with legacy systems in the enterprise, we propose a second solution which tracks all copies of personal information, so they can be deleted on request. Of course, this solution entails additional overhead in the DBMS. Once data leaves the DBMS, it is in some application. We propose “sandboxing” applications in a novel way that will prevent them from leaking data to the outside world when inappropriate. Lastly, we discuss the challenges associated with auditing and logging of data. This paper sketches the design of the above GDPR compliant facilities, which we collectively term SchengenDB. 2021-09-20T18:21:38Z 2021-09-20T18:21:38Z 2021-01-11T16:38:23Z Article http://purl.org/eprint/type/ConferencePaper https://hdl.handle.net/1721.1/132280 en 10.1007/978-3-030-33752-0_2 Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics) Creative Commons Attribution-Noncommercial-Share Alike http://creativecommons.org/licenses/by-nc-sa/4.0/ application/pdf Springer International Publishing Other repository |
| spellingShingle | Kraska, Tim Stonebraker, Michael Brodie, Michael Servan-Schreiber, Sacha Weitzner, Daniel SchengenDB: A Data Protection Database Proposal |
| title | SchengenDB: A Data Protection Database Proposal |
| title_full | SchengenDB: A Data Protection Database Proposal |
| title_fullStr | SchengenDB: A Data Protection Database Proposal |
| title_full_unstemmed | SchengenDB: A Data Protection Database Proposal |
| title_short | SchengenDB: A Data Protection Database Proposal |
| title_sort | schengendb a data protection database proposal |
| url | https://hdl.handle.net/1721.1/132280 |
| work_keys_str_mv | AT kraskatim schengendbadataprotectiondatabaseproposal AT stonebrakermichael schengendbadataprotectiondatabaseproposal AT brodiemichael schengendbadataprotectiondatabaseproposal AT servanschreibersacha schengendbadataprotectiondatabaseproposal AT weitznerdaniel schengendbadataprotectiondatabaseproposal |