JP2021064869A - Thin-client system - Google Patents

Abstract

To connect collected information data to a data center by using a general purpose PC, while maintaining the security of the data.SOLUTION: A thin-client system includes a general purpose PC that is available in a thin-client environment, an exclusive information terminal that is connected to the general purpose PC, and a data center that is connected to the exclusive information terminal via an exclusive security network. The data center has authentication means that, in response to an access request from the general purpose PC via the exclusive information terminal, transmits a server-side public key used for encryption via the exclusive information terminal, and performs authentication of the general purpose PC based on an authentication message generated in the general purpose PC based on the server-side public key.SELECTED DRAWING: Figure 1

Description

The present invention relates to a system and a method for verifying the integrity of a client platform composed of a dedicated information terminal and a general-purpose PC in a thin client system.

In recent years, companies have introduced a thin client system (Thin Client System) that allows clients to have only the minimum necessary functions, manages information resources such as confidential information, and integrates functions such as application processing on a server. Is increasing.

Behind the introduction of the thin client system are (1) realization of a high-speed communication network, (2) strengthening of security for the purpose of preventing leakage of personal information from clients, and (3) client operation management costs (patch information, There are reductions in license management, etc.).

In particular, in order to realize a dedicated network that allows employees to work anywhere, it is necessary to be able to remotely access computers and servers installed in the company in the same secure environment as in the company.

In order to realize a thin client system, a computer dedicated to the thin client system may be introduced, but the introduction of a computer dedicated to the thin client system is not desirable from the viewpoint of both cost and convenience.

Therefore, as described in Patent Document 1, a dedicated USB device or an OS operating system (OS: Operating System) dedicated to the thin client system is stored in the network storage, and a general-purpose computer is used as a client of the thin client system. A method of booting an OS dedicated to a thin client system on a general-purpose computer is used. However, it is difficult to collect information data only with a USB device, and it is also difficult to protect the security of access to the data center. Therefore, configuration and verification of a platform that has a data collection function and can guarantee access to the data center. Is required.

JP-A-2009-175923

It is preferable to install a dedicated PC to configure a thin client system, but as mentioned above, it costs money, so if it is a thin client system in which a dedicated portable information terminal is configured with a general-purpose client PC or tablet PC, etc. Both cost and functionality can be achieved.

However, general-purpose client PCs and tablet PCs are products for general users and are vulnerable in terms of security. Therefore, in a thin client system in which a general-purpose client PC or tablet PC is used to configure a dedicated portable information terminal, the PC side Data may be leaked when editing / sending / receiving data with.

In view of the above, the thin client system according to the present invention is
A thin client system including a general-purpose PC that can be used in a thin client environment, a dedicated information terminal connected to the general-purpose PC, and a data center connected to the dedicated information terminal via a dedicated security network.
The data center transmits a server-side public key used for encryption via the dedicated information terminal in response to an access request from the general-purpose PC via the dedicated information terminal, and is based on the server-side public key. It is characterized by having an authentication means for authenticating the general-purpose PC based on an authentication message generated by the general-purpose PC.

As described above, according to the present invention, by constructing a thin client system using a general-purpose PC and an information terminal, the collected information data is connected to a data center using a general-purpose PC while maintaining data security. Can be done.

The figure explaining the thin client system which concerns on one Embodiment of this invention. The block diagram of the dedicated information terminal which concerns on one Embodiment of this invention. The block diagram of the general-purpose PC which concerns on one Embodiment of this invention. The flow chart which showed the authentication procedure of the thin client system which concerns on one Embodiment of this invention. The figure explaining the content of the authentication message which concerns on one Embodiment of this invention. The detailed flow diagram of the authentication in the authentication control server which concerns on one Embodiment of this invention. The flow chart of transmission / reception between a client and a data center which concerns on one Embodiment of this invention. The figure explaining the thin client system which concerns on other embodiment of this invention. The block diagram of the information terminal which concerns on other embodiment of this invention. The figure explaining the security level control module which concerns on other embodiment of this invention. FIG. 5 is a flow chart of authentication in a thin client system according to another embodiment of the present invention. FIG. 5 is a detailed flow chart of a change in an authentication method according to another embodiment of the present invention. FIG. 3 is a processing flow diagram when a security level setting fails according to another embodiment of the present invention.

(First Embodiment)
From here, the configuration and embodiment of the thin client system proposed in the present invention will be described in detail with reference to the drawings.

FIG. 1 is a diagram illustrating a thin client system configured to include a dedicated information terminal and a general-purpose PC. Specifically, the dedicated information terminal 101 and the general-purpose PC 102 are combined to form the client 10 of the thin client system according to the present embodiment. In the thin client system according to the present embodiment, a terminal such as a portable payment terminal used for other purposes can be used as the dedicated information terminal 101.

