Layered encryption of databases in hybrid cloud environments

By using request-based syntax parsing and machine learning models, the encryption technology is dynamically selected for layered encryption, which solves the problem of over- or under-encryption in data storage in existing technologies and optimizes performance, efficiency and security.

CN116432196BActive Publication Date: 2026-11-17INTERNATIONAL BUSINESS MACHINE CORPORATION
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
CN202310031072.1
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2022-01-11
Filing Date
2023-01-10
Publication Date
2026-11-17
Estimated Expiration
2043-01-10

AI Technical Summary

Technical Problem

In existing technologies, the use of single or static encryption technologies for data storage may lead to over-encryption, wasting computing resources and system performance, or insufficient encryption, resulting in security risks, especially in cloud storage environments.

Method used

By employing request-based syntax parsing and machine learning models, multiple elements and their sensitivities in data storage requests are identified, and appropriate encryption technologies are dynamically selected for layered encryption, storage, and decryption of data.

Benefits of technology

The performance, efficiency, and security of data storage have been optimized. By classifying and personalizing encryption based on the sensitivity of different data elements, the problems of over- or under-encryption are avoided, thereby improving the system's security and computing resource utilization.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN116432196B_ABST
    Figure CN116432196B_ABST
Patent Text Reader

Abstract

This disclosure relates to layered encryption of databases in hybrid cloud environments. In one or more embodiments, techniques for layered encryption of data storage are disclosed. These techniques include request-based parsing of electronic database storage requests to identify multiple request elements, and using one or more trained machine learning (ML) models to determine one or more sensitivities associated with the multiple request elements. The techniques also include: identifying one or more encryption techniques for the multiple request elements based on the one or more sensitivities; encrypting data associated with the database storage request using the identified one or more encryption techniques; and storing the encrypted data and one or more associated encryption keys in an electronic database using the electronic database storage request.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to data security, and more specifically, to layered encryption for data storage. Background Technology

[0002] Data security is a challenging and critical issue. Data encryption used for data storage is typically chosen by the client (e.g., during the design phase) and often employs a single or static encryption technique for each dataset. However, in real-world datasets, different data often exhibit varying levels of sensitivity. Applying a single or static encryption technique to each dataset can lead to over-encryption of some data, resulting in wasted computational resources and poor system performance, or insufficient encryption of other data, leading to security risks.

[0003] For example, D. Sangeetha et al.'s "Enhanced Security of PHR System in Cloud Using Prioritized Level Based Encryption" (hereinafter, "Sangeetha") discloses a system for encrypting "Personal Health Records (PHRs)" in which "separate encryption techniques must be performed on text and image data" (Sangeetha's summary). According to Sangeetha, "data classification is performed before storage in one of three 'protection rings': 'Protection ring 3 corresponds to PHR files with a low criticality level. Protection ring 2 corresponds to PHR files with a medium criticality level. Protection ring 1 corresponds to PHR files with an extreme criticality level' (Sangeetha 62-63). Prioritized level-based encryption (PLBE) is applied to all data in each level (ibid., 58, 63). This predefined level-based encryption can lead to over-encryption of some data, resulting in wasted computational resources and poor system performance, or insufficient encryption of other data, leading to security risks." Summary of the Invention

[0004] The embodiment includes a method. The method includes parsing an electronic database storage request based on the request's syntax to identify multiple request elements. The method further includes using one or more trained machine learning (ML) models to determine one or more sensitivities associated with the multiple request elements. The method also includes identifying one or more cryptographic techniques for the multiple request elements based on the one or more sensitivities. The method further includes using the identified one or more cryptographic techniques to encrypt data associated with the database storage request. The method further includes storing the encrypted data and one or more associated encryption keys in an electronic database using the electronic database storage request.

[0005] The embodiment also includes a system comprising a memory and a processor communicatively coupled to the memory, the processor being configured to perform operations. The operations include parsing an electronic database storage request based on the request's syntax to identify multiple request elements. The operations also include using one or more trained machine learning (ML) models to determine one or more sensitivities associated with the multiple request elements. The operations further include identifying one or more cryptographic techniques for the multiple request elements based on the one or more sensitivities. The operations further include encrypting data associated with the database storage request using the identified one or more cryptographic techniques. The operations also include storing the encrypted data and one or more associated encryption keys in an electronic database using the electronic database storage request.

[0006] The embodiments also include a computer program product comprising a computer-readable storage medium having computer-readable program code contained therein, the computer-readable program code being executable by one or more computer processors to perform operations. The operations include request-based syntax parsing of an electronic database storage request to identify a plurality of request elements. The operations also include using one or more trained machine learning (ML) models to determine one or more sensitivities associated with the plurality of request elements. The operations also include identifying one or more cryptographic techniques for the plurality of request elements based on one or more sensitivities. The operations further include encrypting data associated with the database storage request using the identified one or more cryptographic techniques. The operations also include storing the encrypted data and one or more associated encryption keys in an electronic database using the electronic database storage request.

[0007] The aspects of the above embodiments have many technical advantages. For example, existing encryption techniques may use single or static encryption techniques for data storage, which can lead to over-encryption, resulting in wasted computing resources and poor system performance, or insufficient encryption, resulting in security risks. The aspects of the embodiments described above can be used for layered encryption of data storage, wherein data storage (e.g., database storage) encryption and decryption can be optimized for performance, efficiency, and security.

[0008] Optionally, in one or more embodiments described above, identifying the one or more encryption techniques includes: identifying multiple different sensitivities corresponding to the plurality of request elements based on the one or more trained ML models, thereby identifying multiple different encryption techniques. This has the further advantage of classifying request elements by different sensitivities and applying different encryption techniques.

[0009] Optionally, the above method or operation includes: selecting an ML model for each request element from multiple different ML models based on the characteristics of the request element; and analyzing the request element using the corresponding selected ML model to determine the sensitivity corresponding to each request element. This has the additional advantage of using a suitable ML model to determine the sensitivity of each request element.

[0010] Optionally, the above method or operation includes: identifying multiple different encryption techniques for the data storage request based on a determined sensitivity corresponding to each request element, wherein the encrypted data uses the multiple identified different encryption techniques. This has the advantage of applying multiple different encryption techniques to the request based on a determined sensitivity.

