Electronic apparatus including independently stractured container within a vpc for attack surface management and making method thereof

The implementation of independently structured containers within a VPC with a microservices architecture addresses scalability and resource management issues in ASM, providing efficient and secure resource allocation and compliance.

KR103043055B1Active Publication Date: 2026-11-06AI SPERA INC
View PDF 7 Cites 0 Cited by

Patent Information

Application Number
KR1020240167313
Authority / Receiving Office
KR · KR
Patent Type
Patents
Current Assignee / Owner
Filing Date
2024-11-21
Publication Date
2026-11-06
Estimated Expiration
2044-11-21

AI Technical Summary

Technical Problem

Conventional Attack Surface Management (ASM) solutions struggle with scalability, flexibility, and resource management, especially in large-scale data processing environments, leading to inefficiencies and vulnerabilities due to rigid infrastructure and interconnected configurations.

Method used

An electronic device with independently structured containers within a Virtual Private Cloud (VPC) that utilizes a microservices architecture for dynamic scaling and resource allocation, allowing for flexible and granular resource management through pod pairs and private load balancers.

Benefits of technology

Enables faster and more efficient resource allocation, enhances security by isolating services, and optimizes time and cost through on-demand scaling and independent VPCs for each client, ensuring robust security and compliance.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 112024128428522-PAT00003_ABST
    Figure 112024128428522-PAT00003_ABST
Patent Text Reader

Abstract

An electronic device comprising independently structured containers within a VPC for attack surface management according to the present disclosure comprises: a Virtual Private Cloud (VPC) deployed within a cloud; a container comprising a plurality of worker nodes that are independently deployed within the VPC, separated according to front, backend, and backing functions, and perform tasks corresponding to the separated functions; a memory in which at least one process for performing an attack surface management operation is stored; and at least one processor that performs the operation according to the process; wherein the worker nodes of the container comprise a pair of units called pod pairs, and the at least one processor may be configured such that the pod pairs are dynamically scaled in units of containers according to a microservices architecture (MSA).
Need to check novelty before this filing date? Find Prior Art

Description

Technology Field

[0001] The present disclosure relates to a device and method for managing cyber security risks and attack surfaces, and more specifically, to an electronic device comprising an independently structured container within a VPC for managing attack surfaces and a method for manufacturing the same. Background Technology

[0002] Due to the expansion of cloud computing, the Internet of IoT, and remote work environments, the global security solution industry has recently been providing solutions and services known as Attack Surface Management (ASM).

[0003] The ASM solution is designed to maintain the various security boundaries faced by enterprises. It operated in on-premises and VM environments; while it lacked flexibility, such as resource adjustment based on data throughput, due to its fixed infrastructure, it was not an issue for processing small-scale data.

[0004] However, with the advent of the Fourth Industrial Revolution, as the number of client companies processing large-scale data increases, it has become difficult to manage and respond to attack surfaces using only conventional ASM solutions. This is because time is required to create new VMs and connect them to the network in order to quickly reallocate resources when traffic increases rapidly.

[0005] In addition, the internal configuration of the ASM solution was entirely connected to VMs, so all services could stop in the event of a VM failure, leading to frequent breakdowns and requiring a long time to identify the cause. Furthermore, there was a problem in that it could not respond agilely to the application of new technologies or new security vulnerabilities.

[0006] Conventional patent literature relates to an invention concerning attack surface management itself, which collects attack surface information and performs automated tests based on the collected information; however, there was a problem in that it was still difficult to secure large-scale resource management, flexibility, and scalability for attack surface management with conventional patent literature. Prior art literature

[0007] Republic of Korea Registered Patent Publication B1 (2023.09.15) The problem to be solved

[0008] To solve the problems disclosed in the prior art, the embodiments disclosed in this disclosure aim to provide an electronic device including an independently structured container within a VPC for attack surface management and a method for manufacturing the same, wherein the independent container is structured based on a VPC within a cloud environment to enable scale-in / scale-out for necessary functions.

[0009] The problems that this disclosure aims to solve are not limited to those mentioned above, and other unmentioned problems will be clearly understood by a person skilled in the art from the description below. means of solving the problem

