Support system, support method and support program

Abstract

To provide a new technique for creating security requirements without imposing a burden on users. [Solution] A support system for supporting creation of security requirements, comprising: The support system includes a reception unit, an extraction unit, a questioning unit, and a generation unit, The reception unit receives a request regarding a security requirement from a user, The extraction unit extracts necessary information required to generate the security requirements based on the request, The questioning unit asks a question regarding the necessary information, The generating unit generates security requirements based on the request and the answers to the questions.

Description

[Technical field]

[0001] The present invention relates to an assistance system, an assistance method, and an assistance program. [Background technology]

[0002] Conventionally, there exists a technique for supporting the creation of security requirements.

[0003] For example, Patent Document 1 discloses a technique for inputting a security standard and a security level and displaying security requirements and countermeasures. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2023-45963 A Summary of the Invention [Problem to be solved by the invention]

[0005] Recently, there is an increasing demand for users to create their own security requirements without imposing a burden on themselves, based on vague requests, etc. However, while the technology of Patent Document 1 allows users to input security standards and display security requirements, it does not allow users to create security requirements based on vague requests.

[0006] The present invention has been made in consideration of the above-mentioned circumstances, and an object of the present invention is to provide a new technique for creating security requirements without imposing a burden on the user. [Means for solving the problem]

[0007] [1] A support system for supporting the creation of security requirements, comprising: The support system includes a reception unit, an extraction unit, a questioning unit, and a generation unit, The reception unit receives a request regarding a security requirement from a user, The extraction unit extracts necessary information required to generate the security requirements based on the request, The questioning unit asks a question regarding the necessary information, The generating unit generates security requirements based on the request and the answers to the questions. Support system.

[0008] [8] A method for supporting the creation of security requirements, comprising: The support system includes a reception unit, an extraction unit, a questioning unit, and a generation unit, a step of the reception unit receiving a request regarding a security requirement from a user; The extraction unit extracts necessary information required for generating the security requirements based on the request; a step of the questioning unit asking a question regarding the necessary information; The generating unit generates security requirements based on the request and the answers to the questions. How to help.

[0009] [9] A support program for assisting in the creation of security requirements, comprising: A computer is caused to function as a reception unit, an extraction unit, a questioning unit, and a generation unit; The reception unit receives a request regarding a security requirement from a user, The extraction unit extracts necessary information required to generate the security requirements based on the request, The questioning unit asks a question regarding the necessary information, The generating unit generates security requirements based on the request and the answers to the questions. Support programs.

[0010] With this configuration, it is possible to generate security requirements even for vague requests, allowing users to create security requirements without imposing a burden (time, effort, stress, etc.).

[0011] [2] The support system includes a memory unit, The storage unit stores security guidelines; The extraction unit extracts the security guideline based on the request, The questioning unit asks a question regarding the security guideline. [1] The support system described in the above.

[0012] With this configuration, even users without specialist knowledge can generate their own security requirements using general security guidelines, or generate appropriate security requirements by combining existing authoritative security guidelines.

[0013] [3] The generating unit generates a custom list including items in a hierarchical structure based on the request and the answers to the questions, and further generates security requirements based on the custom list and the answers to the questions about the items. The support system according to [1] or [2].

[0014] With this configuration, it is possible to generate security requirements that meet the needs of the user while minimizing the burden on the user.

[0015] [4] The generating unit generates mixed structure information, which is a structure in which items of different granularities are mixed, based on the request and the answers to the questions, and further generates security requirements based on the mixed structure information and the answers to the questions about the items. The support system according to [1] or [2].

[0016] With this configuration, it is possible to generate security requirements that meet the needs of the user while minimizing the burden on the user.

[0017] [5] the hierarchical structure includes a plurality of items; the interrogator asks questions about items for generating a custom list; when the generation unit receives an answer to a question regarding the item, the generation unit generates a custom list including sub-items indicating more detailed requirement information than the item in the hierarchical structure. The support system according to [3] or [4].

[0018] With this configuration, it is possible to generate detailed security requirements that meet the needs of the user while minimizing the burden on the user.

[0019] [6] The assistance system includes a determination unit, The determination unit determines that answers regarding all items included in the custom list have been received, The interrogation unit generates a security requirement based on the determination result. [5] The support system described in.

[0020] With this configuration, it is possible to switch from a mode for accepting user requests to a mode for generating security requirements.

[0021] [7] The extraction unit, the question unit, and the generation unit are large-scale language models. The support system according to any one of [1] to [6].

[0022] With this configuration, it is possible to extract necessary information, ask questions to the user, and generate security requirements with high accuracy. Effect of the Invention

[0023] According to the present invention, a new technique for creating security requirements can be provided without imposing a burden on the user. [Brief description of the drawings]

[0024] [Figure 1] FIG. 1 is a block diagram showing a configuration of a support system according to an embodiment of the present invention. [Diagram 2] FIG. 2 is a diagram showing a hardware configuration according to the present embodiment. [Diagram 3] FIG. 2 is a block diagram showing functional components according to the embodiment. [Figure 4] 4 shows an example of a data configuration stored in a storage unit in the present embodiment. [Diagram 5] 4 shows an example of a data configuration stored in a storage unit in the present embodiment. [Figure 6] 4 shows an example of a data configuration stored in a storage unit in the present embodiment. [Figure 7] FIG. 1 is a schematic image diagram of a support system according to an embodiment of the present invention. [Figure 8] 4 is a flowchart of a process for supporting the creation of security requirements in the present embodiment. [Figure 9] 5A to 5C are diagrams for explaining details of the text discrimination process in the embodiment. [Figure 10] 5A to 5C are diagrams for explaining details of the text classification process in the present embodiment. [Figure 11] FIG. 13 is an image diagram of a structure in which items of different granularity are mixed in this embodiment. [Figure 12] 13 illustrates an example of an exchange between a user and a support device via a user terminal in this embodiment. [Figure 13] FIG. 4 is a diagram for explaining an example of security level calculation in the embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0025] The support system of the present invention will be described below with reference to the drawings. The drawings show preferred embodiments. However, the present invention may be embodied in many different forms and is not limited to the embodiments set forth herein.

