Zero-trust network access control method and device, computing equipment and storage medium
By verifying tickets on the zero-trust network server, ensuring the consistency of user equipment and identity, solving the problem of inability to timely discover and prevent account impersonation in the existing technology, and achieving efficient security self-checking of network access environments and Improved safety.
Patent Information
- Application Number
- CN202310634502.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-05-31
- Publication Date
- 2024-12-03
AI Technical Summary
The existing zero-trust network access control method cannot detect and perform automatic intervention in a timely manner when a user account is impersonated or an attacker uses his legal identity in violation of regulations, resulting in the risk of data leakage and sensitive data leakage.
The zero-trust network server receives the ticket verification request, verify the identity consistency of the access object in the user equipment through different methods and whether the user's unified network identity is pre-specified, and performs corresponding processing operations to control access rights.
Continuous detection and automatic intervention during the access process are achieved, reducing the risk of data leakage caused by attackers' misappropriation of identity information, improving the accuracy of security protection and the availability and security of zero-trust networks.
Smart Images

Figure CN119071004A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to the field of Internet technology, and more specifically to an access control method and apparatus for a zero-trust network, a computing device, a computer-readable storage medium, and a computer program product. Background Art
[0002] In an era of rapid development of Internet technology, the security of network access has become increasingly important. Zero-trust networks have the technical characteristics of "continuous verification, never trust". This network security protection architecture does not trust any device, user or system by default, but rebuilds the trust foundation of access control based on user identity authentication and authorization, thereby achieving the purpose of network security protection.
[0003] However, the relevant technology focuses on issuing security rules to a single device. When detecting users using terminal applications to access business sites, data or APIs (Application Programming Interfaces), the network access environment of the current device is determined to be safe based on whether there is a violation of the "identity, device, application" security rules. However, the shortcoming is that when a user account is impersonated or an attacker illegally uses a legitimate user identity to access resources on other devices, it is not possible to timely associate and discover and perform automatic intervention. The relevant technology relies more on retrospective tracing and filling loopholes, which may cause serious data leakage risks and sensitive information leakage. Summary of the invention
[0004] In view of this, the present disclosure provides a method and apparatus for access control of a zero-trust network, a computing device, a computer-readable storage medium, and a computer program product, so as to alleviate, mitigate, or even eliminate some or all of the above-mentioned problems and other possible problems.
[0005] According to one aspect of the present disclosure, a method for access control of a zero-trust network is proposed, characterized in that the method is executed by a zero-trust network server, and the method includes: receiving a verification request for a ticket, wherein the verification request is issued by a zero-trust network gateway based on a ticket received from a zero-trust network agent, the ticket is used to establish a communication connection between the zero-trust network agent and the zero-trust network gateway, the zero-trust network agent agent proxies an access request for an access object of the zero-trust network by a user authenticated and logged in at the zero-trust network client through the communication connection, and the ticket includes a unified network identity of the user, the unified network identity of the user includes at least information of a user device of the user, an identity of the user authenticated and logged in at the zero-trust network client, and information of an access object to be accessed by the user; verifying the ticket based on the verification request to obtain a verification result, wherein the verifying the ticket based on the verification request includes: verifying whether the identities of the user device accessing the access object in different ways are consistent, and verifying whether the unified network identity of the user is pre-specified at the zero-trust network server; and executing corresponding processing operations based on the verification result to control the user's access to the access object of the zero-trust network.
[0006] According to some embodiments of the present disclosure, the method further includes: receiving a ticket request from the zero-trust network client, the ticket request being issued by the zero-trust network client based on an access request for an access object of the zero-trust network initiated by a user through an application, and including a unified network identity of the user; in response to determining that the access request complies with a predetermined access control policy based on the ticket request, issuing a ticket to the zero-trust network client so that the zero-trust network client sends the ticket to the zero-trust network agent, so that the zero-trust network agent proxies the access request based on the ticket
[0007] According to some embodiments of the present disclosure, in response to determining that the access request complies with a predetermined access control policy based on the ticket request, issuing a ticket to the zero trust network client includes: verifying whether the identities of the user device accessing the access object in different ways are consistent; verifying whether the user's unified network identity is consistent with predetermined access control list information, wherein the predetermined access control list information pre-specifies the unified network identity of the user allowed to access in the zero trust network; in response to the identity of the user device accessing the access object in different ways being consistent, and the user's unified network identity is consistent with the predetermined access control list information, determining that the access request complies with the predetermined access control policy; and issuing a ticket to the zero trust network client.
[0008] According to some embodiments of the present disclosure, the verification of whether the identities of users accessing the access object through different methods in the user device are consistent includes at least one of the following: verifying whether the identities of users accessing the access object through different applications in the user device are consistent; verifying whether the identity of the user accessing the access object through the application in the user device is consistent with the identity of the user authenticated and logged in on the zero-trust network client.
[0009] According to some embodiments of the present disclosure, the access control list information is constructed in the following manner: associating the information of multiple user devices of the user with the identity of the user authenticated and logged in at the zero-trust network client to form a device ownership relationship; obtaining the information of the access objects that the user is allowed to access through the multiple user devices; and obtaining the access control list information based on the device ownership relationship and the information of the access objects that the multiple user devices are allowed to access.
[0010] According to some embodiments of the present disclosure, the corresponding processing operations are performed based on the verification result to control the user's access to the access object of the zero trust network, including: sending the verification result to the zero trust network gateway so that the zero trust network gateway performs the corresponding processing operations based on the verification result.
[0011] According to some embodiments of the present disclosure, the verification result is sent to the zero-trust network gateway so that the zero-trust network gateway performs corresponding processing operations based on the verification result, including: in response to the identity of the access object accessed in different ways in the user device is not consistent, or the user's unified network identity is not pre-specified, sending the verification failure as the verification result to the zero-trust network gateway, so that the zero-trust network gateway performs a verification failure processing operation.
[0012] According to some embodiments of the present disclosure, the verification failure processing operation includes: causing the zero-trust network client to execute at least one of a pop-up box alarm, disconnecting the network connection with the zero-trust network agent, and forcing the user to exit the authentication login of the zero-trust network client.
[0013] According to some embodiments of the present disclosure, the method also includes: receiving a security work order from a security operation center platform, the security work order including exception information, the exception information indicating that the identity of the user device accessing the access object in different ways is inconsistent or indicating that the unified network identity of the user between different user devices is inconsistent, and is generated by the security operation center platform based on information related to the access request received from the zero trust network gateway; sending the exception information to the zero trust network client, so that the zero trust network client displays the exception information to the user.
[0014] According to some embodiments of the present disclosure, sending the exception information to the zero-trust network client so that the zero-trust network client displays the exception information to the user includes: confirming whether the exception information matches the verification result; in response to the exception information matching the verification result, sending the exception information to the zero-trust network client so that the zero-trust network client displays the exception information to the user.
[0015] According to some embodiments of the present disclosure, the method further includes: receiving a processing result for the abnormal information from the user; and synchronizing the processing result to the security operation center platform to update the processing status of the security work order.
[0016] According to another aspect of the present disclosure, a zero-trust network access control device is proposed, comprising: a receiving module, configured to receive a verification request for a ticket, wherein the verification request is issued by a zero-trust network gateway based on a ticket received from a zero-trust network agent, the ticket is used to establish a communication connection between the zero-trust network agent and the zero-trust network gateway, the zero-trust network agent agent processes an access request for an access object of the zero-trust network through the communication connection from a user who has authenticated and logged in at the zero-trust network client, and the ticket includes a unified network identity of the user, and the unified network identity of the user includes at least the user The invention relates to a method for verifying the ticket based on the verification request, the method comprising: verifying whether the identities of the user device accessing the access object in different ways are consistent, and verifying whether the unified network identity of the user is pre-specified on the zero-trust network server; and a processing module, which is configured to perform corresponding processing operations based on the verification result to control the user's access to the access object of the zero-trust network.
[0017] According to another aspect of the present disclosure, a computing device is proposed, including: a memory and a processor, wherein a computer program is stored in the memory, and when the computer program is executed by the processor, the processor is prompted to execute an access control method for a zero-trust network according to some embodiments of the present disclosure.
[0018] According to another aspect of the present disclosure, a computer-readable storage medium is provided, on which computer-readable instructions are stored. When the computer-readable instructions are executed, the access control method of the zero-trust network according to some embodiments of the present disclosure is implemented.
[0019] According to another aspect of the present disclosure, a computer program product is proposed, including a computer program, which, when executed by a processor, implements the access control method for a zero-trust network according to some embodiments of the present disclosure.
[0020] In the access control method and device of the zero-trust network according to some embodiments of the present disclosure, the zero-trust network server verifies the ticket based on the received verification request to verify whether the identity of the access object accessed in different ways in the user device is consistent and whether the user's unified network identity (which at least includes the information of the user's user device, the identity of the user authenticated and logged in in the zero-trust network client, and the information of the access object to be accessed by the user) is pre-specified in the zero-trust network server, so as to perform corresponding processing operations based on the verification results to control the user's access to the access object of the zero-trust network. Through such a verification method, continuous detection can be performed during the access process, and automatic intervention can be performed when abnormal information and behavior are found, thereby realizing an efficient method for self-checking the security of the network access environment, reducing the risk of data leakage caused by attackers stealing identity information, reducing problems such as leakage of sensitive information, and improving the accuracy of security protection, and enhancing the availability and security of the zero-trust network.
[0021] These and other aspects of the application will be apparent from and elucidated with reference to the embodiments described hereinafter. BRIEF DESCRIPTION OF THE DRAWINGS
[0022] The various aspects, features and advantages of the present disclosure will be readily understood from the following detailed description and accompanying drawings, in which:
[0023] Figure 1 An example implementation environment of an access control system for a zero-trust network according to some embodiments of the present disclosure is schematically shown;
[0024] Figure 2 The flowchart of the access control method of the zero-trust network according to some embodiments of the present disclosure is schematically shown;
[0025] Figure 3A A schematic diagram schematically shows a scenario in which a user queries device information on a zero-trust network client according to some embodiments of the present disclosure;
[0026] Figure 3B A schematic diagram of an access scenario of a zero-trust network in a normal access state according to some embodiments of the present disclosure is schematically shown;
[0027] Figure 3C A schematic diagram of access scenarios of a zero-trust network in an abnormal access state according to some embodiments of the present disclosure is schematically shown;
[0028] Figure 3D Schematically illustrates an example pop-up alert interface when abnormal information in a zero-trust network is detected according to some embodiments of the present disclosure;
[0029] Figure 4 The flowchart of the access control method of the zero-trust network according to some embodiments of the present disclosure is schematically shown;
[0030] Figure 5 The schematic diagram schematically shows the principle of the access control strategy of the zero-trust network according to some embodiments of the present disclosure;
[0031] Figure 6 The flowchart of the access control method of the zero-trust network according to some embodiments of the present disclosure is schematically shown;
[0032] Figure 7 Schematically illustrates an interactive process diagram of a zero-trust network including a security operation center platform according to some embodiments of the present disclosure;
[0033] Figure 8 is a schematic diagram schematically showing an architecture of an access control system of a zero-trust network according to some embodiments of the present disclosure;
[0034] Fig. 9 An example block diagram schematically illustrates an access control device for a zero-trust network according to some embodiments of the present disclosure; and
[0035] Fig.10 An example block diagram of a computing device according to some embodiments of the present disclosure is schematically shown.
[0036] It should be noted that the above-mentioned drawings are merely schematic and illustrative and are not necessarily drawn to scale. DETAILED DESCRIPTION
[0037] Several embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings so that those skilled in the art can implement the present disclosure. The present disclosure can be embodied in many different forms and purposes and should not be limited to the embodiments described herein. These embodiments are provided to make the present disclosure comprehensive and complete, and to fully convey the scope of the present disclosure to those skilled in the art. The embodiments do not limit the present disclosure.
[0038] It will be understood that, although the terms first, second, third, etc. may be used to describe various elements, components and / or parts in this article, these elements, components and / or parts should not be limited by these terms. These terms are only used to distinguish one element, component or part from another element, component or part. Therefore, the first element, component or part discussed below may be referred to as the second element, component or part without departing from the teaching of the present disclosure.
[0039] The terms used herein are only for the purpose of describing specific embodiments and are not intended to limit the present disclosure. As used herein, the singular forms "one", "one" and "the" are intended to also include plural forms, unless the context clearly indicates otherwise. It will be further understood that the terms "include" and / or "comprise" specify the existence of the features, wholes, steps, operations, elements and / or parts when used in this specification, but do not exclude the existence of one or more other features, wholes, steps, operations, elements, parts and / or their groups or add one or more other features, wholes, steps, operations, elements, parts and / or their groups. As used herein, the term "and / or" includes any and all combinations of one or more of the associated listed items.
[0040] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by those of ordinary skill in the art to which the present disclosure belongs. It will be further understood that terms such as those defined in commonly used dictionaries should be interpreted as having a meaning consistent with their meaning in the relevant art and / or the context of this specification, and will not be interpreted in an idealized or overly formal sense, unless explicitly defined as such herein.
[0041] The block diagrams shown in the accompanying drawings are only functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities can be implemented in software form, or in one or more hardware modules or integrated circuits, or in different networks and / or processor devices and / or microcontroller devices.
[0042] The flowcharts shown in the accompanying drawings are only exemplary and do not necessarily include all promotional information and operations / steps, nor do they necessarily have to be executed in the order described. For example, some operations / steps can be decomposed, while some operations / steps can be combined or partially combined, so the actual execution order may change according to actual conditions.
[0043] Those skilled in the art will appreciate that the drawings are merely example interfaces of example embodiments, and the modules or processes in the drawings are not necessarily required for implementing the present application, and therefore cannot be used to limit the scope of protection of the present application.
[0044] Artificial Intelligence (AI) is the theory, method, technology and application system that uses digital computers or machines controlled by digital computers to simulate, extend and expand human intelligence, perceive the environment, acquire knowledge and use knowledge to obtain the best results. In other words, artificial intelligence is a comprehensive technology in computer science that attempts to understand the essence of intelligence and produce a new intelligent machine that can respond in a similar way to human intelligence. Artificial intelligence is to study the design principles and implementation methods of various intelligent machines so that machines have the functions of perception, reasoning and decision-making. Artificial intelligence technology is a comprehensive discipline that covers a wide range of fields, including both hardware-level technology and software-level technology. The basic technologies of artificial intelligence generally include technologies such as sensors, dedicated artificial intelligence chips, cloud computing, distributed storage, big data processing technology, operation / interaction systems, and mechatronics. Artificial intelligence software technology mainly includes computer vision technology, speech processing technology, natural language processing technology, as well as machine learning / deep learning, autonomous driving, smart transportation, and automatic control.
[0045] Cloud technology refers to a hosting technology that unifies hardware, software, network and other resources in a wide area network or local area network to achieve data computing, storage, processing and sharing. Cloud technology is a general term for network technology, information technology, integration technology, management platform technology, application technology, etc. based on the cloud computing business model. It can form a resource pool that can be used on demand and is flexible and convenient. Cloud computing technology will become an important support. The background services of technical network systems require a large amount of computing and storage resources, such as video websites, picture websites and more portal websites. With the high development and application of the Internet industry, in the future, each item may have its own identification mark, and all need to be transmitted to the background system for logical processing. Data of different levels will be processed separately. All kinds of industry data require strong system backing support, which can only be achieved through cloud computing.
[0046] Before describing the embodiments of the present disclosure in detail, some related concepts are first explained for the sake of clarity.
[0047] 1. Zero Trust Network: A communication architecture used for communication between access subjects and access objects. It is based on identity authentication and has the capabilities of business security access, continuous trust assessment and dynamic access control. The functions of zero trust network are used through zero trust network clients (such as intelligent office automation system (IOA) clients).
[0048] 2. Access subject: The party that initiates access in a zero-trust network. The person / device / application that accesses intranet business resources is a digital entity composed of a single person, device, application, or other combination of factors.
[0049] 3. Access object: The party being accessed in a zero-trust network, that is, the enterprise's intranet business resources, including applications, systems (development and testing environment, operation and maintenance environment, production environment, etc.), data, interfaces, functions, etc.
[0050] 4. Trusted application: An application carrier authorized by the management end and accessible to the terminal to the internal business system, including application name, application information summary algorithm, signature information, etc.
[0051] 5. Reachable zone: The list of internal sites set by the enterprise that end users can access through the zero-trust network.
[0052] 6. Login credentials: After a user successfully logs in to the zero-trust network client, the zero-trust network server specifies an encrypted string for the user, which represents the user's login authorization information, including user information and authorization validity period. The login credentials are encrypted and stored in the zero-trust network client.
[0053] 7. Network request credentials: Authorization information issued by the zero-trust network server for a single network request, used to identify the authorization status of the network request.
[0054] 8. Zero-trust network access control policy: It consists of process information (trusted applications) that users can use and accessible business sites (reachable areas). When permissions are enabled, users can access any reachable area through any trusted application. The granularity of the zero-trust network access control policy is the logged-in user, allowing different zero-trust network access control policies to be formulated for different logged-in users.
[0055] 9. Zero Trust Network Gateway: Deployed at the entrance of enterprise applications and data resources, it is responsible for verifying and forwarding each session request to access enterprise resources.
[0056] 10. Access Agent: The terminal access agent is a terminal agent deployed on the controlled device to initiate secure access. It is responsible for initiating requests for trusted identity authentication of the access subject. When the verified identity is trusted, it can establish an encrypted access connection with the access gateway. It is also the policy execution point for access control.
[0057] 11. Direct access: In a zero-trust network access architecture, an application initiates a network access request to a site. After the full-flow proxy hijacks the traffic, it initiates network access to the target site through the full-flow proxy, that is, initiates direct connection access. The full-flow proxy sends the network response of the target site to the application. This access mode is called direct access.
[0058] 12. Proxy access: In a zero-trust network access architecture, an application initiates a network access request to a site. After the full-flow proxy hijacks the traffic, the full-flow proxy initiates traffic forwarding to the zero-trust network gateway, and access to the target business site is proxied by the zero-trust network gateway. After the access, the zero-trust network gateway sends the network response of the target site to the full-flow proxy, and the full-flow proxy forwards the network response of the target site to the application. This access mode is called proxy access.
[0059] 13. Service addressing: In the distributed cascade deployment mode, different services are deployed in different servers. The process of finding the server connection address where the background services that different business modules of the client are concerned about are deployed is called service addressing.
[0060] 14. Atomic operation: one or a series of operations supported by the processor that cannot be interrupted, including CAS (Compare & Set), FAA (Fetch and Add) and other operations. It can be used to implement uninterrupted data exchange operations in multi-threaded programming, thereby avoiding data inconsistency problems caused by uncertainty in execution order and unpredictable interruptions when multiple threads simultaneously rewrite a certain data.
[0061] 15. Sensitive information: User login information including user identity, password, etc., as well as login credentials (big ticket) and network access credentials (small ticket).
[0062] 16. Business module: A collection of multiple files that complete certain specific functions. The concept of module can not only describe the product more clearly, but also more conveniently specify the content to be installed and uninstalled.
[0063] 17. Plug-in: represents each business execution module, which mainly exists in the form of a dynamic link library. Generally, the dynamic link library manages multiple sub-modules.
[0064] 18. Policy: A set of rules issued by the administrator on the management side for enterprise terminal management. Including patch repair, zero-trust network management, security reinforcement strategy, etc. The policy may contain sensitive information such as tickets, time limit, and validity times.
[0065] 19. Network session: The process of information exchange between a user and a business system, such as the process of sending or receiving data after a client and a server establish a network link. This includes connection establishment and termination, or data sending and receiving.
[0066] 20. Access session: Based on network session, and contains a set of related features. Access session is an abstract concept that is bound to a combination of devices, personnel, network attributes, process attributes, and endpoint attributes for each network session that accesses enterprise intranet business resources (including business applications, core systems, asset data, functional interfaces, etc.).
[0067] 21. Security Operations Center Platform: Usually called SOC (Security Operations Center) platform, it usually adopts centralized management, uniformly manages related security products, collects security information of all assets in the network, and conducts in-depth analysis, statistics, and correlation of various security events collected to timely reflect the security status of managed assets, locate security risks, promptly discover and locate various security incidents, and promptly provide processing methods and suggestions to assist administrators in event analysis, risk analysis, early warning management and emergency response processing.
[0068] The technical solution provided in this application involves the field of Internet technology, and specifically explains the design and implementation of an access control strategy for a zero-trust network, which can improve the security of zero-trust network access.
[0069] The following describes an exemplary application of the electronic device provided by the embodiment of the present application. The electronic device provided by the embodiment of the present application can be implemented as various types of user terminals such as personal digital assistants (PDAs), laptops, tablet computers, desktop computers, netbooks, set-top boxes, mobile devices (e.g., mobile phones, portable music players, personal digital assistants, dedicated messaging devices, portable gaming devices), wearable computing devices (e.g., smart watches, head-mounted devices, including smart glasses), and can also be implemented as servers. The following describes an exemplary application when the electronic device is implemented as a terminal device.
[0070] See also Figure 1 , Figure 1 The exemplary implementation environment of the access control system 100 of the zero-trust network according to some embodiments of the present disclosure is schematically shown. Figure 1As shown, the terminal device 110 is a terminal device associated with the user, and an application 111, a zero-trust network agent 112 and a zero-trust network client 113 are running on the terminal device 110, wherein the application 111 can be various types of applications, such as video playback applications, online conference applications, live broadcast applications, news applications, and instant messaging applications. It should be noted that the application 111 refers to an application that is authorized by the zero-trust network server 102 and can access the internal business system (such as the business server 105). The zero-trust network client 113 is a software installed and run on the user's device, which is mainly responsible for verifying the user identity, device credibility and application credibility on the user's device, and applying for unknown processes to the server for process inspection; the zero-trust network client 113 can ensure the security, stability and efficiency of users' access to enterprise resources and data in any network environment by relying on core capabilities such as trusted terminals, trusted identities and trusted applications.
[0071] The zero-trust network agent 112 is used to hijack the access request sent by the application 111, and the access control policy obtained by the zero-trust network client 113 from the zero-trust network server 102 is stored in the zero-trust network agent 112. The zero-trust network server 102 verifies the ticket based on the received verification request to verify whether the identity of the access object accessed in different ways in the user device is consistent and whether the unified network identity of the user is pre-specified in the zero-trust network server 102, thereby performing corresponding processing operations based on the verification result. Next, the zero-trust network agent 112 establishes a communication connection between the application 111 and the business server 105 based on the verification result and the zero-trust network (including the zero-trust network agent, the zero-trust network gateway and the zero-trust network server), and sends the hijacked access request to the business server 105 through the communication connection, and sends the access request response returned by the business server 105 to the application 111 through the communication connection. The following is a specific description.
[0072] For example, after hijacking the access request sent by the application 111, the zero-trust network agent 112 first initiates an authentication request to the zero-trust network client 113 (i.e., the zero-trust network agent 112 applies for a ticket for this access request from the zero-trust network client 113). After receiving the authentication request sent by the zero-trust network agent 112, the zero-trust network client 113 applies for a ticket from the zero-trust network server 102, and sends the ticket returned by the zero-trust network server 102 to the zero-trust network agent 112. After receiving the ticket sent by the zero-trust network client 113, the zero-trust network agent 112 sends the ticket to the zero-trust network gateway 103, so that the zero-trust network gateway 103 sends the ticket to the zero-trust network server 102 for verification. When the zero-trust network server 102 successfully verifies the ticket sent by the zero-trust network gateway 103, the zero-trust network gateway 103 can establish a communication connection with the zero-trust network agent 112, and then the zero-trust network agent 112 forwards the access request sent by the hijacked application 111 to the zero-trust network gateway 103, and the zero-trust network gateway 103 forwards the access request sent by the application 111 to the business server 105. When the zero-trust network server 102 fails to verify the ticket sent by the zero-trust network gateway 103, the connection between the zero-trust network agent 112 and the zero-trust network gateway 103 can be disconnected, and the zero-trust network agent 112 directly forwards the access request sent by the application 111 to the business server 105.
[0073] It should be noted that for proxy access, it actually includes two communication connections between application 111 and zero trust network gateway 103, and between zero trust network gateway 103 and business server 105, which are relayed by zero trust network gateway 103 (that is, when application 111 sends an access request to business server 105, the address of application 111 is replaced with the address of zero trust network gateway 103; when receiving the access request response returned from business server 105, the address of zero trust network gateway 103 is replaced with the address of application 111, and then the access request response is sent to application 111).
[0074] In some embodiments, the zero-trust network service end 102 and the business server 105 can be independent physical servers, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms. The terminal device 110 can be a smart phone, a tablet computer, a laptop computer, a desktop computer, a smart speaker, a smart watch, etc., but is not limited to this. The terminal device 110 can be directly or indirectly connected to the zero-trust network service end 102, the zero-trust network gateway 103, and the business server 105 through wired or wireless communication, which is not limited in the embodiments of the present application.
[0075] Figure 2 The flowchart of the access control method of the zero-trust network according to some embodiments of the present disclosure is schematically shown. Figure 1 As shown in , the access control method of the zero-trust network according to the present disclosure can be executed on the terminal device 110 side. In other embodiments, the access control method of the zero-trust network according to the present disclosure can also be executed in combination by the zero-trust network server 102 and the terminal device 110.
[0076] like Figure 2 As shown in , the access control method of the zero-trust network according to some embodiments of the present disclosure may include steps S210-S230. Steps S210-S230 are described in detail below. Figure 2 The method steps can be executed by the zero-trust network server 102.
[0077] At step S210, a verification request for the ticket is received, wherein the verification request is issued by the zero trust network gateway 103 based on the ticket received from the zero trust network agent 112, and the ticket is used to establish a communication connection between the zero trust network agent 112 and the zero trust network gateway 103, and the zero trust network agent 112 proxies an access request for an access object of the zero trust network to be accessed by a user who is authenticated and logged in at the zero trust network client 113 through the communication connection, and the ticket includes a unified network identity of the user, and the unified network identity of the user includes at least information of the user's user device, the identity of the user who is authenticated and logged in at the zero trust network client 113, and information of the access object that the user wants to access.
[0078] In some embodiments, the zero-trust network server 102 may receive a verification request for a ticket. A ticket is a credential for mutual access between objects in a zero-trust network. Among them, the zero-trust network gateway 103 may issue the verification request based on the ticket received from the zero-trust network agent 112. The ticket may be used to establish a communication connection between the zero-trust network agent 112 and the zero-trust network gateway 103, so that the zero-trust network agent 112 may proxy the zero-trust network client 113 to authenticate and log in the user's access request for the access object of the zero-trust network through the communication connection. The user's authentication login at the zero-trust network client 113 may include quick login, SMS verification code login, PIN+Token login (PIN (Personal identification number) is a fixed personal password, and Token is a dynamic token. Such a combination of dynamic and static authentication login methods can greatly improve the security of access and prevent the leakage of internal important information), instant messaging enterprise software scan code login (for example, login by confirming at the terminal after scanning the code), and other login methods.
[0079] In some embodiments, the ticket may include a unified network identity of the user, which may include at least information about the user's user device, the identity of the user authenticated and logged in at the zero-trust network client 113, and information about the access object that the user wants to access. Among them, the information about the user's user device mainly refers to the basic information of various computer terminal devices (including mobile and fixed terminals) used by the user, which may include the type information, location information, Wi-Fi list information, MAC (Media Access Control) address, CPU (Central Processing Unit) information, memory information, SD card (Secure Digital Memory Card) information, operating system version, etc. of the user's device; the authentication of the identity of the user logged in at the zero-trust network client 113 may include static password authentication, dynamic password authentication, biometric authentication, etc.; the information about the access object that the user wants to access may include the name, domain name, or IP (Internet Protocol) address of the access object, etc. The unified network identity of the user may also include other information. In one example, the unification of the identity of the user in the zero-trust network may include the unification of the identity in the user, device, software, business system, etc.
[0080] In the zero-trust network architecture, the access control policy focuses on fine-grained detection of whether a single access request complies with the user identity, access rights, and dynamic security rules (different access methods are implemented in different environmental states, such as normal access through the gateway, access after secondary authentication, blocking, etc.). As long as these conditions are met, the request initiated by the access subject can achieve the access method corresponding to the access control policy. However, the access control policy only focuses on the legitimacy of the identity and the access rights to business sites, data, APIs and other resources that the user identity has. In order to achieve the unification of user identities in the zero-trust network, the zero-trust network client, zero-trust network server, zero-trust network agent, and zero-trust network gateway are required to perform detection together.
[0081] Zero-trust network agents can set browser proxies (i.e., agent auto-configuration proxy mode, or custom proxy mode, which only affects browser-type application access, while independent client / server applications are not affected by browser system proxies) or full-traffic hijacking mode (all applications are affected). Users access intranet data or business sites through a large number of different types of applications, and set different authentication methods at different business sites, APIs, etc. These points are combined to form a variety of different ways to access resources, including but not limited to the following two categories.
[0082] Category 1: In an enterprise environment, there are generally a large number of intranet sites, and users have the actual access requirements of "single-point authentication, multiple-point access". Therefore, the zero-trust network gateway provides these intranet sites with the functions of unified user login and authentication, and uniformly performs user identity authentication and authorization. For this type of resources, when a user initiates an access request to access the target site from his device, the access request can be sent to the zero-trust network gateway via the zero-trust network agent, and the zero-trust network gateway takes over the unified login authentication. After the zero-trust network gateway passes the user's unified login authentication (the zero-trust network gateway receives the identity information sent by the user and verifies the user's identity through a unified authentication service), the relevant identity information and encrypted signature are passed to the business site in the request header (for security design, the business site generally detects the source of external requests, chooses to trust only the access requests from the zero-trust network gateway and ignores the access requests from non-zero-trust network gateways). After the business site obtains the user information, if the detection is successful, the user successfully logs in to the business site and shares the login state between multiple business systems (for example, when the user logs in to site A, he automatically logs in to site B, thereby achieving single sign-on).
[0083] The second category: The method of using independent applications to request APIs, data and other resources can be to first hijack the access traffic through the zero-trust network agent, and then initiate traffic authentication to the zero-trust network client based on the traffic quintuple (source IP or domain name, source port, destination IP or domain name, destination port, and network protocol), application process identifier and other information. After the zero-trust network client communicates with the zero-trust network server, combined with the access control policy, the subject identity corresponding to the access request is marked with the login user identity of the zero-trust network client, and at the same time, the access permission corresponding to the login user identity of the zero-trust network client is used to determine whether the authentication request is successfully passed.
[0084] Combining the above two types of access methods, it is found that in the specific implementation process, a variety of different access methods for intranet resources can control user network access based on different user identities. In one example, a user who logs in through a zero-trust network client in a single device is expected to access the corresponding intranet data in various ways according to a unified network identity. If there is an inconsistency in user identity, the attacker may have performed malicious behaviors such as lateral attacks in a detected trusted device environment by impersonating the attacker or using leaked information of other users, which is obviously inconsistent with the access behavior of normal users. If post-event logs, attack path analysis and tracing are used, the losses caused to the enterprise by malicious behavior cannot be prevented.
[0085] Therefore, in order to promptly identify abnormal resource access behavior, and to detect anomalies and automatically intervene in the access process in a timely manner through differences with the expected user's access behavior, it is necessary to bind the user's device information, the user's identity authenticated and logged in on the zero-trust network client, and the information of the access object that the user wants to access to form a logically unified network access identity. At the same time, it is necessary to ensure that the identity of the user subject who accesses enterprise resources in different ways remains consistent.
[0086] At step S220, the ticket is verified based on the verification request to obtain a verification result, wherein the verification of the ticket based on the verification request includes: verifying whether the identity of the access object accessed in different ways in the user device is consistent, and verifying whether the user's unified network identity is pre-specified in the zero-trust network server 102.
[0087] After receiving the verification request for the ticket, the zero-trust network server 102 verifies the ticket based on the verification request to obtain a verification result. In some embodiments, after receiving the ticket sent by the zero-trust network gateway 103, the zero-trust network server 102 verifies the ticket, for example, comparing the ticket sent by the zero-trust network gateway 103 with the ticket stored in the zero-trust network server 102 itself (in other words, verifying whether the unified network identity of the user contained in the ticket is pre-specified in the zero-trust network server 102). When the two are consistent, it is determined that the verification is successful, and a verification result representing the successful verification is returned to the zero-trust network gateway 103; when the two are inconsistent, it is determined that the verification failed, and a verification result representing the failure of the verification is returned to the zero-trust network gateway 103. As an example, when the zero-trust network gateway 103 receives the verification result representing the failure of the verification returned by the zero-trust network server 102, the communication connection with the zero-trust network agent 112 can be disconnected, so that the zero-trust network agent 112 directly forwards the access request to the corresponding business server 105 through the physical network card.
[0088] In some embodiments, verifying the ticket based on the verification request may include verifying whether the identities of the user device accessing the access object in different ways are consistent. The "different ways" refer to different media accessed by the user. For example, the "different ways" may include the user accessing the corresponding access object by logging into an instant messaging application and the user accessing the corresponding access object by logging into a browser. In some embodiments, verifying whether the identities of the user device accessing the access object in different ways are consistent may include at least one of the following: verifying whether the identities of the user accessing the access object through different applications in the user device are consistent (for example, whether the identities of the user accessing the corresponding access object by logging into an instant messaging application and the user accessing the corresponding access object by logging into a browser as described above are consistent); verifying whether the identity of the user accessing the access object through an application in the user device is consistent with the identity of the user authenticated and logged in by the zero-trust network client 113 (for example, whether the identity of the user accessing the corresponding access object by logging into a browser is consistent with the identity of the user authenticated and logged in by the zero-trust network client 113). If they are consistent, the verification is successful; otherwise, if they are inconsistent, the verification fails.
[0089] In some embodiments, verifying the ticket based on the verification request may further include verifying whether the unified network identity of the user is pre-specified in the zero-trust network server 102. The "pre-specified" means that the unified network identity of the user is pre-configured in the zero-trust network server 102. If the unified network identity of the verified user is consistent with the unified network identity of the user pre-configured in the zero-trust network server 102, it means that the verification is successful; conversely, if the unified network identity of the verified user is inconsistent with the unified network identity of the user pre-configured in the zero-trust network server 102, it means that the verification fails.
[0090] It should be noted that the zero-trust network server 102 should verify the ticket based on the verification request, and should verify whether the identity of the access object accessed in different ways in the user device is consistent, and whether the user's unified network identity is pre-specified in the zero-trust network server 102. Such a double verification method makes the user's access to the zero-trust network more reliable and secure.
[0091] At step S230, based on the verification result, a corresponding processing operation is performed to control the user's access to the access object of the zero-trust network.
[0092] In some embodiments, the association between the verification result and the corresponding processing operation can be pre-stored and set in the zero-trust network server 102. When the verification result is received, the zero-trust network server 102 can find the corresponding processing operation to match it. For example, when the verification is successful, it means that the user identity of this access meets the security requirements, and the user can access the intranet system based on the successful verification result.
[0093] In some embodiments, step S230 may include: sending the verification result to the zero-trust network gateway 103, so that the zero-trust network gateway 103 performs corresponding processing operations based on the verification result. For example, when the zero-trust network service end 102 successfully verifies the ticket sent by the zero-trust network gateway 103, the zero-trust network agent end 112 forwards the access request sent by the hijacked application to the zero-trust network gateway 103, so as to access the target business site through the zero-trust network gateway 103. Afterwards, after receiving the access request sent by the zero-trust network agent end 112, the zero-trust network gateway 103 forwards the access request to the corresponding business server 105 according to the destination IP address or domain name carried in the access request (i.e., the IP address or domain name corresponding to the business server 105). By utilizing the zero-trust network gateway, access control can be made more effective.
[0094] In some embodiments, the sending of the verification result to the zero-trust network gateway 103 so that the zero-trust network gateway 103 performs a corresponding processing operation based on the verification result may include: in response to the identity of the access object accessed in different ways in the user device being inconsistent, or the user's unified network identity being not pre-specified, sending the verification failure as the verification result to the zero-trust network gateway 103 so that the zero-trust network gateway 103 performs a verification failure processing operation. In other words, as long as the verification result shows that there is an identity inconsistency, the verification failure processing operation can be performed. This avoids the potential risk caused by the theft of the user's identity.
[0095] In some embodiments, the verification failure processing operation may include: causing the zero-trust network client 113 to execute at least one of a pop-up box alarm, disconnecting the network connection with the zero-trust network agent 112, and forcing the user to log out of the authentication login of the zero-trust network client 113. The pop-up box alarm means that the zero-trust network client 113 sends an alarm message to the user's device interface in a pop-up box to let the user know that the verification has failed; disconnecting the network connection with the zero-trust network agent 112 means disconnecting the user's device and being unable to further access the information of the business system; forcing the user to log out of the authentication login of the zero-trust network client 113 means logging out of the user's authenticated identity on the zero-trust network client 113. In this way, the risks found can be handled in a timely manner to avoid causing greater losses.
[0096] In order to better understand the above steps S210-S230, Figure 3A-3D Some example interfaces of zero trust network are shown by way of example. Figure 3A A schematic diagram schematically shows a scenario in which a user queries device information on a zero-trust network client according to some embodiments of the present disclosure; Figure 3B A schematic diagram of an access scenario of a zero-trust network in a normal access state according to some embodiments of the present disclosure is schematically shown; Figure 3C A schematic diagram of access scenarios of a zero-trust network in an abnormal access state according to some embodiments of the present disclosure is schematically shown; Figure 3D An example pop-up alert interface when abnormal information in a zero-trust network is detected according to some embodiments of the present disclosure is schematically shown.
[0097] like Figure 3AAs shown, there is an ownership relationship between the user and the device that accesses the business system resources. The user can find a list of all devices belonging to him / her in the zero-trust network client of any device, and can perform renewal and logout operations. Specifically, when the user "×××" uses the local machine (i.e., the system Windows 10ProfessionalBit-64) to log in to the zero-trust network client, the device status column will show online, which means that the user has successfully logged in to the zero-trust network client. The zero-trust network client will also record and display the user's most recent login time and login validity period, and the user can renew or log out based on this. Similarly, when the user "×××" uses other devices (i.e., the system macOS 12.5.1) to log in to the zero-trust network client, the above content will also be displayed. In some examples, the user may also have other devices, so all the user's associated devices can be uniformly managed and displayed through "batch management".
[0098] like Figure 3B As shown, the network access environment of the device is ensured to be safe through security detection of identity, device and software. The information of the user's user device, the identity of the user authenticated and logged in at the zero-trust network client 113, and the information of the access object to be accessed by the user form a logical unified network identity of the user, and continuous detection can be performed before and during the access. Figure 3B The interface is the interface that presents the security status after the user successfully logs in and accesses the zero-trust network client. "The current security status is normal, and enterprise resources can be accessed" means that the logged-in user has the right to access the business system or intranet resources. At the same time, "Continuously detect each access request" reminds the user that the zero-trust network is continuously detecting each user's access request to prevent user information from being stolen or intranet resources from being stolen. Specifically, the "√" symbol is used to indicate the status of authentication and access security; "Normal identity" detected can include the normal strength of the email account password and the consistency of the zero-trust network login identity with the business system login identity; "Device security" detected can include normal system reinforcement, software security, and network configuration security; "Normal software access" detected can include the trustworthiness of the software publisher and normal software access behavior. Users can view specific access and protection information by clicking "Authentication details", "Device reinforcement details" and "Software access details".
[0099] like Figure 3C As shown, if the zero-trust network client account logged in by a common login device is different from the login identity of the current device, the user will be prompted that the identities of all associated devices are abnormal. Figure 3CThe interface is the interface that presents security risks after the user successfully logs in and accesses the zero-trust network client. "Your system currently has security risks" means that the access status is abnormal, and the logged-in user has no right to access the business system or intranet resources. Specifically, the "√" symbol is used to indicate the state of passing authentication and access security, and the "×" symbol is used to indicate the state of not passing authentication and having security risks. Identity, device, and software may all be abnormal. Here, the scenario of identity abnormality and device and software security is used as an example. Detection of "identity abnormality" may include not authorizing others to log in to the zero-trust network and business system account despite identity security authentication; detection of "device security" may include device standardization, device security without vulnerabilities, and normal system security reinforcement detection; detection of "normal software access" may include software publisher trustworthiness and legal software access behavior. Users can view specific access and protection information by clicking "Authentication Details", "Device Reinforcement Details", and "Software Access Details".
[0100] like Figure 3D As shown in the figure, when access anomalies occur in a zero-trust network, users are notified through a pop-up box alarm. Figure 3D In the interface, it is displayed that "The following 1 abnormality is detected, which may cause network connection abnormality. It is recommended to handle it." Users can click "View details" to view the cause of the network connection abnormality this time, and can click "Repair now" to restore the network connection.
[0101] Figure 4 A flowchart of a method for access control of a zero-trust network according to some embodiments of the present disclosure is schematically shown.
[0102] like Figure 4 As shown in , the access control method of the zero-trust network according to some embodiments of the present disclosure may also include:
[0103] S410, receiving a ticket request from the zero-trust network client, where the ticket request is issued by the zero-trust network client based on an access request for an access object of the zero-trust network initiated by a user through an application, and includes a unified network identity of the user;
[0104] S420, in response to determining that the access request complies with a predetermined access control policy based on the ticket request, issuing a ticket to the zero trust network client so that the zero trust network client sends the ticket to the zero trust network agent, so that the zero trust network agent proxies the access request based on the ticket.
[0105] Steps S410-S420 are described in detail below. Steps S410-S420 may be performed by the zero-trust network server 102 and may be performed before steps S210-S230.
[0106] At step S410, a ticket request is received from the zero-trust network client 113, which is issued by the zero-trust network client 113 based on an access request for an access object of the zero-trust network initiated by the user through an application. In some embodiments, after receiving the authentication request sent by the zero-trust network agent 112, the zero-trust network client 113 extracts the request parameters carried in the authentication request, wherein the request parameters may include: the address and port of the application, the address and port of the business site, and the identifier of the application (such as the process identifier corresponding to the application, etc.); then, the zero-trust network client 113 may obtain the characteristic information of the application (such as the process information summary algorithm value corresponding to the application, the process path, the last modification time of the process, copyright information, signature information, etc.) based on the identifier of the application carried in the request parameters; then, the zero-trust network gateway 103 sends a ticket request to the zero-trust network client 113 (i.e., applies for a ticket to the zero-trust network server 102), wherein the ticket request carries the address and port of the application, the address and port of the business site, and the characteristic information of the application, and may include the user's unified network identity (as described above).
[0107] At step S420, in response to determining that the access request complies with a predetermined access control policy based on the ticket request, a ticket is issued to the zero trust network client 113 so that the zero trust network client 113 sends the ticket to the zero trust network agent 112, so that the zero trust network agent 112 proxies the access request based on the ticket. The predetermined access control policy is pre-stored in the zero trust network server 102. In some embodiments, after receiving the ticket request sent by the zero trust network client 113, the zero trust network server 102 processes the ticket request, and after the access request complies with the predetermined access control policy, generates a ticket corresponding to the access request sent by the application, and returns the ticket (and optionally the maximum number of uses of the ticket and the effective use time of the ticket) as a response to the zero trust network client 113. After receiving the ticket (and optionally the maximum number of uses of the ticket and the valid usage time of the ticket) returned by the zero trust network server 102, the zero trust network client 113 sends the ticket (and optionally the maximum number of uses of the ticket and the valid usage time of the ticket) as a response to the authentication request to the zero trust network agent 112, so that the zero trust network agent 112 proxies the access request based on the ticket.
[0108] Combine the following Figure 5Further explanation. Figure 5 The schematic diagram schematically shows the principle of the access control policy of the zero-trust network according to some embodiments of the present disclosure.
[0109] like Figure 5 As shown in the figure, through the zero-trust network, the access paths of users (i.e., access subjects) to resources (i.e., access objects, such as office resources, data resources, development and operation resources, the Internet, etc.) are converged. At the beginning, users are considered untrustworthy in any access environment, and only after filtering through the access control policy engine (control flow) are they converted to trusted access. Among them, the access control policy engine can include a unified policy decision point and a unified policy execution point. The unified policy decision point can be responsible for matching the information contained in the access request (such as user identity, request object, context, etc.) with the predetermined access control policy, and finally decide whether the request can be allowed; while the unified policy execution point can be responsible for actually controlling the access request after the decision of the unified policy decision point is completed, such as rejecting illegal requests, recording audit logs, etc. The unified policy execution point usually ensures that access control is implemented correctly. In this process, the policy is uniformly decided and executed, and then the data flow that meets the predetermined access control policy is sent to the access object. Control flow can usually be used to describe the access control process in a zero-trust network, that is, to filter, review, identify and authorize access requests through the access control policy engine, and finally decide whether the request is allowed to pass; in this process, various security devices and components in the zero-trust network (such as zero-trust network gateways, etc.) can participate in the control flow to protect and detect network traffic in real time. Zero-trust network agents and zero-trust network gateways provide a unified entry (data flow) for access subjects to request access to the resources of objects through the network. Data flow can usually be used to describe the data transmission process in the network, that is, the data traffic involved when requesting resources from access subjects to access objects. In a zero-trust network, after providing a unified entry for access subjects through zero-trust network agents and zero-trust network gateways, all data flows initiated by access subjects will be centrally managed and detected through zero-trust network agents and zero-trust network gateways to ensure that data is not accessed or tampered with without authorization, thereby enhancing data security and integrity. The zero-trust network server provides authentication (authentication refers to verifying whether the user has the right to access the system) operations for the unified entrance. Only network requests that pass the authentication are trusted. Then, the network requests that pass the authentication are forwarded by the zero-trust network agent to the zero-trust network gateway, which then proxies access to the actual business system.
[0110] Figure 6 A flowchart of a method for access control of a zero-trust network according to some embodiments of the present disclosure is schematically shown.
[0111] like Figure 6 As shown in , in some embodiments, in response to determining that the access request complies with a predetermined access control policy based on the ticket request, issuing a ticket to the zero trust network client in step S420 may include:
[0112] S610, verifying whether the identities of the user device accessing the access object in different ways are consistent;
[0113] S620, verifying whether the unified network identity of the user is consistent with predetermined access control list information, wherein the predetermined access control list information pre-specifies the unified network identity of the user that is allowed to access in the zero-trust network;
[0114] S630, in response to the identity of the user device accessing the access object in different ways being consistent, and the unified network identity of the user being consistent with the predetermined access control list information, determining that the access request complies with the predetermined access control policy;
[0115] S640, issuing a ticket to the zero trust network client.
[0116] At step S610, the verification method is substantially the same as that described in step S220.
[0117] At step S620, the predetermined access control list information may be pre-stored in the zero-trust network server 102. When verification is required, the user's unified network identity is compared to see whether it is the same as the predetermined access control list information pre-stored in the zero-trust network server 102. By pre-storing in this way, the efficiency of verification can be improved.
[0118] At step S630, when the identities of the access objects accessed in different ways in the user device are consistent, and the user's unified network identity is consistent with the predetermined access control list information, it is determined that the access request complies with the predetermined access control policy. This can further increase the security of the zero-trust network.
[0119] At step S640 , when it is determined that the access request complies with the predetermined access control policy, the zero trust network server 102 issues a ticket to the zero trust network client 113 .
[0120] In some embodiments, the access control list information may be constructed in the following manner: associating the information of multiple user devices of the user with the identity of the user authenticated and logged in at the zero-trust network client 113 to form a device ownership relationship; obtaining the information of the access objects that the user is allowed to access through the multiple user devices; and obtaining the access control list information based on the device ownership relationship and the information of the access objects that the multiple user devices are allowed to access. The access control list information may include website URLs, IP addresses, etc.
[0121] In some embodiments, and with reference to Figure 3A Within the framework of zero-trust network access, standard devices within the enterprise (these standard devices can be considered as one of the more trusted terminal devices after being reviewed and verified by the organization's internal security policies. The organization can ensure their security by controlling access to them and conducting continuous testing), user-owned devices, and devices accessed by third-party organizations are all allowed to access, provided that they pass the verification and standardization process of various rules. The standardization process includes mobile device management (it provides complete mobile device life cycle management from device registration, activation, use, and elimination), device standardization, etc. In this process, a corresponding relationship between devices and access subjects can be established. Enterprise administrators can formulate different levels of control rules for different types of devices, and both users and administrators can decide the time period for the device to be controlled: for devices temporarily used for resource access, a shorter control period can be set; for office equipment within the enterprise, a longer control period can be set. With the changes in the position adjustment, entry and resignation of enterprise users, the ownership relationship between users and devices can change accordingly. Users can maintain and delete the ownership relationship through renewal and cancellation, and enterprise administrators can forcibly isolate or remove devices associated with corresponding users from the enterprise network. During the control period, users can view a list of all their devices, device status, last login time, and control deadline in the zero-trust network client on any device.
[0122] In one example, in a secure network access environment, all devices D1, D2, D3…Dn belonging to user A constitute a set D. During the device control period, it should be through the identity of the corresponding user A (the user identity logged in on the zero-trust network client is A), and no matter how the resource is accessed, the subject identity corresponding to the session received on the zero-trust network gateway side is A. Therefore, if user B logs in on device D2, because the logged-in user identity is B, not user A, the user access environment is considered unsafe. In another example, if user A in device D1 accesses resource oa1.com, and although user A logs in to the zero-trust network client in device D2, user B logs in to site oa2.com in a browser application, and both oa1.com and oa2.com are in the list of business systems associated with devices and users issued by the administrator, the user access environment is considered unsafe. In another example, if oa3.com is not in the business system list, the user logged into the zero-trust network client in device D2 is user A, and user B logged into the site oa3.com in a browser application, then the user access environment is considered safe.
[0123] In order to more efficiently and safely complete the process of network access environment association detection, automatic intervention and self-help release of access subjects, a security operation center platform can also be set up. Figure 7 The interactive process diagram of a zero-trust network including a security operation center platform according to some embodiments of the present disclosure is schematically shown.
[0124] The following describes Figure 7 The functions and effects of each module in the Figure 7As shown, the zero-trust network client may include: an audit data reporting module, which is configured to report the operating data of user operations or clicks to the zero-trust network server; a security incident handling reporting module, which is configured to detect whether the security incident is operated by an authenticated logged-in user, and report the handling result of the security incident to the zero-trust network server; a server-side push command execution module, which is configured to push messages to the zero-trust network server; and a terminal user interaction module, which is configured to interact with the user on the terminal. The zero-trust network server may include: a management interface module, which is configured to receive operation instructions issued by an administrator on the zero-trust network management terminal, wherein the management terminal includes a control page, on which the administrator can configure parameters and then view the results, send the required parameters and commands to the terminal through the zero-trust network server, display the results to the management terminal, and then the administrator views the results through the data in the database of the zero-trust network server; a security event management module, which is configured to receive data pushed by the security operation center platform and the data of the zero-trust network server, and is responsible for pushing security events to the specified terminal or all terminals belonging to the specified user; a user device attribution maintenance module, which is configured to maintain a list of user device information to form a binding relationship between the user and his device; a client processing status synchronization module, which is configured to synchronize the operation of the zero-trust network client with the zero-trust network server, receive the terminal's processing and update the processing status of the security event (work order); an access control policy module, which is configured to pre-store corresponding access control policies. The Security Operation Center (SOC) platform may include: a data collection module configured to collect data from a zero-trust network server and a zero-trust network gateway; an expert rule module configured to regularly formulate and update rules by an expert team that understands the business environment and has experience; a work order processing module configured to generate and process security work orders in the presence of alarm data; and a security event push module configured to push identified security events to the zero-trust network server. The zero-trust network gateway may interact with the Security Operation Center platform.
[0125] In some embodiments, after the zero-trust network gateway forwards the traffic sent from the zero-trust network agent, the access subject identity corresponding to the access session is aggregated to the security operation center platform in the device dimension through centralized or scheduled sending. The "device dimension" refers to combining the user's identity information and device information, and performing data statistics and analysis on the device as the basic unit. For example, when a user logs in using multiple devices, the user's identity can be identified based on the device's unique identifier. In this case, aggregating by device dimension can help the security operation center platform better understand the usage and security risks of each device, promptly detect and handle unsafe behaviors, and protect user data security and privacy.
[0126] In some embodiments, the access control method of the zero-trust network may also include: receiving a security work order from a security operation center platform, the security work order including exception information, the exception information indicating that the identity of the access object accessed in different ways in the user device is inconsistent or indicating that the unified network identity of the user between different user devices is inconsistent, and is generated by the security operation center platform based on information related to the access request received from the zero-trust network gateway (for example, identity information related to the access session); sending the exception information to the zero-trust network client, so that the zero-trust network client displays the exception information to the user. The method steps described can be performed by the zero-trust network server. Therefore, using the security operation center platform, abnormal situations in the access process can be displayed to the user in a timely manner, so that the user can handle them according to the situation.
[0127] In some embodiments, the sending of the exception information to the zero-trust network client so that the zero-trust network client displays the exception information to the user may include: confirming whether the exception information matches the verification result; in response to the exception information matching the verification result, sending the exception information to the zero-trust network client so that the zero-trust network client displays the exception information to the user. This is equivalent to performing a double verification process, making access to the business system safer and more reliable.
[0128] In some embodiments, the access control method of the zero-trust network may further include: receiving the processing result of the abnormal information from the user; synchronizing the processing result to the security operation center platform to update the processing status of the security work order. Through such continuous synchronization and updating, continuous detection during the access process is better achieved.
[0129] As an example, the authenticated login identity of user A's device D3 is A, but the identity accessing the hr.oa.com business site is B. Therefore, the zero-trust network gateway synchronizes with the SOC platform, and the SOC platform pushes an alarm message to the active devices belonging to user A via the zero-trust network server: "It is detected that your device has abnormal risk behavior of logging into hr.oa.com." If it is the authenticated user himself, this alarm message can be closed; if it is the unauthenticated user himself, the login state of the zero-trust network needs to be cancelled. If the user chooses not to operate himself, he needs to cancel the login state in device D3, or cancel the association between the user and the device (device D3 enters the isolation network, and then normally connects to the enterprise network after eliminating the risk), otherwise it cannot normally access other business system resources or cannot access the business system intranet. The zero-trust network client reports the user's repair results for the security incident to the zero-trust network server, which is then synchronized to the SOC platform via the zero-trust network server. The SOC platform combines the zero-trust network gateway data and the zero-trust network server data to identify that the authenticated login identity is consistent in all devices associated with the user, and pushes the status recovery command to the specified terminal via the zero-trust network server. The terminal eventually switches back to the normal network access environment status.
[0130] Figure 8 FIG. 1 is a schematic diagram schematically showing an architecture of an access control system for a zero-trust network according to some embodiments of the present disclosure. Figure 8 As shown, the complete access process of users to business servers is displayed in ascending order of numbers. The zero-trust network server is mainly used to securely schedule business traffic through the policy control engine, and to authorize according to the granularity of people-devices-business systems-applications. Among them, the zero-trust network server can be used to verify the identity of the accessing user, verify the hardware information of the device and the security information of the device, and detect whether the application process is safe (for example, whether there are vulnerabilities, whether there are viruses and Trojans, etc.). In addition, the zero-trust network server will regularly initiate file inspections to the threat intelligence cloud check service (for example, Anzhi) or the antivirus engine. When a malicious process is identified, an asynchronous blocking operation will be performed through the zero-trust network client.
[0131] As an example, the overall zero-trust network access process can be carried out as follows: when the access subject initiates a network access request for the access object through an application, in step ①, the zero-trust network client first hijacks the network access request (pid-url) initiated by the application through the zero-trust network agent; in step ②, the zero-trust network agent initiates an authentication request to the zero-trust network client (that is, the zero-trust network agent applies to the zero-trust network client for a ticket for this network access request), where the request parameters include the source IP or domain name, source port, destination IP or domain name, destination port, and the process identifier (PID, Process Identifier) corresponding to the application IDentification); in step ③, the zero-trust network client obtains the process characteristics; in step ④, the zero-trust network client collects the information summary algorithm, process path, process last modification time, copyright information and signature information of the process through the PID sent by the zero-trust network agent, together with the source IP or domain name, source port, destination IP or domain name and destination port carried in the network access request sent by the zero-trust network agent, and applies to the zero-trust network server for ticket replacement; in step ⑤, the zero-trust network client sends the process characteristics to the zero-trust network server for process inspection; in step ⑥, if the ticket application is successful, the zero-trust network client returns the ticket, the maximum number of times the ticket is used and the validity period of the ticket as a response to the zero-trust network agent; in step ⑦, the zero-trust network agent can initiate Https (Hypertext Transfer Protocol) to the zero-trust network gateway Secure, secure hypertext transfer protocol) request, the authorization (Authorization) header field of the request carries the ticket returned by the zero-trust network client (i.e., the network request credential); in step ⑧, after receiving the Https request sent by the zero-trust network agent, the zero-trust network gateway parses the ticket in the header field, and requests the zero-trust network server to verify the ticket, the ticket can be generated in steps ④ and ⑤ in this visit or in the previous visit, and is used to establish a communication connection between the zero-trust network agent and the zero-trust network gateway, the zero-trust network agent agent authenticates and logs in the zero-trust network client through the communication connection to access the access object of the zero-trust network, and includes the user's unified network identity, the user's unified network identity at least includes the user device information of the user, the identity of the user authenticated and logged in at the zero-trust network client, and the information of the access object that the user wants to access;In step ⑨, the zero-trust network server verifies the ticket based on the verification request to obtain a verification result, wherein the verification of the ticket based on the verification request may include verifying whether the identities of the access objects accessed in different ways in the user device are consistent and verifying whether the unified network identity of the user is pre-specified in the zero-trust network server, and then the zero-trust network gateway receives the verification result returned by the zero-trust network server. If the verification is successful, a connection is successfully established between the zero-trust network gateway and the zero-trust network agent, and then the zero-trust network agent can send the network access request initiated by the hijacked application to the zero-trust network gateway; in step ⑩, the zero-trust network gateway forwards the request to the corresponding business server and acts as an agent for the actual access request; in step; In step , the business server returns the response result to the zero trust network gateway; In step 1, the zero-trust network gateway returns the response result to the zero-trust network agent; in step 2 In the process, the zero trust network agent returns the response result to the application.
[0132] In this way, using the access control method of the zero-trust network according to some embodiments of the present disclosure, the zero-trust network server verifies the ticket based on the received verification request to verify whether the identity of the access object accessed in different ways in the user device is consistent and whether the user's unified network identity (which at least includes the information of the user's user device, the identity of the user authenticated and logged in in the zero-trust network client, and the information of the access object to be accessed by the user) is pre-specified in the zero-trust network server, thereby performing corresponding processing operations based on the verification results to control the user's access to the access object of the zero-trust network. Through such a verification method, continuous detection can be performed during the access process, and automatic intervention can be performed when abnormal information and behavior are found, thereby realizing an efficient method for self-checking the security of the network access environment, reducing the risk of data leakage caused by attackers stealing identity information, reducing problems such as leakage of sensitive information, and improving the accuracy of security protection, enhancing the availability and security of the zero-trust network.
[0133] Fig. 9 An example block diagram of an access control device 900 for a zero-trust network according to some embodiments of the present disclosure is schematically shown. Fig. 9 The access control device 900 for determining a zero-trust network shown in FIG. 9 may correspond to Figure 1 The terminal device 110 shown in .
[0134] like Fig. 9As shown in , the access control device 900 of the zero-trust network may include a receiving module 910, a verification module 920, and a processing module 930. The receiving module 910 may be configured to receive a verification request for a ticket, wherein the verification request is issued by the zero-trust network gateway based on the ticket received from the zero-trust network agent, and the ticket is used to establish a communication connection between the zero-trust network agent and the zero-trust network gateway, and the zero-trust network agent agent is an access request for the access object of the zero-trust network by the user who authenticates and logs in to the zero-trust network client through the communication connection, and the ticket includes the unified network identity of the user, and the unified network identity of the user includes at least the information of the user device of the user, the identity of the user authenticated and logged in to the zero-trust network client, and the information of the access object to be accessed by the user. The verification module 920 may be configured to verify the ticket based on the verification request to obtain a verification result, wherein the verification of the ticket based on the verification request includes: verifying whether the identity of the user device accessing the access object in different ways is consistent, and verifying whether the unified network identity of the user is pre-specified on the zero-trust network server. The processing module 930 may be configured to perform corresponding processing operations based on the verification result to control the user's access to the access object of the zero-trust network.
[0135] In the access control device of the zero-trust network according to some embodiments of the present disclosure, the zero-trust network server verifies the ticket based on the received verification request to verify whether the identity of the access object accessed in different ways in the user device is consistent and whether the user's unified network identity (which at least includes the information of the user's user device, the identity of the user authenticated and logged in in the zero-trust network client, and the information of the access object to be accessed by the user) is pre-specified in the zero-trust network server, so as to perform corresponding processing operations based on the verification results to control the user's access to the access object of the zero-trust network. Through such a verification method, continuous detection can be performed during the access process, and automatic intervention can be performed when abnormal information and behavior are found, thereby realizing an efficient method for self-checking the security of the network access environment, reducing the risk of data leakage caused by attackers stealing identity information, reducing problems such as leakage of sensitive information, and improving the accuracy of security protection, and enhancing the availability and security of the zero-trust network.
[0136] It should be noted that the various modules described above can be implemented in software or hardware or a combination of the two. Multiple different modules can be implemented in the same software or hardware structure, or one module can be implemented by multiple different software or hardware structures.
[0137] Fig.10An example block diagram of a computing device 1000 according to some embodiments of the present disclosure is schematically shown. The computing device 1000 may represent a device for implementing the various means or modules described herein and / or performing the various methods described herein. The computing device 1000 may be, for example, a server, a desktop computer, a laptop computer, a tablet, a smart phone, a smart watch, a wearable device, or any other suitable computing device or computing system, which may include various levels of devices ranging from full-resource devices with a large amount of storage and processing resources to low-resource devices with limited storage and / or processing resources. In some embodiments, the above description of the computing device 1000 may be a computer system that can be used to implement the various means or modules described herein and / or perform the various methods described herein. Fig. 9 The described zero-trust network access control apparatus 900 may be implemented in one or more computing devices 1000 , respectively.
[0138] like Fig.10 As shown in , the example computing device 1000 includes a processing system 1001, one or more computer-readable media 1002, and one or more I / O interfaces 1003 that are communicatively coupled to each other. Although not shown, the computing device 1000 may also include a system bus or other data and command transmission system that couples various components to each other. The system bus may include any one or combination of different bus structures, such as a memory bus or memory controller, a peripheral bus, a universal serial bus, and / or a processor or local bus that utilizes any of a variety of bus architectures. Alternatively, it may also include control and data lines.
[0139] Processing system 1001 represents the functionality of performing one or more operations using hardware. Thus, processing system 1001 is illustrated as including hardware elements 1004 that may be configured as processors, functional blocks, etc. This may include other logic devices implemented in hardware as application specific integrated circuits or formed using one or more semiconductors. Hardware elements 1004 are not limited by the materials from which they are formed or the processing mechanisms employed therein. For example, a processor may be composed of (multiple) semiconductors and / or transistors (e.g., electronic integrated circuits (ICs)). In such a context, processor executable instructions may be electronic executable instructions.
[0140] The computer-readable medium 1002 is illustrated as including a memory / storage device 1005. The memory / storage device 1005 represents a memory / storage device associated with one or more computer-readable media. The memory / storage device 1005 may include volatile media (such as random access memory (RAM)) and / or non-volatile media (such as read-only memory (ROM), flash memory, optical disk, magnetic disk, etc.). The memory / storage device 1005 may include fixed media (e.g., RAM, ROM, fixed hard disk drive, etc.) and removable media (e.g., flash memory, removable hard disk drive, optical disk, etc.). Exemplarily, the memory / storage device 1005 may be used to store the first audio of the first category of users mentioned in the above embodiment, the queue list of requests, etc. The computer-readable medium 1002 may be configured in various other ways as further described below.
[0141] One or more I / O (input / output) interfaces 1003 represent functions that allow a user to type commands and information into the computing device 1000 and also allow information to be displayed to the user and / or sent to other components or devices using various input / output devices. Examples of input devices include keyboards, cursor control devices (e.g., mice), microphones (e.g., for voice input), scanners, touch functions (e.g., capacitive or other sensors configured to detect physical touch), cameras (e.g., visible or invisible wavelengths (such as infrared frequencies) can be used to detect motion that does not involve touch as gestures), network cards, receivers, and the like. Examples of output devices include display devices (e.g., displays or projectors), speakers, printers, tactile response devices, network cards, transmitters, and the like. Exemplarily, in the embodiments described above, the first category of users and the second category of users can input through the input interfaces on their respective terminal devices to initiate requests and record audio and / or video, etc., and can view various notifications and watch videos or listen to audio, etc., through the output interfaces.
[0142] The computing device 1000 also includes a zero-trust network access control policy 1006. The zero-trust network access control policy 1006 can be stored in the memory / storage device 1005 as a computing program instruction, or can be hardware or firmware. The zero-trust network access control policy 1006 can be implemented together with the processing system 1001, etc. Fig. 9 The entire functions of each module of the zero-trust network access control device 900 are described.
[0143] Various techniques may be described herein in the general context of software, hardware, elements, or program modules. Typically, these modules include routines, programs, objects, elements, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The terms "module," "function," etc., as used herein, generally represent software, firmware, hardware, or a combination thereof. The features of the techniques described herein are platform-independent, meaning that these techniques can be implemented on a variety of computing platforms with a variety of processors.
[0144] An implementation of the described modules and techniques may be stored on or transmitted across some form of computer-readable media. Computer-readable media may include various media accessible by computing device 1000. By way of example and not limitation, computer-readable media may include “computer-readable storage media” and “computer-readable signal media”.
[0145] In contrast to a simple signal transmission, carrier wave, or signal itself, "computer-readable storage medium" refers to a medium and / or device capable of persistently storing information, and / or a tangible storage device. Therefore, a computer-readable storage medium refers to a non-signal-bearing medium. Computer-readable storage media include hardware such as volatile and non-volatile, removable and non-removable media and / or storage devices implemented in a method or technology suitable for storing information (such as computer-readable instructions, data structures, program modules, logic elements / circuits, or other data). Examples of computer-readable storage media may include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical storage device, hard disk, cassette, magnetic tape, magnetic disk storage device or other magnetic storage device, or other storage device, tangible medium, or article of manufacture suitable for storing desired information and accessible by a computer.
[0146] "Computer readable signal media" refers to signal bearing media that is configured to send instructions to the hardware of the computing device 1000, such as via a network. Signal media typically can embody computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave, data signal, or other transport mechanism. Signal media also includes any information transfer media. By way of example and not limitation, signal media include wired media such as a wired network or direct connection, and wireless media such as acoustic, RF, infrared, and other wireless media.
[0147] As previously described, hardware elements 1004 and computer-readable media 1002 represent instructions, modules, programmable device logic, and / or fixed device logic implemented in hardware form, which in some embodiments can be used to implement at least some aspects of the technology described herein. Hardware elements may include integrated circuits or systems on a chip, application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), complex programmable logic devices (CPLDs), and other implementations in silicon or components of other hardware devices. In this context, hardware elements can be used as processing devices for executing program tasks defined by instructions, modules, and / or logic embodied by hardware elements, as well as hardware devices for storing instructions for execution, such as the computer-readable storage media described previously.
[0148] The aforementioned combination may also be used to implement various techniques and modules described herein. Therefore, software, hardware or program modules and other program modules may be implemented as one or more instructions and / or logic embodied on some form of computer-readable storage medium and / or by one or more hardware elements 1004. Computing device 1000 may be configured to implement specific instructions and / or functions corresponding to software and / or hardware modules. Therefore, for example, by using a computer-readable storage medium and / or hardware element 1004 of a processing system, a module may be implemented as a module executable by computing device 1000 as software, at least in part, in hardware. Instructions and / or functions may be executed / operable by, for example, one or more computing devices 1000 and / or processing system 1001 to implement the techniques, modules and examples described herein.
[0149] The techniques described herein may be supported by these various configurations of computing device 1000 and are not limited to the specific examples of the techniques described herein.
[0150] In particular, according to an embodiment of the present disclosure, the process described above with reference to the flowchart can be implemented as a computer program. For example, an embodiment of the present disclosure provides a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program contains a program code for executing at least one step in the method embodiment of the present disclosure.
[0151] In some embodiments of the present disclosure, one or more computer-readable storage media are provided, on which computer-readable instructions are stored, and when the computer-readable instructions are executed, the access control method for the zero-trust network according to some embodiments of the present disclosure is implemented. The various steps of the access control method for the zero-trust network according to some embodiments of the present disclosure can be converted into computer-readable instructions through programming, thereby being stored in a computer-readable storage medium. When such a computer-readable storage medium is read or accessed by a computing device or a computer, the computer-readable instructions therein are executed by a processor on the computing device or the computer to implement the method described in some embodiments of the present disclosure.
[0152] In the description of this specification, the description of the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" etc. means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present disclosure. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner. In addition, those skilled in the art may combine and combine the different embodiments or examples described in this specification and the features of the different embodiments or examples, without contradiction.
[0153] Any process or method description in a flowchart or otherwise described herein may be understood to represent a module, segment or portion of code that includes one or more executable instructions for implementing the steps of a custom logical function or process, and the scope of the preferred embodiments of the present disclosure includes alternative implementations in which functions may not be performed in the order shown or discussed (including in a substantially simultaneous manner or in reverse order depending on the functions involved), which should be understood by technicians in the technical field to which the embodiments of the present disclosure belong.
[0154] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as an ordered list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by an instruction execution system, device or apparatus (such as a computer-based system, a system including a processor, or other system that can fetch instructions from an instruction execution system, device or apparatus and execute instructions), or in conjunction with such instruction execution systems, devices or apparatuses. For the purposes of this specification, "computer-readable medium" can be any device that can contain, store, communicate, propagate or transmit a program for use by an instruction execution system, device or apparatus, or in conjunction with such instruction execution systems, devices or apparatuses.
[0155] It should be understood that the various parts of the present disclosure can be implemented by hardware, software, firmware or a combination thereof. In the above-mentioned embodiments, a plurality of steps or methods can be implemented by software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented by hardware, it can be implemented by any one of the following technologies known in the art or a combination thereof: a discrete logic circuit having a logic gate circuit for implementing a logic function for a data signal, a dedicated integrated circuit having a suitable combination of logic gate circuits, a programmable gate array (Programmable Gate Array), a field programmable gate array (Field Programmable Gate Array), etc.
[0156] A person of ordinary skill in the art can understand that all or part of the steps of the above-mentioned embodiment method can be completed by hardware related to program instructions, and the program can be stored in a computer-readable storage medium, which, when executed, includes executing one or a combination of the steps of the method embodiment.
[0157] In addition, each functional unit in each embodiment of the present disclosure may be integrated into a processing module, or each unit may exist physically separately, or two or more units may be integrated into one module. The above-mentioned integrated module may be implemented in the form of hardware or in the form of a software functional module. If the integrated module is implemented in the form of a software functional module and sold or used as an independent product, it may also be stored in a computer-readable storage medium.
[0158] Although the present disclosure has been described in conjunction with some embodiments, it is not intended to be limited to the specific forms set forth herein. On the contrary, the scope of the present disclosure is limited only by the appended claims. Additionally, although individual features may be included in different claims, these may possibly be advantageously combined, and being included in different claims does not imply that the combination of features is not feasible and / or advantageous. The order of features in the claims does not imply any specific order in which the features must work. In addition, in the claims, the word "comprising" does not exclude other elements, and the term "one" or "an" does not exclude a plurality. The figure marks in the claims are provided only as clear examples and should not be interpreted as limiting the scope of the claims in any way.
[0159] It is understandable that in the specific implementation of the present disclosure, various data used for access control of zero-trust networks (such as information of user devices, identity of users authenticated and logged in to zero-trust network clients, etc.) are involved. When the embodiments involving such data described in the present disclosure are applied to specific products or technologies, user permission or consent is required, and the collection, use and processing of relevant data must comply with relevant laws, regulations and standards of relevant countries and regions.
Claims
1. A zero-trust network access control method, It is characterized in that The method is performed by a zero-trust network server, and the method includes: Receive a verification request for a ticket, wherein the verification request is issued by a zero-trust network gateway based on a ticket received from a zero-trust network agent, the ticket is used to establish a communication connection between the zero-trust network agent and the zero-trust network gateway, the zero-trust network agent agent proxies an access request for an access object of the zero-trust network by a user who is authenticated and logged in at the zero-trust network client through the communication connection, and the ticket includes a unified network identity of the user, and the unified network identity of the user includes at least information of a user device of the user, an identity of the user who is authenticated and logged in at the zero-trust network client, and information of an access object to be accessed by the user; Verifying the ticket based on the verification request to obtain a verification result, wherein the verification of the ticket based on the verification request includes: verifying whether the identities of the user device accessing the access object in different ways are consistent, and verifying whether the unified network identity of the user is pre-specified on the zero-trust network server; Based on the verification result, a corresponding processing operation is performed to control the user's access to the access object of the zero-trust network.
2. The method according to claim 1, further comprising: include: Receiving a ticket request from the zero-trust network client, the ticket request is issued by the zero-trust network client based on an access request for an access object of the zero-trust network initiated by a user through an application, and includes a unified network identity of the user; In response to determining that the access request complies with a predetermined access control policy based on the ticket request, a ticket is issued to the zero trust network client so that the zero trust network client sends the ticket to the zero trust network agent, so that the zero trust network agent proxies the access request based on the ticket.
3. The method according to claim 2, in, The step of issuing a ticket to the zero-trust network client in response to determining that the access request complies with a predetermined access control policy based on the ticket request includes: Verifying whether the identities of the user device accessing the access object in different ways are consistent; Verifying whether the unified network identity of the user is consistent with predetermined access control list information, wherein the predetermined access control list information pre-specifies the unified network identity of the user that is allowed to access in the zero-trust network; In response to the identity of the user device accessing the access object in different ways being consistent, and the unified network identity of the user being consistent with the predetermined access control list information, determining that the access request complies with the predetermined access control policy; A ticket is issued to the zero trust network client.
4. The method according to any one of claims 1 to 3, in, The verifying whether the identities of the user equipment accessing the access object in different ways are consistent includes at least one of the following: Verifying whether the identities of users who access the access object through different applications in the user device are consistent; Verify whether the identity of the user who accesses the access object through the application in the user device is consistent with the identity of the user authenticated and logged in on the zero-trust network client.
5. The method according to claim 3, in, The access control list information is constructed in the following manner: Associating information of the user's multiple user devices with the user's identity authenticated and logged in at the zero-trust network client to form a device ownership relationship; Acquire information of access objects that the user is allowed to access through the multiple user devices; The access control list information is obtained based on the device ownership relationship and the information of the access objects that the multiple user devices are allowed to access.
6. The method according to claim 1, in, The performing corresponding processing operations based on the verification result to control the user's access to the access object of the zero-trust network includes: The verification result is sent to the zero-trust network gateway so that the zero-trust network gateway performs corresponding processing operations based on the verification result.
7. The method according to claim 6, in, The step of sending the verification result to the zero-trust network gateway so that the zero-trust network gateway performs a corresponding processing operation based on the verification result includes: In response to the identity of the access object accessed in different ways in the user device being inconsistent, or the user's unified network identity being not pre-specified, the verification failure is sent as a verification result to the zero trust network gateway, so that the zero trust network gateway performs a verification failure processing operation.
8. The method according to claim 7, in, The verification failure processing operation includes: causing the zero-trust network client to execute at least one of a pop-up box alarm, disconnecting the network connection with the zero-trust network agent, and forcing the user to exit the authentication login of the zero-trust network client.
9. The method according to claim 1, further comprising: include: Receiving a security work order from a security operation center platform, the security work order including exception information, the exception information indicating that identities of the user device accessing the access object in different ways are inconsistent or indicating that unified network identities of users between different user devices are inconsistent, and generated by the security operation center platform based on information related to the access request received from the zero-trust network gateway; The exception information is sent to the zero-trust network client, so that the zero-trust network client displays the exception information to the user.
10. The method according to claim 9, in, The sending the exception information to the zero-trust network client so that the zero-trust network client displays the exception information to the user includes: Confirming whether the abnormal information matches the verification result; In response to the exception information matching the verification result, the exception information is sent to the zero-trust network client, so that the zero-trust network client displays the exception information to the user.
11. The method according to claim 10, further comprising: include: receiving a processing result for the abnormal information from the user; The processing result is synchronized to the security operation center platform to update the processing status of the security work order.
12. An access control device for a zero-trust network, include: A receiving module, configured to receive a verification request for a ticket, wherein the verification request is issued by a zero-trust network gateway based on a ticket received from a zero-trust network agent, the ticket is used to establish a communication connection between the zero-trust network agent and the zero-trust network gateway, the zero-trust network agent agent proxies an access request for an access object of the zero-trust network by a user who authenticates and logs in at the zero-trust network client through the communication connection, and the ticket includes a unified network identity of the user, and the unified network identity of the user includes at least information of a user device of the user, an identity of the user who authenticates and logs in at the zero-trust network client, and information of an access object to be accessed by the user; A verification module is configured to verify the ticket based on the verification request to obtain a verification result, wherein the verification of the ticket based on the verification request includes: verifying whether the identities of the user device accessing the access object in different ways are consistent, and verifying whether the unified network identity of the user is pre-specified on the zero-trust network server; The processing module is configured to perform corresponding processing operations based on the verification result to control the user's access to the access object of the zero-trust network.
13. A computing device, include: Memory and processor, A computer program is stored in the memory, and when the computer program is executed by the processor, the processor is prompted to perform the method according to any one of claims 1 to 11.
14. A computer-readable storage medium storing computer-readable instructions, wherein the computer-readable instructions implement the method of any one of claims 1 to 11 when executed.
15. A computer program product comprising a computer program, which, when executed by a processor, implements the method according to any one of claims 1 to 11.
Citation Information
Cited By
Method and device for trusted access of intelligent agent to intelligent agent internet by intelligent agent
CN121567379A