[0010] An electronic device comprising an independently structured container within a VPC for attack surface management according to the present disclosure, for achieving the technical problem described above, comprises: a Virtual Private Cloud (VPC) deployed within a cloud; a container comprising a plurality of worker nodes that are independently deployed within the VPC, separated according to front, backend, and backing functions, and perform tasks corresponding to the separated functions; a memory in which at least one process for performing an attack surface management operation is stored; and at least one processor that performs the operation according to the process; wherein the worker nodes of the container comprise a pair of units called pod pairs, and the at least one processor may be configured such that the pod pairs are dynamically scaled in units of containers according to a microservices architecture (MSA).

[0011] A method for manufacturing an electronic device comprising independently structured containers within a VPC for attack surface management performed by a processor of the device according to the present disclosure for achieving the technical problem described above, the method may include: deploying a Virtual Private Cloud (VPC) within a cloud; deploying containers, each comprising a plurality of worker nodes performing tasks corresponding to the separated functions, independently within the VPC according to front, backend, and backing functions; deploying a pair of unit pod pairs on the worker nodes of the containers; and adjusting the pod pairs so that they are dynamically scaled in container units according to a microservices architecture (MSA).

[0012] In addition to this, a computer program stored on a computer-readable recording medium for implementing the present disclosure may be further provided.

[0013] In addition to this, a computer-readable recording medium for recording a computer program for implementing the present disclosure may be further provided. Effects of the invention

[0014] According to the aforementioned means for solving the problem of the present disclosure, based on a containerized microservices architecture (MSA), it is possible to achieve much faster and more granular resource allocation than a VM-based ASM system, and on-demand resource allocation is possible, thereby providing the effect of optimizing time and cost.

[0015] In addition, according to the aforementioned means for solving the problem of the present disclosure, services are provided based on independent VPCs for each client, thereby providing an advantageous effect for establishing a security environment.

[0016] The effects of the present disclosure are not limited to those mentioned above, and other unmentioned effects will be clearly understood by a person skilled in the art from the description below. Brief explanation of the drawing

[0017] FIG. 1 is a block diagram briefly illustrating the basic configuration of an electronic device including independently structured containers within a VPC for attack surface management according to the present disclosure. FIG. 2 is a conceptual diagram briefly illustrating an environment in which an electronic device including an independently structured container within a VPC for attack surface management according to the present disclosure is used. FIG. 3 is a block diagram briefly illustrating the VPC-specific configuration of an electronic device including independently structured containers within a VPC for attack surface management according to the present disclosure. FIG. 4 is a block diagram showing in detail the internal configuration of an electronic device including an independently structured container within a VPC for attack surface management according to the present disclosure. Specific details for implementing the invention

[0018] Throughout this disclosure, the same reference numerals denote the same components. This disclosure does not describe all elements of the embodiments, and general content in the art to which this disclosure pertains or content that overlaps between embodiments is omitted. The terms 'part, module, component, block' as used in the specification may be implemented in software or hardware, and depending on the embodiments, a plurality of 'parts, modules, components, blocks' may be implemented as a single component, or a single 'part, module, component, block' may include a plurality of components.

[0019] Throughout the specification, when a part is described as being "connected" to another part, this includes not only cases where they are directly connected but also cases where they are indirectly connected, and indirect connections include connections made via a wireless communication network.

[0020] Furthermore, when it is stated that a part "includes" a certain component, this means that, unless specifically stated otherwise, it does not exclude other components but may include additional components.

[0021] Throughout the specification, when it is stated that a component is located "on" another component, this includes not only cases where a component is in contact with another component, but also cases where another component exists between the two components.

[0022] The terms first, second, etc. are used to distinguish one component from another, and the components are not limited by the aforementioned terms.

[0023] Singular expressions include plural expressions unless there is an obvious exception in the context.

[0024] In each step, identification codes are used for convenience of explanation and do not describe the order of the steps; the steps may be performed differently from the specified order unless a specific order is clearly indicated in the context.

[0025] The operating principles and embodiments of the present disclosure will be described below with reference to the attached drawings.

[0026] In this specification, the term "device according to the present disclosure" includes all various devices capable of performing computational processing and providing results to a user. For example, the device according to the present disclosure may include all of a computer, a server device, and a portable terminal, or may be in the form of any one of these.

[0027] Here, the computer may include, for example, a notebook, desktop, laptop, tablet PC, slate PC, etc. equipped with a web browser.

[0028] The above server device is a server that processes information by communicating with an external device, and may include an application server, a computing server, a database server, a file server, a game server, a mail server, a proxy server, and a web server.