[0026] For example, the configuration, operation, etc. of the support system will be described in this embodiment, but the same effects can be achieved by an executed method (step), device, computer program, etc. The program in this embodiment may be provided as a non-transient computer-readable recording medium, may be provided so as to be downloadable from an external server, or may be started in an external computer to implement its functions on a client terminal (so-called cloud computing).

[0027] In addition, in this embodiment, the term "unit" may include, for example, a combination of hardware resources implemented by a circuit in the broad sense and software information processing that can be specifically realized by these hardware resources. In this embodiment, "information" is represented by, for example, a physical value of a signal value representing a voltage or current, a high or low signal value as a binary bit collection consisting of 0 or 1, or a quantum superposition (so-called quantum bit), and communication and calculation can be performed on a circuit in the broad sense.

[0028] A circuit in the broad sense is a circuit realized by appropriately combining a circuit, circuitry, a processor, a memory, etc. In other words, it includes a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), an LSI (Large Scale Integration), an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array), a SoC (System on a Chip), etc.

[0029] <System Overview> Fig. 1 is a block diagram showing the configuration of a support system in this embodiment. As shown in Fig. 1, the support system 0 includes a support device 1 and a user terminal 2. The support device 1 is configured to be able to communicate with the user terminal 2 via a network NW. The support device 1 operates as a server, and the user terminal 2 operates as a client terminal.

[0030] The support device 1 receives questions, requests, and answers to questions posed to the user from the user via the user terminal 2. The support device 1 generates security requirements based on the information received via the user terminal 2.

[0031] A general-purpose server computer, a personal computer, or the like can be used as the support device 1. Also, the support device 1 can be configured using a plurality of computers.

[0032] The user terminal 2 is a terminal for a user who wishes to create security requirements to input questions, requests, and answers to questions from the support device 1. As the user terminal 2, a terminal device such as a smartphone, a tablet terminal, or a personal computer can be used. There may be multiple user terminals 2.

[0033] In this embodiment, the network NW is an IP (Internet Protocol) network, but there is no restriction on the type of communication protocol, and further, there is no restriction on the type and scale of the network.

[0034] <Hardware configuration> Fig. 2 is a hardware configuration diagram. As shown in Fig. 2(a), the information processing device 10 (support device 1) has a control unit 101, a storage unit 102, and a communication unit 103, which are used to perform the functions of each unit and each process.

[0035] The control unit 101 includes one or more processors such as a CPU (Central Processing Unit), and controls the overall operation and processing of the information processing device 10 by executing the support program related to the present invention, an OS (Operating System), browser software, middleware, and other applications.

[0036] The storage unit 102 is a hard disk drive (HDD), a solid state drive (SSD), a read only memory (ROM), a random access memory (RAM), etc., and stores the assistance program according to the present invention and data used when the control unit 101 executes processing based on the program. The control unit 101 executes processing based on the assistance program stored in the storage unit 102, thereby realizing a functional configuration described below.

[0037] The communication unit 103 executes communication control with the network NW, and performs input required to operate the information processing device 10 and output related to the operation results.

[0038] As shown in FIG. 2(b), the terminal device 9 (user terminal 2) has a control unit 91, a storage unit 92, a communication unit 93, an input unit 94, and an output unit 95, and is used to cause each unit and each process to function.

[0039] The control unit 91 of the terminal device 9 includes one or more processors such as a CPU, and controls the overall operation processing of the terminal device 9. The storage unit 92 of the terminal device 9 is an HDD, SSD, ROM, RAM, or the like, and stores the above-mentioned applications and data used when the control unit 91 executes processing based on a program.

[0040] A communication unit 93 of the terminal device 9 controls communication with the network NW. An input unit 94 of the terminal device 9 is a mouse, keyboard, or the like, and inputs operation requests from a user / provider to the control unit 91. An output unit 95 of the terminal device 9 is a display, or the like, and displays the results of processing by the control unit 91, etc.

[0041] <Functional components> As shown in FIG. 3, the support device 1 includes a receiving unit 11, an extracting unit 12, a questioning unit 13, a generating unit 14, a determining unit 15, and an updating unit 16.

[0042] The arrangement of these functional components is just an example, and it is also possible to realize these functional components in multiple computers to configure the support system 0. For example, a part of the functional configuration of the support device 1 may be arranged in the user terminal 2 and one or more devices configured to be able to communicate with the support device 1.

[0043] In addition, a part or all of the functional configuration of the support device 1 may be a natural language processing model (NLP (Natural Language Processing)). For example, the extraction unit 12, the question unit 13, and the generation unit 14 are natural language processing models, and are preferably large-scale language models (LLM (Large Language Models)). The natural language processing model realizes processing of data input as a natural language by a computer.

[0044] <Data Structure> 4 to 6 are examples of data configurations stored in the storage unit in this embodiment. The storage unit of the support device 1 stores security guideline information, item information, information by requirement information, custom list information, and the like.

[0045] The arrangement of each piece of data is an example, and some or all of the data stored in the storage unit of the support device 1 may be stored in one or more devices configured to be able to communicate with the user terminal 2 and the support device 1.

[0046] Security guideline information is information on security guidelines that have already been widely distributed and known both domestically and internationally. As shown in Figure 4(a), security guideline information includes the name of the guideline, the publication year of the guideline, guideline data, etc., and is managed by guideline ID for each security guideline.

[0047] Since the security guideline information includes the publication year of the guideline, the user can specify the publication year to generate security requirements that are a combination of guidelines as desired by the user.

[0048] The guideline data may be in the form of a document file, an image file, etc. The security guideline information may also include a storage destination of the guideline data.

[0049] Furthermore, the security guideline information may include information about the contents of the security guideline, such as information about information assets described in the guideline, information about the use of the site, and information about the number of people involved.

