A gold transaction data security management method and system

Abstract

The present invention provides a gold transaction data security management method and system, which relates to the field of data processing technology. The method comprises: receiving a data operation request sent by a requester, extracting request authentication data from the data operation request according to the request type to which the data operation request belongs, and performing identity authentication and authority authentication on the requester based on the request authentication data; in response to the identity authentication and authority authentication of the requester being passed, executing the operation instruction corresponding to the data operation request. The present invention can reduce the risk of gold transaction data being leaked, provide security protection for the information involved by both parties to the transaction, and improve the security management level of the enterprise's gold transaction data.

Description

Technical Field

[0001] The present invention relates to the technical field of data processing, and in particular to a gold transaction data security management method and system. Background Art

[0002] The security management of gold trading data is very important for both enterprises and individual investors in the gold industry. For enterprises, ensuring the security of gold trading data can prevent the leakage of sensitive information, ensure the competitiveness of enterprises, and maintain the trust between enterprises and users. For individual investors, the security management of gold trading data helps protect investors' investment privacy and financial privacy. Improving the level of security management of gold trading data is an issue that needs to be urgently addressed. Summary of the invention

[0003] In view of the above problems, the present invention provides a gold transaction data security management method and system, aiming to improve the security management level of gold transaction data and provide protection for the privacy of enterprises and individuals.

[0004] A first aspect of an embodiment of the present invention discloses a gold transaction data security management method, comprising:

[0005] Receive a data operation request from a requester, extract request authentication data from the data operation request according to the request type to which the data operation request belongs, and perform identity authentication and authority authentication on the requester based on the request authentication data;

[0006] If the request type of the data operation request is data writing, store information is extracted from the transaction database, and the identity of the requester is authenticated based on the request authentication data;

[0007] In response to the identity authentication of the requester being passed, determining the data writing authority of the requester based on the store information, and authenticating the authority of the requester based on the data writing authority of the requester and the request authentication data;

[0008] If the request type of the data operation request is data query, the gold transaction information is extracted from the transaction database, and the identity of the requester is authenticated based on the request authentication data;

[0009] In response to the identity authentication of the requester being passed, determining the data query authority of the requester based on the transaction data, and authenticating the authority of the requester based on the data query authority of the requester and the request authentication data;

[0010] In response to the identity authentication and authority authentication of the requesting party being passed, the operation instruction corresponding to the data operation request is executed.

[0011] Furthermore, in the process of performing identity authentication and authority authentication on the requester based on the request authentication data, if the request type to which the data operation request belongs is data writing, it also includes:

[0012] Extract the store identification number from the authentication request data, match the store identification number with the store information, and if the match is successful, match the identity identification number in the authentication request data with multiple user identities corresponding to the first target store information that successfully matches, and if there is a user identity that matches the identity identification number of the requester, it means that the identity authentication of the requester is successful;

[0013] In response to the identity authentication of the requester being passed, determining the write permission of the requester based on the target store information, including determining the write permission store of the requester;

[0014] The written store information corresponding to the data operation request is matched with the write permission store. If the match is successful, it means that the permission authentication of the requester is passed.

[0015] Furthermore, in the process of performing identity authentication and authority authentication on the requester based on the request authentication data, if the request type to which the data operation request belongs is data query, it also includes:

[0016] extracting a store identification number associated with the requesting party from the request authentication data, extracting second target store information from the store information based on the store identification number associated with the requesting party, and determining target transaction information associated with the second target store information;

[0017] Authenticate the requester based on the requester's identity type, second target store information, and target transaction information;

[0018] In response to the identity authentication of the requester being passed, determining the query authority of the requester according to the identity type of the requester, including the query authority store of the requester and at least one query authority object belonging to the query authority store;

[0019] Match the queried store information corresponding to the data operation request with the query authority store, and match the queried object information corresponding to the data operation request with at least one query authority object belonging to the query authority store. If all matches are successful, it means that the authority authentication of the requester is passed.

[0020] Furthermore, in the process of authenticating the identity of the requester according to the identity type of the requester, the second target store information and the target transaction information, it also includes:

[0021] If the identity type of the requester is a common user, the transaction sequence number provided by the requester is extracted from the request authentication data and matched with the target transaction information;

[0022] If the match is successful, the target identity information in the target transaction information is determined. If the identity identification number of the requesting party matches the target identity information successfully, it means that the identity authentication of the requesting party is successful;

