The present invention relates generally to a Linux container infrastructure, and more particularly to a security fix of a container in a VM (virtual machine) environment.
More and more companies providing hosting and cloud services are adopting Linux container solutions. The Linux container solutions are emerging cloud technology based on fast and lightweight process virtualization that provides users with an environment as close as possible to a standard Linux distribution. Due to the fact that containers are lightweight compared to VMs, more instances of containers can be deployed than VMs on a host and in less time.
One of the main constraints is poor isolation between containers. Since containers share the same kernel as the host, all infrastructure will be vulnerable to kernel exploits, and malicious code may put the whole environment in danger. For example, Shocker is a malicious code that lets a Docker container access any file on a host, including sensitive information; this compromises security of the host and any other Docker containers on the host. The problem regarding the isolation between containers is still an open problem to the IT industry.
In one aspect, a method for a security fix of a container in a VM (virtual machine) environment is provided. The method is implemented by a computer. The method includes detecting a container in a container environment. The method further includes determining whether the container has a security issue. The method further includes performing live migration of the container to a created VM. The method further includes fixing the security issue of the container in the created VM. The method further includes determining whether the security issue is fixed. The method further includes performing live migration of the created VM to the container environment, in response to determining that the security issue is fixed.
In another aspect, a computer program product for a security fix of a container in a VM (virtual machine) environment is provided. The computer program product comprises a computer readable storage medium having program code embodied therewith. The program code executable to: detect a container in a container environment; determine whether the container has a security issue; perform live migration of the container to a created VM; fix the security issue of the container in the created VM; determine whether the security issue is fixed; and perform live migration of the created VM to the container environment, in response to determining that the security issue is fixed.
In yet another aspect, a computer system for a security fix of a container in a VM (virtual machine) environment is provided. The computer system comprises one or more processors, one or more computer readable tangible storage devices, and program instructions stored on at least one of the one or more computer readable tangible storage devices for execution by at least one of the one or more processors. The program instructions are executable to detect a container in a container environment. The program instructions are executable to determine whether the container has a security issue. The program instructions are executable to perform live migration of the container to a created VM. The program instructions are executable to fix the security issue of the container in the created VM. The program instructions are executable to determine whether the security issue is fixed. The program instructions are executable to perform live migration of the created VM to the container environment, in response to determining that the security issue is fixed.
Embodiments of the present invention disclose an automated method for identification, isolation, and fixing of problems in a given container infrastructure. By taking advantage of isolation of a VM environment and information about the inventory of all system and data hosted on a Linux container infrastructure, the automated management process guarantees that a container is working properly or is isolated awaiting for manual maintenance.
In embodiments of the present invention, the automated method is used to guarantee that a given container works properly or is isolated from the rest of the infrastructure; therefore, the automated method guarantee that the container does not exploit any security and/or performance flaws due to a kernel issue or the lack of properly configuration of the container. For example, in the Shocker issue mentioned previously in this document, a container running the malicious code can be separated from a container infrastructure, by creating a VM and performing live migration of the container to the VM. The security fix is then applied to the container in the VM environment, and then the container is reinstated in the original host—the container infrastructure.
A container is migrated to a VM when there is one of the following problems, for example: (1) a monitoring tool detects some potential security flaws in a container infrastructure, (2) there is performance hassling (e.g., disk I/O problems) in the container, and (3) an application in the container does not behave well. While in a VM environment, an apparatus runs some more detailed tests, in an automated fashion. It fixes one or more problems if possible and then moves the VM snapshot back to the container. If the one or more problems persist, the VM is hold on quarantine and waits for human intervention.
Embodiments of the present invention increase security by monitoring and isolating problematic containers, minimize wasting of human efforts in events of massive flaws of containers in a Linux based container environment, and expedite the procedures to recover containers that are not working properly. The main goal of the automated method is to minimize human intervention while keeping a high degree of confidence that the Linux based container environment is taken care of.
System 100 further comprises central agent 170. Central Agent 170 takes action based on reports provided by intrusion detection system 1 (115), intrusion detection system 2 (125), and intrusion detection system 3 (135). Central agent 170 hosts a security database of known security issues including malware, virus, and known bugs. Central agent 170 continuously monitors a plurality of containers against the security database. Central agent 170 maintains an affected group which includes affected containers that have security issues and need to be migrated to respective VMs. In the embodiment shown in
The following is the process continuously running by central agent 170.
At step 240, central agent 170 performs live migration of the affected containers in the affected group to respective created VMs and destroys the affected containers. At step 250, central agent 170 adds the respective created VMs to a list of VMs. Steps 240 and 250 are described in the second block of the pseudo code presented in the previous paragraph.
At step 260, central agent 170 fixes security issues in the respective created VMs. At step 270, central agent 170 determines whether a respective one of the created VMs is fixed. In response to determines that the respective one of the created VMs is fixed (YES branch of step 270), at step 280, central agent 170 performs live migration of a snapshot of the respective one of the created VMs to the container environment and destroys the respective one of the created VMs. In response to determines that the respective one of the created VMs is not fixed (NO branch of step 270) or the security issues are persistent, at step 280, central agent 170 adds the respective one of the created VMs to quarantine waiting for human intervention. Steps 260-280 are described in the third block of the pseudo code presented in the previous paragraph.
Referring to
The present invention may be a system, a method, and/or a computer program product. The computer program product may include a computer readable storage medium (or media) having computer readable program instructions thereon for causing a processor to carry out aspects of the present invention.
The computer readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device. The computer readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of the computer readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device, such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing. A computer readable storage medium, as used herein, is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire.
Computer readable program instructions described herein can be downloaded to respective computing/processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network (LAN), a wide area network (WAN), and/or a wireless network. The network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. A network adapter card or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing/processing device.
Computer readable program instructions for carrying out operations of the present invention may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C++, and conventional procedural programming languages, such as the “C” programming language, or similar programming languages. The computer readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer, or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). In some embodiments, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry in order to perform aspects of the present invention.
Aspects of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer readable program instructions.
These computer readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, a programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable storage medium having instructions stored therein comprises an article of manufacture, including instructions which implement aspects of the function/act specified in the flowchart and/or block diagram block or blocks.
The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus, or other device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions/acts specified in the flowchart and/or block diagram block or blocks.
The flowchart and block diagrams in the FIGs illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the block may occur out of the order noted in the FIGs. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts or carry out combinations of special purpose hardware and computer instructions.
Number | Name | Date | Kind |
---|---|---|---|
8296759 | Hutchins | Oct 2012 | B1 |
8312043 | van Riel et al. | Nov 2012 | B2 |
8464104 | Ganesh et al. | Jun 2013 | B2 |
8589947 | Potter et al. | Nov 2013 | B2 |
8677004 | Hegde et al. | Mar 2014 | B2 |
8990608 | Gupta et al. | Mar 2015 | B1 |
9104458 | Brandwine | Aug 2015 | B1 |
9378108 | Cohen | Jun 2016 | B2 |
9384029 | Brandwine | Jul 2016 | B1 |
9578017 | Ferguson | Feb 2017 | B2 |
9635055 | Mathur | Apr 2017 | B2 |
9710401 | Rozas | Jul 2017 | B2 |
9729579 | Marino | Aug 2017 | B1 |
9766930 | Tarasuk-Levin | Sep 2017 | B2 |
9766945 | Gaurav | Sep 2017 | B2 |
9819694 | Ponsford | Nov 2017 | B2 |
9886300 | Nakatsu | Feb 2018 | B2 |
10075470 | Vaidya | Sep 2018 | B2 |
20060054682 | de la Huerga | Mar 2006 | A1 |
20070079307 | Dhawan | Apr 2007 | A1 |
20070234337 | Suzuki | Oct 2007 | A1 |
20080082977 | Araujo | Apr 2008 | A1 |
20080163239 | Sugumar | Jul 2008 | A1 |
20090089781 | Shingai | Apr 2009 | A1 |
20090300414 | Huang | Dec 2009 | A1 |
20100009758 | Twitchell, Jr. | Jan 2010 | A1 |
20100094948 | Ganesh et al. | Apr 2010 | A1 |
20110004935 | Moffie | Jan 2011 | A1 |
20110209156 | Box | Aug 2011 | A1 |
20120233282 | Voccio | Sep 2012 | A1 |
20120266147 | Dawson | Oct 2012 | A1 |
20130007090 | Sankararaman | Jan 2013 | A1 |
20130198840 | Drissi | Aug 2013 | A1 |
20130212709 | Tucker | Aug 2013 | A1 |
20130246685 | Bhargava | Sep 2013 | A1 |
20130268799 | Mestery | Oct 2013 | A1 |
20130298184 | Ermagan | Nov 2013 | A1 |
20140096131 | Sonnek | Apr 2014 | A1 |
20140137125 | Hsu | May 2014 | A1 |
20140317677 | Vaidya | Oct 2014 | A1 |
20150040217 | Abuelsaad | Feb 2015 | A1 |
20150052614 | Crowell | Feb 2015 | A1 |
20150154056 | Chen | Jun 2015 | A1 |
20150220358 | Ponsford | Aug 2015 | A1 |
20150237066 | Ponsford | Aug 2015 | A1 |
20150244640 | Ponsford | Aug 2015 | A1 |
20150263983 | Brennan et al. | Sep 2015 | A1 |
20150326588 | Vissamsetty | Nov 2015 | A1 |
20150326592 | Vissamsetty | Nov 2015 | A1 |
20150339146 | Ponsford | Nov 2015 | A1 |
20150378771 | Tarasuk-Levin | Dec 2015 | A1 |
20150378785 | Tarasuk-Levin | Dec 2015 | A1 |
20150378831 | Tarasuk-Levin | Dec 2015 | A1 |
20150378847 | Tarasuk-Levin | Dec 2015 | A1 |
20150379287 | Mathur | Dec 2015 | A1 |
20150381589 | Tarasuk-Levin | Dec 2015 | A1 |
20160098302 | Ben-Yehuda | Apr 2016 | A1 |
20160182567 | Sood | Jun 2016 | A1 |
20160219019 | Mathur | Jul 2016 | A1 |
20160219073 | Mathur | Jul 2016 | A1 |
20160274928 | Linton | Sep 2016 | A1 |
20160283259 | Mehta | Sep 2016 | A1 |
20160283261 | Nakatsu | Sep 2016 | A1 |
20160285958 | Das | Sep 2016 | A1 |
20160292431 | Sreekanti | Oct 2016 | A1 |
20160378563 | Gaurav | Dec 2016 | A1 |
20160378688 | Rozas | Dec 2016 | A1 |
20170034198 | Powers | Feb 2017 | A1 |
20170063722 | Cropper | Mar 2017 | A1 |
20170093923 | Duan | Mar 2017 | A1 |
20170098072 | Stopel | Apr 2017 | A1 |
20170118174 | Mathur | Apr 2017 | A1 |
20170185533 | Rozas | Jun 2017 | A1 |
20170199770 | Peteva | Jul 2017 | A1 |
20170235951 | Harrison | Aug 2017 | A1 |
20170269953 | Prey | Sep 2017 | A1 |
20170270012 | Tarasuk-Levin | Sep 2017 | A1 |
20170272404 | Prey | Sep 2017 | A1 |
20170339018 | Prabhu | Nov 2017 | A1 |
20170366563 | Volfman | Dec 2017 | A1 |
20170373932 | Subramanian | Dec 2017 | A1 |
20170373933 | Subramanian | Dec 2017 | A1 |
20170373935 | Subramanian | Dec 2017 | A1 |
20180004683 | Rozas | Jan 2018 | A1 |
20180007051 | Vij | Jan 2018 | A1 |
20180011699 | Manthiramoorthy | Jan 2018 | A1 |
20180074748 | Makin | Mar 2018 | A1 |
20180157517 | Dong | Jun 2018 | A1 |
20180260574 | Morello | Sep 2018 | A1 |
Entry |
---|
Hamad et al., Secure Live Virtual Machine Migration by Proposed Security Center, IUGNES, Aug. 28, 2015. |
Krahmer, Sebastian, “Docker 0.11—VMM—Container Breakout”, Exploit Database, Published Jun. 18, 2014, 4 pages, <https://www.exploit-db.com/exploits/33808/>. |
Mirkin et al., “Containers checkpointing and live migration”, Proceedings of the Linux Symposium, vol. Two, Jul. 23-26, 2008, Ottawa, Ontario, pp. 85-90. |
“CRIU”, CRIU, released Jun. 14, 2016, 4 pages, <http://criu.org/Main_Page>. |
“How to migrate a container to a virtual machine?”, plesk, Article ID: 117955, created on Oct. 14, 2013, last review on Oct. 20, 2015, 4 pages, <http://kb.plesk.com/en/117955>. |
Number | Date | Country | |
---|---|---|---|
20180053001 A1 | Feb 2018 | US |