The general-purpose PC 102 is connected to the Internet 11, and the dedicated information terminal 101 can be used in a thin client environment by connecting to the data center 13 via the dedicated VPN network 12 as an example of the dedicated security network. .. The data center 13 is composed of an authentication control server 131 and a data server 132. The authentication control server 131 blocks requests via the general Internet 11 and performs an approval process that approves only requests via the dedicated VPN network 12. A user who has obtained the access permission of the authentication control server 131 can access the data server 132.

As shown in FIG. 2, the dedicated information terminal 101 collects data as hardware resources such as a central arithmetic unit (CPU) 21, a RAM 221 which is a main memory 22, a ROM 222 on which a BIOS is mounted, and data. It is composed of a data input device 23, a short-range communication device 24 for connecting to a general-purpose PC 102, and a network device 25 for connecting to a data center 13.

As shown in FIG. 3, the general-purpose PC 102 includes a central processing unit (CPU) 31, a memory 32, a hard disk 33, a short-range communication device 34 for connecting to a dedicated information terminal 101, and a network device 35. Has been done. When the client of the thin client system is configured in combination with the dedicated information terminal 101, the memory of the general-purpose PC 102 is used as a work area for executing the authentication program and the business application. Further, in order to prevent leakage of data contents, access to the hard disk 33 of the general-purpose PC 102 and access to the network device 35 are controlled to be blocked. Further, although not shown, the general-purpose PC is provided with an operation unit.

<Configuration processing>
Since the general-purpose PC 102 and the dedicated information terminal 101 are paired one-to-one to form the client 10, when the general-purpose PC 102 and the dedicated information terminal 101 are connected, the dedicated information terminal 101 registers the MAC address of the PC. On the other hand, when disconnecting from the general-purpose PC 102, the dedicated information terminal 101 sends a notification to the authentication control server 131 that the connection with the general-purpose PC 102 is disconnected, deletes the registered pairing information, and the data remaining in the general-purpose PC 102. Also clear all.

The MAC address of the dedicated information terminal 101 and the information (ID, password, etc.) of the user who operates the dedicated information terminal are registered in the authentication control server 131 in advance. Guarantee that only registered users and dedicated information terminals are allowed access to the authentication control server.

<Authentication processing>
FIG. 4 is a flow chart showing the authentication procedure of the thin client system. To start the authentication, a request is sent from the general-purpose PC 102 to the authentication control server 131 via the dedicated VPN network 12 to which the dedicated information terminal 101 is connected (step S1). _{The authentication control server 131 returns} ^{the public key K S} pub (server-side public key) of the authentication control server 131 in response to the request (access request) (step S2). The dedicated information terminal 101 receives the reply message of the authentication control server 131 ^{, saves the public key K S} _pub of the authentication control server 131 in the dedicated information terminal 101 (step S3), and notifies the general-purpose PC 102.

The dedicated information terminal 101 uses the MAC address of the general-purpose PC 102 and the MAC address of the dedicated information terminal 101 collected at the time of the first connection ^{to generate the public key K C} _pub (client-side public key 501) of the dedicated information terminal 101 (client-side public key 501). Step S4). After that, the dedicated information terminal 101 sends the authentication message (including the user ID and password 502) (step S5) generated by the general-purpose PC 102 to the public key K ^C _pub of the dedicated information terminal 101 and the MAC address 503 of the dedicated information terminal 101. And the MAC address 504 of the general-purpose PC 102 are added, ^{and the encrypted message 505 is created by using the public key K S} _pub of the authentication control server 131 and transmitted to the authentication control server 131 (step S6). In the present embodiment, the user ID and password 502 as the user information included in the authentication message are those input by the operation unit of the general-purpose PC 102, but the present invention is not limited to this, and other methods may be used in advance. The acquired one may be used.

The authentication control server 131 performs an authentication process based on the content of the authentication message 50 (step S7). When the authentication message is successfully verified using the private key, the authentication control server 131 sends a message permitting access to the data server 132 to the client 10 and ends this procedure (step S8).

As shown in FIG. 5, the authentication message 50 includes the public key K ^C _pub of the dedicated information terminal 101, the user ID and password 502 that use the dedicated information terminal 101, and the MAC address 503 of the dedicated information terminal 101. , MAC address 504 of a general-purpose PC.

As shown in FIG. 6, the authentication control server 131 uses the private key K ^S _pri of the authentication control server to decrypt the authentication message 50 (step S11). After that, the authentication control server 131 acquires each item from the decrypted authentication message 50 (step S12).

