Data management method and device, electronic equipment and medium

Abstract

The invention discloses a data management method and device, electronic equipment and a medium, and the method comprises the steps: responding to obtained transmission data of first equipment, extracting the transmission data, and obtaining a check code and equipment information; when it is confirmed that the transmission data is qualified according to the check code, desensitizing the transmission data, and determining an encryption confidentiality level mode corresponding to the transmission data according to the equipment type indicated by the equipment information; according to an encryption method corresponding to the confidentiality level, encrypting the desensitized transmission data by adopting an encryption mode to obtain encrypted data; performing desensitization processing and identification processing on the encrypted data to obtain encrypted identification data after desensitization processing; and storing the encrypted data identification data after the desensitization processing to a target storage area. The method can be applied to the business fields of financial science and technology, medical health, old-age care and the like, the overall data safety is improved, privacy protection of sensitive information is increased, meanwhile, the data management and tracing capacity is improved, and balance between safety and performance is achieved.

Description

Technical Field

[0001] The present application relates to the field of data management, and in particular to a data management method, device, electronic device, and medium. Background Art

[0002] In today's society, data security management is becoming increasingly important, especially in industries involving sensitive information, such as healthcare and finance. In healthcare, for example, patient medical records, diagnostic reports, and genetic testing data are all highly sensitive personal information. This data circulates between hospitals, clinics, and research institutions, and improper data management can easily lead to data leaks or misuse.

[0003] Current data management methods often use a single encryption algorithm for unified encryption and then store it in a fixed directory. However, the sensitivity of the transmitted data generated by different devices may vary, and unified encryption may lead to over-encryption or under-encryption. Secondly, a single encryption method cannot effectively deal with various security threats that may arise in the future. In addition, many management systems store all data in a common path, making the classified management and subsequent use of data difficult, and also increasing the potential risk of data leakage. For example, if the desensitized blood pressure data from home monitoring devices and the desensitized genetic data from gene sequencing equipment use the same encryption and storage method, it obviously cannot meet the requirements of refined management.

[0004] As a result, existing data management methods are relatively crude and unable to effectively and securely manage different types of data. This poses significant challenges and security risks in scenarios such as healthcare and finance, which have extremely high requirements for data security, classification management, and processing efficiency. Summary of the Invention

[0005] The main purpose of the embodiments of the present application is to propose a data management method, device, electronic device and medium, aiming to solve the problems of poor security and low refinement of existing data management methods.

[0006] To achieve the above objectives, a first aspect of an embodiment of the present application provides a data management method, the method comprising:

[0007] In response to the acquired transmission data of the first device, extract the transmission data to obtain a check code and device information, where the device information is used to indicate a type of device sending the transmission data;

[0008] When the transmission data is confirmed to be qualified according to the verification code, the transmission data is desensitized, and the confidentiality level corresponding to the transmission data is determined according to the device type indicated by the device information;

[0009] Encrypting the desensitized transmission data according to the encryption method corresponding to the confidentiality level to obtain encrypted data;

[0010] Performing identification processing on the encrypted data to generate identification data, wherein the identification data has a unique identifier;

[0011] The identification data is stored in a target storage area, where the target storage area is determined according to the device type indicated by the device information.

[0012] The transmission data includes operation data and storage data;

[0013] The step of encrypting the desensitized transmission data according to the encryption method corresponding to the confidentiality level to obtain encrypted data includes:

[0014] In the case where the transmission data is operation data, determining the encryption method of the transmission data from a preset dynamic encryption library according to the confidentiality level;

[0015] In the case where the transmission data is storage data, the encryption method of the transmission data is determined from a preset static encryption library according to the confidentiality level.

[0016] In some embodiments, storing the identification data in a target storage area includes:

[0017] determining a first storage area according to a device type indicated by the device information;

[0018] According to the confidentiality level, determining a second storage area corresponding to the confidentiality level from the first storage area;

[0019] The second storage area is used as the target storage area, and the identification data is stored in the target storage area.

[0020] In some embodiments, when confirming that the transmission data is qualified according to the verification code, desensitizing the transmission data includes:

[0021] When the transmission data is confirmed to be qualified according to the verification code, obtaining first key data in the transmission data;

[0022] Determining an iteration area and a conversion area according to the first key data;

[0023] Based on a preset desensitizing algorithm, the iteration area and the conversion area are iteratively encrypted until the number of iterations meets a preset value, thereby obtaining desensitized transmission data.

[0024] In some embodiments, the method further comprises:

[0025] In response to the acquired access request from the second device, extract the access request to obtain identity information, where the identity information is used to indicate the identity of the user who issued the access request;

[0026] determining an identity authentication level of the user according to the user identity indicated by the identity information;

[0027] When the identity authentication level is lower than a preset level threshold, authenticating the identity information to obtain an authentication result;

[0028] If the authentication result indicates that the identity information authentication is successful, the access permission corresponding to the access request is determined.

[0029] In some embodiments, when the authentication result indicates that the identity information authentication is successful, after determining the access rights corresponding to the access request, the method further includes:

[0030] generating an access log based on the access request;

[0031] Periodically checking the access log to obtain verification data;

[0032] When the inspection data indicates that there is an access anomaly in the access request, an early warning message is issued and the inspection data is displayed.

[0033] In some embodiments, after storing the identification data in the target storage area, the method further includes:

[0034] When the confidentiality level is higher than a preset threshold, storing the identification data in a corresponding virtual address space based on memory mapping;

[0035] Upon receiving an access request from a second device, determining an access pointer based on the access request;

[0036] According to the access pointer, identification data corresponding to the access request is obtained.

[0037] To achieve the above-mentioned purpose, a second aspect of an embodiment of the present application provides a data management device, the device comprising:

[0038] an extraction module, configured to respond to the acquired transmission data of the first device, extract the transmission data, obtain a check code and device information, wherein the device information is used to indicate a type of device sending the transmission data;

[0039] a desensitizing module, configured to desensitize the transmission data when the transmission data is confirmed to be qualified according to the verification code, and determine the confidentiality level corresponding to the transmission data according to the device type indicated by the device information;

[0040] an encryption module, configured to encrypt the transmission data after desensitization according to an encryption method corresponding to the security level, to obtain encrypted data;

[0041] an identification module, configured to perform identification processing on the encrypted data to generate identification data, the identification data having a unique identification;

[0042] a storage module, configured to store the identification data to a target storage area, the target storage area being determined according to a device type indicated by the device information.

[0043] To achieve the above object, a third aspect of the embodiments of the present application provides an electronic device, which comprises a memory and a processor, the memory stores a computer program, and the processor implements the data management method of the first aspect when executing the computer program.

[0044] To achieve the above object, a fourth aspect of the embodiments of the present application provides a computer readable storage medium, which stores a computer program, and the computer program implements the data management method of the first aspect when executed by a processor.

[0045] The data management method, device, electronic device and medium provided by the present application, when receiving transmission data from a first device, first extract a check code and device information. The check code is used to confirm whether the transmission data is qualified. After the data is verified, the device information is used to determine the security level of the transmission data. The data is desensitized before encryption, thereby greatly reducing the risk of sensitive information leakage. According to the security level determined in the second step, a corresponding encryption method is selected to encrypt the desensitized data, so that the data security policy can be more refined and automated. The encrypted data is processed for identification to generate identification data with a unique identification. This unique identification not only facilitates data management and retrieval, but also provides a basis for subsequent data tracking. Through the present application, the overall data security is improved, the privacy protection of sensitive information is increased, the data management and tracking ability is improved, and the balance between security and performance is achieved. BRIEF DESCRIPTION OF DRAWINGS

[0046] Figure 1 is a flowchart of a data management method provided by the embodiments of the present application;

[0047] Figure 2 is Figure 1 a flowchart of determining an encryption method in step S300 in

[0048] Figure 3 is Figure 1 a flowchart of determining a target storage area in step S500 in

[0049] Figure 4 is Figure 1 a flowchart of desensitization in step S200 in

[0050] Figure 5 is a structural schematic diagram of a data management device provided by an embodiment of the present application.

[0051] Figure 6 is a hardware structure schematic diagram of an electronic device provided by an embodiment of the present application. DETAILED DESCRIPTION

[0052] In order to make the purposes, technical solutions and advantages of the present application clearer, the present application is further described in detail below in combination with the drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and do not limit the present application.

[0053] It should be noted that although the functional modules are divided in the device schematic diagram, and the logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in a manner different from the module division in the device or the order in the flowchart. The terms "first", "second", etc. in the specification and claims and the above-described drawings are used to distinguish similar objects, and do not necessarily describe a specific order or sequence.

[0054] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which the present application belongs. The terms used herein are only for the purpose of describing the embodiments of the present application and are not intended to limit the present application.

[0055] In today's society, data security management is increasingly important, especially in sensitive information industries such as medical care and finance. Existing data management faces many challenges: uniform encryption cannot adapt to different sensitivity data, resulting in excessive or insufficient encryption, and a single encryption party cannot resist future threats. In addition, data lacks classified management and universal path storage, so that high sensitivity such as genetic data and low sensitivity such as blood pressure data are protected in the same way, which seriously increases the risk of leakage and management difficulty. The existing method is too rough and cannot meet the fine requirements of the medical and financial fields for data security, classified management and processing efficiency, which constitutes a significant security risk.

[0056] Based on this, the embodiments of the present application provide a data management method, device, electronic device and medium, aiming to solve the problems of poor security and low refinement of existing data management methods.

[0057] The data management method, device, electronic device and medium provided by the embodiments of the present application are specifically described by the following embodiments. First, the data management method in the embodiments of the present application is described.

[0058] The embodiments of the present application can acquire and process relevant data based on artificial intelligence technology. Artificial Intelligence (AI) is the theory, method, technology, and application system that uses digital computers or machines controlled by digital computers to simulate, extend, and expand human intelligence, perceive the environment, acquire knowledge, and use knowledge to achieve optimal results.

[0059] Fundamental AI technologies generally include sensors, dedicated AI chips, cloud computing, distributed storage, big data processing, operating / interaction systems, and mechatronics. AI software technologies primarily encompass computer vision, robotics, biometrics, speech processing, natural language processing, and machine learning / deep learning.

[0060] The data management method provided in the embodiments of the present application relates to the fields of financial technology, medical health, etc. The data management method provided in the embodiments of the present application can be applied to the terminal, can be applied to the server side, and can also be software running in the terminal or the server side. In some embodiments, the terminal can be a smart phone, a tablet computer, a laptop computer, a desktop computer, etc.; the server side can be configured as an independent physical server, or as a server cluster or distributed system composed of multiple physical servers, or as a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms; the software can be an application that implements the data management method, etc., but is not limited to the above forms.

[0061] The present application can be used in many general or special computer system environments or configurations. For example: personal computers, server computers, handheld or portable devices, tablet devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments including any of the above systems or devices, and the like. The present application can be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, and the like that perform specific tasks or implement specific abstract data types. The present application can also be practiced in distributed computing environments in which tasks are performed by remote processing devices connected via a communication network. In a distributed computing environment, program modules can be located in local and remote computer storage media, including storage devices.

