Zero trust authority policy management method, system and device

By adopting a zero-trust architecture in the network, clustering terminal entities and resource entities, and generating target authorization permission policies, the problem of insufficient security of permission control based on network location is solved, and security control of the internal network is realized.

CN118869353BActive Publication Date: 2024-11-26HANGZHOU HIKVISION DIGITAL TECHNOLOGY CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411323573.8
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2024-09-20
Publication Date
2024-11-26
Estimated Expiration
2044-09-20

AI Technical Summary

Technical Problem

The existing network permission control is based on the network location and is easily counterfeited, resulting in insufficient security, especially the IP address inside the firewall is trustworthy but there is actually a risk of attack.

Method used

Adopting a zero-trust architecture, by clustering terminal entities, resource entities and hybrid entities in the network, a target authorization authority policy is generated, and the authorization authority is determined based on the business role and authority policy subgraph of each entity, so as to achieve zero data Trust permission control.

Benefits of technology

Ensure network security, even the PCs on the internal network need to pass verification, prevent counterfeit attacks, and achieve reasonable permission settings and security control.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118869353B_ABST
    Figure CN118869353B_ABST
Patent Text Reader

Abstract

The embodiment of the present application provides a zero-trust permission policy management method, system and device. This embodiment is different from the traditional permission control based on network location, such as the IP outside the firewall is untrusted, and the IP inside the firewall is trusted. Instead, it generates corresponding target authorization permission policies for each terminal entity and hybrid entity based on the zero-trust architecture, and performs zero-trust permission control on the data passing through based on the target authorization permission policy of each entity. Even if the PC in the internal network is untrusted, the data sent by it is also subject to permission control based on its corresponding target authorization permission policy (equivalent to achieving zero-trust permission control), ensuring network security.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to network security, and in particular to a zero-trust authority policy management method, system, and device. Background Art

[0002] To ensure network security, permissions are often configured based on network locations. For example, with a firewall as the boundary, Internet Protocol (IP) addresses outside the firewall are not trusted and do not have direct access to the firewall, while IP addresses inside the firewall are trusted and have access to the firewall. However, this method is easily spoofed to attack. For example, hackers often spoof IP addresses inside the firewall to access the firewall in order to attack the firewall. Summary of the invention

[0003] The embodiments of the present application provide a zero-trust permission policy management method, system, and device to implement zero-trust permission management.

[0004] The present application provides a zero-trust authority policy management method, which is applied to a zero-trust gateway in a network. The method includes:

[0005] Cluster the entities under each specified category in the constructed permission strategy graph to obtain at least one entity subclass; the nodes in the permission strategy graph include terminal entities, resource entities and hybrid entities; the terminal entity sends request data but does not send response data within a set time period; the resource entity sends response data but does not send request data within the set time period; the hybrid entity sends request data within the set time period and sends corresponding response data for the received request data; there is a connection relationship between at least two nodes in the permission strategy graph; wherein the connection relationship from a first node as a terminal entity or a hybrid entity to a second node as a hybrid entity or a resource entity indicates a permission policy for the first node to access the second node, and the permission policy is used to indicate whether the first node is authorized to access the second node; each entity in the same entity subclass belongs to the same business role; the permission strategy graph includes the following two specified categories: the category to which the terminal entity belongs and the category to which the hybrid entity belongs;

[0006] For each entity subclass, the maximum similarity subgraph corresponding to the entity subclass is determined based on the permission policy subgraphs of each entity in the entity subclass; the permission policy subgraph of any entity represents the connection relationship between the entity as a node and other nodes in the permission policy graph, and the other nodes represent entities in other categories other than the category to which the entity belongs; the maximum similarity subgraph corresponding to any entity subclass is the intersection of the permission policy subgraphs of each entity in the entity subclass;

[0007] The target authorization permission policy for each entity under each entity subclass is generated according to the business role to which each entity subclass belongs and the maximum similarity subgraph corresponding to each entity subclass, so as to perform zero-trust permission control on the data passing through based on the target authorization permission policy.

[0008] The present application also provides a zero-trust authority policy management system, which includes:

[0009] Zero Trust Gateway, Multiple Entities;

[0010] The multiple entities are divided into terminal entities, resource entities and hybrid entities by the zero-trust gateway based on data monitored within a set time period; the terminal entity sends request data but does not send response data within the set time period; the resource entity sends response data but does not send request data within the set time period; the hybrid entity sends request data within the set time period and sends corresponding response data for the received request data;

[0011] The zero trust gateway executes the steps in the above method.

[0012] The embodiment of the present application also provides a zero-trust authority policy management device, which is applied to a zero-trust gateway in a network, and the device includes:

[0013] A clustering unit is used to cluster entities under each specified category in the constructed permission strategy graph to obtain at least one entity subclass; the nodes in the permission strategy graph include terminal entities, resource entities and hybrid entities; the terminal entity sends request data but does not send response data within a set time period; the resource entity sends response data but does not send request data within the set time period; the hybrid entity sends request data within the set time period and sends corresponding response data for the received request data; there is a connection relationship between at least two nodes in the permission strategy graph; wherein the connection relationship from a first node as a terminal entity or a hybrid entity to a second node as a hybrid entity or a resource entity indicates a permission policy for the first node to access the second node, and the permission policy is used to indicate whether the first node is authorized to access the second node; each entity in the same entity subclass belongs to the same business role; the permission strategy graph includes the following two specified categories: the category to which the terminal entity belongs and the category to which the hybrid entity belongs;