[0011] Optionally, in one or more of the above embodiments, identifying one or more encryption techniques includes: determining a pairing of data elements and encryption techniques in the electronic database storage request based on providing one or more of the plurality of request elements to the one or more trained ML models.

[0012] Optionally, in one or more of the above embodiments, the electronic database storage request includes Data Manipulation Language (DML) statements, and parsing the electronic database storage request includes: constructing a syntax tree from the electronic database storage request, and using the syntax tree to identify the plurality of request elements.

[0013] Optionally, identifying one or more encryption techniques in one or more of the above embodiments includes determining the one or more encryption techniques based on one or more sensitivities determined using a second or one or more ML model analyses.

[0014] Optionally, identifying one or more encryption techniques in one or more of the above embodiments includes determining the one or more encryption techniques based on looking up one or more sensitivities in a lookup table.

[0015] Optionally, the above method or operation includes: parsing an electronic database query to identify multiple query elements; determining one or more decryption techniques associated with the multiple query elements; retrieving data from an electronic database using the electronic database query; and decrypting the data using the determined one or more decryption techniques. Further, optionally, determining the one or more decryption techniques associated with the multiple query elements includes retrieving the one or more decryption techniques from an electronic catalog. Attached Figure Description

[0016] Figure 1 A layered encryption computing environment for data storage is illustrated according to one embodiment.

[0017] Figure 2A hierarchical encryption controller according to one embodiment is shown.

[0018] Figure 3 This is a flowchart illustrating a layered encryption for data storage according to one embodiment.

[0019] Figure 4A This is a flowchart illustrating a request for parsing hierarchical encryption for data storage according to one embodiment.

[0020] Figure 4B A syntax tree for parsing a request is shown according to one embodiment.

[0021] Figure 5A This is a flowchart illustrating the classification of request elements for hierarchical encryption used for data storage according to one embodiment.

[0022] Figure 5B A request element for hierarchical encryption for data storage is shown according to one embodiment.

[0023] Figure 6A This illustrates the training and use of a machine learning (ML) model according to one embodiment to classify request elements for hierarchical encryption used for data storage.

[0024] Figure 6B The example further illustrates the training and use of an ML model, according to one embodiment, to classify request elements for hierarchical encryption used for data storage.

[0025] Figure 6C A security matrix for layered encryption of data storage is shown according to one embodiment.

[0026] Figure 7 This is a flowchart illustrating a layered encryption method for data storage according to one embodiment.

[0027] Figure 8 This is a flowchart illustrating the decryption of hierarchical encryption for data storage according to one embodiment.

[0028] Figure 9 A cloud computing environment according to one embodiment is described.

[0029] Figure 10 An abstract model layer according to one embodiment is shown. Detailed Implementation

[0030] As discussed above, existing encryption techniques that use single or static encryption for data storage have significant drawbacks. They can lead to over-encryption, resulting in wasted computing resources and poor system performance, or under-encryption, leading to security risks. This is especially true in cloud storage environments (e.g., public cloud, private cloud, hybrid cloud, or any other suitable cloud storage environment). In cloud environments, the amount of data to be stored is often very large, and unstructured data can be mixed with sensitive information of varying levels. This makes secure data storage extremely challenging.

[0031] One or more techniques disclosed herein can be used for layered encryption of data storage, where data storage (e.g., database storage) encryption and decryption can be optimized for performance, efficiency, and security. For example, data storage requests can be parsed, and each element can be categorized based on its potential sensitivity. In one embodiment, one or more ML models can be used to categorize each element. Furthermore, each element can be paired with a suitable encryption technique. For example, one or more ML models can be used to identify a suitable encryption technique for each element based on its sensitivity. The identified encryption technique can be used to encrypt data for secure storage and to decrypt previously stored data.

[0032] Figure 1 A layered encryption computing environment 100 for data storage is illustrated according to one embodiment. In this embodiment, the computing environment 100 facilitates both secure storage of data (e.g., secure storage of encrypted data) and secure retrieval of data (e.g., secure decryption of stored encrypted data). Starting with secure data storage, a storage request 102 is provided to a request analyzer 112 in the data access layer 110. For example, the storage request 102 may be a database storage request (e.g., a Structured Query Language (SQL) request to store data in a relational database).

[0033] In an embodiment, request analyzer 112 receives storage request 102 and parses the request into multiple elements. For example, request analyzer 112 may analyze Data Manipulation Language (DML) (e.g., SQL) statements and abstract them into multiple elements. This is discussed in the following section... Figure 3 and 4A -B will be discussed further.

[0034] In one embodiment, the request analyzer 112 then provides the parsed storage request 102 (e.g., parsed elements from a DML statement) to the element classifier 114. The element classifier 114 can analyze the parsed storage request 102 and identify an appropriate encryption level for the storage request 102. This can be done as a whole for the storage request 102 (e.g., based on the parsed elements) or for different parsed elements of the storage request 102 (e.g., various elements of a DML statement). This is explained below. Figure 3 and Figure 5A -B Further discussion. Furthermore, in one embodiment, the element classifier 114 may identify one or more suitable ML models for each parsed element of the storage request 102, and the ML models may infer the appropriate encryption level for the statement. See below for more details. Figure 6A -C will be discussed further.

[0035] Element classifier 114 then uses data encryption service 122 in data intermediary layer 120 to encrypt the data for storage. For example, element classifier 114 may identify one or more encryption techniques for encrypting the data identified in storage request 102 (e.g., using a suitable ML model). Data encryption service 122 may use the identified encryption techniques to encrypt the data. This is explained below. Figure 7 Further discussion.

[0036] In an embodiment, the data encryption service 122 then uses the encrypted data storage engine 132 and the encryption key storage engine 134 in the memory access layer 130 to store the encrypted data. For example, the encrypted data storage engine 132 may store the encrypted data in the data storage device 142. The data storage device 142 may be any suitable data repository, including any suitable electronic database (e.g., a relational database, a graph database, or any other suitable electronic database), a cloud storage location (e.g., a public cloud, a private cloud, a hybrid cloud, or any other suitable cloud storage location), an on-premises cluster, or any other suitable data repository. The encryption key storage engine 134 may store encryption keys (e.g., those used to encrypt data) in the encryption key storage device 144. In an embodiment, the encryption key storage device 144 may be part of the data storage device 142 (e.g., a table in an electronic database). Alternatively or additionally, the encryption key storage device 144 may be separate from the data storage device 142.

