Method and system for constructing risk prevention and control system based on enterprise digital transformation

Abstract

This application pertains to the technical field of enterprise data analysis and provides a method and system for constructing a risk prevention and control system based on enterprise digital transformation. The method involves first acquiring multiple access request information and access permission information, then generating authentication result information based on this. If the total number of authentication failures exceeds a conventional threshold, risk event information is generated. This application can promptly detect abnormal behavior during monitoring periods, such as a large number of users attempting unauthorized access to the power supply bureau's core system data. It accurately identifies potential risk events such as privilege abuse, brute-force attacks, internal personnel violations, or external penetration attacks. It provides real-time alerts and decision support for security management personnel, facilitating rapid deployment of countermeasures and effectively preventing the leakage of sensitive electricity consumption information, power grid operating parameters, and user privacy data. This significantly enhances the reliability and proactive defense capabilities of the power supply bureau's data security risk prevention and control system.

Description

Technical Field

[0001] This application relates to the technical field of enterprise data analysis, and more specifically, to a method and system for constructing a risk prevention and control system based on enterprise digital transformation. Background Technology

[0002] The core value of enterprises implementing digital transformation lies in improving operational efficiency through systematic integration and process restructuring. However, with the high concentration of data assets and the generalization of circulation boundaries, the data exposure surface and attack vectors have expanded significantly, making data security a fundamental condition that must be prioritized and guaranteed during the transformation process.

[0003] Furthermore, the power supply bureau's data is highly sensitive. If its core infrastructure operation data and user electricity consumption information are leaked, it will not only involve trade secrets and personal privacy, but may also be maliciously used to probe system vulnerabilities, thereby triggering a chain of power outages and directly threatening public safety and social stability.

[0004] Currently, the security management of power supply bureau data typically adopts a role-based access control model, which isolates users and data resources through permission division. However, this model mainly relies on statically configured permission policies, making it difficult to identify specific potential threats, which is not conducive to building a closed-loop dynamic defense architecture and has low reliability issues, requiring further improvement. Summary of the Invention

[0005] Based on this, embodiments of this application provide a method and system for constructing a risk prevention and control system based on enterprise digital transformation, in order to solve the problem of low reliability in the prior art.

[0006] In a first aspect, embodiments of this application provide a method for constructing a risk prevention and control system based on enterprise digital transformation, the method comprising: Based on a preset monitoring time period, obtain access request information and access permission information for multiple users to be categorized. For each of the users to be classified: Based on the required permission information corresponding to the access permission information and access request information, generate authentication result information, wherein the authentication result information includes authentication pass information or authentication failure information; If the total number of authentication failures exceeds a preset threshold, a risk event is generated.

[0007] Compared with existing technologies, the beneficial effects are as follows: The risk prevention and control system construction method based on enterprise digital transformation provided in this application embodiment allows the terminal device to continuously acquire access request information and access permission information corresponding to multiple users to be classified during the monitoring period. Then, the operation is performed for each user to be classified: based on the required permission information corresponding to the access permission information and access request information, authentication result information is effectively generated; if the total number of authentication failure information is greater than the normal threshold information, risk event information is accurately generated, thereby enabling timely detection of abnormal behavior of a large number of users attempting to access data without authorization during the monitoring period, accurately identifying potential risk events such as permission abuse, brute-force attacks, or internal threats, providing real-time alarms and decision support for security management personnel, facilitating rapid response measures, significantly enhancing the reliability of the risk prevention and control system, and to a certain extent solving the problem of low reliability currently.

[0008] Secondly, embodiments of this application provide a risk prevention and control system construction system based on enterprise digital transformation, the system comprising: Access Request Information Acquisition Module: Used to acquire access request information and access permission information for multiple users to be categorized based on a preset monitoring time period; Authentication result information generation module: used to generate authentication result information for each of the users to be classified, based on the required permission information corresponding to the access permission information and access request information, wherein the authentication result information includes authentication pass information or authentication failure information; Risk event information generation module: used to generate risk event information if the total number of authentication failures exceeds a preset threshold.

[0009] Thirdly, embodiments of this application provide a terminal device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the method described in the first aspect above.

