WO2023146308A1

WO2023146308A1 - System for controlling network access on basis of controller, and method therefor

Info

Publication number: WO2023146308A1
Application number: PCT/KR2023/001210
Authority: WO
Inventors: 김영랑
Original assignee: 프라이빗테크놀로지 주식회사
Priority date: 2022-01-27
Filing date: 2023-01-26
Publication date: 2023-08-03
Also published as: KR102439881B1

Abstract

A node according to one embodiment disclosed in the present document may store instructions that cause an access control application to detect a data packet transmission event of a target application, check a transmission protocol of the data packet, determine the existence of a data flow that corresponds to the transmission protocol and identification information of the target application and is authorized by an external server, insert authentication information into the data packet on the basis of the transmission protocol and the authentication information contained in the data flow, and transmit the data packet on the basis of the transmission protocol.

Description

Controller-based system for controlling network access and method therefor

Mutual Citation with Related Applications

The present invention claims the benefit of priority based on Korean Patent Application No. 10-2022-0012071 filed on 2022.01.27., and includes all contents disclosed in the literature of the Korean patent application as part of this specification.

technology field

Embodiments disclosed in this document relate to a system and method for controlling a controller-based network connection.

Multiple devices may communicate data over a network. For example, the terminal may transmit or receive data with a server through the Internet. The network may include a private network such as an intranet as well as a public network such as the Internet.

The terminal performs communication with the server by utilizing IP (Internet Protocol)-based TCP (Transmission Control Protocol) or UDP (User Datagram Protocol), and controls the connection between the source IP and destination IP authorized in TCP or UDP technology. Firewall technology may be used. In the case of such IP communication, since data packets are transmitted in plain text, there is a problem in that a third party can easily view important information of the data packet using sniffing technology such as tapping equipment or rouge WiFi. To solve this problem, VPN (Virtual Private Network) technology and tunneling technology for encrypting data packets between the terminal and the server are used.

Tunneling technology may be limited in scope to controlling only network access subordinate to a specific network or service, since tunneling usage and related specifications are all different depending on service servers. In addition, since the tunneling technology needs to set a wide network bandwidth, it may be difficult to control communication of each application running in the terminal and the unit of a service server to which the application wants to access.

Tunneling-based data packet authentication method identifies an authorized terminal through a tunneling connection process, identifies an application that is the actual communication subject, and at the same time identifies a destination IP and port that the application can access according to authentication information to secure network access. By controlling it, it is possible to provide a safer technology than the existing network security technology. However, since tunneling-based application and data packet authentication technology can be used only when tunneling is connected between the terminal and the gateway, it may be difficult to use in an environment where tunneling is difficult to configure.

When transmitting authentication information by inserting authentication information into data packets in an environment where it is difficult to configure tunneling, the malicious purpose application identifies the authentication data packet through network sniffing and confirms the destination network information that can be accessed through the authentication information. Then, malicious data packets are transmitted by inserting corresponding authentication information, so that unauthorized applications can access the network.

That is, when authentication information is inserted into data packets in an environment where it is difficult to configure tunneling, confidentiality and integrity cannot be guaranteed, so the network access control function by the gateway is incapacitated through various attack routines.

In addition, when tunneling technology is used, there are restrictions on the number and number of target networks that can be tunneled by a terminal, and depending on the type of tunneling, compatibility problems such as loss of data packets occur in the process of transmitting the corresponding data packets. Because of the existence of the tunneling technology, the terminal may encounter a problem in which the tunneling technology cannot be used when the number of target network boundaries to be accessed varies.

Various embodiments disclosed in this document are intended to provide a system and method for solving the above problems in a network environment.

A node according to an embodiment disclosed herein includes communication circuitry, a processor operatively connected to the communication circuitry, and a memory operatively connected to the processor and storing a connection control application and a target application; The memory, when executed by the processor, causes the node, through the access control application, to detect a transmission event of a data packet of the target application, to determine a transmission protocol of the data packet, and to determine the transmission protocol and the target application. Checking whether there is a data flow corresponding to the identification information and authorized from an external server, inserting authentication information into the data packet based on the transmission protocol and authentication information included in the data flow, and inserting the data packet Commands to be transmitted based on the transmission protocol may be stored.

A gateway according to one embodiment disclosed herein includes communication circuitry, a memory, and a processor operatively coupled to the communication circuitry and the memory, the processor receiving a data packet from a node, and storing the data packet in Check whether there is a data flow corresponding to the included information and authorized from an external server, and if the data flow exists, check the transmission protocol of the data packet, and process the data packet based on the transmission protocol It can be.

A server according to an embodiment disclosed herein includes communication circuitry, a memory for storing a database, and a processor operatively connected to the communication circuitry and the memory, wherein the processor controls access control applications of nodes from a network Receives an access request, wherein the network access request includes identification information of a target application included in the node, a transmission protocol, and identification information of a destination network, and the identification information of the target application, the transmission protocol, and identification of the destination network. Based on the information, it is checked whether access to the gateway of the target application is possible through the access policy of the database, and if access is possible, a data flow including authentication information is generated based on the authentication policy of the database. and transmit the data flow to the node and the gateway.

A method of operating an access control application installed in a node according to an embodiment disclosed in this document includes detecting a transmission event of a data packet of a target application, checking a transmission protocol of the data packet, the transmission protocol and the target application. checking whether there is a data flow corresponding to the identification information of the application and authorized from an external server; inserting authentication information into the data packet based on authentication information included in the transmission protocol and the data flow; and and transmitting the data packet based on the transmission protocol.

A method of operating a gateway according to an embodiment disclosed in this document includes receiving a data packet from a node, confirming whether a data flow corresponding to information included in the data packet and authorized from an external server exists, and the If there is a data flow, it may include checking a transport protocol of the data packet, and configuring to process the data packet based on the transport protocol.

According to the embodiments disclosed in this document, data packet authentication technology can be used as a minimum network access control factor for authorized terminals and applications to access an authorized network in a network environment that does not use tunneling, and data packet authentication technology can be used. A secure network access control method applicable to various transmission protocols without tunneling can be provided by applying a technology for protecting authentication information.

According to the embodiments disclosed in this document, a system for controlling network access blocks data packets transmitted by unauthorized objects through a gateway, thereby preventing DoS attacks and brute force attacks through access to service resources. can

According to the embodiments disclosed in this document, a system for controlling network access overcomes the problems inherent in existing IP communication by implementing a secure network connection lifecycle that includes application network access control, threat blocking, and isolation. and provide a secure network connection.

According to the embodiments disclosed in this document, a system for controlling network access can safely control network access even when tunneling technology for protecting data packets is not used in a wide network range.

According to the embodiments disclosed in this document, according to the problem of tunneling technology, which is the problem of the number and limitation of target networks that can be tunneled by a terminal, and the type of tunneling, data packets may be lost in the process of being transmitted. can solve the problem

In addition, according to the embodiments disclosed in this document, a data flow header optimized for each transmission protocol can be inserted, and the corresponding data flow header includes application and destination network information, data flow identification information for identifying authentication information, and corresponding data Minimal network for authorized terminals and applications to access the authorized network in a general IP network environment in which tunneling cannot be used because it can include encrypted authentication information to confirm that flow identification information is transmitted by an authorized subject Access control technology can be provided.

In addition, according to the embodiments disclosed in this document, when data packet authentication information is transmitted in an environment in which tunneling is not used, applications with malicious purposes (eg, ransomware and malware) may sniff the authentication data through network sniffing. After identifying the packet and confirming destination network information that can be accessed through the corresponding authentication information, the authentication information is inserted and transmitted when data packets are transmitted, thereby solving the problem that unauthorized applications can access the network.

In addition, according to the embodiments disclosed in this document, by providing a technology capable of transmitting only allowed data packets while maintaining compatibility of data packets to which the security technology inherent in the target application is applied without using tunneling, It is possible to provide a safe network access control method that can fundamentally block network access of permitted objects (eg, ransomware, malware, etc.).

In addition to this, various effects identified directly or indirectly through this document may be provided.

1 shows an environment including a plurality of networks.

2 illustrates an architecture within a network environment according to various embodiments.

3 is a functional block diagram illustrating a database stored in a controller according to various embodiments.

4 shows a functional block diagram of a node in accordance with various embodiments.

5 describes an operation of controlling transmission of a data packet according to various embodiments.

6 illustrates an example of a data packet in which authentication information is inserted according to various embodiments.

7 shows a signal flow diagram for controller connection according to various embodiments.

