Communication methods, target systems and network systems under zero-trust architecture

By deploying connectors in the intranet system, actively connecting to the zero-trust cloud gateway and encrypting and decrypting communications, the problem of low intranet security under the zero-trust architecture system is solved, and efficient protection of the intranet is achieved.

CN114666080BActive Publication Date: 2024-12-06JINAN HANGKE ELECTRONICS CO LTD

Patent Information

Application Number
CN202011536114.X
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2020-12-23
Publication Date
2024-12-06
Estimated Expiration
2040-12-23

AI Technical Summary

Technical Problem

Under the zero-trust architecture system, in the standard software-defined boundary (SDP) solution, there are security vulnerabilities in the network link connected to the zero-trust cloud gateway and the intranet, resulting in low intranet security.

Method used

By deploying a connector in the intranet system, the connector actively connects to the zero-trust cloud gateway, and after connection, it uses a preset encryption and decryption algorithm to encrypt communication, establish a tunnel, avoiding the intranet being compromised, thereby improving the internal network Security of the network.

Benefits of technology

It effectively improves the security of the intranet, prevents network attacks, and enhances the protection of the intranet.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114666080B_ABST
    Figure CN114666080B_ABST
Patent Text Reader

Abstract

The present application provides a communication method, a target system and a network system under a zero-trust architecture system, wherein the target system includes: a server in an intranet system for providing application services, and a connector connected to the server; the connector is also connected to a zero-trust cloud gateway deployed in an external network; the connector actively connects to the zero-trust cloud gateway; after the connector actively connects to the zero-trust cloud gateway, the connector uses a preset encryption and decryption algorithm to perform encrypted communication with the zero-trust cloud gateway. On the one hand, the connector actively connects to the zero-trust cloud gateway, that is, the connector does not need to provide a port to the outside, and establishes a tunnel with the zero-trust cloud gateway by actively connecting to the zero-trust cloud gateway, thereby preventing the intranet from being breached, thereby improving the security of the intranet. On the other hand, after the connector actively connects to the zero-trust cloud gateway, the connector uses a preset encryption and decryption algorithm to perform encrypted communication with the zero-trust cloud gateway, thereby further improving the security of the intranet.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of information network security, and in particular to a communication method, a target system and a network system under a zero-trust architecture system. Background Art

[0002] As enterprises embrace emerging technologies such as cloud computing, mobile Internet, and IoT, their data and applications are no longer limited to the intranet. Therefore, the traditional firewall-based physical boundary defense can no longer meet the needs, and is replaced by software-defined perimeter (SDP). SDP is a new generation of network security model proposed by the International Cloud Security Alliance (CSA) in 2014. SDP advocates network invisibility, zero trust, and minimum authorization, and is a more suitable enterprise security architecture for the cloud and mobile era. After years of development, SDP has been adopted more and more widely. Gartner, a global authoritative IT consulting firm, even predicts that in 2021, more than 60% of enterprises will use SDP to replace existing VPNs, and 80% of upstream and downstream partners of enterprises will use SDP solutions for access.

[0003] However, the network link between the standard SDP zero-trust cloud gateway and the intranet will have network security vulnerabilities. Once breached, the intranet will no longer be secure. In other words, the security of the intranet is low. Summary of the invention

[0004] The present application provides a communication method, a target system and a network system under a zero-trust architecture system, aiming to solve the problem of low intranet security under a zero-trust architecture system.

[0005] In order to achieve the above objectives, this application provides the following technical solutions:

[0006] The present application provides a target system under a zero-trust architecture system, including: a server in an intranet system for providing application services, and a connector connected to the server; the connector is also connected to a zero-trust cloud gateway deployed in an extranet;

[0007] The connector is used to actively connect to the zero-trust cloud gateway;

[0008] The connector is also used to perform encrypted communication with the zero-trust cloud gateway using a preset encryption and decryption algorithm after actively connecting to the zero-trust cloud gateway.

[0009] Optionally, the connector is deployed at an external entrance of the intranet system.

