Method and system to process issue data pertaining to a system

Abstract

A method to processes issue data in a system is provided. A rules engine monitors a computer network for a violation of a parameter defined by rules in a database and automatically detects the violation. In response, the rules engine generates an issue report indicating the violation. An issue report is received from a human user indicating a potential violation in the computer network. The issue reports are parsed. Based on data parsed from the issue reports, a determination that a common issue is being reported by both the rules engine and the human user is made. In response, the issue report from the rules engine is reconciled with the issue report from the human user resulting in a single issue entry in an issue queue, whereby the reconciling including incrementing a count for each instance of the common issue being reported.

1 . (canceled) 
     
     
         2 . A system comprising:
 one or more hardware processors; and   a storage device storing instructions that, when executed by the one or more hardware processors, cause the one or more hardware processors to perform operations comprising:
 monitoring a computer network for a violation of a parameter defined by rules in a database; 
 automatically detecting the violation; 
 in response to the automatically detecting, generating, by a rules engine, an issue report indicating the violation; 
 receiving, via a user interface, an issue report from a human user, the issue report from the human user indicating a potential violation in the computer network; 
 parsing the issue report from the rules engine and the issue report from the human user; 
 determining, based on data parsed from the issue reports, that a common issue is being reported by both the rules engine and the human user; and 
 reconciling the issue report from the rules engine with the issue report from the human user resulting in a single issue entry in an issue queue, the reconciling including incrementing a count for each instance of the common issue being reported. 
   
     
     
         3 . The system of  claim 2 , wherein the operations further comprise automatically prioritizing the reconciled issue report by applying to the reconciled issue report a merged issue priority based, at least in part, on a combination of associated priority criterion data, the merged issue priority being based on a merge of a plurality of different priority types. 
     
     
         4 . The system of  claim 3 , wherein the operations further comprise causing performance of a corresponding response activity for the reconciled issue report, the response activity to be performed based on the merged issue priority. 
     
     
         5 . The system of  claim 3 , wherein the priority criterion data comprises visibility data relating to a number of times a respective reported violation has been a subject of an issue report. 
     
     
         6 . The system of  claim 3 , wherein the priority criterion data comprises severity data, the parsing including identifying an issue type associated with a respective issue report to obtain the severity data based on the identified issue type. 
     
     
         7 . The system of  claim 3 . wherein the priority criterion data comprises exposure data relating to a potential loss associated with a respective reported issue, the exposure data comprising an exposure value obtained from a database. 
     
     
         8 . The system of  claim 3 , wherein the priority criterion data comprises performance data indicative of a past performance of a reporting entity associated with a respective issue report, the parsing including identifying the reporting entity and retrieving the performance data from a database. 
     
     
         9 . The system of  claim 3 , wherein the merged issue priority is based on a combination of at least two of: visibility data relating to a number of times a relevant reported violation has been a subject of an issue report; severity data relating to a pre-defined severity of an associated issue type; exposure data relating to a potential loss associated with the relevant reported issue; performance data indicative of a past performance of a reporting entity; or performance data indicative of a past performance of a reported entity. 
     
     
         10 . The system of  claim 2 , wherein the operations further comprise:
 determining whether the reconciled issue report corresponds to an existing issue entry in the issue queue; and   reconciling and aggregating issue data for the reconciled issue report with the corresponding existing issue entry in the issue queue resulting in a reduced number of discreet entries in the issue queue.   
     
     
         11 . A method comprising:
 monitoring, by a rules engine, a computer network for a violation of a parameter defined by rules in a database;   automatically detecting, by the rules engine, the violation;   in response to the automatically detecting, generating, by the rules engine, an issue report indicating the violation;   receiving, via a user interface, an issue report from a human user, the issue report from the human user indicating a potential violation in the computer network;   parsing, by a reconciliation and integration module, the issue report from the rules engine and the issue report from the human user;   determining, based on data parsed from the issue reports, that a common issue is being reported by both the rules engine and the human user; and   reconciling, by a hardware processor, the issue report from the rules engine with the issue report from the human user resulting in a single issue entry in an issue queue, the reconciling including incrementing a count for each instance of the common issue being reported.   
     
     
         12 . The method of  claim 11 , further comprising automatically prioritizing the reconciled issue report by applying to the reconciled issue report a merged issue priority based, at least in part, on a combination of associated priority criterion data, the merged issue priority being based on a merge of a plurality of different priority types. 
     
     
         13 . The method of  claim 12 , further comprising causing performance of a corresponding response activity for the reconciled issue report, the response activity to be performed based on the merged issue priority. 
     
     
         14 . The method of  claim 12 , wherein the priority criterion data comprises visibility data relating to a number of times a respective reported violation has been a subject of an issue report. 
     
     
         15 . The method of  claim 12 , wherein the priority criterion data comprises severity Data, the parsing including identifying an issue type associated with a respective issue report to obtain the severity data based on the identified issue type. 
     
     
         16 . The method of  claim 12 , wherein the priority criterion data comprises exposure data relating to a potential loss associated with a respective reported issue, the exposure data comprising an exposure value obtained from a database. 
     
     
         17 . The method of  claim 12 , wherein the priority criterion data comprises performance data indicative of a past performance of a reporting entity associated with a respective issue report, the parsing including identifying the reporting entity and retrieving the performance data from a database. 
     
     
         18 . The method of  claim 12 , wherein the merged issue priority is based on a combination of at least two of: visibility data relating to a number of times a relevant reported violation has been a subject of an issue report; severity data relating to a pre-defined severity of an associated issue type; exposure data relating to a potential loss associated with the relevant reported issue; performance data indicative of a past performance of a reporting entity; or performance data indicative of a past performance of a reported entity. 
     
     
         19 . The method of  claim 11 , further comprising:
 determining whether the reconciled issue report corresponds to an existing issue entry in the issue queue; and   reconciling and aggregating issue data for the reconciled issue report with the corresponding existing issue entry in the issue queue resulting in a reduced number of discreet entries in the issue queue.   
     
     
         20 . A hardware storage device comprising instructions which, when implemented by one or more processors of a machine, cause the machine to perform operations comprising:
 monitoring a computer network for at least one violation of a parameter defined by rules in a database;   automatically detecting the at least one violation;   in response to the automatically detecting, generating, by a rules engine, an issue report indicating the at least one violation;   receiving, via a user interface, an issue report from a human user, the issue report from the human user indicating a potential violation in the computer network;   parsing the issue report from the rules engine and the issue report from the human user;   determining, based on data parsed from the issue reports, that a common issue is being reported by both the rules engine and the human user; and   reconciling the issue report from the rules engine with the issue report from the human user resulting in a single issue entry in an issue queue, the reconciling including incrementing a count for each instance of the common issue being reported.   
     
     
         21 . The hardware storage device of  claim 20 , wherein the operations further comprise automatically prioritizing the reconciled issue report by applying to the reconciled issue report a merged issue priority based, at least in part, on a combination of associated priority criterion data, the merged issue priority being based on a merge of a plurality of different priority types.