If the MAC address of the dedicated information terminal 101 acquired from the authentication message 50 is already registered in the authentication control server 131 (step S13), and if the user ID and password 502 are also OK (step S14), the authentication is OK. After registering the public key K ^C _pub of the dedicated information terminal 101, the MAC address 503 of the dedicated information terminal 101, and the MAC address 504 of the general-purpose PC 102 as a set (step S15), access to the data server 132 is permitted. Finish this procedure.

<Data transmission processing>
FIG. 7 is a flow chart of a transmission / reception procedure between the client 10 and the data center 13. ^{The client 10 uses the public key K S} _pub of the authentication control server 131 to encrypt the transmitted message and then transmits it to the data center 13 (step S21). The authentication control server 131 of the data center 13 ^{uses the private key K S} _pri of the authentication control server 131 to decrypt the message (step S22). It is checked whether the MAC address 503 of the dedicated information terminal 101 and the MAC address 504 of the general-purpose PC 102 in the message match the contents registered in the authentication control server 131 (step S23). If all match, the message content is transmitted to the data server 132 (step S24). The reply message created by the data server 132 is ^{encrypted using the public key K C} _pub of the dedicated information terminal 101, and then transmitted to the client 10 (step S26). ^{The client 10 decrypts the reply message using the private key K C} _pri of the dedicated information terminal 101, and ends this procedure (step S27).

(Second Embodiment)
Hereinafter, the thin client system according to the second embodiment of the present invention will be described. In a thin client system, since the information terminal on the client side always accesses the server side, measures may be taken to prevent information leakage by managing the security level.

Here, the required security level of the security function differs depending on the place where the information terminal is used. In addition, the required security level may differ depending on the usage time even if the usage location is the same.

In consideration of the above, Japanese Patent Application Laid-Open No. 2006-127293 has been published as a technique for restricting the use of an information terminal by changing the security level according to the place and time of use of the information terminal.

Guaranteeing communication security is very important in thin client systems, but if all transmitted / received data between the client and server is set at the highest security level, it will put a wasteful burden on the communication network and reduce communication efficiency. Sometimes.

Also, after setting the security level of the thin client system automatically or manually, if the setting fails for some reason, the security of the system cannot be guaranteed.

Therefore, conventionally, if the authentication method set in the information terminal cannot be reflected for some reason, it may be regarded as an authentication failure and the use of the information terminal may be prohibited.

The thin client system according to the present embodiment is made in consideration of the above circumstances, and is authenticated by a thin client system capable of dynamically changing the security level of the thin client system and a change in the security level. The purpose is to provide a thin client system that continuously enables and a method of dynamically controlling the security level.

In order to solve the above-mentioned problems, the thin client system according to the present embodiment uses means for dynamically changing the security level based on the usage status of the client terminal, the usage environment, and the communication content, and the security level. It is characterized by including means for using various authentication methods in combination, means for ensuring that the security level is set correctly, and means for changing the authentication method.

According to this configuration, it is possible to dynamically change the security level based on the usage status of the client, the usage environment, and the communication content, so that the security of the thin client system can be maintained and the system can be changed. The communication load can be reduced.

In the following description, the same configuration as that of the first embodiment will be described using the same reference numerals, and only the differences will be described. FIG. 8 is a diagram illustrating a thin client system configured to include an information terminal and a server. Specifically, the system is configured by combining the information terminal (client) 101, the authentication server 302, the security level control module 303, and the database 304.

When accessing the database 304 from the dedicated information terminal 101, the authentication of the authentication server 302 is required. The security level control module 303 collects the information of the dedicated information terminal 101, sets the optimum security level based on the usage status, the usage environment, the communication content, and the like, and notifies the authentication server 302 of the set security level. The authentication server 302 authenticates the dedicated information terminal 101 by using a predefined authentication method based on the security level. At this time, the authentication server 302 may change the display screen itself for displaying on the dedicated information terminal 101 at the time of authentication of the dedicated information terminal 101 according to the set security level. Further, even if the set security level is different, the display screen itself is the same, and the display mode of the display screen may be partially changed so that it can be recognized that some input items do not need to be input. ..

As shown in FIG. 9, the dedicated information terminal 101 is connected to the central processing unit (CPU) 21, the RAM 221 which is the main memory 22, the ROM 222 on which the BIOS is mounted, and the database 304 as hardware resources. It is composed of a network device 25 for collecting data, a position information sensor 206 for acquiring position information, and an environment sensor 207 for acquiring environment information.

As shown in FIG. 10, the security level control module 303 collects information on usage status, usage environment, and communication content from each client terminal 101, and uses an algorithm such as machine learning to optimize the security level 401. ~ 403 is selected. In addition, the algorithm has a feedback control function, and the estimation accuracy of the algorithm is excellent.