[0050] Item information is information related to the requirement items described in the security guidelines. As shown in Figure 5(a), item information includes major items, medium items, minor items, etc., and is managed by guideline ID. Item information is structured in a way that mixes items of different granularity based on the content of each guideline. Specifically, item information is structured in a hierarchical structure based on the content of each guideline.

[0051] In this embodiment, it is represented in a hierarchical structure of three levels (major items, medium items, small items), but the number of levels is not limited. For example, in Fig. 5(a), the major items are composed of requirement information related to system architecture and information management, the medium items are composed of requirement information such as formulation of information security policy and access control, and the small items are composed of requirement information such as setting of access authority and user management.

[0052] A medium item is a subitem that indicates more detailed requirement information than a large item in a hierarchical structure, and is a finer-grained item than a large item. For example, as shown in Figure 5(a), requirement information of a large item (information management) may include multiple requirement information of medium items (formulation of information security policy, implementation of risk assessment, access control), and requirement information of a medium item (access control) may include multiple requirement information of small items (setting of access authority, periodic review of access authority, physical access management). Requirement information belonging to a medium item is finer-grained requirement information included in requirement information belonging to a certain large item.

[0053] User information is information about a user who wishes to create security requirements. As shown in Fig. 5(b), the user information includes the user's name, the name of the company to which the user belongs, the address of the user or the company to which the user belongs, contact information, etc., and is managed by user ID. The user information may include information about the user's occupation, the industry of the company to which the user belongs, etc., and may be used to create security requirements.

[0054] The requirement information is a summary of the requirement information related to the items described in the stored security guideline. The requirement information includes medium items, small items, etc., as shown in Figure 5(c), and is managed by the requirement information ID.

[0055] For example, the guideline IDs "GL00001" and "GL00003" in Fig. 5(a) include the medium-level requirement information "access control." On the other hand, the access control of the guideline IDs "GL00001" and "GL00003" includes different requirement information of the small items.

[0056] For example, if different security guidelines stored in the storage unit include the same medium item, the respective sub-items can be grouped by that medium item, as shown in Fig. 5(c). In this way, when a request to strengthen "access control" is received from a user, a security requirement can be created that includes items at a lower level than the item included in the different security guideline.

[0057] In other words, it is possible to create complete security requirements using multiple related security guidelines. Also, if there is overlap in content between different security guidelines, the same content may be grouped together.

[0058] In addition, the storage unit may store information by cloud type that summarizes information by cloud type. Security requirements differ depending on the cloud type. For example, security guidelines differ for EC (Electronic Commerce), remote access, in-house portals, etc., and further, multiple security guidelines exist for each. By summarizing security guidelines by these cloud types, when a specific cloud type is received from a user, it is possible to create complete security requirements using multiple related security guidelines.

[0059] Custom list information is information about custom lists for creating security requirements, which are created based on questions, requests, and answers from users. As shown in Fig. 6(a), custom list information includes custom lists of major items, medium items, minor items, etc. of security requirements desired by users, and is managed by custom list ID. Furthermore, by including user IDs in the custom list information, it is possible to manage which users desire security requirements.

[0060] <Overview> 7 is a schematic image diagram of the support system in this embodiment. Using this schematic image diagram, an image of supporting the creation of security requirements will be explained.

[0061] The user inputs and transmits requests regarding security requirements, questions regarding security requirements, and answers to questions from the support device 1 via the user terminal 2 (see (A)). The support device 1 stores the information received via the user terminal 2 in a storage unit.

[0062] The support device 1 extracts necessary information required to generate security requirements based on the information received via the user terminal 2, and generates a question regarding the necessary information (see (B)). For example, the support device 1 receives a request via the user terminal 2 such as "I would like to install a secure cloud in a new hospital," extracts security guidelines for medical standards, and generates a question such as "Is it okay to comply with the security guidelines for medical standards?"

[0063] The support device 1 sends a question to the user terminal 2 to ask the user a question (see (C)). The support device 1 and the user repeatedly perform the exchanges (processes) (A), (B), and (C) to create security requirements.

[0064] The support device 1 repeats the interactions (processing) of (A), (B), and (C), and when it determines that it has received all the information necessary to generate security requirements that meet the user's needs, it generates the security requirements and transmits them to the user.

[0065] <Processing Flowchart> FIG. 8 is a flowchart of a process for supporting the generation of security requirements in this embodiment.

[0066] <Acceptance of requests> In step S801, the reception unit 11 receives a request for security requirements from a user. Specifically, the reception unit 11 receives a request for security requirement generation from the user via the user terminal 2. The request received from the user may include a question.

[0067] For example, the reception unit 11 receives requests from users including information on the installation site, such as "I would like to install a secure cloud in a new hospital" or "I would like to introduce a secure cloud into a factory." In addition, the reception unit 11 receives requests including the purpose of the system, the use of the system, the scale of the system, etc. The reception unit 11 also receives questions from users, such as "Please tell me what security requirements you recommend."

[0068] The reception unit 11 receives, as requests, both a genuine request for generating security requirements and a question regarding security requirements, etc. The reception unit 11 may alternately receive each of them, or may receive both of them in a sporadic manner.

[0069] <Extracting necessary information> In step S802, the extraction unit 12 extracts necessary information required for generating security requirements based on the request. The extraction unit 12 determines whether the content received from the user is a question or a request (not a question).

[0070] The extraction unit 12 extracts keywords from information such as text received from the user, and compares the extracted keywords with information previously stored in the storage unit to determine whether the content received from the user is a question or a request. Furthermore, the extraction unit 12 may generate synonymous words derived from the extracted keywords and determine whether the content received from the user is a question or a request. Alternatively, the extraction unit 12 may be a machine learning model that has been trained in advance and uses the information received from the user as an input to determine whether the content received from the user is a question or a request.

