Container vulnerability correction system and container vulnerability correction method

The system addresses the challenge of identifying and remediating vulnerabilities in container images by analyzing construction scripts, enabling efficient and targeted remediation based on layer origins.

JP2024170106APending Publication Date: 2024-12-06HITACHI LTD
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
JP2023087085
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-05-26
Publication Date
2024-12-06

AI Technical Summary

Technical Problem

Existing systems struggle to determine the origin of vulnerabilities in container images, making it difficult to propose appropriate remediation methods for layers within containers or container images.

Method used

A container vulnerability remediation system that identifies the origin of vulnerabilities by analyzing container construction scripts and layer creation methods, providing tailored remediation options based on the identified information.

Benefits of technology

Enables effective and targeted vulnerability remediation by specifying appropriate methods for each vulnerable layer, reducing the time required to address security issues in container systems.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024170106000001_ABST
    Figure 2024170106000001_ABST
Patent Text Reader

Abstract

To provide a container vulnerability correction system which can propose an appropriate vulnerability correction method according to the creation origin of a layer having vulnerability of a container or a container image when vulnerability is found in the container on a system or the container image of a registry (repository), and a container vulnerability correction method.SOLUTION: The container vulnerability correction system acquires a container image for creating a container including a vulnerability layer or a container construction script for creating a container image including a vulnerability layer, on the basis of vulnerability specifying information. The container vulnerability correction system analyzes the container construction script to identify a method of creating a vulnerability layer and proposes options of vulnerability correction methods corresponding to the identified method of creating a vulnerability layer.SELECTED DRAWING: Figure 1
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to a container vulnerability correction system and a container vulnerability correction method. [Background technology]

[0002] The security risk of systems is increasing year by year. In order to provide a safe and secure system, it is essential to quickly respond to these vulnerabilities. Patent Document 1 discloses an automated system for solving computer vulnerabilities. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Special Publication No. 2005-532606 Summary of the Invention [Problem to be solved by the invention]

[0004] When a vulnerability is found in a container on a system or in a container image in a registry (repository), it is difficult to determine whether the layer originates from the base image or is a library, binary, configuration file, etc. that was added later. Therefore, when a vulnerability is found in a container or a container image in a registry (repository), it is difficult to propose an appropriate vulnerability remediation method according to the origin (creation method) of the container or container image layer that has the vulnerability.

[0005] The present invention has been made to solve the above problems. That is, one of the objects of the present invention is to provide a container vulnerability correction system and a container vulnerability correction method that can propose an appropriate vulnerability correction method according to the origin of the layer having the vulnerability of the container or the container image when a vulnerability is found in a container on a system or a container image in a registry (repository). [Means for solving the problem]

[0006] In order to solve the above problems, the container vulnerability repair system of the present invention is a container vulnerability repair system that includes an information processing device that acquires information regarding a container or a container image, and the information processing device is configured to acquire vulnerability identification information indicating a container or container image having a vulnerability, and a vulnerability layer that is a layer having a vulnerability, acquire a container image for creating a container including the vulnerability layer or a container construction script for creating a container image including the vulnerability layer based on the vulnerability identification information, identify a method for creating the vulnerability layer by analyzing the container construction script, and propose options for vulnerability repair methods according to the identified method for creating the vulnerability layer.

[0007] The container vulnerability repair method of the present invention is a container vulnerability repair method that uses an information processing device to acquire information regarding a container or a container image, and the information processing device acquires vulnerability identification information indicating a container or container image having a vulnerability, and a vulnerability layer which is a layer having a vulnerability, and based on the vulnerability identification information, acquires a container image for creating a container including the vulnerability layer, or a container construction script for creating a container image including the vulnerability layer, identifies a method for creating the vulnerability layer by analyzing the container construction script, and proposes options for vulnerability repair methods according to the identified method for creating the vulnerability layer. Effect of the Invention

[0008] According to the present invention, when a vulnerability is found in a container on a system or a container image in a registry (repository), it is possible to propose an appropriate vulnerability remediation method according to the origin of the vulnerable layer of the container or container image. Note that the effects described here are not necessarily limited to those described herein, and may be any of the effects described in this disclosure. [Brief description of the drawings]

[0009] [Figure 1] FIG. 1 is a diagram for explaining an overview of a container vulnerability automatic correction system according to a first embodiment of the present invention. [Diagram 2] FIG. 2 is a block diagram showing an example of the configuration of a system including a container vulnerability automatic repair system according to the first embodiment of the present invention. [Diagram 3] FIG. 3 is a block diagram showing an example of the configuration of a computer on which the components shown in FIG. 2 operate. [Figure 4] FIG. 4 is a block diagram showing an example of programs and data stored in a memory or storage device of a terminal used by a user and in a memory or storage device of the container vulnerability automatic correction system. [Diagram 5] FIG. 5 is a diagram for explaining container-container image correspondence management information. [Figure 6] FIG. 6 is a diagram for explaining container image-container construction script correspondence management information. [Figure 7] FIG. 7 is a diagram for explaining vulnerability fix option information. [Figure 8] FIG. 8 is a diagram for explaining the difficulty of identifying a method for creating a layer having vulnerabilities. [Figure 9] FIG. 9 is a flowchart showing a process flow executed by the vulnerability fix option extraction unit. [Figure 10] FIG. 10 shows an example of a vulnerability fix result screen displayed by the vulnerability fix result presentation unit. [Figure 11] FIG. 11 is a flowchart showing a process flow executed by the vulnerability fix option extraction unit. [Figure 12] FIG. 12 is a flowchart showing a process flow executed by the vulnerability fix option extraction unit. [Figure 13] FIG. 13 is a diagram for explaining an overview of a container vulnerability automatic repair system according to the second embodiment of the present invention. [Figure 14]FIG. 14 is a block diagram showing an example of programs and data stored in the memory or storage device of a terminal used by a user and the memory or storage device of the container vulnerability automatic correction system. [Figure 15] FIG. 15 is a diagram for explaining an example of the provisional measure information. [Figure 16] FIG. 16 shows an example of a vulnerability fix result screen displayed by the vulnerability fix result presentation unit. [Figure 17] FIG. 17 is a flowchart showing a process flow executed by the ideal measure re-execution unit of the container vulnerability automatic correction system. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] Hereinafter, each embodiment of the present invention will be described with reference to the drawings. In addition, in all the drawings of the embodiments, the same or corresponding parts may be denoted by the same reference numerals.