[0062] It should be noted that in each specific embodiment of the present application, when it comes to the need to perform relevant processing based on data related to the user's identity or characteristics, such as user information, user behavior data, user historical data, and user location information, the user's permission or consent will be obtained first, and the collection, use, and processing of such data will comply with relevant laws, regulations, and standards. In addition, when the embodiment of the present application needs to obtain the user's sensitive personal information, the user's separate permission or consent will be obtained through a pop-up window or by jumping to a confirmation page. After clearly obtaining the user's separate permission or consent, the necessary user-related data for the normal operation of the embodiment of the present application will be obtained.

[0063] The data management method can be applied to the management system of financial insurance companies, the management system of medical and health consulting companies, and the management system of physical sales companies, without limitation. For ease of explanation, this embodiment describes the steps of the data management method using the system as the main body.

[0064] Figure 1 This is a flow chart of the data management method provided in the embodiment of the present application. Figure 1 The data management method provided in the embodiment of the present application may include but is not limited to steps S100 to S500.

[0065] Step S100: In response to the acquired transmission data of the first device, extract the transmission data to obtain a check code and device information.

[0066] In this step, after obtaining the transmission data, the system will immediately extract the data to parse out key security-related metadata from the original transmission data stream, mainly including checksums and device information.

[0067] A checksum is a preliminary verification mechanism for data integrity and authenticity. Before data transmission, the first device generates a checksum based on all or part of the transmitted data and appends it to the transmitted data or sends it independently. Upon receiving the data, the system recalculates a checksum using the same verification algorithm as the received data and compares it with the received checksum. If the two match, the data has not been tampered with or damaged during transmission. Otherwise, there may be data corruption or malicious tampering, and the system can use this information to decide whether to reject the transmitted data or trigger an exception handling process.

[0068] Device information is used to identify the type of device sending transmitted data. This may include the device's unique identifier, device model, operating system type and version, the device's network environment, and IP address. Device information can be obtained by parsing transmission protocol headers, data packet metadata, or identifiers preset during device registration. The purpose of obtaining device information is that different device types correspond to different security levels, processing capabilities, or data generation modes, necessitating the development of subsequent data processing and security policies tailored to the device type.

[0069] In one example, a user uploads claim application data to an insurance company's data management system using their mobile phone (the first device). The claim application data, as transmitted data, includes a verification code and device information. The data management system responds to the transmitted data and extracts the verification code and device information.

[0070] Step S200: When the transmission data is confirmed to be qualified according to the verification code, the transmission data is desensitized, and the confidentiality level corresponding to the transmission data is determined according to the device type indicated by the device information.

[0071] Specifically, upon confirming the transmission data's eligibility based on the verification code, the system will desensitize the data and determine the corresponding confidentiality level based on the device type indicated by the device information. The desensitization process aims to identify and process sensitive information in the transmitted data to protect user privacy.

[0072] The system will also determine the confidentiality level corresponding to the transmitted data based on the device type indicated by the device information, and subsequently determine the security classification corresponding to the transmitted data to guide subsequent encryption, storage and access strategies.

[0073] The confidentiality level can be determined based on a preset security policy table. For example, data transmitted from a "bank self-service terminal" or "hospital internal system" may be assigned the highest confidentiality level (such as "Top Secret" or "Core Sensitive") because it may contain highly sensitive financial or medical information. Data from a "user mobile app" may be assigned a high confidentiality level (such as "Confidential") because it may involve personal accounts or health records. The classification of confidentiality levels should take into account the sensitivity of the data, the degree of potential harm, and data security standards.

[0074] Step S300: Encrypt the desensitized transmission data according to the encryption method corresponding to the confidentiality level to obtain encrypted data.

[0075] Specifically, after desensitizing the data and determining its confidentiality level, this step will select an appropriate encryption method based on the determined confidentiality level to re-encrypt the desensitized transmission data, thereby generating the final encrypted data. This encryption is an additional security layer on top of desensitization, designed to protect the confidentiality of the desensitized data during transmission and storage.

[0076] Step S400: perform identification processing on the encrypted data to generate identification data, where the identification data has a unique identification.

[0077] Specifically, encrypted data is identified, a unique identifier is assigned to it, and identification data is generated. This identification data will serve as the primary reference for data circulation and management within the system without directly exposing the original or encrypted sensitive content.

[0078] In one example, for desensitized and encrypted claim application data, the system generates a unique claim data identifier, such as a UUID, as its identification data. This claim data identifier is associated with the encrypted data for subsequent query and management, while ensuring that the original sensitive data cannot be directly deduced from this identifier.

[0079] Step S500: Store the identification data in a target storage area, where the target storage area is determined according to the device type indicated by the device information.

[0080] Specifically, the target storage area is determined based on the device type indicated by the device information, and the identified data is then stored in the target storage area. By associating the storage area with the device type, the relationship between data sources and storage policies is strengthened, further enhancing the refinement and security of data management.

[0081] The system first ensures the integrity and source credibility of the transmitted data through data verification and device information identification. Then, by deeply desensitizing qualified data and determining its confidentiality level, the risk of leakage of personal sensitive information is greatly reduced, and a refined classification basis is provided for subsequent security processing. On this basis, the system selects the corresponding encryption method according to the confidentiality level of the data to re-encrypt the desensitized data to ensure the confidentiality of the data during transmission and storage. Subsequently, the system assigns a unique identifier to the encrypted data, so that it can be safely and efficiently referenced and managed in the internal system without exposing the original sensitive content. Finally, these identified data are intelligently stored in the target storage area determined by the device type and confidentiality level, realizing hierarchical and isolated storage of data, further strengthening the security and meticulousness of the data during transmission or storage.

[0082] In some embodiments, the transmitted data may include operational data and stored data, such as Figure 2 As shown, the encryption step in step S300 may include but is not limited to:

[0083] Step S310: When the transmission data is operation data, an encryption method for the transmission data is determined from a preset dynamic encryption library according to the confidentiality level.