[0010] Fourthly, embodiments of this application provide a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of the method described in the first aspect above.

[0011] It is understood that the beneficial effects of the second to fourth aspects mentioned above can be found in the relevant descriptions in the first aspect mentioned above, and will not be repeated here. Attached Figure Description

[0012] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments or the prior art will be briefly introduced below.

[0013] Figure 1 This is a flowchart illustrating a method for constructing a risk prevention and control system according to an embodiment of this application; Figure 2 This is a flowchart illustrating step S200 in a risk prevention and control system construction method provided in an embodiment of this application; Figure 3 This is a flowchart illustrating the process after step S230 in a risk prevention and control system construction method provided in an embodiment of this application; Figure 4 This is a flowchart illustrating the process after step S270 in a risk prevention and control system construction method provided in an embodiment of this application; Figure 5 This is a flowchart illustrating the process after step S300 in a risk prevention and control system construction method provided in an embodiment of this application; Figure 6 This is a block diagram of a risk prevention and control system construction system provided in an embodiment of this application; Figure 7 This is a schematic diagram of a terminal device provided in an embodiment of this application. Detailed Implementation

[0014] In the following description, specific details such as particular system architectures and techniques are set forth for illustrative purposes and not for limitation, in order to provide a thorough understanding of the embodiments of this application. However, those skilled in the art will understand that this application may also be implemented in other embodiments without these specific details. In other instances, detailed descriptions of well-known systems, apparatuses, circuits, and methods have been omitted so as not to obscure the description of this application with unnecessary detail.

[0015] In the description of this application and the appended claims, the terms "first," "second," "third," etc., are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.

[0016] References to "one embodiment" or "some embodiments" as described in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.

[0017] To illustrate the technical solution described in this application, specific embodiments are provided below.

[0018] Please see Figure 1 , Figure 1 This is a flowchart illustrating the method for constructing a risk control system based on enterprise digital transformation, as provided in this embodiment. In this embodiment, the executing entity of the risk control system construction method is a terminal device. It is understood that the types of terminal devices include, but are not limited to, tablet computers, laptops, Ultra-Mobile Personal Computers (UMPCs), netbooks, Personal Digital Assistants (PDAs), etc., and this embodiment does not impose any restrictions on the specific type of terminal device.

[0019] Please see Figure 1 The risk prevention and control system construction method provided in this application includes, but is not limited to, the following steps: In S100, based on a preset monitoring time period, access request information and access permission information corresponding to multiple users to be classified are obtained.

[0020] Specifically, the terminal device can first obtain access request information and access permission information for multiple users to be classified based on a preset monitoring time period. The specific duration of the monitoring time period can be predefined by the security administrator, such as 1 hour, 3 hours, or 6 hours. The users to be classified are used to describe users who request access to any type of enterprise data in the power supply bureau's database. The access request information is used to describe the access operation initiated by the users to be classified for a certain type of enterprise data. The access permission information is used to describe the access permissions granted to the users to be classified.

[0021] In S200, for each user to be classified: based on the required permission information corresponding to the access permission information and access request information, authentication result information is generated.

[0022] Specifically, after the terminal device obtains the access request information and access permission information, the terminal device can perform this process for each user to be classified: based on the required permission information corresponding to the access permission information and access request information, quickly generate authentication result information, which includes authentication pass information or authentication failure information. Authentication pass information is used to describe that the user to be classified has passed the permission authentication, and authentication failure information is used to describe that the user to be classified has failed the permission authentication.

[0023] In S300, if the total number of authentication failure messages exceeds the preset threshold for normal number of failures, risk event information is generated.

[0024] Specifically, if the total number of authentication failure messages exceeds the preset threshold, the terminal device can effectively generate risk event information, thereby promptly identifying abnormal behavior such as a large number of users attempting to access data without authorization during the monitoring period. This effectively captures potential risk events such as privilege abuse, brute-force attacks, or internal threats, providing real-time alerts and decision-making basis for security managers. This, in turn, facilitates rapid response measures and significantly improves the reliability and proactive defense capabilities of the risk prevention and control system.