[0029] The above portable terminal may include, for example, all types of handheld-based wireless communication devices such as PCS (Personal Communication System), GSM (Global System for Mobile communications), PDC (Personal Digital Cellular), PHS (Personal Handyphone System), PDA (Personal Digital Assistant), IMT (International Mobile Telecommunication)-2000, CDMA (Code Division Multiple Access)-2000, W-CDMA (W-Code Division Multiple Access), WiBro (Wireless Broadband Internet) terminals, smartphones, etc., as well as wearable devices such as watches, rings, bracelets, anklets, necklaces, glasses, contact lenses, or head-mounted devices (HMDs).

[0030] Functions related to artificial intelligence according to the present disclosure are operated through a processor and memory. The processor may be composed of one or more processors. In this case, the one or more processors may be general-purpose processors such as CPUs, APs, and DSPs (Digital Signal Processors), graphics-dedicated processors such as GPUs and VPUs (Vision Processing Units), or artificial intelligence-dedicated processors such as NPUs. The one or more processors control the processing of input data according to predefined operation rules or artificial intelligence models stored in memory. Alternatively, if the one or more processors are artificial intelligence-dedicated processors, the artificial intelligence-dedicated processors may be designed with a hardware structure specialized for processing a specific artificial intelligence model.

[0031] The predefined operating rules or artificial intelligence models are characterized by being created through learning. Here, being created through learning means that a predefined operating rules or artificial intelligence models configured to perform desired characteristics (or objectives) are created by a basic artificial intelligence model being trained using multiple learning data by a learning algorithm. Such learning may be performed on the device itself where the artificial intelligence according to the present disclosure is executed, or it may be performed through a separate server and / or system. Examples of learning algorithms include supervised learning, unsupervised learning, semi-supervised learning, or reinforcement learning, but are not limited to the examples described above.

[0032] FIG. 1 is a block diagram briefly illustrating the basic configuration of an electronic device including independently structured containers within a VPC for attack surface management according to the present disclosure.

[0033] Referring to FIG. 1, an electronic device according to the present disclosure may include an input / output module (11), a communication module (12), a memory (13), and a processor (14). Hereinafter, it is assumed that the electronic device is an electronic device and that the method is implemented through the electronic device.

[0034] The input / output module (11) may be various interfaces or connection ports that receive user input or output information to the user. The input / output module (11) may be divided into an input module and an output module.

[0035] The input module receives user input from the user. The input module is for inputting video information (or signals), audio information (or signals), data, or information input by the user, and may include at least one of at least one camera, at least one microphone, and a user input unit. Voice data or image data collected by the input unit may be analyzed and processed into a user control command.

[0036] User input can take various forms, including key input, touch input, and voice input. Examples of input modules capable of receiving such user input include traditional keypads, keyboards, and mice; as well as touch sensors that detect user touch; microphones that receive voice signals; cameras that recognize gestures through image recognition; proximity sensors consisting of light or infrared sensors that detect user approach; motion sensors that recognize user movements using accelerometers or gyroscopes; and all other diverse forms of input means that detect or receive various types of user input. This is a comprehensive concept.

[0037] Here, the touch sensor can be implemented as a piezoelectric or capacitive touch sensor that detects touch through a touch panel or touch film attached to the display panel, or as an optical touch sensor that detects touch by an optical method. In addition, the input module may be implemented in the form of an input interface (USB port, PS / 2 port, etc.) that connects an external input device to receive user input, instead of a device that detects user input itself.

[0038] The output module can output various types of information and provide it to the user. The output module is a comprehensive concept that includes a display for outputting video, a speaker for outputting sound (and / or an amplifier connected thereto), a haptic device for generating vibration, and various other forms of output means. In addition, the output module may be implemented in the form of a port-type output interface that connects the individual output means described above.

[0039] For example, an output module in the form of a display can display text, still images, and videos. The term "display" refers to a broad concept of an image display device that includes all types of devices capable of performing image output functions, such as Liquid Crystal Displays (LCDs), Light Emitting Diode (LED) displays, Organic Light Emitting Diode (OLED) displays, Flat Panel Displays (FPDs), transparent displays, Curved Displays, flexible displays, 1D displays, holographic displays, projectors, and others. Such a display may also take the form of a touch display integrated with the touch sensor of an input module.

[0040] In other words, the input / output module (11) can receive user input or provide output to the user based on a user interface.