The authentication process of this system will be described with reference to the flowchart of FIG. When the client terminal 101 refers to the information in the database, it first requests access to the authentication server 302 (S401). After receiving the authentication request of the client terminal 101, the authentication server 302 notifies the security level control module 303 (S402) in order to select the authentication method, and also returns a response to the client terminal 101 (S403).

After receiving the authentication notification from the authentication server 302, the security level control module 303 issues a request for collecting authentication information according to the security level to the client terminal 101 (S404).

When setting to a low security level, identification information authentication (user ID, password, Pin, etc.) is required as authentication information. When setting to a medium security level, identification information authentication and environmental information authentication (location information, communication content, etc.) are required as authentication information. When setting to a high security level, identification information authentication, environmental information authentication, and biometric information authentication (fingerprint, face, iris, etc.) are required as authentication information.

After receiving both the response from the authentication server 302 and the request for collecting the authentication information from the security level control module 303, the client terminal 101 transmits the authentication information to the security level control module 303 (S405).

The security level control module 303 determines the security level based on the authentication information received from the client terminal 101 (S406). At that time, the authentication method is also selected (S407).

After that, the security level control module 303 notifies both the client terminal 101 and the authentication server 302 of the authentication method (S407).

The client terminal 101 transmits the content of authentication (authentication message) to the authentication server 302 based on the selected authentication method (S408).

After receiving the authentication method notified from the security level control module 303 and the authentication content from the client terminal 101, the authentication server 302 verifies the authentication message (S409). When the verification of the authentication message is successful, the authentication server 302 sends a message permitting access to the database to the client terminal 101, and ends this procedure (S410).

FIG. 12 is a flow chart of changing the authentication method. If the authentication method selected from the security level control module 303 cannot be executed on the client terminal 101 due to the influence of a temporary wireless failure or the like, the authentication method can be changed. When the authentication is started, the authentication method is first selected (S502). Based on the selected authentication method, the authentication server 302 verifies the authentication message (S505). When the verification of the authentication message is successful, the authentication server sends a message permitting access to the database to the client terminal 101 (S506).

When the verification of the authentication message fails in S505, the authentication server 302 sends a notification message to the security level control module 303. After receiving the authentication failure notification message, the security level control module 303 compares the number of times of re-authentication in S504, and if the number of times does not exceed the specified number of times (three times in this embodiment), changes the authentication method. The changed authentication method is transmitted to both the client terminal 101 and the authentication server 302 (S503).

If the number of re-authentications exceeds the specified number (S504), the authentication method is not transmitted (S503), and the process ends with an authentication error (S507).

FIG. 13 is a diagram for explaining the automatic setting of the security level and the manual setting function. The security level control module 303 compares the level value manually set by the user with the usage status of the client terminal 101 and the level value automatically set in consideration of the usage environment and communication contents, and compares the level value automatically set by the user with the manually set security level. If the value is high, select manual setting (S601) and set it as the security level of the system (S602).

When the manual setting of the security level is successful, the authentication server 302 sends a message permitting access to the database to the client terminal 101, and ends this procedure (S603). When the manual setting of the security level fails, the automatic setting value of the security level is used and the setting is performed again (S604).

When the security level reset is successful, a message permitting access to the database from the authentication server 302 is sent to the client terminal 101 as in the case of the manual security level setting, and the automatic setting procedure ends (S604). If the automatic setting of the security level fails, the security level is repeatedly set until the number of times the automatic setting of the security level exceeds the specified number or the setting is successful (S605). If the specified number of times is exceeded, the process is terminated on the assumption that the security level setting has failed (S606). In addition, as an example of the case where the automatic setting of the security level fails, the case where the communication is cut off in the middle or the case where an error is returned due to the system convenience is included.

10 Client 101 Dedicated information terminal 102 General-purpose PC
11 Internet 12 Dedicated VPN network 13 Data center 131 Authentication control server 132 Data server 50 Authentication message 501 Client-side public key 505 Encrypted message

Claims (3)

A thin client system including a general-purpose PC that can be used in a thin client environment, a dedicated information terminal connected to the general-purpose PC, and a data center connected to the dedicated information terminal via a dedicated security network.
The data center transmits a server-side public key used for encryption via the dedicated information terminal in response to an access request from the general-purpose PC via the dedicated information terminal, and is based on the server-side public key. A thin client system comprising an authentication means for authenticating the general-purpose PC based on an authentication message generated by the general-purpose PC. The thin client system according to claim 1, wherein the authentication means authenticates based on user information input by a user in an operation unit of the general-purpose PC. The dedicated information terminal uses the user information included in the authentication message, the identification information of the general-purpose PC, the identification information of the dedicated information terminal, and the information of the client-side public key generated by the dedicated information terminal as the server-side public key. The thin client system according to claim 2, wherein the thin client system is encrypted based on the information of the above and transmitted to the data center.

Images