Container vulnerability correction system and container vulnerability correction method

The container vulnerability remediation system efficiently addresses the challenge of identifying and correcting vulnerabilities in container images by analyzing the construction script and determining the layer's origin, providing targeted remediation options to enhance system security.

WO2024247664A1PCT designated stage expired Publication Date: 2024-12-05HITACHI LTD
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
PCT/JP2024/017448
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-26
Filing Date
2024-05-10
Publication Date
2024-12-05

AI Technical Summary

Technical Problem

Existing systems face challenges in quickly and effectively addressing vulnerabilities in container images by determining the origin of vulnerable layers, making it difficult to propose appropriate remediation methods.

Method used

A container vulnerability remediation system that uses an information processing device to detect vulnerabilities, identify the vulnerable layer, and analyze the container construction script to determine the creation method of the layer, thereby providing options for targeted vulnerability correction based on the layer's origin.

Benefits of technology

Enables appropriate and efficient vulnerability remediation by identifying the creation method of the vulnerable layer and offering tailored correction methods, reducing the time required to address system security risks.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure JP2024017448_05122024_PF_FP_ABST
    Figure JP2024017448_05122024_PF_FP_ABST
Patent Text Reader

Abstract

This container vulnerability correction system acquires, on the basis of vulnerability identification information, a container image for creating a container including a vulnerability layer or a container construction script for creating the container image including the vulnerability layer. The container vulnerability correction system identifies a creation method of the vulnerability layer by analyzing the container construction script and proposes an option of the vulnerability correction method according to the creation method of the identified vulnerability layer.
Need to check novelty before this filing date? Find Prior Art

Description

Container vulnerability correction system and container vulnerability correction method

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

[0002] The security risks of systems are increasing year by year. In order to provide safe and secure systems, it is essential to quickly address these vulnerabilities. Patent Document 1 discloses an automated system for resolving computer vulnerabilities.

[0003] Special Publication No. 2005-532606