[0014] A policy unit is used to determine, for each entity subclass, the maximum similarity subgraph corresponding to the entity subclass based on the permission policy subgraphs of each entity in the entity subclass; the permission policy subgraph of any entity represents the connection relationship between the entity as a node and other nodes in the permission policy graph, and the other nodes represent entities under other categories other than the category to which the entity belongs; the maximum similarity subgraph corresponding to any entity subclass is the intersection of the permission policy subgraphs of each entity in the entity subclass; based on the business role to which each entity subclass belongs and the maximum similarity subgraph corresponding to each entity subclass, a target authorization permission policy for each entity under each entity subclass is generated, so as to perform zero-trust permission control on the data passing through based on the target authorization permission policy.

[0015] The present application also provides an electronic device, including: a processor; and a machine-readable storage medium,

[0016] The machine-readable storage medium stores computer program instructions, which, when executed by a processor, cause the processor to execute the steps in the above method.

[0017] An embodiment of the present application also provides a computer program product, including a computer program, which implements the steps of the above method when executed by a processor.

[0018] An embodiment of the present application also provides a machine-readable storage medium, which stores computer program instructions. When the computer program instructions are executed, the steps of the above method can be implemented.

[0019] It can be seen from the above technical solutions that this embodiment is different from the traditional permission control based on network location, such as the IP outside the firewall is untrusted, and the IP inside the firewall is trusted. Instead, it generates corresponding target authorization permission policies for each terminal entity and hybrid entity based on the zero-trust architecture, so as to perform zero-trust permission control on the data passing through based on the target authorization permission policy of each entity. Even if the PC in the internal network is untrusted, the data sent by it is also subject to permission control based on its corresponding target authorization permission policy (equivalent to realizing zero-trust permission control), thereby ensuring network security.

[0020] Furthermore, this embodiment determines the maximum similarity subgraph corresponding to each entity subclass through the permission policy subgraph of each entity in each entity subclass to perform role profiling for the business role corresponding to each entity subclass. This can generate the target authorization permission strategy for each entity under each entity subclass in combination with the actual business configuration to ensure the rationality of the permission setting. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] Figure 1 A flow chart of the method provided in the embodiment of the present application;

[0022] Figure 2A network structure diagram provided for an embodiment of the present application;

[0023] Figure 3 A schematic diagram of a permission strategy diagram provided for an embodiment of the present application;

[0024] Figure 4 A flowchart for implementing step 101 provided in an embodiment of the present application;

[0025] Figure 5 A schematic diagram of the structure of the device provided in the embodiment of the present application;

[0026] Figure 6 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0027] In order to enable those skilled in the art to better understand the technical solutions provided by the embodiments of the present application and to make the above-mentioned purposes, features and advantages of the embodiments of the present application more obvious and understandable, the technical solutions in the embodiments of the present application are further described in detail below in conjunction with the accompanying drawings.

[0028] Zero-trust permission management means that any user needs to be authenticated before being authorized, even the IP address inside the firewall as described above needs to be authenticated before being authorized, such as accessing the firewall device. The following describes the zero-trust permission policy management method provided in the embodiment of the present application:

[0029] See also Figure 1 , Figure 1 A flowchart of a method provided in an embodiment of the present application. As an embodiment, the process can be applied to a gateway node (also called a zero-trust gateway node). There are also multiple entities in the network. Figure 2 The structure of the network is shown as an example.

[0030] In this embodiment, the gateway node detects data within a set time period. As an embodiment, the gateway node may mirror the data received within the set time period to analyze each business process based on the mirrored data.

[0031] As an embodiment, any business process includes a request sub-process and a response sub-process corresponding to the request sub-process. The request sub-process here refers to the process of one entity (recorded as the first node) sending request data to another entity (recorded as the second node). Correspondingly, the response sub-process corresponding to the request sub-process refers to the process of the second node returning response data to the first node based on the received request data. Based on this, in this embodiment, any business process includes at least: request IP address, response IP address, response result. The response result here includes at least: successful response or unsuccessful response.

[0032] For ease of understanding, this embodiment uses the following parameters to represent any business process (denoted as f) as an example: [request IP address, response IP address, service interface, request method, response result]. The service interface here refers to an entity that sends request data, such as the interface requested by the first node mentioned above. The request method here is such as get, put, etc. under http, which is not specifically limited in this embodiment. Correspondingly, the set of all business processes F=[f1, f2, f3…fn] finally obtained based on the data within the above set time period.

[0033] As an embodiment, this embodiment determines the terminal entities, resource entities and hybrid entities existing in the network based on the service process set F.

[0034] Optionally, this embodiment can sort out a terminal entity set from the business process set F. The terminal entity here corresponds to, for example, a personal PC, etc., which refers to sending request data but not sending response data within the above-mentioned set time period (that is, only executing the action of initiating a request to other entities). Any terminal entity is represented by its IP address, that is, one IP address represents one terminal entity e. The terminal entity set E = [e1, e2, e3…en].

[0035] Optionally, this embodiment can sort out a resource entity set from the business process set F. The resource entity here, such as an independent resource platform, such as a view library storage database, refers to sending response data but not sending request data within the above-mentioned set time period (that is, only executing response actions, such as only responding to request actions). Any resource entity is represented by its IP address, that is, one IP address represents one resource entity s. Resource entity set S = [s1, s2, s3...sn].

[0036] Optionally, this embodiment can sort out a hybrid entity set from the business process set F. The hybrid entity here refers to sending request data in the above-mentioned set time period and sending corresponding response data for the received request data. In other words, the hybrid entity can perform request actions and can also perform response actions. For example, if the hybrid entity is a comprehensive resource platform such as a visual comprehensive platform, it can return response data to the personal PC for the request data of the personal PC, and can also initiate request data to the view library storage database. Any hybrid entity m is characterized by IP address + service interface + request method. Hybrid entity set M=[m1, m2, m3…mn].