[0010] Optionally, the manner in which the connector obtains the information indicating the encryption and decryption algorithm includes:

[0011] The connector is used to knock on and register with the zero-trust intelligent security brain deployed on the external network through the zero-trust cloud gateway after actively connecting to the zero-trust cloud gateway;

[0012] The connector is also used to receive a configuration file sent by the zero-trust intelligent security brain and forwarded through the zero-trust cloud gateway after the knocking and the registration are successful; the configuration file contains information for indicating the encryption and decryption algorithm.

[0013] Optionally, the connector is used to actively connect to the zero-trust cloud gateway, including:

[0014] The connector is specifically used to connect to the zero-trust cloud gateway via a socket.

[0015] Optionally, the connector is connected to the zero-trust cloud gateway through a first network port, and is connected to the server through a second network port;

[0016] The connector is further used to perform encrypted communication with the zero-trust cloud gateway using a preset encryption and decryption algorithm after actively connecting to the zero-trust cloud gateway, including:

[0017] The connector is specifically used to decrypt the encrypted data using a preset decryption algorithm to obtain decrypted data when the first network port receives the encrypted data sent by the zero-trust cloud gateway; forward the decrypted data to the second network port through the internal routing of the connector; and send the decrypted data to the server through the second network port;

[0018] The connector is also used to transmit the response data to the first network port through the internal routing when the response data of the server to the decrypted data is received from the second network port; encrypt the response data to obtain encrypted response data; and send the encrypted response data to the zero-trust cloud gateway through the first network port.

[0019] Optionally, the connector uses a pre-created virtual network card to encrypt and decrypt data.

[0020] The present application also provides a communication method, which is applied to a connector in a target system; the target system includes: a server in an intranet system for providing application services, and a connector connected to the server; the connector is also connected to a zero-trust cloud gateway deployed in an extranet; the method includes:

[0021] Actively connect to the zero-trust cloud gateway;

[0022] Upon receiving the encrypted data sent by the zero-trust cloud gateway, decrypting the encrypted data to obtain decrypted data;

[0023] Sending the decrypted data to a server in the intranet system;

[0024] When receiving the response data sent by the server, encrypt the response data to obtain encrypted response data; the response data refers to result data obtained by the server responding to the decrypted data;

[0025] The encrypted response data is sent to the zero-trust cloud gateway.

[0026] Optionally, after actively connecting to the zero-trust cloud gateway and before decrypting the encrypted data upon receiving the encrypted data sent by the zero-trust cloud gateway and obtaining the decrypted data, the method further includes:

[0027] Knock on the door and register with the zero-trust intelligent security brain in the external network through the zero-trust cloud gateway;

[0028] Receive a configuration file sent by the zero-trust intelligent security brain and forwarded by the zero-trust cloud gateway; the configuration file includes information indicating: the encryption and decryption algorithm used for encrypted transmission between the connector and the zero-trust cloud gateway.

[0029] The present application also provides a network system under a zero-trust architecture system, including: an external network system and a target system, wherein the external network system includes: a zero-trust intelligent security brain, a zero-trust client, and a zero-trust cloud gateway;

[0030] The zero-trust client and the zero-trust cloud gateway are respectively connected to the zero-trust intelligent security brain;

[0031] The target system is any one of the target systems described above;

[0032] The zero-trust client and the zero-trust cloud gateway perform encrypted communication.

[0033] Optionally, a preset proxy server is deployed in the zero-trust cloud gateway;

[0034] The zero-trust cloud gateway is used to access the connector through a preset proxy server reverse proxy when receiving an access request sent by the zero-trust client, and to perform encrypted communication with the connector.

[0035] The communication method, target system and network system under the zero-trust architecture system described in this application, wherein the target system includes a server in the intranet system for providing applications, and a connector connected to the server; the connector is also connected to a zero-trust cloud gateway deployed in the external network.

