Device for preventing leakage of confidential items, method for preventing leakage of confidential items, and program for preventing leakage of confidential items

Abstract

The present invention aims to provide a confidential item leakage prevention device (Web server) that can prevent the leakage of the contents of confidential items by transmitting only at least one of display values ​​and screen control information to a Web client without transmitting the contents of the confidential items to the Web client. [Solution] In this embodiment, (1) it is determined whether a control whose value has been entered or changed on the web client screen exists in the event assignment definition, (2) if it exists, the action setting is referenced and the corresponding return value is obtained as a display value using the control as an argument, (3) it is determined whether the content of the confidential item corresponding to the obtained display value or the value of the control satisfies the specified condition in the condition setting, and if so, the rule in the business rule setting is obtained as screen control information, and (4) at least one of the obtained display value and screen control information is sent from the web server to the web client.

Description

[Technical Field]

[0001] The present invention relates to a device for preventing confidential item leakage, a method for preventing confidential item leakage, and a program for preventing confidential item leakage. [Background technology]

[0002] Paragraph 0004 of Patent Document 1 discloses an information processing device and the like that aims to improve user convenience by not displaying setting items that are not displayed in search results, and paragraph 0013 of Patent Document 1 discloses that the results of the display conditions for each setting item 303 change dynamically when the state of MFP 101 changes or when the setting value is changed by the administrator. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Publication No. 2022-128713 Summary of the Invention [Problem to be solved by the invention]

[0004] In the field of dynamic screen display as described in Patent Document 1, the screen display may be switched based on the contents of confidential items (account number, etc.). For example, if the account number corresponding to the entered employee CD is not set (if it is blank), the account information input button is displayed on the screen, but if the account number corresponding to the entered employee CD is set, the account information input button is not displayed on the screen.

[0005] Here, if the contents of the confidential items (account number, etc.) were also sent from the web server to the web client to make this switching decision, there was a risk that the contents of the confidential items (account number, etc.) would be leaked, as shown in Figure 16.

[0006] The present invention has been made in consideration of the above-mentioned problems, and aims to provide a confidential item leakage prevention device (Web server), a confidential item leakage prevention method, and a confidential item leakage prevention program that can prevent the leakage of the contents of confidential items by not sending the contents of the confidential items to the Web client, but instead sending to the Web client only at least one of a display value, which is a value displayed on the screen of the Web client, and screen control information, which is information for controlling the contents displayed on the screen. [Means for solving the problem]

[0007] In order to solve the above-mentioned problems and achieve the object, the confidential item leakage prevention device of the present invention is a confidential item leakage prevention device that includes a control unit and a storage unit as a web server, and that can prevent leakage of the contents of the confidential items by transmitting to the web client only at least one of display values, which are values ​​to be displayed on the screen of the web client, and screen control information, which is information for controlling the contents displayed on the screen, without transmitting the contents of the confidential items to the web client. The storage unit stores an event assignment definition table in which events are assigned to controls, which are elements that make up the screen, an action setting table in which the controls are set as arguments and return values, a condition setting table in which predetermined conditions for the confidential items or the controls are set, and a business rule setting table in which rules are set that define what control to perform on the screen when the predetermined conditions are satisfied. The control unit controls the confidential items when values ​​are input or changed on the screen. When information about a changed control is sent from the Web client to the Web server, the system is characterized by comprising: an event allocation determination means for determining whether the control into which the value has been input or changed exists in the event allocation definition table; a display value acquisition means for, if the event allocation determination means determines that the control exists, referring to the action setting table and using the control into which the value has been input or changed as an argument to acquire a corresponding return value as the display value; a screen control information acquisition means for determining whether the content of the confidential item corresponding to the display value acquired by the display value acquisition means or the value of the control into which the value has been input or changed satisfies the specified condition in the condition setting table, and if so, acquiring the rule in the business rule setting table as the screen control information; and a transmission means for transmitting at least one of the display value acquired by the display value acquisition means and the screen control information acquired by the screen control information acquisition means from the Web server to the Web client.

[0008] In addition, the confidential item leakage prevention device of the present invention is characterized in that information about a control whose value has been entered or changed on the screen is sent from the web client to the web server when either the condition that the control exists in the event allocation definition table or the condition that the control exists in the condition setting table is satisfied.

[0009] Furthermore, a method for preventing confidential item leakage according to the present invention is a method for preventing confidential item leakage executed by a web server having a control unit and a storage unit, which can prevent leakage of the contents of confidential items by transmitting to the web client only at least one of a display value, which is a value displayed on a screen of the web client, and screen control information, which is information for controlling the contents displayed on the screen, without transmitting the contents of the confidential items to the web client, wherein the storage unit stores an event assignment definition table in which events are assigned to controls that are elements constituting the screen, an action setting table in which the controls are set as arguments and return values, a condition setting table in which predetermined conditions for the confidential items or the controls are set, and a business rule setting table in which rules are set that define what control to perform on the screen when the predetermined conditions are satisfied, and wherein a process executed by the control unit transmits information of a control whose value has been input or changed on the screen to the web server. The method includes an event allocation determination step for determining whether the control into which the value has been input or changed exists in the event allocation definition table when the control is sent from the Web client to the Web server; a display value acquisition step for, if it is determined in the event allocation determination step that the control exists, referring to the action setting table and using the control into which the value has been input or changed as an argument to acquire a corresponding return value as the display value; a screen control information acquisition step for determining whether the content of the confidential item corresponding to the display value acquired in the display value acquisition step or the value of the control into which the value has been input or changed satisfies the specified condition in the condition setting table, and if so, acquiring the rule in the business rule setting table as the screen control information; and a transmission step for transmitting at least one of the display value acquired in the display value acquisition step and the screen control information acquired in the screen control information acquisition step from the Web server to the Web client.

