JP5414584B2 - Security product information providing apparatus, security product information providing method of security product information providing apparatus, and security product information providing program - Google Patents

Description

  The present invention relates to, for example, a security product information providing apparatus that provides information on a security product suitable for a system, a security product information providing method of the security product information providing apparatus, and a security product information providing program.

  Patent Literature 1 describes a method of calculating a risk based on a threat that has been identified after identifying the threat of the information system, and selecting a security product that matches the calculated risk.

  Patent Document 2 describes a technique for accumulating existing cases related to security specifications in a database and automatically generating a draft of the security specifications for the design target system by reflecting the accumulated cases in the security specification template. Yes.

JP 2006-350399 A JP 2004-341623 A

  Since the technique described in Patent Document 1 starts from identifying threats from the information system, the completeness of the requirements for the entire system is unknown.

  The method described in Patent Document 2 automatically generates a draft of a security specification for a design target system from existing cases, but it is unclear whether a draft of a security specification that satisfies all the security requirements of the design target system can be generated.

  An object of the present invention is to enable automatic selection of a combination of security products suitable for a system, for example.

The security product information providing apparatus of the present invention is
A security function database unit that stores data indicating a plurality of security functions corresponding to the system type representing the type of system as security function data;
For each security function, data indicating a security product having the security function is stored as security product function data, and security product combination data indicating a plurality of predetermined combinations of security products as permitted combinations of security products is stored. Product database department;
A target security function group specifying unit that inputs a specific system type and specifies a plurality of security functions corresponding to the input system type as a target security function group based on the security function data;
Target security product group for identifying a plurality of security products having at least one security function included in the target security function group specified by the target security function group specifying unit as the target security product group based on the security product function data A specific part,
A plurality of combinations of security products consisting of at least two security products included in the target security product group specified by the target security product group specifying unit are specified as security product combination candidates, and a plurality of combination candidates of the specified security products are selected. Of these, security product combination candidates that are indicated as permitted combinations of security products in the security product combination data are identified as security product target combinations, and information indicating the identified security product target combinations is output as security product combination information A product combination specifying unit.

  According to the present invention, for example, a combination of security products suitable for a system can be automatically selected.

2 is a functional configuration diagram of a security product sales support system 100 according to Embodiment 1. FIG. FIG. 3 is a schematic diagram of an industry standard specification DB 160 according to the first embodiment. The figure which shows the specific example of the industry standard specification requirement table 161 memorize | stored in industry standard specification DB160 in Embodiment 1. FIG. The figure which shows the specific example of the security functional requirement table 162 memorize | stored in industry standard specification DB160 in Embodiment 1. FIG. FIG. 3 is a schematic diagram of a product STDB 170 in the first embodiment. The figure which shows the specific example of the corresponding | compatible product table 171 memorize | stored in product STDB170 in Embodiment 1. FIG. The figure which shows the specific example of the connectable product table 172 memorize | stored in product STDB170 in Embodiment 1. FIG. FIG. 3 is a schematic diagram of a classification information DB 150 according to the first embodiment. 5 is a flowchart showing a sales support method for security products in the first embodiment. The figure which shows the system requirement list | wrist 111 produced | generated by the request | requirement automatic generation part 110 in Embodiment 1. FIG. The figure which shows corresponding | compatible product list A122 produced | generated by the product automatic selection part 120 in Embodiment 1. FIG. The figure which shows corresponding | compatible product list B123 produced | generated by the product automatic selection part 120 in Embodiment 1. FIG. 6 is a diagram showing a product combination candidate list 124 generated by an automatic product selection unit 120 in the first embodiment. FIG. FIG. 6 is a diagram showing a product combination list 121 generated by a product automatic selection unit 120 in the first embodiment. 2 is a diagram illustrating an example of hardware resources of a security product sales support system 100 according to Embodiment 1. FIG. The figure which shows the coverage function list 131 produced | generated by the function coverage degree calculation part 130 in Embodiment 2. FIG. FIG. 10 is a diagram showing a specific example of an operation & data table 173 stored in a product STDB 170 in the third embodiment. 10 is a flowchart of security feasibility calculation processing (S300) in the third embodiment. FIG. 10 is an excerpt from the operation & data table 173 according to the third embodiment. FIG. 10 is an excerpt from the operation & data table 173 according to the third embodiment. The figure which shows the security feasibility list 141 produced | generated by the security feasibility calculation part 140 in Embodiment 3. FIG. FIG. 10 is a conceptual diagram related to security feasibility in the third embodiment. FIG. 10 is a conceptual diagram related to security feasibility in the third embodiment.

Embodiment 1 FIG.
A mode for automatically selecting a combination of security products suitable for the system will be described.

FIG. 1 is a functional configuration diagram of a security product sales support system 100 according to the first embodiment.
The functional configuration of the security product sales support system 100 according to Embodiment 1 will be described below with reference to FIG.

The security product sales support system 100 (an example of a security product information providing apparatus) includes an automatic request generation unit 110, an automatic product selection unit 120, a function coverage calculation unit 130, and a security feasibility calculation unit 140.
The security product sales support system 100 further includes a classification information DB 150 (DB: database), an industry standards DB 160, and a product STDB 170 (ST: security target).

  The outline of the configuration of the security product sales support system 100 will be described below.

