JP2007122372A - Vulnerability determination system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To determine vulnerability of security measures of a product created by utilizing a support tool irrespective of a level of knowledge and experience on security. <P>SOLUTION: The system is provided with a security measure receiving means 51 for receiving security measure information data of the product created by utilizing the support tool, a mounting technology allocating means for determining detail information for mounting the security measures, a vulnerability determining means 53 for determining vulnerability from a vulnerability database 52f for classifying and storing the vulnerability of product components and a vulnerability measure database 52i for storing measures to be taken for eliminating the vulnerability, a reference vulnerability storage means for storing reference vulnerability expected in the products or the like, a measure level value calculating means for calculating a measure level value by comparing the vulnerability determined by the vulnerability determining means, and a determination result transmitting means for transmitting the measure to be taken and the measure level value to the support tool. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a vulnerability determination system that can determine the vulnerability of a product.

  As for the necessary security measures in our products against information security incidents such as personal information leaks that have been reported frequently in recent mass media, etc., at present, requests from customers and judgments of development staff and product planning staff, etc. Therefore, it is determined what security functions / techniques are incorporated and implemented in the product.

  Accordingly, the security functions and technologies to be implemented are selected and adopted based on security knowledge and experience possessed by customers, developers, product planners, and the like.

  A vulnerability monitoring method for monitoring a vulnerability of a computer system group connected to a network is known (see, for example, Patent Document 1).

Furthermore, a security design support device that supports editing of existing security specifications based on international security evaluation standards is known (see, for example, Patent Document 2).
JP 2003-216576 A JP 2004-220459 A

  However, security functions and technologies incorporated in products are currently entrusted to security knowledge and experience possessed by product development personnel such as product customers, developers, and product planners.

  For this reason, depending on the level of security knowledge and experience possessed by customers and product development personnel, there is a possibility that the security functions and technologies incorporated in the product may be leaked or varied. In addition, there is a risk that the developed product may be commercialized while the vulnerability exists.

  The present invention has been made in view of the above points. The purpose of the present invention is to ensure the security of a product created using a support tool without depending on the level of security and knowledge of customers and product development personnel. The object is to provide a vulnerability determination system capable of determining the vulnerability of countermeasures.

  The present invention relates to security countermeasure receiving means for receiving security countermeasure information data of a product created using a support tool, and detailed information for implementing security countermeasures from the security countermeasure information data received by the security countermeasure receiving means. Implementation technology assignment means to determine the vulnerability, vulnerability database that classifies and stores vulnerabilities in product components, vulnerability countermeasure database that stores measures to be taken to eliminate vulnerabilities, and assigned implementation Vulnerability judgment means for judging the vulnerability of the security countermeasure information data received by the security countermeasure receiving means from the product components classified into technologies and the vulnerabilities stored in the vulnerability database, and assumed by the product etc. The reference vulnerability storage means for storing the reference vulnerability to be determined and the vulnerability determination means Countermeasure level value calculating means for calculating a countermeasure level value by comparing the detected vulnerability with the reference vulnerability stored in the reference vulnerability storage means, and the security countermeasure information data determined by the vulnerability determining means And a determination result transmitting means for transmitting to the support tool a countermeasure to be taken to eliminate the vulnerability and a countermeasure level value.

  According to the present invention, the server receives security countermeasure information data for each product for which security design has been performed on the support tool, and based on this security countermeasure information data, problems of countermeasures against product vulnerabilities, solution information, Since the deviation from the standard countermeasure level is sent to the support tool and displayed on the support tool, the support tool can be used regardless of the level of security and knowledge of customers and product developers. Thus, it is possible to provide a vulnerability determination system that can determine the security countermeasure vulnerability of a product created in the above manner.

  Hereinafter, an embodiment of the present invention will be described with reference to the drawings. First, a hardware configuration of a personal computer (PC) used as a support tool or a server will be described with reference to FIG. The support tool and server will be described later with reference to FIG.

  In FIG. 1, 11 is a CPU (Central Processing Unit). The system bus 11a from the CPU 11 has a nonvolatile memory 12. A DRAM (dynamic ram) 13, a LAN interface 14, a display controller 15, and a USB interface 16 are connected.

