IP Library Granted Patent US 8,646,086
Granted Patent B2
US 8,646,086 · App. 12/951,373 · Granted Feb 4, 2014

Image vulnerability repair in a networked computing environment

Inventors: Al Chakra (Apex, NC); Christopher J. Dawson (Arlington, VA); Yu Deng (Yorktown Heights, NY); Rick A. Hamilton, II (Charlottesville, VA); Jenny S. Li (Danbury, CT); Liangzhao Zeng (Mohegan Lake, NY)
Assignee: International Business Machines Corporation
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,646,086
App. No.
12/951,373
Granted
Feb 4, 2014
Kind
B2
Abstract

Embodiments of the present invention provide an approach to repair vulnerabilities (e.g., security vulnerabilities) in images (e.g., application images) in a networked computing environment (e.g., a cloud computing environment). Specifically, an image is checked for vulnerabilities using a database of known images and/or vulnerabilities. If a vulnerability is found, a flexible/elastic firewall is established around the image so as to isolate the vulnerability. Once the firewall has been put in place, the vulnerability can be repaired by a variety of means such as upgrading the image, quarantining the image, discarding the image, and/or generating a new image. Once the image has been repaired, the firewall can be removed.

Claims (39)

1. A method for repairing image vulnerability in a networked computing environment, comprising:

identifying an image in the networked computing environment having a vulnerability, the image being identified based on a database of known vulnerabilities;

establishing a firewall around the image to isolate the vulnerability;

repairing the image to remove the vulnerability, the repairing comprising discarding the image and generating a new image; and

removing the firewall.

2. The method of claim 1 , the image being an application image.

3. The method of claim 1 , the vulnerability being a security vulnerability.

4. The method of claim 1 , the repairing comprising upgrading the image.

5. The method of claim 1 , the repairing comprising quarantining the image.

6. The method of claim 1 , further comprising updating the database based on the repairing.

7. A system for repairing image vulnerability in a networked computing environment, comprising:

a bus;

a processor coupled to the bus; and

a memory medium coupled to the bus, the memory medium comprising instructions to:

identify an image in the networked computing environment having a vulnerability, the image being identified based on a database of known vulnerabilities;

establish a firewall around the image to isolate the vulnerability;

repair the image to remove the vulnerability, the repairing comprising discarding the image and generating a new image; and

remove the firewall.

8. The system of claim 7 , the image being an application image.

9. The system of claim 7 , the vulnerability being a security vulnerability.

10. The system of claim 7 , the memory medium further comprising instructions to upgrade the image.

11. The system of claim 7 , the memory medium further comprising instructions to quarantine the image.

12. The system of claim 7 , the memory medium further comprising instructions to update the database based on the repair.

13. A computer program product for repairing image vulnerability in a networked computing environment, the computer program product comprising a computer readable storage device, and program instructions stored on the computer readable storage media, to:

identify an image in the networked computing environment having a vulnerability, the image being identified based on a database of known vulnerabilities;

establish a firewall around the image to isolate the vulnerability;

repair the image to remove the vulnerability, the repairing comprising discarding the image and generating a new image; and

remove the firewall.

14. The computer program product of claim 13 , the image being an application image.

15. The computer program product of claim 13 , the vulnerability being a security vulnerability.

16. The computer program product of claim 13 , further comprising program instructions stored on the computer readable storage media to upgrade the image.

17. The computer program product of claim 13 , further comprising program instructions stored on the computer readable storage media to quarantine the image.

18. The computer program product of claim 13 , further comprising program instructions stored on the computer readable storage device to update the database based on the repair.

19. A method for deploying a system for repairing image vulnerability in a networked computing environment, comprising:

deploying a computer infrastructure being operable to:

identify an image in the networked computing environment having a vulnerability, the image being identified based on a database of known vulnerabilities;

establish a firewall around the image to isolate the vulnerability;

repair the image to remove the vulnerability, the repairing comprising discarding the image and generating a new image; and

remove the firewall.

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 9, 2018
From: INTERNATIONAL BUSINESS MACHINES CORPORATION
To: FINJAN BLUE, INC.
Reel/Frame 046037/0040 →
CORRECTIVE ASSIGNMENT TO CORRECT THE ASSIGNOR'S NAME PREVIOUSLY RECORDED ON REEL 025391 FRAME 0087. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT OF ASSIGNOR'S INTEREST. Recorded Dec 23, 2010
From: CHAKRA, AL; DAWSON, CHRISTOPHER J.; DENG, YU; HAMILTON, RICK A., II; LI, JENNY S.; ZENG, LIANGZHAO
To: INTERNATIONAL BUSINESS MACHINES CORPORATION
Reel/Frame 025561/0958 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 22, 2010
From: CHAKRA, AL; DAWSON, CHRISTOPHER J.; DENG, YU; HAMILTON, RICK A., II; LI, JENNY S.; ZENG, LIANGZHOA
To: INTERNATIONAL BUSINESS MACHINES CORPORATION
Reel/Frame 025391/0087 →
Continuity (1)
Related Publication 20120131677A1 · May 24, 2012