[0071] If the content received from the user is a question, the extraction unit 12 generates an answer to the question. Also, if the content received from the user is a request, the extraction unit 12 extracts necessary information required to generate security requirements.

[0072] For example, when the reception unit 11 receives a request from a user to "install a secure cloud in a new hospital," the extraction unit 12 extracts security guidelines related to medical care as security guidelines necessary for generating security requirements.

[0073] 9(a) is a diagram for explaining the details of the sentence discrimination process in this embodiment. A user inputs a request including a question via the user terminal 2. The storage unit stores, for example, "Please tell me" as a keyword for determining a question, and "Please include" or "This is a request" as keywords for determining a request.

[0074] In step S901, the extraction unit 12 determines whether the user input is a question or a request, based on the keywords stored in the storage unit. In step S902, if the extraction unit 12 determines that the user input is a question, it performs a process of grasping the content of the question and generating an answer. In step S903, if the extraction unit 12 determines that the user input is a request, it performs a process of extracting security guidelines for conversion into security requirements (such as asking the user a question).

[0075] 10A is a diagram for explaining details of the text classification process (step S901 in FIG. 9A) in this embodiment. In step S1011, the extraction unit 12 performs a morphological analysis on the received content (text, etc.).

[0076] In step S1012, the extraction unit 12 determines whether the judgment in step S1013 has been made for all of the analyzed morphemes, and if the judgment has been made for all morphemes, it determines that the received content is not a question but a (normal) request, outputs "This is a request" as judgment result 2, and analyzes the content of the request.

[0077] In step S1013, in order to determine whether the received content is a question, the extraction unit 12 determines whether the analyzed morpheme corresponds to the basic form of a verb related to a question, such as "teach." If the extraction unit 12 determines that the analyzed morpheme corresponds to the verb, the process proceeds to S1014.

[0078] In step S1014, the extraction unit 12 determines whether the morpheme following the basic form of the verb related to the determined question corresponds to "will / conjecture form (form expressing will / conjecture)". When the received content is a question, the verb follows the "will / conjecture form", so the extraction unit 12 makes such a determination. When the extraction unit 12 determines that the following corresponds to the "will / conjecture form", it may output "This (the received content) is a question" as the determination result 1.

[0079] There are multiple possible verbs related to questions, and the appropriate "will / inference form" for a question consisting of the verb differs depending on each verb. The memory unit stores a certain number (e.g., 10 types of sentences) of question sentences consisting of multiple verbs for asking questions (e.g., teach, instruct, ask, etc.) and ending with "will / inference form" (an appropriate particle depending on the verb) depending on each verb, and the extraction unit 12 judges whether the received content is a question based on the sentences stored in the memory unit.

[0080] In addition, the memory unit may store a certain number (e.g., 10 types of sentences) of request sentences consisting of multiple verbs (e.g., request, consider, etc.) for making (ordinary) requests rather than questions, with appropriate particles at the end of the sentence, according to each verb, and the extraction unit 12 may determine whether the received content is a request based on the sentences stored in the memory unit.

[0081] By storing sentences in the storage unit, the extraction unit 12 determines whether a sentence is a request in a two-stage determination based on the presence or absence of a basic form of a verb contained in the sentence stored in the storage unit and the verb's sequel (such as an appropriate particle for determining whether the sentence is a request sentence or a question sentence).By configuring in this way, it is possible to determine whether the content related to a security requirement received from a user is a question or a request.

[0082] 4(a) and 5(a), by storing a plurality of security guidelines and their items in the storage unit, the extraction unit 12 can extract security guidelines that meet the needs of the user. The extraction unit 12 extracts security guidelines using the names, items, information on the contents of the security guidelines, etc., of the security guidelines stored in the storage unit.

[0083] The extraction unit 12 extracts necessary information required for extracting security guidelines when no security guidelines can be extracted due to a request from a user received by the reception unit 11. For example, the extraction unit 12 extracts the necessary information such as the purpose of the site or system, who will use it, information assets, the number of people, and operating hours.

[0084] The extraction unit 12 extracts security guidelines that are the basis for generating a custom list, based on requests from users regarding security requirements, questions regarding security requirements, and answers to questions from the questioning unit 13.

[0085] <Questioning> In step S803, the questioning unit 13 asks a question about the necessary information. Specifically, the questioning unit 13 generates a question about the necessary information extracted by the extraction unit 12. For example, the questioning unit 13 transmits the generated question to the user terminal 2 to ask the question to the user.

[0086] The questioning unit 13 asks questions about security guidelines. Specifically, the questioning unit 13 generates a question for determining a security guideline that is a base for creating security requirements, such as "Is it sufficient to comply with the security guidelines of medical standards?", based on the security guidelines extracted by the extraction unit 12.

[0087] In addition, if the extraction unit 12 is unable to extract any security guidelines at all, the questioning unit 13 generates questions to identify candidates for base security guidelines, such as questions regarding the purpose of the site or system, who will use the site or system, questions regarding the information assets that the site or system should protect, the number of people using the site or system, and the operating hours of the site or system.

[0088] Furthermore, the questioning unit 13 asks questions to generate a custom list. The custom list is a list that includes the items of the security guidelines extracted by the extraction unit 12 and has been modified based on the user's requests or the like to meet the user's requests.

[0089] Specifically, the questioning unit 13 asks questions regarding items for generating a custom list. For example, the questioning unit 13 asks questions such as "Are there any items you would like to strengthen?" or, based on items included in the security guidelines extracted by the extraction unit 12, "Is access control an item to be strengthened?"

[0090] The strengthening item is a security requirement item that the user wants to strengthen, specifically, an item for which the user wants to generate fine-grained security requirements. For example, when the user specifies requirement information of a medium item as the strengthening item, a security requirement including requirement information of a small item related to the requirement information is generated.

[0091] Furthermore, the questioning unit 13 asks questions to determine items included in the security guideline extracted by the extraction unit 12. For example, when the extraction unit 12 extracts the guideline ID "GL00001" as a base for generating a custom list, the questioning unit 13 asks questions about the scale of the medical institution where the system will be introduced in order to determine a lower (more detailed) medium item below the major item "System introduction type by scale."

