Account risk assessment method and device, computer equipment, readable storage medium and program product

Abstract

The invention relates to an account risk assessment method and device, computer equipment, a computer readable storage medium and a computer program product. The method is applied to a terminal, the terminal carries out resource calling through a target network service platform, and the method comprises the following steps: responding to a received account detection instruction, calling an interface of the target network service platform, and obtaining a to-be-evaluated account and account data corresponding to the to-be-evaluated account; according to the account usage type of the to-be-assessed account, a risk assessment strategy matched with the to-be-assessed account is determined, and the risk assessment strategy comprises a risk assessment rule and a risk assessment index corresponding to the risk assessment rule; and obtaining target data matched with the risk assessment rule from the account data, and determining that the account passes assessment under the condition that the target data conforms to the risk assessment index. By adopting the method, the evaluation accuracy can be improved.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to a method, apparatus, computer equipment, computer-readable storage medium, and computer program product for risk assessment of an account. Background Art

[0002] Cloud services refer to various computing resources, storage, applications and services provided through the Internet. Cloud services allow users to access and manage computing resources through the Internet without having to purchase and maintain actual hardware infrastructure. Usually, users can register a public cloud account on a public cloud service platform to access and manage cloud services.

[0003] In order to ensure the security and reliability of the service, it is necessary to ensure the security and reliability of the account. In the related technology, account detection can be performed according to the detection rules provided by the public cloud vendor. However, the detection accuracy is poor in this way, and it is impossible to accurately assess the risk of the account. Summary of the invention

[0004] Based on this, it is necessary to provide a risk assessment method, device, computer equipment, computer-readable storage medium and computer program product for an account that can improve accuracy in order to address the above technical issues.

[0005] In a first aspect, the present application provides a method for risk assessment of an account, the method being applied to a terminal, the terminal performing resource invocation through a target network service platform, the method comprising:

[0006] In response to receiving the account detection instruction, calling the interface of the target network service platform to obtain the account to be evaluated and the account data corresponding to the account to be evaluated;

[0007] Determine, according to the account usage type of the account to be evaluated, a risk assessment strategy matching the account to be evaluated, wherein the risk assessment strategy includes risk assessment rules and risk assessment indicators corresponding to the risk assessment rules;

[0008] Target data matching the risk assessment rule is acquired from the account data, and when the target data meets the risk assessment indicator, it is determined that the account has passed the assessment.

[0009] In one embodiment, determining a risk assessment strategy matching the account to be assessed according to the account type of the account to be assessed includes:

[0010] In the case that the account to be evaluated is an interface calling account, a risk assessment strategy matching the account to be evaluated is determined, wherein the risk assessment strategy includes at least one of an account activation duration rule and an account calling resource rule.

[0011] In one embodiment, obtaining target data matching the risk assessment rule from the account data, and determining that the account passes the assessment when the target data meets the risk assessment indicator, includes:

[0012] In the case where the risk assessment rule includes an account activation time rule, obtaining the activation time of the account to be assessed;

[0013] If the time from the activation time to the current time is within a preset time range, determining that the account has passed the evaluation; and / or,

[0014] In the case where the risk assessment rule includes an account calling resource rule, obtaining abnormal response information corresponding to the account to be assessed;

[0015] When the abnormal response type of the abnormal response information meets the preset response type, it is determined that the account has failed the evaluation, and the account to be evaluated is marked.

[0016] In one embodiment, after obtaining the activation time of the account to be evaluated, the method further includes:

[0017] When the time from the activation time to the current time is outside the preset time range, the key information of the account to be evaluated is replaced with the preset key information, and the account to be evaluated is marked.

[0018] In one embodiment, determining a risk assessment strategy matching the account to be assessed according to the account type of the account to be assessed includes:

[0019] In the case that the account to be evaluated is a platform access account, a risk assessment strategy matching the account to be evaluated is determined, wherein the risk assessment strategy includes an account status rule.

[0020] In one embodiment, obtaining target data matching the risk assessment rule from the account data, and determining that the account passes the assessment when the target data meets the risk assessment indicator, includes:

[0021] In the case where the risk assessment rule includes an account status rule, obtaining account status data of the account to be assessed;

[0022] When the account status data corresponds to account deactivation, it is determined that the account to be evaluated has failed the evaluation, and the account to be evaluated is deleted.

