JP2019185542A - Application execution device, control method therefor, and program - Google Patents

Abstract

To provide an application execution device capable of making an administrator provide appropriate security management of an application.SOLUTION: An MFP, acting as an application execution device, stores history information including information pertaining to a cryptographic module that is used while running a Java (R) application. The MFP then identifies a type of cryptographic module that realizes cryptographic function of an application on the basis of the history information, and displays a cryptography usage state 307, an identification result, on an application information screen 300.SELECTED DRAWING: Figure 3

Description

  The present invention relates to an application execution device, a control method thereof, and a program.

  In addition to standard functions such as a copy function, a print function, a scan function, and a FAX transmission / reception function, an MFP (Multi Function Peripheral) is known as an application execution device capable of expanding functions. The MFP acquires an application (hereinafter referred to as “extended application”) for extending the function from an external device or the like, and installs the acquired extended application. In the MFP, the extended application is operated in a predetermined execution environment such as Java VM (Java Virtual Machine) in response to an instruction to execute the extended application by the user.

  By the way, in the MFP, when executing an extended application, an encryption process may be performed in order to prevent information leakage to a third party and data falsification. The encryption processing is, for example, encryption communication in SSL / TLS communication or backup data encryption processing in image data backup. In order to perform such encryption processing, an MFP includes a cryptographic module that is a software module having an encryption function and a decryption function. For example, a standard-compliant cryptographic module that complies with FIPS140-2 is incorporated in the MFP as a cryptographic module capable of performing an encryption process that guarantees a specific security level. FIPS 140-2 is a standard for cryptography, and is a standard for authenticating that a secure cryptographic algorithm is correctly implemented. In the encryption process using the standard-compliant encryption module, an encryption algorithm that is regarded as vulnerable, such as RC4 or RSA1024, is not used. On the other hand, the MFP is required to cooperate with a relatively old business system, and some applications may require RC4 or RSA 1024. Corresponding to such a case, in addition to the standard-compliant cryptographic module, the MFP also incorporates a standard-noncompliant cryptographic module that does not comply with FIPS140-2. In the MFP, the encryption module used for each application is switched (for example, see Patent Document 1).

JP 2012-133812 A

  However, in the conventional MFP, the above-described encryption module switching is performed by internal processing of the MFP. For this reason, conventionally, the administrator of the MFP cannot confirm that the standard-compliant cryptographic module is used in the encryption processing of an application that requires a specific security level. As a result, there arises a problem that the administrator of the MFP cannot appropriately manage the security of each application.

  An object of the present invention is to provide an application execution apparatus, a control method therefor, and a program that allow an administrator to appropriately manage application security.

  In order to achieve the above object, an application execution apparatus of the present invention is an application execution apparatus including a plurality of encryption modules for realizing an encryption function in an application, and the encryption module used when executing the application Storage means for storing history information including information related to, a determination means for determining the type of the cryptographic module that realizes the encryption function of the application based on the history information, and a notification for performing notification control of the determination result by the determination means And a control means.

  ADVANTAGE OF THE INVENTION According to this invention, an administrator can perform an application security management appropriately.