[0084] Specifically, transmitted data is divided into operational data and stored data. Operational data generally refers to data that needs to be frequently accessed, modified, or processed in real time, such as current user transaction requests, medical record query operations, and online service logs. This data often has a short lifecycle or requires high concurrent access.

[0085] Dynamic encryption is used for operational data to ensure immediate security throughout its lifecycle. The system maintains a dynamic encryption library containing a variety of encryption algorithms and key management strategies designed for high efficiency and security, such as symmetric encryption algorithms, transport layer security protocols, and session-based key agreement protocols. This provides operational data with enhanced encryption strength and flexibility to adapt to evolving security threats.

[0086] For example, if the first device is performing real-time health consultation or data analysis, the transmitted data is operational data. Based on the corresponding confidentiality level, the system selects a homomorphic encryption algorithm from a pre-set dynamic encryption library. This encryption method allows calculations to be performed on the data in an encrypted state without decryption, thus ensuring data privacy during the calculation process.

[0087] Step S320: When the transmission data is storage data, determine the encryption method of the transmission data from a preset static encryption library according to the confidentiality level.

[0088] Specifically, stored data typically refers to data that requires long-term preservation, infrequent changes, or serves as historical records, such as user profiles, complete medical records, historical transaction records, and backup data. Static encryption is used for data that requires long-term storage to ensure data security while in storage and prevent data leaks caused by database leaks or storage media loss.

[0089] The system maintains a static encryption library containing encryption algorithms and key management schemes suitable for long-term data protection. Based on the confidentiality level of the data, the system determines the appropriate encryption algorithm and key management strategy from the static encryption library. For example, for "confidential" stored data, database TDE combined with key management services may be used for key protection. For higher-level data, stronger application-layer encryption, even incorporating homomorphic encryption, may be required.

[0090] By differentiating operational data from stored data and employing dynamic and static encryption, we ensure continuous and differentiated data security protection throughout its lifecycle. By selecting different encryption strengths and methods based on confidentiality levels, we optimize the use of security resources while meeting the security requirements of data at different levels.

[0091] In some embodiments, as Figure 3 As shown, the storing step in step S500 may include but is not limited to:

[0092] Step S510: Determine a first storage area according to the device type indicated by the device information.

[0093] Specifically, based on the type of data source device, the data storage area is preliminarily planned to achieve data classification management and optimize storage efficiency.

[0094] The system will have a pre-set storage area mapping table that directs identified data to a specific primary storage area based on device information. For example, data from a mobile app might be initially located in the mobile terminal data buffer storage area, while data from a medical detector might be located in the medical device data pre-processing storage area.

[0095] Step S520: According to the confidentiality level, determine a second storage area corresponding to the confidentiality level from the first storage area.

[0096] Specifically, based on the first storage area, the storage location is further refined according to the confidentiality level of the transmitted data to achieve hierarchical and partitioned storage of data, so as to implement stricter access control and physical security measures.

[0097] After determining the first storage area, the system will select a more specific second storage area within the first storage area or in an associated storage architecture in combination with the security level.

[0098] In one example, in the "mobile terminal data buffer storage area", "top secret" patient genetic data may be diverted to the "high security isolation storage partition" (which may be deployed in an independent encrypted storage array or a computer room that meets specific security standards); "confidential" user transaction data may be diverted to the "general encrypted database storage partition"

[0099] Step S530: Use the second storage area as the target storage area, and store the identification data in the target storage area.

[0100] Specifically, the encrypted data with a unique identifier is ultimately determined and stored, ensuring persistent storage according to the pre-defined, refined security policy. After the two steps above, the target storage area for the encrypted data is determined. The system then stores the generated identification data in this target area.

[0101] Identity data usually no longer contains raw, directly readable sensitive information, but instead consists of a unique identifier that allows systems to reference, retrieve, and manage specific data records even without exposing the original data.

[0102] By storing identified data, data security is further enhanced. First, precise desensitization ensures minimal exposure to sensitive information. Then, confidentiality levels are refined based on the data source and content, further refining security policies. Dynamically selecting the appropriate encryption algorithm based on the data type and confidentiality level ensures encryption strength during data transmission and storage. During storage, highly sensitive data is isolated and stored in the most secure areas through multi-level storage areas, effectively preventing data leaks and internal misuse.

[0103] In some embodiments, as Figure 4 As shown, the desensitization step of step S200 may include but is not limited to:

[0104] Step S210: When the transmission data is confirmed to be qualified according to the verification code, first key data in the transmission data is obtained.

[0105] Specifically, the system accurately identifies sensitive or personally identifiable information contained in transmitted data as primary key data. The system uses a pre-set set of rules or a machine learning model to identify the primary key data within the data. For example, for financial data, the primary key data might include bank account number, ID number, mobile phone number, name, transaction amount, etc.; for medical data, it might include patient name, ID number, medical record number, diagnosis results, medication information, etc. This identification can be based on regular expression matching, keyword recognition, data type determination, or a combination of semantic analysis.

[0106] Step S220: Determine the iteration area and the conversion area according to the first key data.

[0107] Specifically, after identifying the first key data, the system will further analyze the structural characteristics of this data and divide it into an iteration area and a conversion area.

[0108] Iterative regions are sections of data suitable for strengthening through repeated application of encryption algorithms. Examples include birth dates in ID numbers and certain consecutive digits in bank card numbers. Through multiple iterative processes, these regions can be made highly uncorrelated with the original data, making reverse engineering difficult. This provides structured input to the encryption algorithm, ensuring the effectiveness of the desensitization process.

[0109] Transformation areas are parts of the data that are suitable for anonymization through specific mapping or replacement algorithms. For example, names, addresses, and diagnosis results can be anonymized by mapping them to anonymous IDs, general descriptions, or aggregated statistical data.