[0010] Furthermore, a confidential item leakage prevention program according to the present invention is a confidential item leakage prevention program for being executed by a web server having a control unit and a storage unit, which can prevent leakage of the contents of confidential items by transmitting to the web client only at least one of display values, which are values ​​to be displayed on the screen of the web client, and screen control information, which is information for controlling the contents displayed on the screen, without transmitting the contents of the confidential items to the web client, wherein the storage unit stores an event assignment definition table in which events are assigned to controls, which are elements constituting the screen, an action setting table in which the controls are set as arguments and return values, a condition setting table in which predetermined conditions for the confidential items or the controls are set, and a business rule setting table in which rules are set that define what control to perform on the screen when the predetermined conditions are met, and an event allocation determination step of determining whether or not the control into which the value has been input or changed exists in the event allocation definition table when information about a secret item is sent from the Web client to the Web server; a display value acquisition step of, if it is determined in the event allocation determination step that the control into which the value has been input or changed exists, referring to the action setting table and using the control into which the value has been input or changed as an argument to acquire a corresponding return value as the display value; a screen control information acquisition step of determining whether or not the content of the secret item corresponding to the display value acquired in the display value acquisition step or the value of the control into which the value has been input or changed satisfies the predetermined condition in the condition setting table, and if so, acquiring the rule in the business rule setting table as the screen control information; and a transmission step of transmitting at least one of the display value acquired in the display value acquisition step and the screen control information acquired in the screen control information acquisition step from the Web server to the Web client. [Effects of the Invention]

[0011] According to the present invention, the contents of the confidential items are not sent to the web client, but only at least one of the display value, which is the value displayed on the screen of the web client, and the screen control information, which is information for controlling the contents displayed on the screen, is sent to the web client, thereby achieving the effect of preventing the contents of the confidential items from being leaked. [Brief explanation of the drawings]

[0012] [Figure 1] FIG. 1 is a block diagram showing an example of the configuration of a confidential item leakage prevention device. [Figure 2] FIG. 2 is a diagram showing an example of a setting screen in a low-code platform. [Figure 3] FIG. 3 is a diagram showing an example of an execution screen in a low-code platform. [Figure 4] FIG. 4 is a diagram showing an example of a layout editing screen among the setting screens. [Figure 5] FIG. 5 is a diagram showing an example of the generated layout definition (control list). [Figure 6] FIG. 6 is a diagram showing an example of a logic flow setting screen among the setting screens. [Figure 7] FIG. 7 is a diagram showing an example of the generated event allocation definition (event allocation definition table), logic flow definition, action definition, and flow definition. [Figure 8] FIG. 8 is a diagram showing an example of an action setting screen among the setting screens. [Figure 9] FIG. 9 is a diagram showing an example of the employee information acquisition API (action setting table) generated on the action setting screen. [Figure 10] FIG. 10 is a diagram showing an example of a condition setting screen among the setting screens. [Figure 11] FIG. 11 is a diagram showing an example of the generated condition settings (condition setting table). [Figure 12]FIG. 12 is a diagram showing another example of the generated condition settings. [Figure 13] FIG. 13 shows an example of a table summarizing items that can be specified on the left and right sides and a table summarizing operators. [Figure 14] FIG. 14 is a diagram showing an example of a business rule setting screen among the setting screens. [Figure 15] FIG. 15 is a diagram showing an example of the generated business rule settings (business rule setting table). [Figure 16] FIG. 16 is a diagram for explaining the problem of a Web application. [Figure 17] FIG. 17 is a diagram for explaining the problem of a Web application. [Figure 18] FIG. 18 is a diagram for explaining the problem of a Web application. [Figure 19] FIG. 19 is a diagram for explaining the problem of a Web application. [Figure 20] FIG. 20 is a diagram for explaining an outline of the processing in this embodiment. [Figure 21] FIG. 21 is a diagram for explaining a first specific example of this embodiment. [Figure 22] FIG. 22 is a diagram for explaining a first specific example of this embodiment. [Figure 23] FIG. 23 is a flowchart for explaining a first specific example of this embodiment. [Figure 24] FIG. 24 is a diagram for explaining a second specific example of this embodiment. [Figure 25] FIG. 25 is a diagram for explaining a second specific example of this embodiment. [Figure 26] FIG. 26 is a flowchart illustrating a second specific example of this embodiment. [Figure 27] FIG. 27 is a diagram for explaining a third specific example of this embodiment. [Figure 28] FIG. 28 is a diagram for explaining a third specific example of this embodiment. [Figure 29] FIG. 29 is a flowchart illustrating a third specific example of this embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0013] Hereinafter, embodiments of a device for preventing a confidential item from being leaked, a method for preventing a confidential item from being leaked, and a program for preventing a confidential item from being leaked according to the present invention will be described in detail with reference to the accompanying drawings. Note that the present invention is not limited to these embodiments.