[0041] The communication module (12) can communicate with an external device. Accordingly, the device can transmit and receive information with an external device through the communication module. For example, the device can communicate with an external device using the communication module so that information stored and generated within the electric vehicle charging management system is shared. The communication module (12) may include, for example, at least one of a wired communication module, a wireless communication module, a short-range communication module, and a location information module.

[0042] Here, communication, that is, the transmission and reception of data, can be performed via wired or wireless means. To this end, the communication module may be composed of a wired communication module that connects to the Internet, etc., via a Local Area Network (LAN); a mobile communication module that connects to a mobile communication network via a mobile communication base station to transmit and receive data; a short-range communication module that uses a Wireless Local Area Network (WLAN) family communication method such as Wi-Fi or a Wireless Personal Area Network (WPAN) family communication method such as Bluetooth or Zigbee; a satellite communication module that uses a Global Navigation Satellite System (GNSS) such as GPS; or a combination thereof. The wireless communication technology used for communication may include Narrowband Internet of Things (NB-IoT) for low-power communication. In this case, for example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology and may be implemented according to standards such as LTE Cat (category) NB1 and / or LTE Cat NB2, but is not limited to the names mentioned above. Additionally, or generally, wireless communication technology implemented in wireless devices according to various embodiments may perform communication based on LTE-M technology. In this case, for example, LTE-M technology may be an example of LPWAN technology and may be referred to by various names such as eMTC (enhanced Machine Type Communication).For example, LTE-M technology may be implemented in at least one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-Bandwidth Limited), 5) LTE-MTC, 6) LTE Machine Type Communication, and / or 7) LTE M, and is not limited to the names mentioned above. Additionally or generally, wireless communication technology implemented in wireless devices according to various embodiments may include at least one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN) for low-power communication, and is not limited to the names mentioned above. As an example, ZigBee technology can create personal area networks (PANs) related to small / low-power digital communication based on various standards such as IEEE 802.15.4 and may be referred to by various names.

[0043] The memory (13) can store various types of information. The memory can store data temporarily or semi-permanently. For example, the memory may store an operating system (OS) for operating the first device and / or the second device, data for hosting a website, or data regarding a program or application (e.g., a web application) for generating Braille. In addition, the memory can store modules in the form of computer code as described above.

[0044] Examples of memory (13) may include a hard disk drive (HDD), a solid state drive (SSD), flash memory, ROM (Read-Only Memory), and RAM (Random Access Memory). These memories may be provided as built-in or detachable types.

[0045] The processor (14) controls the overall operation of the electronic device. To this end, the processor (14) performs calculations and processing of various information and can control the operation of the components of the first device and / or the second device.

[0046] The processor (14) may be implemented as a computer or a similar device according to hardware, software, or a combination thereof. Hardware-wise, the processor (14) may be provided in the form of an electronic circuit that processes electrical signals to perform control functions, and software-wise, it may be provided in the form of a program that drives the hardware processor. Meanwhile, unless otherwise specifically mentioned in the following description, the operation of the first device and / or the second device may be interpreted as being performed by the control of the processor (14). That is, the modules may be interpreted as the processor (14) controlling the first device and / or the second device to perform the following operations.

[0047] The processor (14) may be implemented with a memory that stores data for an algorithm or a program that reproduces the algorithm for controlling the operation of components within the device, and at least one sub-processor (not shown) that performs the aforementioned operation using the data stored in the memory. In this case, the memory and the processor may each be implemented as separate chips. Alternatively, the memory and the processor may be implemented as a single chip.

[0048] In addition, the processor (14) can control one or a combination of the components described above in order to implement various embodiments according to the present disclosure, which will be described in the drawings below, on the device.

[0049] FIG. 2 is a conceptual diagram briefly illustrating an environment in which an electronic device including an independently structured container within a VPC for attack surface management according to the present disclosure is used.

[0050] Attack surface management is a security approach that anticipates and prepares for attacks from a hacker's perspective on corporate assets exposed to risks connected to the Internet, such as network equipment, databases, servers, ports, applications, and domains.

[0051] As illustrated in FIG. 2, the attack surface management environment (10) checks all windows and doors connecting the house to the outside of the house to protect the house in which the safe is placed, and finds parts where security is weakened because the locking mechanism is broken or broken.

[0052] You can check the security status of RDP, nginx, OpenSSH, Apache, or MySQL connected to the external network to prevent external intrusion and leakage of corporate data or trade secrets.