[0023] If the identity type of the requesting party is an administrative user, matching the identity identification number in the request authentication data with multiple user identities corresponding to the second target store information, and if there is a user identity matching the identity identification number of the requesting party, querying the historical query record of the user identity matching the identity identification number of the requesting party;

[0024] If there is a historical query record, it means that the identity authentication of the requester is passed. Otherwise, the requester is subjected to biometric authentication. If the biometric authentication of the requester is passed, it means that the identity authentication of the requester is passed.

[0025] Further, determining the query authority of the requester according to the identity type of the requester also includes:

[0026] If the identity type of the requesting party is a common user, determining at least one query permission object in at least one query permission store of the requesting party;

[0027] If the identity type of the requester is an administrative user, at least one query permission store of the requester and all query permission objects belonging to the query permission store are determined.

[0028] Furthermore, performing biometric authentication on the requesting party includes performing biometric authentication on the requesting party using at least one of fingerprint feature authentication, face feature authentication, and iris feature authentication.

[0029] A second aspect of an embodiment of the present invention discloses a gold transaction data security management system, which is applied to any of the gold transaction data security management methods described above, including:

[0030] A request response module, used to receive a data operation request from a requester and identify the request type to which the data operation request belongs;

[0031] A data extraction module, used to extract request authentication data from a data operation request according to the request type to which the data operation request belongs;

[0032] A first identity authentication module, used for authenticating the requester based on the request authentication data and the transaction database when the request type to which the data operation request belongs is data writing;

[0033] A first authority authentication module, used for performing authority authentication on the requester based on the request authentication data and the transaction database when the request type to which the data operation request belongs is data writing;

[0034] A second identity authentication module, used for authenticating the requester based on the request authentication data and the transaction database when the request type to which the data operation request belongs is data query;

[0035] A second authority authentication module is used to authenticate the requester's authority based on the request authentication data and the transaction database when the request type to which the data operation request belongs is data query;

[0036] The request execution module is used to execute the operation instructions corresponding to the data operation request after the identity authentication and authority authentication of the requester are passed.

[0037] The present invention has the following advantages:

[0038] The present invention extracts request authentication data from a data operation request issued by a requester, performs dual authentication of the identity and authority of the requester based on the request authentication data, executes relevant operation instructions after the dual authentication is passed, reduces the risk of gold transaction data being leaked, provides security for the information involved by both parties to the transaction, and improves the security management level of the enterprise's gold transaction data. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on the structures shown in these drawings without paying creative work.

[0040] Figure 1 The figure is a flow chart of a gold transaction data security management method in an embodiment of the present invention.

[0041] Figure 2 The figure is a schematic diagram of the structure of a gold transaction data security management system in an embodiment of the present invention. DETAILED DESCRIPTION

[0042] In order to make the purpose, technical solution and advantages of the present invention more clearly understood, some embodiments of the present invention are further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not used to limit the present invention.

[0043] See also Figure 1 , a gold transaction data security management method provided in an embodiment of the present invention specifically includes:

[0044] S1. Receive a data operation request from a requesting party;

[0045] Among them, the data operation request can specifically be a data write request, that is, the requester is ready to write the gold transaction data into the transaction database for data storage, and the requester can be a manager in multiple stores set up by an enterprise in the gold trading industry. The data operation request can specifically be a data query request, that is, the requester is ready to query part of the gold transaction data through the transaction database, wherein the requester can be a manager in the store or an individual user, such as an individual investor who conducts gold transactions with the enterprise. The requester is not specifically limited in this embodiment.

[0046] S2. extracting request authentication data from the data operation request according to the request type to which the data operation request belongs;

[0047] Among them, since the request types to which the data operation request belongs are different, different request types contain different characteristic information, so different request authentication data can be extracted. For example, if the data operation request is a data write request, the data operation request at least includes the requester's personal identity information, the store information to which it belongs, and the transaction object information; if the data operation request is a data query request, considering that the requester's identity may be multiple, the data operation request may include the requester's personal information, the requester's store information, and the store information involved in the transaction.

[0048] S3, performing identity authentication and authority authentication on the requesting party based on the request authentication data;

[0049] Among them, the significance of identity authentication of the requesting party is to verify whether the requesting party meets the basic request conditions. Generally speaking, the two parties engaged in gold transactions, namely the store and the investor, can query the relevant gold transaction data. After the identity authentication of the requesting party is passed, the requesting party is also authenticated for authority, that is, to determine whether the requesting party has the ability to execute the operation instructions corresponding to the issued data operation request.

[0050] S4. In response to the identity authentication and authority authentication of the requesting party being passed, the operation instruction corresponding to the data operation request is executed.