[0014] [1. Overview] In recent years, applications have become more sophisticated and complex due to the increasing sophistication of business processes and rapid changes in the business environment. As applications become more sophisticated and complex, the risk of vulnerabilities in applications also increases. For this reason, there is a need for a system that prevents vulnerabilities from being introduced into applications even as they evolve.

[0015] In the past, when developing applications through programming, there was a risk that confidential information would be sent to the client. While it is possible to create a system that does not allow vulnerabilities to be introduced, there was the problem of the cost and effort required to continually monitor whether the rules were understood and followed across the entire ERP (Enterprise Resource Planning) system.

[0016] Therefore, in this embodiment, a mechanism is constructed that can prevent information leakage by, for example, performing all processing related to screen control on a low-code platform on the server. In other words, in simple terms, this embodiment provides a mechanism for preventing leakage of confidential information in applications with dynamic UI control.

[0017] As a result, it has become possible to develop secure applications without the developer even being aware of it. The specific configuration and operation are explained below.

[0018] [2. Configuration] An example of the configuration of the device 100 (Web server) for preventing confidential item leakage according to this embodiment will be described with reference to Fig. 1. Fig. 1 is a block diagram showing an example of the configuration of the device 100 for preventing confidential item leakage.

[0019] The confidential item leakage prevention device 100 includes a control unit 102, a communication interface unit 104, and a storage unit 106. The units included in the confidential item leakage prevention device 100 are connected to each other so as to be able to communicate with each other via any communication path.

[0020] The communication interface unit 104 (network line 104) communicatively connects the confidential item leakage prevention device 100 to a network 300 via a communication device such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 104 has a function of communicating data with other devices via the communication line. Here, the network 300 has a function of connecting the confidential item leakage prevention device 100 and the Web client 200 so that they can communicate with each other, and is, for example, the Internet or a LAN (Local Area Network). Note that data such as various masters described below may be stored in the Web client 200, for example.

[0021] Various databases, tables, files, etc. are stored in the storage unit 106. Computer programs that work in conjunction with the OS (Operating System) to issue commands to the CPU (Central Processing Unit) to perform various processes are recorded in the storage unit 106. The storage unit 106 can be, for example, a memory device such as RAM (Random Access Memory) or ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, an optical disk, etc.

[0022] The storage unit 106 includes, for example, an event allocation definition table 106a, an action setting table 106b, a condition setting table 106c, and a business rule setting table 106d.

[0023] Here, according to the confidential item leakage prevention device 100 of this embodiment, leakage of the contents of the confidential items can be prevented by not transmitting the contents of the confidential items to the Web client, but instead transmitting to the Web client only at least one of the display value, which is the value displayed on the screen of the Web client, and the screen control information, which is information for controlling the contents displayed on the screen.

[0024] In the event allocation definition table 106a, events are allocated to controls that are elements that make up the screen. As shown in Fig. 7, the event allocation definition table 106a includes, for example, a control ID for the control to which the event is set, information for identifying the event (event type), a logic flow ID, and the like.

[0025] In the action setting table 106b, the above-mentioned controls are set as arguments and return values. As shown in Fig. 9, the action setting table 106b includes, for example, information for identifying an action (the API to be called), a control ID (argument setting) for the control that serves as an argument, and a control ID (return value setting) for the control that serves as a return value.

[0026] The condition setting table 106c sets predetermined conditions for the confidential items or the controls. As shown in Fig. 11, the condition setting table 106c includes, for example, information for identifying the predetermined conditions (condition ID and name), the predetermined conditions (expressions), and the like.

[0027] The predetermined conditions include, for example, · The condition "Account number variable is not empty." - The condition "The account setting radio button is 'Set up'." etc. exist.

[0028] The business rule setting table 106d has set therein rules that define what kind of control is to be performed on the screen when the predetermined conditions are met. As shown in Fig. 15, the business rule setting table 106d includes, for example, information for identifying the rule (business rule ID), the content of the control (processing content), the control ID of the control to be controlled, a condition ID, and the like.

[0029] The rule is, for example, - The rule "Hide the account information input button" corresponds to the condition "The account number variable is not empty." The rule "Display the account information input button" corresponds to the condition "The account setting radio button is 'Set up'." etc. exist.

[0030] The control unit 102 is a CPU or the like that performs overall control of the confidential item leakage prevention device 100. The control unit 102 has an internal memory for storing control programs such as an OS, programs that define various processing procedures, required data, etc., and executes various information processing based on these stored programs.

[0031] The control unit 102 has, in terms of functional concept, for example: (1) an event allocation determination unit 102a as an event allocation determination means for determining whether or not the control whose value has been input or changed exists in the event allocation definition table when information on the control whose value has been input or changed on the screen is sent from the Web client to the Web server; (2) a display value acquisition unit 102b as a display value acquisition means for, when the event allocation determination means determines that the control whose value has been input or changed exists, referring to the action setting table and using the control whose value has been input or changed as an argument to acquire a corresponding return value as the display value; and (3) ) a screen control information acquisition unit 102c as a screen control information acquisition means that determines whether the content of the confidential item corresponding to the display value acquired by the display value acquisition means or the value of the control into which the value has been input or changed satisfies the specified condition in the condition setting table, and if so, acquires the rule in the business rule setting table as the screen control information; and (4) a transmission unit 102d as a transmission means that transmits at least one of the display value acquired by the display value acquisition means and the screen control information acquired by the screen control information acquisition means from the Web server to the Web client.

