Risk prevention and control method, device and system

Abstract

The invention provides a risk prevention and control method, device and system, relates to the technical field of information security, and can be applied to the technical field of finance or other technical fields. The risk prevention and control method comprises the following steps: determining first risk data according to real-name number allocation information of a mobile phone number; determining second risk data according to the media access control address of each application; determining third risk data according to the salary transaction information; determining fourth risk data according to the mobile phone binding information; and determining comprehensive risk data according to the first risk data, the second risk data, the third risk data and the fourth risk data, and sending risk information to a bank server according to the comprehensive risk data. According to the invention, information desensitization measures can be taken actively, so that the risk of information leakage is further avoided.

Description

Technical Field

[0001] The present invention relates to the field of information security technology, and in particular to a risk prevention and control method, device and system. Background Art

[0002] At present, users of corporate banks mainly adopt a two-level method of submitter (handler) plus authorized (managed) person, where the submitter (handler) is generally a human resources / financial staff, and the authorized (managed) person may be the company's financial director / human resources director, or even the company's general manager / legal person, etc., depending on the size of the company. The two roles are generally physical media U shields used on the corporate bank side, which are in the hands of the actual users. It can also be seen from the users of the above two roles that the role of the submitter (handler) is less unique than that of the authorized (managed) person, and the user often needs to be replaced due to reasons such as personnel resignation and job adjustment. Although the actual user of the U shield has been replaced, the previous user's mobile phone number bound to the corporate bank to receive business-related information (such as transaction message push, collection reminder, etc.) is difficult for the new user and authorized (managed) person to know, especially the customized SMS information for the enterprise.

[0003] Even if the customer obtains the information that may be lost, at this time, the corporate customer can only go to the bank business department or contact the account manager to check each business separately, and there may still be omissions. This is because when customizing, the business is handled through different channels through the original mobile phone number, and the information source storage channel is not unique, resulting in the possibility that even if the mobile phone number information bound to a business is modified, other businesses may still be bound to the expired mobile phone number.

[0004] At present, the business-related information bound to the submitter's mobile phone number is mainly submitted through the "Corporate Banking Client" and then sent by the "Corporate Banking Server" to the corresponding business management systems for storage. When the corresponding business transaction occurs, the "host" will first call the corresponding business system to query the mobile phone number corresponding to the transaction, and then send the mobile phone number plus the SMS template to Kafka for pre-processing of message push, and finally Kafka will send it to the operator, and the operator will send the information to the customer. Summary of the invention

[0005] The main purpose of the embodiments of the present invention is to provide a risk prevention and control method, device and system to actively take information desensitization measures, thereby further avoiding the risk of information leakage after the handler is replaced.

[0006] In order to achieve the above object, an embodiment of the present invention provides a risk prevention and control method, including:

[0007] Determine the first risk data based on the real-name release information of the mobile phone number;

[0008] determining second risk data according to the media access control address of each application;

[0009] Determine third-party risk data based on wage transaction information;

[0010] Determine the fourth risk data based on the mobile phone binding information;

[0011] Comprehensive risk data is determined according to the first risk data, the second risk data, the third risk data and the fourth risk data, and risk information is sent to a bank service end according to the comprehensive risk data.

[0012] In one embodiment, the mobile phone number real-name release information includes the number of days for release and real-name information;

[0013] The first risk data determined based on the real-name release information of mobile phone numbers includes:

[0014] Determine the number release information according to the number of days for number release;

[0015] The first risk data is determined according to the number release information and the real-name information.

[0016] In one embodiment, determining the second risk data according to the media access control address of each application includes:

[0017] The second risk data is determined according to the number of media access control addresses of each application, login data of each application, and the number of applications.

[0018] In one embodiment, determining the second risk data according to the number of media access control addresses of each application, login data of each application, and the number of applications includes:

[0019] Determining address registration parameters of each application according to the number of media access control addresses of each application and the registration data of each application;

[0020] The second risk data is determined according to the address login parameters of each application and the number of applications.

[0021] In one embodiment, the salary transaction information includes a salary transaction record and a name of a paying company;

[0022] The third risk data determined based on salary transaction information includes:

[0023] When there is no salary transaction record, determining that the third risk data is the first identification data;

[0024] When the salary transaction record exists and the name of the paying company changes, the third risk data is determined to be the second identification data.

[0025] In one embodiment, determining the third risk data according to the salary transaction information further includes:

[0026] When the wage transaction record does not exist and the name of the paying company has not changed, obtaining the certificate data of the paying company and the certificate data of the company corresponding to the handler;

[0027] The third risk data is determined based on a comparison result between the payment company's certificate data and the certificate data of the enterprise corresponding to the handler.

[0028] In one embodiment, determining the third risk data according to the salary transaction information further includes:

[0029] When the certificate data of the payment company and the certificate data of the enterprise corresponding to the handler are the same, determining the linkage relationship between the payment company and the enterprise corresponding to the handler;

[0030] The third risk data is determined according to the attachment relationship.

[0031] The embodiment of the present invention further provides a risk prevention and control device, including:

[0032] A first risk data determination module, used to determine first risk data according to the real-name release information of the mobile phone number;

[0033] A second risk data determination module, configured to determine second risk data according to the media access control address of each application;

[0034] A third risk data determination module, used to determine third risk data according to the salary transaction information;

[0035] A fourth risk data determination module, used to determine fourth risk data according to mobile phone binding information;

