Static detection of vulnerabilities in base images of software containers

US10223534B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-10223534-B2
Application numberUS-201615292915-A
CountryUS
Kind codeB2
Filing dateOct 13, 2016
Priority dateOct 15, 2015
Publication dateMar 5, 2019
Grant dateMar 5, 2019

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

A system and method for detecting vulnerabilities in base images of software containers are disclosed. The method includes receiving an event indicating that at least one base image should be scanned for vulnerabilities, each base image including at least one image layer, wherein the event designates at least one source of the at least one base image, wherein the least one base image includes resources utilized to execute at least a software container; extracting contents of each image layer of each base image; scanning the extracting contents to detect at least one vulnerability; and generating a detection event, when the at least one vulnerability is detected.

First claim

Opening claim text (preview).

What is claimed is: 1. A method for detecting vulnerabilities in base images of software containers, comprising: receiving an event indicating that at least one base image should be scanned for vulnerabilities, each base image including at least one image layer, wherein the event designates at least one source of the at least one base image, wherein the least one base image includes resources utilized to execute at least a software container; extracting contents of each image layer of the at least one base image; scanning the extracted contents to detect at least one vulnerability; generating a detection event, when the at least one vulnerability is detected; generating a unitary signature for each layer of the at least one base image when no vulnerability is detected; determining, after saving the unitary signature in a database, if repeated scanning of the at least one base image is required based on the unitary signature generated for each layer of the at least one base image, wherein the contents of each layer are extracted and scanned again when it is determined that repeated scanning is required; and generating a safe event when no vulnerability is detected. 2. The method of claim 1 , wherein generating the unitary signature for each layer of the at least one base image further comprises: computing a check-sum over the contents of each image layer of the at least one base image. 3. The method of claim 1 , wherein generating the unitary signature for each layer of the at least one base image further comprises: computing a hash-function over the contents of each image layer of the at least one base image. 4. The method of claim 1 , further comprising: checking if the at least one base image was previously scanned based on the unitary signature generated for each layer of the at least one base image, wherein the contents of each layer are extracted and scanned to detect the at least one vulnerability for the at least one base image that was not previously scanned. 5. The method of claim 4 , wherein checking if the at least one base image was previously scanned further comprises: comparing the generated unitary signatures of the least one base image to unitary signatures of saved scanned layers of base images from the database. 6. The method of claim 1 , further comprising: exporting the at least one base image from the at least one source to a host device. 7. The method of claim 1 , wherein each of the at least one source includes at least one of: a continuous integration system for base images, a host device and an image registry. 8. The method of claim 1 , wherein extracting the contents of each image layer of the at least one base image further comprises: reformatting the at least one base image into a data structure. 9. The method of claim 8 , wherein the data structure includes at least one of: a file having a standard format, and a filesystem structure. 10. The method of claim 1 , wherein the at least one vulnerability includes at least any one of: malware, a vulnerable software library installed in the at least one base image, and a vulnerable software library installed in the at least one base image. 11. The method of claim 9 , wherein scanning to identify at least malware further comprises: receiving intelligence information, wherein the intelligence information includes at least definitions of malwares; and scanning the extracted contents to identify at least one definition of the at least one type of malware defined in the intelligence information. 12. The method of claim 11 , wherein the malware includes at least one of: previously known malware, and newly discovered malware. 13. The method of claim 11 , wherein scanning to identify a vulnerable software library installed in the at least one base image further comprises: determining an identifier of each software library installed in the at least one base image; and comparing each determined identifier against a list of vulnerable software libraries. 14. The method of claim 11 , wherein scanning to identify a vulnerable software package installed in the at least one base image further comprises: determining an identifier of each software package installed in the at least one base image; and comparing each determined identifier against a list of vulnerable software packages. 15. The method of claim 1 , wherein the generating the detection event further comprises: halting a process of updating the source with the least one base image. 16. The method of claim 1 , wherein the detection of vulnerabilities in base images is performed prior to execution of the at least software container. 17. A host device for detecting vulnerabilities in software containers at runtime, comprising: a processing system; and a memory, the memory containing instructions that, when executed by the processing system, configure the host device to: receive an event indicating that at least one base image should be scanned for vulnerabilities, each base image including at least one image layer, wherein the event designates at least one source of the at least one base image, wherein the least one base image includes resources utilized to execute at least a software container; extract contents of each image layer of the at least one base image; scan the extracted contents to detect at least one vulnerability; generate a detection event, when the at least one vulnerability is detected; and generate a unitary signature for each layer of the at least one base image when no vulnerability is detected; determine, after saving the unitary signature in a database, if repeated scanning of the at least one base image is required based on the unitary signature generated for each layer of the at least one base image, wherein the contents of each layer are extracted and scanned again when it is determined that repeated scanning is required; and generate a safe event when no vulnerability is detected. 18. The host device of claim 17 , wherein the host device is further configured to: compute a check-sum over the contents of each image layer of the each base image. 19. The host device of claim 17 , wherein the host device is further configured to: compute a hash-function over the contents of each image layer of the each base image. 20. The host device of claim 17 , wherein the host device is further configured to: check if the at least one base image was previously scanned based on the unitary signature generated for each layer of the each base image, wherein the contents of each layer are extracted and scanned to detect the at least one vulnerability for the at least one base image that was not previously scanned. 21. The host device of claim 20 , wherein the host device is further configured to: compare the generated unitary signatures of the least one base image to unitary signatures of saved scanned image layers of base images from the database. 22. The host device of claim 17 , wherein the host device is further configured to: export the at least one base image from the at least one source to the host device. 23. The host device of claim 17 , wherein the at least one source includes at least one of: a continuous integration system for base images, the host device and an image registry. 24. The host device of claim 17 , wherein the host device is further configured to: reformat the at least one base image into a data structure. 25. The

Assignees

Inventors

Classifications

  • G06F21/577Primary

    Assessing vulnerabilities and evaluating computer system security · CPC title

  • Test or assess software · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US10223534B2 cover?
A system and method for detecting vulnerabilities in base images of software containers are disclosed. The method includes receiving an event indicating that at least one base image should be scanned for vulnerabilities, each base image including at least one image layer, wherein the event designates at least one source of the at least one base image, wherein the least one base image includes r…
Who is the assignee on this patent?
Twistlock Ltd
What technology area does this patent fall under?
Primary CPC classification G06F21/577. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Mar 05 2019 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 9 related publications on this page (citations in our corpus or others sharing the same primary CPC).