[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 depending on 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-mentioned problems. That is, one of the objects of the present invention is to provide a container vulnerability remediation system and a container vulnerability remediation method that, when a vulnerability is found in a container on a system or a container image in a registry (repository), can propose an appropriate vulnerability remediation method according to the origin of the vulnerable layer of the container or container image.

[0006] In order to solve the above problem, the container vulnerability repair system of the present invention is a container vulnerability repair system that includes an information processing device that acquires information about a container or a container image, and the information processing device is configured to acquire vulnerability identification information that indicates a container or container image that has a vulnerability and a vulnerability layer that is a layer that has a vulnerability, acquire a container image for creating a container that includes the vulnerability layer or a container construction script for creating a container image that includes 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 about a container or a container image, and the information processing device acquires vulnerability identification information indicating a container or container image that has a vulnerability and a vulnerability layer that is a layer that has a vulnerability, and based on the vulnerability identification information, acquires a container image for creating a container that includes the vulnerability layer or a container construction script for creating a container image that includes the vulnerability layer, and analyzes the container construction script to identify a method for creating the vulnerability layer and propose options for vulnerability repair methods according to the identified method for creating the vulnerability layer.

[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), an appropriate vulnerability remediation method can be proposed according to the origin of the vulnerable layer of the container or container image. Note that the effects described herein are not necessarily limited to those described herein and may be any of the effects described in this disclosure.

[0009] FIG. 1 is a diagram illustrating an overview of a container vulnerability automatic remediation system according to a first embodiment of the present invention. FIG. 2 is a block diagram illustrating an example of the configuration of a system including the container vulnerability automatic remediation system according to the first embodiment of the present invention. FIG. 3 is a block diagram illustrating an example of the configuration of a computer on which the components shown in FIG. 2 operate. FIG. 4 is a block diagram illustrating 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 remediation system. FIG. 5 is a diagram illustrating container-container image correspondence management information. FIG. 6 is a diagram illustrating container image-container construction script correspondence management information. FIG. 7 is a diagram illustrating vulnerability remediation option information. FIG. 8 is a diagram illustrating the difficulty of identifying a method for creating a layer that has vulnerabilities. FIG. 9 is a flowchart illustrating the processing flow executed by the vulnerability remediation option extraction unit. FIG. 10 shows an example of a vulnerability remediation result screen displayed by the vulnerability remediation result presentation unit. FIG. 11 is a flowchart illustrating the processing flow executed by the vulnerability remediation option extraction unit. FIG. 12 is a flowchart illustrating the processing flow executed by the vulnerability remediation option extraction unit. FIG. 13 is a diagram illustrating an overview of a container vulnerability automatic remediation system according to a second embodiment of the present invention. 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 repair system. Fig. 15 is a diagram for explaining an example of provisional measure information. Fig. 16 shows an example of a vulnerability repair result screen displayed by the vulnerability repair result presentation unit. Fig. 17 is a flowchart showing the processing flow executed by the ideal measure re-execution unit of the container vulnerability automatic repair system.

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

[0011] In the following description, various types of information may be described using expressions such as "record," but the various types of information may also be expressed using other data structures. When describing identification information, expressions such as "ID," "name," and "name" are used, but these are interchangeable. In the following description, processing may be described using a program or function block as the subject, but the subject of the processing may be a CPU or device instead of a program or function block.

[0012] <<First Embodiment>> <Overview> A description will 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 the vulnerability check tool 200.

[0014] The vulnerability check tool 200 scans containers and / or container images stored in the 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 remediation system 100. A 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 description. The container ID / name information includes identification information of the container. The layer ID includes the ID of the layer in which the vulnerability exists. The vulnerability description includes information indicating the vulnerability description.

[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 the container deployment management system 500, the development management system 600, and the 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 construction script 710 and a configuration file 720 .

[0021] As will be described in detail later, upon receiving a vulnerability detection notification, the container vulnerability automatic remediation system 100 acquires vulnerability identification information 210 from the vulnerability check tool 200, and then 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 vulnerable library 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 fix the root cause of the vulnerability by repeating the above operation. Furthermore, the container vulnerability automatic remediation system 100 can identify packages that need to be updated by identifying the command that installed the vulnerable library.

[0023] <Configuration> Fig. 2 is a block diagram showing an example of the configuration of a system including a container vulnerability automatic remediation system 100 according to a first embodiment of the present invention. As shown in Fig. 2, the system includes the container vulnerability automatic remediation 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 via a network NW1 so as to be able to send and receive information to and from each other. The package management server 800 has a library.

[0024] (Explanation of Computer) 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] The CPU 3010 executes programs stored in the memory 3020 to realize predetermined functions of each computer 3000. The memory 3020 stores the programs executed by the CPU 3010 and data necessary for executing the programs. The programs are loaded into the memory 3020 from the 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 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 function as the input / output device 3040 may be connected to the computer 3000. Each component may be configured from multiple computers 3000. For convenience, the computer 3000 may also be referred to as an "information processing device."

[0028] 4 is a block diagram showing an example of programs and data stored in the memory or storage device 4000 of the terminal TR1 used by the user Us1 and the memory or storage device 4100 of the container vulnerability automatic remediation 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 remediation system 100 includes a vulnerability detection notification receiving unit 110, a vulnerability remediation option extraction unit 120, a vulnerability remediation unit 130, a testing unit 140, a vulnerability remediation result presentation unit 150, and a vulnerability remediation result application unit 160. The vulnerability detection notification receiving unit 110, the vulnerability remediation option extraction unit 120, the vulnerability remediation unit 130, the testing unit 140, the vulnerability remediation result presentation unit 150, and the vulnerability remediation 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 container 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 the 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-based information (records). Specifically, the container ID or name 511 stores an ID or name that is identification information for identifying the 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 illustrating 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 row-based information (records). 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] 7 is a diagram illustrating the vulnerability remediation option information 121. As shown in FIG. 7, the vulnerability remediation option information 121 includes, as columns for storing information (values), a vulnerability remediation option 121a, a vulnerability existing layer creation method 121b, and a priority 121c. The vulnerability existing layer creation method 121b includes, as sub-columns for storing information, a base image 121d and an original 121e.

[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 (circle) indicating options that can be taken when the vulnerability existing layer (also referred to as a "vulnerability layer") is a layer created from a base image. The vulnerability remediation option corresponding to "circle" 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 (circle) indicating options that can be taken when the vulnerability existing layer is a layer created from an original. The vulnerability remediation option corresponding to "circle" is an option that can be taken when the vulnerability existing layer is a layer created from an original.

[0037] <Overview of Operation> Figure 8 is a diagram illustrating 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 a container created from the container image IMG1). Therefore, even if a vulnerable layer of the container (or container image IMG1) can be identified, it is difficult to propose (determine) an appropriate vulnerability remediation method.

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

[0040] The container vulnerability automatic remediation system 100 presents (proposes) 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 the vulnerable container (or container image) by being selected by the user.

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

[0042] (Vulnerability Detection Notification Receiving Unit) The vulnerability detection notification receiving unit 110 receives vulnerability identification information 210 from the vulnerability check tool 200 and accepts a vulnerability detection notification.

