Personnel list information management method and device, computer equipment and storage medium

Abstract

The invention relates to a personnel list information management method and device, computer equipment and a storage medium, and relates to the technical field of information management. The method comprises the steps of determining personnel data corresponding to a to-be-processed person in a preset database based on the to-be-processed person contained in a personnel management command; the preset database comprises a white list database and a black list database; based on an instruction type corresponding to the personnel management command, processing the personnel data to obtain processed personnel data; the instruction types comprise an access control instruction, a list updating instruction, a system integration instruction and an analysis and monitoring instruction; wherein the access control instruction is used for determining resources which can be accessed by the to-be-processed personnel; the list updating instruction is used for maintaining personnel data of to-be-processed personnel in a preset database; the system integration instruction is used for associating the personnel data in the preset database with the target system. By adopting the method, the personnel list information management accuracy can be improved.

Description

Technical Field

[0001] The present application relates to the field of information management technology, and in particular to a method, apparatus, computer equipment, storage medium and computer program product for managing personnel list information. Background Art

[0002] In order to strengthen the safety construction of infrastructure and implement the management requirements of infrastructure, the smart engineering system needs to meet the management needs of safety inspections on infrastructure construction sites. Among them, the management needs of safety inspections include functions such as input, processing and query of infrastructure-related personnel, as well as the association of personnel lists with other engineering modules, data security, and authority management.

[0003] At present, the related technology usually adopts a manual processing method to manually manage the personnel list information one by one, and the personnel list information can be manually added, modified or deleted in the list library. This method is prone to omissions or errors when managing the personnel list, resulting in insufficient accuracy in the management of the personnel list information. Summary of the invention

[0004] Based on this, it is necessary to provide a method, device, computer equipment, computer-readable storage medium and computer program product that can improve the accuracy of personnel list information management in response to the above technical problems.

[0005] In a first aspect, the present application provides a method for managing personnel list information. The method comprises:

[0006] Based on the personnel to be processed contained in the personnel management command, determine the personnel data corresponding to the personnel to be processed in a preset database; the personnel data includes entity information, attribute information and violation information; the preset database includes a whitelist database and a blacklist database;

[0007] Based on the instruction type corresponding to the personnel management command, the personnel data is processed to obtain processed personnel data; the instruction type includes access control instructions, list update instructions, system integration instructions, and analysis and monitoring instructions;

[0008] Among them, the access control instructions are used to determine the resources accessible to the personnel to be processed; the list update instructions are used to maintain the personnel data of the personnel to be processed in the preset database; the system integration instructions are used to associate the personnel data in the preset database with the target system; the analysis and monitoring instructions are used to monitor the behavior of the personnel to be processed by analyzing the data, and send an alarm when the personnel to be processed behave abnormally; the analysis data is determined based on the historical data of each of the personnel.

[0009] In one embodiment, the whitelist database includes a whitelist entity table and a whitelist attribute table; the blacklist database includes a blacklist entity table and a violation behavior table;

[0010] The step of determining personnel data corresponding to the personnel to be processed in a preset database based on the personnel to be processed contained in the personnel management command includes:

[0011] If the person to be processed is in the whitelist database, then obtaining the entity information of the person to be processed in the whitelist entity table; the entity information includes an identifier, a name and a role; and obtaining the attribute information of the person to be processed in the whitelist attribute table;

[0012] If the person to be processed is in the blacklist database, the entity information of the person to be processed is obtained in the blacklist entity table; the violation information of the person to be processed is obtained in the violation table; the violation information includes the violation type, violation time and violation details.

[0013] In one embodiment, the processing of the personnel data based on the instruction type corresponding to the personnel management command to obtain the processed personnel data includes:

[0014] In the case where the instruction type is an access control instruction, the access rights corresponding to the attribute information in the whitelist database are updated according to the permission data in the access control instruction to obtain updated personnel data; or

[0015] According to the permission data in the access control instruction, the access rights corresponding to the entity information in the whitelist database are updated to obtain updated personnel data; or

[0016] The access control list in the access control instruction is added to the personnel data in the whitelist database to obtain updated personnel data; the access control list includes access rights between each person and each resource in the whitelist database.

[0017] In one embodiment, the processing of the personnel data based on the instruction type corresponding to the personnel management command to obtain the processed personnel data includes:

[0018] In the case where the instruction type is an access control instruction, the interception authority corresponding to the entity information in the blacklist database is updated according to the permission data in the access control instruction to obtain updated personnel data; the interception authority is used to determine whether the personnel in the blacklist database are blocked from accessing resources, and to determine the corresponding interception strategy when blocking access; the interception strategy includes a cut-off strategy and an alarm strategy.

[0019] In one embodiment, the processing of the personnel data based on the instruction type corresponding to the personnel management command to obtain the processed personnel data includes:

[0020] In the case where the instruction type is a list update instruction, and the person to be processed is in the whitelist database, an update operation is performed on the entity information and attribute information of the person to be processed based on the list update instruction to obtain updated personnel data; the update operation includes adding, deleting and updating;

[0021] In the case where the instruction type is a list update instruction, and the person to be processed is in the blacklist database, determining the appeal review result of the person to be processed in the list update instruction;

[0022] When the appeal review result is approved, the entity information and violation information corresponding to the person to be processed in the blacklist database are removed through the list update instruction to obtain the processed personnel data.

[0023] In one embodiment, the processing of the personnel data based on the instruction type corresponding to the personnel management command to obtain the processed personnel data includes:

[0024] In the case where the instruction type is a system integration instruction, determining a data interface matching the target system;

[0025] The whitelist database and the blacklist database are linked to the target system respectively through the data interface, so that the target system calls the personnel data in the whitelist database and the blacklist database.

[0026] In one embodiment, the whitelist database further includes an access log table; the blacklist database further includes a blacklist history table;

[0027] The processing of the personnel data based on the instruction type corresponding to the personnel management command to obtain the processed personnel data includes:

[0028] When the instruction type is an analysis and monitoring instruction, the access records in the access log table and the violation records in the blacklist history table are analyzed in real time to obtain abnormal analysis results corresponding to the data of each person;

[0029] If the abnormal analysis result is abnormal, an alarm message corresponding to the abnormal analysis result is generated.

[0030] In a second aspect, the present application also provides a device for managing personnel list information. The device comprises:

[0031] A data determination module, for determining personnel data corresponding to the personnel to be processed in a preset database based on the personnel to be processed contained in the personnel management command; the personnel data includes entity information, attribute information and violation information; the preset database includes a whitelist database and a blacklist database;

[0032] An instruction execution module is used to process the personnel data based on the instruction type corresponding to the personnel management command to obtain the processed personnel data; the instruction types include access control instructions, list update instructions, system integration instructions, and analysis and monitoring instructions; wherein the access control instructions are used to determine the resources accessible to the personnel to be processed; the list update instructions are used to maintain the personnel data of the personnel to be processed in the preset database; the system integration instructions are used to associate the personnel data in the preset database with the target system; the analysis and monitoring instructions are used to monitor the behavior of the personnel to be processed by analyzing the data, and send an alarm when the personnel to be processed behave abnormally; the analysis data is determined based on the historical personnel data.

[0033] In a third aspect, the present application further provides a computer device. The computer device includes a memory and a processor, wherein the memory stores a computer program, and when the computer program is executed by the processor, the following steps are implemented:

[0034] Based on the personnel to be processed contained in the personnel management command, determine the personnel data corresponding to the personnel to be processed in a preset database; the personnel data includes entity information, attribute information and violation information; the preset database includes a whitelist database and a blacklist database;

[0035] Based on the instruction type corresponding to the personnel management command, the personnel data is processed to obtain processed personnel data; the instruction type includes access control instructions, list update instructions, system integration instructions, and analysis and monitoring instructions;

[0036] Among them, the access control instructions are used to determine the resources accessible to the personnel to be processed; the list update instructions are used to maintain the personnel data of the personnel to be processed in the preset database; the system integration instructions are used to associate the personnel data in the preset database with the target system; the analysis and monitoring instructions are used to monitor the behavior of the personnel to be processed by analyzing the data, and send an alarm when the personnel to be processed behave abnormally; the analysis data is determined based on the historical data of each of the personnel.

[0037] In a fourth aspect, the present application further provides a computer-readable storage medium. The computer-readable storage medium stores a computer program, which, when executed by a processor, implements the following steps:

[0038] Based on the personnel to be processed contained in the personnel management command, determine the personnel data corresponding to the personnel to be processed in a preset database; the personnel data includes entity information, attribute information and violation information; the preset database includes a whitelist database and a blacklist database;

[0039] Based on the instruction type corresponding to the personnel management command, the personnel data is processed to obtain processed personnel data; the instruction type includes access control instructions, list update instructions, system integration instructions, and analysis and monitoring instructions;

[0040] Among them, the access control instructions are used to determine the resources accessible to the personnel to be processed; the list update instructions are used to maintain the personnel data of the personnel to be processed in the preset database; the system integration instructions are used to associate the personnel data in the preset database with the target system; the analysis and monitoring instructions are used to monitor the behavior of the personnel to be processed by analyzing the data, and send an alarm when the personnel to be processed behave abnormally; the analysis data is determined based on the historical data of each of the personnel.

[0041] In a fifth aspect, the present application further provides a computer program product, including a computer program, which implements the following steps when executed by a processor:

[0042] Based on the personnel to be processed contained in the personnel management command, determine the personnel data corresponding to the personnel to be processed in a preset database; the personnel data includes entity information, attribute information and violation information; the preset database includes a whitelist database and a blacklist database;

[0043] Based on the instruction type corresponding to the personnel management command, the personnel data is processed to obtain processed personnel data; the instruction type includes access control instructions, list update instructions, system integration instructions, and analysis and monitoring instructions;

[0044] Among them, the access control instructions are used to determine the resources accessible to the personnel to be processed; the list update instructions are used to maintain the personnel data of the personnel to be processed in the preset database; the system integration instructions are used to associate the personnel data in the preset database with the target system; the analysis and monitoring instructions are used to monitor the behavior of the personnel to be processed by analyzing the data, and send an alarm when the personnel to be processed behave abnormally; the analysis data is determined based on the historical data of each of the personnel.

[0045] The above-mentioned personnel list information management method, device, computer equipment, storage medium and computer program product obtain a personnel management command and determine the personnel data corresponding to the personnel to be processed in a preset database composed of a blacklist database and a whitelist database based on the personnel to be processed contained in the personnel management command. The personnel data may include entity information, attribute information and violation information of each person. Afterwards, according to the instruction type of the personnel management command, the personnel data is managed and processed accordingly to obtain the processed personnel data. The instruction type may include access control instructions, list update instructions, system integration instructions, and analysis and monitoring instructions. The above-mentioned instruction types can manage personnel data in terms of access rights of personnel to be processed, personnel lists in a preset database, systems associated with the preset database, and behavior monitoring of personnel to be processed, thereby avoiding omissions and errors in the list of management personnel and improving the accuracy of personnel list information management. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0047] FIG1 is a diagram of an application environment of a method for managing personnel list information in one embodiment;

[0048] FIG2 is a schematic flow chart of a method for managing personnel list information in one embodiment;

[0049] FIG3 is a schematic diagram of a flow chart of steps for processing personnel data in one embodiment;

[0050] FIG4 is a schematic flow chart of steps for processing personnel data in another embodiment;

[0051] FIG5 is a block diagram of a device for managing personnel list information in one embodiment;

[0052] FIG. 6 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0053] 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.

[0054] The management method of personnel list information provided in the embodiment of the present application can be applied to the application environment as shown in Figure 1. Among them, the terminal 102 communicates with the server 104 through the network. The terminal 102 can send a personnel management command to the server 104, so that the server 104 determines the personnel data corresponding to the personnel to be processed based on the personnel management command in the preset database in the data storage system. The data storage system can store the data that the server 104 needs to process. The data storage system can be integrated on the server 104, or it can be placed on the cloud or other network servers. After the server 104 determines the personnel data, it can perform management processes of different functions on the personnel data according to the instruction type of the personnel management command, thereby processing the personnel data and obtaining the processed personnel data. For example, the instruction type may include access control instructions, list update instructions, system integration instructions, and analysis and monitoring instructions. For different types of instructions, the specific processing process of the personnel data is different, and the processed personnel data obtained is also different. The access control instruction is mainly used to change the access rights of the personnel to be processed in the personnel data to various resources; the list update instruction is mainly used to add, delete and modify the personnel lists corresponding to the white list database and the black list database in the preset database; the system integration instruction is mainly used to match the personnel to be processed with the target system so that the target system can directly use the personnel data corresponding to the personnel to be processed; the analysis and monitoring instruction is used to monitor the personnel to be processed, and when the behavior of the personnel to be processed is abnormal, the personnel data corresponding to the personnel to be processed is marked and an alarm message is sent to the terminal 102. In addition, after the terminal 102 completes the management of the personnel list information in the server 104, the terminal 102 can call the data in the preset database so that the managed personnel list information can support the system operation.

