Data query method and device, computer equipment and storage medium

Abstract

The invention belongs to the technical field of data processing, and relates to a data query method and device, computer equipment and a storage medium, and the method comprises the steps: receiving a file downloading request triggered by a user through a target interface; wherein the file downloading request at least carries a message and a service parameter; if the user role type is an external user, checking an IP address corresponding to the file downloading request based on an IP white list; if the IP address passes the verification, performing field verification on the service parameters; if the service parameters pass the field verification, parsing the message to obtain parsed data; verifying the analysis data based on a message verification strategy; if the analysis data passes the verification, responding to the file downloading request to query a corresponding first file, and encrypting and signing the first file to obtain a target file; and sending the target file to the user. The data query method and device can be applied to data query scenes in the financial field and the medical field, and the security of data query is effectively improved.

Description

Technical Field

[0001] This application relates to the field of data processing and can be applied to fields such as fintech and digital healthcare, particularly to data query methods, devices, computer equipment, and storage media. Background Technology

[0002] Traditional document data service models suffer from serious security vulnerabilities in the access and transmission management of consumers' personal document data (such as electronic insurance policies and invoices in the insurance sector, and medical data in the medical field). Specifically, current data query methods lack effective identity authentication and authorization mechanisms, allowing unauthorized individuals and organizations to easily obtain document data containing customers' personal information. This insecure transmission and access method exposes consumers' personal information to an extremely high risk of leakage. Once leaked, it could not only trigger criminal cases but also seriously damage consumers' legitimate rights and interests.

[0003] For example, in the financial sector, if an electronic insurance policy is illegally obtained during transmission after a consumer purchases an insurance product, attackers may use the customer information to commit fraud or other illegal activities. In the medical field, if a patient's medical data (such as personal health records, prescriptions, and examination reports) is leaked, it may lead to the exposure of the patient's privacy and even affect the patient's normal life and treatment.

[0004] Therefore, there is an urgent need to provide a secure and reliable method for querying and transmitting file data to ensure that only the consumer or authorized personnel and organizations can view and download file data, and to effectively prevent data leakage during the transmission process. Summary of the Invention

[0005] The purpose of this application is to provide a data query method, apparatus, computer device, and storage medium to solve the technical problem of low security in existing data query methods.

[0006] Firstly, a data query method is provided, including:

[0007] Receive a file download request triggered by a user through a target interface; wherein the file download request carries at least a message and business parameters;

[0008] Obtain the user role type of the user, and determine whether the user role type is an external user;

[0009] If the user role type is an external user, the IP address corresponding to the file download request is verified based on a preset IP whitelist.

[0010] If the IP address passes the verification, then the business parameters are validated.

[0011] If the business parameters pass the field validation, the message is parsed to obtain the corresponding parsed data;

[0012] The parsed data is verified based on a preset message verification strategy;

[0013] If the parsed data passes the verification, the file download request is responded to to retrieve the corresponding first file, and the first file is encrypted and signed to obtain the corresponding target file;

[0014] The target file is sent to the user.

[0015] Secondly, a data query device is provided, comprising:

[0016] The receiving module is used to receive file download requests triggered by users through the target interface; wherein the file download request carries at least a message and service parameters;

[0017] The first judgment module is used to obtain the user role type of the user and determine whether the user role type is an external user;

[0018] The first verification module is used to verify the IP address corresponding to the file download request based on a preset IP whitelist if the user role type is an external user.

[0019] The second verification module is used to perform field verification on the business parameters if the IP address passes the verification.

[0020] The parsing module is used to parse the message to obtain the corresponding parsed data if the business parameters pass the field validation.

[0021] The third verification module is used to verify the parsed data based on a preset message verification strategy.

[0022] The first processing module is used to respond to the file download request if the parsed data passes the verification, to query the corresponding first file, and to encrypt and sign the first file to obtain the corresponding target file.

[0023] The first sending module is used to send the target file to the user.

[0024] Thirdly, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the above-described data query method.

[0025] Fourthly, a computer-readable storage medium is provided, which stores a computer program that, when executed by a processor, implements the steps of the above-described data query method.

[0026] In the above-described data query method, apparatus, computer equipment, and storage medium, the following steps are taken: First, a file download request triggered by a user through a target interface is received; wherein the file download request carries at least a message and business parameters; then, the user's user role type is obtained, and it is determined whether the user role type is an external user; if the user role type is an external user, the IP address corresponding to the file download request is verified based on a preset IP whitelist; if the IP address passes the verification, the business parameters are verified; if the business parameters pass the field verification, the message is parsed to obtain corresponding parsed data; subsequently, the parsed data is verified based on a preset message verification strategy; if the parsed data passes the verification, the file download request is responded to to query the corresponding first file, and the first file is encrypted and signed to obtain the corresponding target file; finally, the target file is sent to the user. Based on the above processing flow, this application combines a multi-layered verification mechanism, including IP address verification, business parameter verification, and parsed data verification, to perform access control on the data query processing corresponding to file download requests. This effectively improves the security and reliability of data queries, ensures information security during the data query interaction process, and helps protect the system from threats of unauthorized access and data tampering. Attached Figure Description

[0027] To more clearly illustrate the solutions in this application, the accompanying drawings used in the description of the embodiments of this application will be briefly introduced below. Obviously, the accompanying drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0028] Figure 1 This is an exemplary system architecture diagram to which this application can be applied;

[0029] Figure 2 This is a flowchart of an embodiment of the data query method according to this application;

[0030] Figure 3 This is a schematic diagram of the structure of one embodiment of the data query device according to this application;

[0031] Figure 4 This is a schematic diagram of the structure of one embodiment of the computer device according to this application. Detailed Implementation

[0032] 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 this application pertains; the terminology used herein in the specification of the application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application; the terms "comprising" and "having," and any variations thereof, in the specification, claims, and foregoing drawings of this application, are intended to cover non-exclusive inclusion. The terms "first," "second," etc., in the specification, claims, or foregoing drawings of this application are used to distinguish different objects, not to describe a particular order.