[0011] In the following explanation, various types of information may be explained using expressions such as "records", but the various types of information may be expressed using other data structures. When explaining identification information, expressions such as "ID", "name", and "designation" are used, but these are mutually interchangeable. In the following explanation, processing may be explained using a program or functional block as the subject, but the subject of processing may be a CPU or a device instead of a program or functional block.

[0012] <<First embodiment>> <Summary> A description will now be given of a container vulnerability automatic remediation system 100 according to a first embodiment of the present invention. Fig. 1 is a diagram for explaining an overview of the container vulnerability automatic remediation system 100 according to the first embodiment of the present invention.

[0013] The container vulnerability automatic correction system 100 acquires vulnerability identification information 210 for vulnerable containers and / or container images detected by a vulnerability check tool 200 .

[0014] The vulnerability check tool 200 scans containers and / or container images stored in a container image registry / repository 400 of containers and / or container images deployed in the monitored system 300, identifies vulnerable containers and / or container images, and transmits vulnerability identification information 210 indicating the identified vulnerable containers and / or container images to the container vulnerability automatic correction system 100. A publicly known vulnerability diagnosis tool (e.g., "Trivy", "Vuls", etc.) can be applied to the vulnerability check tool 200.

[0015] 1 includes information indicating a container ID / name, a layer ID, and a vulnerability content. The information indicating the container ID / name includes identification information of the container. The layer ID includes an ID of a layer having a vulnerability. The vulnerability content includes information indicating the content of the vulnerability.

[0016] The container vulnerability automatic remediation system 100 includes a vulnerability detection notification receiving unit 110, a vulnerability remediation option extracting unit 120, a vulnerability remediation unit 130, a testing unit 140, a vulnerability remediation result presenting unit 150, and a vulnerability remediation result applying unit 160. For convenience, the container vulnerability automatic remediation system 100 may also be referred to as a "container vulnerability remediation system."

[0017] The container vulnerability automatic correction system 100 is connected to each of a container deployment management system 500, a development management system 600, and a code management system 700 so as to be able to send and receive information therebetween.

[0018] The container deployment management system 500 has container-container image correspondence management information 510.

[0019] The development management system 600 has container image-container construction script correspondence management information 610 .

[0020] The code management system 700 includes a container build script 710 and a configuration file 720 .

[0021] Although the details will be described later, the container vulnerability automatic repair system 100 acquires vulnerability identification information 210 from the vulnerability check tool 200, and upon receiving a vulnerability detection notification, identifies and acquires the container construction script 710 that created the container image. The container construction script 710 is, for example, a Dockerfile.

[0022] The container vulnerability automatic remediation system 100 analyzes the installation path of a library having a vulnerability based on the container construction script 710. The container vulnerability automatic remediation system 100 identifies the boundary between the base layer and the original layer by comparing the layer IDs of the base image. If the base image is obtained from the private registry / repository 420, the container vulnerability automatic remediation system 100 can correct the root cause of the vulnerability by repeating the above operations. Furthermore, the container vulnerability automatic remediation system 100 can identify the package to be updated by identifying the command that installed the library having a vulnerability.

[0023] <Configuration> Fig. 2 is a block diagram showing an example of the configuration of a system including a container vulnerability automatic repair system 100 according to a first embodiment of the present invention. As shown in Fig. 2, the system includes the container vulnerability automatic repair system 100, a vulnerability check tool 200, a monitored system 300, a container image registry / repository 400, a container deployment management system 500, a development management system 600, a code management system 700, a package management server 800, and a terminal TR1. These are connected to each other via a network NW1 so as to be able to transmit and receive information to and from each other. The package management server 800 has a library.

[0024] (Computer description) Fig. 3 is a block diagram showing an example of the configuration of a computer 3000 on which the components shown in Fig. 2 operate. The computer 3000 has a CPU (Central Processing Unit) 3010 which is a processor, a memory 3020 which is a primary storage device, a non-volatile secondary storage device 3030, an input / output device 3040, and a port 3050. These components are connected to each other by a bus 3060.

[0025] CPU 3010 executes programs stored in memory 3020 to realize predetermined functions of each computer 3000. Memory 3020 stores the programs executed by CPU 3010 and data necessary for executing the programs. Programs are loaded into memory 3020 from secondary storage device 3030.

[0026] The input / output device 3040 includes one or more devices such as a display (touch panel), a pointer, a keyboard, etc. The user Us1 can operate each computer 3000 by using the input / output device 3040.

[0027] The port 3050 is connected to the network NW1. Each computer 3000 can communicate with other computers 3000 via the port 3050. The computer 3000 on which each component runs may be a virtual environment such as a virtual machine or a container. A display device (display) that does not have a function as the input / output device 3040 may be connected to the computer 3000. Each component may be configured with a plurality of computers 3000. For convenience, the computer 3000 may also be referred to as an "information processing device."