[0055] The terminal 102 may be, but is not limited to, various personal computers, laptops, smart phones, tablet computers, IoT devices, and portable wearable devices. The IoT devices may be smart speakers, smart TVs, smart air conditioners, smart car-mounted devices, etc. Portable wearable devices may be smart watches, smart bracelets, head-mounted devices, etc. The head-mounted devices may be virtual reality (VR) devices, augmented reality (AR) devices, smart glasses, etc. The server 104 may be implemented using an independent server or a server cluster consisting of multiple servers.

[0056] In an exemplary embodiment, as shown in FIG2 , a method for managing personnel list information is provided, which is described by taking the method applied to the server 104 in FIG1 as an example, and includes the following steps S202 to S204. Among them:

[0057] Step S202: based on the personnel to be processed included in the personnel management command, determine the personnel data corresponding to the personnel to be processed in a preset database.

[0058] Among them, personnel data includes entity information, attribute information and violation information; the preset database includes a whitelist database and a blacklist database. Entity information may include custom fields such as the unique identification, name, description, and type of the person to be processed. For example, for entity information in the whitelist database, it may be information such as user ID, user name, user role type, etc. Attribute information may include management attributes of the person to be processed in the system, such as access rights, validity period of permissions, number of resource usages, etc. Violation information may include information such as the violation type, violation time, and violation details of the person to be processed in each violation data. The whitelist database is used to store whitelist users in the smart engineering system, and the blacklist database is used to store blacklist users in the smart engineering system.

[0059] Specifically, the server parses the personnel management command to determine the personnel to be processed contained in the personnel management command. For each person to be processed, according to the type of list to which the person to be processed belongs, a search is performed in the whitelist database or the blacklist database to determine the personnel data corresponding to the person to be processed. The list type can be a blacklist type and a whitelist type. If the personnel management command does not contain the list type of the person to be processed, a search is performed in the blacklist database and the whitelist database respectively to determine the personnel data corresponding to the person to be processed.

[0060] Optionally, the server may determine the personnel data corresponding to the instruction type according to the instruction type of the personnel management command. For example, if the instruction type is an analysis and monitoring instruction, the server may obtain access rights, access records, and violation information in the personnel data, thereby monitoring the personnel to be processed through the analysis and monitoring instruction. If the instruction type is a list update instruction, the server may obtain entity information and attribute information in the personnel data, thereby only updating the entity information and attribute information.

[0061] Step S204: Processing the personnel data based on the instruction type corresponding to the personnel management command to obtain processed personnel data.

[0062] Among them, the instruction types include access control instructions, list update instructions, system integration instructions, and analysis and monitoring instructions; access control instructions are used to determine the resources that the personnel to be processed can access; list update instructions are used to maintain the personnel data of the personnel to be processed in the preset database; system integration instructions are used to associate the personnel data in the preset database with the target system; analysis and monitoring instructions are used to monitor the behavior of the personnel to be processed by analyzing data and send alarms when the personnel to be processed perform abnormal behaviors; analysis data is determined based on historical personnel data. Resources can include equipment, systems, application APPs, etc.

[0063] Specifically, personnel management commands include multiple instruction types. When personnel management commands are of different instruction types, the processing of personnel data is also different. When the personnel management command is an access control instruction, the server can adjust the data related to authority control in the personnel data corresponding to the personnel to be processed, thereby updating the accessible resources of the personnel to be processed. When the personnel management command is a list update instruction, the server can update the personnel data in the whitelist database and the blacklist database, mainly adding, modifying and deleting the entity information and attribute information in the personnel data, thereby completing the addition, modification and deletion of the personnel to be processed.

[0064] For example, if the person to be processed is a person to be added to the whitelist, the server can create a storage space corresponding to the whitelist person in the white order database, and write the entity information and attribute information in the list update instruction into the storage space, thereby completing the addition of the whitelist person.

[0065] In the case where the personnel management command is a system integration command, after determining the personnel to be processed, the relationship data of the target system is added to the personnel data of each person to be processed to obtain the processed personnel data, so that the target system can call the personnel data of the person to be processed through the associated data. The target system can include various systems that need to use personnel list information, such as identity management systems, security protection systems, and business systems. In the case where the personnel management command is an analysis and monitoring command, the server can monitor the personnel to be processed, and the personnel data of the personnel to be processed will not be changed during the monitoring process. If the server determines that the person to be processed has abnormal behavior after analysis, the label corresponding to the abnormal behavior will be written into the personnel data of the person to be processed, thereby completing the processing of the person to be processed. Afterwards, the server can also send the alarm information of the person to be processed to each terminal. In the monitoring process, abnormal behavior analysis is performed based on the historical personnel data in the preset database to determine whether the person to be processed has abnormal behavior.

[0066] In the above-mentioned personnel list information management method, by obtaining a personnel management command and based on the personnel to be processed contained in the personnel management command, the personnel data corresponding to the personnel to be processed is determined in a preset database consisting of a blacklist database and a whitelist database. The personnel data may include entity information, attribute information and violation information of each person. Afterwards, according to the instruction type of the personnel management command, the personnel data is managed and processed accordingly to obtain the processed personnel data. The instruction type may include access control instructions, list update instructions, system integration instructions, and analysis and monitoring instructions. The above-mentioned instruction types can manage personnel data in terms of access rights of personnel to be processed, personnel lists in a preset database, systems associated with the preset database, and behavior monitoring of personnel to be processed, thereby avoiding omissions and errors in the list of management personnel and improving the accuracy of personnel list information management.

[0067] In an exemplary embodiment, the whitelist database includes a whitelist entity table and a whitelist attribute table, and the blacklist database includes a blacklist entity table and a violation behavior table. The specific implementation process of the step "determining the personnel data corresponding to the personnel to be processed in the preset database based on the personnel to be processed included in the personnel management command" includes:

[0068] If the person to be processed is in the whitelist database, the entity information of the person to be processed is obtained in the whitelist entity table; the attribute information of the person to be processed is obtained in the whitelist attribute table; if the person to be processed is in the blacklist database, the entity information of the person to be processed is obtained in the blacklist entity table; the violation information of the person to be processed is obtained in the violation table.

[0069] Among them, the whitelist database may include a whitelist entity table and a whitelist attribute table, and the whitelist entity table and the whitelist attribute table may be associated through a primary key. The blacklist database includes a blacklist entity table and a violation table, and the blacklist entity table and the violation table may be associated through a primary key. The primary key may be a unique identifier of a person. The whitelist entity table may be used to store entity information in the whitelist, the whitelist attribute table may be used to store attribute information in the whitelist, and the blacklist entity table may store blacklisted entity information. The violation table is used to record the violation of the blacklist entity. The violation information includes the violation type, violation time, and violation details. The entity information includes an identifier, a name, and a role.

[0070] Specifically, the server determines the preset database where the person to be processed is located. If the person to be processed is in the whitelist database, the whitelist entity table can be searched to obtain the entity information of the person to be processed. For example, the user ID, user name, user role type and other information of the person to be processed can be obtained. The attribute information of the person to be processed can also be determined in the whitelist attribute table according to the user ID. If the person to be processed is in the blacklist database, the blacklist entity table can be searched to obtain the entity information of the person to be processed. The violation information of the person to be processed can also be determined in the violation behavior table according to the user ID.

[0071] Optionally, the server can obtain the device data for the device entity in the personnel management command. The device data can also include entity information, attribute information and violation information. And the device data can also be stored in a preset database. For example, the server can obtain the device data corresponding to the device entity in the whitelist database. Obtain the device data corresponding to the device entity in the blacklist database. The device data in the blacklist entity table may include user ID, IP address, device serial number, etc. The device data in the violation behavior table may include the violation type, violation time and violation details of the device entity.

[0072] In this embodiment, through the whitelist entity table and whitelist attribute table of the whitelist database, and the blacklist entity table and violation table of the blacklist database, the entity information, attribute information, and violation information of the personnel to be processed can be obtained respectively, and the entity information, attribute information, and violation information of the device data can be obtained, which can increase the accuracy and efficiency of obtaining personnel data.

[0073] In an exemplary embodiment, as shown in FIG3 , the specific implementation process of the step of “processing personnel data based on the instruction type corresponding to the personnel management command to obtain processed personnel data” includes steps S302 to S306. Among them:

[0074] Step S302: When the instruction type is an access control instruction, the access rights corresponding to the attribute information in the whitelist database are updated according to the permission data in the access control instruction to obtain updated personnel data.

[0075] Specifically, each type of attribute information may have corresponding access rights with different resources. When the person to be processed contains attribute information with an access right relationship, the access rights of the person to be processed and different resources also correspond to the attribute information. For example, the server can determine whether the user to be processed can access the corresponding multiple devices based on the user's geographic location, access time, and access device type of the person to be processed. Based on this, when the server receives the access control instruction, it can modify the access rights corresponding to the attribute information of the person to be processed according to the permission data in the access control instruction. After the modification, the person to be processed can determine the accessible resources based on the attribute information.

[0076] Step S304, alternatively, according to the permission data in the access control instruction, the access rights corresponding to the entity information in the whitelist database are updated to obtain updated personnel data.

[0077] Specifically, in addition to modifying the access rights in the attribute information, the server can also directly modify the access rights corresponding to the user role type in the entity information. For example, for a certain user role type, all personnel to be processed in the system are determined, and the access rights corresponding to the user role type in the entity information are uniformly changed, thereby obtaining updated personnel data.

[0078] Step S306, alternatively, adding the access control list in the access control instruction to the personnel data in the whitelist database to obtain updated personnel data.

[0079] The access control list includes the access rights between each person and each resource in the whitelist database.

[0080] Specifically, the access control instruction may include multiple access control lists, and the access control list records the access permission data between the person to be processed and all resources. For each person to be processed, the server can write the access control list into the attribute information of the person to be processed. For example, the attribute information contains an access permission table, which records the permission level between the person to be processed and each resource. The server updates the permission level through the permission data in the access control instruction and obtains an updated access permission table.

[0081] In this embodiment, the personnel data of the personnel to be processed can be processed in a variety of ways through access control instructions, thereby changing the access rights of the personnel to be processed. The access rights of attribute information can be updated, the access rights of entity information can be updated, and an access control list can be created for each person to be processed, thereby improving the richness and flexibility of the control rights of managers at multiple levels.

[0082] In an exemplary embodiment, the specific implementation process of the step of "processing personnel data based on the instruction type corresponding to the personnel management command to obtain processed personnel data" includes:

[0083] In the case where the instruction type is an access control instruction, the interception authority corresponding to the entity information in the blacklist database is updated according to the authority data in the access control instruction to obtain updated personnel data.

[0084] Among them, the interception authority is used to determine whether the personnel in the blacklist database are blocked from accessing resources, and to determine the corresponding interception strategy when blocking access; the interception strategy includes the cut-off strategy and the alarm strategy.

[0085] Specifically, for the personnel data in the blacklist database, the personnel to be processed in the blacklist database usually record the resources that cannot interact with the personnel to be processed, as well as the interception permissions between the resources. If the personnel data corresponding to the access control instruction is the personnel data in the blacklist database, the entity information in the blacklist database and the interception permissions between the resources can be updated according to the permission data in the access control, so as to obtain the updated personnel data. At this time, when the server detects an access request sent by the terminal containing the personnel entity corresponding to the blacklist database, it can determine whether to cut off the connection between the terminal and the resource according to the interception permissions, or send an alarm to the terminal.

[0086] In this embodiment, the interception authority corresponding to the entity information in the blacklist database can be updated through the access control instruction, thereby adjusting the access rights of the blacklist entity, which can improve the richness and flexibility of the management personnel's control authority.

[0087] In an exemplary embodiment, as shown in FIG4 , the specific implementation process of the step of “processing personnel data based on the instruction type corresponding to the personnel management command to obtain processed personnel data” includes steps S402 to S406. Among them:

[0088] Step S402: When the instruction type is a list update instruction and the person to be processed is in the whitelist database, the entity information and attribute information of the person to be processed are updated based on the list update instruction to obtain updated personnel data.

[0089] Among them, update operations include adding, deleting and updating.