[0051] A gold transaction data security management method provided in an embodiment of the present invention extracts request authentication data from a data operation request issued by a requesting party, performs identity and authority dual authentication on the requesting party based on the request authentication data, and executes relevant operation instructions after the dual authentication is passed, thereby reducing the risk of gold transaction data being leaked, providing security protection for the information involved by both parties to the transaction, and improving the security management level of the enterprise's gold transaction data.

[0052] As a possible implementation scheme in this embodiment, for step S3, in the process of identity authentication and authority authentication of the requesting party based on the request authentication data, if the request type to which the data operation request belongs is data writing, the following authentication steps are included:

[0053] S311, extracting store information from the transaction database, and authenticating the requester based on the request authentication data;

[0054] Among them, store information is used to refer to the information related to multiple stores established by enterprises in the gold trading industry, such as store name, store number, store address, store management personnel and other information.

[0055] Authentication of the requesting party includes:

[0056] Extracting a store identification number from the authentication request data, matching the store identification number with the store information, and if the match is successful, matching the identity identification number in the authentication request data with multiple user identities corresponding to the first target store information that successfully matched;

[0057] Specifically, the store identification number indicates a code that is used to uniquely represent a certain store, such as the store number set by the enterprise for each store based on actual conditions. If there is first target store information that matches the store identification number, the identity identification number of the requester is matched with the multiple user identities recorded in the first target store information, wherein the multiple user identities recorded in the first target store information can specifically be relevant information of store members with data writing permissions pre-established by the enterprise. If there is a user identity that matches the identity identification number of the requester, it indicates that the identity authentication of the requester is passed.

[0058] S312, in response to the identity authentication of the requester being passed, determining the data writing authority of the requester based on the store information, and performing authority authentication on the requester based on the data writing authority of the requester and the request authentication data;

[0059] Among them, determining the data writing authority of the requester is specifically to determine the write-authorized store of the requester. It is worth noting that the enterprise can set one or more managers for each store in combination with the actual situation of each store. The managers can write the gold transaction data generated in the store into the enterprise's transaction database after authentication. After determining the write-authorized store of the requester, the written store information corresponding to the data operation request is matched with the write-authorized store. Among them, the written store information corresponding to the data operation request is specifically the store information to which the gold transaction data that the requester is going to write belongs. If the match is successful, it means that the authority authentication of the requester is passed.

[0060] As a possible implementation scheme in this embodiment, for step S3, in the process of identity authentication and authority authentication of the requesting party based on the request authentication data, if the request type to which the data operation request belongs is data query, the following authentication steps are included:

[0061] S321, extracting gold transaction information from the transaction database, and performing identity authentication on the requesting party based on the request authentication data;

[0062] The transaction database stores gold transaction information of multiple stores. In this embodiment, this step specifically includes the following contents:

[0063] extracting a store identification number associated with the requesting party from the request authentication data, extracting second target store information from the store information based on the store identification number associated with the requesting party, and determining target transaction information associated with the second target store information;

[0064] Specifically, taking into account the change in the identity of the requester, if the requester is an individual investor, the store associated with the requester is specifically the store that conducts gold transactions; if the requester is a manager in a store, the store associated with the requester is the store to which the manager belongs, thereby determining the store identification number corresponding to the store associated with the requester, and then extracting the gold transaction information corresponding to the requester in the transaction database based on the determined store identification number and recording it as target transaction information.

[0065] The requesting party is authenticated according to the identity type of the requesting party, the second target store information and the target transaction information.

[0066] S322, in response to the identity authentication of the requesting party being passed, determining the data query authority of the requesting party based on the transaction data, and performing authority authentication on the requesting party based on the data query authority of the requesting party and the request authentication data;

[0067] The data query authority of the requesting party is determined to be specifically the query authority store of the requesting party and at least one query authority object belonging to the query authority store;

[0068] In this step, considering that the identity types of the requesting party are different, the query authority of the requesting party is determined based on the identity type of the requesting party, specifically including:

[0069] If the identity type of the requesting party is a common user, determining at least one query permission object in at least one query permission store of the requesting party;

[0070] If the identity type of the requester is an administrative user, at least one query permission store of the requester and all query permission objects belonging to the query permission store are determined.

[0071] In the process of authenticating the requester's authority, the queried store information corresponding to the data operation request is matched with the query authority store, and the queried object information corresponding to the data operation request is matched with at least one query authority object belonging to the query authority store;