8 shows a signal flow diagram for user authentication according to various embodiments.

9 illustrates a signal flow diagram for network access according to various embodiments.

10 illustrates an operational flow diagram for controlling data packet transmission in accordance with various embodiments.

11 illustrates a signal flow diagram for inserting authentication information according to various embodiments.

12 depicts an operational flow diagram for controlling data packet reception according to various embodiments.

13 illustrates an operational flow diagram for checking authentication information according to various embodiments.

14 illustrates a signal flow diagram for control flow update according to various embodiments.

15 illustrates a signal flow diagram for disconnection according to various embodiments.

16 illustrates a signal flow diagram for termination of application execution according to various embodiments.

17 is a flowchart illustrating a method of operating an access control application installed in a node according to various embodiments.

18 shows a flowchart of a method of operating a gateway according to various embodiments.

Hereinafter, various embodiments of the present invention will be described with reference to the accompanying drawings. However, it should be understood that this is not intended to limit the present invention to the specific embodiments, but to cover various modifications, equivalents, and/or alternatives of the embodiments of the present invention.

In this document, the singular form of a noun corresponding to an item may include one item or a plurality of items, unless the context clearly dictates otherwise. In this document, "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 "A, Each of the phrases such as "at least one of B or C" may include any one of the items listed together in the corresponding one of the phrases, or all possible combinations thereof. Terms such as "first", "second", or "first" or "secondary" may simply be used to distinguish a given component from other corresponding components, and may be used to refer to a given component in another aspect (eg, importance or order) is not limited. A (e.g., first) component is said to be "coupled" or "connected" to another (e.g., second) component, with or without the terms "functionally" or "communicatively." When mentioned, it means that the certain component may be connected to the other component directly (eg by wire), wirelessly, or through a third component.

Each component (eg, module or program) of the components described in this document may include singular or plural entities. According to various embodiments, one or more components or operations among the corresponding components may be omitted, or one or more other components or operations may be added. Alternatively or additionally, a plurality of components (eg modules or programs) may be integrated into a single component. In this case, the integrated component may perform one or more functions of each of the plurality of components identically or similarly to those performed by a corresponding component of the plurality of components prior to the integration. . According to various embodiments, the actions performed by a module, program, or other component are executed sequentially, in parallel, iteratively, or heuristically, or one or more of the actions are executed in a different order, or omitted. or one or more other actions may be added.

The term "module" used in this document may include a unit implemented in hardware, software, or firmware, and may be used interchangeably with terms such as logic, logic block, component, or circuit, for example. A module may be an integrally constructed component or a minimal unit of components or a portion thereof that performs one or more functions. For example, according to one embodiment, the module may be implemented in the form of an application-specific integrated circuit (ASIC).

Various embodiments of this document may be implemented as software (eg, a program or application) including one or more instructions stored in a storage medium (eg, memory) readable by a machine. For example, the processor of the device may call at least one command among one or more commands stored from a storage medium and execute it. This enables the device to be operated to perform at least one function according to the at least one command invoked. The one or more instructions may include code generated by a compiler or code executable by an interpreter. The device-readable storage medium may be provided in the form of a non-transitory storage medium. Here, 'non-temporary' only means that the storage medium is a tangible device and does not contain a signal (e.g. electromagnetic wave), and this term refers to the case where data is stored semi-permanently in the storage medium. It does not discriminate when it is temporarily stored.

Methods according to various embodiments disclosed in this document may be included and provided in a computer program product. Computer program products may be traded between sellers and buyers as commodities. A computer program product is distributed in the form of a device-readable storage medium (eg compact disc read only memory (CD-ROM)), or through an application store or between two user devices (eg smartphones). It can be distributed (e.g., downloaded or uploaded) directly or online. In the case of online distribution, at least part of the computer program product may be temporarily stored or temporarily created in a device-readable storage medium such as a manufacturer's server, an application store server, or a relay server's memory.

1 shows an environment including a plurality of networks.

Referring to FIG. 1 , the first network 10 and the second network 20 may be different networks. For example, the first network 10 may be a public network such as the Internet, and the second network 20 may be a private network such as an intranet or VPN.

The first network 10 may include a source node 101 . In FIG. 1 and embodiments described below, the 'source node' may be various types of devices capable of performing data communication. For example, the source node 101 may be a portable device such as a smartphone or tablet, a computer device such as a desktop or laptop, a multimedia device, a medical device, a camera, a wearable device, or a virtual reality (VR) device. , or home appliances, but is not limited to the aforementioned devices. For example, source node 101 may include a server or gateway capable of transmitting data packets through an application. The source node 101 may also be referred to as 'electronic device' or 'terminal'. Meanwhile, the destination node 102 may include the same or similar device as the above-described source node 101 . For another example, the destination node 102 can be substantially the same as the destination network.

The source node 101 may attempt access to the second network 20 and transmit data to the destination node 102 included in the second network 20 . The source node 101 may transmit data to the destination node 102 via the gateway 103 .

If access to the first network 10 of the starting node 101 is approved, since the starting node 101 can communicate with all servers included in the first network 10, the starting node 101 is malicious. ) can be exposed from program attacks. For example, the origin node 101 may be infected with malicious code 110c, as well as trusted and/or secure applications such as Internet web browser 110a and business application 110b. ) may receive data of an untrusted or unsecured application such as the business application 110d.

The starting node 101 infected by the malicious program may attempt access to the second network 20 and/or data transmission. When the second network 20 is formed based on IP, such as VPN, it may be difficult to individually monitor a plurality of devices included in the second network 20, and application in the OSI layer Security at the layer or transport layer may be vulnerable. In addition, if the source node 101 includes a malicious application after the channel has already been created, the data of the malicious application will be delivered to another electronic device (eg, the destination node 102) within the second network 20. can

Referring to FIG. 2 , a node 201 may be various types of devices capable of performing data communication. For example, the node 201 may be a portable device such as a smartphone or tablet, a computer device such as a desktop or laptop, a multimedia device, a medical device, a camera, a wearable device, a virtual reality (VR) device, Or it may include a home appliance, but is not limited to the aforementioned devices. For example, node 201 may include a server or gateway capable of transmitting data packets through an application. The node 201 may also be referred to as an 'electronic device' or a 'terminal'.

Node 201 may store target application 212 and access control application 211 . The target application 212 may transmit a data packet to the service server 205 through the gateway 203 under the control of the access control application 211 or, conversely, may receive a data packet. As some of the target applications 212 may be trusted and/or secured applications, such as web browsers or business applications, while others may be untrusted or unsecured malicious programs, the network access system according to embodiments may be Through the network access control of the access control application 211 , access to the service server 205 of an unauthorized program (application) may be blocked and the corresponding program may be quarantined. For example, before the target application 212 according to the embodiments communicates with the service server 205 , the access control application 211 may check from the controller 202 whether access is possible. When authentication is complete, the access control application 211 may control data packet transmission of the target application 212 . That is, in order for the target application 212 to access the network, it must go through the access control application 211, and the access control application 211 must be authorized from the controller 202, and the access control application 211 must pass through the controller 202. Authentication-related information may be received from, and the access control application 211 may transmit a data packet of the target application 212 based on the authentication-related information.

The controller 202 may be, for example, a server (or cloud server). The controller 202 can ensure reliable data transmission within a network environment by managing data transmission between the node 201, the gateway 203, and the service server 205. For example, the controller 202 may allow the network access of the authorized node 201 (or the access control application 211) through policy information or blacklist information. In addition, the controller 202 may generate authentication-related information for authenticating data packets based on an authentication policy, and transmit the generated authentication-related information to the access control application 211 or the gateway 203 to transmit data It can prevent packets from being sent without authentication. In one embodiment, the target application 212 may authenticate the data packet based on the authentication information received by the controller 202, and if the data packet is not authenticated, the network connection of the target application 212 is connected to the connection. It can be blocked from the control application 211, the controller 202 or the gateway 203. According to one embodiment, the controller 202 is an access control application (eg, registration, authorization, authentication, renewal, termination) associated with network access of the node 201 or access control application 211. 211) and control data packets can be transmitted and received. A flow through which the control data packet is transmitted (eg, 220) may be referred to as a 'control flow'.