[0090] Specifically, determine the preset database to which the person to be processed contained in the list update instruction belongs. If the person to be processed is in the whitelist database, update the field corresponding to the person to be processed in the whitelist database, thereby completing the update of the entity information and attribute information of the person to be processed. Fields that do not need to be modified are not processed. The update operation can be an add, that is, adding a new person to be processed to the whitelist database. The update operation can be an update, and the personnel data of the person to be processed can be partially updated, for example, updating the attribute information of the person. The update operation can be a delete, that is, deleting the personnel data of the person to be processed.

[0091] Step S404, when the instruction type is a list update instruction and the person to be processed is in the blacklist database, determine the appeal review result of the person to be processed in the list update instruction.

[0092] Specifically, the appeal review result is the final result after the person to be processed in the blacklist database files an appeal to the system after being on the blacklist, and the reviewer reviews it. If the appeal review result is approved, the personnel data of the person to be processed will be removed from the blacklist. If the appeal review result is not approved, no action will be taken.

[0093] Step S406, when the appeal review result is approved, the entity information and violation information corresponding to the person to be processed in the blacklist database are removed through the list update instruction to obtain the processed person data.

[0094] Specifically, the server receives the approved appeal review result and determines the personnel data in the appeal review result. Based on the personnel data in the appeal review result, the corresponding personnel data in the blacklist database is removed, and the removal record is retained to obtain the processed personnel data. The removal record is used to record any personnel data added to or removed from the blacklist database for subsequent analysis and tracing.

[0095] In this embodiment, by adding, deleting, and modifying the personnel data in the whitelist database, and removing the personnel data in the blacklist database, the personnel data can be accurately updated to ensure the accuracy of personnel information management.

[0096] In an exemplary embodiment, the specific implementation process of the step of "processing personnel data based on the instruction type corresponding to the personnel management command to obtain processed personnel data" includes:

[0097] When the instruction type is a system integration instruction, determine the data interface that matches the target system; through the data interface, link the whitelist database and the blacklist database to the target system respectively, so that the target system calls the personnel data in the whitelist database and the blacklist database.

[0098] Specifically, the server obtains the system to be integrated in the system integration instruction, that is, the target system. The target system can be a firewall, an intrusion detection system, a user authentication system, a business system, an identity management system, etc. For each target system, the server determines a data interface that matches the target system. The personnel data of the personnel to be processed is linked to the data interface to obtain the linked personnel data. The target system can directly obtain the personnel data from the blacklist database or the whitelist database through the data interface, thereby completing the integration of the personnel information with the target system.

[0099] In this embodiment, the whitelist database and the blacklist database are respectively linked to the target system through the data interface, so that the target system can be integrated with the personnel data, thereby improving the application scope of the personnel list information.

[0100] In an exemplary embodiment, the specific implementation process of the step of "processing personnel data based on the instruction type corresponding to the personnel management command to obtain processed personnel data" includes:

[0101] When the instruction type is an analysis and monitoring instruction, the access records in the access log table and the violation records in the blacklist history table are analyzed in real time to obtain the abnormal analysis results corresponding to each personnel data; if the abnormal analysis result is abnormal, an alarm information corresponding to the abnormal analysis result is generated.

[0102] The whitelist database also includes an access log table; the blacklist database also includes a blacklist history table. The access log table is used to record the access status of each person in the whitelist, for example, the access status may include the access source, access result, etc. The blacklist history table is used to record the historical status of each entity in the blacklist, for example, the historical status may include the time of joining the blacklist, the time of removing the blacklist, etc. The blacklist history table can help track the changes in the blacklist.

[0103] Specifically, the server can first record the access status of each entity in the whitelist through the access log table, and use the log analysis tool or the security information and time management system to monitor and analyze the access log table in real time to determine whether there is abnormal access behavior. At the same time, the server can also analyze the blacklist history table to determine the trend and characteristics of the violation, and use data mining technology to determine whether there is abnormal access behavior in the subsequent personnel data. In summary, the server can perform real-time analysis on the personnel data of the personnel to be processed according to the analysis and monitoring instructions, determine whether there is abnormal access behavior of the personnel to be processed, and obtain the abnormal analysis results. If the abnormal analysis result is abnormal, an alarm message corresponding to the abnormal analysis result is generated, and the alarm message is sent to the corresponding terminal. If the abnormal analysis result is normal, no subsequent processing is performed.

[0104] In this embodiment, the personnel data of the personnel to be processed can be monitored in real time through analysis and monitoring instructions, so as to determine the abnormal analysis results of each personnel data and improve the security of personnel list information management.

[0105] The following describes in detail the specific implementation process of the above-mentioned personnel list information management method in conjunction with a specific embodiment. The management method is divided into two parts: whitelist information management and blacklist information management. The whitelist information management specifically includes the following contents:

[0106] 1. Data storage and management.

[0107] 1.1, Database selection. It can be a relational database or a non-relational database. Relational databases can be MySQL, Oracle, etc., which are suitable for structured data storage and have good transaction processing capabilities and data consistency guarantees. Relational databases can be used to store entity information in the whitelist, such as user ID, device number, IP address, etc., as well as related attribute information. Non-relational databases can be MongoDB, Redis, etc., which are suitable for storing semi-structured or unstructured data and have high scalability and high performance. Non-relational databases can be used to store dynamic data in the whitelist, such as temporary authorization information, access logs, etc.

[0108] 1.2, Data structure design. The whitelist database may include a whitelist entity table, a whitelist attribute table, and an access log table. Among them, the whitelist entity table is used to store entity information in the whitelist, including fields such as unique identification, name, description, and type. For example, for a user whitelist, information such as user ID, user name, and user role may be stored. The whitelist attribute table is used to store attribute information of whitelist entities, such as access rights, validity period, number of uses, and so on. It can be associated with the whitelist entity table through a foreign key to achieve flexible attribute management. The access log table is used to record access to whitelist entities, including access time, access source, access results, and so on. The access log table can be used to audit and analyze the use of the whitelist.

[0109] 1.3, Data synchronization and backup. Data synchronization is used to ensure the consistency of whitelist data between different systems or nodes. In one example, the whitelist data can be synchronized from the primary database to the backup database or other related systems by means of timed synchronization, event-triggered synchronization, etc. Data backup is used to regularly back up whitelist data to prevent data loss. A combination of full backup and incremental backup can be used to ensure the integrity and recoverability of backup data.

[0110] 2. Access control and authorization.