[0036] A comprehensive risk data determination module is used to determine comprehensive risk data based on the first risk data, the second risk data, the third risk data and the fourth risk data, and send risk information to a bank service end based on the comprehensive risk data.

[0037] In one embodiment, the mobile phone number real-name release information includes the number of days for release and real-name information;

[0038] The first risk data determination module includes:

[0039] A number release information unit, used to determine the number release information according to the number release days;

[0040] The first risk data unit is used to determine the first risk data according to the number release information and the real-name information.

[0041] In one embodiment, the second risk data determination module is specifically used to:

[0042] The second risk data is determined according to the number of media access control addresses of each application, login data of each application, and the number of applications.

[0043] In one embodiment, the second risk data determination module includes:

[0044] An address registration parameter unit, used to determine the address registration parameter of each application according to the number of media access control addresses of each application and the registration data of each application;

[0045] The second risk data unit is used to determine the second risk data according to the address login parameters of each application and the number of applications.

[0046] In one embodiment, the salary transaction information includes a salary transaction record and a name of a paying company;

[0047] The third risk data determination module includes:

[0048] A first identification data unit, used to determine that the third risk data is the first identification data when there is no salary transaction record;

[0049] The second identification data unit is used to determine that the third risk data is the second identification data when the salary transaction record exists and the name of the paying company has changed.

[0050] In one embodiment, the third risk data determination module further includes:

[0051] The certificate data unit is used to obtain the certificate data of the paying company and the certificate data of the company corresponding to the handler when there is no salary transaction record and the name of the paying company has not changed;

[0052] The certificate risk unit is used to determine the third risk data according to the comparison result of the certificate data of the payment company and the certificate data of the enterprise corresponding to the handler.

[0053] In one embodiment, the third risk data determination module further includes:

[0054] A linkage relationship unit, used for determining the linkage relationship between the payment company and the enterprise corresponding to the handler when the certificate data of the payment company and the certificate data of the enterprise corresponding to the handler are the same;

[0055] The attachment risk unit is used to determine the third risk data according to the attachment relationship.

[0056] An embodiment of the present invention also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and running on the processor, and the steps of the risk prevention and control method are implemented when the processor executes the computer program.

[0057] An embodiment of the present invention further provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the steps of the risk prevention and control method are implemented.

[0058] An embodiment of the present invention further provides a computer program product, including a computer program / instruction, which implements the steps of the risk prevention and control method when the computer program / instruction is executed by a processor.

[0059] The embodiment of the present invention further provides a risk prevention and control system, including:

[0060] Risk prevention and control devices as described above;

[0061] The client is used to send the mobile phone number to the server;

[0062] The server is used to send the mobile phone number to the risk prevention and control device and push the risk information from the risk prevention and control device to the customer.

[0063] The risk prevention and control method, device and system of the embodiments of the present invention determine the first risk data according to the real-name release information of the mobile phone number, determine the second risk data according to the media access control address of each application, determine the third risk data according to the salary transaction information, and determine the fourth risk data according to the mobile phone binding information to send the risk information to the bank service end. Information desensitization measures can be actively taken to further avoid the risk of information leakage. BRIEF DESCRIPTION OF THE DRAWINGS

[0064] 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 description of the embodiments 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 these drawings without paying creative work.

[0065] Figure 1 is a flow chart of a risk prevention and control method in an embodiment of the present invention;

[0066] Figure 2 is a flow chart of a risk prevention and control method in another embodiment of the present invention;

[0067] Figure 3 is a flow chart of writing data in an embodiment of the present invention;

[0068] Figure 4 is a flow chart of S101 in an embodiment of the present invention;

[0069] Figure 5 is a flow chart of S102 in an embodiment of the present invention;

[0070] Figure 6 is a flow chart of S103 in an embodiment of the present invention;

[0071] Figure 7 is a flow chart of determining third risk data in an embodiment of the present invention;

[0072] Figure 8 is a flow chart of determining third risk data in another embodiment of the present invention;

[0073] Fig. 9 is a structural block diagram of a risk prevention and control device in an embodiment of the present invention;

[0074] Fig.10 A schematic block diagram of a system structure of an electronic device 9600 according to an embodiment of the present application;

[0075] Fig.11 Schematic diagram of a risk prevention and control system in an embodiment of the present invention. DETAILED DESCRIPTION

[0076] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0077] Those skilled in the art will appreciate that the embodiments of the present invention may be implemented as a system, device, apparatus, method or computer program product. Therefore, the present disclosure may be specifically implemented in the following forms, namely: complete hardware, complete software (including firmware, resident software, microcode, etc.), or a combination of hardware and software.

[0078] The acquisition, storage, use, and processing of data in the technical solution of the present invention are in compliance with the relevant provisions of national laws and regulations. The user information in the embodiments of this application is obtained through legal and compliant channels, and the acquisition, storage, use, and processing of user information are authorized and agreed by the customer.

[0079] In view of the risk of information leakage in the prior art, the embodiments of the present invention provide a risk prevention and control method, device and system, which adds a handler information risk prediction device to the message sending business process, actively intervenes in the SMS sending process through the risk calculation results, automatically analyzes and learns that there may be changes in the submitter (handler), informs the authorizer of the possible risks in advance, and can take active information desensitization measures, thereby further avoiding the risk of information leakage after the submitter (handler) is replaced, and improving the timeliness and flexibility of risk prevention and control. The present invention involves a total of seven modules: corporate bank client, corporate bank service end, handler information risk prediction device, communication operator mobile phone number real-name interface, personal bank service end, various business management systems, and host. The present invention is described in detail below in conjunction with the accompanying drawings.