The classification information DB 150 stores table design information indicating the structure of tables stored in the industry standards DB 160 or the product STDB 170.
The tables stored in the industry standards DB 160 and the product STDB 170 are generated based on the table design information stored in the classification information DB 150.

  The industry standards DB 160 (an example of a security function database unit) has a plurality of security functions (“security function requirements” described later) corresponding to a system type (“customer request 101” described later) representing the type of the target system. Is stored as security function data (an “industry standard specification requirement table 161” or “security function requirement table 162” described later).

  The product STDB 170 (an example of a security product database unit) stores data indicating a security product (corresponding product described later) having the security function for each security function as security product function data (a “corresponding product table 171” described later). To do. Security products include not only commercially available products but also libraries created in-house.

  The product STDB 170 stores security product combination data (a “connectable product table 172” to be described later) indicating a plurality of predetermined combinations of security products as permitted combinations of security products.

The product STDB 170 is a security product indicating an execution process (an “operation” described later) executed by the security product for each security product and a protection status indicating whether or not the security of the processing data processed by the execution process is guaranteed. Process data ("operation & data table 173" described later) is stored.
The product STDB 170 stores execution processing function data (an “operation & data table 173” to be described later) in which execution processing and security functions related to execution processing are associated with each other.

The automatic request generation unit 110 (an example of a target security function group specifying unit) inputs a specific system type.
The request automatic generation unit 110 identifies a plurality of security functions corresponding to the input system type as a target security function group (security function requirements shown in a “system requirement list 111” described later) based on the security function data.

The automatic product selection unit 120 (an example of a target security product group specifying unit and a security product combination specifying unit) has a plurality of security functions having at least one security function included in the target security function group specified by the request automatic generation unit 110. A product is specified as a target security product group ("corresponding product list B123" described later) based on the security product function data.
The automatic product selection unit 120 specifies a plurality of combinations of security products including at least two security products included in the specified target security product group as security product combination candidates.
The automatic product selection unit 120 identifies a security product combination candidate indicated as a permitted combination of security products in the security product combination data among a plurality of combination candidates of the specified security products as a target combination of security products.
The product automatic selection unit 120 outputs information indicating the target combination of the identified security products as security product combination information (a “product combination list 121” described later).

  The function coverage calculating unit 130 (an example of the insufficient security function specifying unit) specifies a security function other than the security function included in the target combination of the security products among the security functions included in the target security function group as the insufficient security function. . The function coverage calculating unit 130 outputs insufficient security function information (“covered function list 131” described later) indicating the specified insufficient security function.

The security feasibility calculation unit 140 (an example of a security assurance determination unit) performs security product processing on a plurality of security products that execute common execution processing as common processing among a plurality of security products included in the target combination of security products. Based on the data, identify as a common processing product group.
The security feasibility calculation unit 140 determines based on the security product processing data whether a security product that does not guarantee the security of the processing data processed by the common processing is included in the common processing product group. Make a processing decision.
The security feasibility calculation unit 140 outputs information including the result of the security unguaranteed process determination as security assurance information (a “security feasibility list 141” described later).

When the security feasibility calculation unit 140 determines that a security product that does not guarantee the security of the processing data processed by the common processing is included in the common processing product group, the security feasibility calculation unit 140 executes a security function related to the common processing in the execution processing It is specified as a security unguaranteed function based on the function data.
The security feasibility calculation unit 140 performs security non-guaranteed function determination for determining whether or not the target security function group includes the security non-guaranteed function.
The security feasibility calculation unit 140 outputs information including the security unguaranteed function determination result as the security assurance information.

FIG. 2 is a schematic diagram of the industry standards DB 160 in the first embodiment.
An overview of the industry standards DB 160 in the first embodiment will be described below with reference to FIG.

The industry standard specifications DB 160 stores data in which standard specifications and standards used in the industry (for example, medical related) are associated with security requirements for each industry.
For example, industry specifications and standards are information described in “reference documents”, the type of “system”, and the function “realization function” of the system.
The security requirement is defined as “SFR (Security Functional Requirements)”.

  For example, these pieces of information are stored in the industry standard specifications DB 160 as the industry standard specifications requirement table 161 and the security function requirement table 162.

FIG. 3 is a diagram showing a specific example of the industry standard specification requirement table 161 stored in the industry standard specification DB 160 in the first embodiment.
The industry standard standards requirement table 161 in the first embodiment will be described below with reference to FIG.

  The industry standard specification requirement table 161 is prepared for each industry in advance and stored in the industry standard specification DB 160.

  The industry standard specification requirement table 161 is data in which a request corresponding to an industry or a system is associated with a requirement of the industry standard / standard.

The request corresponding to the industry and system is information corresponding to the type and function of the target system.
For example, a client server system and a mail system can be cited as requests corresponding to the industry and system.

The requirements of industry standards and standards are system requirements related to security extracted from industry reference documents.
For example, requirements for industry standards and standards include requirements for monitoring targets, log functions, access rights, passwords, logins, virus countermeasures, and the like.

  For example, FIG. 3 shows that an industry client server system requires requirement 1, requirement 2, requirement 3, requirement 4, requirement 9, and requirement 10.

