Data protection method and system

Abstract

This invention relates to a data protection method and system, comprising: S1, the distributor and the output party defining fields of sensitive customer information to be protected; S2, the distributor encrypting the fields to be protected using an encryption method before sending them to the output party; S3, the output party generating an application data file and an attachment file based on the product provider's interface specifications; S4, the distributor receiving the application data file and the attachment file, rewriting the application data file based on the attachment file, and sending the rewritten application data file to the product provider. The data protection method and system described in this invention can effectively protect sensitive customer information without requiring the financial distributor to adapt to new final product provider interface specifications.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and in particular to a data protection method and system. Background Technology

[0002] With the development of internet services, technology output services for B2B clients are gaining increasing popularity. Based on this model, small and medium-sized enterprises (SMEs) can quickly and cost-effectively provide end-users with a wealth of digital services, improving their service quality while gaining commercial value. As the business model in the wealth management distribution sector matures, technology output services in this field can now effectively adapt to both end-product providers and wealth management distributors, processing business data and enabling the rapid implementation of wealth management distribution businesses, bringing convenience and value to a vast customer base.

[0003] Currently, technology providers in the wealth management distribution sector typically record customer information and transaction records submitted by wealth management distributors, process business data, and submit application data and parsed confirmation data according to the specific interface specifications of each end-product provider. In this model, the technology provider, as a third-party technology provider for the wealth management distribution business, handles business processes, is responsible for data interaction, and records customers' sensitive personal information.

[0004] With increasing emphasis on protecting customer personal information, this processing model is facing growing compliance challenges. However, if the technology provider does not record customer information, it cannot effectively handle account-related business and cannot have good data interaction with the final product provider. It is worth noting that the interface specifications of various final product providers vary greatly. If the wealth management distributor interacts directly with the final product provider, the wealth management distributor needs to adapt and modify each one, which is complex and labor-intensive, and goes against the original intention of the rapid implementation of the wealth management distribution business. Summary of the Invention

[0005] To address the shortcomings of existing technologies, this invention proposes a data protection method and system that can effectively protect sensitive customer information without requiring financial product distributors to adapt to new final product provider interface specifications.

[0006] To achieve the above objectives, the technical solution adopted by the present invention includes:

[0007] A data protection method, characterized in that it includes:

[0008] S1. The distributor and the exporter define the fields to be protected for sensitive customer information.

[0009] S2. The distributor encrypts the fields to be protected using encryption methods before sending them to the output party.

[0010] S3. The output party generates the application data file and additional files based on the product provider's interface specifications;

[0011] S4. The distributor receives the application data file and supplementary files, rewrites the application data file based on the supplementary files, and sends the rewritten application data file to the product provider.

[0012] Furthermore, the attached file includes a file header and a file body. The file header includes the file date, file protocol, and number of data entries. The file body includes a placeholder key, a ciphertext string, and field specifications.

[0013] Furthermore, the customer sensitive information fields to be protected include: name, ID number, and address.

[0014] Furthermore, the encryption method is: the Chinese National Cryptography IV encryption algorithm.

[0015] Furthermore, step S3 includes the following steps:

[0016] Query the data interface table, which generates one record based on each customer's sensitive information field to be protected;

[0017] Generate and populate the additional file interface table; generate placeholder keys for the customer's sensitive information fields to be protected, populate the data Id column of the additional file interface table based on the data interface table, record the ciphertext string in the additional file interface table, and populate the field specification column of the additional file interface table based on the interface specification.

[0018] Based on the interface specification, the data in the data interface table is written into the application data file. If it is a field to be protected, the placeholder KEY in the additional file interface table is used to fill it.

[0019] Additional files are generated based on the additional file interface table.

[0020] Furthermore, the additional file interface table includes: TA code, transaction date, data file name, associated table name, original data ID, system field name, placeholder value, original data value, and target type.

[0021] Furthermore, step S4 includes the following steps:

[0022] Obtain the number of data entries in the header of the attached file. If the number of data entries is 0, the data file does not need to be rewritten; if the number of data entries is not 0, the data file needs to be rewritten.

[0023] Read in the attached file and parse it into an object;

[0024] Read in the data file, match the strings to see if they contain a placeholder key. If a placeholder key is found, retrieve the ciphertext string based on the placeholder key, decrypt the plaintext string based on the ciphertext string, and overwrite the specified length following the placeholder key from the starting position according to the field type protocol.

[0025] The present invention also relates to a data protection system, characterized in that it comprises:

[0026] The Protected Fields Definition Module is used by distributors and exporters to define protected fields for sensitive customer information.

[0027] The encryption processing module is used by the distributor to encrypt the fields to be protected using encryption processing methods before sending them to the output party.

[0028] The document generation module is used by the output party to generate application data files and additional files based on the interface specifications of the product provider;

[0029] The rewrite module is used by the reseller to receive the application data file and additional files, rewrite the application data file based on the additional files, and send the rewritten application data file to the product provider.

[0030] The present invention also relates to a computer-readable storage medium, characterized in that the storage medium stores a computer program, which, when executed by a processor, implements the above-described data protection method.

[0031] The present invention also relates to an electronic device, characterized in that it includes a processor and a memory;

[0032] The memory is used to store the application data file and additional files;

[0033] The processor is used to execute the aforementioned data protection method by calling the requested data file and additional files.

[0034] The present invention also relates to a computer program product, including a computer program and / or instructions, characterized in that the computer program and / or instructions, when executed by a processor, implement the steps of the above-described data protection method.

[0035] The beneficial effects of this invention are as follows:

[0036] The data protection method and system described in this invention can effectively protect sensitive customer information, thereby preventing such information from being recorded in third-party systems and greatly satisfying compliance requirements. Furthermore, by adding an attachment file, this solution defines metadata such as the attachment file's processing protocol and record count, as well as data information such as the placeholder key, replacement string, and multi-position output type for the protected data. The original data owner can replace the protected data in the original data file with the attachment file without needing to worry about the original data file's interface specifications. This allows for compatibility upgrades, scalability, and shields the data file's interface specifications. Attached Figure Description

[0037] Figure 1 This is a schematic diagram of a data protection method according to the present invention.

[0038] Figure 2 This is a schematic diagram illustrating the process of generating the data file and additional files for this invention application.

[0039] Figure 3 This is a schematic diagram of the data file rewriting process for this invention application.

[0040] Figure 4 This is a schematic diagram of a data protection system structure according to the present invention. Detailed Implementation

[0041] To better understand the content of this invention, a detailed description will be provided in conjunction with the accompanying drawings and embodiments.

[0042] The first aspect of this invention relates to a data protection method with the following steps: Figure 1 The method shown includes:

[0043] S1. The distributor and the exporter define the fields to be protected for sensitive customer information.

[0044] The financial product distributor and the technology provider agree on the fields to be protected and set them up for storage.

[0045] The customer sensitive information fields to be protected include: name, ID number, and address.

[0046] S2. The distributor encrypts the fields to be protected using encryption methods before sending them to the output party.

[0047] During the transaction application process, the wealth management distributor will encrypt the fields to be protected, such as using the national cryptographic standard 4 (GB4) commonly used in the financial industry. The encrypted fields to be protected, along with other fields, will then be sent to the technology provider. Note that there are no special requirements for the encryption strategy or algorithm used here; as long as the corresponding plaintext can be determined from the encrypted text and the compliance and security levels are met, it is entirely up to the wealth management distributor to decide.

[0048] Because the technology provider does not know the encryption logic of the field to be protected and does not have the key or other information necessary for decryption, it will be unable to obtain the plaintext information of the data to be protected, thus failing to physically achieve the goal of data protection.

[0049] S3. The output party generates the application data file and additional files based on the product provider's interface specifications; such as... Figure 2 This is a schematic diagram illustrating the process of generating application data files and additional files.