1 is a block diagram schematically showing a configuration of an MFP as an application execution apparatus according to an embodiment of the present invention. FIG. 2 is a block diagram schematically showing a software configuration of the MFP in FIG. 1. It is a figure which shows an example of the application information screen display-controlled by the Java application management part of FIG. It is a figure which shows an example of the provider definition file of FIG. 3 is a flowchart showing a procedure of control processing related to display of an application information screen executed by the MFP of FIG. 1. It is a figure which shows an example of the log | history information memorize | stored in HDD of FIG. It is a figure which shows an example of the application information screen display-controlled by the Java application management part of FIG. It is a figure which shows an example of the setting screen displayed on the operation part of FIG. 3 is a flowchart showing a procedure of encryption control processing executed by the MFP of FIG. 1. It is a figure which shows an example of the warning screen display-controlled by the Java application management part of FIG.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

  FIG. 1 is a block diagram schematically showing a configuration of MFP 100 as an application execution apparatus according to an embodiment of the present invention. In FIG. 1, the MFP 100 includes a control unit 101, an operation unit 107, a printer 109, and a scanner 111. The control unit 101 is connected to the operation unit 107, the printer 109, and the scanner 111. The control unit 101 includes a CPU 102, ROM 103, RAM 104, HDD 105, operation unit I / F 106, printer I / F 108, scanner I / F 110, FAX I / F 112, and network I / F 113. The CPU 102, ROM 103, RAM 104, HDD 105, operation unit I / F 106, printer I / F 108, scanner I / F 110, FAX I / F 112, and network I / F 113 are connected to each other via a system bus 114.

  MFP 100 incorporates standard functions such as a copy function, a scan function, and a communication function in advance. Further, in the MFP 100, functions corresponding to the Java application 201 can be expanded by installing a Java application 201 shown in FIG. Further, the MFP 100 provides a management function of a Java application 201 (described later) installed in the MFP 100 to an external device (not shown) on a network connected via a LAN cable (not shown). A control unit 101 controls the overall operation of the MFP 100. The CPU 102 reads a program stored in the ROM 103 and performs control such as reading control and transmission control. The RAM 104 is used as a main memory of the CPU 102 and a temporary storage area for each data. The HDD 105 stores image data and programs. The operation unit I / F 106 connects the operation unit 107 and the control unit 101. Operation unit 107 displays a setting screen for performing various settings of MFP 100. The operation unit 107 receives an instruction from the user.

  A printer I / F 108 connects the printer 109 and the control unit 101. For example, the printer I / F 108 transfers the image data acquired from the control unit 101 to the printer 109. The printer 109 performs print processing based on the image data transferred from the printer I / F 108. The scanner I / F 110 connects the scanner 111 and the control unit 101. The scanner 111 generates scan image data based on information obtained by reading a document. The scanner 111 transmits the scan image data to the control unit 101 via the scanner I / F 110. The FAX I / F 112 connects the control unit 101 to a telephone line (not shown). The FAX I / F 112 transmits and receives FAX data via the telephone line. The network I / F 113 connects the control unit 101 to the LAN cable. The network I / F 113 performs data communication with an external device on the network connected via the LAN cable. For example, the network I / F 113 receives a print instruction from an external device on the network connected via a LAN cable, and transmits a response to the print instruction.

  FIG. 2 is a block diagram schematically showing a software configuration of MFP 100 in FIG. In FIG. 2, the MFP 100 has two hierarchies of a VM environment and a native environment as the operating environment of the software module. In the MFP 100, the installed Java application 201 is operated in the VM environment, and the native application 211 incorporated in advance in the MFP 100 is operated in the native environment.

  In the VM environment, the Java VM 200 causes the CPU 102 to execute the Java application 201 installed to expand the functions of the MFP 100 based on an instruction from the Java application management unit 202 (notification control unit). The Java application 201 is a module that is described in the Java language and in which the program is converted into Java-specific bytecode. In the present embodiment, for ease of explanation, only one Java application 201 is shown in FIG. 2, but the MFP 100 can install a plurality of different types of Java applications. A Java application management unit 202 provides a management function related to a Java application installed in the MFP 100 to an external device (not shown) via the network I / F 113. For example, the Java application management unit 202 displays the application information screen 300 in FIG. 3 on the display unit (not shown) of the external device that has made a management function use request (display request).

  The application information screen 300 includes an application name 301, an application status 302, an encryption usage status 307, an input field 308, and an install button 309. In the application name 301, the name of the Java application installed in the MFP 100 is displayed. In the application status 302, the status of the Java application installed in the MFP 100 is displayed. Further, the application state 302 displays operation buttons for instructing start and stop of each Java application installed in the MFP 100. For example, when a file transmission application that is an installed Java application is being executed, a start 303 indicating that the file transmission application is being executed is displayed in the application status 302 of the file transmission application as shown in FIG. Further, as shown in FIG. 3, a stop button 304 for instructing to stop execution of the file transmission application is displayed in the application state 302 of the file transmission application.

  On the other hand, when the copy application, which is an installed Java application, is stopped, a stop 305 indicating that the copy application is stopped is displayed in the application status 302 of the copy application as shown in FIG. Further, in the application status 302 of the copy application, a start button 306 for giving an instruction to start execution of the copy application is displayed as shown in FIG. In the encryption usage status 307, information regarding whether or not to use the encryption function in each Java application installed in the MFP 100 is displayed, and a clear button 310 is displayed. Details of the clear button 310 will be described later. As described above, the administrator can confirm information related to the Java application installed in the MFP 100 and give instructions regarding execution of the Java application from the application information screen 300. Further, the administrator can issue an instruction to start processing for installing the Java application stored in the external device in the MFP 100 from the application information screen 300. For example, when the administrator inputs a file path indicating the storage location of the Java application 201 in the input field 308 and further selects the install button 309, the Java application 201 is transmitted from the external device to the MFP 100. The MFP 100 stores the received Java application 201 in the HDD 105. In addition, the MFP 100 starts the installation of the Java application 201 by the Java application management unit 202.

  Returning to FIG. 2, in the Java VM 200, a plurality of cryptographic providers are incorporated in advance as software modules that provide a cryptographic function to the Java application 201. Specifically, the Java VM 200 incorporates an FIPS encryption provider 204 and a nonFIPS encryption provider 205. The FIPS cryptographic provider 204 provides a cryptographic function by the FIPS cryptographic module 209 (standard compliant cryptographic module) compliant with FIPS 140-2. FIPS 140-2 is a standard for cryptography, and is a standard for authenticating that a secure cryptographic algorithm is correctly implemented. The nonFIPS cryptographic provider 205 provides a cryptographic function by a nonFIPS cryptographic module 210 (standard noncompliant cryptographic module) that does not comply with FIPS140-2. Here, in the MFP 100, when using the encryption function, it is preferable to use the FIPS encryption module 209 from the viewpoint of security. However, since the FIPS cryptographic module 209 has limited cryptographic algorithms that can be used, the MFP 100 cannot perform encrypted communication with an external device that uses a compromised cryptographic algorithm such as RC4. That is, if only the FIPS encryption module 209 is usable in the MFP 100, there arises a problem that communication partners are limited. On the other hand, in the MFP 100, both the FIPS encryption module 209 and the nonFIPS encryption module 210 are incorporated, and the encryption module is switched for each application using the encryption function. In this embodiment, a case where two cryptographic providers are incorporated in the Java VM 200 will be described. However, three or more cryptographic providers may be incorporated in the Java VM 200.

  When the Java VM 200 starts up, the Java VM 200 calls the cryptographic providers set in the provider definition file 206 one by one. In the provider definition file 206, as shown in FIG. 4, the names and priorities of all the cryptographic providers incorporated in advance in the MFP 100 are set. The cryptographic provider called by the Java VM 200 is registered in the Java VM 200. At this time, the priority order corresponding to the called cryptographic provider is also registered based on the provider definition file 206. For example, based on the provider definition file 206 of FIG. 4, the FIPS cryptographic provider 204 is registered with the priority order 1, and the nonFIPS cryptographic provider 205 is registered with the priority order 2. In JavaVM 200, a registered cryptographic provider can provide a cryptographic function to Java application 201.

  The Java application 201 requests the Java encryption unit 207 to use the encryption function when using the encryption function. In the usage request for the cryptographic function, the cryptographic provider to be used can be specified. For example, when receiving a cryptographic function use request specifying the nonFIPS cryptographic provider 205, the Java cryptographic unit 207 calls the nonFIPS cryptographic provider 205. The nonFIPS encryption provider 205 provides the Java application 201 with the encryption function by the nonFIPS encryption module 210 via the Native encryption unit 208. On the other hand, when a cryptographic function use request for which a cryptographic provider is not specified is received, the Java cryptographic unit 207 calls, for example, the FIPS cryptographic provider 204 with the highest priority according to the priority of each cryptographic provider registered in the Java VM 200. . The FIPS encryption provider 204 provides the Java application 201 with the encryption function of the FIPS encryption module 209 via the native encryption unit 208. Note that JNI (Java Native Interface) is used for function calls between the VM environment and the native environment.

  In the native environment, the native application 211 is executed. The native application 211 includes, for example, a native code obtained by converting a program written in C language into a machine language code. The native application 211 executes standard functions such as copying, printing, scanning, and FAX transmission / reception. When the native application 211 uses the encryption function, the nonFIPS encryption module 210 or the FIPS encryption module 209 is used via the native encryption unit 208.

  FIG. 5 is a flowchart showing a procedure of control processing related to display of application information screen 300 executed by MFP 100 in FIG. FIG. 5A is a flowchart showing a history information storage process performed by MFP 100 in FIG. The process in FIG. 5A is performed by the CPU 102 executing a program stored in the ROM 103. The process of FIG. 5A is performed when a Java application installed in the MFP 100 is executed. In the present embodiment, as an example, a case where the Java application 201 is executed will be described.

  5A, first, when the encryption function is called by the Java application 201 (step S501), the CPU 102 stores history information in the HDD 105 by the native encryption unit 208 (step S502). As shown in FIG. 6, the history information is information indicating the date and time when the cryptographic function was called, the name of the Java application that called the cryptographic function, and the cryptographic provider used. In the present embodiment, the history information stored in the HDD 105 is retained until the clear button 310 on the application information screen 300 is selected by the administrator. Thereafter, the CPU 102 ends this process.

  FIG. 5B is a flowchart showing a procedure of display control processing executed by the MFP 100 of FIG. The process of FIG. 5B is also performed by the CPU 102 executing a program stored in the ROM 103. The process in FIG. 5B is executed when the MFP 100 receives a request for using the management function of the Java application from an external device via the network I / F 113. In the present embodiment, the process of FIG. 5B is executed for all Java applications installed in the MFP 100. In the following, as an example, among the Java applications installed in the MFP 100, the Java application is installed. A case where the processing is executed on 201 will be described.

  In FIG. 5B, the CPU 102 determines whether or not the Java application 201 has used the cryptographic module (step S503). In step S503, when history information indicating that the Java application 201 has used the cryptographic module is stored in the HDD 105, the CPU 102 determines that the Java application 201 has used the cryptographic module. On the other hand, when the history information indicating that the Java application 201 has used the cryptographic module is not stored in the HDD 105, the CPU 102 determines that the Java application 201 does not use the cryptographic module.

  As a result of the determination in step S503, when the Java application 201 does not use the cryptographic module, the CPU 102 displays an application information screen indicating this on the display unit of the external device. Specifically, the CPU 102 displays “no encryption usage” in the encryption usage status 307 of the Java application 201 on the application information screen (step S504). An application information screen 700 in FIG. 7 is a display example when the copy application and the file sharing application among the Java applications installed in the MFP 100 do not use the encryption module. Next, the CPU 102 ends this process.

  As a result of the determination in step S503, when the Java application 201 uses the cryptographic module, the CPU 102 determines whether the Java application 201 has used the nonFIPS cryptographic module 210 based on the history information (step S505). Here, a case where the history information shown in FIG. 6 is stored in the HDD 105 will be described as an example. For example, the history information indicating that the file transmission application has used the nonFIPS encryption provider 205 that provides the encryption function by the nonFIPS encryption module 210 is not stored in the HDD 105 as shown in FIG. At this time, the CPU 102 determines that the file transmission application that is the Java application 201 does not use the nonFIPS encryption module 210. On the other hand, history information 601 and 602 indicating that the print application has used the nonFIPS encryption provider 205 is stored in the HDD 105 as shown in FIG. At this time, the CPU 102 determines that the print application that is the Java application 201 uses the nonFIPS encryption module 210. In the present embodiment, when at least one history information indicating that the Java application 201 has used the nonFIPS encryption provider 205 is stored in the HDD 105, it is determined that the Java application 201 has used the nonFIPS encryption module 210. The

  As a result of the determination in step S505, when the Java application 201 does not use the nonFIPS encryption module 210, the CPU 102 determines that the Java application 201 uses the FIPS encryption module 209. The CPU 102 displays an application information screen indicating this on the display unit of the external device. Specifically, the CPU 102 displays “FIPS” in the encryption usage status 307 of the Java application 201 on the application information screen (step S506). An application information screen 700 in FIG. 7 is a display example when the file transmission application uses the FIPS encryption module 209 among the Java applications installed in the MFP 100. Next, the CPU 102 ends this process.

  As a result of the determination in step S505, when the Java application 201 uses the nonFIPS encryption module 210, the CPU 102 displays an application information screen indicating this on the display unit of the external device. Specifically, the CPU 102 displays “nonFIPS” in the encryption usage status 307 of the Java application 201 on the application information screen (step S507). An application information screen 700 in FIG. 7 is a display example when the print application uses the nonFIPS encryption module 210 among the Java applications installed in the MFP 100. In other words, in the present embodiment, the encryption usage status 307 of each Java application is displayed based on the history information stored when each Java application installed in MFP 100 is executed. Thereafter, the CPU 102 ends this process.

  According to the above-described embodiment, history information including information regarding the cryptographic module used when each Java application installed in MFP 100 is executed is stored in HDD 105. Also, the type of the cryptographic module used by the Java application 201 is determined based on the history information, and the encryption usage status 307 as the determination result is displayed. As a result, it is possible to notify the administrator of the MFP 100 of information related to the cryptographic module used in each Java application installed in the MFP 100, and thus it is possible to cause the administrator to appropriately manage the security of the Java application.

  In the above-described embodiment, the history information holding state of each Java application is reset in accordance with an instruction from the administrator. For example, it is assumed that the administrator of the MFP 100 has dealt with a Java application in which “nonFIPS” is displayed in the encryption usage status 307 so that only the FIPS encryption module 209 is used. As a coping method, for example, there is a change in the communication destination setting for encrypted communication by the Java application, a change in the setting for encryption of the Java application, or a modification of the Java application by the developer of the Java application. After any of the above countermeasures is implemented, when the administrator of the MFP 100 selects the clear button 310 of the encryption usage status 307 of the Java application on the application information screen 300, the history information of the Java application is reset. . In this way, only information related to the cryptographic module used by the Java application after handling can be accumulated.

  Further, in the above-described embodiment, the encryption usage status is displayed when a usage request for the management function of the Java application 201 is received. Thereby, the administrator of MFP 100 can be notified of the encryption usage status at a timing desired by the administrator of MFP 100.

  As described above, the present invention has been described using the above-described embodiment, but the present invention is not limited to the above-described embodiment. For example, history information may be displayed directly. As a result, detailed information regarding the cryptographic module used in each Java application can be notified to the administrator of MFP 100.

  Further, in the above-described embodiment, only the history information of the Java application having experience using both the FIPS encryption module 209 and the nonFIPS encryption module 210 among the history information stored in the HDD 105 may be notified. As a result, it is possible to prevent useless display such as displaying a plurality of history information of Java applications that have used only one type of cryptographic module.

  Furthermore, in the above-described embodiment, a limit may be set on the number of history information of each Java application stored in the HDD 105. As a result, it is possible to prevent the capacity of the HDD 105 from becoming tight by storing the history information of each Java application.

  In the above-described embodiment, the administrator may set the operation control information regarding the restriction on the execution of the Java application that uses the encryption function by the nonFIPS encryption module 210. In the process of FIG. 5 described above, it is not possible to notify the administrator of a high-accuracy cryptographic usage state unless each Java application installed in the MFP 100 accumulates history information to some extent using the cryptographic function. For this reason, before the history information is accumulated to some extent, the encryption function by the nonFIPS encryption module 210 is inadvertently used, so that a desired security level cannot be maintained.

  Corresponding to this, in the present embodiment, the administrator of MFP 100 sets operation control information from setting screen 800 in FIG. A setting screen 800 is displayed on the operation unit 107. The setting screen 800 includes a prohibit button 801, a warning button 802, a permission button 803, and an OK button 804. When the OK button 804 is selected by the administrator with any of the prohibit button 801, the warning button 802, and the allow button 803 set, information indicating the set button is stored in the HDD 105 as operation control information of the Java application 201. Remembered.

  FIG. 9 is a flowchart showing a procedure of encryption control processing executed by MFP 100 of FIG. The processing in FIG. 9 is also performed by the CPU 102 executing a program stored in the ROM 103. The processing in FIG. 9 is executed when the user instructs execution of the Java application 201 that uses the encryption function.

  In FIG. 9, the CPU 102 determines whether or not the Java application 201 uses the nonFIPS encryption module 210 using the native encryption unit 208 (step S <b> 901).

  As a result of the determination in step S <b> 901, when the Java application 201 does not use the nonFIPS cryptographic module 210, the CPU 102 ends this process. As a result of the determination in step S <b> 901, when the Java application 201 uses the nonFIPS encryption module 210, the CPU 102 acquires operation control information of the Java application 201 from the HDD 105 using the native encryption unit 208. Next, the CPU 102 uses the native encryption unit 208 to determine whether or not the acquired operation control information indicates the prohibit button 801 (step S902).

  As a result of the determination in step S902, when the operation control information indicates the prohibit button 801, the CPU 102 notifies the name of the Java application 201 from the native encryption unit 208 to the Java application management unit 202. Next, the CPU 102 stops the Java application 201 by the Java application management unit 202 that has received the notification (step S903), and ends this processing.

  As a result of the determination in step S902, when the operation control information does not indicate the prohibit button 801, the CPU 102 determines whether or not the operation control information indicates the warning button 802 by the native encryption unit 208 (step S904).

  As a result of the determination in step S904, when the operation control information does not indicate the warning button 802, the CPU 102 causes the nonFIPS encryption module 210 to operate using the native encryption unit 208 (step S905). Thereby, the cryptographic function by the nonFIPS cryptographic module 210 is provided to the Java application 201. Next, the CPU 102 ends this process.

  As a result of the determination in step S904, when the operation control information indicates the warning button 802, the CPU 102 displays the warning screen 1000 of FIG. The warning screen 1000 includes a message 1001 confirming an intention to use the nonFIPS encryption module 210, a permission button 1002, and a prohibition button 1003. The user can select either the allow button 1002 or the prohibit button 1003. In addition, the CPU 102 causes the Java application management unit 202 to stop the Java application 201 (step S906). Next, the CPU 102 determines which of the permission button 1002 and the prohibition button 1003 has been selected on the warning screen 1000 (step S907).

  As a result of the determination in step S907, when the prohibit button 1003 is selected, the CPU 102 ends this process. As a result of the determination in step S907, when the permission button 1002 is selected, the CPU 102 causes the Java application management unit 202 to restart the operation of the Java application 201 (step S908), and performs the processing from step S905 onward.

  In the above-described embodiment, the operation control information related to the restriction on the execution of the Java application that uses the cryptographic function by the nonFIPS cryptographic module 210 is set. Thereby, it is possible to prevent the encryption function by the nonFIPS encryption module 210 from being used carelessly before the history information is accumulated to some extent.

  The present invention supplies a program that realizes one or more functions of the above-described embodiments to a system or apparatus via a network or a storage medium, and one or more processors in a computer of the system or apparatus read the program. It can also be realized by processing to be executed. The present invention can also be realized by a circuit (for example, ASIC) that realizes one or more functions.