FIG. 4 is a diagram showing a specific example of the security function requirement table 162 stored in the industry standards DB 160 in the first embodiment.
The security function requirement table 162 according to the first embodiment will be described below with reference to FIG.

  The security function requirement table 162 is prepared in advance for each industry and stored in the industry standards DB 160.

  The security function requirement table 162 is data in which requirements of industry standards / standards are associated with security function requirements.

  The requirements of industry standards / standards are the same as those of the industry standard / standards requirement table 161 (see FIG. 3).

The security function requirement is information for identifying a function related to security.
For example, FAU (security audit), FDP (user data protection), and FIA (identification and authentication) are listed as security functional requirement (SFR) categories.

  For example, FIG. 4 shows that FAU1, FAU2, and FAU5 are required as security functions to satisfy requirement 1.

FIG. 5 is a schematic diagram of product STDB 170 in the first embodiment.
An overview of product STDB 170 in the first embodiment will be described below with reference to FIG.

  The product STDB 170 stores data in which specifications and various requirements are associated with each security product having a specific security function.

  For example, the product STDB 170 has a product function “realization function”, “necessary service / premise”, “list of connectable products”, a process executed by the product, and a product for each security product identified by “product name”. Data to be processed “Operation & Data” is stored.

The “realization function” includes “realization method”, “SFR”, and the like.
“Realization method” is information indicating the form of a product (hardware, software, service, etc.).
For example, these pieces of information are stored in the product STDB 170 as the corresponding product table 171.

The “necessary service / premise” is information such as the type of network to be connected and necessary settings / restrictions.
For example, the network type includes WAN (wide area network), LAN (local area network), VPN (virtual private network), and the like. Necessary settings include administrator settings and operator settings. The necessary restrictions include physical security (for example, a room that manages entry / exit).

The “list of connectable products” is information indicating combinations of products that can be used in combination in one system (including a system including a plurality of devices that communicate and cooperate).
Depending on the product, there are those that can be connected to and communicated with products of other companies (that can be used in combination) depending on the input / output interface, data format, communication protocol, or other specifications.
For example, the “list of connectable products” is stored in the product STDB 170 as a connectable product table 172.

The “operation & data” includes “external I / F (interface)”, “internal I / F”, “SFR”, and the like.
The “external I / F” includes “I / F system”, “I / F format”, “security level”, “protection status”, “target operator”, “premise”, and the like.
For example, these pieces of information are stored in the product STDB 170 as the operation & data table 173.

  The “I / F method” is information indicating a connection method such as serial connection or parallel connection, or a communication method such as the Internet, WAN, LAN, VPN, or telephone line.

  The “I / F format” is information indicating a connection method, a communication method standard, and the like.

  The “security level” is information indicating a settable security level (for example, high / medium / low) and a necessary security level.

  The “protection status” is information indicating whether the security of data to be used is guaranteed.

  The “target operator” is information that identifies a user (operator, administrator, maintenance worker, etc.).

  “Premise” is information indicating usage conditions such as fixing a connection destination and encrypting data.

FIG. 6 is a diagram showing a specific example of the corresponding product table 171 stored in the product STDB 170 in the first embodiment.
The corresponding product table 171 in the first embodiment will be described below with reference to FIG.

  The corresponding product table 171 is stored in the product STDB 170 in advance.

  The corresponding product table 171 is data in which security function requirements and corresponding products are associated with each other.

  The security function requirements are common to the security function requirement table 162 (FIG. 4).

The corresponding product is information indicating the product type / function (or implementation method) and the product name.
For example, the types and functions of products include mail clients, mail servers, and virus detection servers.

  For example, FIG. 6 shows that both products A and B of the mail client have FIA2 to FIA4 as security functions.

FIG. 7 is a diagram illustrating a specific example of the connectable product table 172 stored in the product STDB 170 according to the first embodiment.
The connectable product table 172 according to Embodiment 1 will be described below with reference to FIG.

  The connectable product table 172 is stored in the product STDB 170 in advance.

  The connectable product table 172 is data indicating other products connectable for each product.

  For example, FIG. 7 shows that product A can be used in combination with product B and product C. Further, it indicates that the product A cannot be used in combination with the product D.

FIG. 8 is a schematic diagram of the classification information DB 150 in the first embodiment.
An overview of the classification information DB 150 in the first embodiment will be described below with reference to FIG.

The data (model, format, definition value) stored in the classification information DB 150 indicates a guideline as a classification standard at the time of data input to the industry standards DB 160 and the product STDB 170, and is a system required in each industry. Represents the correspondence with general-purpose systems.
For example, the classification information DB 150 presents a product function “realized function” that can be registered in the product STDB 170 and is used by a registrant to prevent different names for the same function from being registered in the product STDB 170.
Further, the classification information DB 150 is used to define different “functions” and “realization functions”, thereby associating different realization functions between systems with high security and those with less security.

  The “industry”, “system”, “realization function”, “realization method”, “product name”, “list of connectable products”, and “necessary services / premises” defined in the classification information DB 150 are stored in the industry standards DB 160 and the product STDB 170. Used as a data item.

FIG. 9 is a flowchart showing a security product sales support method according to the first embodiment.
A security product sales support method (an example of a security product information providing method) in the first embodiment will be described below with reference to FIG.

  First, an overview of a sales support method for security products will be described.