[0072] Specifically, the queried store information corresponding to the data operation request is the relevant information of the store to which the gold transaction data that the requester wants to query belongs, and the queried object information corresponding to the data operation request is the relevant information related to the order of the gold transaction data that the requester wants to query. Exemplarily, the transaction database records the gold transaction data in each store, wherein the gold transaction data in each store can be divided into multiple transaction orders, each transaction order is regarded as an authority query object, and if both are matched successfully, it means that the authority authentication of the requester is passed.

[0073] As a possible implementation scheme of this embodiment, in the process of authenticating the identity of the requester according to the identity type of the requester, the second target store information and the target transaction information, the following is also included:

[0074] If the identity type of the requester is a common user, the transaction sequence number provided by the requester is extracted from the request authentication data and matched with the target transaction information;

[0075] Specifically, the transaction sequence number is used to uniquely represent one of the transaction orders. Each order in the target transaction information corresponds to a transaction sequence number, and the transaction sequence number provided by the requester is matched with multiple orders in the target transaction information.

[0076] If the match is successful, the target identity information in the target transaction information is determined. If the identity identification number of the requesting party matches the target identity information successfully, it means that the identity authentication of the requesting party is successful;

[0077] Specifically, if there is an order in the target transaction information that matches the transaction serial number provided by the requester, the identity identification number of the requester is matched with the target identity information involved in the order to perform further identity verification on the requester.

[0078] If the identity type of the requesting party is an administrative user, matching the identity identification number in the request authentication data with multiple user identities corresponding to the second target store information;

[0079] Specifically, for the management user, during the identity authentication process, the identity identification number of the requesting party is directly matched with multiple user identities in the second target store information;

[0080] If there is a user identity that matches the identity identification number of the requester, query the historical query record of the user identity that matches the identity identification number of the requester; if there is a historical query record, it means that the identity authentication of the requester is passed;

[0081] Specifically, for multiple management users, if it is determined that the requester is one of the management users in the second target store information, the requester is further verified by obtaining the historical query records of the management user. If there is a historical query record, it means that the requester has performed relevant data query operations, and the identity authentication of the requester is directly passed. Otherwise, the requester is subjected to biometric authentication. In response to the biometric authentication of the requester being passed, it means that the identity authentication of the requester is passed.

[0082] The biometric authentication of the requesting party may be performed by at least one of fingerprint feature authentication, face feature authentication, and iris feature authentication. In this embodiment, the biometric authentication of the requesting party is performed by face feature authentication.

[0083] See also Figure 2 Based on a gold transaction data security management method provided in an embodiment of the present invention, an embodiment of the present invention further provides a gold transaction data security management system, which specifically includes:

[0084] A request response module, used to receive a data operation request from a requester and identify the request type to which the data operation request belongs;

[0085] A data extraction module, used to extract request authentication data from a data operation request according to the request type to which the data operation request belongs;

[0086] A first identity authentication module, used for authenticating the requester based on the request authentication data and the transaction database when the request type to which the data operation request belongs is data writing;

[0087] Specifically, store information is extracted from the transaction database, and the identity of the requester is authenticated based on the request authentication data;

[0088] A first authority authentication module, used for performing authority authentication on the requester based on the request authentication data and the transaction database when the request type to which the data operation request belongs is data writing;

[0089] Specifically, in response to the identity authentication of the requester being passed, determining the data writing authority of the requester based on the store information, and performing authority authentication on the requester based on the data writing authority of the requester and the request authentication data;

[0090] A second identity authentication module, used for authenticating the requester based on the request authentication data and the transaction database when the request type to which the data operation request belongs is data query;

[0091] Specifically, gold transaction information is extracted from the transaction database, and the identity of the requesting party is authenticated based on the request authentication data;

[0092] A second authority authentication module is used to authenticate the requester's authority based on the request authentication data and the transaction database when the request type to which the data operation request belongs is data query;

[0093] Specifically, in response to the identity authentication of the requester being passed, determining the data query authority of the requester based on the transaction data, and performing authority authentication on the requester based on the data query authority of the requester and the request authentication data;

[0094] The request execution module is used to execute the operation instruction corresponding to the data operation request after the identity authentication and authority authentication of the requester are passed, such as executing the data writing instruction or data query instruction corresponding to the data operation request.

[0095] It should be understood that those skilled in the art can make improvements or changes based on the above description, and all such improvements and changes should fall within the scope of protection of the appended claims of the present invention. Parts not described in detail in this specification belong to the prior art known to those skilled in the art.

Claims