[0025] For some possible implementations, please refer to [link to relevant documentation] for information on effectively generating authentication result information. Figure 2 Step S200 includes, but is not limited to, the following steps: In S210, for each user to be classified: compare the required permission information corresponding to the access permission information and access request information.

[0026] Specifically, the terminal device can perform this process for each user to be classified: comparing the required permission information with the access request information, whereby the required permission information describes the permission conditions required to satisfy the access request information; both the access permission information and the required permission information can be predefined by security administrators; the access permission information and the required permission information can be collection permissions, storage permissions, usage permissions, transmission permissions, and / or destruction permissions; collection permissions control whether a user can write or input data into the system; usage permissions control whether a user can query, calculate, or analyze data; transmission permissions control whether a user can transmit data over the network; and destruction permissions control whether a user can delete or destroy data.

[0027] In S220, if the access permission information is equal to the required permission information corresponding to the access request information, then the authentication result information is determined to be authentication passed information.

[0028] Specifically, if the access permission information equals the required permission information corresponding to the access request information, for example, if both the access permission information and the required permission information are usage permissions, then the terminal device can determine that the authentication result information is authentication passed. In S230, if the access permission information is not equal to the required permission information corresponding to the access request information, the authentication result information is determined to be authentication failure information.

[0029] Specifically, if the access permission information is not equal to the required permission information corresponding to the access request information, for example, the required permission information is usage permission, but the access permission information does not include usage permission, then the terminal device can determine that the authentication result information is authentication failure information.

[0030] In some possible implementations, to facilitate the rapid identification of users with relatively high risk and to enable subsequent targeted countermeasures for those users, please refer to [link / reference needed]. Figure 3 After step S230, the method further includes, but is not limited to, the following steps: In S240, based on the authentication failure information, the user to be classified is identified as the target user.

[0031] Specifically, after the terminal device determines the authentication failure information, it can identify the user to be classified as the target user based on the authentication failure information, thereby filtering out all users who failed authentication within the monitoring period. The target user is used to describe the user to be classified who triggered the authentication failure information among all users to be classified.

[0032] In S250, information on the number of individual failures of a target user is obtained based on the monitoring time period.

[0033] Specifically, after the terminal device identifies the target user, it can obtain the individual failure count information of the target user based on the monitoring time period. The individual failure count information describes the total number of times the target user has triggered authentication failure information during the monitoring time period.

[0034] In S260, the individual failure count information is compared with the preset individual failure count threshold information.

[0035] Specifically, after the terminal device obtains the individual failure count information, it can compare the individual failure count information with the preset individual failure count threshold information. The specific value of the individual failure count threshold information can be predefined by the security administrator, such as 5 times, 10 times, or 15 times.

[0036] In S270, if the number of failures of an individual is greater than the threshold information of the number of failures of an individual, then the target user is identified as a core risk user.

[0037] Specifically, if the number of individual failures exceeds the threshold information, the terminal device can identify the target user as a core risk user, thereby identifying the higher-risk user among all users who have triggered authentication failure information.

[0038] For a more in-depth analysis of core risk users, please refer to the following information regarding some possible implementation methods. Figure 4 After step S270, the method further includes, but is not limited to, the following steps: In S280, information on the first failed access request set corresponding to multiple historical risk users and information on the second failed access request set of core risk users are obtained.

[0039] Specifically, after the terminal device identifies core risk users, it can obtain first failed access request set information corresponding to multiple historical risk users and second failed access request set information for core risk users. The machine density level information includes high-level and medium-level information, with high-level information describing a high machine density level and medium-level information describing a medium machine density level. Historical risk users describe users who have historically triggered authentication failures and posed a significant risk; these historical risk users could be other core risk users from the past. The first failed access request set information includes multiple first failed access request messages and their corresponding machine density level information, describing data where historical risk users attempted to initiate access but lacked permission. The second failed access request set information includes multiple second failed access request messages and their corresponding machine density level information, describing data where core risk users attempted to initiate access but lacked permission.

[0040] In S290, based on the machine density level information in descending order, multiple first failed access request information are sorted to generate first access table information, and multiple second failed access request information are sorted to generate second access table information.