The request automatic generation unit 110 specifies the industry standard specification requirement corresponding to the customer request 101 based on the industry standard specification requirement table 161 (S110).
The request automatic generation unit 110 specifies security function requirements necessary for the industry standard specifications requirements of the customer request 101 based on the security function requirement table 162 (S120).

The automatic product selection unit 120 identifies a corresponding product group having the security function requirements of the customer request 101 based on the corresponding product table 171 (S130).
The automatic product selection unit 120 identifies corresponding product combination candidates based on the corresponding product group of the customer request 101 (S140).
The automatic product selection unit 120 selects an available combination from among the combination candidates of the corresponding products based on the connectable product table 172 (S150).

  The function coverage calculating unit 130 identifies the security function requirements covered by the combination of available corresponding products among the security function requirements of the customer request 101 and the insufficient security function requirements (S200: function coverage calculation) processing).

  The security feasibility calculation unit 140 identifies an operation & data for which security is guaranteed and an operation & data for which security is not guaranteed in a combination of available compatible products configured by the corresponding product group of the customer request 101. (S300: Security feasibility calculation processing).

Next, details of each process (S110 to S150) will be described.
The function coverage calculation process (S200) and the security feasibility calculation process (S300) will be described in the second and third embodiments.

In S110, the automatic request generation unit 110 displays a list of “industry”, “system”, and “realized function” defined in the classification information DB 150 (see FIG. 8) on the display device.
The user of this system designates the target “industry”, “system”, and “realization function” from the displayed list using an input device (keyboard, mouse, etc.).
The request automatic generation unit 110 inputs the designated “industry”, “system”, and “realization function” as the customer request 101.

  The request automatic generation unit 110 searches the industry standard standards requirement table 161 (see FIG. 3) for “industry” designated in the customer request 101, and “system” “realization function” designated in the customer request 101. ”To identify industry standard requirements.

For example, FIG. 3 shows an industry standard specification requirement table 161 for “industry” designated in the customer request 101.
Further, it is assumed that “client server system” is designated as “system” and “realized function”.
In this case, the automatic request generation unit 110 specifies “requirements 1 to 4, 9, 10” as the industry standard requirements for the customer request 101.

  It progresses to S120 after S110.

  In S120, the automatic request generation unit 110 searches the security function requirement table 162 (see FIG. 4) for “industry” designated in the customer request 101, and is necessary for the industry standard specifications requirements of the customer request 101. Identify security functional requirements.

The automatic request generation unit 110 generates a system requirement list 111 as information listing the specified security function requirements, and outputs the generated system requirement list 111.
For example, the automatic request generation unit 110 stores the system requirement list 111 in the storage device and displays it on the display device.

FIG. 10 is a diagram showing a system requirement list 111 generated by the automatic request generation unit 110 in the first embodiment.
The system requirement list 111 in the first embodiment will be described below with reference to FIG.

The system requirement list 111 indicates security function requirements for each industry standard specification requirement specified in S110.
The system requirement list 111 is generated by the request automatic generation unit 110.

For example, FIG. 4 shows a security function requirement table 162 for “industry” specified in the customer request 101.
Further, it is assumed that “requirements 1 to 4, 9, and 10” are specified as the industry standard requirements for the customer request 101.

The request automatic generation unit 110 searches the security function requirement table 162 of FIG. 4 and specifies the security function requirement “FAU1, 2, 5” necessary for the industry standard specification requirement “requirement 1” of the customer request 101. The request automatic generation unit 110 similarly specifies the security function requirements for the remaining industry standard requirements “requirements 2 to 4, 9, 10” of the customer request 101.
The automatic request generation unit 110 generates and outputs a system requirement list 111 (see FIG. 10) in which industry standard standards and security function requirements are associated with each other.

  Returning to FIG. 9, the description of the security product sales support method will be continued.

  It progresses to S130 after S120.

  In S <b> 130, the product automatic selection unit 120 inputs the system requirement list 111.

  The automatic product selection unit 120 searches the corresponding product table 171 for “industry” designated in the customer request 101, and specifies a corresponding product having the security function requirement of the customer request 101 for each security function requirement.

The product automatic selection unit 120 generates a list of compatible products A122 by listing the corresponding products for each security function requirement.
Further, the product automatic selection unit 120 generates a corresponding product list B123 by listing a plurality of corresponding products shown in the corresponding product list A122.
A plurality of corresponding products shown in the corresponding product list B123 is a corresponding product group corresponding to the customer request 101.

FIG. 11 is a diagram showing the corresponding product list A122 generated by the product automatic selection unit 120 in the first embodiment.
FIG. 12 is a diagram showing the corresponding product list B123 generated by the product automatic selection unit 120 in the first embodiment.
The corresponding product list A122 and the corresponding product list B123 in the first embodiment will be described below with reference to FIGS.

In FIG. 11, the corresponding product list A 122 indicates a corresponding product for each security function requirement of the customer request 101.
In FIG. 12, a corresponding product list B123 indicates a plurality of corresponding products shown in the corresponding product list A122.
The corresponding product list A122 and the corresponding product list B123 are generated by the product automatic selection unit 120.