[0032] When information about a control in which a value has been entered or changed on a web client screen is sent from the web client to the web server, the event allocation determination unit 102a determines whether the control in which the value has been entered or changed exists in the event allocation definition table 106a (see Figure 7).

[0033] In addition, information about a control whose value has been entered or changed on the screen may be sent from the Web client to the Web server if either the condition that the control exists in the event assignment definition table 106a (see Figure 7) or the condition that the control exists in the condition setting table 106c (see Figure 11) is met.

[0034] If the event allocation determination unit 102a determines that the control exists, the display value acquisition unit 102b refers to the action setting table 106b (see FIG. 9) and acquires the corresponding return value as the display value, using the control in which the value was entered or changed as an argument. In the example of (2-2) in [4-2. Details of Processing] below, "Masakazu Aoki" corresponds to the corresponding return value.

[0035] The screen control information acquisition unit 102c determines whether the content of the confidential item corresponding to the display value acquired by the display value acquisition unit 102b or the value of the control into which the value has been input or changed satisfies the predetermined condition in the condition setting table 106c (see FIG. 11), and if so, acquires the rule in the business rule setting table 106d (see FIG. 15) as the screen control information. In the example of (2-2) in [4-2. Details of Processing] below, "value of account number variable: 123456" corresponds to the content of the confidential item. Also, in the example of (3-2) in [4-2. Details of Processing] below, the radio button control for setting corresponds to the control into which the value has been input or changed.

[0036] The transmission unit 102d transmits at least one of the display value acquired by the display value acquisition unit 102b and the screen control information acquired by the screen control information acquisition unit 102c from the Web server to the Web client.

[0037] [3. Processing Prerequisites] In this section, the premise of the processing according to this embodiment will be described.

[0038] [3-1. Overview of the low-code platform] The low-code platform has a settings screen operated by developers and an execution screen operated by business operators.

[0039] An example of the setting screen is shown in Fig. 2. On the setting screen, the developer sets the screen layout and event processing using GUI operations. The information on the setting screen is saved in a setting information database 400 shown in Fig. 3.

[0040] An example of the execution screen is shown in Figure 3. Once the setting information set on the setting screen is read and deployed in the memory on the web server, the business operator executes the application on the execution screen.

[0041] 3, the Web server 100 transmits a Web page (screen and program) to be executed by the Web client 200 based on the definition information of the application to the Web client 200. The Web client 200 reads and executes the transmitted Web page in a Web browser, and communication between the client Web page (screen and program) and the server application of the Web server 100 is carried out.

[0042] To explain again, the Web server 100 reads the setting information set on the setting screen using a low-code platform and expands the setting information into memory on the Web server 100, thereby generating a server application and a client Web page (screen + program) to be executed on the execution screen of the Web client 200. This client Web page (screen + program) is transmitted from the Web server 100 to the Web client 200, and is read and executed by the Web browser on the Web client 200. The program for the client Web page can be realized using a method that can be implemented using well-known Web application technology (for example, a format including commands and runtime variables written in JavaScript (registered trademark) or the like).

[0043] [3-2.Settings screen] This section will explain in detail how to set up the settings on the settings screen.

[0044] (1) Layout editing screen First, the developer places controls on the layout editing screen shown in Figure 4 using the mouse. By setting the item validation event as circled in Figure 4, the developer is taken to the logic flow setting screen, which will be explained in the next paragraph. The generated layout definition (control list) is shown in Figure 5.

[0045] (2) Logic flow setting screen Next, the developer sets the item verification process on the logic flow setting screen shown in Fig. 6. By setting the API call action as circled in Fig. 6, the developer is taken to the action setting screen described in the next paragraph. The generated event allocation definition (event allocation definition table 106a), logic flow definition, action definition, and flow definition are shown in Fig. 7.

[0046] (3) Action setting screen Next, the developer sets up the API call on the action setting screen shown in Figure 8. An example of the generated employee information acquisition API (action setting table 106b) is shown in Figure 9. Note that if the API return value is set in a control, it is returned to the client, but if the return value is set in a screen variable, the return value is not returned to the client.

[0047] (4) Condition setting screen Next, the developer sets expressions that will be the conditions for business rules (for example, rules for locking, display switching, and mandatory switching) on ​​the condition setting screen shown in Fig. 10. In the example of Fig. 10, the condition "if the radio button to be set is TRUE" is set on the condition setting screen. The generated condition setting (condition setting table 106c) is shown in Fig. 11.

[0048] Another example of condition settings is shown in Figure 12. Also, Figure 13 shows a table summarizing the items that can be specified on the left and right sides, and a table summarizing the operators.

[0049] (5) Business rule setting screen Finally, the developer sets the process to be executed when the condition described in (4) is met and the location where that process will be executed for the control on the business rule setting screen shown in Figure 14. In the example of Figure 14, "Display item" is set as the process to be executed when the condition "When the radio button to set is TRUE" is met, and "Account information input button" is set as the location where that process will be executed. The generated business rule setting (business rule setting table 106d) is shown in Figure 15.

[0050] In addition to "displaying the item", the following processes can also be set as processes to be executed when the conditions are met. "Lock item" "Make field required" "Hide items"

[0051] [4. Specific examples of processing] In this section, we will mainly explain a specific example of the processing according to this embodiment, but before that, we will explain the problems that web applications have traditionally had.