[0023] In a second aspect, the present application further provides a risk assessment device for an account, the device is applied to a terminal, the terminal calls resources through a target network service platform, and the device includes:

[0024] An acquisition module, configured to, in response to receiving an account detection instruction, call an interface of the target network service platform to acquire the account to be evaluated and the account data corresponding to the account to be evaluated;

[0025] A determination module, configured to determine a risk assessment strategy matching the account to be assessed according to the account usage type of the account to be assessed, wherein the risk assessment strategy includes risk assessment rules and risk assessment indicators corresponding to the risk assessment rules;

[0026] The evaluation module is used to obtain target data matching the risk evaluation rule from the account data, and determine that the account has passed the evaluation if the target data meets the risk evaluation index.

[0027] In one embodiment, the determining module is further configured to:

[0028] In the case that the account to be evaluated is an interface calling account, a risk assessment strategy matching the account to be evaluated is determined, wherein the risk assessment strategy includes at least one of an account activation duration rule and an account calling resource rule.

[0029] In one embodiment, the evaluation module is further configured to:

[0030] In the case where the risk assessment rule includes an account activation time rule, obtaining the activation time of the account to be assessed;

[0031] If the time from the activation time to the current time is within a preset time range, determining that the account has passed the evaluation; and / or,

[0032] In the case where the risk assessment rule includes an account calling resource rule, obtaining abnormal response information corresponding to the account to be assessed;

[0033] When the abnormal response type of the abnormal response information meets the preset response type, it is determined that the account has failed the evaluation, and the account to be evaluated is marked.

[0034] In one embodiment, the device is further used for:

[0035] When the time from the activation time to the current time is outside the preset time range, the key information of the account to be evaluated is replaced with the preset key information, and the account to be evaluated is marked.

[0036] In one embodiment, the determining module is further configured to:

[0037] In the case that the account to be evaluated is a platform access account, a risk assessment strategy matching the account to be evaluated is determined, wherein the risk assessment strategy includes an account status rule.

[0038] In one embodiment, the evaluation module is further configured to:

[0039] In the case where the risk assessment rule includes an account status rule, obtaining account status data of the account to be assessed;

[0040] When the account status data corresponds to account deactivation, it is determined that the account to be evaluated has failed the evaluation, and the account to be evaluated is deleted.

[0041] In a third aspect, an embodiment of the present disclosure further provides a computer device, wherein the computer device comprises a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the steps of any one of the methods in the embodiments of the present disclosure are implemented.

[0042] In a fourth aspect, the embodiments of the present disclosure further provide a computer-readable storage medium, wherein a computer program is stored thereon, and when the computer program is executed by a processor, the steps of any one of the methods in the embodiments of the present disclosure are implemented.

[0043] In a fifth aspect, the embodiments of the present disclosure further provide a computer program product, wherein the computer program product includes a computer program, and when the computer program is executed by a processor, the steps of any one of the methods in the embodiments of the present disclosure are implemented.

[0044] The above-mentioned account risk assessment method, device, computer equipment, computer-readable storage medium and computer program product, when performing account risk assessment, in response to receiving an account detection instruction, call the interface of the target network service platform, obtain the account to be assessed and the account data corresponding to the account to be assessed, and determine the risk assessment strategy that matches the account to be assessed according to the account usage type of the account to be assessed, the risk assessment strategy includes risk assessment rules and risk assessment indicators corresponding to the risk assessment rules, obtain target data that matches the risk assessment rules from the account data, and evaluate the target data according to the risk assessment indicators to determine whether the account passes the assessment, thereby achieving a rapid and accurate assessment of account risk. When performing account risk assessment, call the interface to directly obtain the account and account data, and perform risk assessment using different risk assessment strategies according to different account usage types, which effectively improves the flexibility and accuracy of risk assessment. Different from performing risk assessment according to the rules preset by the network service platform, it can set the risk assessment strategy according to the actual application scenario, thereby reducing the loss caused by account risk. Through the correspondence between account usage type and risk assessment strategy, the target data matching in the account data is evaluated and verified in a targeted manner, which further improves the accuracy and reliability of risk assessment, reduces the workload of data processing, improves the efficiency of risk assessment, avoids waste of resources, and is suitable for more application scenarios. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] In order to more clearly illustrate the technical solutions in the embodiments of the present application or related technologies, the drawings required for use in the embodiments of the present application or related technical descriptions will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0046] Figure 1 A schematic diagram of a process of a method for risk assessment of an account in one embodiment;