[0041] Specifically, after the terminal device obtains the first failed access request set information and the second failed access request set information, the terminal device can sort the multiple first failed access request information according to the machine density level information from high to low, that is, from high density level information to medium density level information, to generate first access table information. At the same time, it can sort the multiple second failed access request information according to the machine density level information from high to low, to generate second access table information.

[0042] In S291, the information in the first access table and the information in the second access table are compared.

[0043] Specifically, after the terminal device generates the first access table information and the second access table information, the terminal device can compare the first access table information and the second access table information.

[0044] In S292, if there are a specified number of second failed access request messages in the second access table that are the same as the first failed access request messages in the first access table, and the first three second failed access request messages in the second access table are the same as the first three first failed access request messages in the first access table, then associated tag information is generated based on the core risk user.

[0045] Specifically, if the second access table contains a specified number of second failed access request messages that are identical to the first failed access request messages in the first access table, and the first three second failed access request messages in the second access table are identical to the first three first failed access request messages in the first access table, it indicates that the behavior of the core risk user is highly similar to that of the historical risk user. Therefore, the terminal device can generate associated tag information based on the core risk user. The associated tag information is used to describe the tags that associate the core risk user with the historical risk user.

[0046] In some possible implementations, to facilitate remote analysis of core risk users by security administrators, please refer to [link / reference needed]. Figure 5 After step S300, the method further includes, but is not limited to, the following steps: In S400, basic user information of historically risky users is obtained based on associated tag information.

[0047] Specifically, after the terminal device generates risk event information, the terminal device can obtain basic user information corresponding to historical risk users associated with core risk users based on the associated tag information. The basic user information includes account name information, user ID information, historical access record information, sensitive operation record information, creation time information, last login time information, and lockout reason information.

[0048] In S410, auxiliary analysis data packet information is generated based on risk event information, basic user information, and the second failed access request set information of core risk users.

[0049] Specifically, after the terminal device obtains basic user information, it can effectively generate auxiliary analysis data packet information based on risk event information, basic user information, and the second failed access request set information of core risk users. The auxiliary analysis data packet information is used to assist security managers in analyzing core risk users, and it is a data set of risk event information, basic user information, and the second failed access request set information.

[0050] In the S420, auxiliary analysis data packets are sent to the designated cloud server.

[0051] Specifically, after the terminal device generates auxiliary analysis data packet information, the terminal device can send the auxiliary analysis data packet information to the designated cloud server.

[0052] The implementation principle of the risk prevention and control system construction method based on enterprise digital transformation in this application embodiment is as follows: The terminal device can first continuously obtain access request information and access permission information corresponding to multiple users to be classified based on the monitoring time period, and then perform the following processing for each user to be classified: According to the required permission information corresponding to the access permission information and access request information, authentication result information is quickly generated. If the total number of authentication failure information is greater than the normal number threshold information, risk event information is effectively generated, thereby realizing the timely detection of abnormal behavior of a large number of users attempting to access data without authorization during the monitoring period, accurately identifying potential risk events such as permission abuse, brute force attack or internal threats, providing real-time alarms and decision support for security management personnel, which is conducive to the rapid deployment of countermeasures and significantly enhances the reliability and defense capability of the risk prevention and control system.

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

[0054] Embodiments of this application also provide a risk prevention and control system construction system based on enterprise digital transformation. For ease of explanation, only the parts relevant to this application are shown, such as... Figure 6 As shown, the system 60 includes: Access Request Information Acquisition Module 61: Used to acquire access request information and access permission information for multiple users to be classified based on a preset monitoring time period; Authentication result information generation module 62: For each user to be classified, it generates authentication result information based on the required permission information corresponding to the access permission information and access request information. The authentication result information includes authentication pass information or authentication failure information. Risk event information generation module 63: Used to generate risk event information if the total number of authentication failures exceeds a preset threshold for normal occurrences.

[0055] Optionally, the authentication result information generation module 62 mentioned above includes: Access permission information comparison submodule: Used to compare the required permission information with the access request information for each user to be classified. The authentication pass information determination submodule is used to determine the authentication result information as authentication pass information if the access permission information is equal to the required permission information corresponding to the access request information. The authentication failure information determination submodule is used to determine the authentication result as authentication failure information if the access permission information is not equal to the required permission information corresponding to the access request information.