[0043] 9 is a flowchart showing the processing flow executed by the vulnerability fix option extraction unit 120. The vulnerability fix option extraction unit 120 starts processing from step 900, and after sequentially executing the processing of steps 905 to 925 described below, temporarily ends this processing flow.

[0044] Step 905: When the vulnerability detection notification receiving unit 110 receives the vulnerability identification information 210, the vulnerability fix option extracting unit 120 identifies a layer including a vulnerability based on the vulnerability identification information 210. Furthermore, the vulnerability fix 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 of the container construction script file) of the image containing the vulnerability corresponding to the identified container image and container image tag.

[0046] Step 915: The vulnerability fix option extractor 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 containing 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 extractor 120 determines a response policy according to the installation source based on the vulnerability fix option information 121.

[0049] (Vulnerability Correction Unit) The vulnerability correction unit 130 executes the determined option (selected vulnerability correction method) and corrects the vulnerability.

[0050] (Testing Unit) The testing unit 140 tests whether the vulnerability has been fixed and whether the application operates normally for each response policy (option (vulnerability fix method)) determined by the vulnerability fix option extraction unit 120.

[0051] In this case, the testing unit 140 may perform vulnerability remediation and testing using the determined vulnerability remediation methods in the order stored in the priority column 121c of the vulnerability remediation option information 121. This allows user Us1 to immediately apply a high-priority option, even if vulnerability remediation and testing for all options is not completed (if there are no problems after completion), without waiting for the results of vulnerability remediation and testing for other lower-priority options, thereby shortening the time required to complete vulnerability remediation. User Us1 may input information indicating the priority levels corresponding to vulnerability remediation options into the container vulnerability automatic remediation system 100 via the input / output device 3040, so that the priority levels are stored (registered) in the priority column 121c.

[0052] (Vulnerability fix result presentation unit) The vulnerability fix result presentation unit 150 presents multiple fix options, whether or not they resolve the vulnerability, and the application test results to the administrator (user Us1), allowing the administrator to select the desired fix method.

[0053] 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 apply fix button 1004, a second apply fix button 1005, and a do not apply fix 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 the vulnerability remediation method, the vulnerability solution, and the test results. The first apply fix button 1004 and the 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 do 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 remediation result application unit) The vulnerability remediation result application unit 160 creates a container (or container image) to which a vulnerability remediation method has been applied in accordance with the administrator (user Us1)'s selection of vulnerability remediation options, and deploys it to the monitored system 300 or registers it in the container image registry / repository 400.

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

[0058] If the cause is in the library, the vulnerability fix option extracting unit 120 determines "YES" in step 1105 and executes the processes of steps 1110 to 1125 described below in order.