[0033] In this document, the term "embodiment" means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0034] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings.

[0035] like Figure 1 As shown, system architecture 100 may include terminal device 101, network 102, and server 103. Terminal device 101 may be a laptop 1011, tablet 1012, or mobile phone 1013. Network 102 is used as a medium to provide a communication link between terminal device 101 and server 103. Network 102 may include various connection types, such as wired, wireless communication links, or fiber optic cables, etc.

[0036] Users can use terminal device 101 to interact with server 103 via network 102 to receive or send messages, etc. Various communication client applications can be installed on terminal device 101, such as web browser applications, shopping applications, search applications, instant messaging tools, email clients, social media platform software, etc.

[0037] Terminal device 101 can be various electronic devices with a display screen and support web browsing. In addition to laptops 1011, tablets 1012, or mobile phones 1013, terminal device 101 can also be an e-book reader, an MP3 player (Moving Picture Experts Group Audio Layer III), an MP4 player (Moving Picture Experts Group Audio Layer IV), a laptop computer, and a desktop computer, etc.

[0038] Server 103 can be a server that provides various services, such as a backend server that provides support for the pages displayed on terminal device 101.

[0039] It should be noted that the data query method provided in this application embodiment is generally executed by a server / terminal device, and correspondingly, the data query device is generally set in the server / terminal device.

[0040] It should be understood that Figure 1 The number of terminal devices, networks, and servers shown is merely illustrative. Depending on implementation needs, any number of terminal devices, networks, and servers can be included.

[0041] Continue to refer to Figure 2 The flowchart illustrates an embodiment of the data query method according to this application. Depending on different needs, the order of the steps in the flowchart can be changed, and some steps can be omitted. The data query method provided by this application embodiment can be applied to any scenario requiring data querying, and thus can be applied to products in these scenarios, such as data query scenarios in the financial and medical fields. The data query method includes the following steps:

[0042] Step S201: Receive a file download request triggered by the user through the target interface; wherein the file download request carries at least a message and service parameters.