[0053] Traditionally, VMs had a rigid structure where the entire configuration was interconnected and internal configurations were not separated by function, making it difficult to apply new security patches or implement new IT technologies at the functional level. Furthermore, it was difficult to quickly identify where resources were depleted when they occurred. Additionally, because all configurations were interconnected, strict access control to the external network for data security was insufficient.

[0054] The electronic device according to the present disclosure can solve this problem by configuring containers for each function to introduce an independent structure when performing such attack surface management, and by restricting API communication connected to an external network to strictly limit access to only restricted areas when accessing from the outside is allowed.

[0055] FIG. 3 is a block diagram briefly illustrating the VPC-specific configuration of an electronic device including an independently structured container within a VPC for attack surface management according to the present disclosure, and FIG. 4 is a block diagram showing the internal configuration in detail.

[0056] An electronic device comprising independently structured containers within a VPC for attack surface management according to one embodiment of the present disclosure may include a virtual private cloud (VPC) (100) deployed within a cloud, a container (200) comprising a plurality of work nodes that are independently deployed within the VPC (100) according to front, backend, and backing functions and perform tasks corresponding to the separated functions, a memory in which at least one process for performing an attack surface management operation is stored; and at least one processor (14) that performs the operation according to the process.

[0057] Specifically, as illustrated in FIG. 3, the VPC (100) is subdivided into containers (200) so that the service can be flexibly expanded and scaled in containers (200).

[0058] The container (200) can be divided into a front end (110), an API communication module (120), a back end (130), and a scan module (140). In addition, a database (150, see FIG. 4), a backing system (160), and a default network (170) can also be divided.

[0059] Each container (200) functions independently, and auto-scaling can be performed on each container (200) according to a scale-in / scale-out trigger.

[0060] A scale-in / scale-out trigger refers to a cause that automatically causes scale-in / scale-out to occur based on at least one of the CPU, memory, and external communication response speed according to the performance requirements of each container (200), and the trigger may differ depending on the type of container (200).

[0061] The above VPC (100) can be distributed by target region, and each VPC (100) exists independently so that even if a problem occurs in one VPC (100), it does not affect other VPCs (100).

[0062] As illustrated in FIG. 4, the container (200) may include a pair of unit work nodes and pod pairs. For example, the work nodes (301, 302) of the frontend (110), which is one of the containers (200), include a pair of unit pod pairs, and the at least one processor may be configured so that the pod pairs are dynamically scaled in units of containers according to a microservices architecture (MSA).

[0063] The worker node (301) of the front end (110) includes an nginx pod and a node.js pod, and another worker node (302) of the front end (110) may also include an nginx pod and a node.js pod. A pair of worker nodes (301, 302) can be duplicated. Redis technology can be applied to share login sessions.

[0064] Other containers may also contain a pair of worker nodes and a pair of pods.

[0065] Through pod redundancy, communication is not interrupted even with network fluctuations, and a pair of pods can complement each other's gaps, allowing the ASM solution to operate without failure.

[0066] At least one processor (14) can automatically increase or decrease the number of pods of the work nodes of each container (200) in a cloud environment for automatic expansion and dynamic scaling.

[0067] In one embodiment, the at least one processor (14) can independently expand the pod pairs of the corresponding container (200) when traffic to at least one container (200) increases.

[0068] At this time, the extended pod pairs can be connected in a mesh form. It is a design structure that enables data transmission and reception through an alternative path even if the existing path between pods cannot be used due to network fluctuations or failures on the network.

[0069] Additionally, the container (200) may place a private load balancer between the pods. It must ensure equal traffic distribution between internal pods for availability or load balancing, and the private load balancer can induce traffic distribution according to the increase or decrease of pods.

[0070] In addition, the security of the internal network can be enhanced as traffic for each service is separated through a private load balancer.

[0071] For example, a private load balancer (303) can be placed between the nginx pod in the work node (301) of the frontend (110) and the nginx pod in the work node (302), and between the node.js pod in the work node (301) and the nginx pod in the work node (302) to distribute traffic between pods, and a separate private load balancer can also be placed in the backend (130), which is another container (200), so that traffic is not shared between containers (200).

[0072] When traffic surges in a specific container (200), a load is placed on a specific function, and only the pods of the specific container (200) can be scaled independently to efficiently distribute resources. Since there is no need to provide resources to other containers (200) that are not under load, resource usage can be optimized.