[0052] [4-1. Web application challenges] By using the developer tools and network capture tools installed in the browser, it is possible to understand the request, response, and the contents of variables defined in JAVASCRIPT (registered trademark), etc. However, if these tools are misused, there is a risk that highly secure information (for example, employee account numbers) may be stolen and viewed, as shown in Figure 16.

[0053] This risk can be addressed by paying attention to how the application is created. In other words, as shown in Figure 17, by returning only the necessary information displayed on the screen to the client, the risk of high-security information being leaked can be reduced.

[0054] However, when paying attention to how an application is created, it is necessary to manually check whether the application is created correctly or to check for vulnerabilities using diagnostic tools, which requires time and effort. Also, when screen control using high-security items, such as those described in the next paragraph, is required, there is a problem that the risk of information leakage increases.

[0055] For example, consider a case where the display / non-display of the account information input button is switched depending on whether or not an account number corresponding to the input employee CD is set, as shown in Figure 18. If an account number corresponding to the input employee CD is not set (if it is blank), the account information input button is displayed on the screen, as shown in Figure 19. On the other hand, if an account number corresponding to the input employee CD is set, the account information input button is not displayed on the screen.

[0056] When determining whether or not this account number has been set, if the account number used for determination is returned to the client as shown in FIG. 19, there is a risk that the account number will be leaked and snooped on.

[0057] [4-2. Processing details] Therefore, in this embodiment, the low-code development platform is designed so that all screen control processing is performed by the server. For example, as shown in Figure 20, the server determines whether to display or hide the account information input button depending on whether an account number is set.

[0058] Then, only the value displayed on the screen or the screen control information is returned to the client. In Figure 20, the information in the response "Employee name label value: Yamashita Shigeru" corresponds to the value displayed on the screen, and the information in the response "Account number input button display: Hidden" corresponds to the screen control information.

[0059] This makes it possible to control the client's screen without returning the variable (account number) used for screen control to the client, significantly reducing the risk of information leakage.

[0060] Three specific examples of the process will be described below in detail. In particular, the second example is the most characteristic example of the present application.

[0061] (1) First example As a first specific example, as shown in FIG. 21, an example will be described in which when an employee code "A0001" is entered on the screen, an employee name "Yamashita Shigeru" is returned as a response.

[0062] (1-1) Screen startup process When the screen is launched on the Web client, the following two pieces of information are sent from the Web server to the Web client, as shown in Figure 22. (A) ID information of the control to which the event is assigned (= ID of the control existing in the event assignment definition table 106a) (B) Information on the control specified in the condition used in screen control (= ID of the control existing in the condition setting table 106c) The web client then stores the ID of the control that corresponds to (A) or (B) as a state change control. This state change control is used to determine whether or not to send a request to the server when an event is fired, as explained below.

[0063] In addition to the above, screen information (Html, etc.) of the launched screen and screen operation commands (JavaScript (registered trademark), etc.) are sent from the web server 100 to the web client 200, and are read and executed by the web browser of the web client 200.

[0064] The operational commands on this screen incorporate commands to execute the processing content that is performed depending on whether the control of the event that occurs on the Web client 200 side is the state change control, as explained below in "(1-2) Processing when verification processing is triggered," "(2-2) Processing when verification processing is triggered," and "(3-2) Processing when verification processing is triggered."

[0065] (1-2) Processing when verification processing is triggered First, in step SA1 of FIG. 23, an event is executed by inputting employee CD "A0001" on the screen of the Web client.

[0066] Next, in step SA2 of Figure 23, the Web client determines whether the control of the employee CD text for which the event was fired corresponds to a state change control. In this example, it is determined that it corresponds, and information about the control of the employee CD text for which the event was fired is sent as a request from the Web client to the Web server via the network line.

[0067] Next, the event allocation determination unit 102a in the Web server determines whether or not the control for the employee CD text exists in the event allocation definition table 106a in step SA3 of Fig. 23. In this example, it is assumed to exist, and the process proceeds to the following step SA4.

[0068] Next, in step SA4 of Figure 23, the display value acquisition unit 102b in the Web server refers to the action setting table 106b, and uses the value "A0001" entered in the employee CD text control as an argument to acquire the corresponding return value "Yamashita Shigeru" as the display value, and reflects it in the memory information on the screen.

[0069] Furthermore, the display value acquisition unit 102b in the Web server generates screen change information to be returned to the client at the same time as the reflection in step SA4 of FIG.

[0070] The process then proceeds to step SA5 in FIG. 23, but in this example, since screen control based on business rules is not performed, SA5 is skipped and the process proceeds to the next step SA6.

[0071] Finally, in step SA6 of Figure 23, the sending unit 102d generates a response to be returned to the client based on the generated memory information and screen change information, and sends it from the Web server to the Web client over the network. As a result, the employee name "Yamashita Shigeru" is displayed on the screen of the Web client.

[0072] As explained above in section (1), in this embodiment, when screen information is changed due to an event or the like, the web server can stack only the changed information displayed on the screen and return it to the web client.

[0073] (2) Second example (Example 1: Screen control based on event processing flow) As a second specific example, we will explain an example of switching between displaying and hiding the account information input button depending on the input employee number. Specifically, as shown in Figure 24, when the employee code is set to "A0001" (Yamashita Shigeru, no account set), if the employee code is changed to "A0002" (Aoki Masakazu, account set), the account information input button is hidden. This specific example is also the most distinctive example of this application.