The gateway 203 may be located at a boundary of a network to which the node 201 belongs or a boundary of a network to which the service server 205 belongs. According to one embodiment, the gateway 203 may be connected to the controller 202 based on a cloud. The gateway 203 may forward only authenticated data packets based on the authentication information among the data packets received from the access control application 211 to the service server 205 . A flow in which data packets are transmitted between the access control application 211 and the gateway 203 may be referred to as 'data flow'. Data flows can be created in granular units (eg applications) as well as nodes or IP units. The gateway 203 may block indiscriminate network access in advance by forwarding only data packets for which authentication information has been checked among data packets transmitted from the access control application 211 to the service server 205 .

According to various embodiments, the node 201 may include a connection control application 211 and a network driver (not shown) for managing network access of the target application 212 stored in the node 201 . For example, when an access event for the service server 205 of the target application 212 included in the node 201 occurs, the access control application 211 may determine whether the target application 212 can be accessed. . If the target application 212 is accessible, the access control application 211 may transmit a data packet including authentication information to the gateway 203 . The access control application 211 may control transmission of data packets through a kernel including an operating system and a network driver within the node 201 .

3 is a functional block diagram illustrating a database stored in a controller according to various embodiments. Although FIG. 3 shows only the memory 330, the controller includes a communication circuit for communicating with an external electronic device (eg, the communication circuit 430 of FIG. 4) and a processor for controlling the overall operation of the controller (eg, FIG. Four processors 410) may be further included.

Since the administrator can connect to the controller 202 and set connection-oriented policies to control access between the access control application 211 and the service server 205, network access is more detailed and secure than session management at the service level. can control.

The access policy database 311 may include information about networks and/or services to which the identified networks, nodes, or applications may access. For example, the controller 202, when requesting network access from the access control application 211, identifies a network based on a policy of the access policy database 311 (eg, a network to which the node 201 belongs), a node, A user (eg, a user of the node 201) and/or an application (eg, a target application 212 included in the node 201) may determine whether access to the service server 205 is possible. In , the controller 202 may create a whitelist of target applications 212 accessible to a specific service (eg, IP and port) based on the access policy database 311 .

The authentication policy database 312 determines whether or not the gateway 203 existing between the network boundaries of the service server 205 on a connection path authenticates the transport protocol and the data packet flow between the destination network and When performing authentication, a series of policies related to the authentication method can be set. For example, the authentication policy database 312 may include information for generating authentication information to be inserted or checked to check whether an allowed subject has transmitted a data packet. According to the embodiment, the authentication policy database 312 inserts authentication information for each transport protocol (eg, inserts authentication information into a TCP SYN packet in the case of TCP data packets, inserts authentication information for each data packet in the case of UDP, or inserts authentication information at regular intervals). authentication information insertion at (or interval), maximum number of authentication times for the authentication algorithm, expiration date of authentication information, insertion method or timing), information for encrypting or decrypting authentication information, algorithm information and algorithm for generating and verifying authentication information It may include information for generating authentication information including at least one of a series of included information (eg, Secret Key information when generating HMAC OTP) and whether source IP is authenticated. According to an embodiment, authentication information generated based on the authentication policy database 312 may be transmitted to the node 201 or the gateway 203 . According to the embodiment, the access control application 211 of the node 201 may insert authentication information into a data packet to be transmitted based on the transport protocol, and the gateway 203 may insert the data packet received based on the transport protocol. authentication information can be checked.

The blacklist policy database 313 is a target (e.g., a node ID (eg, node ID ( identifier), an IP address, a media access control (MAC) address, or a user ID) may indicate a blacklist registration policy for blocking access.

The blacklist database 314 may include a list of objects blocked by the blacklist policy database 313 . For example, the controller 202 may isolate the node 201 by rejecting the network access request when identification information of the node 201 requesting network access is included in the blacklist database 314 .

The control flow table 315 is an example of a session table for managing a flow (eg, control flow) of control data packets generated between the node 201 and the controller 202 . When accessing the controller 202 is successful, control flow information may be generated by the controller 202 . The control flow information may include at least one of control flow identification information, an IP address identified during access to and authentication of a controller, a node ID, and a user ID. For example, when access to the service server 205 is requested from the node 201, the controller 202 may search for control flow information through control flow identification information received from the node 201, and the searched control flow Whether the node 201 can access the service server 205 by mapping at least one of the IP address, node ID, or user ID included in the information to the access policy database 311, data flow for data packet transmission It can be judged (determined) whether it is created or not.

According to one embodiment, a control flow may have an expiration time. The node 201 needs to update the expiration time of the control flow, and if the expiration time is not updated for a certain period of time, the control flow (or control flow information) may be removed. In addition, when it is determined that immediate disconnection is necessary according to the security event collected from the node 201 , the controller 202 may remove the control flow according to the connection termination request of the node 201 . When the control flow is removed, the connection of the node 201 may be blocked because the previously generated data flow is also removed.

The data flow table 316 is a table for managing a flow (eg, data flow) in which detailed data packets are transmitted between the node 201 and the gateway 203 and the service server 205 . Data flows can be created in TCP sessions, applications, or more granular units. The data flow table 316 may include an application ID, destination IP address, and/or service port for identifying whether a data packet transmitted from a source is an authorized data packet. The data flow table 316 may be managed based on control flow IDs. In addition, the data flow table 316 may include state information including whether or not the data flow is valid and authorized destination information for determining whether data packets are forwarded based on source IP, destination IP, and port information of the data packet. can According to an embodiment, the data flow table 316 may further include authentication information generated based on the authentication policy database 312 . For example, the authentication information is inserted by a method of inserting authentication information for each transmission protocol (e.g., inserting authentication information into a TCP SYN packet for TCP data packets, inserting authentication information for each data packet in the case of UDP, or authenticating at a certain period (or interval)). Insertion of information, maximum number of authentications for the corresponding authentication algorithm, expiration date of authentication information, insertion method or timing), information for encrypting or decrypting authentication information, algorithm information for generating and verifying authentication information, and a series of information included in the algorithm ( Example: Secret Key information when generating HMAC OTP), and at least one of source IP authentication.

According to an embodiment, the data flow table 316 may be equally stored in the node 201 , the gateway 203 , or the service server 205 .

Referring to FIG. 4 , a node may include a processor 410 , a memory 420 , and a communication circuit 430 . According to one embodiment, the node may further include a display 440 to interface with a user.

The processor 410 may control the overall operation of the node. In various embodiments, the processor 410 may include a single processor core or may include a plurality of processor cores. For example, the processor 410 may include multi-cores such as dual-core, quad-core, and hexa-core. According to embodiments, the processor 410 may further include an internal or external cache memory. According to 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 part of processor 410 is electrically or operatively coupled to other components within the node (e.g., memory 420, communication circuitry 430, or display 440). (coupled with) or connected to. The processor 410 may receive commands from other components of the node, interpret the received commands, and perform calculations or process data according to the interpreted commands. The processor 410 may interpret and process messages, data, commands, or signals received from the memory 420 , the communication circuit 430 , or the display 440 . The processor 410 may generate a new message, data, command, or signal based on the received message, data, command, or signal. Processor 410 may provide processed or generated messages, data, instructions, or signals to memory 420 , communication circuitry 430 , or display 440 .

The processor 410 may process data or signals generated or generated by a program. For example, the processor 410 may request instructions, data, or signals from the memory 420 to execute or control a program. The processor 410 may record (or store) or update instructions, data, or signals in the memory 420 to execute or control a program.

The memory 420 may store commands for controlling nodes, control command codes, 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 volatile memory and non-volatile memory. Volatile memory includes dynamic random access memory (DRAM), static RAM (SRAM), synchronous DRAM (SDRAM), phase-change RAM (PRAM), magnetic RAM (MRAM), resistive RAM (RRAM), and ferroelectric RAM (FeRAM). can include The nonvolatile memory may include read only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), flash memory, and the like.

The memory 420 uses a nonvolatile 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). can include more.

According to one embodiment, the memory 420 may store the target application 212 and the access control application 211 of FIG. 2 . The access control application 211 may perform a function of inserting authentication information into a data packet to be transmitted and a function of creating and updating a control flow with the controller 202 . To this end, the access control application 211 may include one or more security modules.

According to an embodiment, the memory 420 may store some of the information included in the memory of the controller (eg, the memory 330 of FIG. 3 ). For example, the memory 420 may store the data flow table 316 described in FIG. 3 .