[0110] Step S230: Based on a preset desensitizing algorithm, the iteration area and the conversion area are iteratively encrypted until the number of iterations meets a preset value, thereby obtaining desensitized transmission data.

[0111] Specifically, through iterative encryption, the authenticity of sensitive data is further blurred, highly anonymized data is generated, the risk of sensitive information leakage is reduced, and it cannot be identified under unauthorized access, thereby protecting user privacy.

[0112] The system uses a pre-defined encryption algorithm for desensitization, such as a hash function or symmetric encryption algorithm, to process the iteration and transformation areas. For the iteration area, the encryption algorithm is applied repeatedly until the pre-defined number of iterations is reached. The output of each iteration serves as the input for the next, significantly increasing the difficulty of reverse engineering. For example, a numerical sequence might be hashed 1,000 times. For the transformation area, methods such as one-way hashing, substitution mapping, generalization, and scrambling may be used.

[0113] By structuredly dividing key data, the system enables differentiated desensitization processing based on the data's characteristics. This provides flexibility and adaptability, enabling the selection of the most appropriate processing strategy for different data types and desensitization requirements. Furthermore, by repeatedly applying encryption algorithms, the difficulty of reverse engineering sensitive information is significantly increased, generating highly anonymized or pseudonymized desensitized data. This achieves deep privacy protection, making it difficult to identify the original sensitive information even if unauthorized access to the desensitized data occurs, significantly reducing the risk of sensitive information leakage.

[0114] In some embodiments, the data management method may also include, but is not limited to:

[0115] Step S610: In response to the acquired access request from the second device, extract the access request to obtain identity information, where the identity information is used to indicate the identity of the user who issued the access request.

[0116] Specifically, the system responds to and receives an access request from a second device, which is a terminal attempting to access stored data, such as a doctor's workstation, an insurance claims adjuster's computer, or an external application system connected via a specific interface.

[0117] When the system receives an access request, it immediately extracts key user identity metadata from the raw request data stream, such as account name, user ID, employee number, department, IP address, access time, requested resource type, and even biometrics. This identity information can be obtained by parsing request headers, request parameters, or by interacting with specific authentication services.

[0118] In one example, taking a financial insurance company as an example, when a claims adjuster, that is, the second device, attempts to access a user's claims data, the system will obtain the access request and extract the identity information of the claims adjuster from it.

[0119] Step S620: Determine the user's identity authentication level based on the user identity indicated by the identity information.

[0120] Specifically, after successfully obtaining the user's identity information, the system will determine the corresponding authentication level for the user based on the pre-set security policy or user permission configuration. The authentication level defines the authentication strength required for users to access data of varying sensitivity or perform different operations. For example, "Level 1" might only require username and password verification, while "Level 2" might require a username and password plus a text message verification code or fingerprint recognition.

[0121] Determine the level of identity authentication required based on the user's responsibilities and permissions, allowing for appropriate authentication strength. Implement multi-level identity authentication to ensure varying levels of access control for data of varying sensitivities. The system queries the claims specialist's company identity authentication level based on their employee ID.

[0122] The system typically maintains a mapping table between user roles and authentication levels. For example, a "normal user" might be assigned "authentication level 2," while an "administrator" or "core business operator" might be assigned "authentication level 1." Furthermore, authentication levels can be dynamically adjusted. For example, if a user accesses from an unusual location or device, even a normal user might be required to upgrade their authentication level.

[0123] Step S630: When the identity authentication level is lower than the preset level threshold, the identity information is authenticated to obtain an authentication result.

[0124] Specifically, the system will compare the user's authentication level with a preset level threshold. If the user's authentication level is lower than or equal to the threshold, the system will perform the actual authentication process on the identity information and generate an authentication result.

[0125] The preset level threshold is a configurable security parameter that determines when mandatory authentication is triggered. For example, if the threshold is set to "Level 1," all users requiring Level 1 or higher authentication must be authenticated. If certain public resources do not require any authentication, these requests will not trigger this authentication step. Authentication methods can include single-factor authentication and biometric authentication. The authentication result is typically "Authentication passed" or "Authentication failed."

[0126] In one example, the system's preset threshold requires all users who need to access sensitive data to meet at least "Intermediate" authentication strength. Since the claims adjuster is assigned an "Intermediate" authentication level, the system will require them to perform two-factor authentication using fingerprint recognition and a dynamic password. Upon successful authentication, they will receive an "Authentication Passed" result.

[0127] Step S640: If the authentication result indicates that the identity information authentication is successful, determine the access permission corresponding to the access request.

[0128] Specifically, based on user roles and permissions, the scope of access and types of operations to different data are precisely controlled, implementing the principle of least privilege. After identity authentication, the system determines the claims specialist's access rights to specific claims data based on their identity and responsibilities. For example, a junior claims adjuster might only be able to view partially de-identified claims information, while a senior claims adjuster can view more detailed information.

[0129] By strictly authenticating identity information, the system verifies the true identity of the requester, ensuring that only legitimately verified users can access subsequent resources. This effectively prevents unauthorized access attempts and improves data confidentiality and integrity. The authentication results also provide a basis for subsequent permission determination.

[0130] In some embodiments, after step S640, the following steps may be performed, but are not limited to:

[0131] Step S641: Generate an access log based on the access request.

[0132] Specifically, regardless of the identity authentication result, every time the system receives an access request from a second device, a detailed access log is immediately generated. The log record includes but is not limited to: timestamp, user identity information, source IP address, device information, etc.

[0133] Step S642: Periodically check the access log to obtain check data.

[0134] Specifically, the system also periodically checks these logs. For example, at preset intervals, the system automatically or semi-automatically analyzes accumulated access log data to identify potential security threats or abnormal patterns, thereby generating verification data. Verification data is the output of the analysis process. It is not the raw logs themselves, but rather a summary and description of suspicious behavior, abnormal events, or statistical anomalies found in the logs.