[0028] (Explanation of data organization of memory or storage device) 4 is a block diagram showing an example of programs and data stored in a memory or storage device 4000 of a terminal TR1 used by a user Us1 and a memory or storage device 4100 of the container vulnerability automatic correction system 100. Note that, for example, the memory corresponds to the above-mentioned memory 3020, and the storage device corresponds to the above-mentioned secondary storage device 3030.

[0029] The memory or storage device 4000 of the terminal TR1 has (stores (memorizes, holds)) a client program 4001 for displaying images such as a GUI (Graphical User Interface) screen on a display (touch panel). An example of the client program 4001 is a web browser.

[0030] The memory or storage device 4100 of the container vulnerability automatic repair system 100 includes a vulnerability detection notification receiving unit 110, a vulnerability repair option extraction unit 120, a vulnerability repair unit 130, a test unit 140, a vulnerability repair result presentation unit 150, and a vulnerability repair result application unit 160. The vulnerability detection notification receiving unit 110, the vulnerability repair option extraction unit 120, the vulnerability repair unit 130, the test unit 140, the vulnerability repair result presentation unit 150, and the vulnerability repair result application unit 160 are configured by programs stored in the memory or storage device 4100.

[0031] The memory or storage device 4100 of the user vulnerability automatic remediation system 100 includes container-container image correspondence management information 510, container image-container construction script correspondence management information 610, vulnerability remediation option information 121, and test scripts 141 for performing tests.

[0032] (Data Description) Fig. 5 is a diagram for explaining container-container image correspondence management information 510. As shown in Fig. 5, the container-container image correspondence management information 510 includes a container ID or name 511, a container image name 512, and a container image tag 513 as columns for storing information (values).

[0033] In the container-container image correspondence management information 510, information corresponding to each column regarding the container and container image is associated with each other and stored as row-by-row information (records). Specifically, the container ID or name 511 stores an ID or name that is identification information for identifying a container. The container image name 512 stores the name of the container image. The container image tag 513 stores the tag of the container image.

[0034] FIG. 6 is a diagram for explaining container image-container construction script correspondence management information 610. As shown in FIG. 6, the container image-container construction script correspondence management information 610 includes a container image name 611, a container image tag 612, and a container construction script file Path 613 as columns for storing information (values). In the container image-container construction script correspondence management information 610, information corresponding to each column related to the container image is associated with each other and stored as information (records) on a row-by-row basis. Specifically, the container image name 611 stores the name of the container image. The container image tag 612 stores the tag of the container image. The container construction script file Path 613 stores the Path of the container construction script file.

[0035] Fig. 7 is a diagram for explaining vulnerability fix option information 121. As shown in Fig. 7, vulnerability fix option information 121 includes vulnerability fix option 121a, vulnerability existence layer creation method 121b, and priority order 121c as columns for storing information (values). Vulnerability existence layer creation method 121b includes base image 121d and original 121e as subcolumns for storing information.

[0036] In the vulnerability remediation option information 121, information corresponding to each column of the vulnerability remediation option information is associated with each other and stored as row-by-row information (records). Specifically, the vulnerability remediation option 121a stores options for vulnerability remediation methods. The base image 121d of the vulnerability existing layer creation method 121b stores information (o) indicating an option that can be taken when the vulnerability existing layer (also called "vulnerability layer") is a layer created from a base image. The vulnerability remediation option corresponding to "o" is an option that can be taken when the layer is created from a base image. The original of the vulnerability existing layer creation method stores information (o) indicating an option that can be taken when the vulnerability existing layer is a layer created from an original. The vulnerability remediation option corresponding to "o" is an option that can be taken when the layer is created from an original.