[0111] 2.1, Authentication. Authentication can include user authentication and device authentication. User authentication is used to authenticate users who request to access whitelist resources to ensure that only legitimate users can access. Username / password, digital certificate, biometrics and other authentication methods can be used. Device authentication is used to authenticate specific devices or terminals to ensure that only authorized devices can access whitelist resources. Device fingerprint, MAC address binding and other methods can be used.

[0112] 2.2, Authorization strategy. Authorization strategy includes the following three strategies: Role-based access control: assign different access rights according to the user's role. For example, administrators can add, delete, modify and other operations on the whitelist, and ordinary users can only query the whitelist information. Attribute-based access control: dynamic authorization based on the user's attributes and resource attributes. For example, whether the user has the right to access a specific whitelist resource is determined based on the user's geographic location, time, device type and other attributes. Access control list: set an access control list for each whitelist resource to clarify which users or roles can access the resource. A combination of forward authorization and reverse authorization can be used to improve the flexibility and security of authorization.

[0113] 2.3, Access audit. The server can record the access to whitelist resources, including access time, access user, access source, access results, etc. Access audit is used to audit and analyze the use of whitelists to identify potential security risks. Log analysis tools or security information and event management (SIEM) systems can be used to monitor and analyze access logs in real time to detect abnormal access behaviors in a timely manner.

[0114] 3. Whitelist update and maintenance.

[0115] 3.1, Adding whitelist entities can include manual addition and automatic addition. Manual addition: Administrators can manually add whitelist entities through the management interface and enter relevant information of the entity, such as unique identifier, name, description, attributes, etc. Automatic addition: Automatically import whitelist entities from other systems through interfaces or scripts. For example, import the information of legitimate users from the user management system and add them to the whitelist.

[0116] 3.2, Deleting whitelist entities can include manual deletion and automatic deletion. Manual deletion: Administrators can manually delete whitelist entities through the management interface, select the entity to be deleted, and confirm the deletion operation. Automatic deletion: Automatically delete entities in the whitelist according to certain rules or conditions. For example, when a user leaves or a device is scrapped, the corresponding entity is automatically deleted from the whitelist.

[0117] 3.3, updating whitelist attributes can include manual update and automatic update. Manual update: Administrators can manually update the attribute information of whitelist entities through the management interface, such as access rights, validity period, number of uses, etc. Automatic update: Automatically update the attributes of whitelist entities according to certain rules or conditions. For example, when a user's role changes, their access rights in the whitelist are automatically updated.

[0118] 4. Technology integration and expansion.

[0119] 4.1, Integration with other systems. For example, integration with identity management systems to achieve unified authentication and authorization of user identities. Single sign-on (SSO) technology can be used to allow users to log in to one system and access other integrated systems without having to enter their username and password again. Integration with security protection systems, such as firewalls, intrusion detection systems, etc., to achieve security protection for whitelist resources. Whitelist information can be passed to the security protection system to allow it to perform access control and filtering based on the whitelist. Integration with business systems to implement the application of whitelists in business processes. For example, in a financial transaction system, transaction requests from whitelist users are given priority to improve transaction efficiency and security.

[0120] 4.2, Extension and Setting. For example, the server can customize rules, allowing administrators to customize whitelist rules and policies according to actual needs. For example, set specific IP address ranges, device types, user attributes and other conditions as whitelist admission criteria. The server can provide a plug-in mechanism so that third-party developers can develop and integrate customized functional modules. For example, develop a data analysis plug-in to conduct in-depth analysis and mining of whitelist usage. The server can provide an API interface so that other systems can easily call whitelist management functions. For example, develop a mobile application to query whitelist information through the API interface to achieve secure access control for mobile devices.

[0121] In this embodiment, through data storage and management, access control and authorization, whitelist update and maintenance, technology integration and expansion, and through reasonable technology selection and design, efficient, secure and flexible whitelist management can be achieved, providing strong protection for the enterprise's information security and business operations.

[0122] In an exemplary embodiment, the blacklist information management specifically includes the following contents:

[0123] 1. Data storage and management.

[0124] 1.1, Database selection. Databases can include relational databases and non-relational databases. Relational databases can include MySQL, Oracle, etc., which can be used to store structured blacklist data, including basic information of violating entities, descriptions of illegal behaviors, time of joining the blacklist, etc. Relational databases have mature transaction processing and data consistency guarantee mechanisms, and are suitable for storing data that requires strict management. Non-relational databases can include MongoDB, Redis, etc., which have advantages in large-scale blacklist data management. Non-relational databases are usually highly scalable and high-performance, and can quickly handle a large number of read and write operations. You can choose a suitable database based on the specific application scenario and data scale.

[0125] 1.2, Data structure design. The blacklist database may include a blacklist entity table, a violation table, and a blacklist history table. The blacklist entity table is used to store blacklisted entity information, such as user ID, IP address, device serial number, etc. Different table structures can be designed according to different entity types to better manage and query data. The violation table is used to record the violations of blacklist entities, including violation type, violation time, violation details, etc. The violation table helps to understand the reasons why the entity is blacklisted, as well as to conduct review and appeal processing when necessary. The blacklist history table is used to record the historical status of the blacklist entity, including the time of joining the blacklist, the time of removing the blacklist, etc. The blacklist history table can help track changes in the blacklist, as well as perform data analysis and statistics.

[0126] 1.3, Data synchronization and backup. Data synchronization is used in distributed systems to ensure the synchronization of blacklist data between different nodes. Data synchronization tools or distributed database synchronization mechanisms can be used to ensure the consistency of blacklist data on each node. Data backup is used to regularly back up blacklist data to prevent data loss. Database backup tools or cloud storage services can be used to ensure data security and recoverability.

[0127] 2. Access control and interception.

[0128] 2.1, Access detection can be used to perform blacklist detection at various entry points of the system, such as user login, network request, file access, etc. The blacklist database can be queried to determine whether the entity currently requested is in the blacklist. For high-frequency access scenarios, a caching mechanism can be used to cache blacklist data in memory to increase detection speed.

[0129] 2.2, Interception mechanism. When an access request from a blacklisted entity is detected, corresponding interception measures need to be taken. This can include denying access, returning error information, recording logs, etc. Different interception strategies can be set for different types of violations. For example, for serious security violations, the connection can be cut off immediately; for minor violations, a warning can be given and a log can be recorded.