[0135] Verification can be achieved through rule matching, matching based on preset security rules, such as: "The same user fails to log in multiple times in a short period of time", "The user accesses sensitive data during non-working hours", "The same user from different geographical locations logs in simultaneously", "Unauthorized users attempt to access sensitive resources", and "Users frequently access data types that are inconsistent with their responsibilities". Verification can also be achieved through baseline analysis. A baseline of normal user or device behavior is established in advance, and behavior that deviates from the baseline is detected. For example, a claims adjuster usually only accesses claims data in a specific area. If they suddenly start accessing large amounts of data in other areas, this may be marked as an anomaly.

[0136] Step S643: When the inspection data indicates that there is an access anomaly in the access request, a warning message is issued and the inspection data is displayed.

[0137] Specifically, when the inspection data clearly indicates that a certain access request has an access anomaly, the system will immediately issue a warning message and display the inspection data.

[0138] Warning information can be provided in a variety of formats to ensure timely notification to relevant security personnel. These include real-time alerts, email notifications, and automatic blocking. When issuing a warning, the system also displays relevant verification data to the recipient. This data includes a detailed description of the abnormal event, the time, users involved, resources involved, the abnormality type, and any supporting evidence, enabling security personnel to quickly understand the abnormal situation and conduct preliminary analysis and decision-making.

[0139] By issuing timely, multi-channel warnings and providing detailed verification data, the system ensures that security teams are immediately aware of potential threats. This significantly shortens the time it takes to discover and respond to security incidents, allowing organizations to take swift action to contain the damage and mitigate potential losses, thereby comprehensively improving the security resilience of the system.

[0140] In some embodiments, after step S500, the following steps may be performed, but are not limited to:

[0141] Step S710: When the confidentiality level is higher than a preset threshold, the identification data storage is mapped to a corresponding virtual address space based on memory mapping.

[0142] Specifically, when the confidentiality level of the identification data is higher than a preset threshold, the system will use memory mapping technology to directly map the content of the identification data in the storage medium to the virtual address space of the process.

[0143] This threshold is a critical point set by the system based on data sensitivity and security policies. For example, if the threshold is "Confidential", all data with a "Confidential" level or above will trigger this memory mapping mechanism.

[0144] Memory mapping allows part of the file or device memory to be directly visible in the virtual address space of the process. When the process needs to access this data, it does not need to go through traditional read and write system calls, but directly accesses the memory address through a pointer.

[0145] The system can set fine-grained access permissions (read, write, execute) for memory-mapped areas and use virtual memory mechanisms to isolate and prevent unauthorized access. The data itself may still reside on the encrypted storage device, but when mapped into memory, the operating system or hardware security module will be responsible for real-time decryption.

[0146] In one example, once "Level 1 Confidential" claims data for financial and insurance users or "Extremely Confidential" health data for healthcare users is stored, because its confidentiality level exceeds a preset threshold (e.g., the "Highly Sensitive Data Threshold"), the system uses memory mapping technology to map this identifying data to a separate and protected virtual address space in the server's memory. This means that the data is not loaded directly from disk into the regular memory area, but is accessed indirectly through virtual addresses, enhancing data security.

[0147] Step S720: When an access request from the second device is obtained, determine an access pointer based on the access request.

[0148] Specifically, when the system receives an access request from the second device, this step determines an access pointer based on the content of the request. The system then searches an internal index table or metadata management system based on the unique identifier of the target data included in the access request. This index table stores the mapping between identifiers and actual data storage locations.

[0149] If the data is memory-mapped, the access pointer will point directly to its starting address in the virtual address space. If the data is not yet memory-mapped (for example, because its confidentiality level is below a threshold or it is mapped only when needed), the access pointer may point to its logical address or physical storage block in persistent storage (such as a database or file system). This pointer does not directly expose the raw sensitive data, but is a reference to encrypted, desensitized identifying data. It may be a virtual memory address, a file offset, a database record ID, or some internal data structure handle.

[0150] By converting abstract access requests into concrete access pointers, the system can efficiently locate the exact location of the target identification data in the storage system or memory. This simplifies the complexity of subsequent data acquisition and ensures that legitimate access requests can be responded to quickly and accurately while protecting data privacy and security.

[0151] Step S730: Obtain identification data corresponding to the access request according to the access pointer.

[0152] Specifically, if the access pointer points to a virtual address space, the system can directly read the identification data in memory through this pointer. If the access pointer points to persistent storage, the system will retrieve the data block based on the pointer through the file system interface, database query interface, or object storage API. The retrieved data is identification data, so it is displayed in a desensitized and encrypted form. Only when the user has sufficient permissions and the business process requires it, will the system further perform decryption and de-identification (or partial de-identification) operations and display the data to the user.

[0153] By securely and efficiently utilizing access pointers, the system accurately retrieves the identification data requested by the user or system. This not only ensures the correctness and integrity of data access, but also, because it operates on rigorously processed "identification data," further strengthens privacy protection during data access. This mechanism supports the efficient operation of data services while strictly adhering to the principle of least privilege and data security policies.

[0154] Figure 5 This is a schematic diagram of the structure of the data management device provided in the embodiment of the present application. Figure 5 The embodiment of the present application further provides a data management device 800, which can implement the above-mentioned data management method. The data management device 800 includes:

[0155] An extraction module 801 is configured to extract the acquired transmission data of the first device and obtain a check code and device information, where the device information indicates a type of device that sent the transmission data.

[0156] a desensitizing module 802 for desensitizing the transmitted data when the transmission data is confirmed to be qualified according to the verification code, and determining a confidentiality level corresponding to the transmitted data according to the device type indicated by the device information;

[0157] The encryption module 803 is used to encrypt the desensitized transmission data according to the encryption method corresponding to the confidentiality level to obtain encrypted data;

