JP2015079323A - Business management system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To inhibit a proper terminal belonging to one of a plurality of coexisting business management systems from being used in an unauthorized manner by a terminal belonging to the other business management system or non-proper terminal by software authentication.SOLUTION: In a business management system, a client terminal, an application server and a database server are connected to a network, respectively. At a start up of a business management application, the application server compares unique information of the application server with an authentication key of the application server registered with the data base server, and when it is determined that the application server is non-proper application server, the start up of the business management application is stopped.

Description

  The present invention relates to a business management system having a function of preventing unauthorized use of a terminal connected to a network.

  When a terminal connected to a network is authenticated in order to protect a network such as an in-house LAN (Local Area Network), each terminal is authenticated by a monitoring device installed in the network as described in Patent Document 1. It is known to perform connection restriction or to perform hardware authentication and connection restriction by an external medium connected to each terminal as described in Patent Document 2.

JP 2008-154012 A JP2011-29900A

  When each terminal is monitored by a monitoring device installed in the network, the monitoring device transmits an ARP (Address Resolution Protocol) request to all the terminals via the network at regular intervals, and then the ARP is transmitted from each terminal. The reply is received, the unique information of the request destination terminal is read from the received ARP reply frame, and the request destination terminal is authenticated (software authentication). If the request transmission destination terminal is determined to be an unregistered terminal by this authentication, the monitoring device can block network communication with the request transmission destination terminal by transmitting a disturbance message to the request transmission destination terminal.

  In addition, when a terminal brought in from the outside is connected to a protected network such as an in-house LAN, the monitoring device in the network uses the terminal brought in from the outside as a request destination terminal and sends an ARP to the request destination terminal. It is possible to send a request, then receive an ARP reply from the request destination terminal, read the unique information of the request destination terminal from the received ARP reply frame, and automatically authenticate the request destination terminal It is.

  However, in the above method, since the monitoring device targets all terminals connected to the network, when a plurality of business management systems are mixed and each business management system is connected to the network, a certain business management system If a terminal belonging to is authenticated as a regular terminal, use of the terminal cannot be restricted by another business management system. In other words, use of a terminal authenticated by the monitoring device cannot be restricted by any business management system. For this reason, the number of terminals that can be used for terminals authenticated by the monitoring apparatus cannot be limited or managed for each business management system.

  It is also conceivable to perform hardware authentication by connecting an external medium with a USB (Universal Serial Bus) or the like. By performing hard authentication with an external medium, it is possible to restrict connection for each device.

  However, it is difficult to use hard authentication in an environment where the external medium cannot be easily removed such as a dustproof / waterproof / explosion-proof area, or in a situation where the connection of the external medium is restricted such as a tablet.

  In the present invention, even when a plurality of business management systems coexist, a legitimate terminal belonging to one business management system is illegally used by a terminal belonging to another business management system or an unauthorized terminal by software authentication. An object of the present invention is to provide a business management system that can prevent the occurrence of problems.

  To achieve the above object, the present invention provides a client terminal connected to a network, an application server that exchanges information with the client terminal via the network, and unique information of the client terminal and the application server. A business management system including a database server having a database stored as an authentication key, and the application server is managed by the application server by accessing the database server when the business management application is started The unique information of the application server and the authentication key of the application server among the authentication keys registered in the database are collated, the collation result is inconsistent, and the application server If it is determined that the application server, characterized by stopping the activation of the business management applications.

  According to the present invention, even when a plurality of business management systems coexist, a legitimate terminal belonging to one business management system is illegally used by a terminal belonging to another business management system or an unauthorized terminal by software authentication. Can be prevented.

1 is an overall configuration diagram of a business management system according to the present invention. It is explanatory drawing for demonstrating the communication method between terminals. It is a flowchart for demonstrating the process of starting authentication of a server process. It is a flowchart for demonstrating the starting authentication process of a client process. It is a flowchart for demonstrating the process accompanying the process request of a client process. It is a flowchart for demonstrating the process of the specific information registration using an authentication management tool. It is a flowchart for demonstrating the process which determines a regular authentication key.

  Embodiments of the present invention will be described below with reference to the drawings.