For example, FIG. 6 shows a corresponding product table 171 for “industry” designated in the customer request 101.
FIG. 10 shows a system requirement list 111 generated by the automatic request generation unit 110.

The automatic product selection unit 120 extracts security function requirements “FAU 1 to 5”, “FIA 1 and 2”, and “FDP 1 to 3” from the system requirement list 111 of FIG.
The automatic product selection unit 120 searches the corresponding product table 171 in FIG. 6 and specifies the corresponding products “products C and D” having the security function requirement “FAU1”. The automatic product selection unit 120 similarly specifies corresponding products for the remaining security function requirements “FAU 2 to 5”, “FIA 1 and 2”, and “FDP 1 to 3”.
The product automatic selection unit 120 generates a corresponding product list A122 (see FIG. 11) in which security function requirements and corresponding products are associated with each other.
The product automatic selection unit 120 generates a corresponding product list B123 (see FIG. 12) by listing the corresponding products “products A to D” shown in the corresponding product list A122.

  Returning to FIG. 9, the description of the security product sales support method will be continued.

  It progresses to S140 after S130.

In S140, the automatic product selection unit 120 extracts a combination candidate of the corresponding product from the corresponding product group shown in the corresponding product list B123, and generates a product combination candidate list 124 using the extracted combination candidate of the corresponding product as a list.
The combination candidate of the corresponding product extracted from the corresponding product group is configured by at least one of the corresponding products included in the corresponding product group.

FIG. 13 is a diagram showing a product combination candidate list 124 generated by the automatic product selection unit 120 in the first embodiment.
The product combination candidate list 124 according to the first embodiment will be described below with reference to FIG.

The product combination candidate list 124 indicates combinations of corresponding products extracted from the corresponding product list B123.
The product combination candidate list 124 is generated by the product automatic selection unit 120.

  The automatic product selection unit 120 combines the four corresponding products “products A to D” included in the corresponding product list B123 shown in FIG. 12 to identify 15 corresponding product combination candidates, and identifies the corresponding corresponding product combination candidates. And a product combination candidate list 124 (see FIG. 13).

  Returning to FIG. 9, the description of the security product sales support method will be continued.

  After S140, the process proceeds to S150.

In S <b> 150, the product automatic selection unit 120 selects an available combination from among the combination candidates of the corresponding products included in the product combination candidate list 124 based on the connectable product table 172. The usable combination candidates are combinations of products that can be connected to each other. If there is a product that is required to use the corresponding product, that required product shall be included in the available combinations. The essential products are defined in the connectable product table 172, for example.
The product automatic selection unit 120 generates a product combination list 121 by listing the selected available combinations, and outputs the generated product combination list 121.
For example, the product automatic selection unit 120 stores the product combination list 121 in the storage device, displays it on the display device, and prints it using the printer device.

FIG. 14 is a diagram showing a product combination list 121 generated by the product automatic selection unit 120 in the first embodiment.
The product combination list 121 in the first embodiment will be described below with reference to FIG.

The product combination list 121 indicates available combinations among the combinations of corresponding products included in the product combination candidate list 124.
The product combination list 121 is generated by the product automatic selection unit 120.

The product automatic selection unit 120 searches the connectable product table 172 (see FIG. 7) for the products A to D included in the corresponding product list B123 (see FIG. 12), and the product A and the product D cannot be used in combination. Is identified. Moreover, the product automatic selection part 120 specifies that the products A to C and the products B to D can be used in combination.
The product combination list 121 excludes combination candidates including the product A and the product D that cannot be used in combination from the product combination candidate list 124 (see FIG. 13). The product combination list 121 generates a product combination list 121 (see FIG. 14) by listing the remaining combination candidates as available combinations.

  Returning to FIG. 9, the description of the security product sales support method will be continued.

  After S150, the process proceeds to a function coverage calculation process (S200) and a security feasibility calculation process (S300).

In the function coverage calculation process (S200), the function coverage calculation unit 130 is covered by combinations of corresponding products shown in the product combination list 121 among the security function requirements of the customer request 101 shown in the corresponding product list A122. Identify security functional requirements and missing security functional requirements.
Details of the function coverage calculation process (S200) will be described in the second embodiment.

In the security feasibility calculation process (S300), the security feasibility calculation unit 140 performs an operation & data for which security is guaranteed and an operation & data for which security is not guaranteed in the combination of the corresponding products shown in the product combination list 121. Identify.
Details of the security feasibility calculation process (S300) will be described in the third embodiment.

  With the above-described sales support method for security products, it is possible to select a combination of security products that meet the customer request 101 and provide the selected combination as a list (product combination list 121).