[0037] Afterwards, this embodiment can determine the authority policy status of each entity from the business process set F.

[0038] Taking the permission policy of the terminal entity as an example, as an embodiment, this embodiment can first divide the business process containing each terminal entity and the business process of each hybrid entity as the requesting end from the business process set F. For each e mentioned above, there can be multiple business processes f containing the e. Similarly, for each s mentioned above as the requesting end, there can also be multiple business processes f with the requesting end as the s.

[0039] Afterwards, for each terminal entity, the permission policy of the terminal entity is determined based on the response results in each business process including the terminal entity. Optionally, at least two business processes that meet similarity conditions are selected from each business process including the terminal entity; the similarity conditions are such as the same request IP address and the same response IP address; or the request IP address, response IP address, service interface, and request method are all the same.

[0040] As an embodiment, if the response result of at least one of the at least two business processes indicates a successful response (such as a 200 response code of the http protocol, a 200 response code of the ftp protocol, etc.), it means that the request data sent by the entity represented by the requesting IP address in the business process, such as the above-mentioned first node, is successfully responded to by the entity represented by the responding IP address, such as the above-mentioned second node. At this time, it can be considered that the entity represented by the requesting IP address, such as the above-mentioned first node, and the entity represented by the responding IP address, such as the above-mentioned second node, have authorization authority (that is, the first node has the authority to be authorized to access the second node), which can be expressed as: va=[e, s, a], or va=[m, s, a], where a refers to authorization. It should be noted that the at least two business processes that meet the similarity condition are also business processes related to the entity represented by the requesting IP address, such as the above-mentioned first node, and the entity represented by the responding IP address, such as the above-mentioned second node in the business process.

[0041] As another embodiment, if the response results in the at least two business processes are all unsuccessful responses (i.e., response failures, such as indicated by a 404 response code in the http protocol and a 426 response code in the ftp protocol), it means that the request data sent by the entity represented by the requesting IP address in the business process, such as the first node mentioned above, has not been successfully responded to by the entity represented by the responding IP address, such as the second node mentioned above. At this time, it can be considered that the entity represented by the requesting IP address, such as the first node mentioned above, and the entity represented by the responding IP address, such as the second node mentioned above, have unauthorized permissions (i.e., the first node is not authorized to access the second node), which can be expressed as: vu=[e, s, u], or vu=[m, s, u], where u refers to unauthorization authorization.

[0042] In the same way, this embodiment can also determine the corresponding authority policy when the hybrid entity is used as the request end, which will not be described in detail here.

[0043] Afterwards, this embodiment uses the above entities as nodes to construct a permission strategy graph. In the permission strategy graph, the connection relationship between at least two nodes, for example, the connection relationship from the first node to the second node indicates the permission strategy for the first node to access the second node. The permission strategy is used to indicate whether the first node is authorized to access the second node (that is, whether the request data sent by the first node is successfully responded to by the second node). For ease of understanding, Figure 3 An example is given to illustrate the construction of a permission strategy graph. Figure 3 In the permission strategy diagram shown in the figure, the solid line indicates authorization, and the dotted line indicates unauthorized. Figure 3 In the permission policy graph shown, there is no edge between two nodes, which means that the connection relationship between the two nodes is unknown, and it is unknown whether the access rights between the two nodes are authorized.

[0044] It should be noted that, as an embodiment, in the above-mentioned permission policy graph, if there is a mutually exclusive edge between two nodes (that is, the connection relationship from one node to another node in the two nodes has both the above-mentioned solid line and the above-mentioned dotted line), a permission mutual exclusion indication can be output to further confirm the final permission policy between the two nodes.

[0045] Based on the above description, the following Figure 1 The process shown is described as follows:

[0046] like Figure 1 As shown, the process may include the following steps:

[0047] Step 101 , clustering entities under each specified category in the constructed permission strategy graph to obtain at least one entity subclass.

[0048] In this embodiment, the authority policy graph includes the following three categories: the category to which the terminal entity belongs, the category to which the resource entity belongs, and the category to which the hybrid entity belongs. Among them, the category to which the terminal entity belongs and the category to which the hybrid entity belongs are designated categories, and it is necessary to determine the authorization authority policy of each entity under the designated category, as described below.

[0049] As an embodiment, this step 101 may be performed for each specified category as follows during specific implementation: Figure 4 It should be noted that Figure 4 This is just an example and is not intended to be limiting.

[0050] In this embodiment, the same entity subclass can be configured with the same business role, while different entity subclasses can be configured with different business roles. The business role configured for any entity subclass depends on the determination of each entity in the entity subclass, and this embodiment does not specifically limit it.

[0051] Step 102, for each entity subclass, determine the maximum similarity subgraph corresponding to the entity subclass based on the permission policy subgraphs of each entity in the entity subclass; the permission policy subgraph of any entity represents the connection relationship between the entity as a node and other nodes in the permission policy graph, and the above-mentioned other nodes represent entities in other categories other than the category to which the entity belongs; the maximum similarity subgraph corresponding to any entity subclass is the intersection of the permission policy subgraphs of each entity in the entity subclass.

[0052] In this embodiment, the authority policy subgraph of any entity can be determined by the following steps: for each entity, other entities belonging to the same category as the entity are deleted from the authority policy graph to obtain the authority policy subgraph of the entity. At this time, the authority policy subgraph of the entity reflects the connection relationship between the entity and entities of other categories.

[0053] In the specific implementation, if the maximum similarity subgraphs corresponding to S entity subclasses under the same specified category are similar, it means that the business roles corresponding to the S entity subclasses are similar and there may be errors in the entity subclass division. At this time, the S entity subclasses can be classified as the same entity subclass to avoid the subsequent problem of unclear boundaries of different entity permissions.