[0092] The questioning unit 13 asks questions about items included in the custom list. Specifically, the questioning unit 13 asks questions about all items included in the custom list generated by the generation unit 14. For example, the questioning unit 13 asks questions about the requirement information of all items included in the custom list to confirm whether or not they can be adopted as security requirements.

[0093] <Accepting responses> In step S804, the receiving unit 11 receives an answer from the user to the question posed by the questioning unit 13.

[0094] <Create custom list> In step S805, the generation unit 14 generates a custom list including hierarchically structured items based on the request and the answer to the question received by the reception unit 11. By storing the contents described in the guidelines in advance in the storage unit as a hierarchically structured structure as shown in Fig. 5(a), the generation unit 14 can generate a custom list including hierarchically structured items as shown in Fig. 6(a).

[0095] The generation unit 14 generates a custom list based on the security guidelines extracted by the extraction unit 12 based on the request accepted by the acceptance unit 11. Furthermore, the generation unit 14 generates a custom list based on answers to questions asked by the questioning unit 13.

[0096] For example, when the receiving unit 11 receives "access control" as an item to be reinforced, the generating unit 14 generates a custom list that refines the granularity of the received items. Specifically, the generating unit 14 acquires subitems (detailed items) lower than access control from security guidelines other than the security guidelines extracted by the extracting unit 12, and generates a custom list.

[0097] The generating unit 14 may generate a custom list using a guideline other than the base security guideline. For example, when the generating unit 14 generates a custom list related to "access control" based on the guidelines of an international organization, the extracting unit 12 also extracts guidelines of other organizations that contain the description of "access control."

[0098] Since the contents described in each guideline may differ, the generating unit 14 can generate a more detailed custom list by using the multiple guidelines extracted by the extracting unit 12. Specifically, the generating unit 14 generates a guideline by using all descriptions related to the accepted item "access control" described in the multiple guidelines.

[0099] On the other hand, when all descriptions are used, there is a possibility that the description contents are duplicated, so the generation unit 14 judges the keywords contained in each of the descriptions, and deletes one of them if there is a duplicate. In addition, the generation unit 14 may judge whether the contents are duplicated with the base security guideline, and generate a custom list by adding the non-duplicated contents from other guidelines.

[0100] As shown in FIG. 5(a), by storing items of different security guidelines in advance in a hierarchical structure in the storage unit, the generating unit 14 can generate a custom list with fine granularity for specific items.

[0101] When the generation unit 14 receives an answer to a question about an item, it generates a custom list including lower items that are more detailed (finer granularity) than the item in the hierarchical structure. When the generation unit 14 receives requirement information as an answer to a question about an item, it generates a custom list including lower items that indicate requirement information that is more detailed than the item in the hierarchical structure. When the generation unit 14 receives an answer to requirement information, it generates a custom list including finer granularity (lower) requirement information related (linked) to the requirement information.

[0102] In addition, when the generation unit 14 receives an answer regarding the nth item (requirements information), it generates a custom list including the n+1th item (requirements information) which is a detailed item of the nth item (n=1, 2, ...). In this embodiment, n is 3, and the first item is a major item, the second item is a medium item, and the third item is a minor item. When the reception unit 11 receives a medium item as an enhancement item, the generation unit 14 generates a custom list including minor items which are detailed items of the medium item.

[0103] Furthermore, when the content accepted as a reinforcement item is not included in the base security guideline extracted by the extraction unit 12, the generation unit 14 extracts an item related to that content from another security guideline and adds the item to generate a custom list. In this case, the generation unit 14 may extract from a security guideline related to the base security guideline extracted by the extraction unit 12.

[0104] Fig. 11 is an image diagram of a structure in which items of different granularity are mixed in this embodiment. The generating unit 14 may generate mixed structure information in which items of different granularity are mixed as shown in Fig. 11, which is not a hierarchical structure, based on requests and answers to questions.

[0105] Mixed structure information is information in which items of different granularity are mixed together, but there is no information on the higher-level items to which a given item is linked (information on which small items are linked to which medium items, information on which medium items are linked to which large items, etc.), as shown in Figure 11.

[0106] 11, W111 represents a small item, W112 represents a medium item, and W113 represents a large item. The granularity of each item can be determined by the size of the circle, but information on the medium item W112 linked to the small item W111 is not included. The mixed structure information only needs to include information on the item and information for determining the granularity of the item (for example, large item, medium item, small item).

[0107] 12 shows an example of an interaction between a user and a support device via a user terminal in this embodiment. In step S1201, the user inputs a request via the user terminal 2. In step S1202, the reception unit 11 receives the input from the user, the extraction unit 12 extracts a security guideline, and the question unit 13 generates a question.

[0108] In step S1203, the user inputs an answer to the question via the user terminal 2. In step S1204, the receiving unit 11 receives the input from the user, and the generating unit 14 generates a custom list based on the received answer.

[0109] In step S1205, question unit 13 generates a question based on the generated custom list. In step S1206, the user inputs an answer to the question via user terminal 2. In step S1207, reception unit 11 receives an input from the user, and generation unit 14 generates a custom list based on the received answer. In step S1208, the user inputs a question via user terminal 2.

[0110] In this way, by interacting with the support device 1 via the user terminal 2 (inputting requests, answering questions, etc.), the user can generate unique security requirements using general security guidelines, or generate appropriate security requirements by combining existing authoritative security guidelines.

[0111] <Quantification of security level> The generation unit 14 may calculate the security level of the custom list as a numerical value based on the generated custom list. Specifically, the storage unit stores a keyword associated with a numerical value, and the generation unit 14 determines the keyword from the generated custom list and calculates the security level of the custom list as a numerical value using the numerical value associated with the determined keyword. For example, the generation unit 14 calculates the security level of the custom list by adding the numerical value associated with the keyword.