FIG. 15 is a diagram illustrating an example of hardware resources of the security product sales support system 100 according to the first embodiment.
In FIG. 15, the security product sales support system 100 includes a CPU 911 (Central Processing Unit) (also referred to as a microprocessor or a microcomputer). The CPU 911 is connected to the ROM 913, the RAM 914, the communication board 915, the display device 901, the keyboard 902, the mouse 903, the drive device 904, the printer device 906, and the magnetic disk device 920 via the bus 912, and controls these hardware devices. . The drive device 904 is a device that reads and writes a storage medium such as an FD (Flexible Disk Drive), a CD (Compact Disc), and a DVD (Digital Versatile Disc).

  The communication board 915 is wired or wirelessly connected to a communication network such as a LAN (Local Area Network), the Internet, or a telephone line.

  The magnetic disk device 920 stores an OS 921 (operating system), a window system 922, a program group 923, and a file group 924.

  The program group 923 includes programs that execute the functions described as “units” in the embodiment. The program is read and executed by the CPU 911. That is, the program causes the computer to function as “to part”, and causes the computer to execute the procedures and methods of “to part”.

  The file group 924 includes various data (input, output, determination result, calculation result, processing result, etc.) used in “˜part” described in the embodiment.

  In the embodiment, arrows included in the configuration diagrams and flowcharts mainly indicate input and output of data and signals.

  In the embodiment, what is described as “to part” may be “to circuit”, “to apparatus”, and “to device”, and “to step”, “to procedure”, and “to processing”. May be. That is, what is described as “to part” may be implemented by any of firmware, software, hardware, or a combination thereof.

  In the first embodiment, for example, the following security product sales support system 100 has been described.

The security product sales support system 100 includes a DB (industry standard specifications DB 160) in which industry standards and standards are associated with security requirements, and a DB (product STDB 170) in which security products are associated with security requirements.
The security product sales support system 100 uses a security requirement to select a security product that satisfies the requirement for an industry standard or standard.

  By automating product selection based on customer requirements, which was previously done manually, the workload for creating proposal materials for customers was reduced, the creation time was shortened, and the accuracy of the proposal materials was improved. It becomes possible to prevent human error.

Embodiment 2. FIG.
A function coverage calculation process (S200) of the security product sales support method (see FIG. 9) will be described.

  The function coverage calculating unit 130 inputs the product combination list 121 generated by the product automatic selection unit 120.

For each combination of corresponding products shown in the product combination list 121, the function coverage calculating unit 130 determines that at least one of the corresponding products included in the combination of the corresponding products is the security of the customer request 101 indicated in the corresponding product list A122. Determine whether functional requirements are present.
Hereinafter, this determination is referred to as insufficient security function determination.

The function coverage degree calculation unit 130 generates a coverage function list 131 by listing the results of the insufficient security function determination, and outputs the generated coverage function list 131.
For example, the function coverage calculating unit 130 stores the coverage function list 131 in a storage device, displays it on a display device, and prints it using a printer device.

FIG. 16 is a diagram illustrating an exhaustive function list 131 generated by the functional coverage degree calculation unit 130 in the second embodiment.
The coverage function list 131 in the second embodiment will be described below with reference to FIG.

The comprehensive function list 131 shows the security function requirements of the combination of the corresponding products shown in the product combination list 121 among the security function requirements of the customer request 101 shown in the corresponding product list A 122 and the security function requirements that are lacking. Yes.
The coverage function list 131 is generated by the function coverage level calculation unit 130.

  The function coverage calculating unit 130 selects the product combination 1 “products A to C” from the product combination list 121 (see FIG. 14).

The function coverage calculating unit 130 includes a security function provided only for “product D” not included in the product combination 1 “products A to C” of the security function requirements 1 to 10 shown in the corresponding product list A 122 (see FIG. 11). The requirement 8 “FDP1” and the security function requirement 10 “FDP3” are specified.
The specified security function requirement 8 “FDP1” and security function requirement 10 “FDP3” are security function requirements that are insufficient when the product combination 1 “products A to C” is adopted.
The remaining security function requirements 1 to 7 and 9 are security function requirements obtained by adopting the product combination 1 “products A to C”.

  The function coverage calculating unit 130 adds a “coverage function” field to the corresponding product list A 122 and sets whether or not the security function requirement is insufficient in the “coverage function” field. A function list 131 (see FIG. 16) is generated.

  The function coverage calculating unit 130 generates the coverage function list 131 for the remaining product combinations 2 to 12 shown in the product combination list 121 as with the product combination 1.

By generating the comprehensive function list 131, it is possible to notify the user of insufficient security function requirements.
For example, the user can compensate for the missing security function requirement by newly developing only the functional module having the missing security function requirement.

  In the second embodiment, for example, the following security product sales support system 100 has been described.

A security product that satisfies the requirements of the industry standards and standards is selected, and the comprehensiveness (covered function list 131) of the security function requirements corresponding to the requirements is shown.
In response to the requirements of industry standards and standards, select security products that satisfy the requirements, and indicate the insufficient security function requirements that do not meet the requirements.

  By automatically calculating the comprehensiveness of security functional requirements, the workload in creating proposal materials to customers is reduced, the creation time is shortened, the accuracy of the proposal materials is improved, and human error Can be prevented.

Embodiment 3 FIG.
The security feasibility calculation process (S300) of the security product sales support method (see FIG. 9) will be described.

  Based on the operation & data table 173 described below, the security feasibility calculation unit 140 performs an operation & data for which the combination of corresponding products in the product combination list 121 guarantees security and an operation & data for which security is not guaranteed. Identify.

FIG. 17 is a diagram illustrating a specific example of the operation & data table 173 stored in the product STDB 170 according to the third embodiment.
The operation & data table 173 according to the third embodiment will be described below with reference to FIG.

  The operation & data table 173 is stored in the product STDB 170 in advance.

  The operation & data table 173 is data in which “corresponding product”, “operation & data”, “I / F”, “I / F method”, “protection status”, and “SFR” are associated with each other.