[0158] The identification module 804 is used to perform identification processing on the encrypted data to generate identification data, wherein the identification data has a unique identifier;

[0159] The storage module 805 is configured to store the identification data in a target storage area, where the target storage area is determined according to the device type indicated by the device information.

[0160] The transmission data includes operation data and storage data; the encryption module includes:

[0161] an operation encryption unit, configured to determine, when the transmission data is operation data, an encryption method for the transmission data from a preset dynamic encryption library according to the confidentiality level;

[0162] The storage encryption unit is used to determine the encryption method of the transmission data from a preset static encryption library according to the confidentiality level when the transmission data is storage data.

[0163] The storage module includes:

[0164] a first determining unit, configured to determine a first storage area according to a device type indicated by the device information;

[0165] a second determining unit, configured to determine, according to the confidentiality level, a second storage area corresponding to the confidentiality level from the first storage area;

[0166] The third storage unit is configured to use the second storage area as the target storage area and store the identification data in the target storage area.

[0167] The desensitization module includes:

[0168] an acquiring unit, configured to acquire first key data from the transmission data when the transmission data is confirmed to be qualified according to the check code;

[0169] a third determining unit, configured to determine an iteration area and a conversion area according to the first key data;

[0170] The desensitizing unit is used to iteratively encrypt the iteration area and the conversion area based on a preset desensitizing algorithm until the number of iterations meets a preset value, thereby obtaining desensitized transmission data.

[0171] The device further includes an authentication module, which is configured to:

[0172] In response to the acquired access request from the second device, extract the access request to obtain identity information, where the identity information is used to indicate the identity of the user who issued the access request;

[0173] determining an identity authentication level of the user according to the user identity indicated by the identity information;

[0174] When the identity authentication level is lower than a preset level threshold, authenticating the identity information to obtain an authentication result;

[0175] If the authentication result indicates that the identity information authentication is successful, the access permission corresponding to the access request is determined.

[0176] The device further comprises an early warning unit, which is configured to:

[0177] generating an access log based on the access request;

[0178] Periodically checking the access log to obtain verification data;

[0179] When the inspection data indicates that there is an access anomaly in the access request, an early warning message is issued and the inspection data is displayed.

[0180] The apparatus further includes a mapping module, configured to:

[0181] When the confidentiality level is higher than a preset threshold, storing the identification data in a corresponding virtual address space based on memory mapping;

[0182] Upon receiving an access request from a second device, determining an access pointer based on the access request;

[0183] According to the access pointer, identification data corresponding to the access request is obtained.

[0184] The present application also provides an electronic device comprising a memory and a processor, wherein the memory stores a computer program, and the processor implements the above-described data management method when executing the computer program. The electronic device can be any intelligent terminal including a desktop computer, a tablet computer, a mobile phone, and an in-vehicle computer.

[0185] See also Figure 6 , Figure 6This is a schematic diagram of the hardware structure of an electronic device provided in an embodiment of the present application. The electronic device includes:

[0186] The processor 901 can be implemented as a general-purpose CPU (Central Processing Unit), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of the present application;

[0187] The memory 902 can be implemented in the form of a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). The memory 902 can store an operating system and other application programs. When the technical solutions provided in the embodiments of this specification are implemented through software or firmware, the relevant program codes are stored in the memory 902 and are called by the processor 901 to execute the data management method of the embodiments of this application.

[0188] Input / output interface 903, used to implement information input and output;

[0189] Communication interface 904, used to implement communication interaction between this device and other devices, which can be achieved through wired means (such as USB, network cable, etc.) or wireless means (such as mobile network, WiFi, Bluetooth, etc.);

[0190] Bus 905 , which transmits information between various components of the device (e.g., processor 901 , memory 902 , input / output interface 903 , and communication interface 904 );

[0191] The processor 901 , the memory 902 , the input / output interface 903 and the communication interface 904 are connected to each other in communication within the device via a bus 905 .

[0192] An embodiment of the present application further provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, the above-mentioned data management method is implemented.

[0193] The memory, as a non-transient computer-readable storage medium, can be used to store non-transient software programs and non-transient computer executable programs. In addition, the memory may include a high-speed random access memory and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some embodiments, the memory may optionally include a memory remotely arranged relative to the processor, and these remote memories may be connected to the processor via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0194] In addition, the embodiments of the present application may be implemented by providing a computer program product. When the instructions in the computer program product are executed by a processor of an electronic device, the electronic device implements the data management method in the above embodiments.

[0195] The data management method, device, electronic device and medium provided by the embodiments of the present application include: responding to the transmission data of the first device obtained, extracting the transmission data to obtain a verification code and device information; when the transmission data is confirmed to be qualified according to the verification code, desensitizing the transmission data, and determining the encryption confidentiality level corresponding to the transmission data according to the device type indicated by the device information; encrypting the desensitized transmission data using an encryption method according to the encryption method corresponding to the confidentiality level to obtain encrypted data; desensitizing and identifying the encrypted data to obtain encrypted identification data after desensitization; and storing the desensitized encrypted data identification data in a target storage area.

[0196] The embodiments described in the embodiments of this application are intended to more clearly illustrate the technical solutions of the embodiments of this application and do not constitute a limitation on the technical solutions provided by the embodiments of this application. Those skilled in the art will appreciate that with the evolution of technology and the emergence of new application scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0197] Those skilled in the art will understand that the technical solutions shown in the figures do not constitute a limitation on the embodiments of the present application, and may include more or fewer steps than shown in the figures, or a combination of certain steps, or different steps.

[0198] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, i.e., they may be located in one place or distributed across multiple network units. Some or all of the modules may be selected based on actual needs to achieve the objectives of this embodiment.