[0043] In this embodiment, the data query method runs on an electronic device (e.g., Figure 1The server / terminal device shown can acquire the image to be checked via wired or wireless connection. It should be noted that the aforementioned wireless connection methods may include, but are not limited to, 3G / 4G / 5G connections, WiFi connections, Bluetooth connections, WiMAX connections, Zigbee connections, UWB (ultra-wide wireless) connections, and other currently known or future-developed wireless connection methods. The executing entity of this application is specifically a data query system, which can be simply referred to as the system. The aforementioned users can be internal users (internal employees) or external users (external partners, which can be simply referred to as partners). Specifically, users will be pre-classified into two main categories—internal employees and external partners—based on business needs, and different permission groups will be assigned to each category. Detailed permission rules will be set for each category of users in the permission management system. For example, internal employees may have permission to view and download files, while external partners may only have permission to download specific types of files. The permission rules will be stored in the permission database to ensure that the system can quickly query and verify user permissions with each access request. The aforementioned target interface can be a file download interface in a pre-maintained list of interfaces that users have permissions for. The above message is a complete message data assembled from ciphertext, signature, and encrypted key. The above business parameters can also be referred to as business fields.

[0044] This application can be applied to data query scenarios in the financial and medical fields. For example, in the financial field, the aforementioned document download request could be related to an electronic insurance policy. In the medical field, the aforementioned document download request could be related to medical data. Medical data may include data such as personal health records, prescriptions, and examination reports.

[0045] Specifically, the system's request management process for external partners includes:

[0046] 1. The initial authentication process:

[0047] Authentication Request: When an external partner attempts to connect to the system for the first time, they must initiate an authentication request via a specified method (such as SMS verification code or whitelisted IP). Validity Verification: The system generates an SMS verification code valid for two minutes, or verifies whether the partner's IP is on a pre-defined whitelist. Security Certificate and Algorithm Download: After successful verification, the system allows the partner to download the security certificate and algorithm name required for communication. This information will be used for subsequent encrypted communication.

[0048] 2. IP configuration implementation process:

[0049] Initial Access Permissions: For the first 7 days after a partner's initial successful integration, the system will by default allow any IP address to access the system as that partner, giving the partner sufficient time to configure their IP list. IP List Configuration: Within these 7 days, the partner must add their legitimate IP addresses to the list individually or in batches using the interface or tools provided by the system. The system will provide a list of IP addresses that have requested access from the partner within the past 7 days for easy selection. IP Access Control: If the partner fails to configure their IP list within the specified time, the system will by default reject all access requests from unknown IP addresses, even if these requests carry legitimate encryption and signature information. IP Change Handling: If the partner subsequently changes their IP addresses, they must update the IP list in the system beforehand to ensure that the new IP addresses can be recognized and allowed access by the system.

[0050] 3. The process of requesting encryption and signing:

[0051] Encryption Preparation: After receiving the security certificate and algorithm name, the partner initiates a request to the system using an IP address from their IP list. Key Generation: With each request, the partner generates a new key for a symmetric encryption algorithm in real time, ensuring that the key is different for each request to enhance security. Data Encryption and Signing: The partner encrypts the original plaintext data using a symmetric encryption algorithm to obtain ciphertext. Then, a fingerprint is extracted using the security certificate as a signature to sign the ciphertext. Key Encryption and Message Assembly: The symmetric encryption algorithm key is encrypted using an asymmetric encryption algorithm and the security certificate to form an encrypted key. Finally, the ciphertext, signature, and encrypted key are assembled into a complete message and sent to the system.

[0052] 4. Implementation process of interface permission management:

[0053] Interface List Maintenance: During initial integration, the system administrator will maintain a list of authorized interfaces for partners, clearly defining which interfaces the partner can call. Interface Access Control: The system will verify the partner's permission to access the interface with each request. If a partner attempts to access an interface they have not requested, the system will reject the request.

[0054] 5. Implementation process of business field validation: Business field extraction: For interfaces involving the download of sensitive files (such as electronic insurance policies and invoices), the system will extract key business fields from the request, such as the last 6 digits of the policyholder's or insured's identification number. Business permission validation: The system uses information shared by both parties (such as pre-shared business data) to validate the extracted business fields, ensuring that the partner's download request is compliant and authorized.

[0055] 6. Signature Record Implementation Process: Signature Processing: Regardless of whether the electronic policy has a customer signature or not, when an external partner requests to download it, the policy issuance / modification system will record the signature information of both the system and the partner in the file. Signature Consistency: The signature recording method is consistent with the signature method used by internal employees when downloading electronic policies, ensuring that regardless of who downloads the file, the responsible party can be traced through the signature information.

[0056] The key aspects of this system include: The connection between initial connection authentication and IP configuration: Initial connection authentication is a prerequisite for IP configuration; only authenticated partners can perform subsequent IP configuration and access control. The connection between IP configuration and request encryption: IP configuration ensures that only legitimate IP addresses can initiate requests, while request encryption and signing further guarantee the security of these requests during transmission. The connection between interface permission management and business field verification: Both constitute a multi-layered control over partner access permissions, limiting the range of interfaces a partner can access while ensuring compliance for each access through business field verification. The connection between signature records and the overall process: Signature records are integrated throughout the entire external partner management process. Whether it's authentication, IP configuration, request encryption, or interface access, traceable traces are left through signature information, providing strong support for subsequent leak tracing.

[0057] Step S202: Obtain the user role type of the user and determine whether the user role type is an external user.

[0058] In this embodiment, the user's role type can be obtained by querying the user's user information (such as name). The user role type includes internal users (internal employees) or external users (external partners, which can be simply referred to as partners).

[0059] Step S203: If the user role type is an external user, then the IP address corresponding to the file download request is verified based on a preset IP whitelist.

[0060] In this embodiment, the system checks whether the IP address initiating the file download request is in the user-pre-configured IP whitelist. If the IP address is in the whitelist, the IP address passes verification. If the IP address is not in the whitelist, the IP address fails verification, and the system refuses to respond to the file download request, even if other verification steps pass.

[0061] Step S204: If the IP address passes the verification, then perform field verification on the service parameters.

[0062] In this embodiment, the aforementioned business parameters, such as the last 6 digits of the user's ID number, can be extracted from the file download request. Then, the system uses shared information (such as pre-shared business data) to verify the extracted business parameters, ensuring that the user's file download request is compliant and authorized, and generates corresponding parameter verification results. These results include whether the business parameters pass field verification or fail field verification.

[0063] Step S205: If the business parameters pass the field validation, the message is parsed to obtain the corresponding parsed data.

[0064] In this embodiment, after detecting that the above-mentioned business parameters have passed the field verification, the system will receive the message carried in the above-mentioned file download request and parse the message to obtain the three main parts of the message, namely the above-mentioned parsed data. The parsed data includes ciphertext, signature and encrypted symmetric encryption key.

[0065] Step S206: Verify the parsed data based on a preset message verification strategy.

[0066] In this embodiment, the specific implementation process of verifying the parsed data based on the preset message verification strategy will be further described in detail in subsequent specific embodiments of this application, and will not be elaborated on here.

[0067] Step S207: If the parsed data passes the verification, respond to the file download request to query the corresponding first file, and encrypt and sign the first file to obtain the corresponding target file.

[0068] In this embodiment, the above-described specific implementation process of responding to the file download request to query the corresponding first file, and encrypting and signing the first file to obtain the corresponding target file will be further described in detail in subsequent specific embodiments of this application, and will not be elaborated on here.

[0069] The target file is sent to the user.

[0070] In this embodiment, the target file can be sent to the user via email or a user interface to complete the response to the file download request.

[0071] This application first receives a file download request triggered by a user through a target interface; wherein the file download request carries at least a message and business parameters; then, it obtains the user's user role type and determines whether the user role type is an external user; if the user role type is an external user, it verifies the IP address corresponding to the file download request based on a preset IP whitelist; if the IP address passes the verification, it performs field verification on the business parameters; if the business parameters pass the field verification, it parses the message to obtain the corresponding parsed data; subsequently, it verifies the parsed data based on a preset message verification strategy; if the parsed data passes the verification, it responds to the file download request to query the corresponding first file, and encrypts and signs the first file to obtain the corresponding target file; finally, it sends the target file to the user. Based on the above processing flow, this application uses a multi-layered verification mechanism combining IP address verification, business parameter verification, and parsed data verification to perform access control on the data query processing corresponding to the file download request, effectively improving the security and reliability of data query, ensuring information security during the data query interaction process, and helping to protect the system from threats of unauthorized access and data tampering.

[0072] In some optional implementations, the parsed data includes ciphertext, a signature, and an encrypted symmetric encryption key; step S206 includes the following steps:

[0073] The encrypted symmetric encryption key is decrypted to obtain the corresponding original symmetric encryption key.

[0074] In this embodiment, the system uses the private key of the asymmetric encryption algorithm, which is pre-shared with the user (usually stored in a secure environment, such as a hardware security module HSM), to decrypt the encrypted symmetric encryption key, obtaining the original symmetric encryption key. If decryption fails, it indicates that the key may have been tampered with or the sender is illegitimate; in this case, the system will refuse to process the file download request.

[0075] The ciphertext is decrypted based on the original symmetric encryption key.

[0076] In this embodiment, the ciphertext is decrypted using the original symmetric encryption key obtained through decryption to obtain the original plaintext data. If the decrypted data is in an incorrect format or cannot be parsed, it may indicate that the ciphertext has been tampered with or the key does not match; in such cases, the system will refuse to process the file download request.

[0077] If decryption is successful, the signature is verified based on preset signature verification rules.

[0078] In this embodiment, the specific implementation process of verifying the signature based on the preset signature verification rules will be further described in detail in subsequent specific embodiments of this application, and will not be elaborated on here.

[0079] If the signature passes verification, the message is deemed to have passed verification.

[0080] In this embodiment, the message is deemed to have passed verification only if the encrypted symmetric encryption key is successfully decrypted, the ciphertext is successfully decrypted, and the signature is verified. Otherwise, the message is deemed to have failed verification.

[0081] If the signature fails verification, the message is determined to have failed verification.

[0082] In this embodiment, if the above message is determined to have failed verification, it indicates that the message data has been tampered with or the signature is invalid during transmission, and the system will refuse to respond to the above file download request.

[0083] This application decrypts the encrypted symmetric encryption key to obtain the corresponding original symmetric encryption key; then, it decrypts the ciphertext based on the original symmetric encryption key; if decryption is successful, the signature is verified based on a preset signature verification rule; if the signature passes verification, the message is deemed to have passed verification; if the signature fails verification, the message is deemed to have failed verification. Based on the above processing flow, this application, by combining multiple processing steps—decrypting the encrypted symmetric encryption key, decrypting the ciphertext based on the original symmetric encryption key, and verifying the signature based on signature verification rules—can efficiently and accurately complete message verification processing, improving the reliability and security of message verification, ensuring the accuracy of the generated message verification results, and effectively ensuring that the message originates from a legitimate object and has not been tampered with, thereby protecting the system from threats of unauthorized access and data tampering.

[0084] In some optional implementations of this embodiment, verifying the signature based on preset signature verification rules includes the following steps:

[0085] Extract the user's fingerprint information from the preset security certificate and verify the fingerprint information.

[0086] In this embodiment, the aforementioned security certificate is pre-cached by the system and matches the user's certificate information. This security certificate is issued by a trusted Certificate Authority (CA). The corresponding fingerprint information can be obtained by extracting a fingerprint from the security certificate. A fingerprint is a piece of data extracted from a security certificate to uniquely identify it. It is similar to a certificate's "digital fingerprint," helping the system quickly identify and verify the authenticity and integrity of the security certificate.

[0087] Specifically, verifying the aforementioned fingerprint information involves confirming the validity of the certificate corresponding to that fingerprint, ensuring that the certificate was issued by a trusted Certificate Authority. Specifically, the validity of the certificate can be confirmed by quickly querying the Certificate Revocation List (CRL) or the Online Certificate Status Protocol (OCSP) response using the fingerprint information. If the certificate is found to be valid, the fingerprint information is deemed to have passed verification; otherwise, if the certificate is found to be invalid, the fingerprint information is deemed to have failed verification.

[0088] The fingerprint information serves to ensure that the system uses the correct certificate and public key for signature verification, thereby indirectly supporting the hash value comparison process. The existence and verification of the fingerprint are an indispensable part of the entire signature verification process, ensuring its reliability and security.

[0089] If the fingerprint information is verified, the signature is decrypted based on the pre-shared public key corresponding to the user to obtain the corresponding original hash value.

[0090] In this embodiment, a pre-shared public key corresponding to the aforementioned user can be obtained from a trusted certificate authority, and the signature can be decrypted using this public key to obtain the corresponding original hash value.

[0091] Obtain the plaintext data obtained by decrypting the ciphertext, and perform a hash calculation on the plaintext data to obtain the corresponding specified hash value.

[0092] In this embodiment, the plaintext data can be hashed using the same calculation method as the original hash value to obtain the corresponding specified hash value.

[0093] Determine whether the original hash value is consistent with the specified hash value.

[0094] In this embodiment, the specified hash value obtained by calculating the plaintext data is compared with the original hash value obtained by decrypting the signature. If the two are the same, it is determined that the original hash value and the specified hash value are consistent. If the two are different, it is determined that the original hash value and the specified hash value are inconsistent.

[0095] If they match, the signature is deemed to have passed verification; otherwise, the signature is deemed to have failed verification.

[0096] In this embodiment, if the original hash value is found to match the specified hash value, the signature is deemed to have passed verification. However, if the original hash value is found to be inconsistent with the specified hash value, it indicates that the message data has been tampered with during transmission or the signature is invalid, and the system will refuse to process the file download request.

[0097] This application extracts the user's fingerprint information from a preset security certificate and verifies the fingerprint information. If the fingerprint information passes verification, the signature is decrypted using a pre-shared public key corresponding to the user to obtain the corresponding original hash value. Then, the plaintext data obtained by decrypting the ciphertext is acquired, and the plaintext data is hashed to obtain the corresponding specified hash value. Subsequently, it is determined whether the original hash value and the specified hash value are consistent. If they are consistent, the signature is determined to have passed verification; otherwise, the signature is determined to have failed verification. Based on the above processing flow, this application can automatically and accurately complete the signature verification process, effectively ensuring the reliability and security of the signature verification process and improving the accuracy of the generated signature verification results.

[0098] In some alternative implementations, step S207 includes the following steps:

[0099] The file download request is responded to in order to retrieve the corresponding first file.

[0100] In this embodiment, by performing response processing for the above-mentioned file download request, the file that matches the business parameters in the file download request, i.e., the first text mentioned above, can be retrieved from the corresponding file system.

[0101] Obtain the target file type of the first file.

[0102] In this embodiment, the target file type of the first file can be obtained by performing type analysis on the first file. The target file type may include a long-term storage file type or a regular file type. Furthermore, for each file, a type label is pre-assigned, and the file type can be obtained by querying the file's type label.

[0103] The corresponding target file signature strategy is determined based on the target file type.

[0104] In this embodiment, a first document signing strategy corresponding to long-term stored file types and a second document signing strategy corresponding to ordinary file types are pre-built. Specifically, the first document signing strategy includes: File upload: After generating the relevant file with the customer's signature, the system immediately uploads it to the file system for storage. Download request processing: When an internal employee or external partner requests to download the policy, the file system first copies the original file to generate a temporary copy. Signature writing: In the temporary copy, the file system writes the downloading system (such as the internal system name or partner name) and the downloader's identity information (such as employee ID or partner ID) into the PDF signature or file header. File return: The signed temporary copy is returned to the requester, while ensuring that only the original file is retained in the file system, and the signed copy is not retained to avoid storage redundancy.

[0105] Furthermore, the second document signing strategy includes the following: Document Printing: For ordinary documents without customer signatures, the system transmits the document information to the printing platform, which prints according to a preset format. Signing Processing: After printing, the system signs the document, adding the identity information of the system (e.g., order / correction system) and the downloader (e.g., employee or partner) to the PDF signature or document header. Document Storage and Return: The signed document can be stored in the file system or directly returned to the requester. Similarly, the system records relevant information about this signing operation for subsequent tracking.

[0106] The first file is encrypted and signed based on the target file signing strategy to obtain the processed second file.

[0107] In this embodiment, the first file can be encrypted and signed based on the processing steps corresponding to the strategy content of the target file signing strategy, and the generated second file can be used as the final target file.

[0108] Use the second file as the target file.

[0109] This application responds to file download requests to retrieve the corresponding first file; then obtains the target file type of the first file; and determines the corresponding target file signing strategy based on the target file type; subsequently, it encrypts and signs the first file based on the target file signing strategy to obtain a processed second file; the second file is then used as the target file. Based on this processing flow, this application responds to file download requests to retrieve the corresponding first file, then determines the corresponding target file signing strategy based on the target file type of the first file, and then automatically encrypts and signs the first file based on the use of the target file signing strategy, ensuring the security and intelligence of the obtained target file. By using different signing methods for different types of files, it can ensure that business needs are met while protecting sensitive customer information from being leaked.

[0110] In some alternative implementations, after step S202, the electronic device may further perform the following steps:

[0111] If the user role type is internal user, then the user's identity information is obtained, and the user is authenticated based on the identity information.

[0112] In this embodiment, the aforementioned identity information may refer to the username (or password) matched by the user. The aforementioned internal user is also known as an internal employee. When an internal user accesses the system, the system will verify the user's identity based on the aforementioned identity information. If the username (or password) passes verification, the user is deemed to have passed authentication; otherwise, if the username (or password) fails verification, the user is deemed to have failed authentication.

[0113] If the user is authenticated, the target permissions for the user are obtained based on the authentication information.

[0114] In this embodiment, after the user is authenticated, the system retrieves the user's current permissions, i.e., the target permissions, by querying the permissions database based on the user's identity information.

[0115] Determine whether the query operation corresponding to the file download request is within the scope of the target permissions.

[0116] In this embodiment, when a user sends a file to view or download the electronic insurance policy, the system re-verifies the target permissions to check whether the query operation corresponding to the file download request is within the scope of the target permissions.

[0117] If so, the file download request is responded to to retrieve the corresponding third file, and the third file is encrypted and signed to obtain the corresponding specified file.

[0118] In this embodiment, the process of responding to the file download request to retrieve the corresponding third file, and encrypting and signing the third file to obtain the corresponding specified file can be referred to the process of responding to the file download request to retrieve the corresponding first file, and encrypting and signing the first file to obtain the corresponding target file. It will not be elaborated further here.

[0119] Send the specified file to the user.

[0120] In this embodiment, the specified file can be sent to the user via email or a user interface to complete the response to the file download request. Additionally, the system records the user's (internal employee's) operation requests, including operation type, time, IP address, and other information, for subsequent auditing.

