Security gateway, system and method for verifying egress traffic in computer network system
By introducing a secure gateway into the computer network system, terminating TLS communication and verifying egress traffic based on predetermined verification requirements, the security and privacy protection of egress traffic of data center and internal services in the external network are solved, and the egress traffic is achieved. Effective monitoring and management.
Patent Information
- Application Number
- CN202411113839.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2023-08-28
- Filing Date
- 2024-08-14
- Publication Date
- 2024-11-22
AI Technical Summary
Existing computer network systems lack effective security and privacy protections when transmitting egress traffic from data centers and internal services to external networks, making it difficult to ensure the security of data and the implementation of privacy policies, especially in cross-network communications. middle.
Adopt a secure gateway system, including a proxy server and a gateway proxy, terminates Transport Layer Security (TLS) communication, and verifys the validity or invalidity of egress traffic based on predetermined verification requirements, forwards valid traffic or blocks invalid traffic through the gateway proxy to ensure data Security and privacy during transmission.
It realizes centralized security checks on the egress traffic of data centers and internal services, ensures data security and privacy protection, complies with regulations and standards in specific areas, and enhances the monitoring and management capabilities of egress traffic.
Smart Images

Figure CN119011257A_ABST
Abstract
Description
Technical Field
[0001] The embodiments described herein generally relate to security gateways in computer network systems. More specifically, the embodiments described herein relate to methods and systems for security gateways to authenticate egress traffic from a data center and / or internal services to an external network. Background Art
[0002] In computer network systems, a "gateway" or "network gateway" may refer to a device that connects different networks by converting communications from one protocol to another. It should be understood that a gateway may refer to networking hardware used in telecommunications networks that allows data to flow from one discrete network to another. It should also be understood that a gateway may refer to a computer program configured to perform the tasks of the gateway hardware. It should also be understood that a gateway may communicate using more than one protocol to connect multiple networks, and may operate on any of the seven layers of the Open Systems Interconnection model (OSI). Summary of the invention
[0003] It should be understood that there are different ways to transmit egress traffic from a data center and / or internal services to an external network (e.g., the Internet, etc.), including using a Network Address Translation (NAT) service, binding a public Internet Protocol (IP) address to (multiple) physical machines, etc. Features in the embodiments disclosed herein may provide a customized security gateway that serves as a centralized location to collect all traffic (e.g., egress traffic, etc.) and / or provides a secure gateway that inspects the content and / or format of the traffic.
[0004] Features in the embodiments disclosed herein may provide data security and privacy protection for data in a data center and / or internal services, and demonstrate and ensure enforcement of privacy policies of the data center and / or internal services.
[0005] It should be understood that when the data center and / or internal services are considered as a building belonging to the first party, the first party can open some doors of the building so that information (from the second party) enters and / or leaves the building (to the second party), and the first party can work with a third-party partner, such as "hiring security guards" to protect the building so that no one can bring in and / or take out sensitive information. The way to achieve this is to cut off all access to the data center and / or internal services except for some channels with security and / or privacy gateways, and these gateways can be deployed in a neutral environment jointly owned by the first party and the third-party partner to prove the enforcement of data security and privacy policies and meet the standards of specific regional regulations.
[0006] Features in the embodiments disclosed herein may provide a security gateway as a security gateway that brings all traffic (eg, egress traffic, etc.) from a data center and / or internal services to an external network and applies assurance checks to all traffic.
[0007] In an example embodiment, a security gateway for verifying egress traffic in a computer network system is provided. The security gateway includes a proxy server and a gateway agent. The proxy server is configured to terminate transport layer security communications for egress traffic. The proxy server is also configured to forward the egress traffic to the gateway agent. The gateway agent is configured to verify the egress traffic as valid traffic or invalid traffic based on predetermined verification requirements. The proxy server is also configured to receive valid traffic or invalid traffic from the gateway agent, and forward valid traffic to a destination service or block invalid traffic.
[0008] In another example embodiment, an egress traffic verification system for a computer network system is provided. The egress traffic verification system includes a security gateway. The security gateway includes a proxy server and a gateway agent. The proxy server is configured to receive egress traffic and terminate transport layer security (TLS) communications for the egress traffic. The proxy server is also configured to forward the egress traffic to the gateway agent. The gateway agent is configured to verify the egress traffic as valid traffic or invalid traffic based on predetermined verification requirements. The proxy server is also configured to receive valid traffic or invalid traffic from the gateway agent, and forward valid traffic to a destination service or block invalid traffic.
[0009] In another example embodiment, a method for verifying egress traffic in a computer network system is provided. The method includes terminating, by a proxy server, a transport layer security (TLS) communication for egress traffic; forwarding, by the proxy server, the egress traffic to a gateway proxy; verifying, by the gateway proxy, the egress traffic as valid traffic or invalid traffic based on predetermined verification requirements; receiving, by the proxy server, valid traffic or invalid traffic from the gateway proxy; and forwarding, by the proxy server, valid traffic to a destination service or blocking invalid traffic.
[0010] In yet another example embodiment, a non-transitory computer-readable medium having computer-executable instructions stored thereon is provided. The instructions, when executed, cause one or more processors to perform operations including: terminating transport layer security (TLS) communications for egress traffic; validating egress traffic as valid traffic or invalid traffic based on predetermined validation requirements; and forwarding valid traffic to a destination service or blocking invalid traffic. BRIEF DESCRIPTION OF THE DRAWINGS
[0011] The accompanying drawings illustrate various embodiments of systems, methods, and embodiments of other various aspects of the present disclosure. It will be appreciated by those skilled in the art that the element boundaries (e.g., boxes, frame groups, or other shapes) illustrated in the figures represent an example of boundaries. In some examples, an element may be designed as multiple elements, or multiple elements may be designed as one element. In some examples, an element shown as an internal component of an element may be implemented as an external component in another element, and vice versa. Non-restrictive and non-exhaustive descriptions are described with reference to the following drawings. The components in the figures are not necessarily drawn to scale, but are focused on the explanation principle. In the following detailed description, the embodiments are described only as illustrations, because those skilled in the art can clearly see various changes and modifications from the following detailed description.
[0012] Figure 1 is a schematic diagram of an example computer network system for egress traffic validation, arranged in accordance with at least some embodiments described herein.
[0013] Figure 2 is a schematic diagram of an example egress flow verification system arranged in accordance with at least some embodiments described herein.
[0014] Figure 3 is a schematic diagram of another example egress flow verification system arranged in accordance with at least some embodiments described herein.
[0015] Figure 4 is a flow chart illustrating an example process flow for validating egress traffic in a computer network system in accordance with at least some embodiments described herein.
[0016] Figure 5 is a schematic block diagram of an exemplary computer system suitable for implementing an apparatus, arranged in accordance with at least some embodiments described herein. DETAILED DESCRIPTION
[0017] In the following detailed description, specific embodiments of the present disclosure are described herein with reference to the accompanying drawings, which form a part of the description. In this description and in the drawings, unless the context otherwise dictates, the same reference numerals represent elements that can perform the same, similar, or equivalent functions. In addition, unless otherwise specified, the description of each consecutive figure may refer to features from one or more previous figures to provide a clearer context and a more substantial explanation of the current example embodiment. However, the example embodiments described in the detailed description, the drawings, and the claims are not intended to be limiting. Other embodiments may be utilized, and other changes may be made without departing from the spirit or scope of the subject matter presented herein. It is readily understood that, as generally described herein and illustrated in the drawings, the various aspects of the present disclosure may be arranged, replaced, combined, separated, and designed in a variety of different configurations, all of which are expressly contemplated herein.
[0018] It should be understood that the disclosed embodiments are merely examples of the present disclosure, which may be embodied in various forms. Well-known functions or structures are not described in detail to avoid obscuring the present disclosure with unnecessary details. Therefore, the specific structural and functional details disclosed herein should not be interpreted as limiting, but should only serve as a basis for the claims and as a representative basis for teaching those skilled in the art to variously adopt the present disclosure with almost any appropriate detailed structure.
[0019] In addition, the disclosure may be described in the form of functional block components and various processing steps. It should be understood that such functional blocks may be implemented by any number of hardware and / or software components configured to perform the specified functions.
[0020] The scope of the present disclosure should be determined by the appended claims and their legal equivalents, rather than by the examples given herein. For example, the steps recited in any method claim may be performed in any order and are not limited to the order given in the claim. In addition, unless expressly described as "critical" or "essential" herein, no element is essential to the practice of the present disclosure.
[0021] As used herein, "network" or "computer network" is a technical term that may refer to interconnected computing devices that can exchange data and share resources with each other. It should be understood that networked devices can use a system of rules (e.g., communication protocols, etc.) to transmit information through wired or wireless technologies.
[0022] As referred to herein, a "packet," "data packet," "network packet," or "network data packet" in a computer network system is a term of art and may refer to a formatted unit of data carried by a computer network system. It should be understood that a packet may include control information and user data. User data may be referred to as a "payload." Control information may provide information for delivering the payload (e.g., source and destination network addresses, error detection codes, sorting information, etc.). It should also be understood that control information may typically be stored in a packet header and / or trailer. It should also be understood that control information may include metadata. Metadata in a computer network may refer to descriptive information about user data, or "data about data." Metadata may carry individual characteristics related to the communication protocol and the structure of the packet.
[0023] As referenced herein, the "header" of a packet may refer to the initial portion of a packet. It should be understood that the header may contain control information, such as addressing, routing, protocol version, etc. The format of the header information may depend on the communication protocol used. For example, in the Open Systems Interconnection (OSI) model of the International Organization for Standardization (ISO) (the model used in the embodiments disclosed herein), the communication in a computer network system may be split into different layers: physical layer (L1), data link layer (L2), network layer (L3), transport layer (L4), session layer (L5), presentation layer (L6), and application layer (L7). In another example, the Transmission Control Protocol / Internet Protocol (TCP / IP) model may include a physical layer (L1), a data link layer (L2), an Internet layer (L3), a transport layer (L4), and an application layer (L5). Each layer may have its own communication protocol. For example, the L2 header may contain fields such as a destination media access control (MAC) address, a source MAC address, and the like.
[0024] As referred to herein, a "gateway" or "network gateway" in a computer network system is a technical term that may refer to a device that connects different networks by converting communications from one communication protocol to another. It should be understood that a gateway may refer to network hardware used in a telecommunications network that allows data to flow from one discrete network to another discrete network. It should also be understood that a gateway may also refer to a computer program configured to perform the tasks of the gateway hardware. It should also be understood that a gateway may communicate using more than one protocol to connect multiple networks, and may operate on any of the seven layers of the Open Systems Interconnection Model (OSI). In an example embodiment, a gateway may refer to a network device used in telecommunications that connects two networks with different transmission protocols together. That is, a gateway may provide a connection between two networks, and the networks do not need to use the same network communication protocol. It should be understood that a gateway may act as an entry point and an exit point for a network, because all data must pass through or communicate with a gateway before being routed.
[0025] As referred to herein, a gateway "agent" in a computer network system is a general term that may refer to, for example, a computer program, algorithm, etc. that may be installed on a gateway, thereby allowing the gateway agent to manage and monitor all network traffic, as well as other functionality.
[0026] As referred to herein, a "secure gateway" may refer to a gateway that is owned, managed, controlled by a third party that is independent and / or separate from (the first party and the second party) that implements the traffic communication.
[0027] As referred to herein, "traffic," "traffic flow," or "network flow" in a computer network system may refer to data (e.g., a sequence of packets, etc.) from a source computer or device to a destination computer or device, which may be another host, a multicast group, or a broadcast domain. It should be understood that traffic may include all packets and / or media streams in a particular transport connection, and may include a set of packets passing through an observation point in the network during a particular time interval.
[0028] As referred to herein, "egress traffic" may refer to traffic from a data center and / or internal service (a first party) to an external network (e.g., the Internet, etc.) (a second party). It should be understood that egress traffic includes requests flowing from a data center and / or internal service to an external network, and / or responses corresponding to the requests flowing from the external network back to the data center and / or internal service (e.g., confirmation of the request, reply, etc.). That is, egress traffic includes network requests from a data center and / or internal service (e.g., requests issued to obtain or retrieve information from a server) and network responses corresponding to the network requests (e.g., as a reply to the network request) (e.g., from a server in an external network). For example, a data center and / or internal service (a first party) may rely on a tool or application programming interface (API) (e.g., a map tool that provides user location / position coordinates, etc.) of a second party in an external network (e.g., the Internet, etc.) to provide or support services provided by the first party (e.g., to an end user). The first party may send a request to a tool or API of a second party in an external network, and the second party may send a response corresponding to the request back to the first party. The request (from the first party's data center and / or internal service to the second party in the external network) and / or its corresponding response forms egress traffic.
[0029] As referred to herein, a "proxy" or "proxy server" in a computer network system is a general term and may refer to an application or computer device that acts as a proxy between a client requesting a resource or service and a server providing the resource or service.
[0030] As used herein, "load balancing" in a computer network system is a technical term and may refer to the process of distributing a set of tasks across a set of resources (e.g., computing units, etc.) in order to make their overall processing more efficient. Load balancing may optimize response time and avoid unevenly overloading certain computing nodes while other computing nodes are idle. A "load balancer" may refer to a computer device or program configured to perform a load balancing process.
[0031] As referenced herein, a "forward" proxy server in a computer network system is a technical term and may refer to a proxy that is placed between an internal service or device (e.g., a user device, a data center, an internal service, etc.) and an external network (e.g., the Internet, etc.). It should be understood that a forward proxy server may evaluate a request, take any necessary actions, and route the request to a destination on behalf of the client, rather than verifying the client request and sending it directly to the server. In other words, a forward proxy server may help devices on a private network access an external network (e.g., the Internet, etc.). In an example embodiment, a forward proxy server may be an Internet-facing proxy server (rather than an internal-facing proxy server) to retrieve data from various sources (e.g., from the Internet, etc.).
[0032] As referred to herein, a web application firewall or "WAF" in a computer network system is a general term and may refer to a firewall that protects web applications and APIs by filtering, monitoring, and / or blocking malicious web traffic and application layer attacks.
[0033] Figure 1 is a schematic diagram of an example computer network system 100 for egress traffic validation, arranged in accordance with at least some embodiments described herein.
[0034] System 100 may include devices 105, 110, 115, 120, 130, 140, 150, a network 160, a gateway or router 170, and / or network switches 180 and 190. It should be understood that Figure 1 Only an exemplary number of devices (105, 110, 115, 120, 130, 140, 150, 170, 180 and / or 190) and / or networks are shown. The embodiments described herein are not limited to the number of devices and / or networks described. That is, the number of devices and / or networks described herein is for descriptive purposes only and is not intended to be limiting.
[0035] According to at least some example embodiments, devices 105, 110, 115, 120, 130, 140, and / or 150 may be various electronic devices. The various electronic devices may include, but are not limited to, mobile devices such as smartphones, tablet computers, e-book readers, laptop computers, desktop computers, servers, and / or any other suitable electronic devices.
[0036] According to at least some example embodiments, the network 160 may be a medium used to provide a communication link between the devices 105, 110, 115, 120, 130, 140, 150, 170, 180, and / or 190. The network 160 may be the Internet, a local area network (LAN), a wide area network (WAN), a local interconnect network (LIN), a cloud, etc. The network 160 may be implemented by various types of connections, such as a wired communication link, a wireless communication link, a fiber optic cable, etc.
[0037] According to at least some example embodiments, one or more of devices 105, 110, 115, 120, 130, 140, and / or 150 may be a server for providing various services to a user using one or more other devices. The server may be implemented by a distributed server cluster including a plurality of servers, or by a single server.
[0038] Users may use one or more of devices 105, 110, 115, 120, 130, 140, 150, 170, 180, and / or 190 to interact with each other via network 160. Various applications or their localized interfaces may be installed on devices 105, 110, 115, 120, 130, 140, and / or 150, such as social media applications, online shopping services, machine learning services, and the like.
[0039] It should be understood that software applications or services according to the embodiments described herein and / or according to services provided by a service provider may be executed by devices 105, 110, 115, 120, 130, 140, 150, 170, 180, and / or 190. Therefore, means for software applications and / or services may be arranged in devices 105, 110, 115, 120, 130, 140, 150, 170, 180, and / or 190.
[0040] It should also be understood that when services are not performed remotely, system 100 may not include network 160, but only devices 105, 110, 115, 120, 130, 140, 150, 170, 180 and / or 190.
[0041] It should also be understood that devices 105, 110, 115, 120, 130, 140, 150, 170, 180 and / or 190 may each include one or more processors, memory and storage devices, which store one or more programs. Devices 105, 110, 115, 120, 130, 140, 150, 170, 180 and / or 190 may also each include an Ethernet connector, a wireless fidelity receiver, etc. One or more programs, when executed by one or more processors, may cause one or more processors to perform the (multiple) methods described in any embodiment described herein. In addition, it should be understood that a computer-readable non-volatile medium may be provided according to the embodiments described herein. The computer-readable medium stores a computer program. The computer program is used to perform the (multiple) methods described in any embodiment described herein when executed by a processor.
[0042] Figure 2 is a schematic diagram of an example egress flow verification system 200 arranged in accordance with at least some embodiments described herein.
[0043] In an example embodiment, system 200 may include a data center and / or internal service 210, a proxy server 220, a security gateway 230, and an external network 270. In an example embodiment, security gateway 230 may be Figure 1 Gateway 170.
[0044] The internal service 210 is configured to, for example, provide services to end users. In an example embodiment, some services provided by the internal service 210 (e.g., owned by a first party) may rely on a second party's tools or APIs in an external network (e.g., the Internet, etc.) (e.g., a map tool that provides user location / position coordinates, etc.) to provide or support the services provided by the first party (e.g., to end users). The first party's internal service 210 may send requests (for egress traffic) to the second party's tools or APIs in the external network. Requests from the internal service 210 may be sent (to the second party) through the proxy server 220.
[0045] In an example embodiment, proxy server 220 may be a forward proxy server (e.g., owned by a first or third party) configured to forward traffic (e.g., egress traffic) received from internal service 210 to security gateway 230 (e.g., its TLS proxy server 240).
[0046] In an example embodiment, the security gateway 230 includes a proxy server (240, 250) and a gateway proxy 260. In an example embodiment, the proxy server (240, 250) may include a proxy server (e.g., a TLS proxy server, etc.) 240 and a proxy server (e.g., a forwarding proxy server, etc.) 250. In another example embodiment, the proxy server (240, 250) may be a single proxy server. It should be understood that the TLS proxy server 240, the forwarding proxy server 250, and the gateway proxy 260 may be combined and deployed in a neutral or trusted environment. It should also be understood that a neutral or trusted environment may be, for example, an open source environment, a third-party cloud provider, etc., so that a first party (which transmits egress traffic with a second party) may collaborate with a third party, for example, to ensure that the data privacy policy of the first party is enforced.
[0047] In an example embodiment, TLS proxy server 240 is a TLS termination proxy server (or a secure socket layer (SSL) termination proxy server). TLS proxy server 240 can be used as a proxy server that acts as a transition between a client and a server application, and can terminate a TLS tunnel (egress traffic) by decrypting or decoding the communication (i.e., decrypting the egress traffic). That is, TLS proxy server 240 is configured to terminate the TLS process of the egress traffic received from proxy server 220, and send the decrypted or decoded egress traffic to forwarding proxy server 250.
[0048] In an example embodiment, forward proxy server 250 is configured to receive decrypted or decoded egress traffic from TLS proxy server 240 and redirect the data (eg, payload in a request for the egress traffic, etc.) to gateway proxy 260 .
[0049] In an example embodiment, the gateway proxy 260 is configured to receive data from the forward proxy server 250 and parse the data (e.g., each data field therein) based on the format of the data (such as JavaScript Object Notation (JSON) format, Extensible Markup Language (XML) format, etc.). The gateway proxy 260 is configured to interpret the format of the data and / or the type of the data (e.g., Hypertext Transfer Protocol (HTTP) type, non-HTTP type such as HTTP / 2 (or HTTP2) type, Secure File Transfer Protocol (SFTP) type, Simple Mail Transfer Protocol (SMTP) type, Internet Message Access Protocol (IMAP) type, and / or other application layer (L7) types).
[0050] It should be understood that the predetermined rules or verification requirements (which will be Figure 3Detailed description in ) may be stored in the memory of gateway proxy 260 or registered with gateway proxy 260 (e.g., via a registration platform). In an example embodiment, the predetermined rules or validation requirements may include all patterns (e.g., format, value, field, etc.) of the request and / or its corresponding response, which have been predetermined or predefined to satisfy the data privacy policy of the first party.
[0051] In an example embodiment, the gateway agent 260 is configured to verify the parsed data based on predetermined rules or verification requirements. For example, if the request (and / or its response) in the egress traffic matches one of the predetermined rules or verification requirements (i.e., the request and / or its response has been registered with the gateway agent 260), the gateway agent 260 can verify or mark the egress traffic as valid traffic. If the request (and / or its response) in the egress traffic does not match any of the predetermined rules or verification requirements (i.e., the request and / or its response is not registered with the gateway agent 260), the gateway agent 260 can verify or mark the egress traffic as invalid traffic.
[0052] In an example embodiment, for invalid traffic, the gateway proxy 260 may, for example, tag data (e.g., requests in egress traffic and / or responses thereof) based on data types and make recommendations (regarding data types, data tags, etc.) so that the first party can confirm the recommendations and / or modify predetermined rules or verification requirements. The first party may store such requests / responses in the gateway proxy 260 or register such requests / responses with the gateway proxy 260, and may then verify future egress traffic (with such requests / responses) as valid traffic.
[0053] In an example embodiment, the forwarding proxy server 250 may be configured to receive valid traffic or invalid traffic from the gateway proxy 260 to forward the valid traffic to a destination service (e.g., in the external network 270) or to prevent the invalid traffic from being sent to the external network 270. It should be understood that the forwarding proxy server 250 is also configured to establish or reestablish or recover (terminated) TLS and / or SSL communications and / or processing (e.g., encrypting or encoding data in the valid traffic for secure communication) for the valid traffic before forwarding the valid traffic to the destination service.
[0054] In an example embodiment, the destination service in the external network 270 is configured to receive valid traffic (e.g., a request from the internal service 210) and send a response corresponding to the request back to the internal service 210 of the first party. It should be understood that the request (from the first party's data center and / or the internal service 210 to the second party in the external network 270) and / or its corresponding response forms or defines the egress traffic. In an example embodiment, the response can be verified by the gateway proxy 260 based on predetermined rules or verification requirements before being sent to the internal service 210 via the secure gateway 230. In another example embodiment, the response can skip the verification process before being sent to the internal service 210 via the secure gateway 230.
[0055] It should be understood that the predetermined rules or verification requirements can be determined based on compliance or assurance requirements for the egress traffic. The security gateway 230 is configured to provide a centralized location to (1) collect or intercept all egress traffic from the data center or internal service 210 to the external network 270 (including responses from the external network 270 to the internal service 210), (2) parse the data or payload and interpret the data or payload within the request and / or response in the egress data, and (3) (e.g., based on the predetermined rules or verification requirements) apply a privacy protection or assurance policy to or on the egress traffic to verify the data or payload carried within the request and / or response in the egress data.
[0056] It should be understood that the features described in the embodiments disclosed herein provide a security gateway 230 that acts as an egress gateway and is responsible for inspecting egress traffic from a guaranteed Internet data center environment (i.e., a neutral or trusted environment). In an exemplary embodiment, the security gateway 230 includes a gateway agent 260, a forwarding proxy server 250, and a TLS proxy server 240, which are deployed in three separate containers within a pod on a system (e.g., an open source system for automatically deploying, scaling, and managing containerized applications, etc.). Egress traffic (e.g., requests from internal services 210, etc.) can be forwarded to the security gateway 230 (e.g., through the proxy server 220), where the TLS connection is terminated at the proxy server 240 before the request is passed to the proxy server 250. The proxy server 250 passes the request to the gateway agent 260 through a connection (e.g., an Internet Content Adaptation Protocol (ICAP) Transmission Control Protocol (TCP) socket connection) for traffic assurance before forwarding the request to a destination service in the external network 270 or blocking the request. In an example embodiment, gateway proxy 260 may be a WAF proxy.
[0057] Figure 3is a schematic diagram of another example egress flow verification system 300 arranged in accordance with at least some embodiments described herein. It should be understood that unless otherwise indicated, the system 300 may have the same Figure 2 The same process, configuration, arrangement and / or structure as system 200.
[0058] In the example embodiment, system 300 includes internal services 310, at least one proxy server 320, at least one secure gateway 330, and "API and resources" 370. It should be understood that unless otherwise stated, internal services 310 may have the same Figure 2 The proxy server 320 may have the same process, configuration, arrangement and / or structure as the internal service 210; Figure 2 The same process, configuration, arrangement and / or structure as the proxy server 220; the security gateway 330 may have Figure 2 The same process, configuration, arrangement and / or structure as the security gateway 230; and the API and resources 370 may have the same Figure 2 The same process, configuration, arrangement and / or structure of the external network 270.
[0059] In an example embodiment, system 300 also includes at least one load balancer 325, at least one secure gateway cluster 335, an RFS device or RFS cluster 380, and / or a NAT device 390. Each secure gateway cluster 335 includes one, two, or more secure gateways 330. Each RFS cluster 380 includes one or more RFS devices.
[0060] It should also be understood that the system 300 supports both HTTP and non-HTTP based protocols. In general, an HTTP request may include (1) a verb indicating an HTTP method (such as GET, PUT, POST, etc.), (2) a uniform resource identifier (URI) identifying a resource on a server, (3) an HTTP version indicating an HTTP protocol version, (4) a request header containing metadata of the HTTP request message (such as client type, cache settings, message body format, etc.), and (5) a request body representing the message content. An HTTP response may include (1) a status / response code indicating the server status of the requested resource, (2) an HTTP version indicating an HTTP protocol version, (3) a response header containing metadata of the HTTP response message (such as content length, content type, server length, etc.), and (4) a response body representing the response message content.
[0061] It should also be understood that non-HTTP based protocols may require non-trivial processing of data and, therefore, may be implemented in a request forwarding service (RFS) appliance or RFS cluster 380 that is separate from the secure gateway 330. The RFS appliance or RFS cluster 380 may be configured to operate as an intermediary between the source (e.g., internal services 310) and the destination service (e.g., APIs and resources 370 in the external network) of the egress traffic and may be configured to expose HTTP APIs to convert HTTP requests (from the source) into protocol specific messages to and from the destination service. For example, the RFS appliance supports protocols over HTTP such as Secure File Transfer Protocol (SFTP), Simple Mail Transfer Protocol (SMTP), etc. It should also be understood that using the secure gateway 330 for non-HTTP egress traffic may require service owners to refactor their services to use RFS specific APIs for their protocols. If a protocol plug-in does not exist for its service (e.g., in an RFS device), the owner may be required to develop a protocol plug-in for its specific service so that the RFS device or RFS cluster 380 can convert requests from the source to protocol-specific messages to and from the destination service in the external network (370, 270).
[0062] It should also be understood that "NAT" in a computer network system is a technical term and may refer to network address translation. A NAT service or device may be configured to map multiple private addresses within a local network to a public IP address before transmitting the information to the Internet. For example, an organization that wishes to employ a single IP address for multiple devices may use NAT. Some payment APIs in an external network (370, 270) may require a fixed NAT IP address. NAT device 390 may be configured to support such requirements.
[0063] In an example embodiment, the internal service 310 is configured to send the request (in the form of egress traffic) to the API and resources 370 in the external network via the proxy server 320. Based on the type of request (e.g., HTTP request whose destination service does not require a fixed NAT IP address, non-HTTP request, HTTP request whose destination service requires a fixed NAT IP address, etc.), the internal service 310 is configured to send the request (in the form of egress traffic) to the security gateway cluster 335 corresponding to the request type (e.g., respectively) via the corresponding proxy server 320. Figure 3 left, center or right cluster 335).
[0064] It should be understood that unlike some embodiments of the egress gateway, in which all service traffic is forwarded from a single proxy server to a conventional egress gateway to enable authorization and authentication of the source of all egress traffic, the features of the embodiments described herein may be different in the proxy server instance 320 (e.g., Figure 3 The egress traffic may be split between the left, middle, and right proxy servers 320 in the example, and each request forwarded to the security gateway 330 may have a proxy server account header injected into the request (e.g., by the proxy server 320), and then the gateway proxy (e.g., Figure 2 260) in addition to using the request (e.g., domain and API path, etc.), also uses the header as part of the key to find the corresponding request pattern (e.g., in a predetermined rule or verification requirement).
[0065] It should also be understood that splitting of traffic between proxy server instances 320 based on the type of request may be due to different destination service requirements, such as, for example, a fixed NAT IP (via NAT service 390) for a payment API (in the external network 370), outgoing non-HTTP traffic going through the RFS service 380, etc.
[0066] In an example embodiment, the load balancer 325 is configured to send requests from the proxy server 320 to the corresponding security gateway 330 in the security gateway cluster 335. The security gateway 330 is configured to identify the egress traffic through a proxy server account header injected for all outbound / egress traffic at the proxy server 320. In addition to using the request data (e.g., request domain and API path, etc.), the security gateway 330 can also use the proxy server account to match the corresponding request pattern from the data / rule registration service (e.g., in a predetermined rule or verification requirement) to verify (e.g., based on the predetermined rule or verification requirement) the predefined API request pattern.
[0067] In an example embodiment, the security gateway 330 (or 230) can be configured to perform endpoint verification on the egress traffic. It should be understood that endpoint verification can be used to identify the destination service (in the external network) to which the request (in the egress traffic) is being sent. Endpoint verification includes verifying the domain and API path information in the request (and / or the proxy server account inserted by the proxy server 320) based on predetermined rules or verification requirements.
[0068] For example, for a request (from an internal service of a first party) to a map tool or API (of a second party in an external network) that provides user locations or location coordinates, etc., the request (e.g., containing "map.secondparty.com / getLocationCoordinates") may include a domain (represented by a domain name such as "secondparty.com" and / or a host name such as "map" and an API path " / getLocationCoordinates" of the API that returns location coordinates). Such domain and API path information of the request (and / or a proxy server account inserted by the proxy server 320) must match one of the predetermined rules or validation requirements stored in or registered with the security gateway 330 to be determined as valid traffic, such as a registered API endpoint and domain. If there is no match between the request and the predetermined rules or validation requirements, the traffic may be determined as invalid traffic. It should be understood that each request in the egress traffic may have to pass endpoint validation to be determined as valid traffic.
[0069] In an example embodiment, the security gateway 330 (or 230) can be configured to perform account verification on the egress traffic to verify whether the request is sending data to the account / storage of the second party in the external network. It should be understood that the first party may also have accounts, storage, tools, APIs, servers, systems and / or data centers in the external network. It should also be understood that in order to ensure that protected data is not sent to the first party owner's account or storage in the external network, the security gateway 330 (or 230) can be configured to mark and verify fields that may have indications of account / ownership / identification information in the following segments: (1) HTTP request headers, (2) HTTP query parameters (e.g., a set of defined parameters appended to the end of a URL, which are extensions of the URL and are used to help define specific content or operations based on the data being passed), (3) HTTP request body, (4) fully qualified domain name (FQDN), and / or (5) HTTP uniform resource identifier (URI) path. It should also be understood that in addition to annotating and labeling the fields containing account information, a value for the field may also be provided, and the security gateway 330 (or 230) may be configured to verify (based on predetermined rules or validation requirements) that requests (in egress traffic) are only going to these pre-declared accounts in order to be determined as valid traffic.
[0070] In an example embodiment, the security gateway 330 (or 230) can be configured to perform pattern validation on the egress traffic to validate all fields in the data / payload of the request (in the egress traffic) based on predetermined rules or validation requirements. These fields include: (1) HTTP request headers (note that common HTTP headers such as content-length are not included), (2) HTTP request query parameters, and / or (3) structured data in the HTTP request body, etc. Only when all fields in the request data / payload have corresponding matches in the predetermined rules or validation requirements, the pattern validation of the traffic can pass and the traffic can be determined as valid traffic.
[0071] It should be understood that the predetermined authentication requirements may include endpoint authentication, account authentication, and / or mode authentication, which may be performed based on, for example, different types of requests and different levels of authentication requirements required by the second party. For example, egress traffic to a highly trusted second party (which is predefined in the predetermined rules or authentication requirements) may only require endpoint authentication; whereas any egress traffic to a typical / normal second party may require endpoint, account, and / or mode authentication.
[0072] In an example embodiment, for any egress traffic to a first-party controlled server / data center or system (in an external network), such as a video archiving service that sends a GET request to download a video from a first-party controlled data center in an external network, the authentication requirements may require authentication of the API endpoint for the request (i.e., endpoint authentication) and the full HTTP schema.
[0073] In an example embodiment, for a request that is destined for a normal second party in an external network and carries information indicating ownership of a user account associated with a second party destination API, e.g., a Stripe payment API account owned by a payment processor, the validation requirement may require validation of the endpoint and domain for the request, as well as matching the account identification information in the request with annotated and approved account values in a registered request schema (e.g., a predetermined rule or validation requirement). That is, endpoint and schema validation may be required.
[0074] In an example embodiment, for egress traffic to a highly trusted (predefined) second party in an external network, e.g., a highly trusted second party user tax account statement upload, the authentication requirements may only require authentication of the API endpoint and domain for the request (i.e., endpoint-only authentication).
[0075] In an example embodiment, for egress traffic to certain second-party APIs (in an external network) that do not carry protected data and the second party does not store any data, for example, an embedded map widget in a first-party service that uses the second party's map API, the verification requirements may require verifying the API endpoint and domain (i.e., endpoint verification) and providing an official statement that the API does not store any data as well as providing the API documentation as evidence.
[0076] In an example embodiment, for requests (in egress traffic) that are invoked via a second party to an upstream service that is destined for an individual or end-user, such as a push notification service for a mobile user, or a general email service for a first party, the validation requirements may require validation of the API endpoint and domain (i.e., endpoint validation) and full schema validation, and checking of template values.
[0077] In an example embodiment, for requests sent to users / external via a uniform resource locator (URL), such as HTTP-based callback functions that allow lightweight, event-driven communication between two application programming interfaces (APIs), the authentication requirements may require stage 1: authentication via proxy server account and HTTP method; and stage 2: (1) when the backend service sends such requests to users passed via the URL, the backend service can add specific headers in the HTTP request to mark that such requests are sent to users passed via the URL; (2) HTTP method authentication: the request method needs to be consistent, such as consistently using the GET method; (3) such requests may have an empty body, which can be used as a potential condition for authentication; and (4) if (3) is not applicable and there is actually data sent to these URLs, such requests may have a fixed pattern, and in this case, pattern authentication may be required.
[0078] It should be understood that for non-HTTP egress traffic, the security gateway 330 (or 230) can be configured to sample all non-HTTP protocol services after the request is forwarded to the request forwarding service (RFS). In addition, each request may have registered account information fields, domains, and API paths so that the security gateway can verify the destination. That is, endpoint and account verification may be required.
[0079] Figure 4 is a flow chart illustrating an example process flow 400 for validating egress traffic in a computer network system, in accordance with at least some embodiments described herein.
[0080] It should be understood that the process flow 400 disclosed herein may be executed by one or more processors, such as a local device management CPU of a device (e.g., a gateway, etc.), unless otherwise specified, including, for example Figure 1a processor of one or more of devices 105, 110, 115, 120, 130, 140, 150, 170, 180, and / or 190, Figure 5 CPU 505 and / or any other suitable processor.
[0081] It should also be understood that the processing flow 400 may include one or more operations, actions, or functions, as illustrated by one or more of blocks 410, 420, 430, and 440. These various operations, functions, or actions may correspond, for example, to software, program code, or program instructions executable by a processor, which causes these functions to be performed. Although illustrated as discrete blocks, obvious modifications may be made, for example, two or more blocks may be reordered; additional blocks may be added; and various blocks may be divided into more blocks, combined into fewer blocks, or eliminated depending on the desired implementation. It should be understood that prior to the processing flow 400, operations including initialization and the like may be performed. For example, system parameters and / or application parameters may be initialized. It should be understood that Figure 2 and Figure 3 The processes, operations or actions described in the above may be implemented or performed by a processor. The process flow 400 may start from block 410 .
[0082] At block 410 (start), the processor may perform initialization on the security gateway (230, 330). In an example embodiment, the processor may provide memory space for the security gateway (230, 330) to store predetermined rules for traffic verification. A user (e.g., an administrator, an owner, an authorized user, etc.) (e.g., a first party) may store the predetermined rules in the security gateway (230, 330) or register the predetermined rules to the security gateway (230, 330) through a registration platform. The predetermined rules may include, for example, all patterns (e.g., formats, values, fields, etc.) of a request and / or its corresponding response, which have been predetermined or predefined to satisfy the first party's data privacy policy, corresponding proxy server account header information, etc. (see Figure 2 and 3 ). Processing may proceed from block 410 to block 420.
[0083] At block 420 (Terminate TLS), the processor may (1) receive or obtain egress traffic (e.g., from proxy server 220 or 320, or from load balancer 325), and (2) terminate the TLS communication or process (egress traffic), such as by decrypting or decoding the communication (i.e., decrypting egress traffic), and / or sending the decrypted or decoded egress traffic to (e.g., forwarding proxy server 250). Processing may proceed from block 420 to block 430.
[0084] At block 430 (validate egress traffic), the processor may (1) receive or obtain decrypted or decoded egress traffic from the proxy server (240), (2) forward the decrypted or decoded egress traffic (payload, request, etc. therein) to the gateway proxy (260), and (3) validate the egress traffic based on the predetermined rules in block 410. When the egress traffic matches one or more predetermined rules (e.g., the request and / or response of the egress traffic is present in the security gateway (230, 330) or is registered with the security gateway), the processor may determine and / or mark the egress traffic as valid traffic. When the egress traffic does not match any predetermined rules (e.g., the request and / or response of the egress traffic is not present in the security gateway (230, 330) or is not registered with the security gateway (230, 330)), the processor may determine and / or mark the egress traffic as invalid traffic. It should be understood that the processor may also (1) parse, interpret, and determine the type of the request (or response), and (2) perform endpoint, account, and / or architecture validation on the egress traffic based on its type. If the endpoint, account, and / or schema validation passes based on the predetermined rules (e.g., the fields of the endpoint, account, and / or schema validation match one or more predetermined rules), the processor can determine and / or mark the egress traffic as valid traffic. If the endpoint, account, and / or schema validation does not pass based on the predetermined rules, the processor can determine and / or mark the egress traffic as invalid traffic.
[0085] At block 440 (Forward or Block), the processor may receive or obtain valid or invalid traffic from the gateway proxy 260. The processor may also (1) forward valid traffic to the destination service (e.g., in the external network 270 or 370, via the RFS device or cluster 380, or via the NAT device 390), or (2) block invalid traffic from being sent to the destination service. The processor may also establish or reestablish or restore TLS communications or processes (of valid traffic) before forwarding valid traffic to the destination service, for example, by encrypting or encoding communications (i.e., encrypting egress traffic) for secure communications.
[0086] It should be understood that the processor may also execute Figure 2 and 3 It should also be understood that the features in the embodiments disclosed herein may provide for verification of egress traffic (e.g., endpoint, account, and / or mode verification) from a first party's data center and / or internal services to a second party tool and / or API in an external network. The features in the embodiments disclosed herein may also provide for traffic interception and verification of different types of application layer (L7) network protocols.
[0087] Figure 5 Arranged according to at least some embodiments described herein, suitable for implementing an apparatus (e.g., Figure 1105, 110, 115, 120, 130, 140, 150, 170, 180 and / or 190). It should be understood that Figure 5 The computer system shown in FIG. 1 is for illustration only and is not intended to limit the functionality and applicability of the embodiments described herein.
[0088] As depicted, computer system 500 may include a central processing unit (CPU) 505. CPU 505 may perform various operations and processes based on programs stored in read-only memory (ROM) 510 or programs loaded from storage device 540 to random access memory (RAM) 515. RAM 515 may also store various data and programs required for the operation of system 500. CPU 505, ROM 510, and RAM 515 may be connected to each other via bus 520. An input / output (I / O) interface 525 may also be connected to bus 520.
[0089] Components connected to the I / O interface 525 may also include: input devices 530, including keyboards, mice, digital pens, drawing boards, etc.; output devices 535, including displays, such as liquid crystal displays (LCDs), speakers, etc.; storage devices 540, including hard disks, etc.; and communication devices 545, including network interface cards, such as LAN cards, modems, etc. The communication device 545 may perform communication processing via a network (such as the Internet, WAN, LAN, LIN, cloud, etc.). In an embodiment, a drive 550 may also be connected to the I / O interface 525. Removable media 555, such as magnetic disks, optical disks, magneto-optical disks, semiconductor memories, etc., may be installed on the drive 550 as needed, so that a computer program read from the removable media 555 may be installed in the storage device 540.
[0090] It should be understood that reference Figure 4 The processes described in the flowcharts and / or the processes described in other figures may be implemented as computer software programs and / or hardware. A computer program product may include a computer program stored in a computer-readable non-volatile medium. The computer program includes program code for executing the methods shown in the flowcharts and / or GUIs. In this embodiment, the computer program may be downloaded and installed from a network via a communication device 545, and / or may be installed from a removable medium 555. When the computer program is executed by a central processing unit (CPU) 505, the above-mentioned functions specified in the methods in the embodiments disclosed herein may be implemented.
[0091] It should be understood that the disclosed and other solutions, examples, embodiments, modules and functional operations described in this document can be implemented in digital electronic circuits, or in computer software, firmware or hardware, including the structures disclosed in this document and their structural equivalents, or in a combination of one or more of them. The disclosed and other embodiments herein can be implemented as one or more computer program products, that is, one or more modules of computer program instructions encoded on a computer-readable medium, which are executed by a data processing device or control the operation of the data processing device. The computer-readable medium can be a machine-readable storage device, a machine-readable storage substrate, a memory device, a composition of matter that affects a machine-readable propagation signal, or a combination of one or more of them. The term "data processing device" covers all devices, devices and machines for processing data, including, for example, a programmable processor, a computer or multiple processors or computers. In addition to hardware, the device may also include code that creates an execution environment for the computer program in question, for example, code that constitutes a processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of them.
[0092] A computer program (also referred to as a program, software, software application, script, or code) may be written in any form of programming language, including compiled or interpreted languages, and may be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program does not necessarily correspond to a file in a file system. A program may be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files storing one or more modules, subroutines, or portions of code). A computer program may be deployed to execute on a single computer or on multiple computers located at a single site or distributed across multiple sites and interconnected by a communications network.
[0093] The processes and logic flows described in this document may be performed by one or more programmable processors executing one or more computer programs to perform functions by operating on input data and generating output. The processes and logic flows may also be performed by special purpose logic circuits, and the apparatus may also be implemented as special purpose logic circuits, such as field programmable gate arrays, application specific integrated circuits, and the like.
[0094] Processors suitable for executing computer programs include, for example, general-purpose and special-purpose microprocessors, and any one or more processors of any type of digital computer. Typically, the processor will receive instructions and data from a read-only memory or a random access memory or both. The basic elements of a computer are a processor for executing instructions and one or more memory devices for storing instructions and data. Typically, a computer will also include one or more mass storage devices or operably coupled to receive data from or transfer data to or both of one or more mass storage devices for storing data, one or more mass storage devices such as magnetic disks, magneto-optical disks, or optical disks. However, a computer does not necessarily have such a device. Computer-readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media, and memory devices, including, for example, semiconductor memory devices, such as erasable programmable read-only memory, electrically erasable programmable read-only memory, and flash memory devices; magnetic disks, such as internal hard disks or removable disks; magneto-optical disks; and compact disk read-only memory and digital video disk read-only memory disks. The processor and memory can be supplemented by or incorporated into a dedicated logic circuit.
[0095] It should be understood that different features, variations and multiple different embodiments have been shown and described in various details. What is sometimes described in the present application in the form of specific embodiments is for illustrative purposes only and is not intended to limit or imply that only one specific embodiment or specific embodiments are envisioned. It should be understood that the present disclosure is not limited to any single specific embodiment or enumerated variation. A variety of modifications, variations and other embodiments will occur to those skilled in the art, and these modifications, variations and other embodiments are intended to and are actually covered by the present disclosure. In fact, indeed, the scope of the present disclosure should be determined by the appropriate legal interpretation and the construction (including equivalents) of the present disclosure as understood by those skilled in the art based on the complete disclosure present at the time of submission.
[0096] All aspects:
[0097] It will be appreciated that any aspects may be combined with each other.
[0098] Aspect 1. A security gateway for verifying egress traffic in a computer network system, the security gateway comprising: a proxy server; and a gateway agent, wherein the proxy server is configured to terminate Transport Layer Security (TLS) communications for the egress traffic, the proxy server is also configured to forward the egress traffic to the gateway agent, the gateway agent is configured to verify the egress traffic as valid traffic or invalid traffic based on predetermined verification requirements, and the proxy server is also configured to receive valid traffic or invalid traffic from the gateway agent, and forward valid traffic to a destination service or block invalid traffic.
[0099] Aspect 2. The security gateway of Aspect 1, wherein the proxy server comprises a termination proxy server and a forwarding proxy server, the termination proxy server being configured to terminate TLS communications for egress traffic.
[0100] Aspect 3. The security gateway of Aspect 1 or Aspect 2, wherein the proxy server is further configured to reestablish TLS communication for the valid traffic before forwarding the valid traffic to the destination service.
[0101] Aspect 4. The security gateway of any of Aspects 1-3, wherein the gateway agent is configured to perform endpoint authentication for egress traffic.
[0102] Aspect 5. The security gateway of any of Aspects 1-4, wherein the gateway agent is configured to perform account verification for egress traffic.
[0103] Aspect 6. The security gateway of any of Aspects 1-5, wherein the gateway agent is configured to perform pattern verification on egress traffic.
[0104] Aspect 7. The security gateway of any one of Aspects 1-6, wherein the proxy server is configured to forward valid traffic to the destination service via the request forwarding service.
[0105] Aspect 8. The security gateway of any one of aspects 1-6, wherein the proxy server is configured to forward valid traffic to the destination service via a network address translation service.
[0106] Aspect 9. An egress traffic verification system for a computer network system, the egress traffic verification system comprising: a security gateway, which includes a proxy server and a gateway agent; wherein the proxy server is configured to receive egress traffic and terminate Transport Layer Security (TLS) communications for the egress traffic, and the proxy server is also configured to forward the egress traffic to the gateway agent; the gateway agent is configured to verify the egress traffic as valid traffic or invalid traffic based on predetermined verification requirements, and the proxy server is also configured to receive valid traffic or invalid traffic from the gateway agent, and forward valid traffic to a destination service or block invalid traffic.
[0107] Aspect 10. The egress traffic verification system of Aspect 9, wherein the proxy server comprises a termination proxy server and a forwarding proxy server, and the termination proxy server is configured to receive the egress traffic and terminate TLS communication for the egress traffic.
[0108] Aspect 11. The egress traffic verification system of Aspect 9 or Aspect 10 further includes: a request forwarding service, wherein the proxy server is configured to forward valid traffic to the destination service via the request forwarding service.
[0109] Aspect 12. The egress traffic verification system of any one of Aspects 9-11 further includes: a network address translation service, wherein the proxy server is configured to forward valid traffic to the destination service via the network address translation service.
[0110] Aspect 13. The egress traffic verification system of any one of Aspects 9-12, wherein the proxy server is further configured to reestablish TLS communications for the valid traffic before forwarding the valid traffic to the destination service.
[0111] Aspect 14. The egress traffic verification system of any one of Aspects 9-13, wherein the gateway agent is configured to perform endpoint verification for the egress traffic.
[0112] Aspect 15. The egress traffic verification system of any one of Aspects 9-14, wherein the gateway proxy is configured to perform account verification for the egress traffic.
[0113] Aspect 16. The egress traffic verification system of any one of Aspects 9-15, wherein the gateway agent is configured to perform pattern verification on the egress traffic.
[0114] Aspect 17. The egress traffic verification system of any one of Aspects 9-16 further includes: a second proxy server, wherein the second proxy server is configured to receive the egress traffic from the source service and forward the egress traffic to the load balancer.
[0115] Aspect 18. A method for verifying egress traffic in a computer network system, the method comprising: terminating, by a proxy server, Transport Layer Security (TLS) communications for the egress traffic; forwarding, by the proxy server, the egress traffic to a gateway proxy; verifying, by the gateway proxy, the egress traffic as valid traffic or invalid traffic based on predetermined verification requirements; receiving, by the proxy server, valid traffic or invalid traffic from the gateway proxy; and forwarding, by the proxy server, valid traffic to a destination service or blocking invalid traffic.
[0116] Aspect 19. The method of Aspect 18, wherein the proxy server includes a termination proxy server and a forwarding proxy server, and the method further includes terminating TLS communication for egress traffic by the termination proxy server.
[0117] Aspect 20. The method of Aspect 18 or Aspect 19 further includes: before forwarding the valid traffic to the destination service, the proxy server reestablishes TLS communication for the valid traffic.
[0118] Aspect 21. The method of any one of Aspects 18-20, further comprising: performing endpoint verification for egress traffic by a gateway agent.
[0119] Aspect 22. The method of any one of Aspects 18-21 further includes: performing account verification for egress traffic by a gateway agent.
[0120] Aspect 23. The method according to any one of aspects 18-22, further comprising: performing, by a gateway agent, pattern verification on the egress traffic.
[0121] Aspect 24. The method according to any one of aspects 18-23 further comprises: forwarding the valid traffic to the destination service via the request forwarding service by the proxy server.
[0122] Aspect 25. The method according to any one of aspects 18-24, further comprising: forwarding the valid traffic to the destination service via the network address translation service by the proxy server.
[0123] Aspect 26. A non-transitory computer-readable medium having computer-executable instructions stored thereon, which, when executed, cause one or more processors to perform operations including: terminating Transport Layer Security (TLS) communications for egress traffic; verifying the egress traffic as valid traffic or invalid traffic based on predetermined verification requirements; and forwarding valid traffic to a destination service or blocking invalid traffic.
[0124] The terms used in this specification are intended to describe specific embodiments and are not intended to be limiting. Unless otherwise expressly stated, the terms "a", "an" and "the" also include plural forms. The terms "comprise" and / or "include" when used in this specification specify the presence of stated features, integers, steps, operations, elements and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements and / or components.
[0125] With respect to the foregoing description, it should be understood that changes may be made in detail, particularly in the construction materials employed and the shapes, sizes and arrangements of parts, without departing from the scope of the present disclosure. This specification and the described embodiments are merely exemplary, and the true scope and spirit of the present disclosure are indicated by the following claims.
Claims
1. A security gateway for verifying egress traffic in a computer network system, the security gateway comprising: Proxy server; as well as Gateway Proxy, wherein the proxy server is configured to terminate Transport Layer Security (TLS) communications for the egress traffic, and the proxy server is further configured to forward the egress traffic to the gateway proxy, The gateway agent is configured to verify the egress traffic as valid traffic or invalid traffic based on predetermined verification requirements, and The proxy server is further configured to receive the valid traffic or the invalid traffic from the gateway proxy, and is configured to forward the valid traffic to a destination service or block the invalid traffic.
2. The security gateway of claim 1, wherein the proxy server comprises a termination proxy server and a forwarding proxy server, the termination proxy server being configured to terminate the TLS communication for the egress traffic.
3. The security gateway of claim 1, wherein the proxy server is further configured to reestablish the TLS communication for the valid traffic before forwarding the valid traffic to the destination service.
4. The security gateway of claim 1, wherein the gateway agent is configured to perform endpoint authentication for the egress traffic.
5. The security gateway of claim 1, wherein the gateway agent is configured to perform account verification for the egress traffic.
6. The security gateway of claim 1, wherein the gateway agent is configured to perform pattern validation on the egress traffic.
7. The security gateway of claim 1, wherein the proxy server is configured to forward the valid traffic to the destination service via a request forwarding service.
8. The security gateway of claim 1, wherein the proxy server is configured to forward the valid traffic to the destination service via a network address translation service.
9. An egress flow verification system for a computer network system, the egress flow verification system comprising: A security gateway, the security gateway comprising a proxy server and a gateway proxy; wherein the proxy server is configured to receive egress traffic and is configured to terminate Transport Layer Security (TLS) communications for the egress traffic, The proxy server is further configured to forward the egress traffic to the gateway proxy; The gateway agent is configured to verify the egress traffic as valid traffic or invalid traffic based on predetermined verification requirements, and The proxy server is further configured to receive the valid traffic or the invalid traffic from the gateway proxy, and is configured to forward the valid traffic to a destination service or block the invalid traffic.
10. The egress traffic verification system according to claim 9, wherein the proxy server comprises a termination proxy server and a forwarding proxy server, the termination proxy server being configured to receive the egress traffic and being configured to terminate the TLS communication for the egress traffic.
11. The egress flow verification system of claim 9, further comprising: Request forwarding service, The proxy server is configured to forward the valid traffic to the destination service via the request forwarding service.
12. The egress flow verification system of claim 9, further comprising: Network Address Translation Service, The proxy server is configured to forward the valid traffic to the destination service via the network address translation service.
13. The egress traffic verification system of claim 9, wherein the proxy server is further configured to reestablish the TLS communication for the valid traffic before forwarding the valid traffic to the destination service.
14. The egress traffic verification system of claim 9, wherein the gateway agent is configured to perform endpoint verification for the egress traffic.
15. The egress traffic verification system of claim 9, wherein the gateway proxy is configured to perform account verification for the egress traffic.
16. The egress traffic validation system of claim 9, wherein the gateway agent is configured to perform pattern validation on the egress traffic.
17. The egress flow verification system of claim 9, further comprising: Second proxy server, The second proxy server is configured to receive the egress traffic from a source service and is configured to forward the egress traffic.
18. A method for verifying egress traffic in a computer network system, the method comprising: Terminate TLS communications for egress traffic by the proxy server; The proxy server forwards the egress traffic to the gateway proxy; The gateway agent verifies the egress traffic as valid traffic or invalid traffic based on a predetermined verification requirement; The proxy server receives the valid traffic or invalid traffic from the gateway proxy; as well as The proxy server forwards the valid traffic to a destination service or blocks the invalid traffic.
19. The method of claim 18, wherein the proxy server comprises a terminating proxy server and a forwarding proxy server, the method further comprising terminating, by the terminating proxy server, the TLS communication for the egress traffic.
20. The method of claim 18, further comprising: The TLS communication for the valid traffic is reestablished by the proxy server before forwarding the valid traffic to the destination service.
Citation Information
Cited By
Transmission method of application layer protocol, computer program product, electronic equipment and storage medium
CN119484513A
A transmission method of an application layer protocol, a computer program product, an electronic device and a storage medium
CN119484513B