[0050] S3 includes the following steps:

[0051] Query the data interface table, which generates one record based on each customer's sensitive information field to be protected;

[0052] Generate and populate the additional file interface table; generate placeholder keys for the customer's sensitive information fields to be protected, populate the data Id column of the additional file interface table based on the data interface table, record the ciphertext string in the additional file interface table, and populate the field specification column of the additional file interface table based on the interface specification.

[0053] Based on the interface specification, the data in the data interface table is written into the application data file. If it is a field to be protected, the placeholder KEY in the additional file interface table is used to fill it.

[0054] Additional files are generated based on the additional file interface table.

[0055] The document generation process for technology output service providers generally consists of three steps: First, query the data interface table, generate placeholder keys for the fields to be protected according to the configuration, and simultaneously record the data ID and encrypted string in the attachment file interface table. Also, populate the field specification columns in the attachment file interface table according to the interface specifications (note: generate one record for each field to be protected in the data interface table). Second, write the data from the data interface table to the data file according to the interface specifications. If it is a field to be protected, populate it using the placeholder keys from the attachment file interface table. Third, write the attachment file header according to the current date, the number of records in the attachment file interface table, and the specifications, and then write the data from the attachment file interface table line by line into the attachment file body.

[0056] Additional file description: Each file includes a supplementary file, with the filename formatted as: {business filename}.txt.plus;

[0057] The attached file includes a file header and a file body. The file header includes the file date, file protocol, and number of data entries. The file body includes a placeholder key, a ciphertext string, and field specifications.

[0058] The format of the attachment file is as follows:

[0059]

[0060] When processing unprotected fields, the attached file example is as follows:

[0061] Date: 20220912

[0062] FileProtocol:

[0063] Records:0

[0064] When there are protected fields, the attached file example is as follows:

[0065] Date: 20220912

[0066] FileProtocol:C:R,A:L0,N:L0

[0067] Records:2

[0068] @{0000A1}0x01SDFDSFLKSDFKLFKDLFKDS0x01C:40,C:60,C:40

[0069] @{0000A2}0x01SDFSDFDSFDSFDSFSDAsdfsdZCZXCSFWE0x01C:120

[0070] The attachment file interface table includes: TA code, transaction date, data file name, associated table name, original data ID, system field name, placeholder value, original data value, and target type; the record content in the attachment file interface table is shown in the following example:

[0071]

[0072] S4. The distributor receives the application data file and supplementary files, rewrites the application data file based on the supplementary files, and sends the rewritten application data file to the product provider.

[0073] S4 includes the following steps:

[0074] Obtain the number of data entries in the header of the attached file. If the number of data entries is 0, the data file does not need to be rewritten; if the number of data entries is not 0, the data file needs to be rewritten.

[0075] Read in the attached file and parse it into an object;

[0076] Read in the data file, match the strings to see if they contain a placeholder key. If a placeholder key is found, retrieve the ciphertext string based on the placeholder key, decrypt the plaintext string based on the ciphertext string, and overwrite the specified length following the placeholder key from the starting position according to the field type protocol.

[0077] After receiving the data file and attachments, the financial product distributor needs to rewrite the data file according to the attachments, such as... Figure 3 Flowchart of rewriting data files:

[0078] The first step is to determine if the total number of records in the header of the attachment file is 0. If it is 0, it means there are no records in the attachment file, and the corresponding data file is a regular file that does not need to be rewritten. You can proceed directly to step five. If it is not 0, further rewriting is required.

[0079] The second step is to read in all the attached files and parse them into objects for later use.

[0080] The third step involves reading the corresponding data file line by line, matching the strings to see if they contain a placeholder key. If not, continue to the next line and repeat this step until the file is processed. Otherwise, retrieve the ciphertext string based on the placeholder key in the attached file, then decrypt the plaintext string from the ciphertext string. Next, according to the field specifications (the field type and length at the Nth occurrence), overwrite the specified length following the placeholder key from its starting position according to the field type protocol (adding padding if the plaintext string is insufficient). After processing this line, continue to the next line and repeat this step until the file is processed. The processing flow for this step is illustrated below:

[0081] Fourth step: Now the data file is a regular plaintext data file, and it can be moved to the file sending directory for downstream use.

[0082] Another aspect of the present invention relates to a data protection system, the structure of which is as follows: Figure 4 As shown, it includes:

[0083] The Protected Fields Definition Module is used by distributors and exporters to define protected fields for sensitive customer information.

[0084] The encryption processing module is used by the distributor to encrypt the fields to be protected using encryption processing methods before sending them to the output party.

[0085] The document generation module is used by the output party to generate application data files and additional files based on the interface specifications of the product provider;

[0086] The rewrite module is used by the reseller to receive the application data file and additional files, rewrite the application data file based on the additional files, and send the rewritten application data file to the product provider.

[0087] By using this system, the aforementioned computational processing methods can be executed and the corresponding technical effects can be achieved.

[0088] Embodiments of the present invention also provide a computer-readable storage medium capable of implementing all the steps of the methods in the above embodiments, wherein the computer-readable storage medium stores a computer program that, when executed by a processor, implements all the steps of the methods in the above embodiments.

[0089] Embodiments of the present invention also provide an electronic device for performing the above-described method. As an implementation device for the method, the electronic device includes at least a processor and a memory. In particular, the memory stores data and related computer programs required for performing the method, such as application data files and additional files. The processor calls the data and programs in the memory to execute all the steps of the method and obtain the corresponding technical effect.

[0090] Preferably, the electronic device may include a bus architecture, which may include any number of interconnected buses and bridges. The bus will include various circuits linked together by one or more processors and memories. The bus may also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides an interface between the bus and the receiver and transmitter. The receiver and transmitter may be the same element, i.e., a transceiver, providing a unit for communicating with various other systems over a transmission medium. The processor is responsible for managing the bus and general processing, while the memory may be used to store data used by the processor during operation.

[0091] Additionally, the electronic device may further include components such as a communication module, an input unit, an audio processor, a display, and a power supply. The processor (or controller, operating control) used may include a microprocessor or other processor device and / or logic device, which receives input and controls the operation of various components of the electronic device; the memory may be one or more of a buffer, flash memory, hard drive, removable media, volatile memory, non-volatile memory, or other suitable devices, which can store the aforementioned data information, and may also store programs for executing the information, and the processor can execute the program stored in the memory to achieve information storage or processing, etc.; the input unit is used to provide input to the processor, for example, it can be a button or touch input device; the power supply is used to provide power to the electronic device; the display is used to display images and text, for example, it can be an LCD display. The communication module is a transmitter / receiver that transmits and receives signals via an antenna. The communication module (transmitter / receiver) is coupled to the processor to provide input signals and receive output signals, which can be the same as in conventional mobile communication terminals. Based on different communication technologies, multiple communication modules can be incorporated into the same electronic device, such as cellular network modules, Bluetooth modules, and / or wireless LAN modules. The communication module (transmitter / receiver) is also coupled to a speaker and microphone via an audio processor to provide audio output through the speaker and receive audio input from the microphone, thereby enabling typical telecommunications functions. The audio processor can include any suitable buffer, decoder, amplifier, etc. Furthermore, the audio processor is coupled to a central processing unit, enabling on-device recording via the microphone and on-device playback of stored sound via the speaker.

[0092] It will be understood by those skilled in the art that embodiments of the present invention may be provided as methods, systems, or computer program products. Thus, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware. Furthermore, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0093] This invention is 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 will 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 program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, 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, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 a process or multiple processes and / or boxes Figure 1 A system that specifies functions in one or more boxes.

[0094] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including an instruction set implemented in a process. Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