[0080] Figure 1 It is a flow chart of the risk prevention and control method in an embodiment of the present invention. Figure 2 FIG. 1 is a flow chart of a risk prevention and control method in another embodiment of the present invention. Figure 1-Figure 2 As shown, risk prevention and control methods include:

[0081] S101: Determine first risk data based on the real-name release information of the mobile phone number.

[0082] Figure 3 1 is a flowchart of writing data in an embodiment of the present invention. Figure 3 As shown, before executing S101, the process further includes:

[0083] 1. When the submitter (handler) A handles business X through the [Corporate Banking Client] and binds the mobile phone number 136XXXXXXXXX to receive the message, the [Corporate Banking Client] collects the operator number, corporate group number, mobile phone number and other information of the corresponding business and transmits it to the [Corporate Banking Server].

[0084] 2. The [corporate banking service end] sends the operator number, corporate group number, mobile phone number, business number, transaction type (the information to be sent is account active reminder, non-account active reminder, marketing push, etc.) and other information to the [handler information risk prediction device].

[0085] 3. [The risk prediction device for information of the person handling the transaction] stores information such as the operator number, corporate group number, mobile phone number, business number, transaction type (the information to be sent is an active account reminder, a non-active account reminder, marketing push, etc.).

[0086] 4. Repeat steps 1-3 for other businesses. Every time a transaction is generated, a new storage record for the mobile phone number will be added in the [Business Agent Information Risk Prediction Device] to record the business type that the customer has bound.

[0087] When the [Corporate Banking Service] monitors at the end of the day that the [Corporate Banking Client] submits (handlers) a change in the commonly used device for U-shield login or the device MAC address, the [Corporate Banking Service] retrieves the customer behavior data of the customer in the [Corporate Banking Service] through the operator number and corporate group number, and conducts behavioral analysis on the main transaction behaviors before and after the terminal is replaced. If the usage behavior of the main functional processes of customers of more than X businesses changes by more than 20%, the monitoring process is triggered and the situation is sent to the [Handler Information Risk Prediction Device].

[0088] For example, the changes in the use of the main functional processes of customers here mainly refer to the data of process behaviors such as App login, transfer and remittance, account management, and statement query. Taking transfer and remittance as an example, the transfer and remittance behavior process of corporate mobile banking includes quick transfer in the card area on the homepage, transfer in the payee list, quick transfer in the latest remittance, quick transfer in account management, quick transfer in corporate business card, etc. Among them, quick transfer in the card area, quick transfer in the payee list, and quick transfer in the latest remittance account for more than 93% of the total transfer and remittance volume. What is verified here is the number of times and proportion of customers entering transfer and remittance through each entrance. If the original handler’s previous main transfer and remittance entrance was the latest remittance and the percentage of different personal operation entrances was 98% (98 / 100), the number of times the new handler transferred through the latest remittance accounted for 57% (34 / 59) of different personal operation entrances, and the difference between the new handler and the old handler in the same entrance for transfer and remittance was 41%, which was greater than the general behavior change value of 20%, which was considered to be a possible change in the handler.

[0089] [Information risk prediction device for handlers] queries the corresponding mobile phone number information under the submitter (handler) U shield operator number according to the number, obtains the mobile phone number, and calls the following system to obtain the following information:

[0090] 1. Query the mobile phone number through the operator's real-name verification interface to check whether the mobile phone number is real-name. If it is real-name, check whether there has been a second number change within a certain period of time, and return the result.

[0091] 2. Use the mobile phone number to query and retrieve the behavior information of the mobile phone number in other apps, including whether the login terminal of other apps has changed within a certain time period, whether the mobile phone number has been changed, and whether the customer manager's contact address has changed.

[0092] 3. Use the mobile phone number to query and retrieve the wage payment transaction information of the mobile phone number. For example, use the personal mobile banking server to query whether the payee of wage payment has changed in the past X months. If so, return it.

[0093] 4. Use the enterprise group number corresponding to the mobile phone number to check in the device whether the enterprise has bound other mobile phone numbers, and count all time periods and binding times.

[0094] 5. Obtain all transaction types for the services currently bound to the mobile phone number.

[0095] Among them, the real-name release information of the mobile phone number includes the number of days for release and the real-name information.

[0096] Figure 4 is a flow chart of S101 in an embodiment of the present invention. Figure 4 As shown, S101 includes:

[0097] S201: Determine the number release information according to the number of days for releasing the number.

[0098] In specific implementation, if the mobile phone number is a secondary number, it will be sorted according to the number of days since the customer's secondary number was issued. If it exceeds 180 days, it will be marked as -1, and if it is 0-180 days, it will be marked as x indicates the number of days that have passed since the second release of the number, and 0 days is marked as 0.

[0099] S202: Determine the first risk data according to the number release information and the real-name information.

[0100] In specific implementation, the real-name status and secondary number release status of the mobile phone number are obtained through the operator's mobile phone number query results. The results are divided into three types: real-name, non-real-name, and no real-name mobile phone numbers. They are quantitatively assigned values ​​and marked with a. The real-name is marked as 1, the non-real-name is marked as -1, and the no real-name is marked as 0.

[0101] S102: Determine second risk data according to the media access control address of each application.

[0102] In one embodiment, S102 includes: determining the second risk data according to the number of media access control addresses of each application, login data of each application, and the number of applications.