[0112] The generating unit 14 may also calculate a relative security level of the generated custom list based on the numerical value of the custom list with the average security level. By calculating the relative security level, the user can confirm that the generated custom list has a higher security level than the average, and can determine when to stop adding items.

[0113] In addition, the generation unit 14 may calculate and present a numerical value indicating how much the security level will be improved when a certain item is added. By being presented with the degree to which the security level will be improved, the user can determine whether or not to add the item.

[0114] Fig. 13 is a diagram for explaining an example of security level calculation in this embodiment. Fig. 13(a) is an example of calculating a security level for security requirements in the same field (e.g., multi-factor authentication, etc.). In step S1301, the generation unit 14 performs morphological analysis on the wording (or sentence) of the security requirement.

[0115] In step S1302, the generation unit 14 determines whether the determination in step S1304 has been made for all of the analyzed morphemes, and if the determination has been made for all morphemes, it determines that the word following "multi-factor authentication" is not "required" and outputs "security level 4".

[0116] In step S1303, the generation unit 14 determines whether the analyzed morpheme corresponds to "multi-factor authentication". If the generation unit 14 determines that the analyzed morpheme corresponds to "multi-factor authentication", the process proceeds to S1304. In step S1304, the generation unit 14 determines whether the word following "multi-factor authentication" is "required". If the generation unit 14 determines that the word following "multi-factor authentication" is "required", it outputs "security level 5".

[0117] The memory unit stores a combination of a keyword in a certain field (e.g., multi-factor authentication) and the word that follows that keyword (e.g., required, desirable, etc.) in association with a security level, and the generation unit 14 determines the security level by performing a two-stage determination of the keyword and the word that follows it.

[0118] 13(a), the storage unit may store the subsequent word "desirable" in association with security level 4, and the generation unit 14 may output "security level 3" when the subsequent word is other than "required" and "desirable." It may be possible to set the security level to be higher when the subsequent word is a word that further encourages the inclusion of the keyword in the security requirement.

[0119] 13B shows an example of calculating a security level for a security requirement according to a set keyword.In step S1311, the generating unit 14 performs a morphological analysis on the wording of the security requirement.

[0120] In step S1312, the generation unit 14 determines whether the judgment in step S1313 has been made for all of the analyzed morphemes, and if the judgment has been made for all morphemes, it determines that none of the morphemes are any of the keywords set for the judgment in step S1313, and outputs "security level 1 or 2".

[0121] The storage unit stores a security level associated with each keyword (e.g., multi-factor authentication, one-time password, password, etc.), and the generation unit 14 determines whether the security requirement includes the keyword and calculates a security level according to the keyword. It is possible to set a higher security level for a keyword that provides stronger security. In addition, a security level may be set that complies with security level standards of domestic and foreign companies and organizations.

[0122] <Calculation of security risk value> The generating unit 14 may calculate a security risk value instead of a security level. For example, the security risk value is preset to 100, and when a security requirement includes a specific keyword, the generating unit 14 calculates (reduces) the security risk value based on the keyword and the word following the keyword.

[0123] The memory unit stores a plurality of keywords and a subtraction value for each keyword, and further stores subsequent words of the keywords and a weight for each word. The generation unit 14 determines whether a security requirement includes the keyword and the subsequent word, and calculates a security risk value based on the result of the determination, the subtraction value, and the weight.

[0124] Specifically, the security risk value for a case where measures against smartphone spoofing are not taken is set to 100. The security requirement keyword is "multi-factor authentication implemented" with a subtraction value of 80%, and the keyword is "fingerprint authentication implemented" with a subtraction value of 90%. The following word is then "required" with a weight of 1.0, and the following word is "desirable" with a weight of 0.5.

[0125] For example, if a smartphone requires multi-factor authentication, the generation unit 14 calculates a security risk value of 100-80×1.0=20. If a smartphone requires multi-factor authentication, the generation unit 14 calculates a security risk value of 100-80×0.5=60. In addition, if a smartphone requires fingerprint authentication, the generation unit 14 calculates a security risk value of 100-90×1.0=10.

[0126] It is conceivable to set a higher subtraction value to a keyword that provides stronger security. Furthermore, it is conceivable to set a larger weight when a subsequent word is one that more strongly encourages the inclusion of that keyword in the security requirements. In this way, it is possible to calculate a security risk value when no specific wording is present in the security requirements.

[0127] In addition, the generation unit 14 may calculate the magnitude of security risk (security risk value) for each of the three elements before the security requirements are generated (measures) based on the importance of the security risk (degree of security risk) stored in the memory unit and coefficients linked to the three elements of security (confidentiality, availability, and integrity), and may further calculate how much the security risk value of each of the three elements will be reduced by the security requirements (measures) to be generated.

[0128] In this way, it becomes possible to appropriately define the magnitude of security risk regarding the three elements of security before measures are taken, using the importance, coefficients, etc. that can be appropriately set.

[0129] Specifically, the storage unit stores one or more pieces of information (e.g., important information that would be problematic if leaked) associated with each of the three elements, and the generation unit 14 calculates a security risk value before countermeasures (generation of security requirements) are taken based on the importance and the coefficients associated with each of the pieces of information. Furthermore, the generation unit 14 calculates a security risk value after countermeasures (generation of security requirements) are taken based on one or more perspectives (e.g., attack methods) of the threat side (e.g., the side attacking important information).

[0130] For example, consider the calculation of security risk values ​​for confidentiality, availability, and integrity for information assets in a certain smartphone. If the storage unit stores bank account information, personal information of business partners, and contact email addresses as information assets for confidentiality risk in a certain smartphone, and further stores 3, 3, and 2 as the importance of each, the generation unit 14 multiplies the total importance (3+3+2=8) by a preset coefficient (e.g., 10) to calculate the security risk value before measures as 80.