[0036] On the one hand, in this application, the connector actively connects to the zero-trust cloud gateway, that is, the connector does not need to provide a port to the outside, but instead actively connects to the zero-trust cloud gateway to establish a tunnel with the zero-trust cloud gateway, thereby preventing the intranet from being breached and improving the security of the intranet.

[0037] On the other hand, in the present application, after actively connecting to the zero-trust cloud gateway, the connector uses a preset encryption and decryption algorithm to conduct encrypted communication with the zero-trust cloud gateway, thereby further improving the security of the intranet.

[0038] In summary, this application can improve the security of the intranet. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0040] Figure 1 A schematic diagram of an application scenario disclosed in an embodiment of the present application;

[0041] FIG2( a ) is a schematic diagram of the structure of a target system disclosed in an embodiment of the present application;

[0042] FIG2( b ) is a schematic diagram of the structure of another target system disclosed in an embodiment of the present application;

[0043] Figure 3 A schematic diagram of the communication process between a client in a connector and a server in a zero-trust cloud gateway disclosed in an embodiment of the present application;

[0044] Figure 4 A schematic diagram of the structure of a network system under a zero-trust architecture system disclosed in an embodiment of the present application;

[0045] Figure 5 A schematic diagram of the communication process of a zero-trust client accessing an intranet server in a network system under a zero-trust architecture system disclosed in an embodiment of the present application. DETAILED DESCRIPTION

[0046] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0047] Figure 1 This is a schematic diagram of an application scenario of an embodiment of the present application, including an external network system and an internal network system, wherein the external network system includes: a zero-trust client, a zero-trust intelligent security brain and a zero-trust cloud gateway, and the zero-trust client and the zero-trust cloud gateway are respectively connected to the zero-trust intelligent security brain.

[0048] Among them, the zero-trust client is used to connect to the zero-trust cloud gateway and allow users to access servers in the intranet system protected by the zero-trust cloud gateway.

[0049] The zero-trust cloud gateway is used to provide zero-trust client connections and forward zero-trust client data. That is, the zero-trust client accesses the intranet system through the zero-trust cloud gateway.

[0050] Zero Trust Intelligent Security Brain is used to configure and manage Zero Trust clients and Zero Trust cloud gateways.

[0051] Among them, the intranet system includes a server for providing application services to users.

[0052] 2 is a schematic diagram of the structure of a target system provided in an embodiment of the present application, including: a server in an intranet system for providing application services, and a connector connected to the server. In this embodiment, the connector is also connected to a zero-trust cloud gateway in an extranet system. As an example, the connector can be connected to the server and the zero-trust cloud gateway respectively through a network port. For the convenience of description, the network port connecting the connector to the zero-trust cloud gateway can be referred to as the first network port, and the network port connecting the connector to the server can be referred to as the second network port.

[0053] In this embodiment, after the connector is physically connected to the server and the zero-trust cloud gateway respectively, before the zero-trust client accesses the intranet, the connector actively connects to the zero-trust cloud gateway, which can also be called the connector reversely connecting to the zero-trust cloud gateway.

[0054] Optionally, the connector can be connected to the zero-trust cloud gateway via a socket. It should be noted that connecting via a socket is only a specific connection method. In practice, other active connection methods can also be used. This embodiment does not limit the specific active connection method.

[0055] After the connector actively connects to the zero-trust cloud gateway, a tunnel is established between the connector and the zero-trust cloud gateway. Subsequently, the communication between the zero-trust cloud gateway and the connector is encrypted through the preset encryption and decryption algorithm.

[0056] In this embodiment, the server can provide B / S service, C / S service and other services.

[0057] Optionally, in this embodiment, the connector can be deployed at the external entrance of the intranet system, thereby further improving the degree of protection of the intranet, that is, further improving the security of the intranet. When the connector is deployed at the external entrance of the intranet system, the structural diagram of the target system is shown in Figure 2(b).