[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 it is possible to identify the registry from the base image name.

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

[0062] Step 1125: The vulnerability fix option extractor 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 extracting unit 120 proceeds to step 1030 and determines whether the layer ID having the vulnerability is included in the layers that make up the base image.

[0064] If the layer ID having the vulnerability is not included in the layers that make up the base image, the vulnerability fix 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 extractor 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 the 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 extractor 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 using a base image and a unique command. In this case, the vulnerability fix option extraction unit 120 determines "NO" in step 1150 and proceeds to step 1155 to determine whether the container construction script 710 of the base image can be acquired.

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

[0072] If the container construction script 710 for the base image can be acquired, the vulnerability fixation 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. The vulnerability fixation option extraction unit 120 then executes appropriate processing from step 1110 to step 1155 for the newly acquired container construction script 710. This allows the vulnerability fixation option extraction unit 120 to search for the boundary between the base image and the independently created original image for the base image confirmed in the previous processing.

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

[0074] 12 is a flowchart showing the 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 extractor 120 identifies the registry in which the base image is stored from the base image name.

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

[0078] Step 1225: The vulnerability fix option extractor 120 checks the layer configuration of the base image to identify the layers that make up the base image.

[0079] Thereafter, the vulnerability fix option extracting unit 120 proceeds to step 1225 and determines whether the layer ID having the vulnerability is included in the layers that make up the base image.

[0080] If the layer ID having the vulnerability is not included in the layers that make up the base image, the vulnerability fix 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 and temporarily terminates this processing flow.

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

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

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

[0084] If the layer ID containing the vulnerability is included in a layer that constitutes the base image, the vulnerability fix option extraction unit 120 judges "YES" in step 1225 and proceeds to step 1245, identifies that the vulnerability originates from the base image, and proceeds to step 1250, where it determines 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 extractor 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 using a base image and a unique command. In this case, the vulnerability fix option extraction unit 120 determines "NO" in step 1250 and proceeds to step 1255 to determine whether the container construction script 710 of the base image can be acquired.

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

[0088] If the container construction script 710 of the base image can be acquired, the vulnerability fixation option extraction unit 120 determines "YES" in step 1255 and proceeds to step 1260 to acquire a new container construction script 710, and then returns to step 1255. The vulnerability fixation option extraction unit 120 then executes appropriate processing from step 1210 to step 1255 for the newly acquired container construction script 710. This allows the vulnerability fixation option extraction unit 120 to search for the boundary between the base image and the independently created original image for the base image confirmed in the previous processing.

[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 creation 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 a resource configuration file 720 used when building a container based on the container building script 710 used to create the 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) for a vulnerability caused by the resource configuration contents.

[0091] Furthermore, if a vulnerability is contained in a base image, the container vulnerability automatic remediation system 100 of the first embodiment determines whether the base image can be updated by user Us1 (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 remediation system 100 according to the first embodiment repeatedly acquires and analyzes the container construction script 710 used when the base image was created, searching for the root cause of the vulnerability, as long as it is within the management scope of those belonging to a specific group including user Us1. The container vulnerability automatic remediation system 100 according to the first embodiment then terminates processing when the base image is no longer within the management scope of those belonging to the specific group including user Us1, or when the command that installed the vulnerable library is identified. In this way, the container vulnerability automatic remediation system 100 according to the first embodiment can search for the root cause of the vulnerability and remediate the vulnerability from the root.

[0093] <<Second Embodiment>> A container vulnerability automatic remediation system 100 according to a second embodiment of the present invention will be described. Fig. 13 is a diagram for explaining an overview 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 repair system 100 includes a provisional measure information construction unit 170 and an ideal measure re-execution unit 180 .

[0095] The following description will focus on this difference.

[0096] (Explanation of data configuration of memory or storage device) Figure 14 is a block diagram showing an example of programs and data stored in the memory or storage device 4000 of the terminal TR1 used by user Us1 and the 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 the 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 testing unit 140, a vulnerability fix result presenting unit 150, a vulnerability fix result applying unit 160, a provisional measure information composing unit 170, and an ideal measure re-executing unit 180. Note that 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 are configured by programs stored in the memory or storage device 4100.

[0099] The memory or storage device 4100 of the container 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] 15 is a diagram illustrating 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 subcolumns 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 for each layer. The base image information 1509 stores information about 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 correction method 1506 stores information indicating the ideal measure.

[0102] <Operation> The following describes 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, and therefore descriptions thereof will be omitted.

[0103] (Vulnerability fix result presentation unit) The vulnerability fix result presentation unit 150 presents multiple fix options, whether or not the options resolve the vulnerability, and the application test results to the administrator (user Us1), allowing the administrator (user Us1) to select a desired fix method. Furthermore, the vulnerability fix result presentation unit 150 displays a GUI screen that allows user Us1 to select whether or not to save ideal measures that do not currently resolve the vulnerability but may potentially resolve the vulnerability in the future as ideal measures.

[0104] 16 shows an example of a vulnerability fix result screen 1600, which is a GUI screen displayed by the vulnerability fix result presentation unit 150. As shown in Fig. 16, the vulnerability fix result screen 1600 includes vulnerability container information 1601, cause information 1602, test result information 1603, a first fix apply button 1604, a second fix apply button 1605, a first ideal measure save button 1606, a second ideal measure save button 1607, and a fix not apply 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 results. The first apply fix button 1604 and the 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 user Us1 operates the first ideal measure save button 1606, the vulnerability remediation method corresponding to that button is saved as an ideal measure (ideal remediation method).When the user Us1 operates the second ideal measure save button 1607, the vulnerability remediation method corresponding to that button is saved as an ideal measure (ideal remediation method).

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

[0109] When the user Us1 operates the non-application button 1006, the vulnerability remediation method corresponding to that button is not applied and is not implemented.

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

[0111] (Temporary Measure Information Composition Unit) The temporary measure information composition unit 170 composes (creates) the temporary measure information 1500 based on input to the vulnerability fix result screen 1600 .

[0112] (Ideal Measure Re-execution Unit) FIG. 17 is a flowchart showing the processing 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 (that the vulnerability can be corrected) by periodically checking base image updates, 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 displays the test results on the vulnerability fix result presentation unit 150. At this time, the ideal measure re-execution unit 180 may cause the vulnerability fix result presentation unit 150 to display a screen including information indicating that the provisional measures are no longer necessary on the 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 subsequently becomes effective, 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 the cause of a vulnerability exists in a base image, but the vulnerability has not yet been fixed in the latest version of the base image, so updating the base image is not possible, and as a temporary solution, the library is updated directly using the 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 remediation system 100 of the second embodiment periodically checks for base image updates, and when a vulnerability-fixed version of the base image is released, notifies the administrator (user U1) along with the test results of using it to make corrections, so that when a more desirable, ideal remediation method becomes available to remediate the vulnerability, the system can remediate the vulnerability using that ideal remediation 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 processing flow shown in the flowchart of FIG. 11 and the processing 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 a vulnerable container (or container image), it is possible to propose an appropriate vulnerability remediation method (options for vulnerability remediation methods) for a vulnerable container (or container image).

[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 construction unit, 180...ideal measure re-execution 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 repair system including an information processing device that acquires information regarding a container or a container image, wherein 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.

2. A container vulnerability remediation system as described in claim 1, wherein the information processing device is configured to remediate and test vulnerabilities using the vulnerability remediation method of the proposed option.

3. A container vulnerability repair system as described in claim 2, wherein the information processing device is configured to: analyze the container construction script to determine whether the vulnerability layer originates from a base image or otherwise, and to suggest options for a method of repairing the vulnerability according to the determination result.

4. In the container vulnerability repair system described in claim 3, the information processing device is configured to: when the vulnerability layer is derived from the base image, determine whether the registry of the base image is a public registry, and if the registry of the base image is the public registry, terminate the analysis; and if the registry of the base image is not the public registry and the container construction script is obtainable, obtain the obtainable container construction script and analyze the obtained container construction script.

5. A container vulnerability repair system as described in claim 4, wherein the information processing device is configured to: if the vulnerability layer does not originate from the base image, determine that the vulnerability layer originates from a library that was installed later.

6. A container vulnerability repair system as described in claim 1, wherein the information processing device is configured to: determine whether or not the cause lies in a library based on the vulnerability identification information; if the cause is not in the library, determine whether or not the vulnerability layer originates from the base image; and if the vulnerability layer does not originate from the base image, identify a configuration file having a vulnerability and analyze the identified configuration file.

7. A container vulnerability remediation system as described in claim 2, wherein the information processing device is configured to: register, from among the alternative vulnerability remediation methods, an ideal vulnerability remediation method for which testing has shown that the vulnerability remains unresolved and which can resolve the vulnerability in the future; execute, as a temporary measure, the vulnerability remediation method for which testing has shown that the vulnerability has been resolved; and thereafter, when it detects that the ideal vulnerability remediation method has become executable, execute the ideal vulnerability remediation method.

8. A container vulnerability remediation system as described in claim 2, wherein the information processing device is configured to: pre-set a priority order for the optional vulnerability remediation methods; and remediate and test vulnerabilities using the vulnerability remediation methods in an order according to the priority order.

9. A container vulnerability remediation system as described in claim 2, further comprising a display device capable of displaying images, wherein the information processing device is configured to display on the display device a GUI screen including information indicating test results of the vulnerability remediation method and a button to be operated to apply the corresponding vulnerability remediation method.

10. A container vulnerability repair system as described in claim 7, further comprising a display device capable of displaying images, wherein the information processing device is configured to display on the display device a GUI screen including information indicating test results of the vulnerability repair methods, a button that is operated to apply the corresponding vulnerability repair method, and a button that is operated to register the corresponding vulnerability repair method as the ideal vulnerability repair method.

11. In the container vulnerability repair system described in claim 1, the information processing device is configured to: identify a container image corresponding to the vulnerability identification information based on information correlating container identification information with container image identification information; identify a path of a container construction script corresponding to the identified container image based on information correlating container images with paths of a container construction script; and obtain the container construction script using the identified path of the container construction script.

12. A container vulnerability repair method using an information processing device that acquires information about a container or a container image, comprising the steps of: acquiring vulnerability identification information indicating a container or container image having a vulnerability, and a vulnerability layer that is a layer having a vulnerability, using the information processing device; acquiring 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; analyzing the container construction script to identify a method for creating the vulnerability layer; and proposing options for vulnerability repair methods according to the identified method for creating the vulnerability layer.

Citation Information

Patent Citations

  • Container mirror image security scanning and repairing method, device and equipment

    CN113642004A

  • Verification device and verification method

    JP2019056986A

  • Container image verification device, container image verification method, and container image verification program

    JP2020154861A

  • Processing device and processing method

    JP7086261B1