[0131] Possible threat perspectives of confidentiality include spoofing and eavesdropping, and the generation unit 14 calculates the importance of each of the measures after the countermeasures are taken based on the security requirements to be generated, and further calculates a security risk value of confidentiality after the countermeasures are taken from each perspective based on the calculated importance.

[0132] The storage unit stores the keywords and importance of the security requirements related to the three elements in association with each other, so that the generation unit 14 can calculate the importance of each after the countermeasure is taken. The storage unit stores the importance of a certain keyword when it is included in a security requirement in association with each other. The generation unit 14 may calculate a subtracted security risk value based on the calculated security risk values ​​before and after the countermeasure.

[0133] If a certain spoofing countermeasure (security requirement) reduces the importance of all of the bank account information, business partner personal information, and contact email address to 1, the generation unit 14 calculates a security risk value of 1 (importance) x 3 (number) x 10 (coefficient) = 30. If a certain eavesdropping countermeasure (security requirement) reduces the importance of all of the bank account information, business partner personal information, and contact email address to 2, the generation unit 14 calculates a security risk value of 2 (importance) x 3 (number) x 10 (coefficient) = 60.

[0134] Furthermore, the generation unit 14 may display messages regarding suggestions or evaluations for the security requirements to be generated (for example, further consideration is needed regarding theft prevention measures, equivalent measures have been taken, etc.) based on the calculated security risk values ​​for each perspective.

[0135] Alternatively, the generation unit 14 may calculate one security risk value for confidentiality based on the numerical value of the degree of importance that is reduced by the security requirement for each viewpoint. If the security risk value for spoofing is reduced by 50 and the security risk value for eavesdropping is reduced by 30 due to a security requirement, the generation unit 14 may calculate 80 (security risk value of confidentiality before countermeasures)-50-30=0 as the security risk value of confidentiality after countermeasures.

[0136] The storage unit may store business applications (importance level 3), calendar information (importance level 2), network connection information (importance level 1), etc. as information assets for the risk of availability within a certain smartphone, and may further store company-only data (importance level 3) within the business application, company-only schedule information (importance level 3), company executive contact information (importance level 3), etc. as information assets for the risk of integrity within a certain smartphone. In this way, the storage unit may link different information to each of the three elements even for the same smartphone, and further link each piece of information to a different importance level.

[0137] From the perspective of the threat side with respect to availability, possible threats are system destruction and ransomware, while from the perspective of the threat side with respect to integrity, possible threats are data tampering and unauthorized access, etc. In this way, the perspectives for each of the three elements of the threat side may be different.

[0138] The generation unit 14 calculates the security risk value for the availability and integrity in the same way as for the confidentiality. The coefficients associated with the three elements may be different from each other. For example, when the evaluation is performed with emphasis on confidentiality, the coefficient for confidentiality is set higher than the coefficients for availability and integrity.

[0139] <Determining whether a response has been accepted> In step S806, the determination unit 15 determines that answers to all items included in the custom list have been received. For example, information indicating that an answer has been received from a user is linked to the custom list information in FIG. 6(a), and the determination unit 15 makes a determination based on whether or not the information is linked.

[0140] If the determination unit 15 determines that answers to all items have not been received, the process proceeds to step S803 to ask questions regarding the items to which answers have not been received.

[0141] When the determination unit 15 determines that answers to all items have been received, it confirms with the user whether it is OK to end the reception of the request. For example, the determination unit 15 transmits a message or the like to confirm the end of the reception of the request to the user terminal 2. When the determination unit 15 receives a signal indicating that it is OK to end the reception of the request from the user, it ends the request reception mode and proceeds to step S807 (security requirement generation mode) for generating security requirements.

[0142] 9(b) is a diagram for explaining the details of the text discrimination process in this embodiment. The judgment unit 15 confirms with the user whether it is OK to end the request reception, and the user inputs a response to the confirmation via the user terminal. The storage unit stores, for example, "end" as a keyword for determining whether to end the request reception mode, and "no" or "continue" as a keyword for determining whether to continue the request reception mode.

[0143] In step S904, the determination unit 15 determines whether the user's input indicates the end of the request reception mode or the continuation of the request reception mode based on the keyword stored in the storage unit. For example, if the user's input includes the keyword "end" immediately after a message for confirming the end of request reception is sent to the user, the determination unit 15 determines that the request reception mode is to be ended.

[0144] 10B is a diagram for explaining details of the text classification process (step S904 in FIG. 9B) in this embodiment. In step S1041, the determination unit 15 performs a morphological analysis on the received content (text, etc.).

[0145] In step S1042, the judgment unit 15 judges whether the judgment in step S1043 has been made for all of the analyzed morphemes, and if the judgment has been made for all morphemes, it judges that the received content is to continue the request reception mode, outputs "Request reception mode is continuing" as judgment result 4, and continues the request reception mode.

[0146] In step S1043, in order to determine whether the received content is content related to the end of the request receiving mode, the determination unit 15 determines whether the analyzed morpheme corresponds to the basic form of a verb (e.g., "convey everything," "convey everything I wanted to convey," etc.) related to the end of a request (end of the request receiving mode), such as "convey." If the determination unit 15 determines that the analyzed morpheme corresponds to the verb, the process proceeds to S1044.

[0147] In step S1044, the determination unit 15 determines whether the morpheme following the basic form of the determined verb related to the end of the request reception mode corresponds to "infinitive form (a form in which a sentence is normally completed) / general form". When the received content is content related to the end of the request reception mode, the verb following is "infinitive form / general form", so the determination unit 15 makes such a determination. When the determination unit 15 determines that the following corresponds to "infinitive form / general form", it may output "Request reception mode has ended" as determination result 1.

[0148] There are multiple possible verbs related to the end of the request reception mode, and furthermore, the appropriate "final form / general form" for ending the request reception mode consisting of the verb differs depending on each verb. The memory unit stores a certain number (e.g., 10 types of sentences, etc.) of sentences for ending the request reception mode consisting of multiple verbs (e.g., convey, complete, end, etc.) for ending the request reception mode, each of which ends with an "final form / general form" (an appropriate particle depending on the verb), depending on each verb, and the determination unit 15 determines whether the received content is related to the end of the request reception mode based on the sentences stored in the memory unit.

