System and method for event log review

• US 20070179986A1
• Filed: 09/22/2006
• Published: 08/02/2007
• Est. Priority Date: 09/23/2005
• Status: Active Grant

• Current Assignee: Barclays Capital Incorporated (Barclays PLC)
• Original Assignee: Lehman Brothers Incorporated (Barclays PLC)
• Inventors: Adam, Christian
• Granted Patent: US 8,402,002 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 21/552 involving long-term monitoring or reporting
• CPC Class Codes: G06F 2221/2101 Auditing as a secondary aspect
• CPC Class Codes: G06F 2221/2151 Time stamp
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: H04L 63/1425 Traffic logging, e.g. anomaly detection

Abstract

An event log management system includes an event log source to generate event log data associated with an asset of an electronic network, an event log database to store the event log data, an asset database to store asset information, and a log report generator to package the event log data into a log report based on the asset information stored in the asset database.

Claims

1. A system, comprising:

an event log source to generate event log data associated with an asset of an electronic network;

an event log database to store the event log data;

an asset database to store asset information; and

a log report generator to package the event log data into a log report based on the asset information stored in the asset database.

2. The system of claim 1, wherein the log report generator packages the event log data according to asset name.

3. The system of claim 1, wherein the log report generator packages the event log data according to asset type.

4. The system of claim 1, further comprising a report archive database to store the log report.

5. The system of claim 4, wherein the report archive database further stores metadata related to the log report including at least one of an issue time of the report, a name of a reviewer, a name of the report, and a count of events to be reviewed in the report.

6. The system of claim 1, further comprising a review monitor to track a review status of the log report.

7. The system of claim 6, wherein the review monitor further includes a portal to access the log report to be reviewed.

8. The system of claim 7 wherein the portal is either an internet portal or an intranet portal.

9. The system of claim 6, wherein the review monitor further includes an electronic notification to notify a reviewer of the log report to be reviewed.

10. The system of claim 9, wherein the reviewer is an asset manager designated in the asset database.

11. The system of claim 6, wherein the review monitor includes an electronic ticket to track the review status of the log report.

12. The system of claim 6, wherein the review monitor includes a user interface to escalate the log report for further review.

13. The system of claim 6, wherein the review monitor notifies a reviewer of delinquency of a review if the log report is not reviewed within a predetermined time period.

14. The system of claim 1, further comprising a report tracking database to store a review status of the log report.

15. The system of claim 14, wherein the review status includes at least one of a first time stamp of when availability of the log report is communicated to a reviewer, a period of time covered by the log report, a second time stamp of when the log report is reviewed, and an escalation of the log report for further review.

16. A method comprising the steps of:

generating event log data associated with an asset of an electronic network;

storing the event log data in an event log database;

storing asset information in an asset database; and

packaging the event log data into a log report based on the asset information stored in the asset database.

17. The method of claim 16, further comprising the step of packaging the event log data according to asset name.

18. The method of claim 16, further comprising the step of packaging the event log data according to asset type.

19. The method of claim 16, further comprising the step of storing the log report in a report archive database.

20. The method of claim 19, wherein the step of storing the log report includes storing metadata related to the log report including at least one of an issue time of the report, a name of a reviewer, a name of the report, and a count of events to be reviewed in the report.

21. The method of claim 16, further comprising the step of tracking a review status of the log report.

22. The method of claim 16, further comprising the step of accessing a portal to review the log report.

23. The method of claim 22, wherein the portal is either an internet portal or an intranet portal.

24. The method of claim 16, further comprising the step of notifying a reviewer of the log report to be reviewed.

25. The method of claim 24, wherein the reviewer is an asset manager designated in the asset database.

26. The method of claim 16, further comprising the step of escalating the log report for further review.

27. The method of claim 16, further comprising the steps of determining if a predetermined period of time has past without the log report being reviewed, and notifying a reviewer if a review of the log report is delinquent.

28. The method of claim 16, further comprising the step of storing a review status of the log report in a report tracking database.

29. The method of claim 28, wherein the review status includes at least one of a first time stamp of when availability of the log report is communicated to a reviewer, a period of time covered by the log report, a second time stamp of when the log report is reviewed, and an escalation of the log report for further review.