[0103] During the specific implementation, the behavior of other apps is queried through the mobile phone number to obtain the terminal MAC address (media access control address) and the mobile phone number bound to other app logins. The terminal MAC address is compared with the corporate bank MAC address, and the mobile phone number bound to other app logins is compared with the mobile phone number. Quantitative values ​​are assigned according to the address and mobile phone number drift results.

[0104] Figure 5 is a flow chart of S102 in an embodiment of the present invention. Figure 5 As shown, S102 includes:

[0105] S301: Determine address registration parameters of each application according to the number of media access control addresses of each application and the registration data of each application.

[0106] S302: Determine the second risk data according to the address login parameters of each application and the number of applications.

[0107] In one embodiment, the second risk data may be determined by the following formula:

[0108]

[0109] Among them, b is the second risk data, α n The number of media access control addresses logged in for the nth application in the past three months, β n Login data for the nth app in the past three months. The address registration parameter for the nth application, where n is the number of applications.

[0110] S103: Determine third risk data according to the salary transaction information.

[0111] Among them, salary transaction information includes salary transaction records and the name of the paying company. You can check the salary payment information to determine whether the person who handles it is still in the company.

[0112] Figure 6 is a flow chart of S103 in an embodiment of the present invention. Figure 6 As shown, S103 includes:

[0113] S401: When there is no salary transaction record, determining that the third risk data is the first identification data.

[0114] S402: When the salary transaction record exists and the name of the paying company has changed, determining that the third risk data is the second identification data.

[0115] In specific implementation, it is first checked whether there is a wage transaction record. When there is no wage transaction record, it is determined that the third risk data c is the first identification data 0.

[0116] When the salary transaction record exists and the name of the paying company has changed, the third risk data is determined to be the second identification data-1.

[0117] Figure 7 FIG. 1 is a flow chart for determining the third risk data in an embodiment of the present invention. Figure 7 As shown, determining the third risk data based on the salary transaction information also includes:

[0118] S501: When the salary transaction record does not exist and the name of the paying company has not changed, the certificate data of the paying company and the certificate data of the company corresponding to the handler are obtained.

[0119] S502: Determine the third risk data according to a comparison result between the payment company's certificate data and the certificate data of the company corresponding to the handler.

[0120] During specific implementation, the corresponding enterprise group number is retrieved on the host through the payment account, and the certificate type and certificate number information P1 (payment company certificate data) in the payment enterprise account opening element information is checked. At the same time, the certificate type and certificate number information P2 (certificate data of the enterprise corresponding to the handler) in the account opening element information of the enterprise to which the handler belongs is retrieved. If P1 and P2 are the same, the c identifier is 1; if the certificate numbers are different or the certificate types are different, continue to the next step of checking.

[0121] Figure 8 FIG. 1 is a flow chart of determining the third risk data in another embodiment of the present invention. Figure 8 As shown, determining the third risk data based on the salary transaction information also includes:

[0122] S601: When the certificate data of the payment company and the certificate data of the enterprise corresponding to the handler are the same, determining the linkage relationship between the payment company and the enterprise corresponding to the handler.

[0123] S602: Determine the third risk data according to the attachment relationship.

[0124] When it is implemented, check whether the company to which the agent belongs and the payroll company have a branch connection relationship. If so, the first-level company is marked as 0.8, the second-level subsidiary is marked as 0.6, and so on according to the connection level. If there is no branch connection relationship, compare the name of the company to which the agent belongs and the payroll company, and compare the keywords after removing the words such as the nature of the enterprise and the company through text comparison to see if they are consistent. For example, if the name of the payroll company of the client is "Beijing Mingyue Decoration Design Co., Ltd." and the name of the company to which the agent belongs is "Beijing Mingyue Wanjia Design Co., Ltd.", then remove the words "Beijing" and "Limited Shareholding Co., Ltd." during the comparison, and compare "Mingyue Decoration Design" and "Mingyue Wanjia Design". If they are exactly the same, they are marked as 1; if they are more than 50% consistent, they are marked as 0.5; if they are less than 50%, they are marked as 0.

[0125] S104: Determine fourth risk data according to the mobile phone binding information.

[0126] In specific implementation, we can query the mobile phone number binding situation in the group's corporate bank to count whether other mobile phone numbers are bound after this time. If bound, count the number of bindings and assign quantitative values ​​according to whether they are bound. The fourth risk data is marked with d and the calculation method is as follows:

[0127] 1. If the mobile phone number of the agent is unbound and a new mobile phone number other than the agent is bound, the mark is -1.

[0128] 2. If the mobile phone number of the person who handled the transaction has not been unbound, or has been unbound but is still the mobile phone number of the person who handled the transaction, it will be marked as 1.

[0129] 3. If the mobile phone number of the person handling the case has not been unbound but is bound to other mobile phone numbers at the same time, the mark will be 0.

[0130] S105: Determine comprehensive risk data according to the first risk data, the second risk data, the third risk data and the fourth risk data, and send risk information to a bank service end according to the comprehensive risk data.

[0131] During the specific implementation, the comprehensive risk data will be divided into three categories: high risk, medium risk and low risk according to the threshold, and the risk level will be divided based on the type of SMS received by the customer.

[0132] The types of SMS received are divided into three categories according to the risk from high to low: transaction type, non-transaction type, and marketing promotion type. Among them, the risk of transaction type is high, the risk of non-transaction type is medium, and the risk of marketing promotion type is low.

[0133] If the risk information is low risk, the mobile phone number will not be processed and the result will be returned to the [Corporate Banking Service End].