(Example)
FIG. 1 is an overall configuration diagram of a business management system according to the present invention. In FIG. 1, a business management system includes a plurality of client terminals (hereinafter referred to as clients) 101a, 101b, and 101c, a plurality of application servers (hereinafter referred to as AP servers) 102a and 102b, and a database server (hereinafter referred to as a client server). Each of the clients 101 a, 101 b, 101 c, and each of the AP servers 102 a, 102 b and the DB server 103 are connected via a network 104. Note that one or more business management systems may be connected to the network 104 in addition to the business management system shown in FIG.

  Each of the clients 101a, 101b, and 101c is configured by a computer device including information processing resources such as a CPU (Central Processing Unit), a memory, and an input / output interface. At this time, the CPU of each of the clients 101a, 101b, and 101c executes processing according to a program stored in the memory, for example, generates a processing request, and sends the generated processing request to each AP server 102a via the network 104. , 102b.

  Each AP server 102a, 102b is configured by a computer device having information processing resources such as a CPU, a memory, and an input / output interface, for example. At this time, the CPU of each AP server 102a, 102b can start various programs stored in the memory.

  The DB server 103 is configured as a storage device that stores information regarding each terminal belonging to the business management system. The database of the DB server 103 includes, for example, unique information of the clients 101a, 101b, and 101c and the AP servers 102a and 102b. (Authentication key) and the like are stored.

  FIG. 2 is an explanatory diagram for explaining a communication method between terminals. In FIG. 2, a client 101 has a business process client process program (hereinafter referred to as a client process) 211 and an authentication management tool 212 as software resources stored in a memory. The client process 211 issues a processing request to the AP server 102 via the network 104 when the CPU is activated. The client 101 is a generic term for the clients 101a, 101b, and 101c.

  The AP server 102 includes a WEB service 221, a message queue 222, a business process server process program (hereinafter referred to as a server process) 223, and an authentication management tool 224 as software resources stored in the memory. The WEB service 221 functions as an interface for exchanging information with the client 101 via the network 104 and for exchanging information with the message queue 222. The message queue 222 functions as a memory that stores information and data from the WEB service 221 or the server process 223. The server process 223 activates a business system application (business management application) stored in the memory according to a command from the CPU, exchanges information with the DB server 103, processes a processing request from the client 101, and processes When the request is accepted, it functions as an application processing unit that executes processing according to the processing request. The AP server 102 is a generic name for the AP servers 102a and 102b. The DB server 103 has database software 231 as software resources stored in the memory.

  When communication is performed between the client 101 and the AP server 102, communication is performed between the client process 211 and the server process 223. At this time, first, the client process 211 queues a processing request in the message queue 222 via the WEB service 221. The server process 223 sequentially monitors the message queue 222. When a processing request is stored in the message queue 222, the server process 223 extracts the processing request from the message queue 222. The server process 223 communicates with the DB software 231 of the DB server 103 based on the extracted processing request, accesses the DB software 231, executes processing according to the processing request, and stores the processing result in the message queue 222. The processing result stored in the message queue 222 is transferred from the WEB service 221 to the client process 211 via the network 104. When the client process 211 receives the processing result via the WEB service 221, the client process 211 and the server process 223 communicate with each other.

  Further, the authentication management tool 212 and the authentication management tool 224 can register specific information (authentication key) and the like regarding the client 101 and the AP server 102 in the DB software 231 by directly connecting to the DB software 231. At this time, only unique information (authentication key) relating to each terminal belonging to the business management system is registered in the DB software 231 as unique information (authentication key) relating to each terminal.

  FIG. 3 is a flowchart for explaining the server process activation authentication process. In FIG. 3, when the server process 223 starts a business management application in response to a command from the CPU of the AP server 102 (S <b> 300), the server process 223 acquires specific information of the AP server 102 from the memory of the AP server 102. Then, a hash value is generated based on the acquired unique information (S301). Next, the server process 223 collates the generated hash value with the hash value of the unique information of the AP server 102 registered in advance in the DB software 231 (S302), and the AP server 102 is a legitimate terminal. It is determined whether or not (S303). If a positive determination result is obtained in step S303, that is, if both hash values match and the AP server 102 authenticates that it is a legitimate terminal (a legitimate AP server), the server process 223 is activated. Is held, and the process at the time of activation is executed, and then the activation of itself is completed (S304), and the process in this routine is terminated.

  On the other hand, if a negative determination result is obtained in step S303, that is, if both hash values do not match and the AP server 102 authenticates that it is an unauthorized terminal (non-authorized AP server), the server The process 223 outputs an error log (S305), and then terminates itself after stopping its activation (S306), and ends the processing in this routine.

  As described above, the server process 223 has the hash value generated from the unique information of the AP server 102 and the hash value of the unique information of the AP server 102 registered in advance in the DB software 231 when the business management application is started. (Authentication key) is collated, the hash values of the two match, and on the condition that the AP server 101 is authenticated as a regular terminal (regular AP server) The process is executed, the two hash values are inconsistent, and on the condition that the AP server 101 is authenticated as an irregular terminal (non-regular AP server), its own activation is stopped, and the process ends.

  That is, the server process 223 maintains its activation state only when it authenticates the AP server 101 as a regular terminal (regular AP server) when the business management application is activated. If the AP server 101 authenticates itself as an unauthorized terminal (unauthorized AP server), the business management application cannot be executed. For this reason, even if the AP server belonging to another business management system is connected to the network 104, the authentication key related to this AP server is not registered in the DB software 231 and is thus authenticated as an unauthorized AP server. As a result, AP servers belonging to other business management systems can be prevented from using the business management system shown in FIG.

  FIG. 4 is a flowchart for explaining the process of starting authentication of the client process. In FIG. 4, the CPU of the client 101 activates the client process 211 on the assumption that the server process 223 of the AP server 102 is activated (S400). The client process 211 acquires the unique information of the client 101 from the memory of the client 101, and generates a hash value based on the acquired unique information (S401). Next, the client process 211 transmits an authentication request to which the generated hash value is added to the AP server 102 via the network 104 (S402).

  Next, when an authentication request is stored in the message queue 222 via the WEB service 221 of the AP server 102, the server process 223 extracts the authentication request from the message queue 222, and the hash value read from the extracted authentication request Then, the hash value of the unique information of the client 101 registered in the DB software 231 is collated to determine whether or not the client 101 is a legitimate terminal (S403).

  When a positive determination result is obtained in step S403, that is, when the client 101 is authenticated as a regular terminal (regular client), the server process 223 displays information that the client 101 is a regular client. Send to client process 211. When the client process 211 receives information indicating that the client 101 is a legitimate client, the client process 211 holds the activation state, executes the activation process, and then completes the activation (S404). Then, the processing in this routine is terminated.

  On the other hand, if a negative determination result is obtained in step S403, that is, if the client 101 is authenticated as an unauthorized terminal (non-authorized client), the server process 223 determines that the client 101 is an unauthorized client. Information indicating that this is present is transmitted to the client process 211, and an error message is displayed on the client process 211 (S405). Thereafter, the client process 211 terminates the activation after stopping the activation (S406), and terminates the processing in this routine.

  As described above, the client process 211 transmits an authentication request including a hash value generated from the unique information of the client 101 to the AP server 102 at the time of starting, and the AP server 102 that has received the authentication request adds the authentication request to the authentication request. The hash value thus obtained is collated with the hash value of the unique information of the client 101 registered in the DB software 231 in advance, and by matching the hash values of the two, the client 101 is regarded as a regular terminal (regular client). On the condition that it has been authenticated, the startup state is maintained and the startup process is executed. On the other hand, when the client process 211 is started, the AP server 102 that has received the authentication request has authenticated the client 101 as an unauthorized terminal (an unauthorized client) due to a mismatch between the hash values of the two. Stop after starting itself, and then exit.

  That is, the client process 211 holds the activation state only when the AP server 102 that has received the authentication request at the time of activation authenticates the client 101 as a regular terminal (regular client). When the AP server 102 that can execute the process and has received the authentication request authenticates the client 101 as an unauthorized terminal (unauthorized client), the activation is stopped.

  For this reason, even if the client belonging to another business management system is connected to the network 104, the authentication key related to this client is not registered in the DB software 231 and is thus authenticated as an unauthorized client. As a result, it is possible to prevent clients belonging to other business management systems from using the business management system shown in FIG.

  FIG. 5 is a flowchart for explaining the processing accompanying the processing request of the client process. This process is started when the CPU of the client 101 that the AP server 102 authenticates as a legitimate terminal starts the client process 211. First, the client process 211 generates a processing request based on the operator's operation (S500), and transmits the generated processing request to the AP server 102 via the network 104 (S501).

  When the WEB server 221 of the AP server 102 receives a processing request from the client 101, the WEB server 221 stores the received processing request in the message queue 222. Thereafter, the server process 223 retrieves the processing request from the message queue 222, and acquires the specific information (hash value) of the AP server 102 from the memory of the AP server 102 before executing the processing of the retrieved processing request (S511). The acquired unique information (hash value) is compared with the hash value of the unique information of the AP server 102 registered in the DB software 231 (S512), and the AP server 102 is a legitimate terminal, that is, the AP server. It is determined whether 102 is a regular AP server (S513).

  If a positive determination result is obtained in step S513, that is, if the AP server 102 authenticates that it is a legitimate terminal (legal AP server), the server process 223 processes the processing request retrieved from the message queue 222. (Processing required for business management) is executed (S514), the processing result is transmitted to the client 101 via the message queue 222, the WEB service 221 and the network 104 (S515), and the processing in this routine is terminated.

  On the other hand, if a negative determination result is obtained in step S513, that is, if the AP server 102 authenticates that it is an unauthorized terminal (an unauthorized AP server), the server process 223 displays an error message in the message queue 222. Then, the data is transmitted to the client 101 via the WEB service 221 and the network 104 (S516). Receiving the error message, the client 101 displays an error message indicating that the destination terminal of the processing request is an unauthorized terminal (an unauthorized AP server) (S503), and ends the processing in this routine.

  As described above, the client process 211 generates a processing request as a startup process on condition that the client 101 is authenticated as a regular terminal (regular client), and the generated processing request is transmitted to the AP server 102. Send to. When the server process 223 is in the active state and receives a processing request from the client 101, the hash value generated from the unique information of the AP server 102 and the uniqueness of the AP server 102 registered in the DB software 231 in advance. A processing request from the client 101 is accepted on the condition that the hash value (authentication key) of the information is collated and the collation result is the same and the AP server 101 is authenticated as a regular terminal (regular AP server). , Execute processing according to the received processing request (processing necessary for business management), and transmit the processing result to the client 101. On the other hand, the collation result is inconsistent and the AP server 101 is set to an unauthorized terminal ( On the condition that authentication is performed as an unauthorized AP server), the processing request from the client 101 is rejected and an error message is received. To send over di to the client 101.

  As described above, when the server process 223 receives a processing request from the client 101, it accepts the processing request from the client 101 only when the AP server 102 authenticates that it is a legitimate AP server. Even when processing is executed according to the processing request and the processing request is received from the client 101, if the AP server 102 authenticates that it is an irregular AP server, the processing request from the client 101 is rejected. Therefore, unauthorized use of the AP server 102 due to temporary impersonation or the like can be prevented. Further, when the server process 223 is in the active state, only when a processing request is received from the client 101 without authenticating whether or not the AP server 102 is a regular AP server at regular intervals. Since it is possible to authenticate whether or not the AP server 102 is a regular AP server, the AP server 102 can be authenticated at an appropriate timing.

  FIG. 6 is a flowchart for explaining processing for registering unique information using the authentication management tool. This process is a process for the authentication management tools 212 and 224 to register the authentication key of the client 101 or AP server 102 to be managed, that is, the unique information in the DB software 231. Since the processes of the authentication management tools 212 and 224 are the same, the process of the authentication management tool 212 will be described below.

  First, the authentication management tool 212 functions as an authentication management tool that is activated on a terminal for registering the client 101 that is a management target terminal as a regular terminal, and is unique to each terminal in order to identify the client 101. The unique information, for example, the MAC address is acquired from the memory in the authentication management tool 212 (S601). When storing the acquired MAC address as an authentication key in the DB software 231, if all the authentication keys registered in the DB software 231 are always regular authentication keys of any managed terminal, the registered authentication key is Even if it is a legitimate authentication key, there is a high possibility that it will be analyzed by the encryption method. Therefore, the authentication management tool 212 executes processing for including dummy data in the authentication key to be stored in the DB software 231. .

  For example, the authentication management tool 212 is an integer n = 0 to N (N is an integer equal to or greater than 0, and is described in the setting file of the authentication management tool 212. When the authentication management tool 212 is activated, First, an integer n = 0 is set (S602), and then a hash value An is generated for a character string with n added to the head of the MAC address (S603). The hash value An is registered in the DB software 231 as an authentication key (S604).

  Next, the authentication management tool 212 sets n = n + 1 (S605), and then determines whether n is equal to N or smaller than N (S606). If the authentication management tool 212 obtains a positive determination result in step S606, the authentication management tool 212 returns to the process of step S603, repeats the processes of step S603 to step S606, and obtains a negative determination result in step S606. Then, the processing in this routine is terminated. With the above processing, N + 1 authentication keys are generated. Of the generated N + 1 authentication keys, N authentication keys are stored in the DB software 231 as dummy data (dummy data), and the remaining one is stored. One authentication key is stored in the DB software 231 as a normal authentication key.

  FIG. 7 is a flowchart for explaining processing for determining a regular authentication key. This process is a process for selecting one authentication key from the generated N + 1 authentication keys and determining the selected authentication key as a regular authentication key. In this process, among the numerical values added to the beginning of the MAC addresses of the generated N + 1 authentication keys, a method for improving security is adopted by uniquely determining the numerical value of the regular authentication key for each MAC address. Yes.

  First, the authentication management tool 212 acquires the MAC address of a terminal to be authenticated, for example, the client 101 from the memory of the authentication management tool 212 (S701), and generates the hash value A from the acquired MAC address. (S702).

  Next, the authentication management tool 212 generates a numeric character string B by extracting only numbers from the generated hash value A (S703). Thereafter, the authentication management tool 212 determines a numerical value m to be added to the head of the MAC address from the generated numerical character string B. There are various methods for determining the numerical value m. Here, the following processing is executed.

  First, the authentication management tool 212 extracts k digits from the beginning of the character string B for m having an initial value of 1 and m having an initial value of 0 (S704), and creates a numerical value Bk (S705). It is determined whether or not is smaller than N or equal to N (S706).

  When a positive determination result is obtained in step S706, that is, if Bk <= N with respect to N in S606 in FIG. 6, the authentication management tool 212 sets m = Bk and k = k + 1 (S707), Returning to the processing of S705, the processing of Step S705 to Step S706 is repeated.

  On the other hand, if a negative determination result is obtained in step S706, that is, if N <Bk with respect to N in S606 in FIG. 6, the authentication management tool 212 ends creation of the numerical value Bk at that time. Thus, m <= N is satisfied, and a unique numerical value m can be determined for each MAC address, that is, for each terminal. Thereafter, the authentication management tool 212 generates a hash value Am by adding a numerical value m unique to each terminal to the head of the MAC address (S708), and determines the generated hash value Am as a normal authentication key ( S709), the processing in this routine is terminated.

  As described above, when registering authentication keys related to the client 101 and the AP server 102 in the DB software 231, a plurality of authentication keys including a normal authentication key and two or more dummy data are generated, and the generated plurality of authentication keys Are registered in the DB software 231 and the server process 223 authenticates the client 101 and the AP server 102, the regular authentication key of the plurality of authentication keys registered in the DB software 231 is used for the client 101 and the AP server. 102 can be used for authentication. For this reason, even if the hash value indicating the unique information of the client 101 and the AP server 102 is acquired by an unauthorized terminal, it becomes more difficult for the unauthorized terminal to specify the authorized authentication key. High authentication key generation and authentication can be realized.

  According to the present embodiment, even when a plurality of business management systems coexist and each business management system is connected to the network 104, a terminal belonging to one business management system, and a regular authentication key is assigned to the DB server 103. Are registered with each terminal (regular client 101, legitimate AP server 102), a terminal belonging to another business management system or an unauthorized terminal (a regular authentication key is registered in the DB server 103) by software authentication. Non-terminal) can be prevented from being used illegally.

  In addition, this invention is not limited to an above-described Example, Various modifications are included. For example, the above-described embodiments have been described in detail for easy understanding of the present invention, and are not necessarily limited to those having all the configurations described. Further, a part of the configuration of one embodiment can be replaced with the configuration of another embodiment, and the configuration of another embodiment can be added to the configuration of one embodiment. Further, it is possible to add, delete, and replace other configurations for a part of the configuration of each embodiment.

  Each of the above-described configurations, functions, processing units, and the like may be realized by hardware, for example, by designing a part or all of them with an integrated circuit. Each of the above-described configurations, functions, and the like may be realized by software by interpreting and executing a program that realizes each function by the processor. Information such as programs, tables, and files for realizing each function is stored in a memory, a hard disk, a recording device such as an SSD (Solid State Drive), an IC (Integrated Circuit) card, an SD (Secure Digital) memory card, a DVD ( It can be recorded on a recording medium such as a Digital Versatile Disc).

  101, 101a, 101b, 101c client, 102, 102a, 102b AP server, 103 DB server, 104 network, 211 client process, 212 authentication management tool, 221 WEB service, 222 message queue, 223 server process, 224 authentication management tool, 231 DB software.