[0130] 2.3, Real-time update. The blacklist should be able to be updated in real time to respond to new violations. New violating entities can be added to the blacklist in a timely manner through an automated monitoring system or manual review. At the same time, the blacklist needs to be reviewed regularly to remove entities that have corrected their errors or no longer pose a threat.

[0131] 3. Appeal and review.

[0132] 3.1, Complaint channel. The server can provide a complaint channel for blacklisted entities, allowing them to explain their situation and appeal. The complaint channel can be an online form, email, or customer service hotline. The complaint channel should ensure that the complaint process is clear and fair, and there is a dedicated person to handle the complaint.

[0133] 3.2, Review mechanism. The server reviews the appeal and determines whether the entity should be removed from the blacklist. The review can be based on the specific violation, the entity's explanation and the evidence provided. Establish review standards and processes to ensure the consistency and fairness of the review. The review results should be notified to the complainant in a timely manner and updated accordingly in the blacklist database.

[0134] 4. Data analysis and monitoring.

[0135] 4.1, Data analysis is used to analyze blacklist data to understand the trends and characteristics of violations. Data mining technology can be used to discover potential security risks and violation patterns. The analysis results can be used to optimize blacklist management strategies and improve the security and stability of the system.

[0136] 4.2, Monitoring and early warning. The server establishes a blacklist monitoring system to monitor the changes in the blacklist in real time. An early warning mechanism can be set up to issue an alarm in time when the number of entities in the blacklist or violations change abnormally. The monitoring system can also monitor the access to the system, detect possible violations and take timely measures.

[0137] 5. Technology integration and expansion.

[0138] 5.1, Integration with other systems: Blacklist management can be integrated with other security systems, such as firewalls, intrusion detection systems, user authentication systems, etc., to achieve comprehensive security protection. The server can share blacklist data with other systems through API or data interface to improve the overall security level.

[0139] 5.2, Extension and Customization: The server can extend and customize blacklist management according to specific business needs. For example, you can add custom violation types, set different interception strategies, customize the appeal process, etc. The server can provide flexible configuration options, allowing administrators to adjust the parameters and rules of blacklist management according to actual conditions.

[0140] In this embodiment, through data storage and management, access control and interception, appeal and review, data analysis and monitoring, and technical integration and expansion, etc., through reasonable technical selection and design, efficient and accurate blacklist management can be achieved to improve the security and stability of the system.

[0141] 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.

[0142] Based on the same inventive concept, the embodiment of the present application also provides a personnel list information management device for implementing the personnel list information management method involved in the 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 one or more personnel list information management device embodiments provided below can refer to the limitations of the personnel list information management method above, and will not be repeated here.

[0143] In an exemplary embodiment, as shown in FIG5 , a personnel list information management device 500 is provided, comprising: a data determination module 501 and an instruction execution module 502, wherein:

[0144] A data determination module is used to determine the personnel data corresponding to the personnel to be processed in a preset database based on the personnel to be processed contained in the personnel management command; the personnel data includes entity information, attribute information and violation information; the preset database includes a whitelist database and a blacklist database;

[0145] The instruction execution module is used to process the personnel data based on the instruction type corresponding to the personnel management command to obtain the processed personnel data; the instruction types include access control instructions, list update instructions, system integration instructions, and analysis and monitoring instructions; among them, the access control instructions are used to determine the resources accessible to the personnel to be processed; the list update instructions are used to maintain the personnel data of the personnel to be processed in the preset database; the system integration instructions are used to associate the personnel data in the preset database with the target system; the analysis and monitoring instructions are used to monitor the behavior of the personnel to be processed by analyzing the data, and send an alarm when the personnel to be processed behave abnormally; the analysis data is determined based on the historical data of each personnel.

[0146] Furthermore, the whitelist database includes a whitelist entity table and a whitelist attribute table; the blacklist database includes a blacklist entity table and a violation table, and the data determination module 501 is specifically used to: if the person to be processed is in the whitelist database, obtain the entity information of the person to be processed in the whitelist entity table; the entity information includes an identifier, a name and a role; obtain the attribute information of the person to be processed in the whitelist attribute table; if the person to be processed is in the blacklist database, obtain the entity information of the person to be processed in the blacklist entity table; obtain the violation information of the person to be processed in the violation table; the violation information includes the violation type, violation time and violation details.

[0147] Furthermore, the instruction execution module 502 is specifically used for: when the instruction type is an access control instruction, updating the access rights corresponding to the attribute information in the whitelist database according to the permission data in the access control instruction to obtain updated personnel data; or, updating the access rights corresponding to the entity information in the whitelist database according to the permission data in the access control instruction to obtain updated personnel data; or, adding the access control list in the access control instruction to the personnel data in the whitelist database to obtain updated personnel data; the access control list contains the access rights between each person and each resource in the whitelist database.

[0148] Furthermore, the instruction execution module 502 is also specifically used for: when the instruction type is an access control instruction, updating the interception authority corresponding to the entity information in the blacklist database according to the permission data in the access control instruction to obtain updated personnel data; the interception authority is used to determine whether the personnel in the blacklist database are blocked from accessing the resource, and to determine the corresponding interception strategy when blocking access; the interception strategy includes a cut-off strategy and an alarm strategy.

[0149] Furthermore, the instruction execution module 502 is specifically used for: when the instruction type is a list update instruction and the person to be processed is in the whitelist database, updating the entity information and attribute information of the person to be processed based on the list update instruction to obtain updated personnel data; the update operation includes adding, deleting and updating; when the instruction type is a list update instruction and the person to be processed is in the blacklist database, determining the appeal review result of the person to be processed in the list update instruction; when the appeal review result is approved, removing the entity information and violation information corresponding to the person to be processed in the blacklist database through the list update instruction to obtain the processed personnel data.

[0150] Furthermore, the instruction execution module 502 is specifically used to: when the instruction type is a system integration instruction, determine the data interface that matches the target system; through the data interface, link the whitelist database and the blacklist database to the target system respectively, so that the target system calls the personnel data in the whitelist database and the blacklist database.

[0151] Furthermore, the whitelist database also includes an access log table; the blacklist database also includes a blacklist history table. The instruction execution module 502 is specifically used for: when the instruction type is an analysis and monitoring instruction, real-time analysis of the access records in the access log table and the violation records in the blacklist history table is performed to obtain abnormal analysis results corresponding to the data of each personnel; if the abnormal analysis result is abnormal, an alarm information corresponding to the abnormal analysis result is generated.