[0058] Of course, in practice, the deployment of the connector at the external entrance of the intranet system is only a specific implementation method. The connector can also be deployed in the intranet system, or outside the intranet system. This embodiment does not limit the relative position relationship between the connector and the intranet system. When the connector is deployed in the intranet system, the intranet system is the target system of the embodiment of the present application. When the connector is deployed outside the intranet system, the target system of the embodiment of the present application is the system composed of the intranet system and the connector.

[0059] In the embodiment of the present application, a client is configured in the connector, and a server is configured in the zero-trust cloud gateway. After the connector establishes physical connections with the server and the zero-trust cloud gateway respectively, the communication process between the connector and the zero-trust cloud gateway is actually the communication between the client in the connector and the server in the zero-trust cloud gateway. The specific communication process is as follows: Figure 3 As shown, the following steps may be included:

[0060] It should be noted that the "server" in S301 to S318 refers to the server deployed in the zero-trust cloud gateway, and the "client" refers to the client deployed in the connector.

[0061] S301. The zero-trust cloud gateway starts the server.

[0062] S302: The server creates a first virtual network card.

[0063] In this embodiment, the first virtual network card is used to decrypt the encrypted data received by the zero-trust cloud gateway and to encrypt the data to be sent by the zero-trust cloud gateway.

[0064] In this step, the specific implementation method of creating the first virtual network card is the existing technology and will not be repeated here.

[0065] S303: The connector starts the client.

[0066] S304: The client creates a second virtual network card.

[0067] In this embodiment, the second virtual network card is used to decrypt the encrypted data received by the connector and to encrypt the data to be sent by the connector.

[0068] In this step, the specific implementation method of creating the second virtual network card is the existing technology and will not be repeated here.

[0069] S305: The client actively connects to the server.

[0070] In this step, the client can actively connect to the server through socket.

[0071] S306. The client knocks on the zero-trust intelligent security brain through the server.

[0072] In this embodiment, the client knocks on the door of the Zero Trust Intelligent Security Brain through the Zero Trust Cloud Gateway. Specifically, the client knocks on the door of the server (the server of the Zero Trust Cloud Gateway), and the server sends the client's knocking information to the Zero Trust Intelligent Security Brain. The Zero Trust Intelligent Security Brain opens the designated port of the firewall for data encryption transmission, and sends the information that the firewall port has been successfully opened to the server (the server of the Zero Trust Cloud Gateway). The server sends the information that the firewall has been successfully opened to the client (the client of the connector), that is, the client completes the knocking on the door of the Zero Trust Intelligent Security Brain.

[0073] S307. The client registers with the zero-trust intelligent security brain through the server.

[0074] After the client completes the knock on the door of the Zero Trust Intelligent Security Brain, the client relays the registration of the Zero Trust Intelligent Security Brain through the server (the server of the Zero Trust Cloud Gateway). Specifically, the client (the client of the connector) sends a registration request to the server (the server of the Zero Trust Cloud Gateway), and the registration request includes the preset attribute information of the client (the client in the connector). The server (the server in the Zero Trust Cloud Gateway) sends the registration request to the Zero Trust Intelligent Security Brain, and the Zero Trust Intelligent Security Brain registers the preset attribute information of the connector, that is, the connector completes the registration with the Zero Trust Intelligent Security Brain.

[0075] S308. The server receives the configuration file sent to the client by the zero-trust intelligent security brain.

[0076] In this embodiment, the configuration file includes information for indicating the encryption and decryption algorithms used by the client and the server for encryption and decryption.

[0077] S309: The server sends the configuration file to the client.

[0078] S310. When the server receives an access request to the intranet sent by the zero-trust client, the server encrypts the access request using a preset encryption algorithm to obtain encrypted data.

[0079] In this step, the preset encryption algorithm is the encryption algorithm between the zero-trust cloud gateway and the zero-trust client.

[0080] In this embodiment, the encryption algorithm may be a general encryption algorithm, a national encryption algorithm, or a custom encryption algorithm.

[0081] In this step, the specific implementation method of using the encryption algorithm for encryption is the existing technology and will not be repeated here.

[0082] S311. The server sends the encrypted data to the client.