[0134] If the risk information is medium risk and the risk of the transaction type received by the customer through SMS is assessed to be low, a request is sent to the [Corporate Banking Server], and the push fields include the group number, operator number, mobile phone number, and the transaction type bound to the mobile phone number. The [Corporate Banking Server] queries the group authorizer based on the group number, and sends the operator number, the problematic mobile phone number, and the transaction type to the authorizer through the authorization instruction. Inform the authorizer that there is binding information for the mobile phone number and ask the authorizer whether he is willing to unbind. If the authorizer authorizes, the [Corporate Banking Server] will return the authorization through the application, query all the businesses of the mobile phone number under the group number, and send the mobile phone number association unbinding application to the corresponding business management system.

[0135] If the risk information is medium risk and the risk of the transaction type received by the customer's SMS is assessed to be medium or high, query all the businesses of the mobile phone number under the group number, and send the mobile phone number association freezing application to the corresponding business management system. At the same time, send a request to the [Corporate Banking Service], and push fields including group number, operator number, mobile phone number, and transaction type bound to the mobile phone number. The [Corporate Banking Service] queries the group authorizer according to the group number, and sends the operator number, problematic mobile phone number, and transaction type to the authorizer through the authorization instruction. Inform the authorizer that the mobile phone number has been frozen due to risk, and ask the authorizer whether he is willing to unbind it. If the authorizer authorizes within a fixed period, the process is the same as above, and send the mobile phone number association unbinding application to the corresponding business management system. If the authorization is not granted within the specified time, query all the businesses of the mobile phone number under the group number after the specified time, and send the mobile phone number association unfreezing application to the corresponding business management system.

[0136] If the risk information is high risk, all businesses of the mobile phone number under the group number will be immediately queried, and the mobile phone number association unbinding application will be sent to the corresponding business management system. At the same time, a request will be sent to the [Corporate Banking Server], and the push fields include the group number, operator number, mobile phone number, and transaction type bound to the mobile phone number. The [Corporate Banking Server] will query the group authorizer according to the group number and send a text message notification to the authorizer that the mobile phone number corresponding to the transaction type has been unbound.

[0137] Figure 1 The execution subject of the risk prevention and control method shown can be the information risk prediction device of the person in charge. Figure 1 It can be seen from the shown process that the risk prevention and control method of the embodiment of the present invention determines the first risk data based on the real-name release information of the mobile phone number, determines the second risk data based on the media access control address of each application, determines the third risk data based on the salary transaction information, and determines the fourth risk data based on the mobile phone binding information to send the risk information to the bank service end. Information desensitization measures can be actively taken to further avoid the risk of information leakage.

[0138] The specific process of the embodiment of the present invention is as follows:

[0139] 1. Determine the number issuance information according to the number of days for issuing the number, and determine the first risk data according to the number issuance information and the real-name information.

[0140] 2. Determine the address registration parameter of each application according to the number of media access control addresses of each application and the registration data of each application.

[0141] 3. Determine the second risk data according to the address login parameters of each application and the number of applications.

[0142] 4. When there is no salary transaction record, the third risk data is determined to be the first identification data.

[0143] 5. When the salary transaction record exists and the name of the paying company has changed, the third risk data is determined to be the second identification data.

[0144] 6. When the wage transaction record does not exist and the name of the paying company has not changed, obtain the certificate data of the paying company and the certificate data of the company corresponding to the person handling the payment.

[0145] 7. Determine the third risk data based on the comparison result between the certificate data of the payment company and the certificate data of the enterprise corresponding to the handler.

[0146] 8. When the certificate data of the payment company and the certificate data of the enterprise corresponding to the handler are the same, the linkage relationship between the payment company and the enterprise corresponding to the handler is determined.

[0147] 9. Determine the third risk data according to the attachment relationship.

[0148] 10. Determine the fourth risk data based on the mobile phone binding information.

[0149] 11. Determine comprehensive risk data based on the first risk data, the second risk data, the third risk data and the fourth risk data, and send risk information to a bank service end based on the comprehensive risk data.

[0150] In summary, the risk prevention and control method of the embodiment of the present invention provides a solution for automatically predicting risks for the scenario where corporate bank agents receive text messages after handling business via text messages. While helping enterprises to promptly learn about invalid agents, it actively intervenes in the sending of text messages, thereby improving the timeliness and flexibility of risk prevention and control.

[0151] Based on the same inventive concept, an embodiment of the present invention further provides a risk prevention and control device. Since the principle of solving the problem by the device is similar to that of the risk prevention and control method, the implementation of the device can refer to the implementation of the method, and the repeated parts will not be repeated.

[0152] Fig. 9 is a structural block diagram of the risk prevention and control device in an embodiment of the present invention. Fig. 9 As shown, the risk prevention and control device includes:

[0153] A first risk data determination module, used to determine first risk data according to the real-name release information of the mobile phone number;

[0154] A second risk data determination module, configured to determine second risk data according to the media access control address of each application;

[0155] A third risk data determination module, used to determine third risk data according to the salary transaction information;

[0156] A fourth risk data determination module, used to determine fourth risk data according to mobile phone binding information;

[0157] A comprehensive risk data determination module is used to determine comprehensive risk data based on the first risk data, the second risk data, the third risk data and the fourth risk data, and send risk information to a bank service end based on the comprehensive risk data.

[0158] In one embodiment, the mobile phone number real-name release information includes the number of days for release and real-name information;