[0152] Each module in the above-mentioned personnel list information management device can be implemented in whole or in part by software, hardware and their combination. Each of the above-mentioned modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory of the computer device in the form of software, so that the processor can call and execute the operations corresponding to each of the above modules.

[0153] In an exemplary embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be shown in FIG6. The computer device includes a processor, a memory, an input / output interface (Input / Output, referred to as I / O) and a communication interface. The processor, the memory and the input / output interface are connected via a system bus, and the communication interface is connected to the system bus via 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, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store whitelist personnel data and blacklist personnel data. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal via a network connection. When the computer program is executed by the processor, a method for managing personnel list information is implemented.

[0154] Those skilled in the art will understand that the structure shown in FIG. 6 is merely a block diagram of a partial 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 shown in the figure, or combine certain components, or have a different arrangement of components.

[0155] In an exemplary 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-mentioned method embodiments when executing the computer program.

[0156] 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.

[0157] 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.

[0158] 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.

[0159] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods 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 this application can include at least one of non-volatile 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), magnetoresistive 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, etc., but are not limited to this.

[0160] 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 specification.

[0161] 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 managing personnel list information, characterized in that: The method comprises: Based on the personnel to be processed contained in the personnel management command, determine the personnel data corresponding to the personnel to be processed in a preset database; the personnel data includes entity information, attribute information and violation information; the preset database includes a whitelist database and a blacklist database; Based on the instruction type corresponding to the personnel management command, the personnel data is processed to obtain processed personnel data; the instruction type includes access control instructions, list update instructions, system integration instructions, and analysis and monitoring instructions; Among them, the access control instructions are used to determine the resources accessible to the personnel to be processed; the list update instructions are used to maintain the personnel data of the personnel to be processed in the preset database; the system integration instructions are used to associate the personnel data in the preset database with the target system; the analysis and monitoring instructions are used to monitor the behavior of the personnel to be processed by analyzing the data, and send an alarm when the personnel to be processed behave abnormally; the analysis data is determined based on the historical data of each of the personnel.

2. The method according to claim 1, characterized in that The whitelist database includes a whitelist entity table and a whitelist attribute table; the blacklist database includes a blacklist entity table and a violation behavior table; The step of determining personnel data corresponding to the personnel to be processed in a preset database based on the personnel to be processed contained in the personnel management command includes: If the person to be processed is in the whitelist database, then obtaining the entity information of the person to be processed in the whitelist entity table; the entity information includes an identifier, a name and a role; and obtaining the attribute information of the person to be processed in the whitelist attribute table; If the person to be processed is in the blacklist database, the entity information of the person to be processed is obtained in the blacklist entity table; the violation information of the person to be processed is obtained in the violation table; the violation information includes the violation type, violation time and violation details.

3. The method according to claim 1, characterized in that The processing of the personnel data based on the instruction type corresponding to the personnel management command to obtain the processed personnel data includes: In the case where the instruction type is an access control instruction, the access rights corresponding to the attribute information in the whitelist database are updated according to the permission data in the access control instruction to obtain updated personnel data; or According to the permission data in the access control instruction, the access rights corresponding to the entity information in the whitelist database are updated to obtain updated personnel data; or The access control list in the access control instruction is added to the personnel data in the whitelist database to obtain updated personnel data; the access control list includes access rights between each person and each resource in the whitelist database.

4. The method according to claim 3, characterized in that The processing of the personnel data based on the instruction type corresponding to the personnel management command to obtain the processed personnel data includes: In the case where the instruction type is an access control instruction, the interception authority corresponding to the entity information in the blacklist database is updated according to the permission data in the access control instruction to obtain updated personnel data; the interception authority is used to determine whether the personnel in the blacklist database are blocked from accessing resources, and to determine the corresponding interception strategy when blocking access; the interception strategy includes a cut-off strategy and an alarm strategy.

5. The method according to claim 1, characterized in that The processing of the personnel data based on the instruction type corresponding to the personnel management command to obtain the processed personnel data includes: In the case where the instruction type is a list update instruction, and the person to be processed is in the whitelist database, an update operation is performed on the entity information and attribute information of the person to be processed based on the list update instruction to obtain updated personnel data; the update operation includes adding, deleting and updating; In the case where the instruction type is a list update instruction, and the person to be processed is in the blacklist database, determining the appeal review result of the person to be processed in the list update instruction; When the appeal review result is approved, the entity information and violation information corresponding to the person to be processed in the blacklist database are removed through the list update instruction to obtain the processed personnel data.

6. The method according to claim 1, characterized in that The processing of the personnel data based on the instruction type corresponding to the personnel management command to obtain the processed personnel data includes: In the case where the instruction type is a system integration instruction, determining a data interface matching the target system; The whitelist database and the blacklist database are linked to the target system respectively through the data interface, so that the target system calls the personnel data in the whitelist database and the blacklist database.

7. The method according to claim 2, characterized in that: The whitelist database also includes an access log table; the blacklist database also includes a blacklist history table; The processing of the personnel data based on the instruction type corresponding to the personnel management command to obtain the processed personnel data includes: When the instruction type is an analysis and monitoring instruction, the access records in the access log table and the violation records in the blacklist history table are analyzed in real time to obtain abnormal analysis results corresponding to the data of each person; If the abnormal analysis result is abnormal, an alarm message corresponding to the abnormal analysis result is generated.

8. A device for managing personnel list information, characterized in that: The device comprises: A data determination module, for determining personnel data corresponding to the personnel to be processed in a preset database based on the personnel to be processed contained in the personnel management command; the personnel data includes entity information, attribute information and violation information; the preset database includes a whitelist database and a blacklist database; An instruction execution module is used to process the personnel data based on the instruction type corresponding to the personnel management command to obtain the processed personnel data; the instruction types include access control instructions, list update instructions, system integration instructions, and analysis and monitoring instructions; wherein the access control instructions are used to determine the resources accessible to the personnel to be processed; the list update instructions are used to maintain the personnel data of the personnel to be processed in the preset database; the system integration instructions are used to associate the personnel data in the preset database with the target system; the analysis and monitoring instructions are used to monitor the behavior of the personnel to be processed by analyzing the data, and send an alarm when the personnel to be processed behave abnormally; the analysis data is determined based on the historical personnel data.

9. 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 7 are implemented.

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

Images