[0095] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 a process or multiple processes and / or boxes Figure 1 The steps of the functions specified in one or more boxes. Although preferred embodiments of the invention have been described, those skilled in the art, upon learning the basic inventive concept, can make other changes and modifications to these embodiments. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments as well as all changes and modifications falling within the scope of the invention.

[0096] The above description is merely a preferred embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A data protection method, characterized in that, include: S1. The distributor and the exporter define the fields to be protected for sensitive customer information. S2. The distributor encrypts the fields to be protected using encryption methods before sending them to the output party. S3. The output party generates the application data file and additional files based on the product provider's interface specifications; S4. The distributor receives the application data file and supplementary files, rewrites the application data file based on the supplementary files, and sends the rewritten application data file to the product provider. S3 includes the following steps: Query the data interface table, which generates one record based on each customer's sensitive information field to be protected; Generate and populate the additional file interface table; Generate placeholder keys for the sensitive customer information fields to be protected, populate the data Id column of the supplementary file interface table based on the data interface table, record the encrypted string in the supplementary file interface table, and populate the field specification column of the supplementary file interface table based on the interface specification. Based on the interface specification, the data in the data interface table is written into the application data file. If it is a field to be protected, the placeholder KEY in the additional file interface table is used to fill it. Additional files are generated based on the additional file interface table.

2. The method as described in claim 1, characterized in that, The attached file includes a file header and a file body. The file header includes the file date, file protocol, and number of data entries. The file body includes a placeholder key, a ciphertext string, and field specifications.

3. The method as described in claim 1, characterized in that, The customer sensitive information fields to be protected include: name, ID number, and address.

4. The method as described in claim 1, characterized in that, The encryption method is: the Chinese National Cryptography IV encryption algorithm.

5. The method as described in claim 1, characterized in that, The attached file interface table includes: TA code, transaction date, data file name, associated table name, original data ID, system field name, placeholder value, original data value, and target type.

6. The method as described in claim 1, characterized in that, S4 includes the following steps: Obtain the number of data entries in the header of the attached file. If the number of data entries is 0, the data file does not need to be rewritten; if the number of data entries is not 0, the data file needs to be rewritten. Read in the attached file and parse it into an object; Read in the data file, match the strings to see if they contain a placeholder key. If a placeholder key is found, retrieve the ciphertext string based on the placeholder key, decrypt the plaintext string based on the ciphertext string, and overwrite the specified length following the placeholder key from the starting position according to the field type protocol.

7. A data protection system, characterized in that, include: The Protected Fields Definition Module is used by distributors and exporters to define protected fields for sensitive customer information. The encryption processing module is used by the distributor to encrypt the fields to be protected using encryption processing methods before sending them to the output party. The document generation module is used by the output party to generate application data files and additional files based on the interface specifications of the product provider; The rewrite module is used by the reseller to receive the application data file and additional files, rewrite the application data file based on the additional files, and send the rewritten application data file to the product provider. The file generation module also includes: Query the data interface table, which generates one record based on each customer's sensitive information field to be protected; Generate and populate the additional file interface table; generate placeholder keys for the customer's sensitive information fields to be protected, populate the data Id column of the additional file interface table based on the data interface table, record the ciphertext string in the additional file interface table, and populate the field specification column of the additional file interface table based on the interface specification. Based on the interface specification, the data in the data interface table is written into the application data file. If it is a field to be protected, the placeholder KEY in the additional file interface table is used to fill it. Additional files are generated based on the additional file interface table.

8. A computer-readable storage medium, characterized in that, The storage medium stores a computer program, which, when executed by a processor, implements the data protection method according to any one of claims 1 to 6.

9. An electronic device, characterized in that, Including processor and memory; The memory is used to store the application data file and additional files; The processor is configured to execute the data protection method according to any one of claims 1 to 6 by invoking the request data file and additional files.

10. A computer program product comprising a computer program and / or instructions, characterized in that, When the computer program and / or instructions are executed by a processor, they implement the steps of the data protection method according to any one of claims 1 to 6.

Images