[0074] In this specific example, the prerequisites are that an "account number variable" is set as the screen variable, that the condition in the condition setting table 106c is set as "The account number variable is not empty," and that the screen control information in the business rule setting table 106d is set as "Hide the account information input button."

[0075] (2-1) Screen startup process The processing when the screen is started is the same as the processing content explained in (1-1), but in this example, as shown in Figure 25, (A) the ID information of the control to which the event is assigned (= the ID of the control existing in the event assignment definition table 106a) is assumed to be the ID "2-2" of the employee CD text control sent from the web server to the web client. In other words, the web client is assumed to hold the ID "2-2" of the employee CD text control as a status change control.

[0076] (2-2) Processing when verification processing is triggered First, in step SB1 of FIG. 26, an event is executed by inputting employee CD "A0002" on the screen of the Web client.

[0077] Next, in step SB2 of Figure 26, the Web client determines whether the control of the employee CD text for which the event was fired corresponds to a state change control. In this example, as explained in (2-1), the Web client holds the control of the employee CD text as a state change control, so it is determined that it corresponds. If it corresponds, information about the control of the employee CD text for which the event was fired is sent as a request from the Web client to the Web server via the network line.

[0078] Next, the event allocation determination unit 102a in the Web server determines whether or not the control for the employee CD text exists in the event allocation definition table 106a in step SB3 of Fig. 26. In this example, as described in (2-1), the control for the employee CD text exists in the event allocation definition table 106a, so the event allocation determination unit 102a determines that it exists.

[0079] Next, in step SB4 of Figure 26, the display value acquisition unit 102b in the Web server refers to the action setting table 106b, and uses the value "A0002" entered in the employee CD text control as an argument to acquire the corresponding return value "Masakazu Aoki" as the display value, and reflects it in the memory information on the screen.

[0080] Next, in step SB4 of Figure 26, the display value acquisition unit 102b in the Web server refers to the action setting table 106b, uses the acquired "Masakazu Aoki" as an argument, acquires the account number variable "123456" as the corresponding return value, and reflects this in the memory information on the screen.

[0081] Furthermore, the display value acquisition unit 102b in the Web server generates screen change information to be returned to the client at the same time as the reflection in step SB4 of Figure 26. The key point is that the generated screen change information contains only the value of the employee name label, and does not contain information that is not displayed on the screen, such as variables (in this example, the account number variable).

[0082] Next, because the display value acquisition unit 102b was able to acquire the account number variable "123456," the screen control information acquisition unit 102c in the Web server determines in step SB5 of Figure 26 that the condition "account number variable is not empty" in the condition setting table 106c described at the beginning of this section (2) is satisfied. If the condition is satisfied, in step SB5 of Figure 26, the screen control information acquisition unit 102c in the Web server performs screen control in accordance with the screen control information "hide account information input button" in the business rule setting table 106d described at the beginning of this section (2), and reflects the result of the screen control (account information input button display: FALSE) in the memory information.

[0083] At the same time as reflecting the changes, the screen control information acquisition unit 102c in the Web server updates the screen change information to be returned to the client in step SB5 of Figure 26. The key point is that the updated screen change information includes only information related to the value of the employee name label and the display state of the account information input button, and does not include information that is not displayed on the screen, such as variables (in this example, the account number variable).

[0084] Finally, in step SB6 of Figure 26, the sending unit 102d generates a response to be returned to the client based on the updated memory information and screen change information, and sends it from the web server to the web client via the network line. As a result, the employee name "Masakazu Aoki" is displayed on the web client screen, but the account information input button is not displayed. The key point is that this response only contains the value of the employee name label: Masakazu Aoki and information indicating that the account information input button should be hidden, and does not include information such as variables that are not displayed on the screen (in this example, the account number variable).

[0085] As explained above in section (2), in this embodiment, when screen information is changed due to an event or when screen values ​​are changed, the web server performs screen control, and the results of the screen control can be sent from the web server to the web client.

[0086] (3) Third example (Example 2: Screen control without events) As a third specific example, we will explain an example of switching between displaying and hiding the account information input button depending on the value of the radio button. Specifically, as shown in Figure 27, this is an example of screen control that displays the account information input button when the account setting radio button is changed from "Use default" to "Set up."

[0087] In this specific example, the prerequisite is that the condition in the condition setting table 106c is set as "The account setting radio button is set to 'Set'," and the screen control information in the business rule setting table 106d is set as "Display the account information input button."

[0088] (3-1) Screen startup process The processing when the screen is started is the same as the processing content explained in (1-1), but in this example, as shown in Fig. 28, it is assumed that the ID "2-5-2" of the radio button control to be set is sent from the web server to the web client as the control information (= the ID of the control existing in the condition setting table 106c) specified in the condition used in (B) screen control. In other words, it is assumed that the web client holds the ID "2-5-2" of the radio button control to be set as the state change control.

[0089] (3-2) Processing when verification processing is triggered First, in step SC1 of FIG. 29, an event is executed when the account setting radio button on the Web client screen is changed from "Use default" to "Set up."

[0090] Next, in step SC2 of Figure 29, the Web client determines whether the radio button control for which the event was fired corresponds to a state change control. In this example, as described in (3-1), the Web client holds the radio button control for which the event was fired as a state change control, so it is determined that it corresponds. If it corresponds, information about the radio button control for which the event was fired is sent as a request from the Web client to the Web server via a network line.