[0037] Returning to data access layer 110, environment 100 can also facilitate secure data retrieval (e.g., decryption of encrypted data). Query 104 (e.g., DML query) can be provided to query engine 116. In one embodiment, query engine 116 can identify encryption associated with stored data referenced in the query and can decrypt the data using data decryption service 124. For example, query engine 116 can provide query services to users. Query engine 116 can parse the query string and optimize the query path (e.g., rewrite the query string). After obtaining the query results, query engine 116 can invoke data decryption service 124 to decrypt the data. Data decryption service 124 can identify encrypted data in data storage device 142 using encrypted data storage engine 132, identify one or more encryption keys associated with data in encrypted key storage device 144 using encryption key storage engine 134, and decrypt the data. This is explained below. Figure 8 Further discussion.

[0038] Figure 2 A hierarchical encryption controller 200 according to one embodiment is shown. The hierarchical encryption controller 200 includes a processor 202, a memory 210, and a network component 220. The processor 202 typically retrieves and executes programming instructions stored in the memory 210. The processor 202 represents a single central processing unit (CPU), multiple CPUs, a single CPU with multiple processing cores, a graphics processing unit (GPU) with multiple execution paths, etc.

[0039] Network component 220 includes a hierarchical encryption controller 200 and a suitable communication network (e.g., […]). Figure 1 The components necessary for the interface of the communication network that interconnects the different components of the illustrated environment 100, or the communication network that interconnects the environment 100 with other computing systems. For example, network component 220 may include wired, WiFi, or cellular network interface components and associated software. Although memory 210 is shown as a single entity, memory 210 may include one or more memory devices having memory blocks associated with physical addresses, such as random access memory (RAM), read-only memory (ROM), flash memory, or other types of volatile and / or non-volatile memory.

[0040] Memory 210 typically includes program code for performing various functions related to the use of the hierarchical encryption controller 200. The program code is typically described as various functional “applications” or “modules” within memory 210, although alternative implementations may have different functions and / or combinations of functions. Within memory 210, request analyzer 112 facilitates parsing data storage requests, element classifier 114 facilitates classifying the sensitivity of different elements in the data storage request and identifying appropriate encryption techniques, data encryption service 122 facilitates encrypting data identified by the data storage request (e.g., using encryption techniques identified by element classifier 114), and data decryption service 124 facilitates decrypting the stored encrypted data (e.g., identified by the query). See below. Figure 3-8 Further discussion.

[0041] Although the hierarchical encryption controller 200 is shown as a single entity, in embodiments, different components can be implemented using any suitable combination or any other suitable implementation of physical services, cloud computing nodes, and storage locations. For example, the hierarchical encryption controller 200 can be implemented using servers or server clusters (e.g., maintained by the data owner). As another example, the hierarchical encryption controller 200 can be implemented using a combination of compute nodes and storage locations in a suitable cloud environment. For example, one or more components of the hierarchical encryption controller 200 can be implemented using a public cloud, private cloud, hybrid cloud, on-site cluster, or any other suitable implementation.