[0083] In this step, the server sends the encrypted data to the client through the established tunnel.

[0084] S312: When the client receives the encrypted data at the first network port, the client decrypts the encrypted data through the second virtual network card to obtain decrypted data.

[0085] In this step, the decryption algorithm indicated by the configuration file is used for decryption. The specific implementation of the decryption is prior art and will not be described here.

[0086] S313: The client forwards the decrypted data to the second network port through routing, and sends the decrypted data to the intranet server through the second network port.

[0087] In this embodiment, a router is deployed in the connector.

[0088] In this step, the client forwards the decrypted data to the second network port through routing.

[0089] S314. The intranet server responds to the decrypted data and obtains response data.

[0090] In this embodiment, after receiving the decrypted data, the intranet server responds to the decrypted data. For example, the decrypted data is a decrypted access request. The intranet server responds to the decrypted access request. For the convenience of description, the response result data is called response data.

[0091] S315. The intranet server sends the response data to the client.

[0092] In this embodiment, the intranet server may send the response data in plain text to the client.

[0093] S316: When the client receives response data from the second network port, the client forwards the response data to the first network port through routing.

[0094] S317: The client encrypts the response data received by the first network port through the second virtual network card to obtain encrypted response data.

[0095] In this step, for the convenience of description, the encrypted result data is referred to as encrypted response data.

[0096] S318. The client sends the encrypted response data to the server through the first network port.

[0097] It should be noted that in this embodiment, the data transmitted between the connector client and the intranet server can be plain text, because in a local area network, the distance between the connector and the server is very close, so there is no risk even if it is not encrypted.

[0098] Figure 4 A network system under a zero-trust architecture system provided in an embodiment of the present application includes: an external network system and a target system, wherein the external network system includes a zero-trust client, a zero-trust intelligent security brain and a zero-trust cloud gateway, and the target system includes a connector and a server in an intranet system.

[0099] Among them, the zero trust client and zero trust cloud gateway are connected to the zero trust intelligent security brain respectively, and the connector is connected to the zero trust cloud gateway and server respectively.

[0100] In this embodiment, the communication process between the connector and the zero-trust cloud gateway is as follows: Figure 3 The corresponding embodiments will not be described in detail here.

[0101] In this embodiment, after the network system is physically built, the entire process of the zero-trust client accessing the intranet server is as follows: Figure 5 As shown, the following steps may be included:

[0102] S501. The zero-trust cloud gateway sends a knock request to the zero-trust intelligent security brain.

[0103] S502. The Zero Trust Intelligent Security Brain opens the designated port of the firewall for use in encrypted data transmission.

[0104] S503. The zero-trust intelligent security brain sends a message that the firewall port has been successfully opened to the zero-trust cloud gateway.

[0105] S504. The zero-trust cloud gateway sends a registration request to the zero-trust intelligent security brain.

[0106] In this step, the registration request includes the public key of the zero trust cloud gateway.

[0107] S505. The zero-trust intelligent security brain registers the preset attribute information of the zero-trust cloud gateway.

[0108] S506. The zero trust client sends a knock request to the zero trust intelligent security brain.

[0109] S507. The Zero Trust Intelligent Security Brain opens the designated port of the firewall for use in encrypted data transmission.

[0110] S508. The Zero Trust Intelligent Security Brain sends a message to the Zero Trust Client that the firewall port has been successfully opened.

[0111] S509. The zero trust client sends a registration request to the zero trust intelligent security brain.

[0112] In this step, the registration request includes the public key of the zero trust client.

[0113] S510. The zero-trust intelligent security brain registers the preset attribute information of the zero-trust client.

[0114] S511. The zero-trust intelligent security brain sends configuration policy information and configuration file information to the zero-trust client and zero-trust cloud gateway.

[0115] In this step, configuration policy information is used to indicate access control.

[0116] In this step, the Zero Trust Intelligent Security Brain exchanges the public key uploaded when the Zero Trust Client is registered with the public key uploaded when the Zero Trust Cloud Gateway is registered, and sends them to their respective configuration files.