[0091] Next, the event allocation determination unit 102a in the Web server determines whether or not the radio button control to be set exists in the event allocation definition table 106a in step SC3 of Fig. 29. In this example, the event allocation definition table 106a does not have the radio button control to be set, so the event allocation determination unit 102a determines that it does not exist.

[0092] Next, because the account setting radio button has been changed to the "Perform Settings" radio button in step SC1 of (3-2), the screen control information acquisition unit 102c in the Web server determines in step SC5 of Figure 29 that the condition "The account setting radio button is 'Perform Settings'" in the condition setting table 106c described at the beginning of this section (2) is satisfied. If the condition is satisfied, in step SC5 of Figure 29, the screen control information acquisition unit 102c in the Web server performs screen control in accordance with the screen control information "Display account information input button" in the business rule setting table 106d described at the beginning of this section (2), and reflects the result of the screen control (account information input button display: TRUE) in the memory information.

[0093] Furthermore, the screen control information acquisition unit 102c in the Web server generates screen change information to be returned to the client at the same time as the reflection in step SC5 of FIG.

[0094] Finally, in step SC6 of Fig. 29, the sending unit 102d generates a response to be returned to the client based on the generated memory information and screen change information, and sends the response from the Web server to the Web client via the network line. As a result, an account information input button is displayed on the screen of the Web client.

[0095] As explained above in section (3), in this embodiment, even if no event is set, if screen control information is set, the web server can perform screen control in accordance with the screen control information, and the results of the screen control can be sent from the web server to the web client.

[0096] [5. Summary of this embodiment] As explained above, according to the confidential item leakage prevention device 100 of this embodiment, as mainly explained in (2) of [4-2], the contents of the confidential items are not transmitted to the Web client, but rather at least one of the display value, which is the value displayed on the screen of the Web client, and the screen control information, which is information for controlling the contents displayed on the screen, is transmitted to the Web client, thereby preventing leakage of the contents of the confidential items.

[0097] [6. Contribution to the United Nations-led Sustainable Development Goals (SDGs)] This embodiment can contribute to improving business efficiency and promoting appropriate management decisions by companies, thereby contributing to the achievement of SDGs Goals 8 and 9.

[0098] Furthermore, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, thereby contributing to the achievement of SDGs Goals 12, 13, and 15.

[0099] Furthermore, this embodiment can contribute to strengthening control and governance, which can contribute to the achievement of Goal 16 of the SDGs.

[0100] 7. Other Embodiments The present invention may be implemented in various different embodiments other than those described above within the scope of the technical concept set forth in the claims.

[0101] For example, among the processes described in the embodiments, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically using known methods.

[0102] Furthermore, the processing procedures, control procedures, specific names, information including parameters such as registered data and search conditions for each process, screen examples, and database configurations shown in this specification and drawings can be changed as desired unless otherwise specified.

[0103] Furthermore, with regard to the confidential item leakage prevention device 100, the components shown in the figures are functional concepts, and do not necessarily have to be physically configured as shown in the figures.

[0104] For example, all or any part of the processing functions of the confidential item leakage prevention device 100, particularly the processing functions performed by the control unit, may be implemented by a CPU and a program interpreted and executed by the CPU, or may be implemented as hardware using wired logic. The program is recorded on a non-transitory computer-readable recording medium containing programmed instructions for causing the information processing device to execute the processes described in this embodiment, and is mechanically read by the confidential item leakage prevention device 100 as needed. That is, a computer program for providing instructions to the CPU in cooperation with the OS and performing various processes is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive). This computer program is executed by being loaded into RAM and cooperates with the CPU to form the control unit.

[0105] In addition, this computer program may be stored in an application program server connected to the confidential item leakage prevention device 100 via any network, and it is also possible to download all or part of it as needed.

[0106] Furthermore, the program for executing the processes described in this embodiment may be stored in a non-transitory computer-readable recording medium or configured as a program product. Here, the term "recording medium" includes any "portable physical medium" such as a memory card, a Universal Serial Bus (USB) memory, a Secure Digital (SD) card, a flexible disk, a magneto-optical disk, a ROM, an Erasable Programmable Read Only Memory (EPROM), an Electrically Erasable and Programmable Read Only Memory (EEPROM (registered trademark)), a Compact Disk Read Only Memory (CD-ROM), a Magneto-Optical disk (MO), a Digital Versatile Disk (DVD), and a Blu-ray (registered trademark) disc.

[0107] Furthermore, a "program" is a data processing method written in any language or description method, regardless of the format, such as source code or binary code. Note that a "program" is not necessarily limited to a single structure, but also includes a structure that is distributed as multiple modules or libraries, or a structure that achieves its function by cooperating with a separate program, such as an OS. Note that the specific configuration and reading procedure for reading a recording medium in each device shown in the embodiments, as well as the installation procedure after reading, can use well-known configurations and procedures.

[0108] The various databases stored in the memory unit are storage means such as memory devices such as RAM and ROM, fixed disk devices such as hard disks, flexible disks, and optical disks, and store various programs, tables, databases, and web page files used for various processes and providing websites.

[0109] The confidential item leakage prevention device 100 may be configured as an information processing device such as a known personal computer or workstation, or may be configured as the information processing device to which any peripheral device is connected. The confidential item leakage prevention device 100 may be realized by installing software (including programs, data, etc.) that causes the device to perform the processing described in this embodiment.