[0149] By storing the sentence in the memory unit, the determination unit 15 determines whether the content is related to the end of the request receiving mode in a two-stage determination of the presence or absence of a basic form of a verb included in the sentence stored in the memory unit and the sequel to the verb (such as an appropriate particle for determining a sentence related to the end of the request receiving mode).By configuring in this way, it is possible to determine whether the content received from the user regarding a security requirement is related to the end of the request receiving mode.

[0150] <Generating security requirements> In step S807, the generation unit 14 generates security requirements based on the request received by the reception unit 11 and answers to the questions asked by the questioning unit 13. Specifically, the generation unit 14 generates security requirements based on items included in the security guidelines extracted by the extraction unit 12 and answers to questions about the items.

[0151] The generation unit 14 generates security requirements based on the determination result of the determination unit 15. Specifically, the generation unit 14 generates a list of security requirements on the user terminal 2 based on the generated custom list. The generation unit 14 performs processing to display the list of security requirements on the user terminal 2 based on the custom list. In addition, the generation unit 14 may generate a list of security requirements based on the generated mixed structure information.

[0152] Furthermore, the generating unit 14 may perform processing to display the publication year of the used security guideline. In this way, the user can grasp the security guideline described in each security requirement, and can more clearly understand the contents of the security requirement.

[0153] <Updates to security guidelines> The update unit 16 automatically updates the security guidelines from time to time. Since the version of the security guidelines is updated from time to time, the update unit 16 periodically checks for updates to the guidelines.

[0154] Furthermore, the update unit 16 may use the updated security guidelines to update the information stored in the storage unit. For example, the update unit 16 extracts items from the contents of the security guidelines. Furthermore, the update unit 16 generates information by requirement information, etc., based on the extracted information.

[0155] As described above, the configuration of the present invention can provide a new technique for creating security requirements without imposing a burden on the user. [Explanation of symbols]

[0156] 0 Support System 1 Support equipment 11 Reception 12 Extraction part 13 Question Section 14 Generation part 15 Judgment section 16 Update section 2. User terminal NW Network

Claims

1. A support system for supporting creation of security requirements, comprising: The support system includes a storage unit, a reception unit, an extraction unit, a question unit, and a generation unit, the storage unit stores a keyword for determining whether an input from a user is a question about a security requirement or a request for creating a security requirement; The receiving unit receives an input regarding a security requirement from the user; The extraction unit determines whether the input is a question about the security requirement or a request for generating the security requirement other than a question, based on the input and a keyword, and generates an answer to the question if the input is a question, and extracts necessary information required for generating the security requirement if the input is a request for generating the security requirement; The questioning unit asks a question regarding the necessary information, The generating unit generates security requirements based on the request and answers to questions about the necessary information. Support system.

2. The storage unit stores a plurality of security guidelines; The extraction unit extracts necessary information required for generating the security requirements, including security guidelines that are a basis for generating the security requirements, based on the request; the generation unit extracts security guidelines related to the request and the answer based on the request and the answer to the question regarding the necessary information from outside the base security guidelines, and generates security requirements based on the base security guidelines, the request, the answer, and the extracted security guidelines. The support system according to claim 1 .

3. The storage unit stores a keyword for calculating a security level, the generating unit generates security requirements based on the request and answers to questions about the necessary information, calculates a security level for the security requirements based on keywords in the security requirements and keywords for calculating the security level, and presents how much the security level will be improved if a certain item described in a security guideline is added. The support system according to claim 1 .

4. the generating unit generates a custom list including items in a hierarchical structure based on the request and answers to questions about the necessary information, and further generates security requirements based on the custom list and answers to questions about the items. The support system according to any one of claims 1 to 3.

5. the generating unit generates mixed structure information, which is a structure in which items of different granularities are mixed, based on the request and answers to questions about the necessary information, and further generates security requirements based on the mixed structure information and the answers to questions about the items. The support system according to any one of claims 1 to 3.

6. the hierarchical structure includes a plurality of items; the interrogator asks questions about items for generating a custom list; when the generating unit receives an answer to a question regarding the item, the generating unit generates a custom list including sub-items indicating more detailed requirement information than the item in the hierarchical structure. The support system according to claim 4.

7. The assistance system includes a determination unit, The determination unit determines that answers regarding all items included in the custom list have been received, The generating unit generates a security requirement based on the determination result. The support system according to claim 6.

8. A method for supporting creation of security requirements, the method comprising: The support system includes a storage unit, a reception unit, an extraction unit, a question unit, and a generation unit, a step of storing a keyword in the storage unit for determining whether an input from a user is a question about a security requirement or a request for creating a security requirement; the receiving unit receiving an input regarding a security requirement from the user; the extraction unit determines whether the input is a question about the security requirement or a request for generating the security requirement other than a question based on the input and a keyword, and generates an answer to the question if the input is a question, and extracts necessary information required for generating the security requirement if the input is a request for generating the security requirement; a step of the questioning unit asking a question regarding the necessary information; The generating unit generates security requirements based on the request and answers to questions about the required information. How to help.

9. A support program for supporting the creation of security requirements, A computer is caused to function as a storage unit, a reception unit, an extraction unit, a question unit, and a generation unit; the storage unit stores a keyword for determining whether an input from a user is a question about a security requirement or a request for creating a security requirement; The receiving unit receives an input regarding a security requirement from the user; The extraction unit determines whether the input is a question about the security requirement or a request for generating the security requirement other than a question, based on the input and a keyword, and generates an answer to the question if the input is a question, and extracts necessary information required for generating the security requirement if the input is a request for generating the security requirement; The questioning unit asks a question regarding the necessary information, The generating unit generates security requirements based on the request and answers to questions about the necessary information. Support programs.

Images