The communication circuit 430 establishes a wired or wireless communication connection between the node and an external electronic device (eg, the controller 202, gateway 203 or service server 205 of FIG. 2) and performs communication through the established connection. can support According to one embodiment, the communication circuit 430 may be a wireless communication circuit (eg, cellular communication circuit, short-range wireless communication circuit, or global navigation satellite system (GNSS) communication circuit) or a wired communication circuit (eg, a local area network (LAN)). ) communication circuit, or power line communication circuit), and using a corresponding communication circuit among them, a short-distance communication network such as Bluetooth, WiFi direct, or IrDA (infrared data association) or a cellular network, a long-distance communication such as the Internet, or a computer network It may communicate with an external electronic device through a network. The various types of communication circuits 430 described above may be implemented as a single chip or may be implemented as separate chips.

The display 440 may output content, data, or signals. In various embodiments, the display 440 may display image data processed by the processor 410 . According to embodiments, the display 440 may be configured as an integrated touch screen by being combined with a plurality of touch sensors (not shown) capable of receiving a touch input. When the display 440 is configured as a touch screen, a plurality of touch sensors may be disposed above the display 440 or below the display 440 .

A server (eg, controller) according to an embodiment may include a processor 410 , a memory 420 , and a communication circuit 430 . The processor 410, memory 420, and communication circuit 430 included in the server may be substantially the same as the processor 410, memory 420, and communication circuit 430 described above.

A gateway (gateway 203 of FIG. 2 ) according to an embodiment may include a processor 410 , a memory 420 , and a communication circuit 430 . The processor 410, memory 420, and communication circuit 430 included in the gateway may be substantially the same as the processor 410, memory 420, and communication circuit 430 described above.

Referring to FIG. 5, the access control application 211 detects a request for network access to the service server 205 from the target application 212 included in the node 201, and the node 201 or the access control application 211 ) can determine whether or not the controller 202 is in a connected state. When the node 201 or the access control application 211 is not connected to the controller 202, the access control application 211 may block transmission of data packets in a kernel or network driver including an operating system. there is. Through the access control application 211, the node 201 may block access of malicious applications in advance in the application layer of the OSI layer.

In one embodiment, when the access control application 211 is not connected to the controller 202 or when the data packet to be transmitted is not authenticated at the gateway, the data packet transmitted from the access control application 211 is the gateway ( 203) and the access control application 211 can only request access to the controller 202.

In one embodiment, unauthorized data packets may be sent from node 201 if access control application 211 is not installed on node 201 or if a malicious application bypasses control of access control application 211. . In this case, since the gateway 203 present at the boundary of the network blocks unauthorized data packets and data packets for which no data flow exists, data packets transmitted from the node 201 (eg, data packets for creating a TCP session) ) may not reach the service server 205. In other words, node 201 can be isolated from service server 205 .

When transmitting the UDP-based data packet 610, the access control application 211 of the node 201 can manage its own authentication time point for UDP because UDP does not have the concept of creating a session like TCP. In addition, since the target application 212 must create a TCP session with the service server 205 before transmitting the actual data packet when transmitting the TCP-based data packet, the access control application 211 performs a 3-Way Handshake for TCP session creation. In the process, authentication information for the data packet can be managed by inserting authentication information into the TCP SYN data packet for TCP session creation.

According to an embodiment, the UDP-based data packet 610 may include an IP header and a payload. For example, the access control application 211 can insert a data flow header into the payload of the UDP-based data packet 610.

Depending on the embodiment, the access control application 211 may configure a UDP-based data packet into which a data flow header is inserted based on authentication information included in the data flow. For example, when transmitting UDP-based data packets, the access control application 211 may transmit the data packets by inserting a data flow header into only the first data packet of a continuously transmitted UDP data packet flow. In this case, subsequent data packets can be transmitted without data flow header insertion. For another example, if strong data packet authentication is required, the access control application 211 may insert a data flow header into the payload of every UDP data packet.

According to an embodiment, the TCP SYN data packet 620 may include an IP header, a TCP header, and a payload. For example, the connection control application 211 can insert a data flow header into the payload of the TCP SYN data packet 620.

According to the embodiment, the access control application 211 inserts a data flow header into the TCP SYN packet, and the gateway 203 authenticates the data flow header inserted into the TCP SYN packet, and a TCP session is established only for the authenticated target. can lose For example, since the TCP session is not established if not authenticated, the access control application 211 can provide a more efficient TCP-based data packet control method than the method of inserting data flow header information whenever every data packet is transmitted in TCP. can

According to the embodiment, whether the data flow header is a data packet that can be forwarded by the gateway 203 based on the data flow received from the controller 202 in the data packet flow between the target application 212 and the service server 205 It may be information for confirming.

According to an embodiment, the data flow header may be information combining data flow identification information and encrypted authentication information. For example, the authentication information may include information about authentication generated based on the authentication policy of the controller 202 . Depending on the embodiment, authentication information may include an encrypted OTP. According to another embodiment, authentication information may include plain OTP.

According to the embodiment, since a data packet in an IP network has no identifying information other than 5 tuple information, the gateway 203 determines whether or not the terminal to which the IP is assigned has been substantially authenticated and the target for which the application, which is the actual communication subject, is allowed. It is not known whether it was sent by Therefore, in order to confirm that the data packet is transmitted from the authenticated target, the gateway 203 receives the data flow from the controller 202, and the data flow information, destination IP, port information, and authentication information included in the data flow Based on this, data packet authentication and transmission control can be performed.

According to the embodiment, the encrypted authentication information included in the data flow header includes data flow identification information and can be used for the purpose of verifying whether the subject who transmitted the data packet actually transmitted the data packet. For example, the encrypted authentication information may be encrypted and decrypted from an authenticated object through encryption and decryption keys based on authentication information included in the data flow received from the controller 202 .

According to the embodiment, the decrypted authentication information is not information that is fixed at every data packet authentication time, such as data flow identification information, but is changed at every authentication time. OTP (One-Time Password) and random generation type information. there is.

According to the embodiment, the gateway 203 may identify a data flow header in the received data packet, check the data flow information with the data flow identification information, and decrypt the data flow authentication information with a decryption key included in the data flow. . In addition, the gateway 2030 can confirm that the corresponding data packet has been transmitted from an allowed destination by the OTP verification algorithm, and thus can safely control the flow of data packets between the target application 212 and the service server 205 without tunneling. there is.

Since the node 201 needs to be authorized by the controller 202 to access or receive the network, the access control application 211 of the node 201 requests the controller 202 to create a control flow, thereby 201) can try to connect to the controller.

Referring to FIG. 7 , node 201 may detect a controller connection event. For example, when the connection control application 211 is installed and executed within the node 201, the node 201 may detect that a connection to the controller 202 is requested.

At operation 705 , node 201 may request controller connection from controller 202 . For example, the access control application 211 may transmit identification information of the access control application 211 to the controller 202 . Additionally, the access control application 211 may include identification information of the node 201 (eg, terminal ID, IP address, MAC address), type, location, environment, identification information of the network to which the node 201 belongs, and/or network Arbitrary identification information generated by the system itself may be further transmitted.

In operation 710, the controller 202 may identify whether or not the controller connection request (eg, the access control application 211 or the node 201) is accessible. According to one embodiment, the controller 202 determines whether information received from the node 201 is included in the access policy database 311, the node 201, the network to which the node 201 belongs, and/or the connection. Based on at least one of whether the identification information of the control application 211 is included in the blacklist database 314 , it is possible to check whether the controller connection requesting object is accessible.

If the connection is possible, at operation 715 the controller 202 may create a control flow between the node 201 (or the connection control application 211 ) and the controller 202 . In this case, the controller 202 generates control flow identification information in the form of random numbers, and converts identification information of at least one of the node 201, the network to which the node 201 belongs, or the access control application 211 into a control flow table ( 315) can be stored. Information stored in the control flow table 315 may be used for user authentication of the node 201 , information update of the node 201 , policy check for network access of the node 201 , and/or validation.

In operation 720, the controller 202 connects from the access policy database 311 and the authentication policy database 312 corresponding to the identified information (eg, the node 201 and source network information to which the node 201 belongs). Whitelist information of possible applications can be created. In one embodiment, the controller 202 may send the application white list to the connection control application 211 at operation 725 .

In operation 725 , the controller 202 may transmit control flow identification information to the node 201 in response to the controller connection request. Depending on the embodiment, if the object requesting controller access is unavailable or is included in the blacklist, the controller 202 may transmit access unavailability information in operation 725 without generating a control flow. In one embodiment, the controller 202 may transmit the application white list generated through the execution of operation 720 to the connection control application 211 .