[0117] S512, Zero Trust Client knocks on Zero Trust Cloud Gateway.

[0118] S513. The zero-trust cloud gateway opens the firewall-specified port for encrypted data transmission.

[0119] S514. The zero-trust cloud gateway sends a message to the zero-trust client indicating that the firewall port has been successfully opened.

[0120] At this point, a tunnel has been established between the zero-trust client and the zero-trust cloud gateway, and the communication data can be encrypted and transmitted between the two using the specified encryption algorithm.

[0121] S515, the connector actively connects to the zero-trust cloud gateway.

[0122] S516, the connector knocks on the door of the zero trust intelligent security brain through the zero trust cloud gateway.

[0123] In this step, the specific knocking process can be referred to Figure 3 The knocking part in the corresponding embodiment will not be described in detail here.

[0124] S517. The connector registers with the Zero Trust Intelligent Security Brain through the Zero Trust Cloud Gateway.

[0125] In this step, the specific registration implementation process can refer to Figure 3 The registration part in the corresponding embodiment will not be repeated here.

[0126] The above S501~S517 are the preparations for the zero-trust client to access the intranet. After the preparations are ready, the following steps are the specific implementation process of the zero-trust client accessing the intranet.

[0127] S518. The zero trust client sends encrypted data to the zero trust cloud gateway.

[0128] S519, Zero Trust Cloud Gateway accesses the connector through a proxy server and reverse proxy.

[0129] In this embodiment, the proxy server can perform seven-layer reverse proxy, four-layer reverse proxy and other application routing forwarding. Among them, the seven-layer reverse proxy refers to the application layer reverse proxy. The four-layer reverse proxy refers to the transport layer reverse proxy. Since the intranet server can provide B / S application services, C / S application services and other application services to the outside world, among them, the B / S application service corresponds to the seven-layer reverse proxy, and the C / S application service corresponds to the four-layer reverse proxy.

[0130] In this step, the Zero Trust Cloud Gateway encrypts and transmits the connection request from the Zero Trust Cloud Gateway to the connector through internal routing.

[0131] S520, encrypted communication between the zero-trust cloud gateway and the connector.

[0132] In this embodiment, after the connector receives the access request, the connector relays the connection request to the background resource server (corresponding to the server provided above), and the background resource server processes the request of the zero-trust client; after the background resource server processes the connection request of the zero-trust client, the requested data is first transmitted to the connector, and the connector then encrypts and transmits it to the zero-trust cloud gateway. The zero-trust cloud gateway encrypts and transmits the requested data from the zero-trust cloud gateway to the zero-trust client through internal routing. The zero-trust client obtains the data of the connection request issued, and the connection process of the entire data request initiated by the client is completed.