[0159] The first risk data determination module includes:

[0160] A number release information unit, used to determine the number release information according to the number release days;

[0161] The first risk data unit is used to determine the first risk data according to the number release information and the real-name information.

[0162] In one embodiment, the second risk data determination module is specifically used to:

[0163] The second risk data is determined according to the number of media access control addresses of each application, login data of each application, and the number of applications.

[0164] In one embodiment, the second risk data determination module includes:

[0165] An address registration parameter unit, used to determine the address registration parameter of each application according to the number of media access control addresses of each application and the registration data of each application;

[0166] The second risk data unit is used to determine the second risk data according to the address login parameters of each application and the number of applications.

[0167] In one embodiment, the salary transaction information includes a salary transaction record and a name of a paying company;

[0168] The third risk data determination module includes:

[0169] A first identification data unit, used to determine that the third risk data is the first identification data when there is no salary transaction record;

[0170] The second identification data unit is used to determine that the third risk data is the second identification data when the salary transaction record exists and the name of the paying company has changed.

[0171] In one embodiment, the third risk data determination module further includes:

[0172] The certificate data unit is used to obtain the certificate data of the paying company and the certificate data of the company corresponding to the handler when there is no salary transaction record and the name of the paying company has not changed;

[0173] The certificate risk unit is used to determine the third risk data according to the comparison result of the certificate data of the payment company and the certificate data of the enterprise corresponding to the handler.

[0174] In one embodiment, the third risk data determination module further includes:

[0175] A linkage relationship unit, used for determining the linkage relationship between the payment company and the enterprise corresponding to the handler when the certificate data of the payment company and the certificate data of the enterprise corresponding to the handler are the same;

[0176] The attachment risk unit is used to determine the third risk data according to the attachment relationship.

[0177] In summary, the risk prevention and control device of the embodiment of the present invention determines the first risk data according to the real-name release information of the mobile phone number, determines the second risk data according to the media access control address of each application, determines the third risk data according to the salary transaction information, and determines the fourth risk data according to the mobile phone binding information to send the risk information to the bank service end. It can take active information desensitization measures to further avoid the risk of information leakage.

[0178] Fig.10 FIG. 9 is a schematic block diagram of the system structure of the electronic device 9600 according to an embodiment of the present application. Fig.10 As shown, the electronic device 9600 may include a central processor 9100 and a memory 9140; the memory 9140 is coupled to the central processor 9100. It is worth noting that Fig.10 is exemplary; other types of structures may also be used to supplement or replace this structure to implement telecommunication functions or other functions.

[0179] In one embodiment, the risk prevention and control method function may be integrated into the central processing unit 9100. The central processing unit 9100 may be configured to perform the following control:

[0180] Determine the first risk data based on the real-name release information of the mobile phone number;

[0181] determining second risk data according to the media access control address of each application;

[0182] Determine third-party risk data based on wage transaction information;

[0183] Determine the fourth risk data based on the mobile phone binding information;

[0184] Comprehensive risk data is determined according to the first risk data, the second risk data, the third risk data and the fourth risk data, and risk information is sent to a bank service end according to the comprehensive risk data.

[0185] From the above description, it can be seen that the risk prevention and control method provided by this application determines the first risk data based on the real-name release information of the mobile phone number, determines the second risk data based on the media access control address of each application, determines the third risk data based on the salary transaction information, and determines the fourth risk data based on the mobile phone binding information to send risk information to the bank service end. It can take active information desensitization measures to further avoid the risk of information leakage.

[0186] In another embodiment, the risk prevention and control device can be configured separately from the central processor 9100. For example, the risk prevention and control device can be configured as a chip connected to the central processor 9100, and the functions of the risk prevention and control method can be implemented through the control of the central processor.

[0187] like Fig.10 As shown, the electronic device 9600 may also include: a communication module 9110, an input unit 9120, an audio processor 9130, a display 9160, and a power supply 9170. It is worth noting that the electronic device 9600 does not necessarily have to include Fig.10 In addition, the electronic device 9600 may also include Fig.10 For components not shown, reference may be made to the prior art.

[0188] like Fig.10 As shown, the central processing unit 9100 is sometimes also referred to as a controller or an operation control, and may include a microprocessor or other processor device and / or logic device. The central processing unit 9100 receives input and controls the operation of various components of the electronic device 9600.

[0189] The memory 9140 may be, for example, one or more of a cache, a flash memory, a hard drive, a removable medium, a volatile memory, a non-volatile memory or other suitable devices. The above-mentioned information related to the failure may be stored, and a program for executing the relevant information may also be stored. The CPU 9100 may execute the program stored in the memory 9140 to implement information storage or processing, etc.

[0190] The input unit 9120 provides input to the central processing unit 9100. The input unit 9120 is, for example, a key or a touch input device. The power supply 9170 is used to provide power to the electronic device 9600. The display 9160 is used to display display objects such as images and texts. The display may be, for example, an LCD display, but is not limited thereto.

[0191] The memory 9140 may be a solid-state memory, such as a read-only memory (ROM), a random access memory (RAM), a SIM card, etc. It may also be a memory that saves information even when the power is off, can be selectively erased, and is provided with more data, examples of which are sometimes referred to as EPROMs, etc. The memory 9140 may also be some other type of device. The memory 9140 includes a buffer 9141 (sometimes referred to as a buffer memory). The memory 9140 may include an application / function storage unit 9142, which is used to store application programs and function programs or processes for executing the operation of the electronic device 9600 through the central processor 9100.