[0121] If this application detects that the user role type is an internal user, it obtains the user's identity information and verifies the user's identity based on the identity information. If the user passes the identity verification, it obtains the user's target permissions based on the identity information. Then, it determines whether the query operation corresponding to the file download request is within the scope of the target permissions. If so, it responds to the file download request to retrieve the corresponding third file, and encrypts and signs the third file to obtain the corresponding specified file. Subsequently, the specified file is sent to the user. Based on the above processing flow, when this application detects that the user role type is an internal user, it automatically and intelligently performs identity verification and permission verification on the user. Only when the user passes both identity verification and permission verification will it respond to the file download request, effectively improving the standardization and security of file download request processing.

[0122] In some optional implementations of this embodiment, after step S208, the electronic device may further perform the following steps:

[0123] Retrieve the preset information type.

[0124] In this embodiment, the above-mentioned information type is the type of log information that needs to be recorded as defined according to the actual log content. For example, it may include the downloader / system, IP address, HTTP header, timestamp, file summary (such as policy number), etc.

[0125] Based on a preset log collection strategy, target log data corresponding to the file download request is collected according to the information type.

[0126] In this embodiment, the log collection strategy includes deploying a log collection mechanism at key nodes of the system (such as file download interfaces) to ensure that all related operations are recorded in real time. Based on the log collection strategy, target log data corresponding to the aforementioned information types generated during the processing of the file download requests can be collected from the system.