[0054] Step 103, generating a target authorization permission policy for each entity under each entity subclass according to the business role to which each entity subclass belongs and the maximum similarity subgraph corresponding to each entity subclass, so as to perform zero-trust permission control on the data packets passing through based on the target authorization permission policy.

[0055] As an embodiment, when this step 103 is specifically implemented, the business roles to which each entity subclass belongs and the maximum similarity subgraph corresponding to each entity subclass can be output first, so that the user can edit the maximum similarity subgraph corresponding to each entity subclass based on the output business roles to which each entity subclass belongs and the maximum similarity subgraph corresponding to each entity subclass, such as deleting, modifying, adding entities and / or connection relationships between entities in combination with actual business needs. By outputting the business roles to which each entity subclass belongs and the maximum similarity subgraph corresponding to each entity subclass, it can generate the target authorization permission policy for each entity under each entity subclass in combination with the actual business configuration to ensure the rationality of the permission setting. On the other hand, the visualization effect is good, and the maximum similarity subgraph corresponding to each entity subclass can be corrected by editing.

[0056] Afterwards, obtain the connection relationship between the nodes in the maximum similarity subgraph corresponding to the business role adjusted by the user based on the actual needs of the business corresponding to each output business role; the maximum similarity subgraph corresponding to any business role refers to the maximum similarity subgraph corresponding to the entity subclass belonging to the business role. Optionally, users, such as administrators, can control the connection relationship between the nodes in the maximum similarity subgraph based on actual needs. Afterwards, the target authorization permission policy for each entity under each entity subclass can be generated based on the connection relationship between the nodes in the current maximum similarity subgraphs. For example, if the line from the first node to the second node in a maximum similarity subgraph is a solid line, it means that the first node has the authorization permission to access the second node.

[0057] As another embodiment, this embodiment may also generate and output the zero-trust gateway rules of each entity based on each maximum similarity subgraph (that is, visually display the zero-trust gateway rules of each entity), and then the administrator may adjust the zero-trust gateway rules of at least one entity that is visually displayed based on actual business needs to adjust the specific permission policy of the entity. Specifically, this embodiment may generate the zero-trust gateway rules of each entity under each entity subclass based on the business role to which each entity subclass belongs and the maximum similarity subgraph corresponding to each entity subclass, and output the visualized zero-trust gateway rules of each entity, so that external users can adjust the outputted at least one visualized zero-trust gateway rule of each entity based on the business needs corresponding to the business role to which each entity belongs to generate the target authorization permission policy for each entity under each entity subclass.

[0058] After that, this embodiment can perform zero-trust permission control based on the target authorization permission policy of each entity. For example, taking the IP address as the dimension, when the data is received, the target authorization permission policy of the entity represented by the IP address is searched based on the IP address of the sender of the data. If there is no target authorization permission policy for the entity represented by the IP address (the entity at this time can be considered as an illegal entity), the data is intercepted, such as directly discarding the data. If it exists, the corresponding permission policy is found based on the IP address of the target end to which the data is to be reached, so as to ensure that any request end can access the specific interface of the response end, and the data that does not follow the request method and request interface in the permission policy is also intercepted, such as discarding.

[0059] Based on this, as an embodiment, the target authorization permission policy of the terminal entity or hybrid entity as the requesting end under each different business role includes at least: the IP address of the requesting end, the allowed request method, the resource entity or hybrid entity as the responding end that is allowed to access, and the specific interface of the responding end.

[0060] Based on this, this embodiment performs zero-trust authority control on the data passing through based on the target authorization authority policy, including: after receiving the request data sent by the terminal entity or hybrid entity as the requesting end, if it is determined based on the IP address of the requesting end that there is currently no target authorization authority policy for the requesting end, or if it is determined based on the IP address of the requesting end that there is currently a target authorization authority policy for the requesting end, but the request method of the request data or the response end accessed or the interface accessed does not comply with the target authorization authority policy, then the request data is intercepted.

[0061] So far, completed Figure 1 The process shown.

[0062] pass Figure 1 It can be seen from the shown process that this embodiment is different from the traditional permission control based on network location, such as the IP outside the firewall is untrusted, and the IP inside the firewall is trusted. Instead, it generates corresponding target authorization permission policies for each terminal entity and hybrid entity based on the zero-trust architecture, so as to perform zero-trust permission control on the data passing through based on the target authorization permission policy of each entity. Even if the PC in the internal network is untrusted, the data sent by it is also subject to permission control based on its corresponding target authorization permission policy (equivalent to realizing zero-trust permission control), thereby ensuring network security.

[0063] Furthermore, this embodiment determines the maximum similarity subgraph corresponding to each entity subclass through the permission policy subgraph of each entity in each entity subclass to perform role profiling for the business role corresponding to each entity subclass. This can generate the target authorization permission strategy for each entity under each entity subclass in combination with the actual business configuration to ensure the rationality of the permission setting.

[0064] Below Figure 4 The process shown is described as follows:

[0065] See also Figure 4 , Figure 4 The step 101 provided in the embodiment of the present application is implemented as a flowchart. Figure 4 As shown, the process may include the following steps:

[0066] Step 401 : for each designated category, determine the permission policy subgraph of each entity under the designated category based on the constructed permission policy graph.

[0067] The permission policy subgraph of any entity is described above and will not be repeated here.

[0068] Step 402 : determining the distances between the entities in the specified category according to the permission policy subgraphs of the entities in the specified category to generate a matrix corresponding to the category based on the distances between the entities.