At operation 730, the access control application 211 may perform a check on the application. For example, the access control application 211 can perform a check for applications based on the white list of accessible applications received from the controller 202 . The access control application 211 may check whether the application exists (installed) in the node 201 based on the accessible application information, and in the case of the existing application, integrity and stability are checked according to the validation policy ( Above the application, tampering inspection, code signing inspection, fingerprint inspection) can be performed.

At operation 735 , the access control application 211 may send the application check result to the controller 202 . For example, the access control application 211 may transmit information about existing applications and results of validation to the controller 202 .

In operation 740, the controller 202 may check whether the application is valid based on the received application information. If it is a valid application, the controller 202 selects the gateway 203 where the node 201 is located in the access policy database 311 and the authentication policy database 312 to allow access of the node 201 connected to the network. You can check. In addition, the controller 202 may generate a data flow based on source IP, destination IP, and port information so that the node 201 can transmit data packets without a network access request procedure. According to the embodiment, the data flow is a method of inserting authentication information for each transmission protocol (e.g., inserting authentication information into a TCP SYN packet in the case of TCP data packets, inserting authentication information into each data packet in the case of UDP, or authenticating at a certain period (or interval)) Insertion of information, maximum number of authentications for the corresponding authentication algorithm, expiration date of authentication information, insertion method or timing), information for encrypting or decrypting authentication information, algorithm information for generating and verifying authentication information, and a series of information included in the algorithm ( Example: Secret Key information when generating HMAC OTP) and authentication information including at least one of source IP authentication. According to an embodiment, authentication information included in a data flow may also be referred to as authentication-related information.

The controller 202 may transmit the generated data flow to the gateway 203 and the access control application 211 (operations 745 and 750).

In operation 755, the access control application 211 may process the resulting value according to the received response. For example, the connection control application 211 may store the received control flow identification information and display a user interface screen indicating completion of the controller connection to the user. When the controller connection is completed, the request for network connection of the node 201 to the destination network may be controlled by the controller 202 .

According to another embodiment, controller 202 may determine that node 201 is unreachable. For example, if identification information of the node 201 and/or a network to which the node 201 belongs is included in a blacklist database, the controller 202 may determine that the node 201 is inaccessible. In this case, the controller 202 may transmit a response indicating that access to the controller is impossible in operation 725 without generating a control flow in operation 715 . Also, in this case, operations 730 to 750 may not be performed. Depending on the embodiment, if a controller connection needs to be retried, the connection control application 211 may perform operation 705 again.

In addition, the access control application 211 updates the data flow of the node 201 when the data flow received from the controller 202 exists, and transmits the data packet based on the data flow allowed in advance when accessing the network. data flow can be managed. Afterwards, when a data packet transmission request is detected, the access control application 211 may process the data packet to be transmitted based on authentication information included in the received data flow.

According to an embodiment, when it is determined that the application does not need to be inspected, operations 730 to 750 may not be performed.

In order for the node 201 to be granted detailed access rights to the destination network, the access control application 211 of the node 201 may authenticate the user of the node 201 from the controller 202 .

Referring to FIG. 8 , node 201 may receive an input for user authentication. An input for user authentication may be, for example, a user input for inputting a user ID and password. For another example, the input for user authentication may be a user input (eg, biometric information) for stronger authentication. In this case, the access control application 211 of the node 201 may request user authentication from the controller 202 in operation 805 . If the control flow between the node 201 and the controller 202 has already been created, the access control application 211 may transmit input information for user authentication together with control flow identification information.

At operation 810 , controller 202 may authenticate the user based on the information received from node 201 . For example, the controller 202 may use the user ID, password, and/or enhanced authentication information included in the received information and a database included in the memory of the controller 202 (e.g., the access policy database of FIG. 3). 311 or the blacklist database 314), it is possible to determine whether the user can access according to the access policy and whether the user is included in the blacklist.

If the user is authenticated, in operation 815, the controller 202 may add user identification information (eg, user ID) to identification information of the control flow. The added user identification information can be used for the authenticated user's controller access or network access.

The controller 202 may generate accessible application information based on the access policy database 311 or the authentication policy database 312 in operation 820 . For example, the accessible application information may be an application whitelist generated based on an access policy.

In operation 825, the controller 202 may transmit information indicating that the user is authenticated to the node 201 in response to the user authentication request. In addition, the controller 202 may transmit accessible application information to the access control application 211 .

At operation 830, the access control application 211 may perform a check on the application. For example, the access control application 211 can perform a check for applications based on the white list of accessible applications received from the controller 202 . The access control application 211 may check whether the application exists (installed) in the node 201 based on the accessible application information, and in the case of the existing application, integrity and stability are checked according to the validation policy ( Above the application, tampering inspection, code signing inspection, fingerprint inspection) can be performed.

At operation 835 , the access control application 211 may transmit the application check result to the controller 202 . For example, the access control application 211 may transmit information about existing applications and results of validation to the controller 202 .

In operation 840, the controller 202 may check whether the application is valid based on the received application information. If it is a valid application, the controller 202 selects the gateway 203 where the node 201 is located in the access policy database 311 and the authentication policy database 312 to allow access of the node 201 connected to the network. You can check. In addition, the controller 202 may generate a data flow based on source IP, destination IP, and port information so that the node 201 can transmit data packets without a network access request procedure. According to the embodiment, the data flow is a method of inserting authentication information for each transmission protocol (e.g., inserting authentication information into a TCP SYN packet in the case of TCP data packets, inserting authentication information into each data packet in the case of UDP, or authenticating at a certain period (or interval)) Insertion of information, maximum number of authentications for the corresponding authentication algorithm, expiration date of authentication information, insertion method or timing), information for encrypting or decrypting authentication information, algorithm information for generating and verifying authentication information, and a series of information included in the algorithm ( Example: Secret Key information when generating HMAC OTP) and authentication information including at least one of source IP authentication. According to an embodiment, authentication information included in a data flow may also be referred to as authentication-related information.

The controller 202 may transmit the generated data flow to the gateway 203 and the access control application 211 (operations 845 and 850).

In operation 855, the access control application 211 may process the resulting value according to the received response. For example, the access control application 211 may store the received control flow identification information and display a user interface screen indicating completion of user authentication to the user. When user authentication is complete, the request for network access of the node 201 to the destination network may be controlled by the controller 202 .

According to another embodiment, controller 202 may determine that user authentication of node 201 is not possible. For example, if identification information of the node 201 and/or the network to which the node 201 belongs is included in the blacklist database, the controller 202 may determine that the node 201 is inaccessible and user authentication is not possible. . In this case, the controller 202 may not reflect user identification information in operation 815 and may transmit a response indicating that access to the controller is impossible in operation 825 . Also, in this case, operations 830 to 850 may not be performed.

In addition, the access control application 211 updates the data flow of the node 201 when the data flow received from the controller 202 exists, and transmits the data packet based on the data flow allowed in advance when accessing the network. data flow can be managed.

According to an embodiment, operations 830 to 850 may not be performed when the application test is not required.

After node 201 is authorized by controller 202, node 201 controls the network access of other applications stored in node 201 through node 201's access control application 211 to provide trusted data. delivery can be guaranteed.

At operation 905 , connection control application 211 may detect a network connection event of another application stored in node 201 (eg, target application 212 of FIG. 2 ).

In operation 910, the access control application 211 may check the existence of a data flow corresponding to identification information of the application requesting network access, destination network identification information, and port information. Depending on the embodiment, if a data flow exists but is not valid, the access control application 211 may drop the data packet. According to another embodiment, if a data flow exists, the access control application 211 may transmit a data packet based on the data flow. According to the embodiment, the access control application 211 of the node 201 may perform a network access request in operation 915 without performing operation 910 .

When the data flow needs to be updated, such as when the data flow does not exist or when the authentication time expires and renewal is required, in operation 915, the access control application 211 may request the controller 202 to access the network. For example, the network access request may include control flow identification information, destination network identification information, and port information. According to embodiments, the network access request may further include a data packet transmission protocol.

In operation 920, the controller 202 determines the access requested identification information (eg, destination network identification information) in the access policy corresponding to the identified information (eg, node, user, source network identification information) based on the control flow identification information. and port information) and whether the destination network is accessible can be checked. According to an embodiment, the controller 202 may check whether the target application is accessible to the gateway 203 . According to an embodiment, the controller 202 may check whether the transport protocol is included in the access policy. Depending on the embodiment, the controller 202 may transmit a connection failure result to the connection control application 211 of the node 201 when network access is impossible (operation 935).

If it is possible to connect, in operation 925, the controller 202 may check whether data packet authentication between the node 201 and the gateway 203 is required and an authentication method based on the authentication policy.