A display device 17 is connected to the display controller 15, and a keyboard 18 and a mouse 19 are connected to the USB interface 16.

  The support tool and the server are connected to each other via the LAN interface 14.

  Next, a client / server system including a support tool and a server will be described with reference to FIG.

  In FIG. 2, 31 is a support tool as a client, and 32 is a server. The support tool 31 and the server 32 are connected to each other via the LAN interface 14.

  The support tool 31 is an online state (connection state with the server 32) or an offline state (server 32) so that the incorporation of security functions and technologies into the product does not depend on the level of security knowledge and experience possessed by development personnel. This means a security support tool that can objectively design security without omissions. Here, security design refers to outputting a summary of countermeasures against existing threats and vulnerabilities by using a security database existing in the tool against threats and vulnerabilities of each component of the product.

  The support tool 31 also has the following functions.

  First, a function of individually storing security countermeasure information data for each product for which security design has been performed on the support tool 31.

  Second, a function of transmitting individual security countermeasure information data to the server 32 for each stored product.

  Third, the function of receiving the vulnerability determination result output from the server 32 side based on the security countermeasure information data transmitted from the support tool 31 side.

  Fourth, a function for displaying the vulnerability determination result received from the server 32.

  The server 32 has the following functions.

First, the function of receiving individual security countermeasure information data for each product transmitted from the support tool 31 side,
Second, an implementation technology assignment function for determining detailed information for implementing security measures from the received security measure information data,
Third, a vulnerability database that classifies and stores product component vulnerabilities,
Fourth, a vulnerability determination function that determines the vulnerability of security measures received from the assigned implementation technology and vulnerability database,
Fifth, a vulnerability countermeasure database that records measures to be taken to eliminate vulnerabilities,
Sixth, a standard vulnerability storage function that stores vulnerability information that is a standard for vulnerability countermeasures for products, etc.
Seventh, a countermeasure level value calculation function for calculating a countermeasure level value by comparing with the vulnerability determined by the vulnerability determination function,
Eighth, a result transmission function for transmitting various determination results obtained from the vulnerability determination function to a support tool.

  The support tool 31 includes a modeling processing unit 41 that performs modeling processing of a target product for which security measures are to be implemented, a security countermeasure policy review processing unit 42 that performs security processing policy review processing, and a security function implementation review that performs security function implementation processing. The processing unit 43, an information asset data input unit 44 for inputting information asset data, and a security database 45 for individually storing security countermeasure information data designed on the support tool 31 are provided.

  As shown in the flowchart of FIG. 3, the modeling processing unit 41 inputs devices that constitute the target product (step S1), and inputs information assets to be protected that the input component devices have (step S2). , Modeling the target product. By executing this modeling process, an assumed threat of the protected asset input from the security database 45 is derived (step S3). In this way, modeling of the target product is completed.

  Next, the security countermeasure policy review processing unit 42 is executed (step S4). In this process, a countermeasure policy for the assumed threat derived in step S3 is extracted from the security database 45 (step S4). Of the extracted countermeasure policies, the person in charge of product development determines and determines how far the target product is to be implemented using this support tool 31.

An example of the operation screen displayed on the display device 17 of the support tool 31 at this time is shown in FIGS. FIG. 9 shows the “Derivation of Threats and Countermeasures” screen. This screen is a screen A that displays threats, a technical measure screen B that is a technical measure among measures to be taken to eliminate vulnerabilities, and an operation that is to be taken to eliminate vulnerabilities Measure screen C, which is an aspect measure, “Confirm known vulnerabilities” button D for confirming known vulnerabilities, “Measured threat list display” button E for displaying a list of threats already implemented Have. When the “Confirm Known Vulnerabilities” button D is touched, a screen for confirming known vulnerabilities for each threat is displayed on the display device 17 as shown in FIG.