[0192] The memory 9140 may also include a data storage unit 9143 for storing data, such as contacts, digital data, pictures, sounds, and / or any other data used by the electronic device. The driver storage unit 9144 of the memory 9140 may include various drivers for communication functions of the electronic device and / or for executing other functions of the electronic device (such as messaging applications, address book applications, etc.).

[0193] The communication module 9110 is a transmitter / receiver 9110 that sends and receives signals via an antenna 9111. The communication module (transmitter / receiver) 9110 is coupled to the central processor 9100 to provide input signals and receive output signals, which may be the same as the case of a conventional mobile communication terminal.

[0194] Based on different communication technologies, multiple communication modules 9110 may be provided in the same electronic device, such as a cellular network module, a Bluetooth module and / or a wireless LAN module, etc. The communication module (transmitter / receiver) 9110 is also coupled to a speaker 9131 and a microphone 9132 via an audio processor 9130 to provide an audio output via the speaker 9131 and receive an audio input from the microphone 9132, thereby realizing a common telecommunication function. The audio processor 9130 may include any suitable buffer, decoder, amplifier, etc. In addition, the audio processor 9130 is also coupled to the central processor 9100, so that recording can be performed on the local machine through the microphone 9132, and the sound stored on the local machine can be played through the speaker 9131.

[0195] The embodiment of the present invention also provides a computer-readable storage medium capable of implementing all the steps of the risk prevention and control method in the above embodiment, where the execution subject is a server or a client. The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, all the steps of the risk prevention and control method in the above embodiment are implemented. For example, when the processor executes the computer program, the following steps are implemented:

[0196] Determine the first risk data based on the real-name release information of the mobile phone number;

[0197] determining second risk data according to the media access control address of each application;

[0198] Determine third-party risk data based on wage transaction information;

[0199] Determine the fourth risk data based on the mobile phone binding information;

[0200] Comprehensive risk data is determined according to the first risk data, the second risk data, the third risk data and the fourth risk data, and risk information is sent to a bank service end according to the comprehensive risk data.

[0201] In summary, the computer-readable storage medium of the embodiment of the present invention determines the first risk data according to the real-name release information of the mobile phone number, determines the second risk data according to the media access control address of each application, determines the third risk data according to the salary transaction information, and determines the fourth risk data according to the mobile phone binding information to send the risk information to the bank service end, and can actively take information desensitizing measures to further avoid the risk of information leakage.

[0202] The embodiment of the present invention also provides a computer program product capable of implementing all the steps of the risk prevention and control method in the above embodiment, where the execution subject is a server or a client. The computer program product includes a computer program / instruction. When the computer program / instruction is executed by a processor, all the steps of the risk prevention and control method in the above embodiment are implemented. For example, when the processor executes the computer program, the following steps are implemented:

[0203] Determine the first risk data based on the real-name release information of the mobile phone number;

[0204] determining second risk data according to the media access control address of each application;

[0205] Determine third-party risk data based on wage transaction information;

[0206] Determine the fourth risk data based on the mobile phone binding information;

[0207] Comprehensive risk data is determined according to the first risk data, the second risk data, the third risk data and the fourth risk data, and risk information is sent to a bank service end according to the comprehensive risk data.

[0208] In summary, the computer program product of the embodiment of the present invention determines the first risk data based on the real-name release information of the mobile phone number, determines the second risk data based on the media access control address of each application, determines the third risk data based on the salary transaction information, and determines the fourth risk data based on the mobile phone binding information to send the risk information to the bank service end. It can actively take information desensitization measures to further avoid the risk of information leakage.

[0209] Based on the same inventive concept, an embodiment of the present invention also provides a risk prevention and control system. Since the principle of solving the problem by the system is similar to that of the risk prevention and control method, the implementation of the system can refer to the implementation of the method, and the repeated parts will not be repeated.

[0210] Fig.11 Schematic diagram of the risk prevention and control system in an embodiment of the present invention. Fig.11 As shown in the figure, the risk prevention and control system includes:

[0211] Risk prevention and control devices as described above;

[0212] The client is used to send the mobile phone number to the server;

[0213] The server is used to send the mobile phone number to the risk prevention and control device and push the risk information from the risk prevention and control device to the customer.

[0214] In summary, the risk prevention and control system of the embodiment of the present invention determines the first risk data based on the real-name release information of the mobile phone number, determines the second risk data based on the media access control address of each application, determines the third risk data based on the salary transaction information, and determines the fourth risk data based on the mobile phone binding information to send the risk information to the bank service end. It can actively take information desensitization measures to further avoid the risk of information leakage.

[0215] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the hardware + program embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0216] The above is a description of a specific embodiment of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0217] Although the present application provides method operation steps as described in the embodiments or flowcharts, more or fewer operation steps may be included based on conventional or non-creative labor. The order of steps listed in the embodiments is only one way of executing the order of many steps and does not represent the only execution order. When the actual device or client product is executed, it can be executed in the order of the method shown in the embodiments or the drawings or in parallel (for example, in a parallel processor or multi-threaded processing environment).