Claims (5)

A client terminal connected to a network and having a client process for generating a processing request, an application server that exchanges information with the client terminal via the network, and unique information of the client terminal connected to the network And a database server having a database that stores the unique information of the application server as an authentication key, respectively,
The application server is
Has a server process to manage business management applications,
The server process is
When starting up the business management application, the database server is accessed, and the unique information of the application server managed by the application server is compared with the authentication key of the application server among the authentication keys registered in the database. The business management system is characterized in that, when the collation result is inconsistent and the application server determines that the application server is an unauthorized application server, the business management application is stopped. The server process is
When the business management application is started, if the collation result is the same and the application server is determined to be a legitimate application server, the startup state of the business management application is retained,
The client process is
The application server is started on the condition that the application for business management is in an activated state, and an authentication request including unique information of the client terminal managed by the client terminal is transmitted to the application server via the network, and the application server When the authentication result indicating that the client terminal is a legitimate client terminal is received via the network, a startup process is executed, and the client terminal is authenticated as an unauthorized client terminal. The business management system according to claim 1, wherein when the result is received from the application server via the network, the activation is stopped. The server process is
When the application server receives the authentication request from the client process, the application server accesses the database server, and the client terminal among the unique information of the client terminal included in the authentication request and the authentication key registered in the database If the client terminal authenticates that the client terminal is a legitimate client terminal, the authentication result that the client terminal is a legitimate client terminal is When the client terminal is transmitted to the client terminal via a network and the verification result is inconsistent and the client terminal is authenticated as an unauthorized client terminal, the client terminal is an unauthorized client terminal. Authentication result via the network Business management system according to claim 2, characterized by transmitting to the serial client terminal. The client process is
A processing request is generated from the application server on the condition that the authentication result indicating that the client terminal is a legitimate client terminal is received via the network, and the generated processing request is transmitted via the network. Send to the application server,
The server process is
When the application server receives the processing request, the application server accesses the database server, and the application server specific information managed by the application server and the authentication key of the application server among the authentication keys registered in the database And when the application server determines that the application server is a legitimate application server, it accepts the processing request and executes processing according to the accepted processing request. 3. The business management system according to claim 2, wherein when it is determined that the application server is a non-regular application server because of a mismatch, acceptance of the processing request is rejected. In the database server, a client terminal authentication management tool for registering the unique information of the client terminal as an authentication key in the database of the database server, or registering the unique information of the application server as an authentication key in the database of the database server Application server authentication management tool is connected,
The authentication key registered by each authentication management tool is:
The business management system according to claim 1, comprising a plurality of authentication keys including two or more dummy data in addition to a regular authentication key.

Images