[0047] Figure 2 A schematic diagram of a flow chart of a method for risk assessment of an account in another embodiment;

[0048] Figure 3 A schematic diagram of a flow chart of a method for risk assessment of an account in another embodiment;

[0049] Figure 4 is a structural block diagram of a risk assessment device for an account in an embodiment;

[0050] Figure 5 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0051] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is 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 application and are not used to limit the present application.

[0052] In one embodiment, Figure 1 As shown, a method for risk assessment of an account is provided. This embodiment uses the method applied to a terminal as an example. It can be understood that the method can also be applied to a server, and can also be applied to a system including a terminal and a server, and is implemented through the interaction between the terminal and the server. In this embodiment, the method is applied to a terminal, and the terminal calls resources through a target network service platform. The method includes:

[0053] Step S110, in response to receiving the account detection instruction, calling the interface of the target network service platform to obtain the account to be evaluated and the account data corresponding to the account to be evaluated;

[0054] Exemplarily, the target network service platform may include a cloud service platform, and the user may call resources through the cloud service platform. In some examples, the account detection instruction may be sent to the user; or it may be periodically automatically triggered, which may be determined according to the actual application scenario.

[0055] Optionally, when receiving the account detection instruction, the interface of the target network service platform is called to obtain the account to be evaluated and the corresponding account data. In one example, the interface of the target network service platform may include but is not limited to the account identity management interface, the operation audit interface, etc., which can be determined according to the actual application scenario.

[0056] Step S120, determining a risk assessment strategy matching the account to be assessed according to the account usage type of the account to be assessed, wherein the risk assessment strategy includes risk assessment rules and risk assessment indicators corresponding to the risk assessment rules;

[0057] Exemplarily, the account usage types may be divided according to the different usage functions of the account in actual application scenarios. For example, the account usage types may include but are not limited to platform access accounts, interface call accounts, etc.

[0058] Optionally, different account usage types may correspond to different risk assessment strategies, and the account usage type and risk assessment strategy may be determined based on the account characteristics and risk scenarios in actual application scenarios. The risk assessment strategy includes risk assessment rules and risk assessment indicators corresponding to the risk assessment rules. Different risk assessment rules correspond to different risk assessment indicators. The risk assessment rules may include one or more. When the risk assessment rules include multiple ones, they are used to evaluate data of different dimensions.

[0059] Step S130, obtaining target data matching the risk assessment rule from the account data, and determining that the account has passed the assessment if the target data meets the risk assessment indicator.

[0060] Exemplarily, after the risk assessment strategy is determined, matching target data is obtained from the account data according to the risk assessment rule. In one example, the risk assessment rule may include the type of data to be assessed, and the target data may be screened from the account data according to the type of data.

[0061] Optionally, determine whether the target data meets the corresponding risk assessment indicators. The risk assessment indicators may include the judgment of the data range, the judgment of the data type, etc., which may be determined based on the actual application scenario. If the target data meets the risk assessment indicators, it can be considered that the probability of the account to be assessed having a risk is low, and the account to be assessed is determined to have passed the assessment.

[0062] In one example, if the target data does not meet the risk assessment index, it can be considered that the probability of the account to be assessed being at risk is high, and it is determined that the account to be assessed has not passed the assessment. Exemplarily, the risk assessment index may also include a method for handling risky accounts. If the account to be assessed has not passed the assessment, subsequent operations may be performed according to the method for handling risky accounts. For example, the method for handling risky accounts may include but is not limited to marking, sending warning information, deleting, etc., which may be specifically set according to the actual application scenario.