[0037] <Overview of operation> Figure 8 is a diagram to explain the difficulty of identifying the creation method of a vulnerable layer. A container image IMG1 created from a base image BIMG1 is composed of layers. The layers of a typical container image IMG1 can be broadly divided into layers created from the base image BIMG1 and layers created later (layers created by the user's own commands).

[0038] However, the boundary between the layer created from the base image BIMG1 and the layer created later cannot be determined from the container image IMG1 (or the container created from the container image IMG1). Therefore, even if the layer with the vulnerability of the container (or the container image IMG1) can be identified, it is difficult to propose (decide) an appropriate method to fix the vulnerability.

[0039] In response to this, the container vulnerability automatic repair system 100 according to the first embodiment acquires vulnerability identification information 210, which is information related to layers of a container (or container image) having a vulnerability, by using a vulnerability check tool 200. The container vulnerability automatic repair system 100 identifies the creation origin (creation method) of the layer having a vulnerability based on the vulnerability identification information 210, container-container image correspondence management information 510, and container image-container construction script correspondence management information 610.

[0040] The container vulnerability automatic remediation system 100 presents (suggests) options of vulnerability remediation methods for remediating vulnerabilities based on the creation origin (creation method) of the identified layer. The presented options of vulnerability remediation methods are applied to a container (or container image) having a vulnerability by being selected by a user.

[0041] <Activation> The operations of the vulnerability detection notification receiving unit 110, the vulnerability fix option extracting unit 120, the vulnerability fix unit 130, the testing unit 140, the vulnerability fix result presenting unit 150, and the vulnerability fix result applying unit 160 will be described below.

[0042] (Vulnerability detection notification reception department) The vulnerability detection notification receiving unit 110 receives the vulnerability identification information 210 from the vulnerability check tool 200 and receives the vulnerability detection notification.

[0043] (Vulnerability fix option extraction part) 9 is a flowchart showing a processing flow executed by the vulnerability fix option extraction unit 120. The vulnerability fix option extraction unit 120 starts processing from step 900, and executes the processing from step 905 to step 925 described below in order, and then temporarily ends this processing flow.

[0044] Step 905: When the vulnerability detection notification receiving unit 110 receives the vulnerability identification information 210, the vulnerability remediation option extracting unit 120 identifies a layer including a vulnerability based on the vulnerability identification information 210. Furthermore, the vulnerability remediation option extracting unit 120 identifies a container image and a container image tag corresponding to the container having a vulnerability based on the vulnerability identification information 210 and the container-container image correspondence management information 510.

[0045] Step 910: Based on the identified container image and container image tag, and the container image-container construction script correspondence management information 610, the vulnerability fix option extraction unit 120 identifies the container construction script file (path to the container construction script file) of the image that includes the vulnerability corresponding to the identified container image and container image tag.

[0046] Step 915: The vulnerability fix option extraction unit 120 acquires the container construction script 710 from the code management system 700 using the path of the identified container construction script file.

[0047] Step 920: The vulnerability fix option extraction unit 120 identifies the installation source of the image of the layer including the vulnerability, based on the layer ID of the container construction script 710 and the vulnerability identification information 210. This process will be described in detail later.

[0048] Step 925: The vulnerability fix option extracting unit 120 determines a course of action according to the installation source based on the vulnerability fix option information 121.

[0049] (Vulnerability fix department) The vulnerability repair unit 130 executes the determined option (selected vulnerability repair method) and repairs the vulnerability.

[0050] (Testing Department) The test unit 140 tests, for each of the response policies (options (vulnerability remediation methods)) determined by the vulnerability remediation option extraction unit 120, whether the vulnerability has been remediated and whether the application operates normally.

[0051] At this time, the test unit 140 may perform vulnerability repair and testing using the determined vulnerability repair method in the order stored in the priority order 121c of the vulnerability repair option information 121. This allows the user Us1 to immediately apply an option with a high priority order as long as the vulnerability repair and testing of the option is completed (completed and there is no problem) even if the vulnerability repair and testing of all options is not completed, without waiting for the results of vulnerability repair and testing of other options with a low priority order, thereby shortening the time required to complete vulnerability repair. Note that the user Us1 may input information indicating the priority order corresponding to the vulnerability repair options to the container vulnerability automatic repair system 100 via the input / output device 3040, so that the priority order is stored (registered) in the priority order 121c.

[0052] (Vulnerability fix result presentation part) The vulnerability fix result presenting unit 150 presents a plurality of fix options, whether or not the options solve the vulnerabilities, and the application test results to the administrator (user Us1), and allows the administrator to select a desired fix method.

[0053] Fig. 10 shows an example of a vulnerability remediation result screen 1000 which is a GUI screen displayed by the vulnerability remediation result presentation unit 150. As shown in Fig. 10, the vulnerability remediation result screen 1000 includes vulnerability container information 1001, cause information 1002, test result information 1003, a first fix apply button 1004, a second fix apply button 1005, and a fix not apply button 1006.

[0054] Vulnerable container information 1001 includes the name of the vulnerable container, the image name, and the image tag. Cause information 1002 includes information indicating the cause of the vulnerability. Test result information 1003 includes information indicating a vulnerability remediation method, a vulnerability solution, and a test result. A first apply fix button 1004 and a second apply fix button 1005 are buttons made up of images.

[0055] When the first apply fix button 1004 is operated by the user Us1, the vulnerability fix method corresponding to that button is applied. When the second apply fix button 1005 is operated by the user Us1, the vulnerability fix method corresponding to that button is applied. When the not apply fix button 1006 is operated by the user, the vulnerability fix method corresponding to that button is not applied or implemented.

[0056] (Vulnerability fix result application part) The vulnerability remediation result application unit 160 creates a container (or container image) to which the vulnerability remediation method has been applied in accordance with the vulnerability remediation option selected by the administrator (user Us1), and deploys it to the monitored system 300 or registers it in the container image registry / repository 400.

[0057] (Details of the process to identify the source of the image containing the vulnerable layer) 11 is a flowchart showing a processing flow executed by the vulnerability fix option extraction unit 120. The vulnerability fix option extraction unit 120 starts processing from step 1100 and proceeds to step 1105, where it checks the vulnerability content of the vulnerability identification information 210 and determines whether or not the cause lies in the library. For example, if the vulnerability content of the vulnerability identification information 210 indicates that the cause lies in the library, such as "Lib-1 ver1," it is determined that the cause lies in the library, and if the vulnerability content of the vulnerability identification information 210 indicates a setting value, such as "value1," it is determined that the cause is not in the library.

[0058] If the cause lies in the library, the vulnerability fix option extraction unit 120 judges "YES" in step 1105, and sequentially executes the processes of steps 1110 to 1125 described below.

[0059] Step 1110: The vulnerability fix option extraction unit 120 acquires the base image name and tag of the container image from the container construction script 710 acquired in step 915 of FIG.

[0060] Step 1115: The vulnerability fix option extraction unit 120 identifies the registry in which the base image is stored from the base image name. Note that the base image name includes the registry host name, repository name, etc., so that the registry can be identified from the base image name.

[0061] Step 1120: The vulnerability fix option extraction unit 120 connects to the identified registry and pulls (acquires, downloads) the base image.

[0062] Step 1125: The vulnerability fix option extracting unit 120 checks the layer configuration of the base image to identify the layers that make up the base image.

[0063] Thereafter, the vulnerability fix option extraction unit 120 proceeds to step 1030 and determines whether or not the layer ID having the vulnerability is included in the layers that constitute the base image.

[0064] If the layer ID having the vulnerability is not included in the layers that constitute the base image, the vulnerability remediation option extraction unit 120 judges "NO" in step 1130, executes the processing of steps 1135 and 1140 described below in order, and then proceeds to step 1195 to temporarily terminate this processing flow.

[0065] Step 1135: The vulnerability fix option extraction unit 120 identifies that the layer having the vulnerability originates from a library that was installed later.

[0066] Step 1140: The vulnerability fix option extraction unit 120 identifies the command that installed the library having a vulnerability from the container construction script 710.

[0067] If the layer ID having the vulnerability is included in a layer that constitutes the base image, the vulnerability fix option extraction unit 120 judges "YES" in step 1130 and proceeds to step 1145, where it determines that the vulnerability originates from the base image.

[0068] Thereafter, the vulnerability fix option extractor 120 proceeds to step 1150 and determines whether the registry of the base image is a public registry / repository 410 .

[0069] If the registry of the base image is the public registry / repository 410, the vulnerability fix option extraction unit 120 determines "YES" in step 1150, proceeds to step 1095, and temporarily ends this processing flow.

[0070] If the registry of the base image is not the public registry / repository 410, the confirmed base image may have been created by a base image and a unique command. Therefore, in this case, the vulnerability fix option extraction unit 120 judges "NO" in step 1150 and proceeds to step 1155 to judge whether the container construction script 710 of the base image can be acquired.

[0071] If the base image container construction script 710 cannot be obtained, no further detailed analysis can be performed, so the vulnerability fix option extraction unit 120 judges "NO" in step 1155 and proceeds to step 1195, temporarily terminating this processing flow.

[0072] If the container construction script 710 of the base image can be acquired, the vulnerability fix option extraction unit 120 determines "YES" in step 1155 and proceeds to step 1160 to acquire a new container construction script 710, and then returns to step 1110. Then, the vulnerability fix option extraction unit 120 executes an appropriate process among steps 1110 to 1155 for the newly acquired container construction script 710. This allows the vulnerability fix option extraction unit 120 to search for the boundary between the base image and the original image created by itself, for the base image confirmed in the previous process.

[0073] If it is determined in step 1105 above that the cause is not in the library, the vulnerability fix option extraction unit 120 determines "NO" in step 1105 and proceeds to step 1165, where the processing flow shown in FIG. 12 is executed.

[0074] Fig. 12 is a flowchart showing a processing flow executed by the vulnerability fix option extraction unit 120. When the vulnerability fix option extraction unit 120 proceeds to step 1165 in Fig. 11, it starts processing from step 1200 and sequentially executes the processing of steps 1205 to 1220 described below.

[0075] Step 1205: The vulnerability fix option extraction unit 120 acquires the base image name and tag of the container image from the container construction script 710 acquired in step 915 of FIG.

[0076] Step 1215: The vulnerability fix option extracting unit 120 identifies the registry in which the base image is stored from the base image name.

[0077] Step 1220: The vulnerability fix option extraction unit 120 connects to the identified registry and pulls (acquires, downloads) the base image.

[0078] Step 1225: The vulnerability fix option extracting unit 120 checks the layer configuration of the base image to identify the layers that constitute the base image.

[0079] Thereafter, the vulnerability fix option extraction unit 120 proceeds to step 1225 to determine whether or not the layer ID having the vulnerability is included in the layers that constitute the base image.

[0080] If the layer ID having the vulnerability is not included in the layers that constitute the base image, the vulnerability remediation option extraction unit 120 judges "NO" in step 1225, executes the processing of steps 1230 to 1240 described below in order, and then proceeds to step 1295 to temporarily terminate this processing flow.

[0081] Step 1230: The vulnerability fix option extraction unit 120 identifies that the layer having the vulnerability originates from a library that was installed later.

[0082] Step 1235: The vulnerability fix option extraction unit 120 identifies the configuration file 720 having a vulnerability from the container construction script 710.

[0083] Step 1240: The vulnerability fix option extracting unit 120 identifies the setting item that is the cause of the vulnerability from the setting file 720.

[0084] If the layer ID having the vulnerability is included in a layer that constitutes the base image, the vulnerability remediation option extraction unit 120 judges "YES" in step 1225 and proceeds to step 1245, determines that the vulnerability originates from the base image, and proceeds to step 1250 to determine whether the registry of the base image is the public registry / repository 410.

[0085] If the registry of the base image is the public registry / repository 410, the vulnerability fix option extraction unit 120 determines "YES" in step 1250, proceeds to step 1295, and temporarily ends this processing flow.

[0086] If the registry of the base image is not the public registry / repository 410, the confirmed base image may have been created by a base image and a unique command. Therefore, in this case, the vulnerability fix option extraction unit 120 judges "NO" in step 1250 and proceeds to step 1255 to judge whether the container construction script 710 of the base image can be acquired.

[0087] If the base image container construction script 710 cannot be obtained, no further detailed analysis can be performed, so the vulnerability fix option extraction unit 120 judges "NO" in step 1255 and proceeds to step 1295, temporarily terminating this processing flow.

[0088] If the container construction script 710 of the base image can be acquired, the vulnerability fix option extraction unit 120 judges "YES" in step 1255 and proceeds to step 1260 to acquire a new container construction script 710, and then returns to step 1255. Then, the vulnerability fix option extraction unit 120 executes an appropriate process among steps 1210 to 1255 for the newly acquired container construction script 710. This allows the vulnerability fix option extraction unit 120 to search for the boundary between the base image and the original image created by itself, for the base image confirmed in the previous process.

[0089] <Effects> As described above, the container vulnerability automatic remediation system 100 according to the first embodiment of the present invention can propose an appropriate vulnerability remediation method (options for vulnerability remediation methods) for a vulnerable container (or container image) by identifying the origin (creation method) of the layer of the vulnerable container (or container image).

[0090] Furthermore, the container vulnerability automatic remediation system 100 according to the first embodiment can identify the resource configuration file 720 used when constructing a container based on the container construction script 710 used to create a vulnerable container, acquire the identified configuration file 720, verify its contents, and identify the configuration item that caused the vulnerability. Therefore, the container vulnerability automatic remediation system 100 according to the first embodiment can also propose a vulnerability remediation method (options for vulnerability remediation methods) corresponding to a vulnerability caused by the resource configuration contents.

[0091] Furthermore, when a vulnerability is contained in a base image, the container vulnerability automatic patching system 100 of the first embodiment determines whether the base image is one that user Us1 can update (whether user Us1 is the owner of the base image, whether the base image was created by someone belonging to a specific group that includes user Us1, whether it was downloaded from somewhere, whether it is a public repository, a private repository, etc.).

[0092] The container vulnerability automatic patching system 100 according to the first embodiment repeatedly acquires and analyzes the container construction script 710 used when the base image was created, and searches for the root cause of the vulnerability, as long as it is within the range of management of those belonging to a specific group including the user Us1. The container vulnerability automatic patching system 100 according to the first embodiment then ends the process when the base image is outside the range of management of those belonging to a specific group including the user Us1, or when the command that installed the library having the vulnerability is identified. In this way, the container vulnerability automatic patching system 100 according to the first embodiment can search for the root cause of the vulnerability and patch the vulnerability from the root.

[0093] <<Second embodiment>> The container vulnerability automatic remediation system 100 according to the second embodiment of the present invention will now be described. Fig. 13 is a diagram for explaining the outline of the container vulnerability automatic remediation system 100 according to the second embodiment of the present invention. The container vulnerability automatic remediation system 100 according to the second embodiment differs from the container vulnerability automatic remediation system 100 according to the first embodiment only in the following points.

[0094] The container vulnerability automatic correction system 100 includes a temporary measure information configuration unit 170 and an ideal measure re-execution unit 180.

[0095] The following description will focus on these differences.

[0096] (Explanation of data organization of memory or storage device) FIG. 14 is a block diagram showing an example of programs and data stored in a memory or storage device 4000 of a terminal TR1 used by a user Us1, and a memory or storage device 4100 of the container vulnerability automatic correction system 100.

[0097] The memory or storage device of the terminal TR1 has (stores (memorizes, holds)) a client program 4001 for displaying a GUI screen on a display (touch panel). An example of the client program 4001 is a web browser.

[0098] The memory or storage device 4000 of the terminal TR1 includes a vulnerability detection notification receiving unit 110, a vulnerability fix option extracting unit 120, a vulnerability fix unit 130, a test unit 140, a vulnerability fix result presenting unit 150, a vulnerability fix result applying unit 160, a provisional measure information constructing unit 170, and an ideal measure re-executing unit 180. The vulnerability detection notification receiving unit 110, the vulnerability fix option extracting unit 120, the vulnerability fix unit 130, the test unit 140, the vulnerability fix result presenting unit 150, the vulnerability fix result applying unit 160, the provisional measure information constructing unit 170, and the ideal measure re-executing unit 180 are configured by programs stored in the memory or storage device 4100.

[0099] The memory or storage device 4100 of the user vulnerability automatic remediation system 100 includes container-container image correspondence management information 510, container image-container construction script correspondence management information 610, vulnerability remediation option information 121, temporary measure information 1500, and test scripts 141 for performing tests.

[0100] Fig. 15 is a diagram for explaining an example of provisional measure information 1500. As shown in Fig. 15, the provisional measure information 1500 includes, as columns for storing information (values), a container name 1501, an image name 1502, an image tag 1503, layer information 1504, a provisional measure 1505, and an ideal modification method 1506. The layer information 1504 includes, as sub-columns for storing information, a layer ID 1507, a creation method 1508, base image information 1509, and a layer construction command 1510.

[0101] The container name 1501 stores the name of the container. The image name 1502 stores the name of the container image. The image tag 1503 stores the tag of the container image. The layer ID 1507 of the layer information 1504 stores the ID of the layer. The creation method 1508 stores the creation method of each layer. The base image information 1509 stores information on the base image. The layer construction command 1510 stores a command for constructing the corresponding layer. The provisional measure 1505 stores information indicating the provisional measure. The ideal modification method 1506 stores information indicating the ideal measure.

[0102] <Activation> Below, we will explain the operations of the vulnerability detection notification receiving unit 110, the vulnerability fix option extracting unit 120, the vulnerability fix unit 130, the testing unit 140, the vulnerability fix result presenting unit 150, the vulnerability fix result applying unit 160, the provisional measure information composing unit 170, and the ideal measure re-executing unit 180. Note that the operations of the vulnerability detection notification receiving unit 110, the vulnerability fix option extracting unit 120, the vulnerability fix unit 130, and the testing unit 140 are the same as those in the first embodiment, so their explanations will be omitted.

[0103] (Vulnerability fix result presentation part) The vulnerability fix result presentation unit 150 presents the administrator (user Us1) with multiple fix options, whether or not the options resolve the vulnerability, and the application test results, and allows the administrator to select a desired fix method. Furthermore, the vulnerability fix result presentation unit 150 displays a GUI screen that allows the user Us1 to select whether or not to save an ideal measure that cannot resolve the vulnerability at present but may be able to resolve the vulnerability in the future as an ideal measure.

[0104] Fig. 16 shows an example of a vulnerability remediation result screen 1600 which is a GUI screen displayed by the vulnerability remediation result presentation unit 150. As shown in Fig. 16, the vulnerability remediation result screen 1600 includes vulnerability container information 1601, cause information 1602, test result information 1603, a first apply remediation button 1604, a second apply remediation button 1605, a first save ideal measure button 1606, a second save ideal measure button 1607, and a do not apply remediation button 1608.

[0105] Vulnerable container information 1601 includes the name of the vulnerable container, the image name, and the image tag. Cause information 1602 includes information indicating the cause of the vulnerability. Test result information 1603 includes information indicating the vulnerability remediation method, the vulnerability solution, and the test result. A first apply fix button 1604 and a second apply fix button 1605 are buttons made up of images.

[0106] When the first apply fix button 1604 is operated by the user Us1, the vulnerability fix method corresponding to that button is applied. When the second apply fix button 1605 is operated by the user Us1, the vulnerability fix method corresponding to that button is applied. The first ideal measure save button 1606 and the second ideal measure save button 1607 are buttons made up of images.

[0107] When the first ideal measure save button 1606 is operated by the user Us1, the vulnerability remediation method corresponding to the button is saved as an ideal measure (ideal remediation method). When the second ideal measure save button 1607 is operated by the user Us1, the vulnerability remediation method corresponding to the button is saved as an ideal measure (ideal remediation method).

[0108] When the non-apply fix button 1608 is operated by the user Us1, the vulnerability fix method corresponding to that button is not applied and is not implemented.

[0109] When the non-apply fix button 1006 is operated by the user Us1, the vulnerability fix method corresponding to that button is not applied and is not implemented.

[0110] (Vulnerability fix result application part) The vulnerability remediation result application unit 160 creates a container (or container image) to which the vulnerability remediation method has been applied in accordance with the vulnerability remediation option selected by the administrator (user Us1), and deploys it to the monitored system 300 or registers it in the container image registry / repository 400.

[0111] (Provisional Measures Information Component) The provisional measure information configuration part 170 configures (creates) the provisional measure information 1500 based on the input to the vulnerability fix result screen 1600.

[0112] (Ideal Measures Re-Implementation Department) FIG. 17 is a flowchart showing a process flow executed by the ideal measure re-execution unit 180 of the container vulnerability automatic correction system 100.

[0113] The ideal measure re-execution unit 180 starts the process from step 1700 , proceeds to step 1710 , identifies an ideal correction method based on the provisional measure information 1500 , and proceeds to step 1720 .

[0114] When the ideal measure re-execution unit 180 proceeds to step 1720, it determines whether or not it has been detected that the ideal correction method is possible. For example, the ideal measure re-execution unit 180 detects that the ideal correction method is possible (vulnerability can be corrected) by periodically checking a base image update, etc.

[0115] If it cannot be detected that the ideal correction method is possible, the ideal measure re-execution unit 180 determines “NO” in step 1720 and returns to step 1720 .

[0116] If it is detected that the ideal correction method is possible, the ideal measure re-execution unit 180 judges "YES" in step 1720, executes the processing of steps 1730 to 1750 described below in order, and then proceeds to step 1795 to temporarily terminate this processing flow.

[0117] Step 1730: The ideal measure re-execution unit 180 causes the vulnerability correction unit 130 to execute the ideal correction method.

[0118] Step 1740: The ideal measure re-execution unit 180 causes the test unit 140 to execute a test.

[0119] Step 1750: The ideal measure re-execution unit 180 causes the vulnerability remediation result presentation unit 150 to display the test result. At this time, the ideal measure re-execution unit 180 may cause the vulnerability remediation result presentation unit 150 to display a screen including information indicating that the provisional measure is no longer necessary on a display device (display) of the terminal TR1.

[0120] <Effects> As described above, the container vulnerability automatic remediation system 100 according to the second embodiment of the present invention achieves the same effects as those of the first embodiment. Furthermore, the container vulnerability automatic remediation system 100 according to the second embodiment can apply a provisional vulnerability remediation method when an ideal vulnerability remediation method is not effective, and when the ideal vulnerability remediation method becomes effective after the fact, can notify the user of this and apply the ideal vulnerability remediation method instead of the provisional vulnerability remediation method.

[0121] For example, there are cases where a vulnerability exists in a base image, but the vulnerability has not yet been fixed in the latest version of the base image, so it is not possible to address the issue by updating the base image, and as a temporary measure, the library is updated directly using a package update command. On the other hand, in this case, there are cases where it would be desirable to use a base image that addresses the vulnerability once it is released.

[0122] Therefore, the container vulnerability automatic patching system 100 of the second embodiment periodically checks for base image updates, and when a vulnerability-fixing version of the base image is released, notifies the administrator (user Us1) of the updates along with the test results of using the updated version to patch the vulnerability. When a more desirable, ideal patching method becomes available, the vulnerability can be patched again using that ideal patching method.

[0123] <<Modifications>> The present invention is not limited to the above-described embodiments, and various modifications can be adopted within the scope of the present invention. Furthermore, the above-described embodiments can be combined with each other without departing from the scope of the present invention.

[0124] In each of the above embodiments, either one of the process flow shown in the flowchart of FIG. 11 and the process flow shown in the flowchart of FIG. 12 may be executed.

[0125] In each of the above embodiments, instead of the processing flow shown in the flowchart of Fig. 11, a processing flow in which steps 1155 and 1160 of the flowchart of Fig. 11 are omitted may be executed. In each of the above embodiments, instead of the processing flow shown in the flowchart of Fig. 12, a processing flow in which steps 1255 and 1260 of the flowchart of Fig. 12 are omitted may be executed. Even in these cases, by identifying the origin (creation method) of the creation of the layer of the vulnerable container (or container image), it is possible to propose an appropriate vulnerability remediation method (options of vulnerability remediation methods) for the vulnerable container (or container image). [Explanation of symbols]

[0126] 100...container vulnerability automatic repair system, 110...vulnerability detection notification receiving unit, 120...vulnerability repair option extraction unit, 130...vulnerability repair unit, 140...testing unit, 150...vulnerability repair result presentation unit, 160...vulnerability repair result application unit, 170...temporary measure information composition unit, 180...ideal measure re-implementation unit, 200...vulnerability check tool, 210...vulnerability identification information, 300...monitored system, 400...container image registry / repository, 500...container deployment management system, 600...development management system, 700...code management system

Claims

1. A container vulnerability correction system including an information processing device that acquires information about a container or a container image, The information processing device includes: Obtaining vulnerability identification information that indicates a container or container image having a vulnerability and a vulnerability layer that is a layer having a vulnerability; Based on the vulnerability identification information, a container image for creating a container including the vulnerability layer or a container construction script for creating a container image including the vulnerability layer is obtained, and a method for creating the vulnerability layer is identified by analyzing the container construction script, and a vulnerability fixing method option is proposed according to the identified method for creating the vulnerability layer. It was configured as follows: Container vulnerability remediation system.

2. 2. The container vulnerability correction system according to claim 1, The information processing device includes: remediating the vulnerability according to the alternative vulnerability remediation method and testing; It was configured as follows: Container vulnerability remediation system.

3. 3. The container vulnerability correction system according to claim 2, The information processing device includes: By analyzing the container build script, it is determined whether the vulnerability layer originates from a base image or not, and depending on the determination result, it is possible to suggest options for remediating the vulnerability. It was configured as follows: Container vulnerability remediation system.

4. 4. The container vulnerability correction system according to claim 3, The information processing device includes: If the vulnerability layer is from the base image, determining whether the registry of the base image is a public registry, and terminating analysis if the registry of the base image is the public registry; If the registry of the base image is not the public registry and the container construction script is available, obtain the available container construction script and analyze the obtained container construction script. It was configured as follows: Container vulnerability remediation system.

5. 5. The container vulnerability correction system according to claim 4, The information processing device includes: if the vulnerability layer does not originate from the base image, identifying the vulnerability layer as originating from a subsequently installed library; It was configured as follows: Container vulnerability remediation system.

6. 2. The container vulnerability correction system according to claim 1, The information processing device includes: Based on the vulnerability identification information, it is determined whether or not the cause is in a library, and if the cause is not in the library, it is determined whether or not the vulnerability layer is derived from the base image; if the vulnerability layer does not originate from the base image, identifying configuration files having vulnerabilities and analyzing the identified configuration files; It was configured as Container vulnerability remediation system.

7. 3. The container vulnerability correction system according to claim 2, The information processing device includes: From the options of vulnerability remediation methods, register an ideal vulnerability remediation method that has been found to have an unresolved vulnerability as a result of the test and that can resolve the vulnerability in the future; Implementing the vulnerability remediation method as a provisional measure, the method being tested to have resolved the vulnerability; Thereafter, when it is detected that the ideal vulnerability remediation method is executable, the ideal vulnerability remediation method is executed. It was configured as follows: Container vulnerability remediation system.

8. 3. The container vulnerability correction system according to claim 2, The information processing device includes: Predetermining a priority order of the vulnerability remediation methods of the options; remediating and testing vulnerabilities according to said vulnerability remediation methods in said prioritized order; It was configured as follows: Container vulnerability remediation system.

9. 3. The container vulnerability correction system according to claim 2, A display device capable of displaying an image is provided, The information processing device includes: displaying, on the display device, a GUI screen including information indicating a test result of the vulnerability remediation method and a button to be operated to apply the corresponding vulnerability remediation method; It was configured as follows: Container vulnerability remediation system.

10. The container vulnerability correction system according to claim 7, A display device capable of displaying an image is provided, The information processing device includes: displaying, on the display device, a GUI screen including information showing a test result of the vulnerability remediation method, a button operated to apply the corresponding vulnerability remediation method, and a button operated to register the corresponding vulnerability remediation method as the ideal vulnerability remediation method; It was configured as follows: Container vulnerability remediation system.

11. 2. The container vulnerability correction system according to claim 1, The information processing device includes: Identifying a container image corresponding to the vulnerability identification information based on information in which container identification information and container image identification information are associated with each other; Identifying a path of a container construction script corresponding to the identified container image based on information associating a container image with a path of a container construction script; Obtaining the container construction script using the identified path of the container construction script. It was configured as follows: Container vulnerability remediation system.

12. A container vulnerability correction method using an information processing device that acquires information about a container or a container image, By the information processing device, Obtaining vulnerability identification information that indicates a container or container image having a vulnerability and a vulnerability layer that is a layer having a vulnerability; Based on the vulnerability identification information, a container image for creating a container including the vulnerability layer or a container construction script for creating a container image including the vulnerability layer is obtained, and a method for creating the vulnerability layer is identified by analyzing the container construction script, and a vulnerability fixing method option is proposed according to the identified method for creating the vulnerability layer. How to fix container vulnerabilities.

Citation Information

Patent Citations

  • An automated system for resolving computer vulnerabilities

    JP2005532606A