Next, the security function implementation review processing unit 43 is executed (step S5). The security function implementation review processing unit 43 extracts from the security database 45 security functions necessary for realizing the countermeasure policy selected by the person in charge of product development. A product development person selects and determines which of the extracted security functions is to be adopted by the product. An example of this security function implementation operation screen is shown in FIG.
Through the series of processes described above, countermeasure result data 46 as product security countermeasure information data is formed and stored in the support tool 31 in the form of a file. The countermeasure result data 46 is transmitted to the server 32. As shown in FIG. 2, the countermeasure result data 46 includes a product information file 46a, a mounted device file 46b, a mounted I / F file 46c, an information asset file 46d, and a countermeasure threat file 46e.

  The server 32 includes a security countermeasure receiving unit 51 that receives countermeasure result data of a product created using the support tool, countermeasure result data received by the security countermeasure receiving unit 51, and data stored in the database 52. A determination unit 53 that determines vulnerability of the countermeasure result data based on the determination result 53 is provided. The database 52 includes a countermeasure result database 52a, a product configuration database 52b, a similar product information database 52c, an information asset database 52d, a threat database 52e, a vulnerability database 52f, a standard security countermeasure database 52g, a security function database 52h, a vulnerability A solution information database 52i for storing measures to be taken to eliminate the problem. The server 32 also has a problem / problem file 52j that stores problems and problems of the countermeasure result data, and a solution information file 52k that stores countermeasures to be taken to eliminate the vulnerability.

  The detailed operation of the server 32 will be described with reference to FIGS. First, the countermeasure threat file 46e received by the security countermeasure receiver 51 is opened (step S11).

  Next, the threat database 52e in the database 52 of the server 32 is opened (step S12).

  One record of the countermeasure threat is read from the received countermeasure threat file 46e (step S13).

  Then, it is determined whether there is no countermeasure threat data (step S14). If “NO” is determined in step S14, that is, if it is determined that there is countermeasure threat data, the read record data is searched from the threat database 52e in the server 32 (step S15).

  It is determined whether there is matching data (step S16). If “NO” is determined in the determination in step S16, the process returns to the process in step S13 described above.

  On the other hand, if “YES” is determined in the determination in step S16, the same database as the file in the countermeasure result data 46 is opened in the database 52 in the server 32 linked to the matched threat data ( Step S17).

  Then, one record of data is read from this opened one database (step S18).

  It is determined whether there is record data (step S19). If “YES” in the determination in step S19, that is, it is determined that there is record data, the read record data is compared with the data in the file existing in the countermeasure result data 46 (step S20).

  It is determined whether there is matching data (step S21). If “YES” is determined in the determination in step S21, the process returns to step S18 described above.

  On the other hand, if “NO” is determined in the determination in step S21, it is added to the problem / task data file 52j (step S22). Then, the process returns to step S18.

  By the way, when it is determined as “NO” in the determination in step S19, it is determined whether or not all corresponding databases have been completed (step S23).

  If “NO” is determined in the determination in step S23, the completed database is closed (step S24), and another corresponding database is opened (step S25). Thereafter, the process returns to step S18.

  On the other hand, if “YES” is determined in the determination in step S23, all databases and files are closed (step S26).

  Then, it is determined whether all applicable countermeasure threat records have been completed (step S27). If "NO" is determined in the determination in step S27, the process returns to step S13 described above.

  On the other hand, if “YES” is determined in the determination in step S27 and if “YES” is determined in the above-described step S14, the process proceeds to step S31a and subsequent steps in FIG.

  That is, the information asset file 46d received by the security countermeasure receiving unit 51 is opened (step S31a). Then, the countermeasure threat file 46e received by the security countermeasure receiver 51 is closed (step S31b).

  Next, the threat database 52e in the database 52 of the server 32 is closed (step S32).

  One record of information asset is read from the received information asset file 46d (step S33).

  Then, it is determined whether there is no information asset data (step S34). If “NO” is determined in step S34, that is, if it is determined that there is information asset data, the read record data is searched from the information asset database 52b in the server 32 (step S35).

  It is determined whether there is matching data (step S36). If “NO” is determined in the determination in step S36, the process returns to the process in step S33 described above.

  On the other hand, if “YES” is determined in the determination in step S36, the threat database 52e, the vulnerability database 52f, and the security function database 52h in the server 32 linked with the matched information asset record data are opened. (Step S37).

  Then, one record of data is read from this opened one database (step S38a). Next, the problem / task data file 52j is opened (step S38b).

  It is determined whether there is record data (step S39). If “YES” in the determination in step S39, that is, it is determined that there is record data, the read record data is compared with the data in the file existing in the countermeasure result data 46 (step S40).

  It is determined whether there is matching data (step S41). If “YES” is determined in the determination in step S41, the process returns to the process in step S38a.

  On the other hand, if “NO” is determined in the determination in step S41, it is added to the problem / task data file 52j (step S42). Then, the process returns to step S38a.

  By the way, when it is determined as “NO” in the determination in step S39, it is determined whether or not all corresponding databases are completed (step S43).

  If “NO” is determined in the determination in step S43, the completed database is closed (step S44), and another corresponding database is opened (step S45). Thereafter, the process returns to step S38a.

  On the other hand, if “YES” is determined in the determination in step S43, all databases and files are closed (step S46).

  Then, it is determined whether all corresponding countermeasure threat records have been completed (step S47). If “NO” is determined in the determination in step S47, the process returns to step S33 described above.

  On the other hand, if “YES” is determined in the determination in step S47 and if “YES” is determined in the above-described step S34, the process proceeds to step S51 and subsequent steps in FIG.

  In FIG. 6, all the databases on the server 32 side already opened at this time are closed (step S51). Next, the problem / task data file 52j is closed (step S52).

  Then, the threat database 52e in the server 32 is closed (step S53).

  It is determined whether solution information is added (step S54). If “YES” is determined in the determination in step S54, the solution information database 52i in the server 32 is opened (step S55). Further, the problem / task data file 52j is opened (step S56). Further, the solution information file 52k is opened (step S57).

  Then, one record is read from the problem / task data file 52j (step S58).

  Further, it is determined whether there is data (step S59).

  If “NO” is determined in the determination in step S59, that is, if it is determined that there is data, the read record data is searched from the solution information database 52i in the server 32 (step S60).

  It is determined whether there is matching data (step S61). If “YES” is determined in the determination in step S61, a record of the matching solution information data is written in the solution information file 52k (step S62).

  On the other hand, if “NO” is determined in the determination in step S61, the process returns to the process in step S58 described above.

  By the way, when it determines with "YES" by determination of step S59, the solution information database 52i in the server 32 is closed (step S63). Next, the problem / task data file 52j is closed (step S64). Then, the solution information file 52k is closed (step S65).

  Then, when “NO” is determined in step S54 described above and after step S65, the processing after step S71 in FIG. 7 is performed.

