Method of handling personal information in a backup data and a backup system
The method and system for handling personal information in backup data systems address the challenge of securely deleting sensitive data by using user-specific encryption keys, enabling efficient and secure data deletion within backup systems, thus enhancing security and GDPR compliance.
Patent Information
- Application Number
- PCT/EP2023/063241
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-05-17
- Publication Date
- 2024-11-21
AI Technical Summary
Current methods for handling personal information in backup data systems face challenges in securely deleting sensitive data without rewriting the backup, particularly in compliance with GDPR regulations, which can be complex and costly.
A method and system that detect personally identifiable information (PII) in backup data, encrypt it with user-specific keys, and store these keys in a key table, allowing for secure deletion of sensitive data by removing user keys without restoring or reading the backup data, ensuring enhanced security and compliance.
This approach provides secure and efficient deletion of sensitive data from backup storage without rewriting the backup, enhancing data protection and compliance with GDPR regulations by leveraging multiple unique encryption keys based on user preferences and time, ensuring data integrity and availability.
Smart Images

Figure EP2023063241_21112024_PF_FP_ABST
Abstract
Description
[0001] METHOD OF HANDLING PERSONAL INFORMATION IN A BACKUP DATA AND A BACKUP SYSTEM
[0002] TECHNICAL FIELD
[0003] The disclosure relates generally to handling personal data, and more particularly, the disclosure relates to a method of handling personal information in a backup data and a backup system.
[0004] BACKGROUND
[0005] Sensitive data refers to confidential information that must be protected in an organization's network from an external entity or within the organization’s network unless they have permission to access it. The General Data Protection Regulation, GDPR defines sensitive data as personal data that directly identifies an individual including the individual’s name, surname, phone number, social security number, driver's license number, or any other personally identifiable information, PII. The personal data include Sensitive Personal Data, Protected Health Information, PHI, Education Records, Customer Information, Confidential Personnel Information, Card Holder Data, Confidential Information, and the like. To prevent unauthorized access or data breaches, it is important to restrict access to sensitive data only to authorized personnel and implement effective data security measures and information security practices. However, the GDPR has increased scrutiny over the protection of sensitive data, leading to the need for better data management, third-party risk management, and improved cybersecurity measures, where the GDPR compliance may increase the financial costs for the data owner, potentially reaching several million United States Dollar, USD.
[0006] The current technology for the protection of personal data uses GDPR with pseudonymous data which replaces any information that directly identifies information of an individual with a pseudonym or other words. The information of the individual may include a name, a contact number, and a contact address. Under the GDPR, the personal data can be classified as directly identifying information or pseudonymous data. The GDPR encourages the use of pseudonymous data because it lowers the risk of data breaches that could have adverse impacts on individuals.
[0007] Confidentiality, Integrity, and Availability, CIA triad model is a widely used framework that guides policies for data sensitivity within organizations. Confidentiality is a key factor in maintaining privacy and preventing unauthorized access to sensitive information. The organizations may use one or more measures such as data encryption, passwords, two-factor authentication, biometric verification, security tokens, key fobs, soft tokens, limiting where information appears, limiting the number of times information can be transmitted, storing on air-gapped computers, storing on disconnected storage devices, stored in hard copy and the like, to provide access to the sensitive information. Integrity is an important factor in protecting the sensitive data, which maintains the consistency, accuracy, and trustworthiness of data over a lifecycle of the sensitive data, which may be achieved with file permissions, user access control, audit logging, and version control, over its lifecycle, cryptographic checksums, backups, and redundancies. Even when the data is breached, the data remains unchanged or unaltered in transit by unauthorized people, maintaining the integrity of the data. Availability is also an important factor to ensure that sensitive information and sensitive data are accessible to the concerned persons. The availability may involve maintaining hardware and making repairs immediately, patching software as soon as possible, providing adequate communication bandwidth, implementing fast and adaptive disaster recovery with a comprehensive disaster recovery plan, safeguarding against data loss or interruption during natural disasters and fire, extra security equipment and software such as firewalls and additional servers that guard against downtime and prevent denial-of-service, DoS attacks.
[0008] Another existing technique uses data privacy to protect the PII by information privacy laws. The privacy law collects and uses the PII by both public and private organizations. The privacy laws ensure that organizations collect personal data in a transparent and lawful manner, including the purpose of the data collection, and how the collected data to be used. The GDPR requires organizations to obtain the consent of each of the individuals for collecting and using their PII, especially while providing data breach notifications, appointing a data protection officer, and anonymizing data for privacy. In addition, the GDPR includes a provision “The right to erasure”, also known as the “right to be forgotten”, which provides individuals the right to request that organizations delete the sensitive information and sensitive data or the personal data. While the GDPR does not require any request from the organizations to delete an individual's data. Where removing the personal data from the backup can be more complex than deleting the data in a primary storage, which involves reading and rewriting the personal data in the backup. Therefore, there arises a need to address the aforementioned technical problem / drawbacks in handling personal information in a backup data and a backup system.
[0009] SUMMARY
[0010] It is an object of the disclosure to provide a method of handling personal information in a backup data and a backup system while avoiding one or more disadvantages of prior art approaches.
[0011] This object is achieved by the features of the independent claims. Further, implementation forms are apparent from the dependent claims, the description, and the figures.
[0012] According to a first aspect, there is provided a method of handling personal information in a backup data. The method includes detecting one or more pieces of personally identifiable information, PII, in a data to be backed up. The method includes obtaining one or more first keys for each user to which any of the pieces of PII relates. The method includes encrypting each of the detected pieces of PII using one of the first keys associated with a user to which said piece of PII relates when the data is written into a backup storage. The method includes storing the first keys in a key table. The method includes storing in a PII table a location in the backup storage where each of the pieces of PII is written. All entries in the PII table related to each particular user are encrypted by a second key associated with said user.
[0013] This method provides an optimal solution for leveraging different encryption keys based on the personal data of each user and the associated time. This method provides multiple unique keys for each user where the backup storage encrypts the personal data with specific topics or user preferences, ensuring enhanced security and protection. This method deletes the sensitive data of a specific user from the backup storage without restoring or reading the backup data. By deleting the specific user’s keys from the key table, the sensitive data of the user is safely and effectively deleted from the backup storage without rewriting the backup data.
[0014] Optionally, the method further includes deleting one or more first keys associated with a user from the key table that were used for encrypting one or more pieces of PII related to the user based on a PII deletion request of said user.
[0015] Optionally, the one or more first keys associated with a user include a first key related to certain period of time relevant for PII of the user and / or a first key related to certain type of PII of the user. Optionally, the PII deletion request of the user includes an indication of a period of time and / or a type of PII of the user, and the method further includes determining one or more first keys to be deleted from the key table based on the indication of the period of time and / or the type of PII of the user in the PII deletion request.
[0016] Optionally, the second key associated with a user is identical to one of the first keys associated with the user.
[0017] Optionally, the key table is stored in a storage media being separate from a backup storage media for storing the backup data and / or outside the backup storage.
[0018] According to a second aspect, there is provided a backup system. The backup system includes a personally identifiable information, PII, detector, a key manager, and a controller. The PII detector configured for detecting one or more pieces of personally identifiable information, PII, in a data to be backed up into a backup storage. The key manager configured for obtaining one or more first keys for each user to which any of the pieces of PII relates and storing the first keys in a key table. The controller is configured for encrypting each of the detected pieces of PII using one of the first keys associated with a user to which said piece of PII relates when the data is written into the backup storage, and storing a location in a PII table in the backup storage where each of the pieces of PII is written. All entries in the PII table related to each particular user are encrypted by a second key associated with said user.
[0019] The backup system provides an optimal solution for leveraging different encryption keys based on the personal data of each user and associated time. The backup system provides multiple unique keys for each user where the backup storage encrypts the personal data with specific topics or user preferences, ensuring enhanced security and protection. The backup system deletes the sensitive data of a specific user from the backup storage without restoring or reading the backup data. By deleting the specific user’s keys from the key table, the sensitive data of the user is safely and effectively deleted from the backup storage without rewriting the backup data.
[0020] Optionally, the key manager is further configured for deleting one or more first keys associated with a user from the key table that were used for encrypting one or more pieces of PII related to the user based on a PII deletion request of said user. Optionally, the one or more first keys associated with a user includes a first key related to certain period of time relevant for PII of the user and / or a first key related to certain type of PII of the user.
[0021] Optionally, the PII deletion request of the user includes an indication of a period of time and / or a type of PII of the user, and the key manager is configured for determining one or more first keys to be deleted from the key table based on the indication of the period of time and / or the type of PII of the user in the PII deletion request.
[0022] Optionally, the second key associated with a user is identical to one of the first keys associated with the user.
[0023] Optionally, the key table is stored in a storage media being separate from a backup storage media for storing the backup data and / or outside the backup storage.
[0024] Therefore, in contradistinction to the prior art, according to a method of handling personal information in a backup data and a backup system provides the solution to delete the sensitive data of a person without reading the backup data.
[0025] These and other aspects of the disclosure will be apparent from the implementation(s) described below.
[0026] BRIEF DESCRIPTION OF DRAWINGS
[0027] Implementations of the disclosure will now be described, by way of example only, with reference to the accompanying drawings, in which:
[0028] FIG. 1 is a block diagram that illustrates a backup system in accordance with an implementation of the disclosure;
[0029] FIG. 2 illustrates a system view of handling personal identifiable information in a backup system in accordance with an implementation of the disclosure;
[0030] FIGS. 3 A and 3B are flow diagrams that illustrate a method of handling personal information in backup data in accordance with an implementation of the disclosure; and FIG. 4 is an illustration of a computer system (e.g. data storage) in which the various architectures and functionalities of the various previous implementations may be implemented.
[0031] DETAILED DESCRIPTION OF THE DRAWINGS
[0032] Implementations of the disclosure provide a method of handling personal information in a backup data and a backup system.
[0033] To make solutions of the disclosure more comprehensible for a person skilled in the art, the following implementations of the disclosure are described with reference to the accompanying drawings.
[0034] Terms such as "a first", "a second", "a third", and "a fourth" (if any) in the summary, claims, and foregoing accompanying drawings of the disclosure are used to distinguish between similar objects and are not necessarily used to describe a specific sequence or order. It should be understood that the terms so used are interchangeable under appropriate circumstances, so that the implementations of the disclosure described herein are, for example, capable of being implemented in sequences other than the sequences illustrated or described herein. Furthermore, the terms "include" and "have" and any variations thereof, are intended to cover a non-ex elusive inclusion. For example, a process, a method, a system, a product, or a device that includes a series of steps or units, is not necessarily limited to expressly listed steps or units but may include other steps or units that are not expressly listed or that are inherent to such process, method, product, or device.
[0035] FIG. 1 is a block diagram that illustrates a backup system 100 in accordance with the implementation of the disclosure. The backup system 100 includes a personally identifiable information, PII detector 102, a key manager 104, and a controller 106. The PII detector 102 is configured for detecting one or more pieces of PII, in a data to be backed up into a backup storage 110. The key manager 104 is configured for obtaining one or more first keys for each user to which any of the pieces of PII relates and storing the first keys in a key table 108. The controller 106 is configured for encrypting each of the detected pieces of PII using one of the first keys associated with a user to which said piece of PII relates when the data is written into the backup storage 110, and storing as in a PII table 112 a location in the backup storage 110 where each of the pieces of PII is written. All entries in the PII table 112 related to each particular user are encrypted by a second key associated with said user.
[0036] The backup system 100 provides an optimal solution for leveraging different encryption keys based on the personal data of each user and associated time. The backup system 100 provides multiple unique keys for each user to encrypt PII related to the user and the backup storage 110 encrypts the personal data with specific topics or user preferences with said keys, ensuring enhanced security and protection. The backup system 100 is thereby enabled to delete the sensitive data of a specific user from the backup storage 110 without restoring or reading the backup data, by deleting the related keys from the key table 108. By deleting the specific user’s keys from the key table 108, the sensitive data of the user is safely and effectively deleted from the backup storage 110 without rewriting the backup data.
[0037] Optionally, the key manager 104 is further configured for deleting one or more first keys associated with a user from the key table 108 that were used for encrypting one or more pieces of PII related to the user based on a PII deletion request of said user.
[0038] Optionally, the one or more first keys associated with a user includes a first key related to certain period of time relevant for PII of the user and / or a first key related to certain type of PII of the user.
[0039] Optionally, the PII deletion request of the user includes an indication of a period of time and / or a type of PII of the user, and the key manager 104 is configured for determining one or more first keys to be deleted from the key table 108 based on the indication of the period of time and / or the type of PII of the user in the PII deletion request.
[0040] Optionally, the second key associated with a user is identical to one of the first keys associated with the user.
[0041] Optionally, the key table 108 is stored in a storage media being separate from a backup storage media for storing the backup data and / or outside the backup storage 110.
[0042] FIG. 2 illustrates a system view of handling personal identifiable information in a backup system 200 in accordance with the implementation of the disclosure. The backup system 200 includes personally identifiable information, PII detector system 202. The PII detector system 202 is configured to connect with a key table 204, a PII table 206, and a backup storage 212. The key table 204 includes the first keys of the users, for example, a first key A 208A of a first user, a first key B 208B of a second user and so on, up to a first key N 208N of an Nth user. In another example, the key table 204 includes a plurality of first keys for each of the users, such as first keys Al and A2 for the first user, first keys Bl and B2 for the second user and so on, up to first keys N1 and N2 for the Nth user (not shown). The PII table 206 includes locations in the backup storage 212 where the pieces of PII are written, for example a PII location A 210A where a piece of PII related to the first user is written , a PII location B 210B where a piece of PII related to the second user is written and so on, up to a PII location N 210N where a piece of PII related to the Nth user is written. In another example, the PII table 206 includes a plurality of locations of the PII in the backup storage 212 storing sensitive information related to each of the users. At that, all entries of the PII table 206 related to each particular user are encrypted by a second key associated with said user. Optionally, the second key used for encrypting entries of the PII table 206 associated with a user is identical to one of the first keys associated with the same user from the key table 204.
[0043] The backup storage in FIG. 2 includes a first tape 214A and a second tape 214B to include any of non-sensitive data, first-user-sensitive data, and second-user-sensitive data. Though, the backup storage 210 may be any storage medium such as a magnetic tape, a compact disc, and non-volatile memory cards. Optionally, the backup storage 210 can be any backup medium such as Hard Disk Drive, HDD, Solid State Drive, SSD, or Flash Drive.
[0044] When data is written in the backup system 200, the personal identifiable information, PII detector system 202 is configured to detect pieces of the PII in the data to be backed up and determine a user to which each detected piece of the PII relates. The PII may include the sensitive data and the non-sensitive data of each user. Optionally, the PII detector system 202 feeds the detected PII and an indication of a user to which the detected PII relates, such as the first user, into the backup system 200. The backup system 200 obtains the first key A for the first user to which the PII relates, for example, from a key manager, and stores the first key A in the key table 204. The backup system 200 includes a controller that encrypts each piece of the detected PII related to the first user using the first key A associated with the first user and stored in the PII table 206 in the backup storage 212. The backup system 200 also stores a location of the encrypted PII within the backup storage 212 in the PII table 206. Optionally, the location of the PII in the PII table 206 includes a start position and a size or an end position of the encrypted data, i.e. the encrypted piece of the PII, in the backup storage 212, and an indication of a user to which the encrypted piece of PII relates, such as an Identifier, ID, of the user. Thereby, the PII table 206 stores all locations in the backup storage 212 where the encrypted pieces of PII are written.
[0045] The key table 204 store the first keys used to encrypt the detected PII associated with the users. The PII table 206 store the locations of the encrypted PII in the backup storage 210. Optionally, the PII table 206 is comprised as part of the backup format in the backup storage 210. At that, entries of the PII table 206 related to each particular user are encrypted by a second key associated with said user. The user and / or the backup system may replace the first keys in the key table 204 based on time, i.e. every day, every week, or every month. The key table 204 may be managed by a key manager. The user and / or the backup system may provide separate first keys in the key table 204 for separate images, separate videos, and textual data.
[0046] Optionally, one or more parts of the key table 204 and / or the PII table 206 are encrypted by a key specific to a user. The key specific to the user may be different from data keys, i.e. the first keys associated with the user. The backup system 200 may further use a generic key for encrypting non-sensitive data of each user. Optionally, the backup system 200 stores the nonsensitive data without encryption. The backup system 200 stores the sensitive data and the nonsensitive data in the first tape 214A and 214B. The user may request to delete a particular sensitive data in the backup storage 210, in this case the backup system 200 deletes from the key table 204 a relevant first key associated with the user that was used for encrypting the PII related to the user, rather than physically erasing the sensitive data from the backup storage 210. Optionally, user-specific keys can be stored in a key manager for providing access to and restriction in the backup storage 210. Optionally, if the key table 204 includes a single first key per user, it is enabled to delete of all the sensitive data related to a user from the backup storage 210 by deleting the single first key from the key table 204. The user and / or the backup system may also change the one or more first keys in the key table 204 frequently or in certain time periods which enables to delete certain old sensitive data of the user, but at the same time it is possible to keep one or more first keys per topic for the user in the key table 204 to enable controllable partial sensitive data deletion.
[0047] FIGS. 3 A and 3B are flow diagrams that illustrate a method of handling personal information in a backup data in accordance with the implementation of the disclosure. At a step 302, one or more pieces of personally identifiable information, PII, are detected in a data to be backed up. At a step 304, one or more first keys for each user to which any of the detected pieces of PII relates are obtained. At a step 306, each of the detected pieces of PII is encrypted using one of the first keys associated with a user to which said piece of PII relates, when the data is written into a backup storage. At a step 308, the first keys are stored in a key table. At a step 310, a location in the backup storage where each of the pieces of PII is written is stored in a PII table. At that, all entries in the PII table related to each particular user are encrypted by a second key associated with said user.
[0048] This method provides an optimal solution for leveraging different encryption keys for different pieces of the sensitive and personal data of each user so that, for example, to use different keys for different topics of the sensitive data and / or different time periods associated with the sensitive data. This method provides using multiple unique keys for each user to encrypt the sensitive data with specific topics in accordance with user preferences, ensuring enhanced handling, security, and protection of the sensitive data in the backup storage. This method allows efficient deleting a specific sensitive data of a specific user by simple deleting encryption keys from the key table without restoring or reading the backup data. By deleting the specific user’s keys from the key table, the sensitive data of the user is safely and effectively deleted from the backup storage without timely processes of restoring and decrypting the sensitive data from the backup storage.
[0049] Optionally, the method further includes deleting one or more first keys associated with a user from the key table that was used for encrypting one or more pieces of PII related to the user based on a PII deletion request of said user.
[0050] Optionally, the one or more first keys associated with a user includes a first key related to certain period of time relevant for PII of the user and / or a first key related to certain type of PII of the user.
[0051] Optionally, the PII deletion request of the user includes an indication of a period of time and / or a type of PII of the user, and the method further includes determining one or more first keys to be deleted from the key table based on the indication of the period of time and / or the type of PII of the user in the PII deletion request.
[0052] Optionally, the second key associated with a user is identical to one of the first keys associated with the user.
[0053] Optionally, the key table is stored in a storage media being separate from a backup storage media for storing the backup data and / or outside the backup storage. For example, it is advantageous when the key table is stored in a faster storage media as compared with the backup storage media.
[0054] FIG. 4 is an illustration of a computer system (e.g. a backup system) in which the various architectures and functionalities of the various previous implementations may be implemented. As shown, the computer system 400 includes at least one processor 404 that is connected to a bus 402, wherein the computer system 400 may be implemented using any suitable protocol, such as PCI (Peripheral Component Interconnect), PCI-Express, AGP (Accelerated Graphics Port), Hyper Transport, or any other bus or point-to-point communication protocol (s). The computer system 400 also includes a memory 406.
[0055] Control logic (software) and data are stored in the memory 406 which may take a form of random-access memory (RAM). In the disclosure, a single semiconductor platform may refer to a sole unitary semiconductor-based integrated circuit or chip. It should be noted that the term single semiconductor platform may also refer to multi-chip modules with increased connectivity which simulate on-chip modules with increased connectivity which simulate on- chip operation, and make substantial improvements over utilizing a conventional central processing unit (CPU) and bus implementation. Of course, the various modules may also be situated separately or in various combinations of semiconductor platforms per the desires of the user.
[0056] The computer system 400 may also include a secondary storage 410. The secondary storage 410 includes, for example, a hard disk drive and a removable storage drive, representing a floppy disk drive, a magnetic tape drive, a compact disk drive, digital versatile disk (DVD) drive, recording device, universal serial bus (USB) flash memory. The removable storage drive at least one reads from and writes to a removable storage unit in a well-known manner.
[0057] Computer programs, or computer control logic algorithms, may be stored in at least one of the memory 406 and the secondary storage 410. Such computer programs, when executed, enable the computer system 400 to perform various functions as described in the foregoing. The Memory 406, the secondary storage 410, and any other storage are possible examples of computer-readable media.
[0058] In an implementation, the architectures and functionalities depicted in the various previous figures may be implemented in the context of the processor 404, a graphics processor coupled to a communication interface 412, an integrated circuit (not shown) that is capable of at least a portion of the capabilities of both the processor 404 and a graphics processor, a chipset (namely, a group of integrated circuits designed to work and sold as a unit for performing related functions, and so forth).
[0059] Furthermore, the architectures and functionalities depicted in the various previous-described figures may be implemented in a context of a general computer system, a circuit board system, a game console system dedicated for entertainment purposes, an application-specific system. For example, the computer system 400 may take the form of a desktop computer, a laptop computer, a server, a workstation, a game console, an embedded system.
[0060] Furthermore, the computer system 400 may take the form of various other devices including, but not limited to a personal digital assistant (PDA) device, a mobile phone device, a smart phone, a television, and so forth. Additionally, although not shown, the computer system 400 may be coupled to a network (for example, a telecommunications network, a local area network (LAN), a wireless network, a wide area network (WAN) such as the Internet, a peer-to-peer network, a cable network, or the like) for communication purposes through an I / O interface 408.
[0061] It should be understood that the arrangement of components illustrated in the figures described is exemplary and that other arrangement may be possible. It should also be understood that the various system components (and means) defined by the claims, described below, and illustrated in the various block diagrams represent components in some systems configured according to the subject matter disclosed herein. For example, one or more of these system components (and means) may be realized, in whole or in part, by at least some of the components illustrated in the arrangements illustrated in the described figures.
[0062] In addition, while at least one of these components are implemented at least partially as an electronic hardware component, and therefore constitutes a machine, the other components may be implemented in software that when included in an execution environment constitutes a machine, hardware, or a combination of software and hardware.
[0063] Although the disclosure and its advantages have been described in detail, it should be understood that various changes, substitutions, and alterations can be made herein without departing from the spirit and scope of the disclosure as defined by the appended claims.
Claims
CLAIMS1. A method of handling personal information in a backup data, comprising: detecting one or more pieces of personally identifiable information, PII, in a data to be backed up, obtaining one or more first keys for each user to which any of the pieces of PII relates, encrypting each of the detected pieces of PII using one of the first keys associated with a user to which said piece of PII relates, when the data is written into a backup storage (110, 212), storing the first keys in a key table (108, 204), and storing in a PII table (112, 206) a location in the backup storage (110, 212), where each of the pieces of PII is written, wherein all entries in the PII table (112, 206) related to each particular user are encrypted by a second key associated with said user.
2. The method of claim 1, further comprising: deleting from the key table (108,204) one or more first keys associated with a user that were used for encrypting one or more pieces of PII related to the user based on a PII deletion request of said user.3 The method of claim 2, wherein the one or more first keys associated with a user comprise a first key related to certain period of time relevant for PII of the user and / or a first key related to certain type of PII of the user.
4. The method of claim 3, wherein the PII deletion request of the user comprises an indication of a period of time and / or a type of PII of the user, and the method further comprises determining one or more first keys to be deleted from the key table (108, 204) based on the indication of the period of time and / or the type of PII of the user in the PII deletion request.
5. The method of any of claims 1 to 4, wherein the second key associated with a user is identical to one of the first keys associated with the user.
6. The method of any of claims 1 to 5, wherein the key table (108, 204) is stored in a storage media being separate from a backup storage (110, 212) media for storing the backup data and / or outside the backup storage (110, 212).
7. A backup system (100, 200), comprising: a personally identifiable information, PII, detector (102) configured for detecting one or more pieces of personally identifiable information, PII, in a data to be backed up into a backup storage (110, 212), a key manager (104) configured for obtaining one or more first keys for each user to which any of the pieces of PII relates and storing the first keys in a key table (108, 204), and a controller (106) configured for: encrypting each of the detected pieces of PII using one of the first keys associated with a user to which said piece of PII relates, when the data is written into the backup storage (110, 212), and storing in a PII table (112, 206) a location in the backup storage (110, 212) where each of the pieces of PII is written, wherein all entries in the PII table (112, 206) related to each particular user are encrypted by a second key associated with said user.
8. The backup system (100, 200) of claim 7, wherein the key manager (104) is further configured for deleting from the key table (108, 204) one or more first keys associated with a user that were used for encrypting one or more pieces of PII related to the user based on a PII deletion request of said user.
9. The backup system (100, 200) of claim 8, wherein the one or more first keys associated with a user comprise a first key related to certain period of time relevant for PII of the user and / or a first key related to certain type of PII of the user.
10. The backup system (100, 200) of claim 9, wherein the PII deletion request of the user comprises an indication of a period of time and / or a type of PII of the user, and the key manager (104) is configured for determining one or more first keys to be deleted from the key table (108, 204) based on the indication of the period of time and / or the type of PII of the user in the PII deletion request.
11. The backup system (100, 200) of any of claims 7 to 10, wherein the second key associated with a user is identical to one of the first keys associated with the user.
12. The backup system (100, 200) of any of claims 7 to 11, wherein the key table (108, 204) is stored in a storage media being separate from a backup storage (110, 212) media for storing the backup data and / or outside the backup storage (110, 212).
Citation Information
Patent Citations
Systems, methods, and apparatuses for storing PII information via a metadata driven blockchain using distributed and decentralized storage for sensitive user information
US20210182423A1
Storing, reading, and encrypting personal identifiable information
US20230090611A1
Cited By
Secure data erasure framework using individualized encryption key management
US20260141108A1