[0199] Those skilled in the art can understand that all or some of the steps in the method disclosed above, the function modules / units in the system and the device can be implemented as software, firmware, hardware or appropriate combination thereof.

[0200] The terms "first", "second", "third", "fourth" and the like in the description of the application and in the claims, if any, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the use of these terms herein is to be construed to cover a general order and / or structure unless otherwise indicated. Furthermore, the terms "comprise", "have" and "include" and any variations thereof are intended to cover a non-exclusive inclusion, such that a process, method, system, product or apparatus that comprises, has or includes a list of elements is not necessarily limited to those elements, but can include other elements not expressly listed or inherent to such process, method, system, product or apparatus.

[0201] It should be understood that, in the present application, "at least one" means one or more, and "multiple" means two or more. "And / or" is used to describe the relationship between associated objects, which means that there can be three relationships, for example, "A and / or B" can mean that there are three cases: only A, only B, and A and B at the same time, where A and B can be singular or plural. The character " / " generally represents an "or" relationship between the associated objects. "At least one of the following" or similar expressions means any combination of these items, including any combination of single or multiple items. For example, at least one of a, b or c can mean a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, and c can be single or multiple.

[0202] In several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the above-mentioned units is only a logical function division, and actual implementation can have another division manner, for example, a plurality of units or components can be combined or integrated into another system, or some features can be omitted or not executed. In addition, the coupling or direct coupling or communication connection between the displayed or discussed objects can be indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0203] The units described above as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0204] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0205] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium and includes multiple instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of various embodiments of the present application. The aforementioned storage medium includes: various media that can store programs, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0206] The preferred embodiments of the present invention are described above with reference to the accompanying drawings, but are not intended to limit the scope of the present invention. Any modifications, equivalent substitutions, and improvements made by those skilled in the art without departing from the scope and essence of the present invention should be within the scope of the present invention.

Claims

1. A data management method, characterized in that: The method comprises: In response to the acquired transmission data of the first device, extract the transmission data to obtain a check code and device information, where the device information is used to indicate a type of device sending the transmission data; When the transmission data is confirmed to be qualified according to the verification code, the transmission data is desensitized, and the confidentiality level corresponding to the transmission data is determined according to the device type indicated by the device information; Encrypting the desensitized transmission data according to the encryption method corresponding to the confidentiality level to obtain encrypted data; Performing identification processing on the encrypted data to obtain identification data, wherein the identification data has a unique identifier; The identification data is stored in a target storage area, where the target storage area is determined according to the device type indicated by the device information.

2. The method according to claim 1, characterized in that The transmission data includes operation data and storage data; The step of encrypting the desensitized transmission data according to the encryption method corresponding to the confidentiality level to obtain encrypted data includes: In the case where the transmission data is operation data, determining the encryption method of the transmission data from a preset dynamic encryption library according to the confidentiality level; In the case where the transmission data is storage data, the encryption method of the transmission data is determined from a preset static encryption library according to the confidentiality level.

3. The method according to claim 1, characterized in that Storing the identification data in a target storage area includes: determining a first storage area according to a device type indicated by the device information; According to the confidentiality level, determining a second storage area corresponding to the confidentiality level from the first storage area; The second storage area is used as the target storage area, and the identification data is stored in the target storage area.

4. The method according to claim 1, wherein When the transmission data is confirmed to be qualified according to the verification code, desensitizing the transmission data includes: When the transmission data is confirmed to be qualified according to the verification code, obtaining first key data in the transmission data; Determining an iteration area and a conversion area according to the first key data; Based on a preset desensitizing algorithm, the iteration area and the conversion area are iteratively encrypted until the number of iterations meets a preset value, thereby obtaining desensitized transmission data.

5. The method according to any one of claims 1 to 4, characterized in that The method further comprises: In response to the acquired access request from the second device, extract the access request to obtain identity information, where the identity information is used to indicate the identity of the user who issued the access request; determining an identity authentication level of the user according to the user identity indicated by the identity information; When the identity authentication level is lower than a preset level threshold, authenticating the identity information to obtain an authentication result; If the authentication result indicates that the identity information authentication is successful, the access permission corresponding to the access request is determined.

6. The method according to claim 5, characterized in that If the authentication result indicates that the identity information authentication is successful, after determining the access rights corresponding to the access request, the method further includes: generating an access log based on the access request; Periodically checking the access log to obtain verification data; When the inspection data indicates that there is an access anomaly in the access request, an early warning message is issued and the inspection data is displayed.

7. The method according to any one of claims 1 to 4, characterized in that After storing the identification data in the target storage area, the method further includes: When the confidentiality level is higher than a preset threshold, mapping the identification data storage to a corresponding virtual address space based on memory mapping; Upon receiving an access request from a second device, determining an access pointer based on the access request; According to the access pointer, identification data corresponding to the access request is obtained.

8. A data management device, characterized in that: The device comprises: an extraction module, configured to respond to the acquired transmission data of the first device, extract the transmission data, obtain a check code and device information, wherein the device information is used to indicate a type of device sending the transmission data; a desensitizing module, configured to desensitize the transmission data when the transmission data is confirmed to be qualified according to the verification code, and determine the confidentiality level corresponding to the transmission data according to the device type indicated by the device information; An encryption module, configured to encrypt the desensitized transmission data according to an encryption method corresponding to the confidentiality level to obtain encrypted data; an identification module, configured to perform identification processing on the encrypted data to generate identification data, wherein the identification data has a unique identifier; The storage module is used to store the identification data in a target storage area, where the target storage area is determined according to the device type indicated by the device information.

9. An electronic device, characterized in that: The electronic device includes a memory and a processor, the memory stores a computer program, and the processor implements the data management method according to any one of claims 1 to 7 when executing the computer program.

10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the data management method according to any one of claims 1 to 7 is implemented.

Images