In FIG. 7, it is determined whether or not the deviation information from the reference is added (step S71). If “YES” is determined in the determination in step S71, the uncorresponding count is set to “0” (step S72a).
The countermeasure threat file 46e received by the security countermeasure receiver 51 is opened (step S72b). Next, the reference security countermeasure database 52g in the database 52 of the server 32 is opened (step S72c).

  One record of the countermeasure threat is read from the received countermeasure threat file 46e (step S73).

  Then, it is determined whether there is no countermeasure threat data (step S74). If “NO” is determined in step S74, that is, if it is determined that there is countermeasure threat data, the read record data is searched from the reference security countermeasure database 52g in the server 32 (step S75).

  It is determined whether there is matching data (step S76). If “NO” is determined in the determination in step S76, the process returns to the process in step S73 described above.

  On the other hand, if “YES” is determined in the determination in step S76, the vulnerability data in the countermeasure result data 46 linked to the matched threat data, each data of the security function, and the same database 52f in the server 32, 52h is opened (step S77).

  Then, one record of data is read from this opened one database (step S78).

  It is determined whether there is record data (step S79). If “YES” in the determination of step S79, that is, it is determined that there is record data, the read record data is compared with the data in the file existing in the countermeasure result data 46 (step S80).

  It is determined whether there is matching data (step S81). If “YES” is determined in the determination in step S81, the process returns to the process in step S78 described above.

  On the other hand, if “NO” is determined in the determination in step S81, the uncorresponding count is incremented (step S82). Then, the process returns to step S78.

  By the way, when it is determined as “NO” in the determination in step S79, it is determined whether or not all corresponding databases are completed (step S83).

  If “NO” is determined in the determination in step S83, the completed database is closed (step S84), and another corresponding database is opened (step S85). Thereafter, the process returns to step S78.

  On the other hand, if “YES” is determined in the determination in step S83, all databases and files are closed (step S86).

  Then, it is determined whether all applicable countermeasure threat records have been completed (step S87). If "NO" is determined in the determination in step S87, the process returns to step S73 described above.

  On the other hand, if “YES” is determined in the determination in step S87 and if “YES” is determined in the above-described step S74, the process proceeds to step S91 and subsequent steps in FIG.

  In FIG. 8, all databases and files are closed (step S91). Then, it is determined whether the unsupported count is 20% or less (step S92). If “YES” is determined in the step S92, the deviation level is set to “1” (step S93).

  On the other hand, if “NO” is determined in the determination in step S92, it is determined whether the unsupported count is 40% or less (step S94). If “YES” is determined in the step S94, the deviation level is set to “2” (step S95).

  On the other hand, if “NO” is determined in the determination in step S94, it is determined whether the unsupported count is 60% or less (step S96). If “YES” is determined in the step S96, the deviation level is set to “3” (step S97).

  On the other hand, if “NO” is determined in the determination in step S96, it is determined whether the unsupported count is 80% or less (step S98). If "YES" is determined in the step S98, the deviation level is set to "4" (step S99).

  On the other hand, if “NO” is determined in the determination in step S98, the deviation level is set to “5” (step S100).

  FIG. 12 shows the deviation level displayed on the display device 17 of the support tool 31. In this way, it is displayed how much the standard measure is implemented according to the deviation level.

  As described above, the server 32 receives the security countermeasure information data for each product for which security design has been performed on the support tool 31, and based on the security countermeasure information data, the problem of the countermeasure against the vulnerability of the product and the solution information Since the deviation from the standard countermeasure level is transmitted to the support tool and displayed on the support tool 31, the support tool can be used regardless of the level of security knowledge and experience possessed by customers and product development personnel. It is possible to determine the vulnerability of a security measure of a product created using the 31.

