Security patch tool

Patent metadata

Field	Value
Publication number	US-10108482-B2
Application number	US-201615187026-A
Country	US
Kind code	B2
Filing date	Jun 20, 2016
Priority date	Jun 20, 2016
Publication date	Oct 23, 2018
Grant date	Oct 23, 2018

Abstract

A security patch tool includes a retrieval engine, a parser, and a reporting engine. The retrieval engine retrieves, from a first database, a log indicating a plurality of patches that have been applied and whether each patch of the plurality of patches was applied successfully. The parser determines, based on the log, a second plurality of patches of the plurality of patches that were not applied successfully and determines, based on the log, an error code for each patch of the second plurality of patches. The retrieval engine further retrieves, from a second database, a remedy for each error code for each patch of the second plurality of patches. The reporting engine generates a report indicating the plurality of patches, the error code for each patch of the second plurality of patches, and the remedy for each error code for each path of the second plurality of patches.

First claim

What is claimed is:

1. A security patch tool comprising:
a retrieval engine configured to retrieve, from a first database, a log indicating a plurality of patches that have been applied and whether each patch of the plurality of patches was applied successfully;
a parser configured to:
determine, based on the log, that a first patch and a second path of the plurality of patches were not applied successfully; and
determine, based on the log, a first error code indicating that the first patch did not apply successfully because there were insufficient system resources and a second error code indicating that the second patch did not apply successfully because an application was executing, wherein the retrieval engine is further configured to retrieve, from a second database, a first remedy for the first error code and a second remedy for the second error code;

a reporting engine configured to generate a report indicating the plurality of patches, the error code for each patch of the second plurality of patches, and the remedy for each error code for each path of the second plurality of patches; and
a remediation engine configured to:
free up system resources before re-applying the first patch; and
close the application before re-applying the second patch.

2. The security patch tool of claim 1 , wherein the retrieval engine retrieves a log indicating a plurality of patches that have been applied at least once every fifteen minutes.

3. The security patch tool of claim 1 , wherein the parser is further configured to store, in a third database, a log indicating the plurality of patches, the error code for each patch of the second plurality of patches, and the remedy for each error code for each path of the second plurality of patches.

4. The security patch tool of claim 1 , wherein the reporting engine generates the report in response to a received request for the results of applying the first plurality of patches.

5. The security patch tool of claim 1 , wherein the reporting engine is further configured to generate an e-mail message comprising a link to the report.

6. The security patch tool of claim 1 , wherein the log further indicates a plurality of servers, a location for each server of the plurality of servers, and an operating system for each server of the plurality of servers.

7. A method comprising:
retrieving, from a first database, a log indicating a plurality of patches that have been applied and whether each patch of the plurality of patches was applied successfully;
determining, based on the log, that a first patch and a second path of the plurality of patches were not applied successfully;
determining, based on the log, a first error code indicating that the first patch did not apply successfully because there were insufficient system resources and a second error code indicating that the second patch did not apply successfully because an application was executing;
retrieving, from a second database, a first remedy for the first error code and a second remedy for the second error code; and
generating a report indicating the plurality of patches, the error code for each patch of the second plurality of patches, and the remedy for each error code for each path of the second plurality of patches;
freeing up system resources before re-applying the first patch; and
closing the application before re-applying the second patch.

8. The method of claim 7 , further comprising retrieving a log indicating a plurality of patches that have been applied at least once every fifteen minutes.

9. The method of claim 7 , further comprising storing, in a third database, a log indicating the plurality of patches, the error code for each patch of the second plurality of patches, and the remedy for each error code for each path of the second plurality of patches.

10. The method of claim 7 , generating the report is in response to a received request for the results of applying the first plurality of patches.

11. The method of claim 7 , further comprising generate an e-mail message comprising a link to the report.

12. The method of claim 7 , wherein the log further indicates a plurality of servers, a location for each server of the plurality of servers, and an operating system for each server of the plurality of servers.

13. A system comprising:
a first database;
a second database; and
a parser configured to:
determine, based on a log retrieved from the first database, the log indicating a plurality of patches that have been applied and whether each patch of the plurality of patches was applied successfully, that a first patch and a second path of the plurality of patches were not applied successfully; and
determine, based on the log, a first error code indicating that the first patch did not apply successfully because there were insufficient system resources and a second error code indicating that the second patch did not apply successfully because an application was executing, wherein a first remedy for the first error code and a second remedy for the second error code are retrieved from the second database;

a reporting engine configured to generate a report indicating the plurality of patches, the error code for each patch of the second plurality of patches, and a retrieved remedy for each error code for each path of the second plurality of patches; and
a remediation engine configured to:
free up system resources before re-applying the first patch ; and
close the application before re-applying the second patch.

14. The system of claim 13 , wherein the log further indicates a plurality of patches that have been applied at least once every fifteen minutes.

15. The system of claim 13 , wherein the parser is further configured to store, in a third database, a log indicating the plurality of patches, the error code for each patch of the second plurality of patches, and the remedy for each error code for each path of the second plurality of patches.

16. The system of claim 13 , wherein the reporting engine generates the report in response to a received request for the results of applying the first plurality of patches.

17. The system of claim 13 , wherein the reporting engine is further configured to generate an e-mail message comprising a link to the report.

18. The system of claim 13 , wherein the log further indicates a plurality of servers, a location for each server of the plurality of servers, and an operating system for each server of the plurality of servers.

Assignees

• Bank Of America

Inventors

• Kumar Vivek
• Kumar Hitendra
• Kumar Amit
• Bolduc Scott M

Classifications

• G06F8/65

  Updates (security arrangements therefor G06F21/57) · CPC title

• G06F11/0709

  in a distributed system consisting of a plurality of standalone computer nodes, e.g. clusters, client-server systems · CPC title

• G06F11/0772

  Means for error signaling, e.g. using interrupts, exception flags, dedicated error registers · CPC title

• G06F11/0793 Primary

  Remedial or corrective actions (recovery from an exception in an instruction pipeline G06F9/3861; by retry G06F11/1402; for recovering from a failure of a protocol instance or entity H04L69/40) · CPC title

• G06F11/079

  Root cause analysis, i.e. error or fault diagnosis (in a hardware test environment G06F11/22; in a software test environment G06F11/36) · CPC title