[0133] If the functions described in the method of the embodiment of the present application are implemented in the form of software functional units and sold or used as independent products, they can be stored in a storage medium readable by a computing device. Based on this understanding, the part of the embodiment of the present application that contributes to the prior art or the part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions to enable a computing device (which can be a personal computer, server, mobile computing device or network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk and other media that can store program code.

[0134] The various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the various embodiments can be referenced to each other.

[0135] With respect to the above description of the disclosed embodiments, the features recorded in each embodiment in this specification may be replaced or combined with each other, so that professional and technical personnel in this field can implement or use the present application.

[0136] The above description of the disclosed embodiments enables those skilled in the art to implement or use the present application. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application will not be limited to the embodiments shown herein, but will conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A target system under a zero-trust architecture system, characterized in that: include: A server in the intranet system for providing application services, and a connector connected to the server; the connector is also connected to a zero-trust cloud gateway deployed in the extranet; The connector is used to actively connect to the zero-trust cloud gateway; The connector is further used to perform encrypted communication with the zero-trust cloud gateway using a preset encryption and decryption algorithm after actively connecting to the zero-trust cloud gateway; The way in which the connector obtains the information indicating the encryption and decryption algorithm includes: The connector is used to knock and register with the zero-trust intelligent security brain deployed on the external network through the zero-trust cloud gateway after actively connecting to the zero-trust cloud gateway; The connector is also used to receive a configuration file sent by the zero-trust intelligent security brain and forwarded through the zero-trust cloud gateway after the knocking and the registration are successful; the configuration file contains information for indicating the encryption and decryption algorithm.

2. The system according to claim 1, characterized in that The connector is deployed at the external entrance of the intranet system.

3. The system according to claim 1, characterized in that The connector is used to actively connect to the zero-trust cloud gateway, including: The connector is specifically used to connect to the zero-trust cloud gateway via a socket.

4. The system according to claim 1, characterized in that The connector is connected to the zero-trust cloud gateway through a first network port, and is connected to the server through a second network port; The connector is further used to perform encrypted communication with the zero-trust cloud gateway using a preset encryption and decryption algorithm after actively connecting to the zero-trust cloud gateway, including: The connector is specifically used to decrypt the encrypted data using a preset decryption algorithm to obtain decrypted data when the first network port receives the encrypted data sent by the zero-trust cloud gateway; forward the decrypted data to the second network port through the internal routing of the connector; and send the decrypted data to the server through the second network port; The connector is also used to transmit the response data to the first network port through the internal routing when the response data of the server to the decrypted data is received from the second network port; encrypt the response data to obtain encrypted response data; and send the encrypted response data to the zero-trust cloud gateway through the first network port.

5. The system according to claim 4, characterized in that The connector uses a pre-created virtual network card to encrypt and decrypt data.

6. A communication method, characterized in that: A connector applied to a target system; the target system includes: a server in an intranet system for providing application services, and a connector connected to the server; the connector is also connected to a zero-trust cloud gateway deployed in an extranet; the method includes: Actively connect to the zero-trust cloud gateway; Upon receiving the encrypted data sent by the zero-trust cloud gateway, decrypting the encrypted data to obtain decrypted data; Sending the decrypted data to a server in the intranet system; When receiving the response data sent by the server, encrypt the response data to obtain encrypted response data; the response data refers to result data obtained by the server responding to the decrypted data; Sending the encrypted response data to the zero-trust cloud gateway; After actively connecting to the zero-trust cloud gateway, and before decrypting the encrypted data upon receiving the encrypted data sent by the zero-trust cloud gateway to obtain the decrypted data, the method further includes: Knock on the door and register with the zero-trust intelligent security brain in the external network through the zero-trust cloud gateway; Receive a configuration file sent by the zero-trust intelligent security brain and forwarded by the zero-trust cloud gateway; the configuration file includes information indicating: the encryption and decryption algorithm used for encrypted transmission between the connector and the zero-trust cloud gateway.

7. A network system under a zero-trust architecture system, characterized in that: include: An external network system and a target system, wherein the external network system includes: a zero-trust intelligent security brain, a zero-trust client, and a zero-trust cloud gateway; The zero-trust client and the zero-trust cloud gateway are respectively connected to the zero-trust intelligent security brain; The target system is a target system as claimed in any one of claims 1 to 5; The zero-trust client and the zero-trust cloud gateway perform encrypted communication.

8. The system according to claim 7, characterized in that A preset proxy server is deployed in the zero-trust cloud gateway; The zero-trust cloud gateway is used to access the connector through a preset proxy server reverse proxy when receiving an access request sent by the zero-trust client, and to perform encrypted communication with the connector.

Citation Information

Patent Citations

  • Enterprise intranet access method based on reverse connection and application layer tunnel

    CN108600204A

  • Application access control security system and method

    CN111490993A

  • Method for constructing server zero-trust connection architecture

    CN112016073A

  • 5G network security protection method and system

    CN112073969A

  • Secure and control data migrating between enterprise and cloud services

    US20160269371A1

Cited By

  • Zero-trust IM terminal configuration method based on identity authentication

    CN116318971A

  • Zero-trust im terminal configuration method based on identity authentication

    CN116318971B