1 is a hardware configuration diagram of a personal computer (PC) used as a support tool or server according to an embodiment of the present invention. The figure which shows the client server system comprised with the support tool and a server. The flowchart for demonstrating operation | movement of the support tool. Part of a flowchart for explaining the operation of the server. Part of a flowchart for explaining the operation of the server. Part of a flowchart for explaining the operation of the server. Part of a flowchart for explaining the operation of the server. Part of a flowchart for explaining the operation of the server. Security countermeasure policy review operation screen displayed on the support tool. Security countermeasure policy review operation screen displayed on the support tool. Security function implementation review operation screen displayed on the support tool. Deviation level display screen displayed on the support tool.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 11 ... CPU, 12 ... Non-volatile memory, 13 ... DRAM, 17 ... Display apparatus, 31 ... Support tool, 32 ... Server.

Claims (3)

Security countermeasure receiving means for receiving security countermeasure information data of a product created using a support tool;
Implementation technology assigning means for determining detailed information for implementing security measures from the security measure information data received by the security measure receiving means;
A vulnerability database that classifies and stores vulnerabilities in product components;
Vulnerability determination means for determining the vulnerability of the security countermeasure information data received by the security countermeasure reception means from the assigned implementation technology and the product components classified as vulnerabilities stored in the vulnerability database;
A vulnerability determination system comprising: determination result transmission means for transmitting the vulnerability of the security countermeasure information data obtained by the vulnerability determination means to the support tool. Security countermeasure receiving means for receiving security countermeasure information data of a product created using a support tool;
Implementation technology assigning means for determining detailed information for implementing the security countermeasures from the security countermeasure information data received by the security countermeasure receiving means;
A vulnerability database that classifies and stores vulnerabilities in product components;
A vulnerability countermeasure database that stores countermeasures to be taken to eliminate vulnerabilities;
Vulnerability determination means for determining the vulnerability of the security countermeasure information data received by the security countermeasure reception means from the assigned implementation technology and the product components classified as vulnerabilities stored in the vulnerability database;
Vulnerability characterized by comprising a determination result transmission means for transmitting to the support tool the vulnerability of the security countermeasure information data determined by the vulnerability determination means and the countermeasure to be taken to eliminate the vulnerability Sex determination system. Security countermeasure receiving means for receiving security countermeasure information data of a product created using a support tool;
Implementation technology assigning means for determining detailed information for implementing security measures from the security measure information data received by the security measure receiving means;
A vulnerability database that classifies and stores vulnerabilities in product components;
A vulnerability countermeasure database that stores countermeasures to be taken to eliminate vulnerabilities;
Vulnerability determination means for determining the vulnerability of the security countermeasure information data received by the security countermeasure reception means from the assigned implementation technology and the product components classified as vulnerabilities stored in the vulnerability database;
Reference vulnerability storage means for storing reference vulnerability assumed in products, etc.,
Countermeasure level value calculating means for calculating a countermeasure level value by comparing the vulnerability determined by the vulnerability determining means and the reference vulnerability stored in the reference vulnerability storage means;
A determination result transmitting means for transmitting to the support tool the vulnerability of the security countermeasure information data determined by the vulnerability determination means, the countermeasure to be taken to eliminate the vulnerability, and the countermeasure level value; Feature vulnerability determination system.

Images