[0042] Figure 3 This is a flowchart 300 illustrating hierarchical encryption for data storage according to one embodiment. At block 302, a request is made to the analyzer (e.g., Figure 1-2 The request analyzer 112 shown receives a request. In this embodiment, the request is a storage request to store data in a suitable secure storage location (e.g., to store the data in an encrypted format in a suitable electronic database). Figure 1 The storage request 102 shown is alternatively a query to retrieve data from a suitable secure storage location (e.g., decrypting data stored in an encrypted format in a suitable electronic database). Figure 1 The query shown is 104.

[0043] At box 304, the request parser parses the request. In this embodiment, the request may be a suitable DML request (e.g., an SQL request), and the request parser parses the request based on its syntax. For example, the request parser may construct a syntax tree from the DML request and use the syntax tree to parse the request into distinct elements. This is explained below. Figure 4A -B will be discussed further.

[0044] At box 306, the element classifier determines whether the request is a query (e.g., the opposite of a storage request). This is merely an example, and any suitable software or hardware component can determine whether the request is a query (e.g., a request analyzer or any other suitable software or hardware component). If the request is not a query (e.g., it is a data storage request), the process proceeds to box 308. If the request is a query, the process proceeds to box 316.

[0045] At box 308, the element classifier (e.g., Figure 1-2 The element classifier 114 shown classifies the sensitivity of request elements (e.g., storage request elements). For example, the element classifier may receive a parsed DML request generated by the request analyzer in block 304. The element classifier can use the parsed elements to classify the request as a whole or as the sensitivity of individual request elements. For example, the element classifier may select an appropriate ML model for each request element and can use the ML model to classify the sensitivity of the request. This is explained below. Figure 5A -B will be discussed further.

[0046] In box 310, data encryption services (e.g., Figure 1-2 The data encryption service 122 shown in the diagram matches the encryption technology with the request element. For example, as shown below regarding... Figure 5A As discussed in section -B, in this embodiment, the element classifier associates a security level with each element in the request (e.g., a digital security level). The data encryption service can use this security level to determine the appropriate encryption technique for each request element. See below for more details. Figure 7 Further discussion.

[0047] In one embodiment, the data encryption service may select from a variety of encryption technologies, with a trade-off between computational burden and speed in terms of security. For example, stronger encryption technologies are generally more secure but require more computational resources and take longer to encrypt and decrypt. Weaker encryption technologies may be slightly less secure but require fewer computational resources and take less time to encrypt and decrypt. In this embodiment, the data encryption service selects a stronger encryption technology for request elements with a higher security level and a weaker encryption technology for request elements with a lower security level.

[0048] In box 312, the data encryption service encrypts the data. In an embodiment, the data encryption service uses a selected encryption technique (e.g., selected at box 312) to encrypt the data associated with the received request (e.g., the request received at box 302). This generates encrypted ciphertext instead of the data, which can be securely stored.

[0049] In box 314, the data encryption service stores the encrypted data and the encryption key (or multiple keys). For example, the data encryption service may store the ciphertext generated in box 312 in a suitable data storage device (e.g., Figure 1 The data storage device (142) shown in the diagram is used. The data storage device can be a relational database, a graph database, another form of electronic database, or any other suitable storage repository. The data encryption service also stores associated encryption keys or multiple keys (e.g., if multiple encryption technologies are used). For example, the data encryption service may store the keys in a suitable encryption key storage device (e.g., Figure 1 The encryption key storage device 144 shown is used in this device.

[0050] Returning to box 306, if the request is a query, the process proceeds to box 316. In box 316, the data decryption service (e.g., ...) Figure 1-2 The data decryption service 124 shown retrieves the sensitivity of query elements. For example, as discussed above with respect to box 308, data storage requests can be categorized based on the sensitivity of the request elements. In an embodiment, the sensitivity of the storage request is categorized as a whole based on the element. Alternatively or additionally, the corresponding sensitivity of each element of the storage request is categorized separately. In an embodiment, these categorized sensitivities are stored (e.g., in a suitable data storage device) and retrieved by the data decryption service. This is merely an example, and in an embodiment, the decryption technique associated with each query element can be stored directly (e.g., in a catalog, as described below). Figure 8 (As discussed). In this embodiment, the data decryption service skips box 316 and proceeds to box 318 instead.

[0051] In box 318, the data decryption service matches categorized query elements with decryption techniques. As discussed above regarding box 310, and as follows regarding... Figure 7 As discussed, when storing secure data, the encryption service matches the requested element to one or more suitable encryption technologies. In an embodiment, the data decryption service identifies one or more encryption technologies associated with the requested data (e.g., using the sensitivity retrieved at box 316 or directly from the catalog). This is explained below. Figure 8 Further discussion.

[0052] In box 320, the data decryption service retrieves one or more encryption keys associated with the query. For example, the data decryption service may retrieve the encryption key from a suitable encryption key storage device (e.g., Figure 1 The encryption key storage device 144 shown retrieves the encryption key. This will also be discussed below regarding... Figure 8 Further discussion.

[0053] In box 322, the data decryption service decrypts the data. For example, the data decryption service uses one or more encryption keys retrieved in box 318 to generate the original data from the stored ciphertext.

[0054] Figure 4A This is a flowchart illustrating the parsing of a request for hierarchical encryption for data storage according to one embodiment. In one embodiment, Figure 4A Corresponding to Figure 3 The explanation is in box 304. In block 402, a request is made to the analyzer (e.g., Figure 1-2 The request analyzer 112 shown extracts data from the request (e.g., in...). Figure 3 The block 302 shown receives a DML request and constructs a syntax tree to parse the request based on its syntax.

[0055] For example, Figure 4B A syntax tree for parsing a request (e.g., an SQL request) is illustrated according to one embodiment. In this embodiment, request 452 attempts to insert the value (1, 2) into table FOO at positions (COL1, COL2). In this embodiment, the request adds a new row to table FOO with the value 1 at COL1 and the value 2 at COL2.

[0056] The request 452 can be parsed to generate a syntax tree, which has a graphical representation 460 and a textual representation 470. As shown, the body of the request includes an SQL statement, which comprises three elements: an INSERT element, an INTO element, and a Values ​​element. The INSERT element is the action. The INTO element identifies the destination locations, here COL1 and COL2 of table FOO. The Values ​​element identifies the values ​​to be inserted, here decimal values ​​1 and 2. In this embodiment, this is illustrated using a graphical representation 460 and a textual representation 470 of the syntax tree.

[0057] return Figure 4A At box 404, the request parser is asked to extract column elements using a syntax tree. For example, using... Figure 4B In the example shown, the request analyzer can extract column elements COL1 and COL2 from table FOO from request 452. In box 406, the request analyzer provides the column elements to a classification service for classification (e.g., to determine the sensitivity level of the column elements). This is explained below. Figure 5A -B will be discussed further.

[0058] Figure 5A This is a flowchart illustrating the classification of request elements for hierarchical encryption used for data storage according to one embodiment. In one embodiment, Figure 5A Corresponding to Figure 3 Box 306 in the explanation. In box 502, the element classifier (e.g., Figure 1-2The element classifier 114 in the middle of the explanation identifies the extracted elements. For example, the element classifier can receive elements that have already been parsed by the requested analyzer (e.g., as mentioned above regarding...). Figure 4A The request discussed in -B (e.g., in Figure 1 (See storage request 102 or query 104 shown). An element classifier can identify the elements extracted from the parsed request (e.g., using...). Figure 4B (Extracted from the syntax tree shown). These can include different elements of a DML request (e.g., an SQL request), including operations, column and row identifiers, values, and any other suitable elements.

[0059] In box 504, the element classifier selects the appropriate ML model for risk assessment. For example, as shown below... Figure 6A As discussed in -C, multiple ML models can be trained to identify the sensitivity level of a given request element (e.g., a given parsed element in a DML statement). In embodiments, ML models can be trained to identify the sensitivity level of each element in the request or any subset of elements in the request. Alternatively or additionally, the ML model can be trained to identify the sensitivity level of the request as a whole.

[0060] In this embodiment, the element classifier can select a suitable ML model for different elements. For example, the element classifier can select a suitable ML model based on the characteristics of the element or any other suitable factor. The element classifier can use any suitable characteristics, including the element's type (e.g., operation, column identifier, row identifier, value), the element's content (e.g., column name), the element's data type (e.g., floating-point, BLOB, etc.), the element's access frequency, the element's owner (e.g., user-level), the element's data length, the communication method used for the element (e.g., encrypted or unencrypted communication), the data source used for the element (e.g., private cloud, public cloud, etc.), or the operation type (e.g., GRANT, REVOKE, UPDATE, INSERT, etc.). These are merely examples, and the element classifier can use any suitable techniques.

[0061] At box 506, the element classifier can identify the encryption technology of the element. In an embodiment, the ML model identified at block 504 can also be used to identify the corresponding encryption technology. For example, as follows regarding... Figure 6AAs discussed in -C, the ML model can be trained to identify both the sensitivity of an element and the corresponding encryption technique. Alternatively or additionally, the ML model identified at box 504 can identify the sensitivity level of the element (or multiple elements), and the element classifier can use this identified sensitivity level to identify the corresponding encryption technique. For example, the element classifier can use an additional ML model to infer the encryption technique from the identified sensitivity. Alternatively or additionally, the element classifier can use a lookup table or any other suitable technique.

[0062] Figure 5B A request element 540 for hierarchical encryption of data storage according to one embodiment is shown. As discussed above, the element classifier (e.g., Figure 1-2 The element classifier 114 shown uses a number of factors to classify the request elements. In one embodiment, the element classifier can identify the sensitivity of each request element. Further, in one embodiment, the element classifier can also identify the corresponding encryption algorithm of the element (e.g., based on sensitivity and other factors).

[0063] For example, such as Figure 5B As shown, the element classifier can use column names as factors to determine the sensitivity of an element. A column name like "User ID" might suggest the element is insensitive (e.g., because the user ID is public), while columns like "Salary" or "BirthDate" might suggest the element is sensitive (e.g., because this information is not public). Furthermore, data types (e.g., short integer, floating-point, char, date, etc.) can be used as factors along with access frequency, owner, data length, communication method, data source, and database operation. In this embodiment, these factors are used to determine the sensitivity of an element.

[0064] Alternatively or additionally, these factors can be used to determine the appropriate encryption technique given a certain sensitivity. For example, different encryption techniques require different levels of computational resources. Two elements can both be considered highly sensitive, but can have very different access frequencies. Elements with higher access frequencies can be associated with less resource-intensive encryption techniques (e.g., saving computational resources due to frequent access), while elements with lower access frequencies can be associated with more resource-intensive encryption techniques.

[0065] Figure 6AThis illustration demonstrates the training and use of an ML model according to one embodiment to classify request elements for hierarchical encryption used for data storage. Data element 602, encryption technology 604, and encryption context 606 are provided to the element classification ML model 610. In this embodiment, data element 602 is a parsed element from a request, as discussed above with respect to Figure 4-AB. Encryption context 606 can identify contextual information regarding suitable encryption technologies, including permitted encryption technologies, frequently used encryption technologies, encryption technology vendors or providers, or other suitable information.

[0066] In this embodiment, encryption technology 604 is a list of supported encryption technologies. Many encryption technologies can be used. For example, the Advanced Encryption Standard (AES) technology can be used. AES is commonly used and is extremely efficient in its 128-bit form (e.g., not computationally intensive). However, AES also uses 192-bit and 256-bit keys for more demanding encryption purposes. AES is generally considered to be effectively unbreakable against all attacks except brute force and is becoming increasingly common as a highly reliable standard for encrypting data.

[0067] Triple DES is the successor to the original Data Encryption Standard (DES) algorithm, created in response to weaknesses identified in DES. Triple DES is a symmetric encryption algorithm that was once very widely used but has become less common. Triple DES applies the DES algorithm three times to each block of data and is commonly used for a variety of purposes, including encrypting UNIX ciphers and ATM PINs.

[0068] Blowfish is another encryption technology used as an alternative to DES. Blowfish is a symmetric tool that divides messages into 64-bit blocks and encrypts them individually. Blowfish has earned a reputation for speed, flexibility, and effective hardness to crack. Blowfish is commonly found in e-commerce platforms, secure payments, and password management tools.

[0069] Twofish is a symmetric encryption technique that decrypts 128-bit data blocks. Furthermore, Twofish encrypts data in 16 rounds, regardless of the key size. Twofish is well-suited to many software and hardware environments and is considered one of the fastest and most efficient techniques of its type. Many file and folder encryption software solutions today use this method.

[0070] Rivest-Shamir-Adleman (RSA) is an asymmetric encryption algorithm that cancels out the factorization of the product of two large prime numbers. Only a user who knows both numbers can successfully decode the message. Digital signatures often use RSA, but the algorithm typically slows down when encrypting large amounts of data. In this embodiment, for each request element, the data encryption service may choose between AES, Triple DES, Blowfish, Twofish, RSA, or any other suitable encryption technique.

[0071] In this embodiment, the element classification ML model 610 generates pairs of data elements and encryption algorithms 620. The element classification ML model can use any suitable ML model, including decision trees, deep learning models, neural networks, or any other suitable ML model. In this embodiment, the element classification ML model 610 is a supervised ML model trained using suitable training data reflecting the data elements and corresponding encryption techniques. See also Figure 6B Further discussion of the element classification ML model 610.

[0072] Figure 6B Further illustrated is a process 650 according to one embodiment for training and using an ML model to classify request elements for hierarchical encryption used for data storage. In one embodiment, process 650 illustrates a technique for classifying request elements using an ML model. This is merely an example, and any suitable technique can be used.

[0073] In box 654, the element classifier (e.g., Figure 1-2 The element classifier 114 (explained in the text) receives one or more encryption techniques 604. The element classifier performs type vectorization on the encryption techniques 604, generating one or more feature vectors describing the algorithms. The ML model can use these feature vectors to infer the pairing of data elements and encryption techniques 620.

[0074] At box 656, the element classifier uses the default safety matrix (e.g., the following). Figure 6C The security matrix shown in the diagram is used to transform (multiple) vectors (e.g., the vectors generated at box 654). At box 658, the element classifier groups spatially adjacent vectors. At box 664, the element classifier uses data element 602 and cryptographic context 606 to map the most similar group (e.g., cryptographic technique group) to the target data element 602. At box 670, the element classifier refines the groups by modifying the customized security matrix 668. At box 672, the element classifier evaluates the modeling of data element (DE) and cryptographic technique pairs and generates pairings of data element and cryptographic technique 620.

[0075] Figure 6CA security matrix 680 for hierarchical encryption of data storage is illustrated according to one embodiment. In this embodiment, each column entry is associated with a corresponding security level (e.g., a numerical security level). The security level can be used to identify suitable encryption techniques. For example, a lower security level value (e.g., "1" for the "Password" column) may indicate more sensitive data, suitable for a stronger and more computationally expensive encryption level. A higher security level value (e.g., "6" for the "HireData" column) may indicate less sensitive data, suitable for a weaker and less computationally expensive encryption level, or even no encryption at all.

[0076] Figure 7 This is a flowchart 700 illustrating hierarchical encryption for data storage according to one embodiment. In block 704, the element classifier (e.g., Figure 1-2 The element classifier 114 shown receives request 702 (e.g., a DML storage request). In an embodiment, the element classifier sends a request to a data encryption service (e.g., Figure 1-2 The data encryption service 122 shown provides classified elements 706.

[0077] In box 708, the data encryption service matches categorized elements with encryption techniques (e.g., as mentioned above regarding...). Figure 6A (As discussed in -C). Further, in one embodiment, the data encryption service stores the encryption technique corresponding to each element in a secure directory. The secure directory can be any suitable repository, including database tables, remote storage locations, or any other suitable repository. In this embodiment, the secure directory can be used during decryption to identify the encryption technique corresponding to each element. This is explained below. Figure 8 Box 808 in the text will be discussed further.

[0078] In box 710, the data encryption service determines whether the identified encryption technology is a symmetric key technology. If yes, the process proceeds to box 712. In box 712, the data encryption service identifies the encryption key (e.g., a symmetric encryption key). If no, the process proceeds to box 714. In box 714, the data encryption service identifies the private encryption key. In both scenarios, the process proceeds to box 716.

[0079] In box 716, the data encryption service encrypts the data. For example, the data encryption service may use the key generated in box 712 or 714, and the encryption technique identified in box 708, to encrypt the data identified in 702 and generate ciphertext. In box 718, the data encryption service stores the ciphertext (e.g., as requested in 702).

[0080] Figure 8This is a flowchart 800 illustrating the decryption of hierarchical encryption for data storage according to one embodiment. In block 804, a request is made to the analyzer (e.g., Figure 1-2 The request analyzer 112 shown receives query 802 (e.g., a DML query retrieving previously encrypted data). The request analyzer generates a parsed query 806 (e.g., as described above regarding...). Figure 4A -B (discussed).

[0081] In box 808, the data decryption service (e.g., Figure 1-2 The data decryption service 124) identifies the encryption techniques used for parsed queries. For example, as mentioned above... Figure 7 As discussed in box 708, during encryption, the encryption technique corresponding to each element can be stored in a secure directory. The data decryption service can use this secure directory to identify the encryption technique corresponding to each element. For example, the secure directory could be a database table, and the data decryption service could retrieve the encryption technique for each element from the database table.

[0082] In box 810, the data decryption service matches the key and encryption technique. For example, the data decryption service may identify an encryption key used to decrypt the stored data of an element. The key can be a public key, a symmetric key, or any other suitable encryption key. In box 812, the data decryption service decrypts the data (e.g., the data identified in query 802) and generates plaintext 814.

[0083] Various embodiments of the invention have been described for illustrative purposes, but are not intended to be exhaustive or limited to the disclosed embodiments. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the described embodiments. The terminology used herein has been chosen to best explain the principles of the embodiments, their practical application, or technical improvements to technologies found in the market, or to enable those skilled in the art to understand the embodiments disclosed herein.

[0084] In the foregoing, reference has been made to the embodiments set forth in this disclosure. However, the scope of this disclosure is not limited to the specifically described embodiments. Rather, any combination of features and elements, whether or not different embodiments are involved, is considered to implement and practice the contemplated embodiments. Furthermore, while the embodiments disclosed herein may achieve advantages over other possible solutions or over the prior art, whether a particular advantage is achieved by a given embodiment does not limit the scope of this disclosure. Thus, the aspects, features, embodiments, and advantages discussed herein are merely illustrative and should not be considered as elements or limitations of the appended claims unless expressly stated in the claims. Similarly, references to “the invention” should not be construed as a generalization of any inventive subject matter disclosed herein and should not be considered as elements or limitations of the appended claims unless expressly stated in the claims.

[0085] Various aspects of the present invention can be embodied in the following forms: a completely hardware embodiment, a completely software embodiment (including firmware, resident software, microcode, etc.), or an embodiment combining hardware and software aspects, which can be collectively referred to herein as a "circuit", "module" or "system".

[0086] This invention can be a system, method, and / or computer program product with any possible level of technical detail integration. The computer program product may include a computer-readable storage medium (or media) having computer-readable program instructions thereon for causing a processor to execute aspects of the invention.

[0087] Computer-readable storage media can be tangible means for retaining and storing instructions for use by an instruction execution device. Computer-readable storage media can be, for example, but not limited to, electronic storage devices, magnetic storage devices, optical storage devices, electromagnetic storage devices, semiconductor storage devices, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of computer-readable storage media includes: portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), static random access memory (SRAM), portable compact disk read-only memory (CD-ROM), digital universal disk (DVD), memory sticks, floppy disks, mechanical encoding devices such as punch cards or protrusions in slots having instructions recorded thereon, and any suitable combination of the foregoing. As used herein, computer-readable storage media should not be construed as transient signals themselves, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through waveguides or other transmission media (e.g., light pulses passing through fiber optic cables), or electrical signals transmitted through wires.

[0088] The computer-readable program instructions described herein can be downloaded from a computer-readable storage medium to a suitable computing / processing device via a network (e.g., the Internet, a local area network, a wide area network, and / or a wireless network), or to an external computer or external storage device. The network may include copper cables, optical fibers, wireless transmissions, routers, firewalls, switches, gateway computers, and / or edge servers. A network adapter card or network interface in each computing / processing device receives the computer-readable program instructions from the network and forwards them to a computer-readable storage medium within the suitable computing / processing device.

[0089] Computer-readable program instructions used to perform the operations of this invention may be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state setting data, integrated circuit configuration data, or source code or object code written in any combination of one or more programming languages, including object-oriented programming languages ​​(such as Smalltalk, C++, etc.) and procedural programming languages ​​(such as the "C" programming language or similar programming languages). The computer-readable program instructions may be executed entirely on a user's computer, partially on a user's computer, as a standalone software package, partially on a user's computer and partially on a remote computer, or entirely on a remote computer or server. In the latter case, the remote computer may be connected to the user's computer via any type of network (including a local area network (LAN) or a wide area network (WAN)) or may be connected to an external computer (e.g., via the Internet using an Internet service provider). In some embodiments, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGAs), or programmable logic arrays (PLAs) may execute computer-readable program instructions by utilizing state information from the computer-readable program instructions to personalize the electronic circuitry in order to perform aspects of this invention.

[0090] The present invention will now be described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer-readable program instructions.

[0091] These computer-readable program instructions may be provided to a processor of a computer or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions / actions specified in one or more blocks of a flowchart and / or block diagram. These computer-readable program instructions may also be stored in a computer-readable storage medium that causes a computer, programmable data processing apparatus, and / or other device to operate in a particular manner, such that the computer-readable storage medium storing the instructions includes an article of manufacture containing instructions that implement aspects of the functions / actions specified in one or more blocks of a flowchart and / or block diagram.

[0092] Computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus, or other device to produce computer-implemented processing, such that the instructions executed on the computer, other programmable apparatus, or other device perform the functions / actions specified in one or more boxes of a flowchart and / or block diagram.

[0093] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. Each block in a flowchart or block diagram may represent a module, segment, or portion of instructions, including one or more executable instructions for implementing a specified logical function. In some alternative implementations, the functions marked in the blocks may occur in a different order than those marked in the figures. For example, two blocks shown consecutively may actually be completed as a single step, executed simultaneously, substantially simultaneously, or with partial or complete temporal overlap, or the blocks may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented using a dedicated hardware-based system that performs the specified function or action or executes a combination of dedicated hardware and computer instructions.

[0094] It should be understood that while this disclosure includes a detailed description of cloud computing, the implementation of the teachings cited herein is not limited to cloud computing environments. Rather, embodiments of the invention can be implemented in conjunction with any other type of computing environment now known or developed hereafter.

[0095] Cloud computing is a service delivery model that enables convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, network bandwidth, servers, processing, memory, storage, applications, virtual machines, and services), which can be rapidly provisioned and released with minimal management effort or interaction with the service provider. This cloud model may include at least five features, at least three service models, and at least four deployment models.

[0096] The features are as follows:

[0097] On-demand self-service: Cloud consumers can unilaterally and automatically provide computing power, such as server time and network storage, as needed, without requiring human interaction with the service provider.

[0098] Extensive network access: Capabilities are available through networks and accessed via standard mechanisms that facilitate the use of heterogeneous thin client or thick client platforms (e.g., mobile phones, laptops, and PDAs).

[0099] Resource pooling: A provider's computing resources are pooled to serve multiple consumers using a multi-tenant model, where different physical and virtual resources are dynamically assigned and reassigned as needed. There is a sense of location independence because consumers typically do not have control or knowledge of the exact location of the resources provided, but may be able to specify the location at a higher level of abstraction (e.g., country, state, or data center).

[0100] Rapid flexibility: The ability to provide capacity quickly and flexibly, automatically scaling down and up rapidly in some situations to scale up rapidly. For consumers, the available supply capacity often appears unlimited and can be purchased in any quantity at any time.

[0101] Measuring services: Cloud systems automatically control and optimize resource usage by leveraging metering capabilities at a level of abstraction appropriate to the service type (e.g., storage, processing, bandwidth, and active user accounts). Resource usage can be monitored, controlled, and reported, providing transparency to both service providers and consumers.

[0102] The service model is as follows:

[0103] Software as a Service (SaaS): This provides consumers with the ability to use the provider's applications running on cloud infrastructure. Applications can be accessed from different client devices via thin client interfaces such as web browsers (e.g., web-based email). Consumers do not manage or control the underlying cloud infrastructure, including the network, servers, operating system, storage, or even individual application capabilities, with possible exceptions such as limited user-specific application configuration settings.

[0104] Platform as a Service (PaaS): This provides consumers with the ability to deploy applications created or acquired by the consumer using programming languages ​​and tools supported by the provider onto cloud infrastructure. Consumers do not manage or control the underlying cloud infrastructure, including networks, servers, operating systems, or storage, but they have control over the deployed applications and the configuration of any application hosting environment.

[0105] Infrastructure as a Service (IaaS): The capabilities offered to consumers are processing, storage, networking, and other basic computing resources that enable consumers to deploy and run arbitrary software, which may include operating systems and applications. Consumers do not manage or control the underlying cloud infrastructure, but rather have control over the operating system, storage, deployed applications, and potentially limited control over selected networking components (e.g., host firewalls).

[0106] The deployment model is as follows:

[0107] Private cloud: A cloud infrastructure that operates solely for an organization. It can be managed by the organization or a third party and can exist on-site or off-site.

[0108] Community cloud: A cloud infrastructure shared by several organizations and supporting a specific community with shared concerns (e.g., tasks, security requirements, policies, and compliance considerations). It can be managed by an organization or a third party and can exist on-site or off-site.

[0109] Public cloud: Makes cloud infrastructure available to the public or large industry groups and is owned by an organization that sells cloud services.

[0110] Hybrid cloud: A cloud infrastructure is a combination of two or more clouds (private, community, or public) that remain a single entity but are bound together by standardized or proprietary technologies that enable data and applications to be ported (e.g., cloud bursting for load balancing between clouds).

[0111] Cloud computing environments are service-oriented, focusing on statelessness, loose coupling, modularity, and semantic interoperability. At the heart of cloud computing is the infrastructure comprising a network of interconnected nodes.

[0112] See now Figure 9The figure depicts an illustrative cloud computing environment 950. As shown, the cloud computing environment 950 includes one or more cloud computing nodes 910 that can communicate with local computing devices used by cloud consumers, such as personal digital assistants (PDAs) or cellular phones 954A, desktop computers 954B, laptop computers 954C, and / or automotive computer systems 954N. The nodes 910 can communicate with each other. They can be physically or virtually grouped (not shown) in one or more networks, such as private clouds, community clouds, public clouds, or hybrid clouds, or combinations thereof, as described above. This allows the cloud computing environment 950 to provide infrastructure, platforms, and / or software as services that cloud consumers do not need to maintain on their local computing devices. It should be understood that... Figure 9 The types of computing devices 954A-N shown are intended to be illustrative only, and computing node 910 and cloud computing environment 950 can communicate with any type of computerized device via any type of network and / or network-addressable connection (e.g., using a web browser).

[0113] See now Figure 10 This demonstrates the 950 (cloud computing environment) Figure 9 This provides a set of functional abstractions. It should be understood beforehand. Figure 10 The components, layers, and functions shown are intended to be illustrative only, and embodiments of the invention are not limited thereto. As described, the following layers and corresponding functions are provided:

[0114] The hardware and software layer 1060 includes hardware and software components. Examples of hardware components include: a mainframe 1061; a server 1062 based on a RISC (Reduced Instruction Set Computer) architecture; a server 1063; a blade server 1064; a storage device 1065; and network and networking components 1066. In some embodiments, software components include network application server software 1067 and database software 1068.

[0115] The virtualization layer 1070 provides an abstraction layer from which the following examples of virtual entities can be provided: virtual server 1071; virtual storage 1072; virtual network 1073, including virtual private network; virtual application and operating system 1074; and virtual client 1075.

[0116] In one example, management layer 1080 may provide the following functionalities: Resource Provisioning 1081 Provides dynamic procurement of computing resources and other resources used to perform tasks within the cloud computing environment. Metering and Pricing 1082 Provides cost tracking as resources are utilized within the cloud computing environment and bills or invoices for the consumption of these resources. In one example, these resources may include application software licenses. Security Provides authentication for cloud consumers and tasks, as well as protection for data and other resources. User Portal 1083 Provides consumers and system administrators with access to the cloud computing environment. Service Level Management 1084 Provides cloud computing resource allocation and management to ensure that required service levels are met. Service Level Agreement (SLA) Planning and Fulfillment 1085 Provides pre-scheduling and procurement of cloud computing resources, anticipating future requirements for those resources according to the SLA.

[0117] Workload layer 1090 provides examples of functionalities that can leverage a cloud computing environment. Examples of workloads and functionalities that can be provided from this layer include: mapping and navigation 1091; software development and lifecycle management 1092; virtual classroom education delivery 1093; data analytics and processing 1094; transaction processing 1095; and layered encryption 1096 (e.g., implementing...). Figure 2 The layered encryption controller 110 shown may include one or more aspects of the request analyzer 112, element classifier 114, data encryption service 122, and data decryption service 124 (any one or all of these).

[0118] While the foregoing describes embodiments of the present invention, other and further embodiments of the invention may be devised without departing from the basic scope of the invention, and the scope of the invention is defined by the appended claims.

[0119] While the foregoing describes embodiments of the present invention, other and further embodiments of the invention may be devised without departing from the basic scope of the invention, and the scope of the invention is defined by the appended claims.

Claims

1. A method for data encryption, comprising: Parse electronic database storage requests based on request syntax to identify multiple request elements; Use one or more trained machine learning (ML) models to determine one or more sensitivities associated with the plurality of request elements; Based on the one or more sensitivity identifications, one or more encryption techniques are used for the plurality of request elements, including: Identify one or more groups of cryptographic techniques from a plurality of available cryptographic techniques, wherein each group of cryptographic techniques includes one or more available cryptographic techniques having spatially adjacent feature vectors. By mapping each of the plurality of request elements to a corresponding group of encryption techniques based on encryption context data, a pair for each request element is generated. Select one or more encryption technologies from the generated pairings for the plurality of request elements; Use one or more of the identified encryption techniques to encrypt the data associated with the database storage request; and The electronic database storage request is used to store encrypted data and one or more associated encryption keys in the electronic database.

2. The method of claim 1, wherein, Identifying the one or more encryption techniques includes: identifying multiple different sensitivities corresponding to the multiple request elements based on the one or more trained ML models, and identifying multiple different encryption techniques.

3. The method according to claim 1, further comprising: The ML model for each request element is selected from multiple different ML models based on the characteristics of the request element. as well as Based on the analysis of the request elements using the appropriate selected ML model, the sensitivity corresponding to each request element is determined.

4. The method of claim 3, further comprising: Based on the determined sensitivity corresponding to each request element, multiple different encryption techniques are identified for the data storage request, wherein the data is encrypted using the multiple different encryption techniques identified.

5. The method of claim 1, wherein identifying the one or more encryption techniques used for the plurality of request elements based on the one or more sensitivity criteria further comprises: A security matrix is ​​used to refine each generated pair, wherein the security matrix associates each of the plurality of request elements with a corresponding security level, including: For a given pair including a corresponding request element and one or more available encryption technologies, the one or more available encryption technologies are filtered based on the security level associated with the request element.

6. The method of claim 1, wherein the electronic database storage request includes Data Manipulation Language (DML) statements, and wherein parsing the electronic database storage request includes: Construct a syntax tree from the electronic database storage request; as well as The syntax tree is used to identify the plurality of request elements.

7. The method of claim 1, wherein identifying the one or more encryption techniques comprises: The one or more encryption techniques are determined based on one or more sensitivities identified using a second or more ML model analysis.

8. The method of claim 1, wherein identifying the one or more encryption techniques comprises: The one or more encryption techniques are determined based on one or more sensitivities identified by searching a lookup table.

9. The method of claim 1, further comprising: Parse electronic database queries to identify multiple query elements; Determine one or more decryption techniques associated with the plurality of query elements; Use the electronic database query to retrieve data from the electronic database; as well as The data is decrypted using one or more of the identified decryption techniques.

10. The method of claim 9, wherein determining the one or more decryption techniques associated with the plurality of query elements comprises: Retrieve one or more decryption techniques from the electronic catalog.

11. A system for data encryption, comprising: Memory; as well as A processor communicatively coupled to the memory, the processor being configured to perform the steps of the method according to any one of claims 1 to 10.

12. A computer program product for data encryption, comprising: Computer-readable program code, which can be executed by one or more computer processors to perform the steps of the method according to any one of claims 1 to 10.

Citation Information

Patent Citations

  • Database self-adaptive encryption method

    CN108595971A

  • Encryption profiles for encrypting user-submitted data

    US10699023B1

  • Machine learning methods and systems for protection and redaction of privacy information

    US11144669B1