[0063] In the disclosed embodiment, when performing risk assessment of an account, in response to receiving an account detection instruction, the interface of the target network service platform is called to obtain the account to be assessed and the account data corresponding to the account to be assessed, and according to the account usage type of the account to be assessed, the risk assessment strategy matching the account to be assessed is determined, the risk assessment strategy includes risk assessment rules and risk assessment indicators corresponding to the risk assessment rules, the target data matching the risk assessment rules are obtained from the account data, and the target data is evaluated according to the risk assessment indicators to determine whether the account passes the assessment, thereby achieving a rapid and accurate assessment of the account risk. When performing account risk assessment, the interface is called to directly obtain the account and account data, and different risk assessment strategies are used to perform risk assessment according to different account usage types, which effectively improves the flexibility and accuracy of risk assessment. Different from performing risk assessment according to the rules preset by the network service platform, the risk assessment strategy can be set according to the actual application scenario, thereby reducing the loss caused by account risk. Through the correspondence between account usage type and risk assessment strategy, the target data matching in the account data is evaluated and verified in a targeted manner, which further improves the accuracy and reliability of risk assessment, reduces the workload of data processing, improves the efficiency of risk assessment, avoids waste of resources, and is suitable for more application scenarios.

[0064] In one embodiment, Figure 2 As shown, the risk assessment strategy matching the account to be assessed is determined according to the account type of the account to be assessed, including:

[0065] Step S121, when the account to be evaluated is an interface calling account, determine a risk assessment strategy matching the account to be evaluated, wherein the risk assessment strategy includes at least one of an account activation duration rule and an account calling resource rule.

[0066] Exemplarily, when the account to be evaluated is an interface calling account, a corresponding risk assessment strategy is determined, and the risk assessment strategy includes at least one of an account activation duration rule and an account calling resource rule.

[0067] In one example, the interface calling account includes an account used for programmatic access and management through an API (application programming interface), and the user uses the interface calling account to create, update, query, or delete cloud resources through API requests, wherein the interface calling account interacts with the API of the cloud service through coding in a programming language (such as Python, Java, etc.).

[0068] Optionally, the account activation duration rule can be used to judge and verify the account activation duration to avoid the risk of account leakage caused by the account being activated for too long. The account resource call rule can be used to judge and verify the situation of the account calling resources. In an example, different accounts can correspond to different resource call permissions. By judging and verifying the situation of the account calling resources, accounts with abnormal account resource calls can be effectively screened out to avoid the problem of account information leakage.

[0069] In the embodiment of the present disclosure, when the account to be evaluated is an interface calling account, a corresponding risk assessment strategy is determined, and the risk assessment strategy includes at least one of an account activation duration rule and an account calling resource rule, thereby being able to take into account that the interface calling account is an account used in a code program, and that the account can call the resources of a target network service platform, and to verify the account activation duration and the called resources, and to effectively screen out accounts with excessive usage time and abnormal resource calls, thereby improving data security and reliability.

[0070] In one embodiment, Figure 3 As shown, the step of obtaining target data matching the risk assessment rule from the account data and determining that the account has passed the assessment when the target data meets the risk assessment indicator includes:

[0071] Step S131, when the risk assessment rule includes an account activation time rule, obtaining the activation time of the account to be assessed;

[0072] Step S132, if the time from the activation time to the current time is within a preset time range, determining that the account has passed the evaluation; and / or,

[0073] Step S133, when the risk assessment rule includes an account calling resource rule, obtaining abnormal response information corresponding to the account to be assessed;

[0074] Step S134: if the abnormal response type of the abnormal response information meets the preset response type, determine that the account has not passed the evaluation, and mark the account to be evaluated.

[0075] Exemplarily, when the risk assessment rule includes an account activation duration rule, the corresponding target data is determined to be the activation time of the account to be assessed, and the activation time of the account to be assessed is obtained.

[0076] In one example, when the risk assessment rule is an account activation rule, its corresponding risk assessment indicator may include that the account activation duration is within a preset duration range. The account activation duration is determined according to the activation time of the account, and the account activation duration is the duration from the activation time of the account to the current time.

[0077] When the account activation time is within the preset time range, the account is determined to have passed the assessment, wherein the preset time range can be set according to the actual application scenario. For example, the time threshold can be set according to the actual application scenario, and 0 to the time threshold is determined as the preset time range. If the account activation time is within the preset time range, it can be considered that the probability of the account being at risk is small.

[0078] Exemplarily, when the risk assessment rule includes an account calling resource rule, it is determined that the corresponding target data is abnormal response information of the account to be assessed, and the abnormal response information of the account to be assessed is obtained.

[0079] In one example, when the risk assessment rule is an account calling resource rule, the corresponding risk assessment indicator may include that the response information type of the account calling resource meets the preset response type. The abnormal response type is determined according to the abnormal response information of the account.