100 MFP
201 Java application 202 Java application management unit 209 FIPS encryption module 210 nonFIPS encryption module 601, 602 History information 300, 700 Application information screen 800 Setting screen

Claims (8)

An application execution device including a plurality of cryptographic modules for realizing a cryptographic function in an application,
Storage means for storing history information including information on the cryptographic module used when the application is executed;
A discriminating means for discriminating a type of a cryptographic module for realizing the cryptographic function of the application based on the history information;
An application execution apparatus comprising: a notification control unit that performs notification control of a determination result by the determination unit.   The application execution apparatus according to claim 1, wherein the history information holding state is reset in accordance with an instruction of an administrator of the application execution apparatus.   The application execution apparatus according to claim 1, wherein the notification control unit performs control to display the determination result when a display request for information on the application is received.   The application execution apparatus according to claim 1, wherein the notification control unit performs control to display the history information. A standard-compliant cryptographic module that conforms to a specific standard and a non-standard cryptographic module that does not conform to the specific standard,
5. The application execution apparatus according to claim 4, wherein the notification control unit performs control to display history information of an application that has used both the standard-compliant cryptographic module and the non-standard-compliant cryptographic module.   6. The application execution apparatus according to claim 5, wherein operation control information related to restriction on execution of an application that uses the non-standard-compliant cryptographic module is set. A method for controlling an application execution apparatus including a plurality of cryptographic modules for realizing a cryptographic function in an application,
A storage step of storing history information including information on the cryptographic module used when executing the application;
A determining step of determining a type of a cryptographic module that realizes the cryptographic function of the application based on the history information;
And a notification control step for performing notification control of the determination result in the determination step. A program for causing a computer to execute a control method of an application execution apparatus including a plurality of cryptographic modules for realizing a cryptographic function in an application,
The control method of the application execution device is:
A storage step of storing history information including information on the cryptographic module used when executing the application;
A determining step of determining a type of a cryptographic module that realizes the cryptographic function of the application based on the history information;
A notification control step for performing notification control of the determination result in the determination step.

Images