[0069] As an embodiment, this embodiment can convert the permission policy subgraph of any entity into a vector corresponding to the permission policy subgraph based on the connection relationship between the entity and entities in other categories in the permission policy subgraph (such as authorization (successful response, unauthorized (unsuccessful response), unknown). For example, authorization is represented by 1, unauthorized is represented by 0, and unknown is represented by a fixed value such as 2. Then, the distance between every two entities under the specified category is calculated based on the vectors corresponding to the permission policy subgraphs of the two entities, and finally the above-mentioned matrix is ​​formed.

[0070] As an embodiment, the distance calculation formula here may be, for example, Graph embedding of a kernel method or a Graph kernel method, etc., which is not specifically limited in this embodiment.

[0071] Applied to this embodiment, through step 402, a matrix corresponding to the category to which the terminal entity belongs (denoted as Le) and a matrix corresponding to the category to which the hybrid entity belongs (denoted as Lm) are finally obtained.

[0072] Step 403: Based on the distances between the entities in the matrix, unsupervised clustering is performed on the entities in the specified category to obtain at least one entity subclass.

[0073] The manner of performing unsupervised clustering of entities under the specified category based on the distances between the entities in the above matrix is ​​not specifically limited in this embodiment. For example, entities with the same distance may be regarded as the same entity subclass, etc.

[0074] According to the above Figure 4 The process shown will eventually cluster the entities under each specified category to obtain at least one entity subclass.

[0075] So far, completed Figure 4 The process shown.

[0076] It should be noted that in this embodiment, the entities in the above network will change dynamically. For example, when a terminal entity is added, the target authorization permission policy of the terminal entity is generated according to the business role to which the terminal entity belongs and based on the maximum similarity subgraph corresponding to the business role (equivalent to the permission policy template); the maximum similarity subgraph corresponding to any business role refers to the maximum similarity subgraph corresponding to the entity subclass belonging to the business role; when a hybrid entity is added to the network, the target authorization permission policy of the hybrid entity is generated according to the business role to which the hybrid entity belongs and based on the maximum similarity subgraph corresponding to the business role (equivalent to the permission policy template). This can provide effective use of permission policy templates and reduce frequent permission application and configuration processes.

[0077] It should be noted that if a new resource entity needs to be added, such as a new resource entity based on a request from a terminal entity or a hybrid entity, the resource entity is added, and the permission policy of the terminal entity or the hybrid entity is adjusted by permission application and / or manual adjustment. This embodiment is not specifically limited.

[0078] It should also be noted that, in this embodiment, after the target authorization authority policy of each entity under each entity subclass is generated, the target authorization authority policy of at least one entity may be dynamically adjusted.

[0079] For example, mining out the entity that acts as an attacker from various entities, and canceling the target authorization permission policy of the entity that acts as an attacker; and mining out the entity that has private authorization from various entities, and deleting the privately authorized permissions in the target authorization permission policy of the entity; the privately authorized permissions refer to the permissions indicated by the remaining subgraph obtained by deleting the maximum similarity subgraph corresponding to the entity subclass to which the entity belongs from the permission policy subgraph of the entity; and / or,

[0080] Monitor data within a period of time after generating the target authorization permission policy for each entity under each entity subclass, build a permission policy graph based on the monitored data, return to the step of clustering the entities under each category in the constructed permission policy graph to obtain at least one entity subclass, so as to regenerate the target authorization permission policy for each current entity.

[0081] As an embodiment, by means of the permission policy representation of each entity under the above-mentioned zero-trust architecture, such as the above-mentioned maximum similarity subgraph, the entity that acts as an attacker can be quickly and efficiently mined through simple rule editing.

[0082] Optionally, the above-mentioned entity acting as an attacker includes at least: an invalid entity, an orphan entity, a dormant entity, an entity with invalid permissions, and an entity with an invalid role;

[0083] Among them, the target authorization permission policy of the invalid entity is: unauthorized. The entity subclass to which the orphan entity belongs only includes the orphan entity. A dormant entity refers to an entity that has no interactive behavior within a preset period of time. An entity with invalid permissions refers to an entity whose requests have always failed. An entity with an invalid role refers to an entity whose actual business role is different from the business role configured for the entity subclass to which the entity belongs.

[0084] As an embodiment, in a specific implementation, due to an error, N identical permission policies may exist for the same entity. To avoid redundant authorization, N-1 identical permission policies may be deleted.

[0085] The method provided in the embodiments of the present application is described above.

[0086] It can be seen from the above description that this embodiment constructs permission policies in a graphical manner by combing the relationships between various entities in the existing network environment, such as terminal entities, resource entities, hybrid entities, etc., and automatically configures permission policies for terminal entities and hybrid entities. It can better handle scenarios with a large number of terminals, a large number of services, and complex permission configurations between terminals and services.

[0087] The following describes the system and device provided in the embodiments of the present application:

[0088] The present application embodiment provides a zero-trust authority policy management system, which may include:

[0089] Zero Trust Gateway, Multiple Entities;

[0090] The multiple entities are divided into terminal entities, resource entities and hybrid entities by the zero-trust gateway based on data monitored within a set time period; the terminal entity sends request data but does not send response data within the set time period; the resource entity sends response data but does not send request data within the set time period; the hybrid entity sends request data within the set time period and sends corresponding response data for the received request data;

[0091] The zero trust gateway executes the steps in the above method.

[0092] The present application also provides a zero-trust authority policy management device. Figure 5 , Figure 5 This is a structural diagram of a device provided in an embodiment of the present application. The device is applied to a zero-trust gateway in a network, and the device includes:

[0093] A clustering unit is used to cluster entities under each specified category in the constructed permission strategy graph to obtain at least one entity subclass; the nodes in the permission strategy graph include terminal entities, resource entities and hybrid entities; the terminal entity sends request data but does not send response data within a set time period; the resource entity sends response data but does not send request data within the set time period; the hybrid entity sends request data within the set time period and sends corresponding response data for the received request data; there is a connection relationship between at least two nodes in the permission strategy graph; wherein the connection relationship from a first node as a terminal entity or a hybrid entity to a second node as a hybrid entity or a resource entity indicates a permission policy for the first node to access the second node, and the permission policy is used to indicate whether the first node is authorized to access the second node; each entity in the same entity subclass belongs to the same business role; the permission strategy graph includes the following two specified categories: the category to which the terminal entity belongs and the category to which the hybrid entity belongs;

[0094] A policy unit is used to determine, for each entity subclass, the maximum similarity subgraph corresponding to the entity subclass based on the permission policy subgraphs of each entity in the entity subclass; the permission policy subgraph of any entity represents the connection relationship between the entity as a node and other nodes in the permission policy graph, and the other nodes represent entities under other categories other than the category to which the entity belongs; the maximum similarity subgraph corresponding to any entity subclass is the intersection of the permission policy subgraphs of each entity in the entity subclass; based on the business role to which each entity subclass belongs and the maximum similarity subgraph corresponding to each entity subclass, a target authorization permission policy for each entity under each entity subclass is generated, so as to perform zero-trust permission control on the data passing through based on the target authorization permission policy.

[0095] Optionally, the permission policy for the first node to access the second node is determined by the following steps:

[0096] Obtaining the business process related to the first node and the second business node based on the data detected within the set time period; any business process indicates a request sub-process in which the first node sends request data to the second node and a response sub-process in which the second node returns response data to the first node based on the received request data; any business process at least includes: a request IP address, a response IP address, and a response result; the request IP address is the IP address of the first node, and the response IP address is the IP address of the second node; the response result at least includes: a successful response or an unsuccessful response;

[0097] Determine the permission policy for the first node to access the second node based on the response results in each obtained business process; wherein, if the response results in N business processes among all the obtained business processes are successful responses, then determine that the permission policy for the first node to access the second node is that the first node is authorized to access the second node; otherwise, determine that the permission policy for the first node to access the second node is that the first node is not authorized to access the second node; wherein N is greater than or equal to 1.

[0098] Optionally, clustering the entities under each specified category in the constructed permission strategy graph to obtain at least one entity subclass includes:

[0099] For each specified category, determine the permission policy subgraph of each entity under the specified category based on the constructed permission policy graph; determine the distance between the entities under the specified category according to the permission policy subgraphs of the entities under the specified category to generate a matrix corresponding to the category based on the distances between the entities;

[0100] Based on the distances between the entities in the matrix, unsupervised clustering is performed on the entities under the specified category to obtain at least one entity subclass.

[0101] Optionally, generating a target authorization authority strategy according to the business role to which each entity subclass belongs and the maximum similarity subgraph corresponding to each entity subclass includes:

[0102] Output visualized business roles to which each entity subclass belongs and the maximum similarity subgraph corresponding to each entity subclass, and obtain the connection relationship between nodes in the maximum similarity subgraph corresponding to each business role adjusted by the user based on the actual needs of the business corresponding to each business role; the maximum similarity subgraph corresponding to any business role refers to the maximum similarity subgraph corresponding to the entity subclass belonging to the business role; based on the connection relationship between the nodes in the current maximum similarity subgraphs, generate the target authorization permission policy for each entity under each entity subclass; or

[0103] Based on the business roles to which each entity subclass belongs and the maximum similarity subgraph corresponding to each entity subclass, zero-trust gateway rules for each entity under each entity subclass are generated and visualized zero-trust gateway rules for each entity are output, so that external users can adjust at least one of the output visualized zero-trust gateway rules for each entity based on the business needs corresponding to the business roles to which each entity belongs to generate target authorization permission policies for each entity under each entity subclass.

[0104] Optionally, the target authorization authority policy of the terminal entity or hybrid entity as the requesting end under each different business role includes at least: the IP address of the requesting end, the allowed request mode, the resource entity or hybrid entity as the responding end that is allowed to be accessed, and the specific interface of the responding end;

[0105] The zero-trust permission control of the data passing through based on the target authorization permission policy includes: after receiving the request data sent by the terminal entity or hybrid entity as the requesting end, if it is determined based on the IP address of the requesting end that the target authorization permission policy of the requesting end does not currently exist, or if it is determined based on the IP address of the requesting end that the target authorization permission policy of the requesting end currently exists, but the request method of the request data or the response end accessed or the interface accessed does not comply with the target authorization permission policy, then the request data is intercepted.

[0106] Optionally, the policy unit further generates a target authorization permission policy for the terminal entity according to the business role to which the terminal entity belongs and based on the maximum similarity subgraph corresponding to the business role when a new terminal entity is added to the network; the maximum similarity subgraph corresponding to any business role refers to the maximum similarity subgraph corresponding to the entity subclass belonging to the business role; when a new hybrid entity is added to the network, the target authorization permission policy for the hybrid entity is generated according to the business role to which the hybrid entity belongs and based on the maximum similarity subgraph corresponding to the business role.

[0107] Optionally, after generating the target authorization permission policy for each entity under each entity subclass, the policy unit is further used to:

[0108] Mining out the entity that acts as an attacker from various entities, and canceling the target authorization permission policy of the entity that acts as an attacker; and mining out the entity that has private authorization from various entities, and updating the privately authorized permissions in the target authorization permission policy of the entity; the privately authorized permissions refer to the permissions indicated by the remaining subgraph obtained by deleting the maximum similarity subgraph corresponding to the entity subclass to which the entity belongs from the permission policy subgraph of the entity; and / or,

[0109] Monitor data within a period of time after generating the target authorization permission policy for each entity under each entity subclass, build a permission policy graph based on the monitored data, return to the step of clustering the entities under each category in the constructed permission policy graph to obtain at least one entity subclass, so as to regenerate the target authorization permission policy for each current entity.

[0110] Optionally, the entity acting as an attacker includes at least: an invalid entity, an orphan entity, a dormant entity, an entity with invalid permissions, and an entity with an invalid role;

[0111] Wherein, the target authorization authority policy of the invalid entity is: unauthorized;

[0112] The entity subclass to which the orphan entity belongs only includes the orphan entity;

[0113] The dormant entity refers to an entity that does not have any interactive behavior within a preset time period;

[0114] The entity with invalid permissions refers to an entity whose requests have always failed;

[0115] The entity with an invalid role refers to an entity whose actual business role is different from the business role configured for the entity subclass to which the entity belongs.

[0116] So far, completed Figure 5 Structural description of the device shown.

[0117] The present application also provides Figure 5 The hardware structure of the device shown is described in FIG. Figure 6 The structure in the electronic device shown. Figure 6 , Figure 6 This is a structural diagram of an electronic device provided in an embodiment of the present application. Figure 6 As shown, the hardware structure may include: a processor and a machine-readable storage medium, the machine-readable storage medium storing machine-executable instructions that can be executed by the processor; the processor is used to execute the machine-executable instructions to implement the method disclosed in the above example of this application.

[0118] Based on the same application concept as the above method, an embodiment of the present application also provides a machine-readable storage medium, on which a number of computer instructions are stored. When the computer instructions are executed by a processor, the method disclosed in the above example of the present application can be implemented.

[0119] Exemplarily, the above-mentioned machine-readable storage medium can be any electronic, magnetic, optical or other physical storage device, which can contain or store information, such as executable instructions, data, etc. For example, the machine-readable storage medium can be: RAM (Radom Access Memory), volatile memory, non-volatile memory, flash memory, storage drive (such as hard disk drive), solid state drive, any type of storage disk (such as optical disk, DVD, etc.), or similar storage medium, or a combination thereof.

[0120] The above are only embodiments of the present application and are not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included within the scope of the claims of the present application.

Claims

1. A zero-trust authority policy management method, characterized in that: The method is applied to a zero-trust gateway in a network, and the method includes: Cluster the entities under each specified category in the constructed permission strategy graph to obtain at least one entity subclass; the nodes in the permission strategy graph include terminal entities, resource entities and hybrid entities; the terminal entity sends request data but does not send response data within a set time period; the resource entity sends response data but does not send request data within the set time period; the hybrid entity sends request data within the set time period and sends corresponding response data for the received request data; there is a connection relationship between at least two nodes in the permission strategy graph; wherein the connection relationship from a first node as a terminal entity or a hybrid entity to a second node as a hybrid entity or a resource entity indicates a permission policy for the first node to access the second node, and the permission policy is used to indicate whether the first node is authorized to access the second node; each entity in the same entity subclass belongs to the same business role; the permission strategy graph includes the following two specified categories: the category to which the terminal entity belongs and the category to which the hybrid entity belongs; For each entity subclass, the maximum similarity subgraph corresponding to the entity subclass is determined based on the permission policy subgraphs of each entity in the entity subclass; the permission policy subgraph of any entity represents the connection relationship between the entity as a node and other nodes in the permission policy graph, and the other nodes represent entities in other categories other than the category to which the entity belongs; the maximum similarity subgraph corresponding to any entity subclass is the intersection of the permission policy subgraphs of each entity in the entity subclass; The target authorization permission policy for each entity under each entity subclass is generated according to the business role to which each entity subclass belongs and the maximum similarity subgraph corresponding to each entity subclass, so as to perform zero-trust permission control on the data passing through based on the target authorization permission policy.

2. The method according to claim 1, characterized in that The permission policy for the first node to access the second node is determined by the following steps: Obtaining the business process related to the first node and the second node based on the data detected within the set time period; any business process indicating a request sub-process in which the first node sends request data to the second node and a response sub-process in which the second node returns response data to the first node based on the received request data; Any business process at least includes: a request IP address, a response IP address, and a response result; the request IP address is the IP address of the first node, and the response IP address is the IP address of the second node; the response result at least includes: a successful response or an unsuccessful response; Determine the permission policy for the first node to access the second node based on the response results in each obtained business process; wherein, if the response results in N business processes among all the obtained business processes are successful responses, then determine that the permission policy for the first node to access the second node is that the first node is authorized to access the second node; otherwise, determine that the permission policy for the first node to access the second node is that the first node is not authorized to access the second node; wherein N is greater than or equal to 1.

3. The method according to claim 1, characterized in that The clustering of entities under each specified category in the constructed permission strategy graph to obtain at least one entity subclass includes: For each specified category, determine the permission policy subgraph of each entity under the specified category based on the constructed permission policy graph; determine the distance between the entities under the specified category according to the permission policy subgraphs of the entities under the specified category to generate a matrix corresponding to the category based on the distances between the entities; Based on the distances between the entities in the matrix, unsupervised clustering is performed on the entities under the specified category to obtain at least one entity subclass.

4. The method according to claim 1, characterized in that The target authorization authority strategy is generated according to the business role to which each entity subclass belongs and the maximum similarity subgraph corresponding to each entity subclass, including: Output visualized business roles to which each entity subclass belongs and the maximum similarity subgraph corresponding to each entity subclass, and obtain the connection relationship between nodes in the maximum similarity subgraph corresponding to each business role adjusted by the user based on the actual needs of the business corresponding to each business role; the maximum similarity subgraph corresponding to any business role refers to the maximum similarity subgraph corresponding to the entity subclass belonging to the business role; based on the connection relationship between the nodes in the current maximum similarity subgraphs, generate the target authorization permission policy for each entity under each entity subclass; or Based on the business roles to which each entity subclass belongs and the maximum similarity subgraph corresponding to each entity subclass, zero-trust gateway rules for each entity under each entity subclass are generated and visualized zero-trust gateway rules for each entity are output, so that external users can adjust at least one of the output visualized zero-trust gateway rules for each entity based on the business needs corresponding to the business roles to which each entity belongs to generate target authorization permission policies for each entity under each entity subclass.

5. The method according to claim 1, characterized in that The target authorization authority policy of the terminal entity or hybrid entity as the requesting end under each different business role at least includes: the IP address of the requesting end, the allowed request method, the resource entity or hybrid entity as the responding end that is allowed to be accessed, and the specific interface of the responding end; The zero-trust permission control of the data passing through based on the target authorization permission policy includes: after receiving the request data sent by the terminal entity or hybrid entity as the requesting end, if it is determined based on the IP address of the requesting end that the target authorization permission policy of the requesting end does not currently exist, or if it is determined based on the IP address of the requesting end that the target authorization permission policy of the requesting end currently exists, but the request method of the request data or the response end accessed or the interface accessed does not comply with the target authorization permission policy, then the request data is intercepted.

6. The method according to claim 1, characterized in that The method further comprises: When a terminal entity is newly added to the network, a target authorization authority policy for the terminal entity is generated according to the business role to which the terminal entity belongs and based on the maximum similarity subgraph corresponding to the business role; the maximum similarity subgraph corresponding to any business role refers to the maximum similarity subgraph corresponding to the entity subclass belonging to the business role; When a hybrid entity is newly added to the network, a target authorization authority policy for the hybrid entity is generated according to the business role to which the hybrid entity belongs and based on the maximum similarity subgraph corresponding to the business role.

7. The method according to claim 1, characterized in that After generating the target authorization permission policy for each entity under each entity subclass, the method further includes: Mining out the entity that acts as an attacker from various entities, and canceling the target authorization permission policy of the entity that acts as an attacker; and mining out the entity that has private authorization from various entities, and updating the privately authorized permissions in the target authorization permission policy of the entity; the privately authorized permissions refer to the permissions indicated by the remaining subgraph obtained by deleting the maximum similarity subgraph corresponding to the entity subclass to which the entity belongs from the permission policy subgraph of the entity; and / or, Monitor data within a period of time after generating the target authorization permission policy for each entity under each entity subclass, build a permission policy graph based on the monitored data, return to the step of clustering the entities under each category in the constructed permission policy graph to obtain at least one entity subclass, so as to regenerate the target authorization permission policy for each current entity.

8. The method according to claim 7, characterized in that The entities acting as attackers include at least: invalid entities, orphan entities, dormant entities, entities with invalid permissions, and entities with invalid roles; Wherein, the target authorization authority policy of the invalid entity is: unauthorized; The entity subclass to which the orphan entity belongs only includes the orphan entity; The dormant entity refers to an entity that does not have any interactive behavior within a preset time period; The entity with invalid permissions refers to an entity whose requests have always failed; The entity with an invalid role refers to an entity whose actual business role is different from the business role configured for the entity subclass to which the entity belongs.

9. A zero-trust authority policy management system, characterized in that: The system includes: Zero Trust Gateway, Multiple Entities; The multiple entities are divided into terminal entities, resource entities and hybrid entities by the zero-trust gateway based on data monitored within a set time period; the terminal entity sends request data but does not send response data within the set time period; the resource entity sends response data but does not send request data within the set time period; the hybrid entity sends request data within the set time period and sends corresponding response data for the received request data; The zero trust gateway executes the steps in any method of claims 1 to 8.

10. A zero-trust authority policy management device, characterized in that: The device is applied to a zero-trust gateway in a network, and the device includes: A clustering unit is used to cluster entities under each specified category in the constructed permission strategy graph to obtain at least one entity subclass; the nodes in the permission strategy graph include terminal entities, resource entities and hybrid entities; the terminal entity sends request data but does not send response data within a set time period; the resource entity sends response data but does not send request data within the set time period; the hybrid entity sends request data within the set time period and sends corresponding response data for the received request data; there is a connection relationship between at least two nodes in the permission strategy graph; wherein the connection relationship from a first node as a terminal entity or a hybrid entity to a second node as a hybrid entity or a resource entity indicates a permission policy for the first node to access the second node, and the permission policy is used to indicate whether the first node is authorized to access the second node; each entity in the same entity subclass belongs to the same business role; the permission strategy graph includes the following two specified categories: the category to which the terminal entity belongs and the category to which the hybrid entity belongs; A policy unit is used to determine, for each entity subclass, the maximum similarity subgraph corresponding to the entity subclass based on the permission policy subgraphs of each entity in the entity subclass; the permission policy subgraph of any entity represents the connection relationship between the entity as a node and other nodes in the permission policy graph, and the other nodes represent entities under other categories other than the category to which the entity belongs; the maximum similarity subgraph corresponding to any entity subclass is the intersection of the permission policy subgraphs of each entity in the entity subclass; based on the business role to which each entity subclass belongs and the maximum similarity subgraph corresponding to each entity subclass, a target authorization permission policy for each entity under each entity subclass is generated, so as to perform zero-trust permission control on the data passing through based on the target authorization permission policy.

11. An electronic device, characterized in that: include: processor; and a machine-readable storage medium, The machine-readable storage medium stores computer program instructions, which, when executed by a processor, cause the processor to perform the steps of any one of the methods of claims 1 to 8.