[0080] If the abnormal response type meets the preset response type, it can be considered that the account has an abnormality and has failed the risk assessment. Optionally, the preset response type can be determined according to the actual application scenario. For example, the preset response type can include a forbidden response. When the account calls a resource and there is a forbidden response, it can be considered that the account attempts to use unauthorized permissions, and there may be an account leak.

[0081] In one example, under the account call resource rule, the corresponding risk assessment indicator includes a risk account processing method that can be set to mark and send warning information. At this time, the assessment account is marked and abnormal information is sent to the relevant information recipient so that the operation and maintenance personnel can conduct risk investigation on the account in a timely manner.

[0082] In the embodiments of the present disclosure, when the risk assessment rules include the account activation time rule, the time from the activation time of the account to be assessed to the current time is evaluated, so that accounts with too long activation time can be effectively screened out and risk warnings can be issued; when the risk assessment rules include the account call resource rule, the abnormal response information of the account to be assessed is evaluated, so that accounts with abnormal resource calls can be effectively screened out and marked, thereby avoiding the problem of account information leakage and effectively improving security and reliability.

[0083] In one embodiment, after obtaining the activation time of the account to be evaluated, the method further includes:

[0084] When the time from the activation time to the current time is outside the preset time range, the key information of the account to be evaluated is replaced with the preset key information, and the account to be evaluated is marked.

[0085] For example, when the time from the activation moment to the current moment is outside the preset time range, it can be considered that the account activation time is long, and the key information of the account to be evaluated is replaced with the preset key information, and the account to be evaluated is marked. Among them, the preset key information can be determined according to the actual application scenario. Since the interface calling account is the account used in the code program, it is necessary to replace the key information of the account to avoid authorizing the use of the same account key information in the code program for a long time.

[0086] In the embodiment of the present disclosure, when the time from the activation moment to the current moment is outside the preset time range, the key information of the account to be evaluated is replaced to avoid authorizing the use of the same account key information in the code program for a long time, thereby strengthening data security protection.

[0087] In one embodiment, determining a risk assessment strategy matching the account to be assessed according to the account type of the account to be assessed includes:

[0088] In the case that the account to be evaluated is a platform access account, a risk assessment strategy matching the account to be evaluated is determined, wherein the risk assessment strategy includes an account status rule.

[0089] Exemplarily, when the account to be evaluated is a platform access account, a risk assessment strategy matching the account to be evaluated is determined, and the risk assessment strategy includes an account status rule for judging and verifying the account status.

[0090] In one example, a platform access account may include an account for managing and accessing cloud resources through a graphical user interface (console) provided by a cloud service, such as a console access account, where a user uses the console access account to log in to the management interface of the cloud service to perform operations such as creating, configuring, monitoring, and managing resources.

[0091] In the embodiment of the present disclosure, when the account to be evaluated is a platform access account, a corresponding risk assessment strategy is determined, and the risk assessment strategy includes an account status rule, so that the account status of the platform access account can be verified, and accounts with abnormal status can be effectively screened out, thereby improving data security and reliability.

[0092] In one embodiment, acquiring target data matching the risk assessment rule from the account data, and determining that the account has passed the assessment when the target data meets the risk assessment indicator, includes:

[0093] In the case where the risk assessment rule includes an account status rule, obtaining account status data of the account to be assessed;

[0094] When the account status data corresponds to account deactivation, it is determined that the account to be evaluated has failed the evaluation, and the account to be evaluated is deleted.

[0095] Exemplarily, when the risk assessment rules include an account status rule, the corresponding target data is determined to be the account status data of the account to be assessed, and the account status information of the account to be assessed is obtained.

[0096] In one example, when the risk assessment rule is an account status rule, the corresponding risk assessment indicator may include whether the account is deactivated. If the account status information corresponds to account deactivation, it can be considered that the account is abnormal and has failed the risk assessment. At this time, the account to be assessed is deleted to avoid account redundancy and account management loopholes caused by subsequent failure to activate according to regulations.

[0097] In a possible implementation, when the account to be evaluated is an interface calling account, the risk assessment strategy may also include an account status rule, and the abnormal account status may be determined according to the method described in the above embodiment.

