Patent Grant
12348494
The present disclosure relates to technologies of controlling network access of a terminal based on a tunnel between a plurality of networks.
Because an environment of controlling network access of a terminal based on a tunneling technology is able to allow an authorized terminal to access a target network through an authorized tunnel to fundamentally block access of an unauthorized terminal or access using a general TCP/IP mechanism, there are advantages capable of minimizing security and threat inherent in the TCP/IP and authorizing network access based on various pieces of identification information (a terminal ID, a user ID, and the like) in a network access process based on an IP address.
The tunneling technology used in general, for example, IP security protocol virtual private network (IPSec VPN), Open VPN, or generic routing encapsulation (GRE) tunneling, is based on an access target for each terminal or each network, and a secure socket layer (SSL)/transport layer security (TLS) VPN is devised to be connected to an access target for each smaller web service.
Such a tunneling technology is a network technology which operates in Layer 3/4 and Layer 7 of open system interconnection (OSI) and establishes a criterion (entity) transmitting data packets to the network for each terminal (source node). Because the network access of the terminal is by a request of each application (a transmission request of a data packet) run (operated) on the terminal, the tunneling technology established for each terminal has a structure incapable of performing access control for each application.
Therefore, a tunnel is a minimal controllable unit, and should be able to control flow of data packets for each application and each destination network and should be able to block data packets transmitted from a terminal or network boundary to an unauthorized tunnel or unauthorized data packets.
Particularly, when data packets are transmitted to a cloud service network over an uncontrollable network (e.g., the Internet, a mobile network operator network, or the like) depending on a destination or should pass through a plurality of network boundaries between networks for each resource or each segment which should be protected in an internal network, that is, when there are a plurality of network boundaries in which different management policies are accompanied on a path to a destination, a series of technologies for routing only authorized flow to a boundary of a destination network should be accompanied at the same time as a technology for blocking the unauthorized flow.
In general, a VPN technology is used or a multi-protocol label switching (MPLS) and dynamic multipoint VPN (DMVPN) technology is used, to support a boundary and a boundary of networks. However, control of authorized flow and unauthorized flow, and a control method for routing of the authorized flow are not provided, and network access control (NAC) and firewall technologies should be essentially applied for partial network control.
A terminal may be protected by an end to end security (EES) technology or a technology such as SSL/TLS to ensure confidentiality of data packets depending on an application of an active state and a destination service. However, because the VPN technology encrypts and encapsulates all data packets which start from the terminal by means of a tunneling technology, there is a problem in which data packets are doubly encrypted when having different protection systems depending on a destination service.
Details described in the background art are written to increase the understanding of the background of the present disclosure, which may include details rather than an existing technology well known to those skilled in the art.
An aspect of the present disclosure provides an apparatus for controlling network access to generate a tunnel connecting an application of a terminal with a gateway of a destination network, based on a tunnel between the application of the terminal and the gateway and a tunnel between the gateway and the gateway, in a tunnel-based access control network environment configured with a plurality of networks, such that a data packet from the application of the terminal may be securely transmitted to a destination node, and a method thereof.
The technical problems to be solved by the present disclosure are not limited to the aforementioned problems, and any other technical problems not mentioned herein will be clearly understood from the following description by those skilled in the art to which the present disclosure pertains. Furthermore, it may be easily seen that purposes and advantages of the present disclosure may be implemented by means indicated in claims and a combination thereof.
According to an aspect of the present disclosure, an apparatus for controlling network access device may include a memory storing a tunnel policy, a tunnel routing policy, and a tunnel table and a control device that generates tunnel information and data flow information based on the tunnel policy, the tunnel routing policy, and the tunnel table depending on a network access request of a terminal and transmits the generated tunnel information and the generated data flow information to the terminal and a gateway of each network such that a tunnel between the terminal and a destination network is generated. The control device may generate the data flow information based on information of the destination network and an application ID of the terminal or the information of the destination network and an ID of the terminal.
In an embodiment of the present disclosure, the control device may identify a routing path of each tunnel located on a communication path from the terminal to the destination network based on the tunnel policy and the tunnel routing policy and may identify whether an available tunnel is present based on the tunnel table.
In an embodiment of the present disclosure, the control device may generate and transmit the tunnel information and the data flow information to the terminal and the gateway of each network, when an available tunnel is present in each section from the terminal to the destination network.
In an embodiment of the present disclosure, the control device may transmit information necessary to generate a tunnel together with the generated tunnel information and the generated data flow information to the terminal and the gateway of each network, when an available tunnel is present in each section from the terminal to the destination network.
In an embodiment of the present disclosure, the control device may transmit the data flow information including whether network address translation (NAT) is performed, an NAT address, whether encryption is performed, an encryption algorithm, or an encryption key to the terminal.
In an embodiment of the present disclosure, the control device may transmit the data flow information including network address translation (NAT) is performed, an NAT address, a data flow header, whether decryption is performed, a decryption algorithm, a decryption key, whether routing is performed, or a routing tunnel ID to the gateway of each network.
According to another aspect of the present disclosure, a method for controlling network access device may include storing a tunnel policy, a tunnel routing policy, and a tunnel table, generating tunnel information and data flow information based on the tunnel policy, the tunnel routing policy, and the tunnel table depending on a network access request of a terminal, and transmitting the generated tunnel information and the generated data flow information to the terminal and a gateway of each network such that a tunnel between the terminal and a destination network is generated. The data flow information may be generated based on information of the destination network and an application ID of the terminal or the information of the destination network and an ID of the terminal.
An embodiment of the present disclosure may include identifying a routing path of each tunnel located on a communication path from the terminal to the destination network based on the tunnel policy and the tunnel routing policy and identifying whether an available tunnel is present based on the tunnel table.
An embodiment of the present disclosure may include transmitting the generated tunnel information and the generated data flow information to the terminal and the gateway of each network, when an available tunnel is present in each section from the terminal to the destination network and transmitting information necessary to generate a tunnel together with the generated tunnel information and the generated data flow information to the terminal and the gateway of each network, when the available tunnel is present in each section from the terminal to the destination network.
In an embodiment of the present disclosure, the data flow information transmitted to the terminal may include whether network address translation (NAT) is performed, an NAT address, whether encryption is performed, an encryption algorithm, or an encryption key.
In an embodiment of the present disclosure, the data flow information transmitted to the gateway of each network may include whether network address translation (NAT) is performed, an NAT address, a data flow header, whether decryption is performed, a decryption algorithm, a decryption key, whether routing is performed, or a routing tunnel ID.
According to another aspect of the present disclosure, a method for controlling network access device may include receiving data flow information, performing a manipulation process in a data packet based on the data flow information, and transmitting the data packet, the manipulation process of which is performed, through a tunnel to a destination network. The data flow information may be generated based on information of the destination network and an application ID of the terminal or the information of the destination network and an ID of the terminal.
An embodiment of the present disclosure may include replacing a destination IP and port information based on an NAT address included in the data flow information.
An embodiment of the present disclosure may include encrypting the data packet based on a type of an encryption algorithm and an encryption key included in the data flow information, inserting a header included in the data flow information into the encrypted data packet, and fragmenting and transmitting the data packet into which the header is inserted.
According to another aspect of the present disclosure, a method for controlling network access device may include receiving a data packet from a terminal through an authorized tunnel, identifying whether the data packet is authorized based on a header included in previously stored data flow information, decrypting the authorized data packet based on whether decryption is performed, a decryption algorithm, and a decryption key included in the data flow information, replacing an IP header of the decrypted data packet with a network address translation (NAT) address based on whether NAT is performed and the NAT address included in the data flow information, and removing the header of the data packet, the header being replaced with the NAT address. The data flow information may be generated based on information of a destination network and an application ID of the terminal or the information of the destination network and an ID of the terminal.
An embodiment of the present disclosure may include determining the data packet as an authorized data packet, when a header is present in the data packet and is identical to a header included in the data flow information.
An embodiment of the present disclosure may further include receiving and processing the data packet, the header of which is removed, when the gateway is a gateway of the destination network.
An embodiment of the present disclosure may further include forwarding the data packet, the header of which is removed, to a gateway of the destination, when the gateway is not the gateway of the destination network.
The system for controlling the network access and the method thereof according to an embodiment of the present disclosure may generate a tunnel connecting an application of a terminal with a gateway of a destination network, based on a tunnel between the application of the terminal and the gateway and a tunnel between the gateway and the gateway, in a tunnel-based access control network environment configured with a plurality of networks, such that a data packet from the application of the terminal may be securely transmitted to a destination node.
Hereinafter, various embodiments of the disclosure may be described with reference to accompanying drawings. However, it should be understood that this is not intended to limit the present disclosure to specific implementation forms and includes various modifications, equivalents, and/or alternatives of embodiments of the present disclosure.
A singular form of a noun corresponding to an item in the present disclosure may include one or plural of the items, unless the relevant context clearly indicates otherwise. As used herein, each of such phrases as “A or B,” “at least one of A and B,” “at least one of A or B,” “A, B, or C,” “at least one of A, B, and C,” and “at least one of A, B, or C,” may include any one of, or all possible combinations of the items enumerated together in a corresponding one of the phrases. As used herein, such terms as “1st” and “2nd,” or “first” and “second” may be used to simply distinguish a corresponding component from another, and does not limit the components in other aspect (e.g., importance or order). It is to be understood that if an element (e.g., a first element) is referred to, with or without the term “operatively” or “communicatively”, as “coupled with,” “coupled to,” “connected with,” or “connected to” another element (e.g., a second element), it means that the element may be coupled with the other element directly (e.g., wiredly), wirelessly, or via a third element.
Each (e.g., a module or a program) of components described in the present disclosure may include singular or plural entities. According to various embodiments, one or more of corresponding components or operations may be omitted, or one or more other components may be added. Alternatively or additionally, a plurality of components (e.g., modules or programs) may be integrated into a single component. In such a case, according to various embodiments, the integrated component may still perform one or more functions of each of the plurality of components in the same or similar manner as they are performed by a corresponding one of the plurality of components before the integration. According to various embodiments, operations performed by the module, the program, or another component may be carried out sequentially, in parallel, repeatedly, or heuristically, or one or more of the operations may be executed in a different order or omitted, or one or more other operations may be added.
As used in the present disclosure, the term “module” may include a unit implemented in hardware, software, or firmware, and may interchangeably be used with other terms, for example, “logic,” “logic block,” “part,” or “circuitry”. A module may be a single integral component, or a minimum unit or part thereof, adapted to perform one or more functions. For example, according to an embodiment, the module may be implemented in the form of an application-specific integrated circuit (ASIC).
Various embodiments of the present disclosure may be implemented as software (e.g., a program or an application) including instructions that are stored in a machine-readable storage medium (e.g., a memory). For example, a processor of the machine may invoke at least one of the one or more instructions stored in the storage medium, and execute it, with or without using one or more other components under the control of the processor. This allows the machine to be operated to perform at least one function according to the at least one instruction invoked. The one or more instructions may include a code generated by a complier or a code executable by an interpreter. The machine-readable storage medium may be provided in the form of a non-transitory storage medium. Here, the term “non-transitory” simply means that the storage medium is a tangible device and does not include a signal (e.g., an electromagnetic wave), but this term does not differentiate between where data is semipermanently stored in the storage medium and where data is temporarily stored in the storage medium.
A method according to various embodiments disclosed in the present disclosure may be included and provided in a computer program product. The computer program product may be traded as a product between a seller and a buyer. The computer program product may be distributed in the form of a machine-readable storage medium (e.g., compact disc read only memory (CD-ROM)), or be distributed (e.g., downloaded or uploaded) online via an application store (e.g., PlayStore™), or between two user devices (e.g., smart phones) directly. If distributed online, at least a part of the computer program product may be temporarily generated or at least temporarily stored in the machine-readable storage medium, such as a memory of the manufacturer's server, a server of the application store, or a relay server.
As shown in
A terminal 11 may be various types of devices capable of performing data communication. For example, the terminal 11 may include a portable device, such as a smartphone and a tablet, a computer device, such as a desktop or a laptop, a multimedia device, a medical device, a camera, a wearable device, a virtual reality (VR) device, or a home appliance, but not limited to the above-mentioned devices. The terminal 11 may be referred to as an ‘electronic device’ or a ‘node’.
The terminal 11 may attempt to access the second network 20 or the third network 30, and may transmit data to the first destination node 23 included in the second network 20 through the tunnel 120 or may transmit data to the second destination node 33 included in the third network 30 through the tunnel 130. At this time, the first destination node 23 and the second destination node 33 may include an electronic device, such as a terminal, as well as a server.
When access of the terminal 11 to the second network 20 is granted, the terminal 11 may communicate with the first destination node 23 included in the second network 20. When access of the terminal 11 to the third network 30 is granted, the terminal 11 may communicate with the second destination node 33 included in the third network 30.
Security solutions such as an NAC 12, a firewall 13, and a VPN 14 are applicable to a boundary of the first network 10, and security solutions such as a VPN 21 and a firewall 22 are applicable to a boundary of the second network 20 and a boundary of the third network 30. A network environment in which various security solutions (equipment) are applied to the boundary of the network has problems of investment cost (CAPEX) and operation cost (OPEX), difficulties with policy establishment and management for each equipment, or problems with security and management of a TCP/IP technology, limited network section protection technology application, or the like.
As shown in
The first network 10 may include a terminal 11 and a first gateway 15. The second network 20 may include a second gateway 24 and a first destination node 23. The third network 30 may include a third gateway 34 and a second destination node 33.
The terminal 11 and the first gateway 15 may be connected through a first tunnel 110. The first gateway 15 and the second gateway 24 may be connected through a second tunnel 120. The first gateway 15 and the third gateway 34 may be connected through a third tunnel 130.
The terminal 11 may communicate with the first destination node 23 of the second network 20 through a fourth tunnel 210 connecting the first tunnel 110 with the second tunnel 120 and may communicate with the second destination node 33 of the third network 30 through a fifth tunnel 220 connecting the first tunnel 110 with the third tunnel 130. At this time, the fourth tunnel 210 may connect an access control application 111 in the terminal 11 with the first destination node 23, and the fifth tunnel 220 may connect the access control application 111 in the terminal 11 with the second destination node 33. A target application 112 may transmit a data packet to the first destination node 23 or the second destination node 33 under control of the access control application 111. The four tunnel 210 and the fifth tunnel 220 may refer to a tunnel routing technology among the first tunnel 110, the second tunnel 120, and the third tunnel 130.
The terminal 11 may include the access control application 111 for managing network access of an application stored in the terminal 11 and a network driver (not shown). For example, when an access event of the target application 112 included in the terminal 11 to the first destination node 23 occurs, the access control application 111 may determine whether access of the target application 112 is possible. When the access of the target application 112 is possible, the access control application 111 may transmit a data packet to the second gateway 24 through the fourth tunnel 210. In other words, the access control application 111 may control transmission of a data packet by means of a kernel including an operating system in the terminal 11 and the network driver. The access control application 111 may play a role as a kind of agent in conjunction with network access of the target application 112.
The controller 40 may be a network access control device, which may be implemented as, for example, a server (or a cloud server). The controller 40 may manage data transmission between the respective gateways 15, 24, and 34 to ensure reliability of the data transmission in a network environment. For example, the controller 40 may manage access of the terminal 11 to the destination network 20 or 30 by means of policy information or blacklist information, may mediate generation of the authorized first tunnel 110 between the terminal 11 and the first gateway 15, may mediate generation of the authorized second tunnel 120 between the first gateway 15 and the second gateway 24, may mediate generation of the authorized third tunnel 130 between the first gateway 15 and the third gateway 34, may mediate generation of the authorized fourth tunnel 210 between the terminal 11 and the second gateway 24, may mediate generation of the authorized fifth tunnel 220 between the terminal 11 and the third gateway 34, or may remove each tunnel 110, 120, 130, 210, or 220 depending on a security event collected from each gateway 15, 24, or 34. The terminal 11 may communicate with the destination network 20 or 30 through only the tunnel authorized by the controller 40. When there is no authorized tunnel, access of the terminal 11 to the destination network 20 or 30 may be blocked. According to an embodiment, the controller 40 may transmit and receive a control data packet with the terminal 11 to perform various operations (e.g., registration, grant, authentication, update, and end) associated with network access of the terminal 11. Flow (e.g., 250) in which the control data packet is transmitted may be referred to as control flow.
The controller 40 may propagate data flow including information which should be processed for each node which is present on a communication path, in conjunction with mediating the access, to provide a structure in the form of a dynamic policy, which provides a necessary access control policy at a necessary time. For example, data flow information and tunnel information between the terminal 11 and the first gateway 15 may be transmitted to the terminal 11, data flow information or/and tunnel information between the first gateway 23 and the second gateway 24 may be transmitted to the first gateway 23, and data flow information or/and tunnel information between the second gateway 24 and the first destination node may be transmitted to the second gateway 24. Because the data flow includes a structure in the form of a similar tunnel including header information for determining whether there are authorized flow and an authorized data packet, whether the data packet is encrypted, an encryption algorithm, encryption key information, data packet manipulation information, and the like, data packet control optimized for various flow generated between one terminal and multiple destinations is possible.
Each gateway 15, 24, or 34 may generate the authorized tunnel 110, 120, 130, 210, or 220 with the terminal 11 under control of the controller 40. As an example, the second gateway 24 may forward a data packet, received through the authorized tunnel 210, to the first destination node 23. Flow (e.g. 270) in which a data packet is transmitted among the terminal 11, the first gateway 15, and the second gateway 24 may be referred to as data flow. Each gateway 15, 24, or 34 may be connected with the controller 40 based on a cloud.
Each gateway 15, 24, or 34 may further include communication circuitry (e.g., communication circuitry 430 of
Each gateway 15, 24, or 34 may perform processing, such as routing, decryption, or network address translation (NAT) of the data packet, based on the data flow received from the controller 40.
As shown in
The access policy database 311 may include information about an identified network, a network accessible by a terminal, a user or an application, and/or a service. For example, when access to a destination network is requested from the terminal, a controller may determine whether the identified network (e.g., the network to which the terminal belongs), the terminal, the user (e.g., the user of the terminal), and/or the application (e.g., the application included in the terminal) is accessible to the destination network based on the access policy database 311.
The tunnel policy database 312 may include a type of each tunnel 110, 120, 130, 210, or 220 on a connection path, an encryption method, and encryption level information. For example, when access to a destination network 20 or 30 is requested from the terminal, a controller 40 may provide the terminal with an optimal tunnel for accessing the destination network 20 or 30 and information about it based on the tunnel policy database 312.
The blacklist policy database 313 may include a policy for permanently or temporarily blocking access of a specific terminal. The blacklist policy database 313 may be generated based on a risk level of a security event among security events collected on a periodic basis from the terminal or the gateway, a cycle of occurrence, and/or information identified by means of an action analysis (e.g., at least one of a terminal identifier (ID), an IP address, a media access control (MAC) address, a user ID).
The blacklist database 314 may include a list of at least one of a terminal, an IP address, a MAC address, or a user blocked by the blacklist policy database 313. For example, when identification information of the terminal requesting to access the destination network is included in the blacklist database 314, the controller may deny the access request of the terminal to separate the terminal from the destination network.
The control flow table 315 is an example of a session table for managing flow (e.g., control flow) of a control data packet generated between the terminal and the controller. When the terminal successfully accesses the controller, control flow information may be generated by the controller. The control flow information may include at least one of identification information of control flow, an IP address identified when accessing and authenticating the controller, a terminal ID, or a user ID. For example, when access to the destination network is request from the terminal, the controller may search for control flow information by means of the control flow identification information received from the terminal and may map at least one of the IP address, the terminal ID, or the user ID included in the found control flow information to the access policy database 311, thus determining whether access of the terminal is possible and whether to generate a tunnel.
According to an embodiment, the control flow may have an expiration time. The terminal should update the expiration time of the control flow. When the expiration time is not updated during a certain time, the control flow (or control flow information) may be removed. Furthermore, when it is determined to need to immediately block access depending on a security event collected from the terminal or the gateway, the controller may remove the control flow depending on an access end request of the terminal. When the control flow is removed, because the tunnel and the data flow, which are previously generated, are also removed, access of the terminal to a network may be blocked.
The tunnel table 316 may be a table for managing a tunnel connected between the terminal and the gateway or a destination node. The tunnel may be generated for, for example, each device or IP. When a tunnel is generated between the terminal and the gateway, the tunnel table 316 may include tunnel identification information, control flow identification information when the tunnel is dependent on control flow, a tunnel end point (TEP), a tunnel start point (TSP), a tunnel algorithm, a tunnel type, and/or additional information for managing the tunnel.
The data flow table 317 may be a table for managing flow (e.g., data flow) in which a detailed data packet is transmitted between the terminal and the gateway or the destination node. The data flow may be generated for each TCP session in the tunnel, for each application of a source terminal, or in a more detailed unit. The data flow table 317 may include data flow identification information, control flow identification (ID) information when data flow is dependent on control flow, sequential tunnel routing information for each section when passing through one or more gateways on a communication path, whether a data packet is encrypted or decrypted in each section, encryption and decryption algorithms, encryption and decryption keys, header information for detecting whether a data packet transmitted from the terminal is an authorized data packet, a tunnel ID corresponding to each data flow, an application ID for identifying data flow of an authorized target, a destination IP address, and/or a service port.
The tunnel routing policy database 318 may include a type of each tunnel 110, 120, 130, 210, or 220 on a connection path, an encryption method, and encryption level information. For example, when access to the destination network 20 or 30 is requested from the terminal, the controller 40 may provide the terminal with an optimal tunnel for accessing the destination network 20 or 30 and information about it based on the tunnel policy database 312.
As shown in
The processor 410 may control the overall operation of the terminal 11. The processor 410 may include one processor single core or may include a plurality of processor cores. For example, the processor 410 may include a multi-core such as a dual-core, a quad-core, or a hexa-core. According to embodiments, the processor 410 may further include a cache memory located internally or externally. According to various embodiments, the processor 410 may be configured with one or more processors. For example, the processor 410 may include at least one of an application processor, a communication processor, or a graphical processing unit (GPU).
All or a portion of the processor 410 may be electrically or operatively combined or connected with another component (e.g., the memory 420, the communication circuitry 430, or the display 440) in the terminal. The processor 410 may receive commands of other components of the terminal, may interpret the received commands, and may perform calculation or may process data, depending on the interpreted commands. The processor 410 may interpret and process a message, data, an instruction, or a signal received from the memory 420, the communication circuitry 430, or the display 440. The processor 410 may generate a new message, data, instruction, or signal based on the received message, data, instruction, or signal. The processor 410 may provide the memory 420, the communication circuitry 430, or the display 440 with the processed or generated message, data, instruction, or signal.
The processor 410 may process data or a signal which is generated or occurs by a program. For example, the processor 410 may request an instruction, data, or a signal from the memory 420 to run or control the program. The processor 410 may record (or store) or update an instruction, data, or a signal in the memory 420 to run or control the program.
The memory 420 may store an instruction controlling the terminal 11, a control instruction code, control data, or user data. For example, the memory 420 may include at least one of an application program, an operating system (OS), middleware, or a device driver.
The memory 420 may include one or more of a volatile memory or a non-volatile memory. The volatile memory may include a dynamic random access memory (DRAM), a static RAM (SRAM), a synchronous DRAM (SDRAM), a phase-change RAM (PRAM), a magnetic RAM (MRAM), a resistive RAM (RRAM), a ferroelectric RAM (FeRAM), or the like. The non-volatile memory may include a read only memory (ROM), a programmable ROM (PROM), an electrically programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a flash memory, or the like.
The memory 420 may further include a non-volatile medium such as a hard disk drive (HDD), a solid state disk (SSD), an embedded multi media card (eMMC), or a universal flash storage (UFS).
According to an embodiment, the memory 420 may store some of pieces of information included in a memory (e.g., a memory 330 of
The communication circuitry 430 may assist in establishing a wired or wireless communication connection between the terminal and an external electronic device (e.g., the controller 40 of
The display 440 may output content, data, or a signal. The display 440 may display image data processed by the processor 410. The display 440 may be combined with a plurality of touch sensors (not shown) capable of receiving a touch input or the like to be configured with an integrated touch screen. When the display 440 is configured with the touch screen, the plurality of touch sensors may be arranged over the display 440 or under the display 440.
As shown in
According to another embodiment, when the access control application 111 is not installed in the terminal 11 or when the malicious application bypasses control of the access control application 111, an unauthorized data packet may be transmitted from the terminal 11. In this case, because a first gateway 24 and a second gateway 34 which are present on a boundary of a network block a data packet received through an unauthorized tunnel (operation 520), a data packet transmitted from the terminal 11 (e.g., a data packet for generating a TCP session) may fail to arrive at a destination network 20 or 30. In other words, the terminal 11 may be separated from the destination network 20 or 30.
For a terminal 11 to access a destination network 20 or 30, because there is a need to be authorized by a controller 40, an access control application 111 of the terminal 11 may attempt to access the controller 40 by requesting the controller 40 to generate control flow.
In operation 605, the terminal 11 may detect a controller access event. For example, the access control application 111 is installed and run in the terminal 11, and the terminal 11 may detect that access to the controller 40 is requested by means of the access control application 111.
As an example, referring to
In operation 610, the terminal 11 may request controller access from the controller 40 in response to detecting the controller access event. The terminal 11 may request the controller access by means of the access control application 111. According to an embodiment, the access control application 111 may transmit identification information (e.g., a terminal ID, an IP address, or a MAC address) of the terminal 11, a type of the terminal 11, a location of the terminal 11, an environment of the terminal 11, identification information of a network to which the terminal 11 belongs, and/or identification information of the access control application 111.
In operation 615, the controller 40 may identify whether access of the terminal 11 is possible in response to the received request. According to an embodiment, the controller 40 may identify whether the access of the terminal 11 is possible based on a database included in a memory 330. For example, the controller 40 may identify whether the access of the terminal 11 is possible based on whether information received from the access control application 111 is included in an access policy database 311 and/or whether the identification information of the terminal 11 and/or the network to which the terminal 11 belongs is included in a blacklist database 314.
When the access of the terminal 11 is possible, the controller 40 may generate control flow between the terminal 11 and the controller 40. In this case, the controller 40 may generate control flow identification information in the form of a random number and may store the identification information of the terminal 11 and/or the network to which the terminal 11 belongs in a control flow table. Information (e.g., control flow identification information and/or control flow information) stored in the control flow table 315 may be used to authenticate a user of the terminal 11, update information of the terminal 11, identify a policy for network access of the terminal 11, and/or check validity.
When the control flow is generated, in operation 620, the controller 40 may transmit a response to the controller access request to the terminal 11. In this case, the controller 40 may transmit the generated control flow identification information to the terminal 11.
In operation 625, the terminal 11 may process a result value depending on the received response. For example, the access control application 111 may store the received control flow identification information and may display a user interface screen indicating that the controller access is completed to a user. When the controller access is completed, a network access request of the terminal 11 for a destination network may be controlled by the controller 40.
According to another embodiment, the controller 40 may determine that access of the terminal 11 is impossible. For example, when the identification information of the terminal 11 and/or the network to which the terminal 11 belongs is included in the blacklist database, the controller 40 may determine that the access of the terminal 11 is impossible. In this case, the controller 40 may fail to generate control flow in operation 615 and may transmit a response indicating that the access of the terminal 11 is impossible in operation 620.
When receiving the response indicating that the access of the terminal 11 is impossible, in operation 625, the terminal 11 may output a user interface screen indicating that controller access is impossible to the user. For example, referring to
For a terminal 11 to obtain detailed access right for a destination network 20 or 30, an access control application 111 of the terminal 11 may receive authentication for a user of the terminal 11 from a controller 40.
In operation 805, the terminal 11 may receive an input for user authentication. The input for the user authentication may be, for example, a user input inputting a user ID and a password. For another example, the input for the user authentication may be a user input (e.g., biometric information) for more reinforced authentication.
In operation 810, the terminal 11 may request user authentication from the controller 40. For example, the access control application 111 may transmit input information for user authentication to the controller 40. When control flow between the terminal 11 and the controller 40 is generated in advance, the access control application 111 may transmit the input information for user authentication together with control flow identification information.
In operation 815, the controller 40 may authenticate a user based on information received from the terminal 11. For example, the controller 40 may determine whether the user is accessible depending on an access policy and whether the user is included in a blacklist based on a user ID, a password, and/or reinforced authentication information, which are included in the received information, and a database (e.g., an access policy database 311 or a blacklist database 314 of
When the user is authenticated, the controller 40 may add identification information (e.g., a user ID) of the user to identification information of control flow. The added user identification information may be used for controller access or network access of the authenticated user.
In operation 820, the controller 40 may transmit information indicating that the user is authenticated as a response to the user authentication request to the terminal 11.
In operation 825, the terminal 11 may process a result value for the user authentication. For example, the terminal 11 may display a user interface screen indicating that the user authentication is completed to the user.
According to another embodiment, the controller 40 may determine that the user authentication is impossible. For example, when the identification information of the user is included in the blacklist database 314, the controller 40 may determine that the user authentication is impossible. In this case, in operation 820, the controller 40 may transmit information indicating that the user authentication is impossible to the terminal 11. In operation 825, the terminal 11 may display a user interface screen indicating that the user authentication fails.
The terminal 11 authorized from a controller 40 may control network access of other applications (e.g., a target application 112) stored in the terminal 11 by means of an access control application 111 to ensure trusted data transmission.
In operation 905, the access control application 111 may detect a network access event. For example, the access control application 111 may detect that the target application 112 such as a web browser attempts to access a destination network such as the Internet. For example, a user may run the web browser and may input and call a web address to be accessed.
In operation 910, the access control application 111 may request network access of the target application 112 from the controller 40. In this case, the access control application 111 may transmit identification information of the target application 112, an IP of an access target, and service port information together with identification information of control flow generated between the terminal 11 and the controller 40 to the controller 40.
In operation 915, the controller 40 may identify an access policy based on the request received from the access control application 111. For example, the controller 40 may determine whether access of the target application 112 is possible based on whether the information received from the access control application 111 meets the access policy of the controller 40. When the access of the target application 112 is impossible, the controller 40 may transmit information indicating the access is impossible to the terminal 11. In this case, the access control application 111 may drop a data packet of the target application 112 and may display a user interface screen indicating that access to a network is impossible.
In operation 920, when the access of the target application 112 is possible, the controller 40 may identify a tunnel policy and a tunnel routing policy. For example, the controller 40 may identify a type and a scheme of a tunnel between gateways which are present on a communication path, a type and a scheme of a tunnel between the gateway and a destination node, a type and a scheme of a tunnel between a terminal and the gateway, and a series of tunnel routing paths for tunnels respectively connected from the terminal to gateways or nodes of a destination network based on the tunnel policy and the tunnel routing policy and may identify whether there is a valid tunnel on each path in a tunnel table.
In operation 925, when there is the valid tunnel in each section from a source (the terminal 11) to a destination, the controller 40 may generate and transmit tunnel information and data flow information necessary to use the valid tunnel to the terminal 11 (930). For example, the tunnel information and the data flow information are shown in
In operation 925, when there is no valid tunnel in each section from the source (the terminal 11) to the destination, the controller 40 may generate information (e.g., a tunnel type, a scheme, authentication information, and/or an IP or a port of a TEP) necessary to generate a tunnel and information included in a data flow table and may transmit the generated information to the first gateway 15, the second gateway 24, and the terminal 11. At this time, likewise, the data flow information optimized for the corresponding node may be transmitted to the corresponding node. When there is no tunnel policy for generating a new tunnel or when the new tunnel is not generated, the controller 40 may notify the terminal 11 that network access is impossible. In this case, the access control application 211 may drop a data packet of the target application 221 and may display a user interface screen indicating that the network access is impossible.
The access control application 111 may process a result value depending to a response of the controller 40. When receiving the information that the network access of the target application is impossible or the information that there is no authorized tunnel, the access control application 111 may drop a data packet and may output a user interface screen indicating that the network access is impossible. For example, referring to
When the tunnel information and the data flow information are transmitted to the terminal 11 and the respective gateways 15 and 24, in operation 945, a fourth tunnel 210 may be generated between the terminal 11 and the second gateway 24. A data packet of the target application 112 may be transmitted through the tunnel generated in operation 945 (950). In this case, the access control application 111 may receive a data packet from the destination network and may process data provided from the destination network. For example, referring to
The access control application 111 may first identify whether there is an authorized tunnel between the target application 112 and the second gateway 24 before performing operation 910. For example, the access control application 111 may identify identification information of the target application 112, identification information and service port information of the second network 20, and authentication information (e.g., header information of data flow) and may identify whether there is a tunnel corresponding to the identified information in a data flow table stored in a memory of the terminal 11. When there is an authorized tunnel, the access control application 111 may fail to request network access. When there is no authorized tunnel, in operation 910, the access control application 111 may request the network access.
To ensure integrity and stability of the target application, the access control application 111 may further check validity of the target application before requesting the network access. For example, the access control application 111 may perform whether the target application 112 is forged or falsified, code signing check, and/or fingerprint check. For another example, the access control application 111 may identify whether the target application 112, an access target IP, and a service port are accessible based on an access policy database 311 received from the controller 40. When it fails in checking the validity of the target application 112, the access control application 111 may drop a data packet without requesting the network access. In this case, the access control application 111 may display a user interface screen indicating that the access is impossible. When it succeeds in checking the validity of the target application 112, in operation 910, the access control application 111 may request network access.
As shown in
When the data flow information is transmitted to a terminal 11, whether the encryption is performed, the encryption algorithm, and the encryption key are included. When the data flow information is transmitted to a destination gateway 24, whether decryption is performed, a decryption algorithm, and a decryption key may be included rather than whether the encryption is performed, the encryption algorithm, and the encryption key.
As shown in
As described in detail in
The communication device 310 may provide an interface for communicating with the first gateway 15, the second gateway 24, or a third gateway 34.
The control device 320 may perform the overall control such that respective components may normally perform their own functions. Such a control device 320 may be implemented in the form of hardware, may be implemented in the form of software, or may be implemented in the form of a combination thereof. Preferably, the control device 320 may be implemented as, but not limited to, a microprocessor.
The control device 320 may generate tunnel information and data flow information based on a tunnel policy database 312 and a tunnel routing policy database 318, which are stored in the memory 330, depending on a network access request from the terminal 11.
The control device 320 may identify a routing path of each tunnel located on a communication path from a source terminal to a destination gateway or a destination node, based on the tunnel policy database 312 and the tunnel routing policy database 318, and may identify whether an available tunnel is present based on a tunnel table 316.
When the available tunnel is present in each section from the terminal 11 to the destination gateway 24, the control device 320 may generate and transmit tunnel information and data flow information to each of the terminal 11 and the respective gateways 15 and 24. For example, the tunnel information and the data flow information transmitted to the terminal 11 may include information (header insertion, encryption, and the like) necessary for the terminal 11 to transmit a data packet to the first gateway 15, the tunnel information and the data flow information transmitted to the first gateway 15 may include information (header check and forwarding, routing, decryption, header removal, reception, or the like) necessary for the first gateway 15 to transmit a data packet to the second gateway 24, and the tunnel information and the data flow information transmitted to the second gateway 24 may include information (header check and forwarding, routing, decryption, header removal, reception, or the like) necessary to transmit data to a first destination node 23.
When the available tunnel is not present in each section from the terminal 11 to the destination gateway 24, the control device 320 may generate and transmit a series of pieces of information (e.g., a tunnel type, a scheme, authentication information, an IP and a port of the TEP, and the like) necessary to generate a tunnel between the terminal 11 and the destination gateway 24 and the above-mentioned data flow information to each of the terminal 11 and the respective gateways 15 and 24. Likewise, the tunnel information and the data flow information may include information optimized for a corresponding destination.
When the control device 320 is unable to generate a new tunnel in each section from a source to a destination, it may notify the terminal 11 that network access is impossible.
An access control application 111 of a terminal 11 may perform a data packet manipulation process based on data flow information transmitted from a controller 40 (1310).
In operation 1320, the access control application 111 may identify whether to replace a destination IP and port information of a data packet by an NAT policy based on the data flow information. At this time, when replacement is needed, the access control application 111 may replace the destination IP and the port information based on an NAT address included in the data flow information.
In operation 1330, the access control application 111 may identify whether the data packet is encrypted based on the data flow information. At this time, when encryption is needed, the access control application 111 may encrypt the data packet based on a type of an encryption algorithm and an encryption key, which are included in the data flow information. The access control application 111 may insert a header into the encrypted data packet to allow each gateway 15 or 24 on a communication path to identify whether there is an authorized data packet using the header and perform routing control. The access control application 111 may insert the header (a data flow header) included in the data flow information into the encrypted data packet.
In operation 1340, the access control application 111 may identify whether any of manipulation processes (NAT and encryption) for the data packet is performed. When any of the manipulation processes is performed, the data packet may be fragmented based on a maximum transmit unit (MTU) value (1350).
In operation 1360, the access control application 111 may transmit the data packet. A header may be inserted into a payload or a TCP or IP header option field and the other location of the data packet prior to tunneling. For example, for a data packet passing through multiple boundaries, a tunneling technology may support only encapsulation, and the payload of the data packet may be encrypted by means of an internal encryption algorithm through the above process. Encryption in units of tunneling and encryption and a type in units of data packets may be provided by a method optimized according to an environment and situation of a network depending on a tunnel policy of the controller 40. A structure of the data packet is shown in, for example,
As shown in
The second gateway 24 may receive and store tunnel information and data flow information from a controller 40.
The second gateway 24 may receive a data packet (1510). At this time, the second gateway 24 may identify whether the data packet is received through an authorized tunnel (a fourth tunnel 210) and may drop the data packet, when the data packet is not received through the authorized tunnel.
When the data packet is received through the authorized tunnel, the second gateway 24 may inspect a header of the data packet (1520). For example, the second gateway 24 may identify whether there is a header in the data packet. When there is no header, the second gateway 24 may drop the data packet. When there is the header, the second gateway 24 may identify whether there is data flow corresponding to the header in a data flow table. When there is no data flow corresponding to the header, the data packet may be dropped. When there is the data flow, the data packet may be authorized.
For the authorized data packet, the second gateway 24 may decrypt the data packet based on whether decryption is performed, a decryption algorithm, and a decryption key, which are included in the data flow information (1530). At this time, when it fails in the decryption, the second gateway 24 may drop the data packet.
The second gateway 24 may replace an IP header of the data packet into an NAT address based on whether NAT is performed and the NAT address, which are included in the data flow information.
The second gateway 24 may remove the header of the data packet (1550) and may process reception.
When the first gateway 15 performs the processes of
As another example, the first gateway 15 may determine whether a header of data flow is present in the data packet received from the terminal 11, without performing the processes of
In operation 1605, a terminal 11 may request a controller 40 to release network access. For example, the terminal 11 may transmit identification information of control flow between the terminal 11 and a controller 40 together with information requesting to release the network access to the controller 40.
According to an embodiment, the terminal 11 may attempt to release the network access in response to a network access release event such as a request of a user, restart of the terminal 11, or a request of an access control application 111. For example, referring to
In operation 1610, the controller 40 may remove (or release) control flow corresponding to the received identification information in response to the request of the terminal 11.
In operation 1615, the controller 40 may request a second gateway 24 or/and a first gateway 15 to remove a tunnel dependent on the removed control flow. The tunnel dependent on the removed control flow may be plural in number. In this case, the controller 40 may request to remove all tunnels dependent on the removed control flow.
In operation 1620, the second gateway 24 may remove a tunnel in response to the request of the controller 40. When the tunnel is removed, a data packet transmitted to a destination network corresponding to the controlled tunnel may be blocked by the access control application 111 or the second gateway 24. Through the above-mentioned operation, a system including the terminal 11 may release the authorized tunnel if necessary to provide perfect blocking and separation of the terminal 11 from the network.
| Number | Date | Country | Kind |
|---|---|---|---|
| 10-2020-0045526 | Apr 2020 | KR | national |
The present application is the National Stage of International Application No. PCT/KR2020/012924, filed on Sep. 24, 2020, which claims priority from U.S. patent application Ser. No. 16/580,866, filed on Sep. 24, 2019, and Ser. No. 16/580,974, filed on Sep. 24, 2019. International Application No. PCT/KR2020/012924 also claims priority to Korean Patent Application No. 10-2020-0045526, filed on Apr. 14, 2020. The present application is a continuation-in-part of U.S. patent application Ser. No. 16/580,974, filed on Sep. 24, 2019. All prior applications are herein incorporated by reference.
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/KR2020/012924 | 9/24/2020 | WO |
| Publishing Document | Publishing Date | Country | Kind |
|---|---|---|---|
| WO2021/060854 | 4/1/2021 | WO | A |
| Number | Name | Date | Kind |
|---|---|---|---|
| 5995623 | Kawano | Nov 1999 | A |
| 6076168 | Fiveash | Jun 2000 | A |
| 6738909 | Cheng | May 2004 | B1 |
| 6963982 | Brustoloni | Nov 2005 | B1 |
| 7139276 | Sitaraman | Nov 2006 | B1 |
| 7215667 | Davis | May 2007 | B1 |
| 7302496 | Metzger | Nov 2007 | B1 |
| 7318234 | Dharmarajan | Jan 2008 | B1 |
| 7346770 | Swander | Mar 2008 | B2 |
| 7359983 | Maufer | Apr 2008 | B1 |
| 7606902 | Rao et al. | Oct 2009 | B2 |
| 7760636 | Cheriton | Jul 2010 | B1 |
| 7920701 | Cox | Apr 2011 | B1 |
| 7978714 | Rao et al. | Jul 2011 | B2 |
| 8000327 | Minei | Aug 2011 | B1 |
| 8019868 | Rao et al. | Sep 2011 | B2 |
| 8024488 | Salowey et al. | Sep 2011 | B2 |
| 8289968 | Zhuang | Oct 2012 | B1 |
| 8291119 | Rao et al. | Oct 2012 | B2 |
| 8363650 | Rao et al. | Jan 2013 | B2 |
| 8385199 | Coward | Feb 2013 | B1 |
| 8612612 | Dukes | Dec 2013 | B1 |
| 8843998 | Fu et al. | Sep 2014 | B2 |
| 8892778 | Rao et al. | Nov 2014 | B2 |
| 8897299 | Rao et al. | Nov 2014 | B2 |
| 8923853 | Shaw | Dec 2014 | B1 |
| 9088564 | Hobson et al. | Jul 2015 | B1 |
| 9106538 | Asnis | Aug 2015 | B1 |
| 9143481 | Wood | Sep 2015 | B2 |
| 9143942 | Agarwal et al. | Sep 2015 | B2 |
| 9148408 | Glazemakers | Sep 2015 | B1 |
| 9240938 | Dimond et al. | Jan 2016 | B2 |
| 9252972 | Dukes | Feb 2016 | B1 |
| 9356866 | Sivaramakrishnan | May 2016 | B1 |
| 9402002 | Hao | Jul 2016 | B1 |
| 9578052 | Cp et al. | Feb 2017 | B2 |
| 9715597 | Smith et al. | Jul 2017 | B2 |
| 9860208 | Ettema et al. | Jan 2018 | B1 |
| 9912673 | Evenden et al. | Mar 2018 | B2 |
| 9984230 | Pikhur et al. | May 2018 | B2 |
| 10033766 | Gupta et al. | Jul 2018 | B2 |
| 10129207 | Wan | Nov 2018 | B1 |
| 10162767 | Spurlock et al. | Dec 2018 | B2 |
| 10176344 | Smith et al. | Jan 2019 | B2 |
| 10205743 | Cp et al. | Feb 2019 | B2 |
| 10243833 | Tang et al. | Mar 2019 | B2 |
| 10326672 | Scheib et al. | Jun 2019 | B2 |
| 10339303 | Mehta et al. | Jul 2019 | B2 |
| 10402577 | Knapp et al. | Sep 2019 | B2 |
| 10484334 | Lee et al. | Nov 2019 | B1 |
| 10659434 | Kim et al. | May 2020 | B1 |
| 10659462 | Kim et al. | May 2020 | B1 |
| 10764249 | Kommula | Sep 2020 | B1 |
| 10785111 | Hill et al. | Sep 2020 | B2 |
| 10812576 | Yuan | Oct 2020 | B1 |
| 10903990 | Ladd | Jan 2021 | B1 |
| 11271777 | Kim | Mar 2022 | B2 |
| 11379611 | Horesh | Jul 2022 | B1 |
| 20010039576 | Kanada | Nov 2001 | A1 |
| 20020010800 | Riley et al. | Jan 2002 | A1 |
| 20020049899 | Kenworthy | Apr 2002 | A1 |
| 20020161905 | Haverinen | Oct 2002 | A1 |
| 20020163920 | Walker et al. | Nov 2002 | A1 |
| 20030041172 | Calvignac | Feb 2003 | A1 |
| 20030055978 | Collins | Mar 2003 | A1 |
| 20030106067 | Hoskins | Jun 2003 | A1 |
| 20030123481 | Neale | Jul 2003 | A1 |
| 20030131263 | Keane | Jul 2003 | A1 |
| 20030142823 | Swander | Jul 2003 | A1 |
| 20030188192 | Tang | Oct 2003 | A1 |
| 20030212900 | Liu | Nov 2003 | A1 |
| 20040081150 | Chiang | Apr 2004 | A1 |
| 20040088385 | Blanchet | May 2004 | A1 |
| 20040136534 | Stiscia | Jul 2004 | A1 |
| 20040139339 | Yeh | Jul 2004 | A1 |
| 20040190449 | Mannal | Sep 2004 | A1 |
| 20040215819 | Tsuruoka | Oct 2004 | A1 |
| 20050060328 | Suhonen et al. | Mar 2005 | A1 |
| 20050111399 | Sapienza et al. | May 2005 | A1 |
| 20050273609 | Eronen | Dec 2005 | A1 |
| 20050273853 | Oba et al. | Dec 2005 | A1 |
| 20050283604 | Deshpande | Dec 2005 | A1 |
| 20060018291 | Patel | Jan 2006 | A1 |
| 20060029062 | Rao et al. | Feb 2006 | A1 |
| 20060029063 | Rao et al. | Feb 2006 | A1 |
| 20060029064 | Rao et al. | Feb 2006 | A1 |
| 20060037071 | Rao et al. | Feb 2006 | A1 |
| 20060153067 | Vasseur | Jul 2006 | A1 |
| 20060159029 | Samuels et al. | Jul 2006 | A1 |
| 20060182111 | Wahl | Aug 2006 | A1 |
| 20060190720 | Ozaki | Aug 2006 | A1 |
| 20060215684 | Capone | Sep 2006 | A1 |
| 20060242405 | Gupta | Oct 2006 | A1 |
| 20060262808 | Lin | Nov 2006 | A1 |
| 20070088959 | Cox | Apr 2007 | A1 |
| 20070147421 | Kim | Jun 2007 | A1 |
| 20070186100 | Wakameda | Aug 2007 | A1 |
| 20070189486 | Ise | Aug 2007 | A1 |
| 20080080509 | Khanna | Apr 2008 | A1 |
| 20080130515 | Vasseur | Jun 2008 | A1 |
| 20080148379 | Xu et al. | Jun 2008 | A1 |
| 20080162924 | Chinitz | Jul 2008 | A1 |
| 20080313240 | Freking | Dec 2008 | A1 |
| 20090077618 | Pearce et al. | Mar 2009 | A1 |
| 20090245204 | Voyer | Oct 2009 | A1 |
| 20090287955 | Matsumoto | Nov 2009 | A1 |
| 20100002693 | Rao et al. | Jan 2010 | A1 |
| 20100005311 | Okamoto | Jan 2010 | A1 |
| 20100011056 | Bryson | Jan 2010 | A1 |
| 20100024026 | Ylonen et al. | Jan 2010 | A1 |
| 20100061253 | Kaminsky et al. | Mar 2010 | A1 |
| 20100199325 | Raleigh | Aug 2010 | A1 |
| 20100278338 | Chang | Nov 2010 | A1 |
| 20100306816 | McGrew | Dec 2010 | A1 |
| 20110032868 | Huang | Feb 2011 | A1 |
| 20110158237 | McDysan | Jun 2011 | A1 |
| 20110161416 | McDysan | Jun 2011 | A1 |
| 20110261723 | Yamato | Oct 2011 | A1 |
| 20110271093 | McKenna | Nov 2011 | A1 |
| 20120014314 | Chen | Jan 2012 | A1 |
| 20120084368 | Go | Apr 2012 | A1 |
| 20120303835 | Kempf | Nov 2012 | A1 |
| 20120304276 | Legacy | Nov 2012 | A1 |
| 20130054761 | Kempf | Feb 2013 | A1 |
| 20130083799 | Xie et al. | Apr 2013 | A1 |
| 20130128892 | Rao et al. | May 2013 | A1 |
| 20130163470 | Chidambaram et al. | Jun 2013 | A1 |
| 20130166720 | Takashima et al. | Jun 2013 | A1 |
| 20130232263 | Kelly et al. | Sep 2013 | A1 |
| 20130318345 | Hengeveld | Nov 2013 | A1 |
| 20130322255 | Dillon | Dec 2013 | A1 |
| 20130336159 | Previdi | Dec 2013 | A1 |
| 20140059356 | Nesnow | Feb 2014 | A1 |
| 20140101716 | Touboul | Apr 2014 | A1 |
| 20140105382 | Liu | Apr 2014 | A1 |
| 20140108668 | Zhang et al. | Apr 2014 | A1 |
| 20140122716 | Santhiveeran et al. | May 2014 | A1 |
| 20140156720 | Janakiraman | Jun 2014 | A1 |
| 20140211799 | Yu | Jul 2014 | A1 |
| 20140237137 | Ervin et al. | Aug 2014 | A1 |
| 20140237539 | Wing et al. | Aug 2014 | A1 |
| 20140241247 | Kempf | Aug 2014 | A1 |
| 20140301396 | Hong | Oct 2014 | A1 |
| 20140301397 | Zhou | Oct 2014 | A1 |
| 20140334488 | Guichard | Nov 2014 | A1 |
| 20140359159 | Diaz-Cuellar | Dec 2014 | A1 |
| 20150026768 | Wu | Jan 2015 | A1 |
| 20150074756 | Deng et al. | Mar 2015 | A1 |
| 20150085664 | Sachdev | Mar 2015 | A1 |
| 20150095648 | Nix | Apr 2015 | A1 |
| 20150109967 | Hogan | Apr 2015 | A1 |
| 20150121449 | Cp et al. | Apr 2015 | A1 |
| 20150188949 | Mahaffey | Jul 2015 | A1 |
| 20150261972 | Lee | Sep 2015 | A1 |
| 20150281060 | Xiao | Oct 2015 | A1 |
| 20150281131 | Bhat | Oct 2015 | A1 |
| 20150281173 | Quinn | Oct 2015 | A1 |
| 20150341259 | Li et al. | Nov 2015 | A1 |
| 20150347768 | Martin et al. | Dec 2015 | A1 |
| 20150371055 | Park | Dec 2015 | A1 |
| 20160043866 | Nixon | Feb 2016 | A1 |
| 20160092700 | Smith et al. | Mar 2016 | A1 |
| 20160094661 | Jain | Mar 2016 | A1 |
| 20160099917 | Glazemakers et al. | Apr 2016 | A1 |
| 20160105471 | Nunes | Apr 2016 | A1 |
| 20160142293 | Hu et al. | May 2016 | A1 |
| 20160180092 | Aktas | Jun 2016 | A1 |
| 20160182550 | Spurlock | Jun 2016 | A1 |
| 20160191380 | De | Jun 2016 | A1 |
| 20160197830 | Ulevitch | Jul 2016 | A1 |
| 20160226779 | Kikuchi | Aug 2016 | A1 |
| 20160261557 | Herrero | Sep 2016 | A1 |
| 20160283728 | Antonopoulos | Sep 2016 | A1 |
| 20160285735 | Chen et al. | Sep 2016 | A1 |
| 20160285846 | Abe | Sep 2016 | A1 |
| 20160292430 | Antonopoulos | Oct 2016 | A1 |
| 20160294710 | Sreeramoju | Oct 2016 | A1 |
| 20160315853 | Liste | Oct 2016 | A1 |
| 20160352685 | Park | Dec 2016 | A1 |
| 20160359673 | Gupta et al. | Dec 2016 | A1 |
| 20160360352 | Khan et al. | Dec 2016 | A1 |
| 20160366108 | Kamble | Dec 2016 | A1 |
| 20160366187 | Kamble | Dec 2016 | A1 |
| 20160371484 | Mehta et al. | Dec 2016 | A1 |
| 20160373304 | Sharma | Dec 2016 | A1 |
| 20160378685 | Spurlock et al. | Dec 2016 | A1 |
| 20160378975 | Pikhur et al. | Dec 2016 | A1 |
| 20160379003 | Kapoor et al. | Dec 2016 | A1 |
| 20160381051 | Edwards et al. | Dec 2016 | A1 |
| 20160381076 | Kamble | Dec 2016 | A1 |
| 20170012956 | Lee et al. | Jan 2017 | A1 |
| 20170026349 | Smith | Jan 2017 | A1 |
| 20170034052 | Chanda | Feb 2017 | A1 |
| 20170041229 | Zheng | Feb 2017 | A1 |
| 20170063782 | Jain et al. | Mar 2017 | A1 |
| 20170063927 | Schultz | Mar 2017 | A1 |
| 20170078184 | Tang et al. | Mar 2017 | A1 |
| 20170099160 | Mithyantha | Apr 2017 | A1 |
| 20170104851 | Arangasamy | Apr 2017 | A1 |
| 20170118228 | Cp et al. | Apr 2017 | A1 |
| 20170171055 | Wang | Jun 2017 | A1 |
| 20170223063 | Herrero | Aug 2017 | A1 |
| 20170237552 | Karame | Aug 2017 | A1 |
| 20170237760 | Holeman | Aug 2017 | A1 |
| 20170264695 | Markovitz | Sep 2017 | A1 |
| 20170317954 | Masurekar | Nov 2017 | A1 |
| 20170339631 | Pugaczewski et al. | Nov 2017 | A1 |
| 20170346731 | Pukhraj Jain | Nov 2017 | A1 |
| 20170353378 | Chen | Dec 2017 | A1 |
| 20170359247 | Dixon | Dec 2017 | A1 |
| 20170374025 | Pan | Dec 2017 | A1 |
| 20180013786 | Knopf | Jan 2018 | A1 |
| 20180018476 | Smith et al. | Jan 2018 | A1 |
| 20180026949 | Kimn et al. | Jan 2018 | A1 |
| 20180041470 | Schultz | Feb 2018 | A1 |
| 20180063077 | Tumuluru | Mar 2018 | A1 |
| 20180123827 | Josyula | May 2018 | A1 |
| 20180124183 | Kozat | May 2018 | A1 |
| 20180139176 | Sato | May 2018 | A1 |
| 20180262487 | Zaifman | Sep 2018 | A1 |
| 20180309786 | Apelewicz | Oct 2018 | A1 |
| 20180324761 | Velev et al. | Nov 2018 | A1 |
| 20180337788 | Gajek | Nov 2018 | A1 |
| 20180359231 | Vemulapalli | Dec 2018 | A1 |
| 20190005148 | Lam | Jan 2019 | A1 |
| 20190014152 | Verma et al. | Jan 2019 | A1 |
| 20190021122 | Kawasaki et al. | Jan 2019 | A1 |
| 20190036708 | Fregly | Jan 2019 | A1 |
| 20190097805 | Shin et al. | Mar 2019 | A1 |
| 20190109822 | Clark et al. | Apr 2019 | A1 |
| 20190109848 | Clark et al. | Apr 2019 | A1 |
| 20190155752 | Spurlock et al. | May 2019 | A1 |
| 20190173736 | Ponnuswamy et al. | Jun 2019 | A1 |
| 20190173850 | Jain | Jun 2019 | A1 |
| 20190173891 | Cp et al. | Jun 2019 | A1 |
| 20190190746 | Lee | Jun 2019 | A1 |
| 20190205045 | Hugot et al. | Jul 2019 | A1 |
| 20190207747 | Durvasula | Jul 2019 | A1 |
| 20190222559 | Wang et al. | Jul 2019 | A1 |
| 20190238592 | Qureshi et al. | Aug 2019 | A1 |
| 20190246148 | Oh | Aug 2019 | A1 |
| 20190246160 | Williams | Aug 2019 | A1 |
| 20190278908 | Mehta et al. | Sep 2019 | A1 |
| 20190306018 | Steverson | Oct 2019 | A1 |
| 20190306035 | Scheib et al. | Oct 2019 | A1 |
| 20190312775 | Patil | Oct 2019 | A1 |
| 20190313295 | Xu | Oct 2019 | A1 |
| 20190335022 | Pasam | Oct 2019 | A1 |
| 20190349317 | Lu | Nov 2019 | A1 |
| 20190349369 | Bengtson et al. | Nov 2019 | A1 |
| 20190372948 | Varghese | Dec 2019 | A1 |
| 20190379532 | Si | Dec 2019 | A1 |
| 20190394049 | Hartwig et al. | Dec 2019 | A1 |
| 20200036735 | Canard | Jan 2020 | A1 |
| 20200052928 | Lee | Feb 2020 | A1 |
| 20200068049 | Ngo | Feb 2020 | A1 |
| 20200076733 | Venkataraman | Mar 2020 | A1 |
| 20200076740 | Kim | Mar 2020 | A1 |
| 20200076927 | Barthur | Mar 2020 | A1 |
| 20200112540 | Venkataraman | Apr 2020 | A1 |
| 20200119981 | Guthrie | Apr 2020 | A1 |
| 20200153604 | Sun | May 2020 | A1 |
| 20200162919 | Velev et al. | May 2020 | A1 |
| 20200177550 | Valluri et al. | Jun 2020 | A1 |
| 20200177606 | Valluri et al. | Jun 2020 | A1 |
| 20200177658 | Barthur | Jun 2020 | A1 |
| 20200184112 | Wallach | Jun 2020 | A1 |
| 20200213154 | Han et al. | Jul 2020 | A1 |
| 20200213280 | Guim Bernat | Jul 2020 | A1 |
| 20200228503 | Zhang | Jul 2020 | A1 |
| 20200244625 | Tummalapenta et al. | Jul 2020 | A1 |
| 20200252898 | Bild | Aug 2020 | A1 |
| 20200274851 | Qiao et al. | Aug 2020 | A1 |
| 20200287749 | Glazemakers et al. | Sep 2020 | A1 |
| 20200314179 | He | Oct 2020 | A1 |
| 20200351254 | Xiong | Nov 2020 | A1 |
| 20200389393 | Bosch et al. | Dec 2020 | A1 |
| 20210218777 | Chander et al. | Jul 2021 | A1 |
| 20210243163 | Miriyala et al. | Aug 2021 | A1 |
| 20210266156 | Zee | Aug 2021 | A1 |
| 20210266161 | Zee | Aug 2021 | A1 |
| 20210328830 | Kim | Oct 2021 | A1 |
| 20210360083 | Duggal et al. | Nov 2021 | A1 |
| 20220104181 | Velev et al. | Mar 2022 | A1 |
| 20220109698 | Roh | Apr 2022 | A1 |
| 20220247720 | Kim | Aug 2022 | A1 |
| 20230247003 | Chanak et al. | Aug 2023 | A1 |
| Number | Date | Country |
|---|---|---|
| 104284385 | Jan 2015 | CN |
| 105471748 | Apr 2016 | CN |
| 107445011 | Dec 2017 | CN |
| 3254415 | Dec 2017 | EP |
| 2007243655 | Sep 2007 | JP |
| 2009163546 | Jul 2009 | JP |
| 2010011122 | Jan 2010 | JP |
| 2011015327 | Jan 2011 | JP |
| 2011166704 | Aug 2011 | JP |
| 5239341 | Jul 2013 | JP |
| 2015053069 | Mar 2015 | JP |
| 2016189127 | Nov 2016 | JP |
| 2017535843 | Nov 2017 | JP |
| 2017537501 | Dec 2017 | JP |
| 2018508140 | Mar 2018 | JP |
| 2018524843 | Aug 2018 | JP |
| 2019079504 | May 2019 | JP |
| 1020020088728 | Nov 2002 | KR |
| 1020030075810 | Sep 2003 | KR |
| 100692653 | Mar 2007 | KR |
| 1020070037650 | Apr 2007 | KR |
| 100748698 | Aug 2007 | KR |
| 1020070102698 | Oct 2007 | KR |
| 100856674 | Aug 2008 | KR |
| 1020100008740 | Jan 2010 | KR |
| 101020470 | Feb 2011 | KR |
| 1020120045859 | May 2012 | KR |
| 101173583 | Aug 2012 | KR |
| 1020130045919 | May 2013 | KR |
| 1020130076798 | Jul 2013 | KR |
| 1020140055857 | May 2014 | KR |
| 1020140074357 | Jun 2014 | KR |
| 101481337 | Jan 2015 | KR |
| 1020150013453 | Feb 2015 | KR |
| 1020150088494 | Aug 2015 | KR |
| 101561108 | Oct 2015 | KR |
| 101578193 | Dec 2015 | KR |
| 1020160029660 | Mar 2016 | KR |
| 1020160056118 | May 2016 | KR |
| 1020160123069 | Oct 2016 | KR |
| 1020170010835 | Feb 2017 | KR |
| 101743559 | Jun 2017 | KR |
| 1020170063795 | Jun 2017 | KR |
| 1020170132608 | Dec 2017 | KR |
| 1020180006413 | Jan 2018 | KR |
| 1020180019273 | Feb 2018 | KR |
| 1020180030023 | Mar 2018 | KR |
| 1020180032864 | Apr 2018 | KR |
| 101861201 | May 2018 | KR |
| 1020180062838 | Jun 2018 | KR |
| 1020180086964 | Aug 2018 | KR |
| 101910605 | Oct 2018 | KR |
| 1020180132868 | Dec 2018 | KR |
| 2019-0037088 | Apr 2019 | KR |
| 1020190036504 | Apr 2019 | KR |
| 1020190052541 | May 2019 | KR |
| 1020190073114 | Jun 2019 | KR |
| 102119257 | Jun 2020 | KR |
| 102146568 | Aug 2020 | KR |
| WO 2013170177 | Nov 2013 | WO |
| 2014062337 | Apr 2014 | WO |
| 2016057177 | Apr 2016 | WO |
| 2016190641 | Dec 2016 | WO |
| 2017016473 | Feb 2017 | WO |
| WO 2017081864 | May 2017 | WO |
| WO 2017126556 | Jul 2017 | WO |
| WO 2018116123 | Jun 2018 | WO |
| 2021060856 | Apr 2021 | WO |
| Entry |
|---|
| Extended European Search Report dated Oct. 28, 2022 for European Pat. App. No. 20868832.5. |
| Extended European Search Report dated Oct. 17, 2022 for European Pat. App. No. 20868932.3. |
| International Search Report and Written Opinion of the International Searching Authority; Application No. PCT/KR2020/012924; Completed: Jan. 5, 2021; Mailing Date: Jan. 5, 2021; 11 Pages. |
| Hassan, Suhaidi, et al.; Border Gateway Protocol based Path Vector mechanism for inter-domain routing in Software Defined Network environment; IEEE Conference on Open Systems (ICOS); Langkawi, Malaysia; Oct. 10, 2016; 5 Pages. |
| Glatz, Eduard, et al.; Classifying Internet One-way Traffic; Proceedings of the 12th ACM SIGMETRICS/Performance joint international conference on Measurement and Modeling of Computer Systems (SIGMETRICS 12); Association for Computing Machinery; New York, NY, USA; May 15, 2012; 29 Pages. |
| Bilger, Brent, et al.; Cloud Security Alliance (CSA); Software-Defined Perimeter Working Group (SDP) Specification 1.0; Apr. 2014; 28 Pages. |
| Garbis, Jason, et al.; Cloud Security Alliance (CSA); Software-Defined Perimeter Architecture Guide; Mar. 10, 2020; 43 Pages. |
| Waliyi, Adebayo Gbenga; Study and Implementation of Wireless Sensor Networks to Manage Energy in a Smart Home; African University of Science and Technology; AUST Institutional Repository; Abuja, Nigeria; Dec. 15, 2017; 69 Pages. |
| Ikuta, Takayuki, et al.; Software Defined Perimeter (SDP) Usage Scenario Collection, Version 1.0; Japan Cloud Security Alliance, SDP Working Group; Apr. 25, 2019; 52 Pages. |
| Korean Office Action; Application No. 10-2020-0117543; Mailed: Nov. 13, 2020; 6 pages. |
| Korean Notice of Allowance; Application No. KR 10-2020-0105345; Dated: May 2, 2021. |
| Japanese Office Action; Application No. 2021-039780; Issued: Jun. 8, 2021; 13 Pages. |
| Extended European Search Report; Application No. 21162189.1; Completed: Jul. 7, 2021; Issued: Jul. 16, 2021; 44 Pages. |
| US Notice of Allowance; U.S. Appl. No. 16/580,974; Issued: Mar. 14, 2022; 8 Pages. |
| Japanese First Office Action; Application No. 2022-515499; 7 Pages. |
| Japanese Office Action; Application No. 2022002658; Issued: Mar. 3, 2022; 10 Pages. |
| Japanese Office Action issued Dec. 5, 2024 for Japanese Patent Appl. No. 2023136154. |
| Number | Date | Country | |
|---|---|---|---|
| 20220247719 A1 | Aug 2022 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16580974 | Sep 2019 | US |
| Child | 17656080 | US | |
| Parent | 16580866 | Sep 2019 | US |
| Child | 16580974 | US |