The corresponding product indicates the type and function “realized function” and “product name” of the corresponding product.
The operation & data indicates an execution process “operation” executed by the corresponding product and “data” processed by the execution process.
I / F indicates whether an interface for execution processing is an external interface or an internal interface.
The I / F method indicates the type of network used in the execution process.
The protection status indicates whether the security of data processed by the execution process is guaranteed.
SFR indicates security function requirements related to execution processing. The SFR is determined for each operation & data. If the operation & data is the same, the SFR is the same even if the corresponding products are different.

FIG. 18 is a flowchart of the security feasibility calculation process (S300) in the third embodiment.
19 and 20 are excerpt diagrams of the operation & data table 173 in the third embodiment.
The security feasibility calculation process (S300) in the third embodiment will be described below with reference to FIGS.

In S <b> 310, the security feasibility calculation unit 140 selects one combination of corresponding products from a plurality of combinations of corresponding products shown in the product combination list 121.
Hereinafter, the combination of the corresponding products selected in S310 is referred to as “selected combination”.
It progresses to S320 after S310.

  In S320, the security feasibility calculation unit 140 searches the operation & data table 173 and identifies operations & data common to a plurality of corresponding products included in the selected combination.

For example, it is assumed that “Product C” and “Product D” are included in the selected combination.
The security feasibility calculation unit 140 refers to the operation & data table 173 shown in FIG. 17, and the operation & data “pattern update, pattern” is operation & data common to “product C” and “product D”. Identify that.

Hereinafter, the common operation & data specified in S320 is referred to as “common processing”.
In addition, corresponding products that are included in the selected combination and that execute common processing are referred to as “common processing products”.
It progresses to S330 after S320.

In S330, the security feasibility calculation unit 140 searches the operation & data table 173 and identifies the protection status of the common process for each common process product.
The security feasibility calculation unit 140 determines whether or not the protection status of all common processing products is “protected” with respect to the common processing.
If all the protection statuses are “protected” (YES), the process proceeds to S342.
If at least one of the protection statuses is “no protection” (NO), the process proceeds to S340.

In S340, the security feasibility calculation unit 140 searches the operation & data table 173 and identifies one or a plurality of SFRs related to the common process.
Hereinafter, each SFR specified in S340 is referred to as “related SFR”.
It progresses to S341 after S340.

In S341, the security feasibility calculation unit 140 determines whether or not a related SFR is included in a plurality of security function requirements (required SFR group) indicated in the corresponding product list A122.
When the related SFR is included in the request SFR group (YES), the process proceeds to S343.
When the related SFR is not included in the request SFR group (NO), the process proceeds to S342.

In S342, the security feasibility calculation unit 140 determines that the security for the common process is guaranteed by the selected combination (security feasibility “OK”).
It progresses to S350 after S342.

In S343, the security feasibility calculation unit 140 determines that security for the common process is not guaranteed by the selected combination (security feasibility “NG”).
It progresses to S350 after S343.

  For example, when the common processing product is “product C, D” and the common processing is “pattern update, pattern”, the protection status in FIG. 19 is both “protected” (S330: YES), and security is realized. The sex is “OK” (S342).

For example, if the common processing product is “product C, E” and the common processing is “pattern update, pattern”, the protection status is “no protection” for “product E” in FIG. 20 (S330: NO). The related SFR is “FAU2” (S340).
When the related SFR “FAU2” is included in the requested SFR group (S341: YES), the security feasibility is “NG” (S343).
When the related SFR “FAU2” is not included in the requested SFR group (S341: NO), the security feasibility is “OK” (S342).

When a plurality of common processes of the selected combination are identified in S320, S330 to S343 are executed for each identified common process.
Then, after determining the security feasibility for all the common processes specified for the selected combination, the process proceeds to S350.

In S350, the security feasibility calculation unit 140 generates a security feasibility list 141 by listing the security feasibility of the selected combination for each common process, and outputs the generated security feasibility list 141.
For example, the security feasibility calculation unit 140 stores the security feasibility list 141 in a storage device, displays it on a display device, and prints it using a printer device.

FIG. 21 is a diagram showing a security feasibility list 141 generated by the security feasibility calculation unit 140 in the third embodiment.
For example, the security feasibility calculation unit 140 generates a security feasibility list 141 as shown in FIG.
“Result” indicates security feasibility, “Operation & data” indicates common processing, and “SFR” indicates related SFR (or related SFR included in the request SFR group).

  Returning to FIG. 18, the description of the security feasibility calculation process (S300) will be continued.

  It progresses to S360 after S350.

In S <b> 360, the security feasibility calculation unit 140 determines whether a combination of corresponding products that have not been selected remains in the product combination list 121.
When the combination of the corresponding products that have not been selected remains (YES), the process returns to S310, selects the combination of the corresponding products that have not been selected, and executes S320 to S350 for the selected combination of the corresponding products.
If all combinations of compatible products have been selected (NO), the security feasibility calculation process (S300) ends.

  22 and 23 are conceptual diagrams regarding security feasibility in the third embodiment.