[0098] In the embodiment of the present disclosure, when the risk assessment rules include account status rules, the account status data of the account to be assessed is obtained, and the deactivated accounts to be assessed are screened and deleted, so that the accounts with abnormal account status can be deleted, thereby avoiding account redundancy, reducing data processing workload, and improving efficiency; at the same time, it effectively avoids the problem of account management loopholes caused by subsequent failure to enable the account according to regulations, and effectively strengthens data security protection.

[0099] In one embodiment, the risk assessment strategy may also include an account usage time rule, the corresponding target data is the most recent usage time of the account, and the corresponding risk assessment indicator is whether the duration from the most recent usage time to the current time is within a preset range, and the preset range may be determined according to the actual application scenario. If it is not within the preset range, it may be considered that the account usage rate is low and it is an idle account, and it has not passed the assessment. An early warning message may be sent to prompt the user to confirm whether to delete the account to avoid account redundancy. In one example, the interface call account may include an API account.

[0100] Through this embodiment, the flexibility and accuracy of account risk identification on the target network service platform can be effectively improved, risk assessment can be performed from more dimensions, losses caused by improper account information management can be avoided, data security and reliability can be improved, and it is suitable for more application scenarios.

[0101] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0102] Based on the same inventive concept, the embodiment of the present application also provides an account risk assessment device for implementing the account risk assessment method involved above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above method, so the specific limitations in the embodiment of the risk assessment device for one or more accounts provided below can refer to the limitations of the account risk assessment method above, and will not be repeated here.

[0103] In an exemplary embodiment, Figure 4 As shown, a risk assessment device 400 for an account is provided, the device is applied to a terminal, the terminal calls resources through a target network service platform, and the device includes:

[0104] The acquisition module 410 is used to call the interface of the target network service platform in response to receiving the account detection instruction, and obtain the account to be evaluated and the account data corresponding to the account to be evaluated;

[0105] A determination module 420, configured to determine a risk assessment strategy that matches the account to be assessed according to the account usage type of the account to be assessed, wherein the risk assessment strategy includes a risk assessment rule and a risk assessment indicator corresponding to the risk assessment rule;

[0106] The evaluation module 430 is used to obtain target data matching the risk evaluation rule from the account data, and determine that the account has passed the evaluation if the target data meets the risk evaluation index.

[0107] In one embodiment, the determining module is further configured to:

[0108] In the case that the account to be evaluated is an interface calling account, a risk assessment strategy matching the account to be evaluated is determined, wherein the risk assessment strategy includes at least one of an account activation duration rule and an account calling resource rule.

[0109] In one embodiment, the evaluation module is further configured to:

[0110] In the case where the risk assessment rule includes an account activation time rule, obtaining the activation time of the account to be assessed;

[0111] If the time from the activation time to the current time is within a preset time range, determining that the account has passed the evaluation; and / or,

[0112] In the case where the risk assessment rule includes an account calling resource rule, obtaining abnormal response information corresponding to the account to be assessed;

[0113] When the abnormal response type of the abnormal response information meets the preset response type, it is determined that the account has failed the evaluation, and the account to be evaluated is marked.

[0114] In one embodiment, the device is further used for:

[0115] When the time from the activation time to the current time is outside the preset time range, the key information of the account to be evaluated is replaced with the preset key information, and the account to be evaluated is marked.

[0116] In one embodiment, the determining module is further configured to:

[0117] In the case that the account to be evaluated is a platform access account, a risk assessment strategy matching the account to be evaluated is determined, wherein the risk assessment strategy includes an account status rule.

[0118] In one embodiment, the evaluation module is further configured to:

[0119] In the case where the risk assessment rule includes an account status rule, obtaining account status data of the account to be assessed;

[0120] When the account status data corresponds to account deactivation, it is determined that the account to be evaluated has failed the evaluation, and the account to be evaluated is deleted.

[0121] Each module in the risk assessment device for the above account can be implemented in whole or in part by software, hardware, or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute operations corresponding to each module.