The controller 202 may check whether a valid data flow corresponding to the identification information and port information of the destination network exists in the data flow table. According to the embodiment, if a valid data flow exists in the data flow table, the controller 202 may transmit the corresponding data flow to the gateway 203 and the access control application (operations 930 and 935). According to another embodiment, when a valid data flow does not exist, the controller 202 may create a data flow based on a transport protocol, source IP, destination IP, port information, and authentication policy. In this case, the controller 202 may transmit the generated data flow to the gateway 203 and the access control application (operations 930 and 935). According to the embodiment, the data flow inserts authentication information for each transport protocol (e.g., inserts authentication information into TCP SYN packets in the case of TCP data packets, inserts authentication information into each data packet in the case of UDP, or at regular intervals (or intervals)). Insertion of authentication information, maximum number of authentications for the corresponding authentication algorithm, expiration date of authentication information, insertion method or timing), information for encrypting or decrypting authentication information, algorithm information for generating and verifying authentication information, and a series of information included in the algorithm (Example: Secret Key information when generating HMAC OTP), and authentication information including at least one of source IP authentication. According to an embodiment, authentication information included in a data flow may also be referred to as authentication-related information. According to another embodiment, if network connectivity is unavailable or if authentication between node 201 and gateway 203 is not possible, controller 202 may, in operation 935, send a network connectivity unavailable result to the access control application. .

At operation 940 , the connection control application 211 of the node 201 may process the resulting value of the response received from the controller 202 . For example, when the connection control application 211 receives a network connection failure result from the controller 202, it may drop a data packet to be transmitted by the target application. For another example, when a data flow is received from the controller 202, the access control application 211 may transmit a data packet based on the received data flow. According to an embodiment, when the access control application 211 transmits a data packet based on the received data flow, the data packet is authenticated based on authentication information included in the data flow through the operations shown in FIG. 10 . You can insert information (or data flow headers).

In one embodiment, after performing operation 910, the access control application 211 may perform validation on the access application according to the validation policy. For example, the access control application 211 may further perform an integrity and stability test of the access application (forgery or tampering test, code signing test, fingerprint test, etc.). The access control application 211 may perform operation 915 when the validation result is successful.

10 shows a signal flow diagram for controlling data packet transmission according to various embodiments. According to an embodiment, the operations shown in FIG. 10 may be performed through the access control application 211 of FIG. 2 .

The access control application 211 of the node 201 transmits a trusted data packet by controlling the transmission of the data packet based on whether or not to insert authentication information into the corresponding data packet and the transmission protocol when transmission of the data packet is detected. can provide.

Referring to FIG. 10 , in operation 1005, the connection control application 211 may detect a data packet transmission event. For example, the access control application 211 sends a data packet to a target application of the node 201 (eg, the target application 212 of FIG. 2) after network access is allowed through the operations shown in FIG. movement can be sensed.

In operation 1010, the access control application 211 may identify a transmission protocol of the data packet, a target application transmitting the data packet, and information included in the data packet (eg, source identification information, destination identification information, port information, etc.) there is. For example, the access control application 211 may check whether a data flow corresponding to the identified information exists, and may perform operation 1015 when the data flow exists. For another example, if the data flow does not exist or the data flow is invalid, the access control application 211 may drop the data packet.

In operation 1015, the connection control application 211 may ascertain the type of data packet. For example, the access control application 211 can determine whether the data packet to be transmitted is a TCP session creation data packet, a TCP session end data packet, a TCP session-based data transfer data packet, or a UDP-based data packet. According to the embodiment, when the data packet to be transmitted is a TCP session creation data packet, the access control application 211 may perform operation 1020. According to the embodiment, when the data packet to be transmitted is a TCP session termination data packet, the connection control application 211 may perform operation 1035. According to the embodiment, when the data packet to be transmitted is a TCP session-based data transmission data packet, the access control application 211 may perform operation 1045. According to the embodiment, when the data packet to be transmitted is a UDP-based data packet, the access control application 211 may perform operation 1055.

If the data packet is a TCP session creation data packet, in operation 1020, the connection control application 211 may perform a TCP data packet authentication information insertion procedure. For example, the access control application 211 may perform a TCP data packet authentication information insertion procedure through operations shown in FIG. 11 .

The connection control application 211 may transmit a TCP session creation data packet in operation 1025 . For example, the TCP session creation data packet may be a data packet in which authentication information is inserted. For another example, the TCP session creation data packet may be a data packet in which a data flow header is inserted into a payload.

In operation 1030, the access control application 211 may receive and process the TCP session creation completion data packet. For example, when the connection control application 211 receives the TCP session creation completion data packet, it may set the data flow to the TCP session creation completion state, and send information indicating that the TCP session creation has been completed to the service server (eg, FIG. 2 service server 205) or a controller (controller 202 in FIG. 2). According to the embodiment, when TCP session creation is complete, the connection control application 211 may transmit a TCP session-based data packet based on the data flow set to the TCP session creation complete state.

If the data packet is a TCP session end data packet, at operation 1035, the connection control application 211 may update the data flow. For example, the access control application 211 may set the data flow to a TCP session end state. In this case, the access control application 211 can no longer transmit TCP-based data packets thereafter. According to an embodiment, the access control application 211 may have to perform the TCP session creation procedure again in order to transmit the TCP-based data packet thereafter. In this case, the access control application 211 may transmit a TCP session end data packet to the server where the TCP session is created (operation 1040).

If the data packet is a TCP session-based data transfer data packet In operation 1045, the connection control application 211 may check the TCP session creation state if the data packet is a TCP session-based data transfer data packet. For example, the access control application 211 may check the TCP session creation state in the data flow, and transmit a TCP data packet when the TCP session is in the created state (operation 1040). For another example, the access control application 211 may check the TCP session creation state in the data flow, and drop the data packet when the TCP session is not created (operation 1050).

If the data packet is a UDP-based data transmission data packet, in operation 1055, the access control application 211 may perform a UDP data packet authentication information insertion procedure. For example, the access control application 211 may perform a UDP data packet authentication information insertion procedure through the operations shown in FIG. 11 .

At operation 1060, the connection control application 211 may send a UDP data packet.

Referring to FIG. 11 , in operation 1105, the access control application 211 may detect a data packet authentication information insertion event. For example, the access control application 211 may detect a data packet authentication information insertion event through operation 1020 or operation 1055 shown in FIG. 10 .

In operation 1110, the access control application 211 may check whether authentication information needs to be inserted. For example, the access control application 211 may check authentication-related information included in a data flow corresponding to a data packet to be transmitted, and determine whether authentication information needs to be inserted based on the authentication-related information. According to embodiments, when authentication information insertion is not required, the access control application 211 may transmit a data packet in operation 1150 without performing operations 1115 to 1145 . According to another embodiment, if authentication information needs to be inserted, the access control application 211 may perform operation 1115.

At operation 1115, the access control application 211 may check the authentication information usage count and due date. For example, the access control application 211 may check the number of uses of the authentication information and the expiration date based on authentication information or authentication information included in the data flow. Depending on the embodiment, if the authentication information can be used regardless of the number of times and the period of use of the authentication information, if there is a remaining number of uses of the authentication information, or if the expiration date of the authentication information remains, the access control application 211 performs operations 1120 to 1120. Operation 1140 may be performed without performing operation 1135 . According to another embodiment, the access control application may perform operation 1120 when the number of times and the period of use of the authentication information are used and there is no remaining number of times of use of the authentication information or the period of use of the authentication information has elapsed.

In operation 1120, the access control application 211 may request the controller 202 to update authentication information. For example, the authentication information renewal request may include data flow identification information.

At operation 1125, the controller 202 may check the authentication policy and update the data flow. For example, the controller 202 may check a data flow corresponding to the received data flow identification information, and update the data flow based on an authentication policy corresponding to the destination IP, port, and transport protocol of the data flow. . Depending on the embodiment, the controller 202 inserts authentication information for each transport protocol included in the authentication policy (e.g., inserts authentication information into a TCP SYN packet in case of TCP data packets, inserts authentication information into each data packet in case of UDP, or Authentication information insertion at regular intervals (or intervals), maximum number of authentication times for the corresponding authentication algorithm, expiration date of authentication information, insertion method or timing), information for encrypting or decrypting authentication information, algorithm information for generating and verifying authentication information, and The data flow may be updated based on authentication information including at least one of a series of information included in the algorithm (eg, Secret Key information when generating the HMAC OTP) and whether or not the source IP has been authenticated.