Through the security feasibility calculation process (S300), “protection status” can be determined for “operation” and “data” (see FIG. 22).
In the above processing, “I / F”, “operator (authority, etc.)” and the like may be added to the security feasibility determination conditions. For example, if the operation is an internal I / F or the operation is limited to an administrator, the security feasibility is set to “OK”.

  Through the security feasibility calculation process (S300), an operation for accessing the external server D from the internal terminal A through the firewall can be specified as an operation whose security is not guaranteed (see FIG. 23).

  In the third embodiment, for example, the following security product sales support system 100 has been described.

Select security products that meet the requirements of industry standards and standards.
The security product sales support system 100 simulates whether the security corresponding to the request can be secured by the selected security product.

  By verifying the security function requirements corresponding to the request and the security product information (operation & data table 173), it is possible to determine whether security can be ensured for each operation & data of the security product.

  100 Sales Support System for Security Products, 101 Customer Request, 110 Automatic Request Generation Unit, 111 System Requirements List, 120 Product Automatic Selection Unit, 121 Product Combination List, 122 Compatible Product List A, 123 Compatible Product List B, 124 Product Combination Candidate list, 130 function coverage calculation unit, 131 coverage function list, 140 security feasibility calculation unit, 141 security feasibility list, 150 classification information DB, 160 industry standard standards DB, 161 industry standard standards requirement table, 162 security Functional requirement table, 170 product STDB, 171 compatible product table, 172 connectable product table, 173 operation & data table, 901 display device, 902 keyboard, 903 mouse, 904 drive device, 906 printer device, 9 11 CPU, 912 bus, 913 ROM, 914 RAM, 915 communication board, 920 magnetic disk device, 921 OS, 922 window system, 923 program group, 924 file group.

Claims (6)

A security function database unit that stores data indicating a plurality of security functions corresponding to the system type representing the type of system as security function data;
For each security function, data indicating a security product having the security function is stored as security product function data, and security product combination data indicating a plurality of predetermined combinations of security products as permitted combinations of security products is stored. Product database department;
A target security function group specifying unit that inputs a specific system type and specifies a plurality of security functions corresponding to the input system type as a target security function group based on the security function data;
Target security product group for identifying a plurality of security products having at least one security function included in the target security function group specified by the target security function group specifying unit as the target security product group based on the security product function data A specific part,
A plurality of combinations of security products consisting of at least two security products included in the target security product group specified by the target security product group specifying unit are specified as security product combination candidates, and a plurality of combination candidates of the specified security products are selected. Of these, security product combination candidates that are indicated as permitted combinations of security products in the security product combination data are identified as security product target combinations, and information indicating the identified security product target combinations is output as security product combination information A security product information providing apparatus comprising a product combination specifying unit. The security product information providing device further includes:
Of the security functions included in the target security function group, the security functions other than the security functions included in the target combination of the security products are identified as insufficient security functions, and insufficient security function information indicating the identified insufficient security functions is output. The security product information providing apparatus according to claim 1, further comprising a function specifying unit. The security product database unit stores security product processing data indicating an execution process executed by the security product for each security product and a protection status indicating whether security of the processing data processed by the execution process is guaranteed. And
The security product information providing device further includes:
A plurality of security products that execute a common execution process as a common process among a plurality of security products included in the target combination of the security products are identified as a common process product group based on the security product process data, and the common process A security unguaranteed process determination is made based on the security product process data to determine whether a security product that does not guarantee the security of the processed data is included in the common process product group. The security product information providing apparatus according to claim 1, further comprising a security assurance determination unit that outputs information including the result as security assurance information. The security product database unit stores execution processing function data in which execution processing and security functions related to execution processing are associated with each other,
When the security assurance determination unit determines that a security product that does not guarantee the security of the processing data processed by the common processing is included in the common processing product group, the security processing related to the common processing is changed to the execution processing function. A security unguaranteed function is specified based on data, a security unguaranteed function determination is performed to determine whether the target security function group includes the security unguaranteed function, and the result of the security unguaranteed function determination is included. 4. The security product information providing apparatus according to claim 3, wherein the information is output as the security assurance information. A security function database unit that stores data indicating a plurality of security functions corresponding to a system type representing a system type as security function data, and data indicating a security product having the security function for each security function. Security product information providing method of a security product information providing apparatus comprising: a security product database unit storing security product combination data that stores a plurality of predetermined combinations of security products as permitted combinations of security products. In
The target security function group specifying unit inputs a specific system type, specifies a plurality of security functions corresponding to the input system type as a target security function group based on the security function data,
The target security product group specifying unit selects a plurality of security products having at least one security function included in the target security function group specified by the target security function group specifying unit based on the security product function data. Identified as a group,
The security product combination specifying unit specifies a plurality of combinations of security products including at least two security products included in the target security product group specified by the target security product group specifying unit as security product combination candidates, and specifies the specified security. Among a plurality of product combination candidates, a security product combination candidate indicated as a permitted combination of security products in the security product combination data is identified as a target combination of security products, and information indicating the specified target combination of security products is security information A security product information providing method for a security product information providing apparatus, characterized in that the product is output as product combination information.   A security product information providing program for causing a computer to execute the security product information providing method according to claim 5.

Images