[0073] In addition, since all pods have redundancy and automatic recovery functions, if a pod failure occurs within a worker node of a specific container (200) and functionality is degraded, a scale-in can be performed to add a new pod to ensure resource usage.

[0074] On the other hand, if the load of applications installed on a pod increases, K8s can automatically add new pods to distribute traffic across multiple pods, and if the load decreases, it can reduce the number of pods to optimize resources.

[0075] Therefore, pod growth and decline are dynamically scaled according to fine-grained criteria considering ASM characteristics, and pods per container can be expanded by utilizing microservices architecture (MSA).

[0076] In one embodiment, the frontend work nodes (301, 302) of the frontend (110) include an nginx pod and a node.js pod, and the at least one processor (14) may be configured to scale out the frontend (110) when the CPU load for the nginx pod exceeds a preset threshold or the memory load for the node.js pod exceeds a preset threshold.

[0077] For example, the preset threshold for CPU load may be 70%, and the preset threshold for memory load may be 75%. Since the importance of CPU and memory may vary depending on the pod type, scale-out can be performed on the more important CPU or memory.

[0078] Additionally, as an embodiment, the backend work node of the backend (130) includes a Scan pod and a Core pod, and the at least one processor (14) may be configured to scale out the backend (130) when the scan processing capability of the Scan pod becomes more than twice the maximum scan processing capability, or when the CPU load and memory load for the Core pod exceed a preset threshold.

[0079] Referring to FIG. 4, the Scan pod may be an ASM Scan of the backend (130), and the Core pod may be an ASM Core of the backend (130). The Scan pod and Core pod may be redundant and arranged as a pair with a private load balancer in between.

[0080] Scan pods can scan up to 42,910.16 IPs and 39,137.97 domains per 24 hours, and to handle the Scan pod's 24-hour maximum, Core pods, which perform scoring and post-processing functions, must be configured with higher performance than Scan pods.

[0081] Therefore, if the Scon pod processes twice the maximum amount that can be processed in 24 hours, when the Core pod reaches the CPU 60% and memory 70% threshold, at least one processor (14) can perform auto-scale-out.

[0082] Additionally, as an embodiment, the at least one processor (14) may be configured to scale up the database (150) when the number of the Scan pods and the Core pods reaches the maximum number of scale-outs and it is monitored that the node where the database (150) is running is in an overloaded state.

[0083] For example, if the Scan pod processes twice the maximum capacity that can be processed in 24 hours, and the Core pod reaches the CPU 60% and memory 70% thresholds and at least one processor (14) performs auto-scale-out, and the nodes within the database (150) which is a container (200) are overloaded when scaled out to the maximum number of scale-outs possible from the Scan pod and Core pod, the performance of the nodes within the database (150) can be auto-scaled up by 30%. Additional resources can be allocated to the CPU or memory.

[0084] In other words, when the number of the Scan pods and Core pods reaches the maximum number of scale-outs and it is monitored that the node where the database (150) is running is overloaded, at least one processor (14) can be configured to scale up the database (150).

[0085] In one embodiment, the CPU allocation and memory allocation can be dynamically adjusted using a scale-up method in K8s for the database (150).

[0086] The database (150) can perform auto-scale-up by selecting a scalable method in K8s.

[0087] For reference, the database (150) is separated into a main DB required for the ASM service and a CUSTOMER DB where customer subscription information is stored, and the CUSTOMER DB can be logically isolated with a separate scheme for tenancy separation to enhance security.

[0088] The electronic device (100) according to the present disclosure monitors and tracks CPU usage, memory usage, and network status in real time, and can automatically add pods by targeting a target container when resources become insufficient or usage increases rapidly.

[0089] Meanwhile, the above container (200) may further include an internet gateway (180) that operates in an isolated environment within the VPC (100) and allows limited connection to external services.

[0090] A limited internet service for external API integration can be provided, and the frontend (110) can attempt a limited connection with the Google Maps API to provide location information, and the backend (130) can attempt a limited connection with the company's internal service API.

[0091] In other words, the network can be isolated by separating it into different subnets according to the purpose. Referring to FIG. 4, if the VPC (100) has the address 192.168.0.0 / 16, the default network (170) subnet, the frontend (110) subnet (192.168.10), the backend (130) subnet (192.168.20), the backing system (160) subnet (192.168.30), and the database (150) subnet (192.168.100) all have different addresses and are network isolated from each other.

[0092] In an isolated state, it can only be connected to an external API through an internet gateway (120) connected to the frontend subnet and the backend subnet.