When updating of the data flow is completed, the controller 202 may transmit the updated data flow to the gateway 203 and the access control application 211 (operations 1130 and 1135). Depending on the embodiment, when the data flow corresponding to the received data flow identification information does not exist, when the data flow needs to be removed based on the authentication policy, or when updating of the data flow fails, the controller 202 controls access A failure result of authentication information update may be transmitted to the application 211 (operation 1135).

At operation 1140, access control application 211 may generate authentication information. For example, the access control application 211 may generate authentication information based on authentication information included in an updated data flow or an existing data flow. Depending on the embodiment, the access control application 211 may generate authentication information by using an authentication information generation algorithm and additional information in authentication information included in the data flow. Depending on the embodiment, the access control application 211 may encrypt authentication information based on an encryption algorithm and an encryption key included in authentication information.

At operation 1145, connection control application 211 may insert a data flow header into the data packet. For example, the access control application 211 may insert a data flow header in which data flow identification information and encrypted authentication information are combined into a data packet based on a transport protocol. Depending on the embodiment, if the transport protocol is TCP, the access control application 211 may insert a data flow header into the payload of the TCP SYN data packet. Depending on the embodiment, if the transport protocol is UDP, the access control application 211 may insert a data flow header into the payload of the UDP data packet.

In one embodiment, in the case of UDP data packets, the access control application 211 may insert a data flow header into every UDP data packet, insert a data flow header on a certain data packet basis or time basis, or determine the flow of data packets. It is possible to determine whether or not to insert a data flow header at the point at which this starts. That is, the access control application 211 may insert a data flow header into the UDP data packet according to the determined data flow header insertion method.

In operation 1150, the access control application 211 may transmit the data packet in which the data flow header is inserted. Depending on the embodiment, the access control application 211 may transmit the data packet without inserting the data flow header in the case of a data packet that does not require insertion of the data flow header.

12 depicts an operational flow diagram for controlling data packet reception according to various embodiments. Depending on the embodiment, the operations shown in FIG. 12 may be performed through the gateway 203 of FIG. 2 .

Referring to FIG. 12 , in operation 1205, the gateway 203 may detect a data packet reception event. For example, gateway 203 may receive a data packet from a node's connection control application.

In operation 1210, the gateway 203 may check whether a data flow corresponding to the data packet exists. For example, the gateway 203 may check whether a data flow exists based on the transport protocol, destination IP, and port included in the 5 Tuples information of the data packet. Depending on the embodiment, the gateway 203 may drop the data packet when the data flow does not exist.

If there is a data flow, in operation 1215, the gateway 203 may check the type of data packet. For example, the gateway 203 can determine whether the data packet is a TCP session creation data packet, a TCP session based data packet but not a TCP session creation data packet, or a UDP based data transfer data packet. According to an embodiment, when the data packet is a TCP session creation data packet, the gateway 203 may perform operation 1220. According to embodiments, when the data packet is a TCP session-based data packet but not a TCP session creation data packet, the gateway 203 may perform operation 1225. According to an embodiment, when the data packet is a UDP-based data transmission data packet, the gateway 203 may perform operation 1235.

If the data packet is a TCP session creation data packet, in operation 1220, the gateway 203 may perform a TCP data packet authentication information check. For example, the gateway 203 may perform TCP data packet authentication information check through the operations shown in FIG. 13 . Depending on the embodiment, if the authentication information check fails, the gateway 203 may drop the TCP data packet. According to another embodiment, if the authentication information check succeeds, the gateway 203 may forward the TCP data packet.

If the data packet is a TCP session-based data packet but not a TCP session creation data packet, in operation 1225, gateway 203 may forward the data packet.

If the data packet is a UDP-based data transmission data packet, in operation 1235, the gateway 203 may perform a UDP data packet authentication information check. For example, the gateway 203 may perform UDP data packet authentication information check through the operations shown in FIG. 13 . Depending on the embodiment, if the authentication information check fails, the gateway 203 may drop the UDP data packet. According to another embodiment, if the authentication information check succeeds, the gateway 203 may forward the UDP data packet.

13 illustrates an operational flow diagram for checking authentication information according to various embodiments. The operations shown in FIG. 13 may be performed through the gateway 203 of FIG. 2 .

Referring to FIG. 13 , in operation 1305, the gateway 203 may detect a data packet authentication information checking event. For example, the gateway 203 may detect a data packet authentication information check event through operation 1220 or operation 1235 shown in FIG. 12 .

In operation 1310, the gateway 203 may check whether authentication information needs to be checked. For example, the gateway 203 can check whether authentication information of a corresponding data packet needs to be checked in authentication information included in a data flow corresponding to the data packet. Depending on the embodiment, if checking the authentication information of the corresponding data packet is not required, the gateway 203 may forward the data packet (operation 1315).

When it is necessary to check the authentication information of the data packet, in operation 1320, the gateway 203 may check whether a data flow header is inserted into the data packet. Depending on the embodiment, when it is impossible to identify the data flow header, the gateway 203 may drop the data packet (operation 1350).

If the identification of the data packet header is possible, in operation 1325 the gateway 203 may examine the data flow. For example, the gateway 203 may check whether the data flow corresponding to the data packet and the data flow identified based on the data flow header are the same. According to an embodiment, when the data flow corresponding to the data packet and the data flow identified based on the data flow header are not the same, the gateway 203 may drop the data packet (operation 1350).

When the data flows are identical to each other, in operation 1330, the gateway 203 may decrypt authentication information. For example, the gateway 203 may decrypt authentication information included in the data flow header based on authentication information included in the data flow in order to check the authentication information included in the data flow header. Depending on the embodiment, the gateway 203 may decrypt authentication information through a decryption algorithm and a decryption key included in authentication information. Depending on the embodiment, when authentication information decryption fails, the gateway 203 may drop the data packet (operation 1350).

If the authentication information decryption succeeds, in operation 1335, the gateway 203 may check the authentication information. For example, the gateway 203 may check decrypted authentication information based on authentication information included in the data flow. According to an embodiment, the gateway 203 may check whether the decrypted authentication information is valid based on an authentication information check algorithm or related information included in authentication information. According to an embodiment, if the authentication information is not valid, the gateway 203 may drop the data packet (operation 1350).

If the authentication information is valid, in operation 1340, the gateway 203 may remove the data flow header. For example, the gateway 203 may remove a data flow header included in the received data packet. If the data flow header is removed from the data packet, gateway 203 may forward the data packet (act 1345).

Referring to FIG. 14 , in operation 1405, the access control application 211 may detect a control flow update event.

In operation 1410, the access control application 211 may request a control flow update from the controller 202 based on the control flow identification information.

In operation 1415, the controller 202 may check whether a control flow exists in a control flow table (eg, the control flow table 315 of FIG. 3) based on the received control flow identification information. Depending on the embodiment, when the control flow does not exist (eg, when the connection is disconnected by another security system, when the connection is disconnected by its own risk detection, etc.), the controller 202 determines that the connection of the node 201 is valid. Therefore, a connection failure result may be transmitted to the connection control application 211 (operation 1420).

The controller 202 may update the update time when a control flow exists in the control flow table (eg, the control flow table 315 of FIG. 3 ). In this case, the controller 202 may transmit identification information of the updated control flow to the connection control application 211 (operation 1420).

In one embodiment, the controller 202 is required to perform re-authentication among data flows subordinate to the identified control flow, or if there is a data flow to which access is no longer possible, the controller 202 transmits information about the corresponding data flow to an access control application ( 211) (operation 1420).

At operation 1425 , the connection control application 211 of the node 201 may process the resulting value of the response received from the controller 202 . For example, the access control application 211 may block all network accesses of applications when the control flow update result is impossible. For another example, the access control application 211 may update the data flow when the control flow update result is normal and updated data flow information exists.

Referring to FIG. 15 , in operation 1505 node 201 terminates node 201, terminates access control application 211, terminates target application, no longer uses the network connection, and information identified from the interworking system. At least one of connection termination requests may be detected based on . In this case, at operation 1510, node 201 or access control application 211 may request controller 202 to remove the control flow.

In operation 1515, the controller 202 may remove the identified control flow based on the received control flow identification information.

In operation 1520, the controller 202 may remove all data flows dependent on the removed control flow. Thus, node 201 can no longer connect to the destination network based on the removed data flow.