[0127] Invoke the default log storage system.

[0128] In this embodiment, the selection of the above-mentioned log storage system is not specifically limited and can be determined according to actual business needs. For example, a local database, local disk, cloud server, blockchain, etc. can be used.

[0129] The target log data is stored in the log storage system.

[0130] In this embodiment, the target log data can be stored in a selected log storage system and a certain retention period (such as three years) can be set to meet the needs of subsequent auditing and tracking.

[0131] In addition, outside the system, the legal entity that owns this system will sign information security transmission agreements with external partners, stipulating their respective information security obligations, ensuring that partners have sound information management systems, and ensuring that neither party discloses sensitive documents.

[0132] This application obtains a preset information type; then, based on a preset log collection strategy, it collects target log data corresponding to the file download request according to the information type; subsequently, it calls a preset log storage system; and finally, it stores the target log data in the log storage system. Based on the above processing flow, this application, by combining the use of a log collection strategy and a log storage system, can achieve complete and accurate logging of file download requests, ensuring the security and intelligence of target log data storage, and meeting the needs of subsequent auditing and tracing through log recording.

[0133] In some optional implementations of this embodiment, after step S208, the electronic device may further perform the following steps:

[0134] Invoke the default log analysis tool.

[0135] In this embodiment, a suitable log analysis tool can be selected or developed that can efficiently process and analyze large amounts of log data.

[0136] Based on the log analysis tool, abnormal behavior detection is performed on the pre-collected log data corresponding to file downloads to obtain the corresponding abnormal behavior detection results.