[0056] Optionally, the system 60 also includes: Target user identification module: used to identify users to be classified as target users based on authentication failure information; Individual Failure Count Information Acquisition Module: Used to acquire individual failure count information of target users based on the monitoring time period; Individual failure count comparison module: used to compare individual failure count information with preset individual failure count threshold information; Core Risk User Identification Module: This module identifies a target user as a core risk user if the number of failures of an individual exceeds the individual's failure threshold.

[0057] Optionally, the system 60 also includes: Failed access request set information acquisition module: used to acquire first failed access request set information corresponding to multiple historical risk users and second failed access request set information for core risk users. The first failed access request set information includes multiple first failed access request information and machine density level information corresponding to each first failed access request information. The second failed access request set information includes multiple second failed access request information and machine density level information corresponding to each second failed access request information. The machine density level information includes high density level information and medium density level information. Access table information generation module: It is used to sort multiple first failed access request information according to the machine density level information from high to low to generate first access table information, and sort multiple second failed access request information to generate second access table information. Access table information comparison module: used to compare the first access table information and the second access table information; The associated tag information generation module is used to generate associated tag information based on the core risk user if there are a specified number of second failed access request information in the second access table information that are the same as the first failed access request information in the first access table information, and the first three second failed access request information in the second access table information are the same as the first three first failed access request information in the first access table information. The associated tag information is used to describe the tag that associates the core risk user with the historical risk user.

[0058] Optionally, the system 60 also includes: Basic User Information Acquisition Module: Used to acquire basic user information of historically risky users based on associated tag information; The auxiliary analysis data packet information generation module is used to generate auxiliary analysis data packet information based on risk event information, basic user information, and the second failed access request set information of core risk users. Assisted analysis data packet information sending module: used to send auxiliary analysis data packet information to the specified cloud server.

[0059] It should be noted that the information interaction and execution process between the above modules are based on the same concept as the method embodiments of this application. For details on their specific functions and technical effects, please refer to the method embodiments section, and they will not be repeated here.

[0060] This application also provides a terminal device, such as... Figure 7 As shown, the terminal device 70 in this embodiment includes: a processor 71, a memory 72, and a computer program 73 stored in the memory 72 and executable on the processor 71. When the processor 71 executes the computer program 73, it implements the steps described in the above-described risk prevention and control system construction method embodiment, for example... Figure 1 Steps S100 to S300 are shown; or, when processor 71 executes computer program 73, it implements the functions of each module in the above-described device, for example... Figure 6 The functions of modules 61 to 63 are shown.

[0061] The terminal device 70 can be a desktop computer, laptop, handheld computer, cloud server, or other computing device, and includes, but is not limited to, a processor 71 and a memory 72. Those skilled in the art will understand that... Figure 7 This is merely an example of terminal device 70 and does not constitute a limitation on terminal device 70. It may include more or fewer components than shown, or combine certain components, or different components. For example, terminal device 70 may also include input / output devices, network access devices, buses, etc.

[0062] The processor 71 can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.; the general-purpose processor can be a microprocessor or any conventional processor, etc.

[0063] The memory 72 can be an internal storage unit of the terminal device 70, such as the hard disk or memory of the terminal device 70. The memory 72 can also be an external storage device of the terminal device 70, such as a plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, etc., equipped on the terminal device 70. Furthermore, the memory 72 can include both internal storage units and external storage devices of the terminal device 70. The memory 72 can also store computer program 73 and other programs and data required by the terminal device 70. The memory 72 can also be used to temporarily store data that has been output or will be output.

[0064] One embodiment of this application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, can implement the steps of the various method embodiments described above. The computer program includes computer program code, which can be in the form of source code, object code, executable file, or some intermediate form. The computer-readable medium can include any entity or device capable of carrying computer program code, a recording medium, a USB flash drive, a portable hard drive, a magnetic disk, an optical disk, a computer memory, a read-only memory (ROM), a random access memory (RAM), an electrical carrier signal, a telecommunication signal, and a software distribution medium, etc.