[0218] Although the present specification embodiment provides the method operation steps as described in the embodiment or flow chart, more or less operation steps may be included based on conventional or non-creative means. The order of steps listed in the embodiment is only one way in the order of execution of many steps, and does not represent a unique execution order. When the device or terminal product in practice is executed, it can be executed in sequence or in parallel (such as a parallel processor or a multi-threaded processing environment, or even a distributed data processing environment) according to the method shown in the embodiment or the accompanying drawings. The term "include", "comprise" or any other variant thereof is intended to cover non-exclusive inclusion, so that the process, method, product or equipment including a series of elements not only includes those elements, but also includes other elements not clearly listed, or also includes elements inherent to such process, method, product or equipment. In the absence of more restrictions, it is not excluded that there are other identical or equivalent elements in the process, method, product or equipment including the elements.

[0219] For the convenience of description, the above devices are described in various modules according to their functions. Of course, when implementing the embodiments of this specification, the functions of each module can be implemented in the same or more software and / or hardware, or the module implementing the same function can be implemented by a combination of multiple sub-modules or sub-units. The device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0220] Those skilled in the art also know that, in addition to implementing the controller in a purely computer-readable program code, the controller can be made to implement the same function in the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers by logically programming the method steps. Therefore, such a controller can be considered as a hardware component, and the devices for implementing various functions included therein can also be considered as structures within the hardware component. Or even, the devices for implementing various functions can be considered as both software modules for implementing the method and structures within the hardware component.

[0221] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0222] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0223] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0224] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0225] The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0226] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0227] Those skilled in the art will appreciate that the embodiments of this specification may be provided as methods, systems or computer program products. Therefore, the embodiments of this specification may take the form of complete hardware embodiments, complete software embodiments or embodiments combining software and hardware. Moreover, the embodiments of this specification may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes.

[0228] The various embodiments in this specification may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The embodiments of this specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules may be located in local and remote computer storage media, including storage devices.

[0229] Each embodiment in this specification is described in a progressive manner, and the same and similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment. In the description of this specification, the description of the reference terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the embodiment of this specification. In this specification, the schematic representation of the above terms does not necessarily target the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described can be combined in any one or more embodiments or examples in a suitable manner. In addition, those skilled in the art can combine and combine the different embodiments or examples described in this specification and the features of different embodiments or examples without contradiction.

[0230] The above is only an example of the embodiment of the present specification and is not intended to limit the embodiment of the present specification. For those skilled in the art, the embodiment of the present specification may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the embodiment of the present specification shall be included in the scope of the claims of the embodiment of the present specification.

Claims

1. A risk prevention and control method, characterized in that: include: Determine the first risk data based on the real-name release information of the mobile phone number; determining second risk data according to the media access control address of each application; Determine third-party risk data based on wage transaction information; Determine the fourth risk data based on the mobile phone binding information; Comprehensive risk data is determined according to the first risk data, the second risk data, the third risk data and the fourth risk data, and risk information is sent to a bank service end according to the comprehensive risk data.

2. The risk prevention and control method according to claim 1, characterized in that: The mobile phone number real-name release information includes the number of days for release and real-name information; The first risk data determined based on the real-name release information of mobile phone numbers includes: Determine the number release information according to the number of days for number release; The first risk data is determined according to the number release information and the real-name information.

3. The risk prevention and control method according to claim 1, characterized in that: Determining the second risk data according to the media access control address of each application includes: The second risk data is determined according to the number of media access control addresses of each application, login data of each application, and the number of applications.

4. The risk prevention and control method according to claim 3 is characterized in that: Determining the second risk data according to the number of media access control addresses of each application, login data of each application, and the number of applications includes: Determining address registration parameters of each application according to the number of media access control addresses of each application and the registration data of each application; The second risk data is determined according to the address login parameters of each application and the number of applications.

5. The risk prevention and control method according to claim 1, characterized in that: Payroll transaction information includes payroll transaction records and the name of the paying company; The third risk data determined based on salary transaction information includes: When there is no salary transaction record, determining that the third risk data is the first identification data; When the salary transaction record exists and the name of the paying company changes, the third risk data is determined to be the second identification data.

6. The risk prevention and control method according to claim 5, characterized in that: The third risk data determined based on salary transaction information also includes: When the wage transaction record does not exist and the name of the paying company has not changed, obtaining the certificate data of the paying company and the certificate data of the company corresponding to the handler; The third risk data is determined based on a comparison result between the payment company's certificate data and the certificate data of the enterprise corresponding to the handler.

7. The risk prevention and control method according to claim 6, characterized in that: The third risk data determined based on salary transaction information also includes: When the certificate data of the payment company and the certificate data of the enterprise corresponding to the handler are the same, determining the linkage relationship between the payment company and the enterprise corresponding to the handler; The third risk data is determined according to the attachment relationship.

8. A risk prevention and control device, characterized in that: include: A first risk data determination module, used to determine first risk data according to the real-name release information of the mobile phone number; A second risk data determination module, configured to determine second risk data according to the media access control address of each application; A third risk data determination module, used to determine third risk data according to the salary transaction information; A fourth risk data determination module, used to determine fourth risk data according to mobile phone binding information; A comprehensive risk data determination module is used to determine comprehensive risk data based on the first risk data, the second risk data, the third risk data and the fourth risk data, and send risk information to a bank service end based on the comprehensive risk data.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and running on the processor, characterized in that: When the processor executes the computer program, the steps of the risk prevention and control method described in any one of claims 1 to 7 are implemented.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the risk prevention and control method described in any one of claims 1 to 7 are implemented.

11. A risk prevention and control system, characterized in that: include: The risk prevention and control device as claimed in claim 8; The client is used to send the mobile phone number to the server; The server is used to send the mobile phone number to the risk prevention and control device and push the risk information from the risk prevention and control device to the customer.

Images