[0137] In this embodiment, log analysis tools are used to detect abnormal download behaviors in pre-collected log data corresponding to file downloads, such as frequent downloads, downloads outside of working hours, and access from unusual IP addresses, and corresponding abnormal behavior detection results are generated. The abnormal behavior detection results include whether abnormal behavior exists or not.

[0138] Content analysis is performed on the abnormal behavior detection results to determine whether there is any suspicious behavior in the log data.

[0139] In this embodiment, by performing content analysis on the abnormal behavior detection results, if the detected abnormal behavior content indicates the presence of abnormal behavior, then the log data is determined to contain suspicious behavior. Conversely, if the detected abnormal behavior content indicates the absence of abnormal behavior, then the log data is determined to contain no suspicious behavior.

[0140] If so, the suspicious behavior will be handled accordingly based on the preset anomaly handling strategy.

[0141] In this embodiment, the above-mentioned anomaly handling strategy includes: immediately conducting further investigations into detected suspicious behavior. If an illegal request is confirmed, relevant intranet download permissions or system access interface permissions are revoked through the system management interface to prevent further illegal operations. Specifically, if suspicious behavior is identified in the log data, appropriate processing is performed on the detected suspicious behavior based on the above-mentioned anomaly handling strategy. Furthermore, log analysis reports can be generated periodically to summarize abnormal behavior patterns, processing results, and improvement suggestions, providing decision support for system security management.

[0142] This application utilizes a pre-defined log analysis tool to detect abnormal behavior in pre-collected log data related to file downloads, obtaining corresponding abnormal behavior detection results. Subsequently, content analysis is performed on these abnormal behavior detection results to determine if suspicious behavior exists in the log data. If so, the suspicious behavior is handled according to a pre-defined anomaly handling strategy. Based on this process, this application uses a log analysis tool to detect abnormal behavior in pre-collected log data related to file downloads and performs content analysis on the detected results. If suspicious behavior is detected in the log data, it automatically and intelligently handles the suspicious behavior according to the anomaly handling strategy, thereby enabling timely detection and handling of potential security threats and ensuring the stability and security of system operation.

[0143] In some alternative implementations, the user information obtained is subject to user consent and complies with relevant laws and policies.

[0144] Furthermore, any software tools or components not belonging to our company that appear in the embodiments of this application are merely illustrative examples and do not represent actual use.

[0145] Furthermore, the data query method proposed in this application has the following advantages:

[0146] 1. It meets the information security requirements for viewing and downloading sensitive documents in financial and medical business scenarios without affecting the use of the original documents. In the event of a sensitive document leak, the responsible party can be quickly traced to prevent recurrence. 2. For sensitive documents that need to be stored long-term, a memory copy and signature writing method is used to write the visitor's signature, avoiding tampering with the original file, redundant files, and wasted storage. 3. For external partners, it prevents the risk of impersonation, information eavesdropping, and information tampering, ensuring information security during system interactions. 4. Suspicious requests are detected through log analysis, and further unauthorized requests from partners and internal employees are prevented by revoking interface permissions and internal network download permissions. 5. The interface for downloading sensitive documents has added business field validation. Only business field values ​​known to both parties are used for further identity verification to ensure the compliance of downloaded attachments.

[0147] It should be understood that the sequence number of each step in the above embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

[0148] It should be emphasized that, to further ensure the privacy and security of the aforementioned target files, they can also be stored in a node of a blockchain.

[0149] The blockchain referred to in this application is a novel application model of computer technologies such as distributed data storage, peer-to-peer transmission, consensus mechanisms, and encryption algorithms. Essentially, a blockchain is a decentralized database, a chain of data blocks linked together using cryptographic methods. Each data block contains information about a batch of network transactions, used to verify the validity of the information (anti-counterfeiting) and generate the next block. A blockchain can include an underlying blockchain platform, a platform product service layer, and an application service layer.

[0150] The embodiments of this 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 that knowledge to obtain optimal results.

[0151] Foundational technologies for artificial intelligence generally include sensors, dedicated AI chips, cloud computing, distributed storage, big data processing, operating / interactive systems, and mechatronics. AI software technologies mainly encompass computer vision, robotics, biometrics, speech processing, natural language processing, and machine learning / deep learning.

[0152] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by instructing related hardware through computer-readable instructions. These computer-readable instructions can be stored in a computer-readable storage medium. When the program is executed, it can include the processes of the embodiments of the methods described above. The aforementioned storage medium can be a non-volatile storage medium such as a magnetic disk, optical disk, or read-only memory (ROM), or random access memory (RAM).

[0153] It should be understood that although the steps in the flowcharts of the accompanying figures are shown sequentially as indicated by the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the accompanying figures may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times, and their execution order is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the sub-steps or stages of other steps.

[0154] Further reference Figure 3 As a response to the above Figure 2 To implement the method shown, this application provides an embodiment of a data query device, which is similar to... Figure 2 Corresponding to the method embodiments shown, this device can be specifically applied to various electronic devices.

[0155] like Figure 3 As shown, the data query device 300 described in this embodiment includes: a receiving module 301, a first judgment module 302, a first verification module 303, a second verification module 304, a parsing module 305, a third verification module 306, a first processing module 307, and a first sending module 308. Wherein:

[0156] The receiving module 301 is used to receive a file download request triggered by a user through a target interface; wherein the file download request carries at least a message and service parameters;

[0157] The first judgment module 302 is used to obtain the user role type of the user and determine whether the user role type is an external user;

[0158] The first verification module 303 is used to verify the IP address corresponding to the file download request based on a preset IP whitelist if the user role type is an external user.

[0159] The second verification module 304 is used to perform field verification on the service parameters if the IP address passes the verification.

[0160] The parsing module 305 is used to parse the message to obtain the corresponding parsed data if the business parameters pass the field validation.

[0161] The third verification module 306 is used to verify the parsed data based on a preset message verification strategy;

[0162] The first processing module 307 is used to respond to the file download request if the parsed data passes the verification, to query the corresponding first file, and to encrypt and sign the first file to obtain the corresponding target file.