[0065] The above are all preferred embodiments of this application, and are not intended to limit the scope of protection of this application. Therefore, all equivalent changes made in accordance with the methods, principles and structures of this application should be covered within the scope of protection of this application.

Claims

1. A risk prevention and control system construction method based on enterprise digital transformation, characterized by, The method includes: Based on a preset monitoring time period, obtain access request information and access permission information for multiple users to be categorized. For each of the users to be classified: Based on the required permission information corresponding to the access permission information and access request information, generate authentication result information, wherein the authentication result information includes authentication pass information or authentication failure information; If the total number of authentication failures exceeds a preset threshold, a risk event is generated.

2. The method of claim 1, wherein, For each of the users to be classified: based on the required permission information corresponding to the access permission information and access request information, authentication result information is generated, including: For each user to be classified: compare the required permission information corresponding to the access permission information and access request information; If the access permission information is equal to the required permission information corresponding to the access request information, then the authentication result information is determined to be authentication passed information; If the access permission information is not equal to the required permission information corresponding to the access request information, then the authentication result information is determined to be authentication failure information.

3. The method of claim 2, wherein, After determining that the authentication result information is authentication failure information if the access permission information is not equal to the required access permission information corresponding to the access request information, the method further includes: Based on the authentication failure information, the user to be classified is determined to be the target user; Based on the monitoring time period, obtain the individual failure count information of the target user; Compare the individual failure count information with the preset individual failure count threshold information; If the number of failures of an individual is greater than the threshold number of failures for an individual, then the target user is determined to be a user with core risk.

4. The method according to claim 3, characterized in that, After determining that the target user is a core risk user if the number of individual failures exceeds the individual failure threshold, the method further includes: Obtain first failed access request set information corresponding to multiple historical risk users and second failed access request set information of the core risk users. The first failed access request set information includes multiple first failed access request information and machine density level information corresponding to each first failed access request information. The second failed access request set information includes multiple second failed access request information and machine density level information corresponding to each second failed access request information. The machine density level information includes high density level information and medium density level information. Based on the machine density level information in descending order, multiple first failed access request information are sorted to generate first access table information, and multiple second failed access request information are sorted to generate second access table information. Compare the information in the first access table and the information in the second access table; If the second access table information contains a specified number of second failed access request information that are the same as the first failed access request information in the first access table information, and the first three second failed access request information in the second access table information are the same as the first three first failed access request information in the first access table information, then according to the core risk user, associated tag information is generated, wherein the associated tag information is used to describe the tag that associates the core risk user and the historical risk user.

5. The method according to claim 4, characterized in that, After generating risk event information if the total number of authentication failures exceeds a preset threshold, the method further includes: Based on the associated tag information, obtain the basic user information of the historical risk users; Based on the risk event information, the basic user information, and the second failed access request set information of the core risk users, auxiliary analysis data packet information is generated; Send the auxiliary analysis data packet information to the designated cloud server.

6. A risk prevention and control system construction system based on enterprise digital transformation, characterized in that, The system includes: Access Request Information Acquisition Module: Used to acquire access request information and access permission information for multiple users to be categorized based on a preset monitoring time period; Authentication result information generation module: used to generate authentication result information for each of the users to be classified, based on the required permission information corresponding to the access permission information and access request information, wherein the authentication result information includes authentication pass information or authentication failure information; Risk event information generation module: used to generate risk event information if the total number of authentication failures exceeds a preset threshold.

7. The system according to claim 6, characterized in that, The authentication result information generation module includes: Access permission information comparison submodule: used to compare the required permission information corresponding to the access permission information and access request information for each of the users to be classified; The authentication pass information determination submodule is used to determine the authentication result information as authentication pass information if the access permission information is equal to the required permission information corresponding to the access request information. The authentication failure information determination submodule is used to determine the authentication result information as authentication failure information if the access permission information is not equal to the required permission information corresponding to the access request information.

8. A terminal device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the steps of the method as described in any one of claims 1 to 5.

9. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method as described in any one of claims 1 to 5.

Images