[0110] Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the drawings, and all or part of them can be configured by functionally or physically distributing and integrating them in any unit depending on various additions or functional loads. In other words, the above-described embodiments can be implemented in any combination, or embodiments can be implemented selectively. [Industrial Applicability]

[0111] The present invention is useful, for example, in fields where a screen display is required. [Explanation of symbols]

[0112] 100 Confidential item leakage prevention device (Web server) 102 Control section 102a Event allocation determination unit 102b Display value acquisition unit 102c Screen control information acquisition unit 102d Transmitter 104 Communication interface unit 106 Storage section 106a Event assignment definition table 106b Action Settings Table 106c Condition Setting Table 106d Business Rule Settings Table 200 Web clients 300 Network

Claims

1. A confidential item leakage prevention device as a web server, comprising a control unit and a storage unit, which can prevent leakage of the contents of confidential items by transmitting to the web client only at least one of a display value, which is a value displayed on a screen of the web client, and screen control information, which is information for controlling the contents displayed on the screen, without transmitting the contents of the confidential items to the web client, The storage unit includes: an event assignment definition table in which events are assigned to controls that are elements that configure the screen; an action setting table in which the control is set as an argument and a return value; a condition setting table in which predetermined conditions for the confidential items or the controls are set; a business rule setting table in which rules are set that define what control should be performed on the screen when the predetermined condition is satisfied; is stored, The control unit an event allocation determination means for determining whether or not the control whose value has been input or changed exists in the event allocation definition table when information on the control whose value has been input or changed on the screen is transmitted from the Web client to the Web server; a display value acquisition means for, when the event assignment determination means determines that the control exists, referencing the action setting table and using the control whose value has been input or changed as an argument, acquiring a corresponding return value as the display value; a screen control information acquisition means for determining whether the content of the confidential item corresponding to the display value acquired by the display value acquisition means or the value of the control into which the value has been input or changed satisfies the predetermined condition in the condition setting table, and if so, acquiring the rule in the business rule setting table as the screen control information; a transmitting means for transmitting at least one of the display value acquired by the display value acquiring means and the screen control information acquired by the screen control information acquiring means from the web server to the web client; To have A device for preventing leakage of confidential items, characterized by:

2. information on a control whose value has been input or changed on said screen is transmitted from said Web client to said Web server when either a condition that said control exists in said event assignment definition table or a condition that said control exists in said condition setting table is satisfied; 2. The device for preventing leakage of confidential items according to claim 1.

3. A method for preventing leakage of confidential items executed by a web server having a control unit and a storage unit, which can prevent leakage of the contents of confidential items by transmitting to the web client only at least one of a display value, which is a value displayed on a screen of the web client, and screen control information, which is information for controlling the contents displayed on the screen, without transmitting the contents of the confidential items to the web client, The storage unit includes: an event assignment definition table in which events are assigned to controls that are elements that configure the screen; an action setting table in which the control is set as an argument and a return value; a condition setting table in which predetermined conditions for the confidential items or the controls are set; a business rule setting table in which rules are set that define what control should be performed on the screen when the predetermined condition is satisfied; is stored, Executed by the control unit, an event allocation determination step of determining whether or not the control whose value has been input or changed exists in the event allocation definition table when information of the control whose value has been input or changed on the screen is transmitted from the Web client to the Web server; a display value acquisition step of, when it is determined in the event assignment determination step that the control exists, referring to the action setting table and using the control in which the value has been input or changed as an argument, acquiring a corresponding return value as the display value; a screen control information acquisition step of determining whether the content of the confidential item corresponding to the display value acquired in the display value acquisition step or the value of the control into which the value has been input or changed satisfies the predetermined condition in the condition setting table, and if so, acquiring the rule in the business rule setting table as the screen control information; a transmitting step of transmitting at least one of the display value acquired in the display value acquiring step and the screen control information acquired in the screen control information acquiring step from the web server to the web client; containing, A method for preventing leakage of confidential items, comprising:

4. A confidential item leakage prevention program to be executed by a web server having a control unit and a storage unit, which can prevent leakage of the contents of confidential items by transmitting to the web client only at least one of a display value, which is a value displayed on a screen of the web client, and screen control information, which is information for controlling the contents displayed on the screen, without transmitting the contents of the confidential items to the web client, The storage unit includes: an event assignment definition table in which events are assigned to controls that are elements that configure the screen; an action setting table in which the control is set as an argument and a return value; a condition setting table in which predetermined conditions for the confidential items or the controls are set; a business rule setting table in which rules are set that define what control should be performed on the screen when the predetermined condition is satisfied; is stored, To cause the control unit to execute an event allocation determination step of determining whether or not the control whose value has been input or changed exists in the event allocation definition table when information of the control whose value has been input or changed on the screen is transmitted from the Web client to the Web server; a display value acquisition step of, when it is determined in the event assignment determination step that the control exists, referring to the action setting table and using the control in which the value has been input or changed as an argument, acquiring a corresponding return value as the display value; a screen control information acquisition step of determining whether the content of the confidential item corresponding to the display value acquired in the display value acquisition step or the value of the control into which the value has been input or changed satisfies the predetermined condition in the condition setting table, and if so, acquiring the rule in the business rule setting table as the screen control information; a transmitting step of transmitting at least one of the display value acquired in the display value acquiring step and the screen control information acquired in the screen control information acquiring step from the web server to the web client; containing, A program for preventing the leakage of confidential information.

Images