[0093] Additionally, the at least one processor (14) may be configured to physically back up regional critical service data to a physically separated container (200).

[0094] The primary backup can be performed in a local area, and the secondary backup can be performed in a remote area. For example, you can perform a primary backup in the Pangyo area and a secondary backup in the Pyeongchon area.

[0095] Referring to Fig. 4, only users with certain permissions can access the cloud system (1000) through an SSLVPN connection.

[0096] At this time, the containers that can be directly accessed via SSLVPN may be limited to Bastion servers within the default network (170). Bastion servers can operate RBAC-based K8s clusters and perform deployments, cluster policy deployments, etc.

[0097] In other words, a user with access rights can access the Bastion server of the default network (170) via the cloud system (1000) through the SLLVPN. The default network (170) deployed inside the VPC operates in an isolated environment physically separated from the external network, thereby minimizing the attack surface.

[0098] In addition, users with access rights can obtain only information related to the ASM solution from the Bastion server and cannot access other containers (200), so they can access admin information while maintaining security.

[0099] However, by allowing limited connection to specific external services through the internet gateway (501), it is possible to support the application of essential security patches or the use of essential external resources.

[0100] Meanwhile, at least one of the above-mentioned container (200) may further include at least one of a private load balancer that performs traffic distribution between the pod pairs and a big data platform (405) that integrates all log data within the device to provide an integrated dashboard.

[0101] For example, the frontend (110) can distribute traffic between pods evenly by deploying a private load balancer (303) that connects a pair of pods.

[0102] Additionally, the backing system (160) can collect all logs of the electronic device according to the present disclosure, e.g., services, applications, audits, through a big data platform and provide an integrated dashboard.

[0103] As illustrated in FIG. 4, a developer can build a container through a build server and push it to a VPC (100) that stores the container.

[0104] In addition to structuring independent containers (200) within the VPC (100), the electronic device (100) according to the present disclosure can operate the VPC (100) separately for each region to properly comply with the compliance required for each region.

[0105] By providing strong control over the physical location and processing method of data, it may be more advantageous for companies to meet global compliance requirements. In particular, this can be achieved by hosting regional VPCs (100) when it is prohibited to transfer specific data outside the region where the company is located.

[0106] Additionally, an enterprise using the electronic device (100) according to the present disclosure may share the resources of the work nodes between the front end (110) and the back end (130), but may provide an isolated environment between the front end (110) and the back end (130) to ensure independence.

[0107] Among the work nodes of the frontend (110), nginx pods provide static resources and node.js pods provide dynamic resources, so that the application can be deployed and web services can be provided in a mixed configuration. Auto-scaling can be performed based on the resource threshold of nginx pods or node.js pods.

[0108] Work nodes of the backend (130) are also shared, and the Scan pod can scan customer assets, while the Core pod can handle scoring, preprocessing, and frontend (110) requests. The backend (130) can perform pod-by-pod auto-scaling based on resource load.

[0109] The database (150) has a multi-tenant structure to maintain independence, so unlike pods, the auto-scaling conditions may be more complex.

[0110] As an example, scaling up may occur immediately if the CPU exceeds a preset threshold or if the IOS exceeds a preset threshold. Alternatively, scaling up may occur after checking for latency if the average response latency increases by 50% and the query time exceeds a preset threshold. Alternatively, scaling up may be performed after additional verification if the number of connections exceeds a preset threshold or if a specific tenant occupies 50% of the total resources. Different triggers may be checked and different methods of scaling up may be performed depending on the priority.

[0111] Meanwhile, a method for manufacturing an electronic device comprising independently structured containers within a VPC for attack surface management performed by a processor of the device according to the present disclosure may include the steps of: deploying a Virtual Private Cloud (VPC) within a cloud; independently deploying containers within the VPC, each comprising a plurality of worker nodes that perform tasks corresponding to the separated functions, by separating them according to front, backend, and backing functions; deploying a pair of unit pod pairs from the worker nodes of the containers; and adjusting the pod pairs so that they are dynamically scaled in container units according to a microservices architecture (MSA).

[0112] Content that overlaps with the above is omitted for the sake of brevity in the specification.

[0113] Meanwhile, the disclosed embodiments may be implemented in the form of a recording medium that stores instructions executable by a computer. The instructions may be stored in the form of program code and, when executed by a processor, may generate a program module to perform the operation of the disclosed embodiments. The recording medium may be implemented as a computer-readable recording medium.