[0163] The first sending module 308 is used to send the target file to the user.

[0164] In this embodiment, the operations performed by the above modules or units correspond one-to-one with the steps of the data query method in the aforementioned embodiments, and will not be repeated here.

[0165] In some optional implementations of this embodiment, the parsed data includes ciphertext, signature, and encrypted symmetric encryption key; the third verification module 306 includes:

[0166] The first decryption submodule is used to decrypt the encrypted symmetric encryption key to obtain the corresponding original symmetric encryption key.

[0167] The second decryption submodule is used to decrypt the ciphertext based on the original symmetric encryption key;

[0168] The verification submodule is used to verify the signature based on preset signature verification rules if the decryption is successful.

[0169] The first determination submodule is used to determine that the message passes verification if the signature passes verification.

[0170] The second determination submodule is used to determine that the message has failed verification if the signature fails verification.

[0171] In this embodiment, the operations performed by the above modules or units correspond one-to-one with the steps of the data query method in the aforementioned embodiments, and will not be repeated here.

[0172] In some optional implementations of this embodiment, the verification submodule includes:

[0173] The extraction unit is used to extract the user's fingerprint information from a preset security certificate and to verify the fingerprint information;

[0174] The decryption unit is used to decrypt the signature based on a pre-shared public key corresponding to the user to obtain the corresponding original hash value if the fingerprint information passes verification.

[0175] A calculation unit is used to obtain plaintext data obtained by decrypting the ciphertext, and to perform hash calculation on the plaintext data to obtain the corresponding specified hash value;

[0176] A judgment unit is used to determine whether the original hash value is consistent with the specified hash value;

[0177] The determination unit is used to determine that the signature passes the verification if the signature matches, and otherwise determine that the signature fails the verification.

[0178] In this embodiment, the operations performed by the above modules or units correspond one-to-one with the steps of the data query method in the aforementioned embodiments, and will not be repeated here.

[0179] In some optional implementations of this embodiment, the first processing module 307 includes:

[0180] The response submodule is used to respond to the file download request in order to retrieve the corresponding first file;

[0181] The acquisition submodule is used to obtain the target file type of the first file;

[0182] The first determining submodule is used to determine the corresponding target file signature strategy based on the target file type;

[0183] The processing submodule is used to encrypt and sign the first file based on the target file signing strategy to obtain the processed second file.

[0184] The second determining submodule is used to use the second file as the target file.

[0185] In this embodiment, the operations performed by the above modules or units correspond one-to-one with the steps of the data query method in the aforementioned embodiments, and will not be repeated here.

[0186] In some optional implementations of this embodiment, the data query device further includes:

[0187] The verification module is used to obtain the user's identity information and verify the user's identity based on the identity information if the user role type is an internal user.

[0188] The first acquisition module is used to acquire the user's target permissions based on the identity information if the user passes the authentication.

[0189] The second judgment module is used to determine whether the query operation corresponding to the file download request is within the permission range of the target permission;

[0190] The second processing module is used to respond to the file download request if the request is true, to retrieve the corresponding third file, and to encrypt and sign the third file to obtain the corresponding specified file.

[0191] The second sending module is used to send the specified file to the user.

[0192] In this embodiment, the operations performed by the above modules or units correspond one-to-one with the steps of the data query method in the aforementioned embodiments, and will not be repeated here.

[0193] In some optional implementations of this embodiment, the data query device further includes:

[0194] The second acquisition module is used to acquire preset information types;

[0195] The collection module is used to collect target log data corresponding to the file download request based on the information type according to a preset log collection strategy.

[0196] The first calling module is used to call the preset log storage system;

[0197] A storage module is used to store the target log data into the log storage system.

[0198] In this embodiment, the operations performed by the above modules or units correspond one-to-one with the steps of the data query method in the aforementioned embodiments, and will not be repeated here.

[0199] In some optional implementations of this embodiment, the data query device further includes:

[0200] The second calling module is used to call the preset log analysis tools;

[0201] The detection module is used to perform abnormal behavior detection on the pre-collected log data corresponding to file downloads based on the log analysis tool, and obtain the corresponding abnormal behavior detection results.

[0202] The analysis module is used to perform content analysis on the abnormal behavior detection results to determine whether there is suspicious behavior in the log data;

[0203] The third processing module is used to process the suspicious behavior accordingly based on a preset anomaly handling strategy if the situation is as described.

[0204] In this embodiment, the operations performed by the above modules or units correspond one-to-one with the steps of the data query method in the aforementioned embodiments, and will not be repeated here.

[0205] To address the aforementioned technical problems, embodiments of this application also provide a computer device. Please refer to [link / reference needed]. Figure 4 , Figure 4 This is a basic structural block diagram of the computer device in this embodiment.

[0206] The computer device 4 includes a memory 41, a processor 42, and a network interface 43 that are interconnected via a system bus. It should be noted that only the computer device 4 with components 41-43 is shown in the figure; however, it should be understood that it is not required to implement all the shown components, and more or fewer components can be implemented alternatively. Those skilled in the art will understand that the computer device described here is a device capable of automatically performing numerical calculations and / or information processing according to pre-set or stored instructions, and its hardware includes, but is not limited to, microprocessors, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), digital signal processors (DSPs), embedded devices, etc.

[0207] The computer device can be a desktop computer, laptop, handheld computer, or cloud server, etc. The computer device can interact with the user via a keyboard, mouse, remote control, touchpad, or voice control.

[0208] The memory 41 includes at least one type of readable storage medium, including flash memory, hard disk, multimedia card, card-type memory (e.g., SD or DX memory), random access memory (RAM), static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic memory, magnetic disk, optical disk, etc. In some embodiments, the memory 41 may be an internal storage unit of the computer device 4, such as the hard disk or memory of the computer device 4. In other embodiments, the memory 41 may also be an external storage device of the computer device 4, such as a plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, etc., equipped on the computer device 4. Of course, the memory 41 may also include both the internal storage unit and its external storage device of the computer device 4. In this embodiment, the memory 41 is typically used to store the operating system and various application software installed on the computer device 4, such as computer-readable instructions for data query methods. In addition, the memory 41 can also be used to temporarily store various types of data that have been output or will be output.

