Abstract:
A system to monitor the vulnerability of a computer system is provided. The system comprises an configuration information storing unit to store the configuration information on the computer system to be monitored, a manager information storing unit to register the information on the system manager who does the vulnerability management work for the computer system to be monitored, a vulnerability information storing unit to store various types of vulnerability information, a vulnerability information offering unit to retrieve from the aforementioned vulnerability information storing unit the vulnerability information to be applied to the computer system to be monitored based on the aforementioned configuration information and to offer it to the aforementioned system manager, and a vulnerability measure information submission unit to generate vulnerability measure information based on the work log of the vulnerability modification measures that the system manager has taken and to submit this to the supervisor of the system manager who has done the aforementioned vulnerability modification work.

Description:
[0001]    This application claims the benefit of Japanese Patent Application No. 2002-10886 filed on Jan. 18, 2002, the entire contents of which are incorporated by reference.  
         BACKGROUND OF THE INVENTION  
         [0002]    The present invention generally relates to a method and a system to monitor the vulnerabilities of a computer system group, which, for instance, is connected to a network.  
           [0003]    Recently, networks and servers at corporations and government offices have frequently been attacked by crackers or infected with new viruses. With frequent occurrences of such damages, strengthening of network security has been called for.  
           [0004]    Many illegal accesses by crackers and recent viruses affect a computer system by attacking the vulnerabilities (security holes) of the system or software. To prevent damages that attribute to such system vulnerabilities, users must check the security information generated by vendors and take measures by modifying the configuration of the system according to the security information.  
           [0005]    However, it is extremely difficult to find information needed for one&#39;s own system from among vast amount of security information, and to take necessary measures without a delay. Further, despite the fact that it is an extremely important matter for a corporation whether or not the measures have been taken, a network system manager would be solely in charge of the decision because the matter is too technical. It used to be practically impossible for corporate executives with little technical knowledge to handle the information. Therefore, even when the system manager has not taken the necessary measures, no function was available for his/her supervisor to check that.  
         BRIEF SUMMARY OF THE INVENTION  
         [0006]    This invention was made considering the abovementioned situation. The object of the present invention is to offer a system, which can offer to system managers only the security information necessary for a system within an organization, and can also allow executives of the organization to check whether or not measures have been taken.  
           [0007]    According to the first aspect of the present invention, a method to monitor the vulnerabilities of a computer system is offered. The method comprises a vulnerability information offering process, wherein the vulnerability information to be applied to the computer system to be monitored is specified based on the configuration information of the computer system to be monitored, which is then provided to the system manager of the aforementioned system; a work log storing process, wherein the input of the record of vulnerability modification work applied to the aforementioned computer system based on the aforementioned vulnerability information is received from the aforementioned system manager, which is then stored as a work log; and a vulnerability modification information submission process, wherein the vulnerability modification information is generated based on the work log stored in the aforementioned work log storing unit, which is then submitted to the supervisor of the system manager who did the aforementioned vulnerability modification work.  
           [0008]    According to this configuration, to the system manager, only the vulnerability information necessary for the computer to be monitored can be provided being associated with this system. Further, the record of the modification measures that the system manager has taken can be provided as the vulnerability modification information to the supervisor who overlooks the work of this system manager. In this manner, the system manager will be able to quickly take the measures to modify the vulnerabilities, while the supervisor will be able to check the measures taken without having technical knowledge.  
           [0009]    According to the second aspect of the present invention, a system to monitor the vulnerabilities of a computer system is provided. The system comprises an configuration information storing unit, which stores the configuration information on the computer system to be monitored; a manager information storing unit, wherein the information on the system manager who does the vulnerability modification work for the computer system to be monitored is registered; a vulnerability information storing unit that stores various types of vulnerability information; and a vulnerability information offering unit, which retrieves from the aforementioned vulnerability information storing unit the vulnerability information to be applied to said computer system to be monitored, and offers the information to the aforementioned system manager.  
           [0010]    Further, it is preferable that this system also has a work log storing unit, which receives from the aforementioned system manager the input of the record of vulnerability modification work applied to the aforementioned computer system based on the aforementioned vulnerability information, and stores the input as the work log. Also, in this case, it is more preferable that this system further has a vulnerability modification information submission unit, which generates vulnerability modification information based on the work log stored in the aforementioned work log storing unit, and submits the information to the supervisor of the system manager who did the aforementioned vulnerability modification work.  
           [0011]    According to this configuration, a system that can realize the method according to the aforementioned first aspect can be obtained.  
           [0012]    Further, the other features and the prominent effects of the present invention will be more clearly understood by referring to the following detailed description of the preferred embodiment and the attached drawings. 
       
    
    
     BRIEF DESCRIPTION OF THE DRAWINGS  
       [0013]    [0013]FIG. 1 shows a schematic block diagram of an embodiment of the present invention.  
         [0014]    [0014]FIG. 2 shows a diagram to explain the configuration of computer system configuration information.  
         [0015]    [0015]FIG. 3 shows a diagram to explain the configuration of security level values.  
         [0016]    [0016]FIG. 4 shows a diagram to explain the configuration of vulnerability information.  
         [0017]    [0017]FIG. 5 shows a process diagram of the updating process for vulnerability DB.  
         [0018]    [0018]FIG. 6 shows a login screen.  
         [0019]    [0019]FIG. 7 shows a screen to offer information to the system manager.  
         [0020]    [0020]FIG. 8 shows a configuration information registration screen.  
         [0021]    [0021]FIG. 9 shows a screen that displays a list of vulnerability information.  
         [0022]    [0022]FIG. 10 shows a screen that displays details on vulnerability information.  
         [0023]    [0023]FIG. 11 shows an input screen for vulnerability modification work.  
         [0024]    [0024]FIG. 12 shows a screen to offer information to a manger of an organization.  
         [0025]    [0025]FIG. 13 shows a screen to offer security level information to a manager of an organization.  
         [0026]    [0026]FIG. 14 shows a flow chart of the security level value computing process. 
     
    
     DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS  
       [0027]    Preferred embodiments of the present invention will be described in detail below with reference to the accompanying drawings.  
         [0028]    In FIG. 1, reference numeral  1  denotes a security level information offering system according to the present embodiment. FIG. 1 shows a schematic block diagram of this system  1 .  
         [0029]    This system  1  comprises a user system DB  2 , which stores various information  7 - 11  related to a user A and this user&#39;s A computer system  6  to be monitored; a vulnerability DB  3 , which stores information  24  on the vulnerability of the computer system  6 , a vulnerability monitor processing unit  4 , which offers the vulnerability information  24  in the aforementioned vulnerability DB  3  based on the user information  7 - 11  stored in the aforementioned user system DB  2 , as well as computing the security level; and a vulnerability DB updating unit  5 , which generates the aforementioned vulnerability information  24  and updates the aforementioned vulnerability DB  3 .  
         [0030]    In the user system DB  2 , for each user, the configuration information  7  on the aforementioned computer system  6 , the system manager information  8 , the organization information  9 , the vulnerability modification information  10  and the security level value  11  are stored.  
         [0031]    As shown in FIG. 2, as the computer system configuration information  7 , besides attribute information  12  such as the name of the computer system, the manager, the place of installation, and the intended use, hardware configuration  13  such as the type of CPU and the memory capacity, software configuration  14  such as the names of the OS and the application program, setting  15  such as the starting service, the network technology used  16 , related equipment  17  such as the UPS, mirroring  18  such as RAID, and security measure information  19  such as the names of firewall and IDS are stored.  
         [0032]    In the system manager information  8  shown in FIG. 1, the name of the manager (denoted by reference numeral  21  in FIG. 1) of the system  6  to be monitored, and the address to which the information is offered are stored. In the organization information  9 , the name of the organization wherein the aforementioned manager  21  belongs, the name of the manager (executive; indicated with Key  22  in the figure) of the organization, and the address to which the information is offered are stored being associated with the aforementioned system manager information  8 .  
         [0033]    The vulnerability modification information  10  is comprised for each system by recording the work log of the vulnerability modification, which the aforementioned system manager  21  has applied based on the vulnerability information. As illustrated in FIG. 3, the aforementioned security level value  11  comprises the security reference value  11   a,  the security level value history  11   b  and the internal factor point  11   c.  The security reference value  11   a  is a reference value to indicate the security level of the organization to the executive of the organization (manager of the organization  22 ). It has been predetermined and stored, taking into consideration the damages and the stock price effects of a case when security-related problems should occur at said organization. Further, in the security level value history  11   b,  security levels computed in the past are stored as the history. The internal factor point  11   c  is used to obtain the security level. This point  11   c  will be explained in detail later.  
         [0034]    Meanwhile, as illustrated in FIG. 4, in the vulnerability DB  3 , as the vulnerability information  24 , the vulnerability summary information  25 , which contains summary information on the vulnerability; the threat information, which describes the threat due to said vulnerability; the vulnerability patch information  27  to modify said vulnerability; the vulnerability verification information  28 , which describes the result of verification of the aforementioned modification in the actual system; and the threat level value  29  to weight the threat of each vulnerability information are stored. As illustrated in FIG. 5, to generate this information, the operator of this system  1  first collects from the external vendor the vulnerability information or patch information, most of which is offered in English, translates the information into other language if necessary (Step S 1 ), and technically verifies the vulnerability information (Step S 2 ). Then, he adds the unique threat level value  29  to each of the vulnerability information (Step S 3 ), and updates the aforementioned vulnerability DB  3  (Step S 4 ). This updating of the DB 3  is made through the aforementioned DB updating unit  5 .  
         [0035]    Meanwhile, as illustrated in FIG. 1, the aforementioned vulnerability monitor processing unit  4  comprises a user authentication unit  30 , which authenticates the user who accesses this system  1 ; an configuration information/manager information/organization information registration unit  31 , which receives from the system manager  21  or the like, the input of configuration information  7  and manager information  8 , and updates such information; a vulnerability information offering unit  32 , which fetches vulnerability information  24  from the aforementioned vulnerability DB  3  and offers it to the aforementioned system manager  21 ; a vulnerability modification work log recording unit  33 , which receives from the system manager  21  the input of the record of the modification work this system manager  21  has applied based on the aforementioned vulnerability information  24 , and records it as the aforementioned vulnerability modification information  10 ; a vulnerability measure information preparing unit  34 , which generates vulnerability measure information based on this modification information  10 , and reports it to the aforementioned organization manager (executive  22 ); a security level computing unit  35 , which computes the security level of said organization based on both the aforementioned vulnerability information  24  and the information  10  on how the vulnerability is modified; and a security level information preparing unit  36 , which offers information on the computed security level to the aforementioned organization manager (executive  22 ).  
         [0036]    These components  1 - 36 , in actuality, are realized by means of one or more computer software programs installed in a storage medium such as a hard disk provided in an ordinary computer system. The CPU of the aforementioned computer system will call this computer software program onto the RAM, and properly run it so that the functions of the present invention will take effect.  
         [0037]    Next, the detailed explanation of the configurations and functions of the aforementioned components  1 - 36  will be provided based on the diagrams of screen configurations in FIG. 6 and figures thereafter, in reference to actual operation.  
         [0038]    [0038]FIG. 6 illustrates an example of a login screen for this system  1 .  
         [0039]    For instance, when the aforementioned system manager  21  connects to the aforementioned system  1 , he makes the connection through the Internet from his own terminal, and opens this log-in screen. Then, he inputs necessary information respectively in the user name input box  40  and the password input box  41  in this log-in screen, and presses the “Go” button  42 . Then, the aforementioned user-authenticating unit  30  authenticates said system manager  21 , and establishes the connection to this monitoring system  1 .  
         [0040]    When the connecting user is the system manager  21 , according to the result of the aforementioned authentication, the aforementioned vulnerability information offering unit  32  displays the screen illustrated in FIG. 7 on the terminal of the aforementioned system manager  21 . This screen displays the computer group  44  for which the execution of modification software is recommended. To make this display, the configuration information  7  of the aforementioned computer system needs to be appropriately registered in the aforementioned user system DB  2 . To input or update this configuration information, the configuration registration button  45  in this screen illustrated in FIG. 7 should be pressed.  
         [0041]    When this button  45  is pressed, the aforementioned configuration information/manager information/organization information registration unit  31  displays the screen shown in FIG. 8. The system manager  21  can input the configuration information on the computer system through this screen. In this embodiment, as indicated in the computer list  46  in this screen, the organization wherein this system manager  21  belongs has both “Tokyo Main Office” and “Nagoya Plant”. Further, as the computers to be monitored, three computers; i.e., MA-T1, MA-T2 and MA-T3 at Tokyo Main Office and three computers; i.e., MA-N1, MA-N2 and MA-N3 at Nagoya Plant are respectively installed and connected to the network.  
         [0042]    Of these, this screen displays the system configuration information on MA-T1. Through this screen, each of the information  12 - 19  explained in reference to FIG. 2 is inputted for each system. Here, it is essential that the name of the system manager is registered, and then, this system manager information can be edited by pressing the manager registration button indicated with Key  47  in this figure.  
         [0043]    Furthermore, in the present embodiment, an automatic diagnostic button  48  is provided in this screen. Each of the aforementioned information can be automatically obtained from the computer system  6  to be monitored, by pressing this automatic diagnostic button  48 . In other words, as illustrated in FIG. 1, to the aforementioned computer system  6 , a configuration information obtaining system  60 , which obtains the configuration information on this computer system  6 , is connected. Then, when the aforementioned button  48  is pressed, the aforementioned configuration information/manager information/organization information registration unit  31  can start the aforementioned configuration information obtaining system  60  to obtain all or a part of the configuration information on the aforementioned computer system  6 .  
         [0044]    When the system manager  21  accesses this vulnerability monitoring system  1 , the vulnerability information offering unit  32  compares the configuration information  7  registered as explained above in the user system DB  2  and the vulnerability information  24  in the aforementioned vulnerability DB  3 . If this vulnerability DB  3  contains vulnerability information  24  that is compatible with the hardware configuration, etc. of the aforementioned system  6 , this computer is picked up as a computer that needs security measures, and displayed in the list indicated with Key  44  in the screen illustrated in FIG. 7. In this example, all of the aforementioned computers are picked up as a computer system that needs vulnerability modification. In this manner, each of the vulnerability information  24  will be associated with each of the computer systems to be monitored.  
         [0045]    The system manager  21  can view the vulnerability list  50  as illustrated in FIG. 9 by pressing the vulnerability list button  49  in this screen. This vulnerability list is based on the aforementioned attribute information  12 , and may be displayed in reference to the system type, the OS, or the location. Then, by clicking each of the vulnerabilities in this screen, he can access more detailed information. In such a case, the aforementioned vulnerability information offering unit  32  fetches each of the detailed information ( 25 - 28 ) illustrated in FIG. 4 from the aforementioned vulnerability DB  3 , and displays it as illustrated in FIG. 10.  
         [0046]    In this manner, this system manager  21  will be able to check the details on this vulnerability and decide on whether or not to take modifications of this vulnerability. After checking this detailed vulnerability information, if modifications are taken, he will input the vulnerability modification work record by pressing the work log button  51  in this screen.  
         [0047]    [0047]FIG. 11 illustrates the input screen for this work log. In this screen, tasks needed to modify the selected vulnerability are listed in time series, and the system manager  21  will check whether or not each necessary task has been performed, and input the date of implementation.  
         [0048]    The aforementioned vulnerability modification work log recording unit  33  stores the vulnerability modification work inputted in this manner in the aforementioned user system DB  2  as the aforementioned vulnerability modification information  10 . Then when all the tasks listed in FIG. 11 have been completed, this completion of work will be recorded. Further, this screen includes the “not applicable” button  52  and the “temporary measure” button  53 . When the aforementioned vulnerability information does not apply to the system, it can be treated as completed by pressing this not-applicable button  52 . The temporary-measure button  53  is used when no effective patch is available for the vulnerability, so measures need to be taken later.  
         [0049]    Next, a case when the aforementioned manager  22  of the organization connects to this vulnerability monitoring system  1  will be explained.  
         [0050]    When the aforementioned manager  22  of the organization logs in this system  1 , the aforementioned user-authenticating unit  30  will detect, based on the aforementioned organization information  9 , that the user is the manager  22  of the organization. Based on this detection, the aforementioned vulnerability information-offering unit  32  generates and presents vulnerability measure information for the manager  22  of the organization as illustrated in FIG. 12. As displayed in this screen, this vulnerability measure information contains vulnerability information, the effective date of the information, and the date when the measure was taken, for instance, for each manager and for each system. The date when the measure was taken is obtained from the aforementioned modification information  10  and is displayed here. Further, based on the vulnerabilities that have not been taken care, the threat information  26 , etc. is fetched from the aforementioned vulnerability DB  3 , and is displayed in this screen as indicated with Key  54 .  
         [0051]    By viewing this screen, the manager  22  of the organization will be able to check the state of security management of the network related to the organization or the computer system connected to this network. Also, as this system keeps a record of modification work applied by the system manager  21  and presents it to the manager  22  of the organization, this manager  22  of the organization can appropriately supervise the system manager  21 .  
         [0052]    Furthermore, if the display button  55  for the state of improvement is pressed in the screen in FIG. 12, the aforementioned security level computing unit  35  will be started and compute the security level for each vulnerability. Also, this security level computing unit  35  comprises a security level value comparing unit  59  to compare the security values between vulnerabilities and between computers and to compute the security level value for each computer and for each network.  
         [0053]    As illustrated in FIG. 13, two graphs illustrate the aforementioned security level; i.e., the first graph  56  and the second graph  57 .  
         [0054]    The first graph  56  indicates the modification program application rate. For each effective date of each of the vulnerability information, the bar graph indicates the number of modification programs applied. As this graph is based on the effective date, the vulnerability information that became effective in the previous month will be counted in the previous month even if the modification work is applied in the present month.  
         [0055]    The second graph  57  is a line graph, which indicates the change in the security level based on the aforementioned modification result. Next, the display procedure of this second graph  57  will be explained.  
         [0056]    First, in this embodiment, the security level is defined to be comprised of “internal factor,” “external factor” and “other.” 
         [0057]    The internal factor is a static value evaluated by such factors as the presence or absence of security policy or its daily operational situation, the network configuration or the installation of security equipment, and the installation situation. A security consultant derives this internal factor through an evaluation using a check sheet once in, say, three months or six months.  
         [0058]    The external factor is a dynamic value obtained by new vulnerability information found each day. This external factor is basically computed each time the aforementioned manager of the organization accesses the system, based on the type of equipment for which the vulnerability information is obtained, the threat level value in the aforementioned vulnerability information, and the information on how many days have passed since this vulnerability information took effect.  
         [0059]    The weighting percentages for the computation of security level are as follows: 70% internal factor, 20% external factor and 10% other. However, as the other category indicates human errors or the like, it will be excluded from the evaluation in this embodiment. Therefore, in this embodiment, the security level value is computed from the maximum internal factor value of 70 points and the maximum external factor value of 20 points to the maximum total point of 90 points. Further, as mentioned earlier, the internal factor points are pre-computed and stored in the aforementioned user system DB  2 .  
         [0060]    [0060]FIG. 14 illustrates a flow chart, which indicates the processes in which the aforementioned security level computing unit  35  computes the security level value.  
         [0061]    In this embodiment, to obtain the security level of the entire network, first, in Steps S 5 -S 9  in FIG. 14, the security levels of a plurality of computers belonging in this network are computed. Then, in Steps S 10 -S 14 , the security levels of these computers are compared, and the lowest value is adopted as the security level of the network.  
         [0062]    For this, the aforementioned security level computing unit  35  first starts processing with the first vulnerability information on the first (n=1) computer from among a plurality of computers belonging in the network (Step S 5 ).  
         [0063]    Then, from the user system DB  2 , the information on the type of said computer (equipment), the threat level value of the aforementioned vulnerability information, and the information on how many days have passed since this vulnerability information took effect is obtained (Step S 6 ), and the external factor point value wpp on this vulnerability information is computed by means of the following equation (Step S 7 ).  
           Wpp= 20 +hp×hk×il ×date  
         [0064]    Where, Wpp means that the lower the value, the more serious the threat.  
         [0065]    hp is the reference parameter, which is −1 here.  
         [0066]    hk is the type of the computer (machine type). The hk for security equipment is 2 points, and for any other equipment is 1 point.  
         [0067]    il is the aforementioned threat level value (See Key  29  in FIG. 4) added to said vulnerability information. It is set in three steps: S is 4 points, A is 2 points and B is 1 point.  
         [0068]    date is the number of days that have passed without taking measures, which is obtained as the difference between the date when the aforementioned vulnerability information took effect and the present date.  
         [0069]    These external point values wpp are obtained for all unprocessed vulnerabilities applied in the system concerned (Step S 8 ), and the smallest value of them is outputted as the external factor point value wpp (n) of said computer system (Step S 9 ).  
         [0070]    Further, the external factor point values wpp (n) are obtained similarly for all computer systems belonging in the network in the organization concerned (Step S 10 ). In this manner, when the processing has been completed for all computer systems, the smallest wpp in the network is set as the external factor point value wpp (all) for the entire network (Step S 11 ).  
         [0071]    Then, the aforementioned security level computing unit  35  obtains the inner factor point  11   c  from the aforementioned security level value  11  (Step S 12 ), and by adding the aforementioned external factor point wpp (n) and wpp (all) to this, the security level value (SP) is computed (Steps S 13 , S 14 ).  
         [0072]    Next, the aforementioned security level information preparing unit  36  prepares the second graph  57  illustrated in FIG. 13 using the security level value SP, the aforementioned security reference value  11   a  and the security level value history  11   b  (Step S 15 ).  
         [0073]    That is, in this embodiment, the aforementioned security level information preparing unit  36  fetches the security level value on the last day of each month of the past year from the aforementioned security level value history  11   b,  and sets that as the security level value for each month. Then, the security level value SP currently obtained is set as the security level value of the present month. Then, as illustrated in FIG. 13, these security values are indicated as a line graph  57  with the aforementioned security reference value as the central value.  
         [0074]    With this line graph, even an executive with little technical knowledge will be able to evaluate the security level value of the organization concerned at a glance.  
         [0075]    Further, the present invention is not limited to the aforementioned embodiment. Variations may be made without departing from the scope of the invention.  
         [0076]    For instance, while the system manager and the manager of the organization receive various kinds of information from the aforementioned vulnerability monitoring system through the Internet in the aforementioned embodiment, this is not the only method. For instance, various kinds of information may be offered through a means such as E-mail.  
         [0077]    Also, while the aforementioned security level is indicated using a bar graph and a line graph, this is not the only method. It may be indicated by displaying specific numbers. Further, the specific computing method for the aforementioned security level may be altered in various ways within the scope of the present invention. For instance, the security level obtained using only the external factor points wpp, wpp (n), wpp (all) may be offered without using the internal factor point.  
         [0078]    According to the configuration explained above, a method and a system can be offered, which can offer to a security manager only the security information needed for his own system, and can allow an executive to check whether or not the measures have been taken.