1. A gold transaction data security management method, characterized in that: include: Receive a data operation request from a requester, extract request authentication data from the data operation request according to the request type to which the data operation request belongs, and perform identity authentication and authority authentication on the requester based on the request authentication data; If the request type of the data operation request is data writing, store information is extracted from the transaction database, and the identity of the requester is authenticated based on the request authentication data; In response to the identity authentication of the requester being passed, determining the data writing authority of the requester based on the store information, and authenticating the authority of the requester based on the data writing authority of the requester and the request authentication data; If the request type of the data operation request is data query, the gold transaction information is extracted from the transaction database, and the identity of the requester is authenticated based on the request authentication data; In response to the identity authentication of the requester being passed, determining the data query authority of the requester based on the transaction data, and authenticating the authority of the requester based on the data query authority of the requester and the request authentication data; In response to the identity authentication and authority authentication of the requesting party being passed, executing the operation instruction corresponding to the data operation request; In the process of identity authentication and authority authentication of the requester based on the request authentication data, if the request type of the data operation request is data writing, it also includes: Extract the store identification number from the authentication request data, match the store identification number with the store information, and if the match is successful, match the identity identification number in the authentication request data with multiple user identities corresponding to the first target store information that successfully matches, and if there is a user identity that matches the identity identification number of the requester, it means that the identity authentication of the requester is successful; In response to the identity authentication of the requester being passed, determining the write permission of the requester based on the target store information, including determining the write permission store of the requester; Match the written store information corresponding to the data operation request with the store with write permission. If the match is successful, it means that the requester's permission authentication is passed; In the process of identity authentication and authority authentication of the requester based on the request authentication data, if the request type of the data operation request is data query, it also includes: extracting a store identification number associated with the requesting party from the request authentication data, extracting second target store information from the store information based on the store identification number associated with the requesting party, and determining target transaction information associated with the second target store information; Authenticate the requester based on the requester's identity type, the second target store information, and the target transaction information; In response to the identity authentication of the requester being passed, determining the query authority of the requester according to the identity type of the requester, including the query authority store of the requester and at least one query authority object belonging to the query authority store; Match the queried store information corresponding to the data operation request with the query permission store, and match the queried object information corresponding to the data operation request with at least one query permission object belonging to the query permission store. If both are matched successfully, it means that the requester's permission authentication is passed; The process of authenticating the identity of the requester according to the identity type of the requester, the second target store information and the target transaction information also includes: If the identity type of the requester is a common user, the transaction sequence number provided by the requester is extracted from the request authentication data and matched with the target transaction information; If the match is successful, the target identity information in the target transaction information is determined. If the identity identification number of the requesting party matches the target identity information successfully, it means that the identity authentication of the requesting party is successful; If the identity type of the requesting party is an administrative user, matching the identity identification number in the request authentication data with multiple user identities corresponding to the second target store information, and if there is a user identity matching the identity identification number of the requesting party, querying the historical query record of the user identity matching the identity identification number of the requesting party; If there is a historical query record, it means that the identity authentication of the requester is passed. Otherwise, the requester is subjected to biometric authentication. If the biometric authentication of the requester is passed, it means that the identity authentication of the requester is passed. The query rights of the requester are determined based on the identity type of the requester, and also include: If the identity type of the requesting party is a common user, determining at least one query permission object in at least one query permission store of the requesting party; If the identity type of the requester is an administrative user, determining at least one query permission store of the requester and all query permission objects belonging to the query permission store; Performing biometric authentication on the requesting party includes performing biometric authentication on the requesting party using at least one of fingerprint feature authentication, face feature authentication, and iris feature authentication.

2. A gold transaction data security management system, characterized in that: The gold transaction data security management system is applied to the gold transaction data security management method described in claim 1, comprising: A request response module, used to receive a data operation request from a requester and identify the request type to which the data operation request belongs; A data extraction module, used to extract request authentication data from a data operation request according to the request type to which the data operation request belongs; A first identity authentication module, used for authenticating the requester based on the request authentication data and the transaction database when the request type to which the data operation request belongs is data writing; A first authority authentication module, used for, when the request type to which the data operation request belongs is data writing, performing authority authentication on the requester based on the request authentication data and the transaction database; A second identity authentication module, used for authenticating the requester based on the request authentication data and the transaction database when the request type to which the data operation request belongs is data query; A second authority authentication module is used to authenticate the requester's authority based on the request authentication data and the transaction database when the request type to which the data operation request belongs is data query; The request execution module is used to execute the operation instructions corresponding to the data operation request after the identity authentication and authority authentication of the requester are passed.

Images