[0114] Computer-readable recording media include all types of recording media that store instructions that can be decoded by a computer. Examples include ROM (Read Only Memory), RAM (Random Access Memory), magnetic tape, magnetic disk, flash memory, optical data storage devices, etc.

[0115] As described above, the disclosed embodiments have been explained with reference to the attached drawings. Those skilled in the art will understand that the present disclosure may be practiced in forms different from the disclosed embodiments without changing the technical spirit or essential features of the present disclosure. The disclosed embodiments are illustrative and should not be interpreted restrictively. Explanation of the symbols

[0116] 100: VPC 110: Frontend Container 120: API communication module container 130: Backend Container 140: Scan Module Container 150: DB container 160: Backing System Container 170: Default network container 11: Input / Output Module 12: Communication Module 13: Memory 14: Processor

Claims

Claim 1 An electronic device comprising: a Virtual Private Cloud (VPC) deployed within a cloud; a container including a plurality of worker nodes that are independently deployed within the VPC, separated according to front-end, back-end, and backing functions, and perform tasks corresponding to the separated functions; a memory storing at least one process for performing an attack surface management operation; and at least one processor that performs the operation according to the process; wherein the worker nodes of the container include a pair of units called pod pairs, and the at least one processor includes an independently structured container within the VPC for attack surface management configured such that the pod pairs are dynamically scaled in container units according to a microservices architecture (MSA). Claim 2 An electronic device comprising an independently structured container within a VPC for attack surface management, wherein the at least one processor independently expands a pod pair of the corresponding container when traffic surges in at least one of the containers, and the expanded pod pairs are configured to be connected in a mesh form. Claim 3 An electronic device comprising an independently structured container within a VPC for attack surface management, wherein the frontend worker node of the frontend container includes an nginx pod and a node.js pod, and the at least one processor is configured to scale out the frontend container when the CPU load for the nginx pod exceeds a preset threshold or the memory load for the node.js pod exceeds a preset threshold. Claim 4 An electronic device comprising an independently structured container within a VPC for attack surface management, wherein the backend worker node of the backend container includes a Scan pod and a Core pod, and the at least one processor is configured to scale out the backend container when the scan processing capability of the Scan pod becomes more than twice the maximum scan processing capability, or when the CPU load and memory load for the Core pod exceed a preset threshold. Claim 5 In claim 4, the at least one processor is an electronic device comprising an independently structured container within a VPC for attack surface management configured to scale up a database container when the number of the Scan pods and the Core pods reaches a scale-out maximum number and it is monitored that the node where the database is running is overloaded. Claim 6 In claim 1, the VPC is an electronic device comprising independently structured containers within the VPC for attack surface management distributed by target region. Claim 7 An electronic device comprising an independently structured container within a VPC for attack surface management, wherein the container further comprises an internet gateway that operates in an isolated environment within the VPC and allows limited connectivity with external services. Claim 8 In claim 7, the at least one processor is an electronic device comprising an independently structured container within a VPC for attack surface management configured to physically dissipate and back up regional critical service data to a physically separated, distinct container. Claim 9 An electronic device comprising an independently structured container within a VPC for attack surface management, wherein at least one of the above-mentioned containers further comprises: a Private Load Balancer that performs traffic distribution between the pod pairs; and a Big Data Platform that integrates all log data within the device to provide an integrated dashboard. Claim 10 A method for manufacturing an electronic device comprising independently structured containers within a VPC for attack surface management performed by a processor of the device, comprising: a step of deploying a Virtual Private Cloud (VPC) within a cloud; a step of deploying a container comprising a plurality of worker nodes that are independently deployed, each classified according to front-end, back-end, and backing functions within the VPC and perform tasks corresponding to the classified functions; a step of deploying a pair of unit pod pairs from the worker nodes of the container; and a step of adjusting the pod pairs so that they are dynamically scaled in container units according to a microservices architecture (MSA).

Citation Information

Patent Citations

  • Multi-cluster ingress

    KR1020230038597A

  • Technologies for automatically configuring minimum cloud service access permissions for container applications.

    KR1020230146534A

  • Kubernetes-based auto-scale method and apparatus

    KR1020230158736A

  • Method for balanced scale-out of resource on distributed and collaborative container platform environment

    KR102172607B1

  • Apparatus, method, system and program for integrated security control for monitoring Kubernetes cluster

    KR102606713B1