[0122] In an exemplary embodiment, a computer device is provided. The computer device may be a terminal, and its internal structure diagram may be as shown in FIG. Figure 5As shown. The computer device includes a processor, a memory, an input / output interface, a communication interface, a display unit and an input device. The processor, the memory and the input / output interface are connected through a system bus, and the communication interface, the display unit and the input device are connected to the system bus through the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The input / output interface of the computer device is used to exchange information between the processor and the external device. The communication interface of the computer device is used to communicate with an external terminal in a wired or wireless manner, and the wireless manner can be implemented through WIFI, a mobile cellular network, near field communication (Near Field Communication, NFC) or other technologies. When the computer program is executed by the processor, a risk assessment method for an account is implemented. The display unit of the computer device is used to form a visually visible picture, which can be a display screen, a projection device or a virtual reality imaging device. The display screen can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer device can be a touch layer covering the display screen, or a button, trackball or touchpad set on the computer device shell, or an external keyboard, touchpad or mouse.

[0123] Those skilled in the art will understand that Figure 5 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0124] In one embodiment, a computer device is further provided, including a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the steps in the above method embodiments when executing the computer program.

[0125] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments are implemented.

[0126] In one embodiment, a computer program product is provided, including a computer program, which implements the steps in the above method embodiments when executed by a processor.

[0127] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant regulations.

[0128] A person of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment method can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, an artificial intelligence (AI) processor, etc., but are not limited to this.

[0129] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0130] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A method for risk assessment of an account, characterized in that: The method is applied to a terminal, and the terminal calls resources through a target network service platform. The method includes: In response to receiving the account detection instruction, calling the interface of the target network service platform to obtain the account to be evaluated and the account data corresponding to the account to be evaluated; Determine, according to the account usage type of the account to be evaluated, a risk assessment strategy matching the account to be evaluated, wherein the risk assessment strategy includes risk assessment rules and risk assessment indicators corresponding to the risk assessment rules; Target data matching the risk assessment rule is acquired from the account data, and when the target data meets the risk assessment indicator, it is determined that the account has passed the assessment.

2. The method according to claim 1, characterized in that The step of determining a risk assessment strategy that matches the account to be assessed based on the account type of the account to be assessed includes: In the case that the account to be evaluated is an interface calling account, a risk assessment strategy matching the account to be evaluated is determined, wherein the risk assessment strategy includes at least one of an account activation duration rule and an account calling resource rule.

3. The method according to claim 2, characterized in that The acquiring target data matching the risk assessment rule from the account data, and determining that the account passes the assessment when the target data meets the risk assessment indicator, includes: In the case where the risk assessment rule includes an account activation duration rule, obtaining the activation time of the account to be assessed; If the time from the activation time to the current time is within a preset time range, determining that the account has passed the evaluation; and / or, In the case where the risk assessment rule includes an account calling resource rule, obtaining abnormal response information corresponding to the account to be assessed; When the abnormal response type of the abnormal response information meets the preset response type, it is determined that the account has failed the evaluation, and the account to be evaluated is marked.

4. The method according to claim 3, characterized in that: At the time of obtaining the activation of the account to be evaluated, the method further includes: When the time from the activation time to the current time is outside the preset time range, the key information of the account to be evaluated is replaced with the preset key information, and the account to be evaluated is marked.

5. The method according to claim 1, characterized in that The step of determining a risk assessment strategy that matches the account to be assessed based on the account type of the account to be assessed includes: In the case that the account to be evaluated is a platform access account, a risk assessment strategy matching the account to be evaluated is determined, wherein the risk assessment strategy includes an account status rule.

6. The method according to claim 5, characterized in that The acquiring target data matching the risk assessment rule from the account data, and determining that the account passes the assessment when the target data meets the risk assessment indicator, includes: In the case where the risk assessment rule includes an account status rule, obtaining account status data of the account to be assessed; When the account status data corresponds to account deactivation, it is determined that the account to be evaluated has failed the evaluation, and the account to be evaluated is deleted.

7. A risk assessment device for an account, characterized in that: The device is applied to a terminal, and the terminal calls resources through a target network service platform. The device includes: An acquisition module, configured to, in response to receiving an account detection instruction, call an interface of the target network service platform to acquire the account to be evaluated and the account data corresponding to the account to be evaluated; A determination module, configured to determine a risk assessment strategy matching the account to be assessed according to the account usage type of the account to be assessed, wherein the risk assessment strategy includes risk assessment rules and risk assessment indicators corresponding to the risk assessment rules; The evaluation module is used to obtain target data matching the risk evaluation rule from the account data, and determine that the account has passed the evaluation if the target data meets the risk evaluation index.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.

9. 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 method according to any one of claims 1 to 6 are implemented.

10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

Images