[0209] In some embodiments, the processor 42 may be a central processing unit (CPU), a controller, a microcontroller, a microprocessor, or other data processing chip. The processor 42 is typically used to control the overall operation of the computer device 4. In this embodiment, the processor 42 is used to execute computer-readable instructions stored in the memory 41 or to process data, for example, to execute computer-readable instructions for the data query method.

[0210] The network interface 43 may include a wireless network interface or a wired network interface, which is typically used to establish communication connections between the computer device 4 and other electronic devices.

[0211] This application also provides another embodiment, namely, providing a computer-readable storage medium storing computer-readable instructions that can be executed by at least one processor to cause the at least one processor to perform the steps of the data query method described above.

[0212] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0213] Obviously, the embodiments described above are only some embodiments of this application, not all embodiments. The accompanying drawings show preferred embodiments of this application, but do not limit the patent scope of this application. This application can be implemented in many different forms; rather, the purpose of providing these embodiments is to provide a more thorough and comprehensive understanding of the disclosure of this application. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art can still modify the technical solutions described in the foregoing specific embodiments, or make equivalent substitutions for some of the technical features. Any equivalent structures made using the content of this application's specification and drawings, directly or indirectly applied to other related technical fields, are similarly within the scope of patent protection of this application.

Claims

1. A data query method, characterized in that, Includes the following steps: Receive a file download request triggered by a user through a target interface; wherein the file download request carries at least a message and business parameters; Obtain the user role type of the user, and determine whether the user role type is an external user; If the user role type is an external user, the IP address corresponding to the file download request is verified based on a preset IP whitelist. If the IP address passes the verification, then the business parameters are validated. If the business parameters pass the field validation, the message is parsed to obtain the corresponding parsed data; The parsed data is verified based on a preset message verification strategy; If the parsed data passes the verification, the file download request is responded to to retrieve the corresponding first file, and the first file is encrypted and signed to obtain the corresponding target file; The target file is sent to the user.

2. The data query method according to claim 1, characterized in that, The parsed data includes ciphertext, a signature, and an encrypted symmetric encryption key; the step of verifying the parsed data based on a preset message verification strategy specifically includes: The encrypted symmetric encryption key is decrypted to obtain the corresponding original symmetric encryption key. Decrypt the ciphertext based on the original symmetric encryption key; If decryption is successful, the signature is verified based on the preset signature verification rules; If the signature passes verification, the message is deemed to have passed verification. If the signature fails verification, the message is determined to have failed verification.

3. The data query method according to claim 2, characterized in that, The step of verifying the signature based on preset signature verification rules specifically includes: Extract the user's fingerprint information from the preset security certificate and verify the fingerprint information; If the fingerprint information is verified, the signature is decrypted based on the pre-shared public key corresponding to the user to obtain the corresponding original hash value; Obtain the plaintext data obtained by decrypting the ciphertext, and perform a hash calculation on the plaintext data to obtain the corresponding specified hash value; Determine whether the original hash value is consistent with the specified hash value; If they match, the signature is deemed to have passed verification; otherwise, the signature is deemed to have failed verification.

4. The data query method according to claim 1, characterized in that, The steps of responding to the file download request to retrieve the corresponding first file, and encrypting and signing the first file to obtain the corresponding target file, specifically include: Respond to the file download request to retrieve the corresponding first file; Obtain the target file type of the first file; Determine the corresponding target file signature strategy based on the target file type; The first file is encrypted and signed based on the target file signing strategy to obtain the processed second file; Use the second file as the target file.

5. The data query method according to claim 1, characterized in that, After the step of determining whether the user role type is an external user, the method further includes: If the user role type is an internal user, then obtain the user's identity information and verify the user's identity based on the identity information; If the user is authenticated, then the user's target permissions are obtained based on the authentication information; Determine whether the query operation corresponding to the file download request is within the scope of the target permissions; If so, respond to the file download request to retrieve the corresponding third file, and encrypt and sign the third file to obtain the corresponding specified file; Send the specified file to the user.

6. The data query method according to claim 1, characterized in that, Following the step of sending the target file to the user, the method further includes: Retrieve preset information types; Based on a preset log collection strategy, target log data corresponding to the file download request is collected according to the information type; Invoke the default log storage system; The target log data is stored in the log storage system.

7. The data query method according to claim 1, characterized in that, Following the step of sending the target file to the user, the method further includes: Invoke the default log analysis tool; Based on the log analysis tool, abnormal behavior detection is performed on the pre-collected log data corresponding to file downloads to obtain the corresponding abnormal behavior detection results; Content analysis is performed on the abnormal behavior detection results to determine whether there is any suspicious behavior in the log data; If so, the suspicious behavior will be handled accordingly based on the preset anomaly handling strategy.

8. A data query device, characterized in that, include: The receiving module is used to receive file download requests triggered by users through the target interface; wherein the file download request carries at least a message and service parameters; The first judgment module is used to obtain the user role type of the user and determine whether the user role type is an external user; The first verification module is used to verify the IP address corresponding to the file download request based on a preset IP whitelist if the user role type is an external user. The second verification module is used to perform field verification on the business parameters if the IP address passes the verification. The parsing module is used to parse the message to obtain the corresponding parsed data if the business parameters pass the field validation. The third verification module is used to verify the parsed data based on a preset message verification strategy. The first processing module is used to respond to the file download request if the parsed data passes the verification, to query the corresponding first file, and to encrypt and sign the first file to obtain the corresponding target file. The first sending module is used to send the target file to the user.

9. A computer device, characterized in that, The system includes a memory and a processor, wherein the memory stores computer-readable instructions, and the processor executes the computer-readable instructions to implement the steps of the data query method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-readable instructions, which, when executed by a processor, implement the steps of the data query method as described in any one of claims 1 to 7.

Images