In operation 1525, the controller 202 may request the gateway 203 to remove all data flows dependent on the removed control flow. The gateway 203 may remove the data flow, and thus data packets corresponding to source network, destination network, and port information included in the removed data flow may no longer be transmitted.

Referring to FIG. 16 , in operation 1605, the access control application 211 of the node 201 may check in real time whether or not the running application is terminated, and may detect an application execution termination event.

Depending on the embodiment, the access control application 211 may check whether a data flow corresponding to terminated application identification information and PID (Process ID and Child Process ID Tree) information exists.

At operation 1610 , the connection control application 211 may perform a data flow removal request to the controller 202 . For example, the access control application 211 may transmit identification information of a terminated application or identification information of a data flow corresponding to the terminated application to the controller 202 and may perform a data flow removal request.

In operation 1615, the controller 202 may delete the data flow requested to be removed. In addition, the controller 202 may perform a removal request for the removed data flow to the gateway 203 (operation 1620). The gateway 203 may remove the data flow, and thus data packets corresponding to source network, destination network, and port information included in the removed data flow may no longer be transmitted.

17 is a flowchart illustrating a method of operating an access control application installed in a node according to various embodiments. According to an embodiment, the operations shown in FIG. 17 may be performed through the access control application 211 of the node 201 of FIG. 2 .

Referring to FIG. 17 , in operation 1705, the access control application 211 may detect a data packet transmission event of the target application.

At operation 1710, the connection control application 211 may ascertain the transport protocol of the data packet. For example, the access control application 211 can determine whether the transport protocol of the data packet is TCP or UDP.

In operation 1715, the access control application 211 may check whether a data flow corresponding to the transport protocol and identification information of the target application and authorized from the external server exists.

In operation 1720, the access control application 211 may insert authentication information into the data packet based on information about authentication included in the transport protocol and data flow.

At operation 1725, the connection control application 211 may transmit the data packet based on the transport protocol. For example, the access control application 211 may transmit a data packet into which a data flow header is inserted based on a transport protocol.

18 is a flowchart of a method of operating a gateway according to various embodiments. According to an embodiment, the operations shown in FIG. 18 may be performed through the gateway 203 of FIG. 2 .

Referring to FIG. 18 , in operation 1805 the gateway 203 may receive a data packet from the node 201 .

In operation 1810, the gateway 203 may check whether a data flow corresponding to the information included in the data packet and authorized from the external server exists.

In operation 1820, the gateway 203 may check the transmission protocol of the data packet if there is a data flow.

At operation 1825, gateway 203 may process the data packet based on the transport protocol.

The above description is only an illustrative example of the technical idea disclosed in this document, and those skilled in the art to which the embodiments disclosed in this document belong will be within the scope of the essential characteristics of the embodiments disclosed in this document. Many modifications and variations will be possible.

Therefore, the embodiments disclosed in this document are not intended to limit the technical idea disclosed in this document, but to explain, and the scope of the technical idea disclosed in this document is not limited by these embodiments. The scope of protection of technical ideas disclosed in this document should be interpreted according to the scope of the following claims, and all technical ideas within the equivalent scope should be construed as being included in the scope of rights of this document.

Claims

In node,

communication circuit;

a processor in operative connection with the communication circuitry; and

a memory operatively connected to the processor and storing a connection control application and a target application, wherein the memory, when executed by the processor, causes the node to:

Detecting a transmission event of a data packet of the target application through the access control application;

Check the transmission protocol of the data packet;

Checking whether there is a data flow corresponding to the transmission protocol and identification information of the target application and authorized from an external server;

Inserting authentication information into the data packet based on authentication information included in the data flow and the transmission protocol;

A node that stores instructions that cause the data packet to be transmitted based on the transport protocol.
According to claim 1,

The authentication information includes a data flow header in which information obtained by encrypting the authentication information and identification information of the data flow are combined.
According to claim 1,

The authentication-related information is at least one of a method for inserting authentication information for each transmission protocol, a cycle for inserting authentication information, a maximum number of authentication times for an authentication algorithm, information for encrypting/decrypting authentication information, and an algorithm for generating authentication information. Including, node.
The method of claim 1, wherein the instructions are the node,

If the transport protocol confirmed through the access control application is a TCP protocol, inserting the authentication information into a payload of a TCP SYN data packet;

and inserting the authentication information into a payload of a UDP data packet when the transport protocol is a UDP protocol.
The method of claim 1, wherein the instructions are the node,

Through the access control application, if the data packet is a TCP session creation data packet, the authentication information is inserted into the TCP session creation data packet, and the TCP session creation data packet in which the authentication information is inserted is transmitted to a service server, ,

The node configured to set state information of the data flow to a TCP session creation complete state when receiving a TCP session creation complete data packet from the service server.
The method of claim 1, wherein the instructions are the node,

Through the access control application, when the data packet is a TCP session end data packet, setting state information of the data flow to a TCP session end state;

and to transmit the TCP session end data packet.
The method of claim 1, wherein the instructions are the node,

Transmitting the data packet when it is determined through the access control application that the authentication information is unnecessary to be inserted into the data packet based on the authentication information;

Inserting the authentication information into the data packet when it is determined that the authentication information needs to be inserted into the data packet;

Check whether the authentication information needs to be renewed;

When renewal of the authentication information is required, requesting renewal of the authentication information from the external server;

Receiving a data flow in which the authentication information is updated from the external server;

and to insert authentication information into the data packet based on the updated data flow.
The method of claim 1, wherein the instructions are the node,

detecting a network access request event of the target application through the access control application;

Performs a network access request to the external server, the network access request includes the transport protocol, identification information of the target application or identification information of a destination network of the target application,

If connection is possible, a node configured to receive a data flow including the authentication information from the external server.
in the gateway

communication circuit;

Memory; and

a processor in operative connection with the communication circuitry and the memory, the processor comprising:

receive data packets from the node;

Check whether there is a data flow corresponding to the information included in the data packet and authorized from an external server;

If the data flow exists, check the transmission protocol of the data packet;

and processing the data packet based on the transport protocol.
The method of claim 9, wherein the processor,

When the data packet is a TCP session creation data packet, checking authentication information for the TCP session creation data packet;

If the data packet is not a TCP session creation data packet, forward the data packet;

and if the data packet is a UDP-based data packet, check authentication information for the UDP-based data packet.
The method of claim 9, wherein the processor,

Check information about authentication included in the data flow;

Based on the authentication information, it is determined whether authentication information of the data packet needs to be checked;

When checking the authentication information is required, check whether a data flow header is included in the data packet;

Check whether the data flow identified through the data flow header and the data flow are the same;

Drop the data packet when the data flow identified through the data flow header and the data flow are not the same; and

Wherein the gateway configured to perform authentication information check of the data packet based on the data flow header and the authentication information when the data flow identified through the data flow header is the same as the data flow.
The method of claim 11, wherein the processor,

Decrypt authentication information included in the data flow header based on the authentication information;

Check whether the decrypted authentication information is valid based on the authentication information;

Drop the data packet if the authentication information is not decrypted or invalid; and

and if the authentication information is valid, remove the data flow header from the data packet, and forward the data packet from which the data flow header is removed.
in the server,

communication circuit;

a memory for storing a database; and

a processor in operative connection with the communication circuitry and the memory, the processor comprising:

Receive a network access request from an access control application of a node, the network access request including identification information of a target application included in the node, a transport protocol, and identification information of a destination network;

Based on the identification information of the target application, the transmission protocol, and the identification information of the destination network, it is determined whether or not the target application can access the gateway through an access policy of the database;

If accessible, create a data flow including information about authentication based on the authentication policy of the database;

configured to transmit the data flow to the node and the gateway.
According to claim 13,

The authentication information,

A server including at least one of a method for inserting authentication information for each transmission protocol, a cycle for inserting authentication information, a maximum number of authentication times for an authentication algorithm, information for encrypting/decrypting authentication information, and an algorithm for generating authentication information.
In the operating method of the access control application installed in the node,

detecting a transmission event of a data packet of a target application;

checking a transmission protocol of the data packet;

checking whether a data flow corresponding to the transmission protocol and identification information of the target application and applied from an external server exists;

inserting authentication information into the data packet based on authentication information included in the transmission protocol and the data flow; and

transmitting the data packet based on the transmission protocol; Including, method.
In the operation method of the gateway,

receiving a data packet from a node;

confirming whether a data flow corresponding to the information included in the data packet and applied from an external server exists;

checking a transmission protocol of the data packet if the data flow exists; and

configured to process the data packet based on the transport protocol; Including, method.