JP7517493B2 - Management system, control device, management method and program - Google Patents

Description

The present invention relates to a management system, a control device, a management method, and a program.

Information processing devices (computers) generally have a function for setting access authority (hereinafter simply referred to as authority) for data, etc. stored in the information processing device according to a user ID (identifier). Furthermore, generally, in order to protect important functions or data, etc., access authority for important functions or data, etc. is restricted to an administrator of the information processing device, etc. In other words, in order to protect important functions or data, etc., a specific user (an administrator of the information processing device, etc.) is granted stronger authority than users other than the specific user (hereinafter referred to as general users).

Patent document 1 describes a technology for restricting access to controlled data stored internally in a device to users with special authority, based on the life cycle state of the device and the location and/or time of the device.

JP 2016-058035 A

The disclosures of the above prior art documents are incorporated herein by reference. The following analysis has been made from the perspective of the present invention.

As described above, important functions, data, etc. can be protected by restricting access rights to the important functions, data, etc. to the administrator of the information processing device. However, there are cases where general users need to temporarily access important functions, data, etc.

Here, in the technology described in Patent Document 1, if access to the controlled data is restricted to users with special authority (such as an administrator), users other than the administrator are not permitted to access the controlled data. Therefore, in the technology described in Patent Document 1, if access to the controlled data is restricted to users with special authority, convenience for users other than the administrator may decrease.

Furthermore, with the technology described in Patent Document 1, if the state (life cycle state) of a device that stores controlled data internally, the device's location, and/or the time satisfy certain conditions, a user with access rights can access the controlled data. Therefore, the technology described in Patent Document 1 cannot prevent a user with access rights from unnecessarily accessing the controlled data.

The present invention aims to provide a management system, control device, management method, and program that contribute to reducing the security risks of managed devices while improving user convenience.

According to a first aspect of the present invention, a management system is provided. The management system includes a managed device that can be operated using a first ID having a predetermined authority, a control device that controls the managed device, and a terminal that acquires terminal location information indicating the location of the terminal and transmits the terminal location information to the control device. The control device includes an ID usage management unit that requests the managed device to authenticate the terminal, and when the managed device authenticates the terminal, determines whether or not to permit the terminal to use the first ID based on the terminal location information and a usage determination time.

According to a second aspect of the present invention, a control device is provided. The control device controls a managed device that can be operated using a first ID having a predetermined authority. The control device further includes an ID usage management unit that requests the managed device to authenticate the terminal, and when the managed device authenticates the terminal, determines whether or not to permit the terminal to use the first ID based on terminal location information indicating the location of the terminal and a usage determination time.

According to a third aspect of the present invention, there is provided a management method. The management method includes a step of acquiring terminal location information indicating a location of a terminal. The management method further includes a step of requesting authentication of the terminal from a managed device that can be operated using a first ID having a predetermined authority. The management method further includes a step of determining, when the terminal is authenticated, whether or not to permit the terminal to use the first ID based on the terminal location information and a usage determination time.
It should be noted that this method is tied to a specific machine, called a control device, which controls the managed device.

According to a fourth aspect of the present invention, there is provided a program. The program causes a computer that controls a control device to execute a process of receiving, from a terminal, terminal location information indicating the location of the terminal. The program further causes the computer to execute a process of requesting authentication of the terminal from a managed device that is operable using a first ID having a predetermined authority. The program further causes the computer to execute a process of determining, when the terminal is authenticated, whether or not to permit the terminal to use the first ID based on the terminal location information and a usage determination time.
These programs can be recorded on a computer-readable storage medium. The storage medium can be a non-transient medium such as a semiconductor memory, a hard disk, a magnetic recording medium, an optical recording medium, etc. The present invention can also be embodied as a computer program product.

According to each aspect of the present invention, a management system, a control device, a management method, and a program are provided that contribute to reducing the security risk of the managed devices while improving user convenience.

FIG. 1 is a diagram for explaining an overview of an embodiment. 1 is a block diagram showing an example of an overall configuration of a management system 1. FIG. FIG. 11 is a diagram showing an example of a usage application information table 105. FIG. 2 is a diagram showing an example of a managed server table 106. FIG. 2 is a diagram illustrating an example of a work user table 107. 13 is a flowchart showing an example of an operation of the management server 100. 13 is a flowchart showing an example of an operation of the management server 100. 13 is a flowchart showing an example of an operation of the management server 100. 4 is a flowchart showing an example of an operation of the management system 1. 4 is a flowchart showing an example of an operation of the management system 1. 4 is a flowchart showing an example of the operation of the control device 300. 4 is a flowchart showing an example of the operation of the control device 300.

First, an overview of one embodiment will be described with reference to FIG. 1. Note that the reference numerals in this overview are added to each element for convenience as an example to aid in understanding, and the description of this overview is not intended to be limiting in any way. Furthermore, the connection lines between the blocks in each block diagram include both bidirectional and unidirectional lines. Unidirectional arrows are used to indicate the main signal (data) flow diagrammatically, and do not exclude bidirectionality. Furthermore, although not explicitly shown, input ports and output ports exist at the input and output ends of each connection line in the circuit diagrams, block diagrams, internal configuration diagrams, connection diagrams, etc. disclosed in this application. The same applies to input/output interfaces.

As mentioned above, there is a need for a management system that contributes to reducing the security risks of managed devices while improving user convenience.

As an example, the management system 1000 shown in FIG. 1 is provided. The management system 1000 includes a managed device 1010, a control device 1020, and a terminal 1030.

The managed device 1010 can be operated using a first ID that has a specific authority. The terminal 1030 acquires terminal location information indicating the location of the terminal 1030, and transmits the terminal location information to the control device 1020.

The control device 1020 controls the managed device 1010. Furthermore, the control device 1020 includes an ID usage management unit 1021. The ID usage management unit 1021 requests the managed device 1010 to authenticate the terminal 1030. When the managed device 1010 authenticates the terminal 1030, the ID usage management unit 1021 judges whether or not to permit the terminal 1030 to use the first ID in the managed device 1010 based on the terminal location information received from the terminal 1030 and the time to be judged. In the following description, the time to be judged is referred to as the usage judgment time.

Here, it is assumed that the first ID is a user ID (hereinafter referred to as a privileged ID) that has stronger authority than the user ID of a general user. Also, it is assumed that the time to be judged is the time of judgment. In this case, for the terminal 1030 authenticated by the managed device 1010, the control device 1020 judges whether or not to permit the terminal 1030 to use the privileged ID in the managed device 1010 based on the location of the terminal 1030 and the time of judgment. Therefore, the control device 1020 permits the terminal 1030 authenticated by the managed device 1010, which is present in a location that satisfies a specified condition at a time that satisfies a specified condition, to use the privileged ID in the managed device 1010.

In other words, in the management system 1000, the control device 1020 allows an external device (i.e., the terminal 1030) different from the managed device 1010 to use the privileged ID of the managed device 1010. Furthermore, in the management system 1000, even a general user can use the privileged ID of the managed device 1010 if certain conditions are met. Therefore, the management system 1000 contributes to improving the convenience of users who use the managed device 1010.

Meanwhile, the control device 1020 has the managed device 1010 authenticate the terminal 1030. Furthermore, the control device 1020 determines whether or not to permit the terminal 1030 to use the privileged ID of the managed device 1010 based on the location and time of the terminal 1030. In other words, the control device 1020 restricts the terminals 1030 that can use the privileged ID of the managed device 1010, and the locations and times at which it can be used. Therefore, the management system 1000 contributes to reducing the security risk of the managed device 1010.

Therefore, the management system 1000 contributes to reducing security risks of the managed device 1010 while improving user convenience.

[First embodiment]
The first embodiment will be described in detail with reference to the drawings. In the following description, the managed device will be called a managed server. However, this does not mean that the managed device is limited to a server.

Figure 2 is a block diagram showing an example of the overall configuration of the management system 1 according to this embodiment. The management system 1 includes a management server 100, a terminal 200, and a control device 300. Note that while Figure 2 shows one terminal 200, this is not intended to limit the management system 1 to being configured to include one terminal 200. Of course, the management system 1 may include two or more terminals 200.

The control device 300 is connected to managed servers (managed devices) (301a, 301b). In the following description, the managed servers (310a, 310b) will be referred to as managed servers 310 when there is no need to distinguish between them. Also, while FIG. 2 shows two managed servers (301a, 301b), this is not intended to limit the number of managed servers 310 to two. It goes without saying that the management system 1 may be configured to include one or three or more managed servers 310.

The control device 300 and the managed server 310 are arranged in a managed server network (first network) 400. In the management system 1 according to this embodiment, the managed server network 400 is a LAN (Local Area Network). In other words, in the management system 1 according to this embodiment, the control device 300 and the managed server 310 are arranged in a LAN. When the terminal 200 is present in the managed server network 400, it is possible to connect to the control device 300 and the managed server 310 via the managed server network 400.

The terminal 200 can also be connected to the management server 100 via a second network different from the managed server network 400. For example, the second network may be the Internet. Or, the second network may be a LAN different from the managed server network 400.

The management server 100 includes a usage application management unit 103, a management server control unit 104, and a management server storage unit 101. Furthermore, the management server 100 includes a communication means (not shown). Of course, the management server 100 may also include hardware and/or software (not shown).

The terminal 200 is an information processing device (computer) used by a working user. For example, the terminal 200 may be a smartphone, a tablet terminal, or the like. The terminal 200 includes an ID management relay unit 201 and a location information acquisition unit 202. Furthermore, the terminal 200 includes a communication means (not shown). It goes without saying that the terminal 200 may also include hardware and/or software not shown.

The control device 300 is an information processing device (computer) that controls the managed server 310. The control device 300 includes an ID usage management unit 301. Furthermore, the control device 300 includes a communication means (not shown). Of course, the control device 300 may also be configured to include hardware and/or software not shown.

The managed server 310 is an information processing device (computer). Specifically, the managed server 310 is an information processing device (computer) that can be connected using at least one of a first ID having a predetermined authority and a second ID different from the first ID. In the following description, the first ID is assumed to be a privileged ID.

The management server 100 is described in detail below.

The management server storage unit 101 stores information necessary to operate the management server 100. The management server storage unit 101 stores the ID management database 102. The management server storage unit 101 is realized by a magnetic disk device, an optical disk device, or a semiconductor memory.

The ID management database 102 is described in more detail below.

The ID management database 102 stores information that associates information for identifying the managed server 310 with usage application information. In the following description, the table that associates information for identifying the managed server 310 with usage application information is referred to as the usage application information table 105.

The information for identifying the managed server 310 may be a number assigned to each managed server 310, and the details are not important as long as the information can identify the managed server 310. In the following description, the information for identifying the managed server 310 is referred to as the managed server ID.

The usage application information includes a privilege ID (first ID), information indicating the authority corresponding to the privilege ID, the start time of usage, and the end time of usage.

The information indicating the authority corresponding to the privileged ID is information indicating the authority that can be used using the privileged ID on the managed server 310. In the following explanation, the information indicating the authority corresponding to the privileged ID that is included in the usage application information is referred to as the authority to be applied for.

The usage start time is the time when the user plans to start using the managed server 310. On the other hand, the usage end time is the time when the user plans to end using the managed server 310. In other words, the user applies to use the managed server 310 from the usage start time to the usage end time.

Figure 3 is a diagram showing an example of the usage application information table 105. Specifically, Figure 3 shows a table that associates a managed server ID, a work user ID, a privilege ID, the authority to be applied for, a usage start time, and a usage end time.

Furthermore, the ID management database 102 stores the managed server ID, server connection information, authentication information corresponding to the second ID, registered location information, and distance threshold in association with each other. In the following description, the second ID is referred to as the connected user ID. The connected user ID is a user ID linked to a privileged ID and is a user ID for connecting to the managed server 310. In the following description, a table that associates the managed server ID, server connection information, connected user authentication information corresponding to the connected user ID (second ID), registered location information, and distance threshold is referred to as the managed server table 106. In the following description, the authentication information corresponding to the connected user ID is referred to as connected user authentication information. The connected user authentication information is information that includes the connected user ID and a password corresponding to the connected user ID.

The server connection information is information required to connect to the managed server 310. For example, the server connection information may include a host name and a port number corresponding to the managed server 310. Also, for example, the server connection information may include an IP address and a port number corresponding to the managed server 310.

Registered location information is information indicating a location that has been applied for use by a user and registered. For example, registered location information may be information indicating the location where the user of terminal 200 plans to perform work using a privileged ID.

The distance threshold is a distance used as a threshold to determine whether the difference between the location of the terminal 200 and the location previously applied for use is within a specified range.

Figure 4 is a diagram showing an example of the managed server table 106. Specifically, Figure 4 shows a table that associates a managed server ID, a host name, a port number, a connected user ID, a password corresponding to the connected user ID (connected user password), registered location information, and a distance threshold.

Furthermore, the ID management database 102 stores authentication information corresponding to a third ID. In the following description, the table that stores the third ID and the password corresponding to the third ID is referred to as the work user table 107. In the following description, the third ID is referred to as the work user. In the following description, the authentication information corresponding to the work user ID (third ID) is referred to as work user authentication information.

The work user ID is a user ID corresponding to a user who uses the terminal 200. The work user authentication information is information that includes the work user ID and a password corresponding to the work user ID.

Figure 5 shows an example of the work user table 107. Specifically, Figure 5 shows an example of a table that associates work user IDs with passwords. For example, referring to Figure 5, the password corresponding to the work user ID "suzuki" is "B7343a7cbdd302".

In the following explanation, for the sake of convenience, it is assumed that the ID management database 102 stores a user table, a usage application information table 105, and a managed server table 106. However, this is not intended to limit the ID management database 102 to storing (holding) data in table format.

The usage application management unit 103 authenticates the working user. Furthermore, the usage application management unit 103 accepts usage application information and registers the accepted usage application information in the ID management database 102. Specifically, the usage application management unit 103 accepts usage application information including the managed server ID, the privilege ID, the authority for which the usage application is applied, the start time of use, and the end time of use, which are the subject of the usage application. Then, the usage application management unit 103 registers the usage application information including the managed server ID, the privilege ID, the authority for which the usage application is applied, the start time of use, and the end time of use in the ID management database 102.

The management server control unit 104 receives a login request from the working user from the ID management relay unit 201. When the management server control unit 104 receives a login request from the ID management relay unit 201, it responds to the ID management relay unit 201 with a list of managed servers 310 corresponding to the working user from among the managed servers 310 registered in advance. Then, when the management server control unit 104 receives a managed server ID from the ID management relay unit 201, it refers to the usage application information table 105 and responds to the ID management relay unit 201 with usage application information corresponding to the received managed server ID.

The terminal 200 is described in detail below.

The location information acquisition unit 202 acquires terminal location information indicating the location of the terminal 200. The location information acquisition unit 202 is realized, for example, using a GPS (Global Positioning System) function.

The ID management relay unit 201 transmits the connected user authentication information corresponding to the connected user ID and the terminal location information to the control device 300. Furthermore, the ID management relay unit 201 transmits the registration location information and the distance threshold to the control device 300. Specifically, when making a usage application, the ID management relay unit 201 transmits the registration location information and the distance threshold to the control device 300. More specifically, the ID management relay unit 201 receives the connected user authentication information and the usage application information corresponding to the managed server 310 to be connected from the management server 100. Then, the ID management relay unit 201 transmits the connected user authentication information, the usage application information, and the terminal location information to the control device 300.

Furthermore, the terminal 200 acquires terminal location information at a predetermined time interval and transmits the terminal location information to the control device 300. Specifically, after the control device 300 permits the terminal 200 to use the privileged ID of the managed server 310, the location information acquisition unit 202 acquires terminal location information at a predetermined time interval. Then, after the control device 300 permits the terminal 200 to use the privileged ID of the managed server 310, the ID management relay unit 201 transmits the terminal location information to the control device 300 at a predetermined time interval.

The control device 300 is described in detail below.

When the managed server 310 authenticates the connection user authentication information sent from the terminal 200, the ID usage management unit 301 judges whether or not to permit the terminal 200 to use the privileged ID (first ID) based on the terminal location information and the time when the terminal location information was received. In the following explanation, the time when the ID usage management unit 301 received the terminal location information is also referred to as the usage judgment time.

Specifically, it is assumed that the managed server 310 authenticates the connection user authentication information sent from the terminal 200, and the difference between the location of the terminal 200 and the location previously requested for use is equal to or less than the distance threshold. Furthermore, it is assumed that the usage judgment time is after the specified usage start time and before the specified usage end time. In this case, the ID usage management unit 301 permits the terminal 200 to use the first ID. Here, it is assumed that the managed server 310 is the managed server 310 to which the terminal 200 is to connect. Furthermore, it is assumed that the usage start time and usage end time are times previously registered as usage application information.

Furthermore, it is assumed that the ID usage management unit 301 receives terminal location information from the terminal 200 after permitting the terminal 200 to use the privileged ID of the managed server 310. In this case, the ID usage management unit 301 determines whether to permit the terminal 200 to use the privileged ID corresponding to the managed server 310 to which it is to be connected, based on the terminal location information and the usage determination time.

Furthermore, after the ID usage management unit 301 permits the terminal 200 to use the privileged ID corresponding to the connected managed server 310, it is assumed that at least one of the terminal location information and the usage determination time no longer satisfies the predetermined condition. In that case, the ID usage management unit 301 makes the privileged ID unavailable for use by the terminal 200.

Specifically, after the ID usage management unit 301 permits the terminal 200 to use the privileged ID corresponding to the managed server 310 to which it is to connect, the distance between the location of the terminal 200 and the work location for which use has been applied in advance exceeds the distance threshold for which use has been applied in advance. In that case, the ID usage management unit 301 makes the privileged ID unavailable for use by the terminal 200.

In addition, the ID usage management unit 301 may permit the terminal 200 to use the privileged ID corresponding to the managed server 310 to which the terminal 200 is to be connected, and then the usage decision time may exceed the usage application time that was previously applied for. In this case, the ID usage management unit 301 may disable the use of the privileged ID from the terminal 200.

Furthermore, it is assumed that the ID usage management unit 301 receives terminal location information from the terminal 200 after disabling the use of the privileged ID corresponding to the managed server 310 to be connected from the terminal 200. In this case, it is assumed that the usage judgment time is after the usage start time previously applied for and before the usage end time previously applied for. In this case, based on the received terminal location information, the ID usage management unit 301 again permits the terminal 200 to use the privileged ID corresponding to the managed server 310. Specifically, if the received terminal location information satisfies a predetermined condition, it again permits the terminal 200 to use the privileged ID corresponding to the managed server 310.

Next, the operation of the management system 1 according to this embodiment will be described in detail.

First, we will explain the process of registering a work user with reference to Figure 6.

In step A1, the management server control unit 104 accepts input of the work user ID and password.

For example, the administrator of the management server 100 may use an input device (such as a keyboard (not shown)) connected to the management server 100 to input the work user ID and the password corresponding to the work user ID. Alternatively, for example, the administrator of the management server 100 may use an information processing device (computer) different from the management server 100 to input the work user ID and the password corresponding to the work user ID. Then, the information processing device different from the management server 100 may transmit the input work user ID and the password corresponding to the work user ID to the management server 100. In this case, the information processing device may transmit the work user ID and the password corresponding to the work user ID to the management server 100 via a network (for example, the Internet).

Similarly, hereinafter, it is assumed that the administrator of the management server 100 may input information using an input device (keyboard, etc. (not shown)) connected to the management server 100, and detailed explanations will be omitted. Similarly, hereinafter, it is assumed that the administrator of the management server 100 may input information using an information processing device (computer) different from the management server 100, and detailed explanations will be omitted. In that case, as described above, it is assumed that the information processing device may transmit the input information to the management server 100 via a network (e.g., the Internet), and detailed explanations will be omitted.

In step A2, the management server control unit 104 registers the input work user ID and password in the work user table 107.

Next, the process of registering server connection information and connected user authentication information will be described with reference to FIG. 7.

In step A11, the management server control unit 104 accepts input of managed server information including server connection information, connected user authentication information, registered location information, and distance threshold for one or more managed servers 310. Note that it is assumed here that the input connected user authentication information has been registered in advance in the managed server 310.

In step A12, the management server control unit 104 registers the input of the managed server information in the managed server table 106.

In step A13, the management server control unit 104 accepts input of registration location information and a distance threshold for the managed server 310 corresponding to the managed server information registered in the ID management database 102. In step A14, the management server control unit 104 registers the input registration location information and distance threshold in the managed server table 106.

Next, the process of registering application information will be explained with reference to Figure 8.

In step A21, the usage application management unit 103 accepts usage application information for one or more managed servers 310. Specifically, the usage application management unit 103 accepts usage application information for one or more managed servers 310, including a managed server ID, a privilege ID, the authority for which the application is made, a usage start time, and a usage end time.

In step A22, the usage application management unit 103 presents the received usage application information to the administrator of the management server 100 (i.e., the person who approves the usage application). Specifically, the usage application management unit 103 presents usage application information including the managed server ID, privilege ID, the authority to be applied for, the usage start time, and the usage end time for one or more managed servers 310 to the administrator of the management server 100.

For example, the usage application management unit 103 may output the received usage application information using a display device (such as a display (not shown)). Alternatively, the usage application management unit 103 may transmit the received usage application information to an information processing device (such as a PC (Personal Computer)) used by an administrator of the management server 100 via a network (such as the Internet). There are various methods for presenting the received usage application information to an administrator of the management server 100 (i.e., a person who approves the usage application), and the details thereof are not important.

The administrator of the management server 100 checks the presented usage application information. If the administrator of the management server 100 approves the usage application information, the administrator performs a predetermined approval operation. For example, the usage application management unit 103 may display an "Approve" button on the display screen. Then, if the administrator of the management server 100 approves the usage application information, the administrator may perform the approval operation by pressing the "Approve" button.

In step A23, the usage application management unit 103 accepts approval operations from the administrator of the management server 100 or the like regarding the accepted usage application information. In step A24, the usage application management unit 103 registers the approved usage application information in the usage application information table 105.

Next, the operation of the management system 1 will be described with reference to FIG. 9. In the following description, it is assumed that the management server 100 has already executed the processes shown in FIGS. 6 to 8. In other words, it is assumed that the management server 100 has already registered the necessary information in the ID management database 102. In other words, it is assumed that the management server 100 has already registered information in each of the working user table 107, the managed server table 106, and the usage application information table 105.

In step S1, the terminal 200 requests authentication of the working user. Specifically, the ID management relay unit 201 transmits the working user ID and password to the management server 100 and requests authentication of the working user. Here, it is assumed that the terminal 200 is in a state in which it can connect to the management server 100 via a network (second network) different from the managed server network 400.

In step S2, the management server 100 authenticates the work user. Specifically, the management server control unit 104 receives the work user ID and password from the terminal 200. The management server control unit 104 then determines whether the received work user ID and password are registered in the work user table 107.

If the received work user ID and password are not registered in the work user table 107, the management server control unit 104 does not authenticate the work user for which authentication is requested. In this case, the management server control unit 104 notifies the terminal 200 that made the authentication request that the work user for which authentication is requested will not be authenticated.

If the received work user ID and password are registered in the work user table 107, the management server control unit 104 authenticates the work user for which authentication is requested. Note that the following explanation will be given for the case where the management server control unit 104 authenticates the work user for which authentication is requested.

In step S3, if the management server 100 authenticates the work user, it acquires a list of managed servers 310 corresponding to the work user. Specifically, the management server control unit 104 refers to the usage application information table 105 and acquires one or more managed server IDs corresponding to the authenticated work user as a list of managed servers 310.

In step S4, the management server 100 transmits the acquired list of managed servers 310 to the terminal 200. In step S5, the terminal 200 receives the list of managed servers 310.

In step S6, the terminal 200 determines the managed server ID corresponding to the managed server 310 that is the target of the usage application based on the user's operation. Specifically, the ID management relay unit 201 displays the list of managed server IDs received on the display screen of the terminal 200. The user of the terminal 200 selects the managed server ID that is the target of the usage application from the displayed list of managed server IDs. Then, the ID management relay unit 201 determines the managed server ID selected by the user as the managed server ID that corresponds to the managed server 310 that is the target of the usage application.

In step S7, the terminal 200 transmits the determined managed server ID. In step S8, the management server 100 receives the managed server ID.

In step S9, the management server 100 transmits the managed server information, including server connection information, connected user authentication information, registered location information, and distance threshold, and the usage application information to the terminal 200. Specifically, the management server control unit 104 refers to the managed server table 106 and acquires the managed server information corresponding to the received managed server ID. Here, the managed server information includes server connection information, connected user authentication information, registered location information, and distance threshold. Furthermore, the management server control unit 104 refers to the usage application information table 105 and acquires the usage application information corresponding to the received managed server ID. Then, the management server control unit 104 transmits the acquired managed server information and usage application information to the terminal 200.

In step S10, the terminal 200 receives the managed server information and the usage application information.

Here, the ID management relay unit 201 may display the server connection information from the received managed server information on the display screen of the terminal 200. Furthermore, the ID management relay unit 201 may display the received usage application information on the display screen of the terminal 200.

Let us assume that the management system 1 prohibits the user from directly logging in to the managed server 310 using the connected user ID. In this case, it is preferable that the ID management relay unit 201 does not present the connected user authentication information, which is included in the received managed server information, to the user.

In step S11, the terminal 200 uses the server connection information from the received managed server information to connect to the managed server 310. Then, the process proceeds to step S21 shown in FIG. 10.

Next, the operation of the management system 1 will be described with reference to FIG. 10. In the following description, it is assumed that the terminal 200 is in a state in which it can connect to the control device 300 and the managed server 310 via the managed server network 400. In other words, in the following description, it is assumed that the user operates the terminal 200 at a location where it can connect to the managed server network 400.

In step S21, the terminal 200 transmits the received managed server information, usage application information, and terminal location information to the control device 300. Specifically, the location information acquisition unit 202 acquires terminal location information indicating the location of the terminal 200. Then, the ID management relay unit 201 transmits the received managed server information, usage application information, and acquired terminal location information to the control device 300.

In step S22, the control device 300 receives the managed server information, the usage application information, and the terminal location information.

In step S23, the control device 300 transmits connected user authentication information to the managed server 310 for which usage has been requested, and requests user authentication. Specifically, the ID usage management unit 301 connects to the managed server 310 using the server connection information from the received managed server information. The ID usage management unit 301 then transmits connected user authentication information to the connected managed server 310, and requests authentication of the connected user. Specifically, the ID usage management unit 301 transmits the connected user ID and password to the connected managed server 310, and requests authentication of the connected user.

In step S24, the managed server 310 uses the connected user authentication information to perform user authentication. For example, if the OS (Operating System) of the managed server 310 is Linux (registered trademark), the managed server 310 may use ssh to perform user authentication. Also, for example, if the OS of the managed server 310 is Windows (registered trademark), the managed server 310 may use PowerShell to perform user authentication. Of course, the managed server 310 may perform user authentication using a method that corresponds to the operating environment. The managed server 310 then responds to the control device 300 with the result of authentication of the connected user (step S25).

In step S26, the control device 300 determines whether authentication of the connecting user has been successful. If authentication of the connecting user has been successful (Yes branch of step S26), the process proceeds to step S101 shown in FIG. 11. If authentication of the connecting user has failed (No branch of step S26), the ID usage management unit 301 sends a notification of failure of the usage request to the terminal 200 (step S27). Then, the terminal 200 receives the notification of failure of the usage request (step S28).

Next, we will continue to explain the operation of the control device 300 with reference to Figure 11.

In step S101, the ID usage management unit 301 judges whether the difference between the location of the terminal 200 and the location previously applied for usage is equal to or less than a predetermined distance threshold. Specifically, the ID usage management unit 301 compares the terminal location information with the registered location information included in the usage application information. The ID usage management unit 301 then judges whether the difference between the terminal location information and the registered location information included in the usage application information (for example, the location where the user of the terminal 200 plans to work) is equal to or less than the distance threshold included in the usage application information.

If the difference between the location of the terminal 200 and the location previously requested for use exceeds a predetermined distance threshold (No branch in step S101), the process proceeds to step S103. In step S103, the ID usage management unit 301 determines that the use of the requested privileged ID is not permitted on the managed server 310 for which the request for use of the privileged ID has been made. Then, the process proceeds to step S106.

On the other hand, if the difference between the location of the terminal 200 and the location previously applied for use is less than or equal to the predetermined distance threshold (Yes branch of step S101), the process transitions to step S102.

In step S102, the ID usage management unit 301 determines whether the time when the terminal location information was received is between the usage start time and usage end time included in the usage application information. In other words, the ID usage management unit 301 determines whether the usage judgment time is after the specified usage start time and before the specified usage end time.

If the time when the terminal location information was received is not between the usage start time and usage end time included in the usage application information (No branch of step S102), the process transitions to step S103. In step S103, the ID usage management unit 301 determines that the use of the requested privileged ID is not permitted on the managed server 310 for which the usage of the privileged ID has been applied for. Then, the process transitions to step S106.

On the other hand, if the time when the terminal location information was received is between the usage start time and usage end time included in the usage application information (Yes branch of step S102), the process proceeds to step S104. In step S104, the ID usage management unit 301 permits the terminal 200 to use the requested privileged ID on the managed server 310 for which usage has been requested.

In step S105, the ID usage management unit 301 sets the requested authority for the requested privileged ID on the managed server 310. Here, the ID usage management unit 301 may set a password for the privileged ID that has been permitted to be used. For example, the ID usage management unit 301 may create a random password as the password corresponding to the privileged ID.

In step S106, the ID usage management unit 301 transmits information regarding whether the privileged ID can be used to the terminal 200. Specifically, the ID usage management unit 301 transmits information regarding whether the privileged ID can be used to the terminal 200. Furthermore, if a password has been set for the privileged ID that has been permitted for use, the ID usage management unit 301 notifies the terminal 200 of the set password.

When the terminal 200 receives information regarding whether or not the privileged ID can be used, the ID management relay unit 201 displays the information regarding whether or not the privileged ID can be used on the display screen of the terminal 200. Furthermore, when the terminal 200 receives a password corresponding to the privileged ID, the ID management relay unit 201 displays the received password on the display screen of the terminal 200. In this case, the user of the terminal 200 uses the displayed password to log in to the managed server 310 and perform work on the managed server 310.

Next, referring to FIG. 12, the process after the control device 300 permits the terminal 200 to use the privileged ID of the managed server 310 will be described.

In step S201, the ID usage management unit 301 determines whether terminal location information has been received from the terminal 200 at a predetermined time interval. Specifically, the ID usage management unit 301 determines whether terminal location information has been received at a predetermined time interval from the terminal 200 that is permitted to use the privileged ID of the managed server 310.

If the ID usage management unit 301 receives terminal location information from the terminal 200 (Yes branch of step S201), the process proceeds to step S202. On the other hand, if the ID usage management unit 301 does not receive terminal location information from the terminal 200 (No branch of step S201), the process proceeds to step S203.

In step S202, the ID usage management unit 301 determines whether the difference between the location of the terminal 200 and the location for which usage has been applied in advance is equal to or less than a predetermined distance threshold. In other words, the same process as step S101 shown in FIG. 11 is performed.

If the difference between the location of the terminal 200 and the location requested in advance exceeds a predetermined distance threshold (No branch in step S202), the process proceeds to step S203. In step S203, the ID usage management unit 301 disables the requested privileged ID on the managed server 310. Then, the process proceeds to step S207.

On the other hand, if the difference between the location of the terminal 200 and the location previously applied for use is less than or equal to a predetermined distance threshold (Yes branch of step S202), the process transitions to step S204.

In step S204, the ID usage management unit 301 determines whether the requested authority has been set for the requested privileged ID on the managed server 310. If the requested authority has been set for the requested privileged ID on the managed server 310 (Yes branch in step S204), the process proceeds to step S208.

On the other hand, if the requested authority is not set for the privileged ID on the managed server 310 for which use has been requested (No branch in step S204), the process proceeds to step S205. In step S205, the ID usage management unit 301 makes the requested privileged ID available on the managed server 310 for which use has been requested. In other words, after making the requested privileged ID unavailable from the terminal 200, the ID usage management unit 301 permits the terminal 200 to use the privileged ID if the terminal location information and the usage determination time satisfy predetermined conditions.

In step S206, the ID usage management unit 301 sets the requested privileges for the privileged ID on the managed server 310 that has been requested for use.

In step S207, the ID usage management unit 301 transmits to the terminal whether the privileged ID can be used.

In step S208, the ID usage management unit 301 determines whether the current time has passed the usage end time. If the current time has not passed the usage end time (No branch in step S208), the process returns to step S201 and continues. On the other hand, if the current time has passed the usage end time (Yes branch in step S208), the ID usage management unit 301 makes the requested privileged ID unavailable on the managed server 310 (step S209). The ID usage management unit 301 then notifies the terminal 200 that the requested privileged ID has been made unavailable.

As described above, in the management system 1 according to this embodiment, the control device 300 allows an external device (i.e., the terminal 200) different from the managed device 1010 to use the privileged ID of the managed server 310. Furthermore, in the management system 1 according to this embodiment, the control device 300 determines whether to allow the terminal 200 to use the privileged ID of the managed server 310 based on the location and time of the terminal 200. Specifically, in the management system 1 according to this embodiment, when the worker (user of the terminal 200) is at a pre-approved location within a pre-approved time, the control device 300 allows the use of the privileged ID of the managed server 310. As a result, the management system 1 according to this embodiment contributes to reducing the security risk of the managed server 310 while improving user convenience.

In addition, in the management system 1 according to this embodiment, if the control device 300 does not receive terminal location information at a predetermined time interval after permitting the use of the privileged ID, the control device 300 disables the use of the privileged ID of the managed server 310. For example, assume that the user of the terminal 200 has finished using the privileged ID and turned off the power of the terminal 200. When the terminal 200 is turned off, the control device 300 is no longer able to receive terminal location information at a predetermined time interval. In that case, the control device 300 disables the use of the privileged ID of the managed server 310. In other words, in a situation where the user does not actually use the privileged ID, the management system 1 according to this embodiment disables the use of the privileged ID. Therefore, the management system 1 according to this embodiment contributes to protecting the managed server 310 appropriately according to the situation while improving user convenience.

In addition, in the management system 1 according to this embodiment, the control device 300 and the managed server 310 are arranged in a LAN (managed server network 400). Furthermore, in the management system 1 according to this embodiment, the terminal 200 connects to the management server 100 via a network different from the managed server network 400. Therefore, the management system 1 according to this embodiment can manage the privileged ID for the managed server 310 present in the LAN. As a result, the management system 1 according to this embodiment contributes to reducing security risks while improving user convenience for the managed server 310 present in the LAN.

In the above explanation, the management server 100 transmits the managed server IDs corresponding to the authenticated work user to the terminal 200 as a list of managed servers 310. Here, the management server 100 may of course transmit the list of managed servers 310 by associating the registered location information, distance threshold, etc. with the managed server ID. The details of the list of managed servers 310 transmitted from the management server 100 to the terminal 200 do not matter as long as the information is usable when the user selects the managed server 310 for which usage is requested.

The terminal 200 may also transmit terminal location information to the management server 100 together with an authentication request for the working user. Then, when the management server 100 authenticates the working user, it may refer to the managed server table 106 and identify managed servers 310 for which the difference between the terminal location information and the registered location information is within a predetermined range. Then, the management server 100 may transmit the managed server IDs of the identified managed servers 310 to the terminal 200 as a list of managed servers 310.

Also, a QR (Quick Response) code (registered trademark) including the managed server ID may be attached to the managed server 310. Furthermore, in this modified example 1, the terminal 200 is equipped with a camera (not shown). In this case, the terminal 200 uses the camera to photograph the QR code attached to the managed server 310 and reads the information stored in the QR code (i.e., information including the managed server ID). The terminal 200 transmits the read information to the management server 100. The management server 100 refers to the managed server table 106 and acquires the managed server information based on the received managed server ID. Furthermore, the management server 100 refers to the usage application information table 105 and acquires the usage application information based on the received managed server ID. The management server 100 may then transmit the acquired managed server information and usage application information to the terminal 200.

In the above description, the control device 300 controls whether or not the privileged ID of the information processing device (managed server 310) can be used. However, this is not intended to limit the control target of the control device 300 to the managed server 310. The managed device may be a network device. In that case, the control device 300 may connect to the network device (i.e., the managed device) and control whether or not the privileged ID can be used in the network device.

Furthermore, for example, the control device 300 may control a system including two or more information processing devices. Specifically, the control device 300 may connect to the system and control whether or not a privileged ID can be used in the system. The control target of the control device 300 may be any device to which a privileged ID is set, regardless of the type of device.
The present invention is also described as follows:
(Appendix 1)
a management target device that can be operated using a first ID having a predetermined authority;
A control device that controls the managed device;
A terminal that acquires terminal location information indicating a location of the terminal and transmits the terminal location information to the control device;
Including,
The control device requests the managed device to authenticate the terminal, and if the managed device authenticates the terminal, determines whether to allow the terminal to use the first ID based on the terminal location information and the usage judgment time.
(Appendix 2)
The terminal acquires the terminal location information at a predetermined time interval and transmits the terminal location information to the control device;
The management system described in Appendix 1, wherein when the ID usage management unit receives terminal location information from the terminal after the managed device authenticates the terminal, it determines whether to allow the terminal to use the first ID corresponding to the managed device to which it is connected based on the terminal location information and the usage judgment time.
(Appendix 3)
The terminal transmits registration position information and a distance threshold to the control device;
The management system described in Appendix 1 or 2, wherein the ID usage management unit permits the terminal to use the first ID when the managed device authenticates the terminal, when the difference between the terminal location information and the registered location information is less than the distance threshold, and when the usage judgment time is after a specified usage start time and before a specified usage end time.
(Appendix 4)
The management system described in Appendix 3, wherein the ID usage management unit makes the first ID corresponding to the managed device to be connected unavailable from the terminal, receives the terminal location information from the terminal, and if the usage determination time is after the usage start time and before the usage end time, again allows the terminal to use the first ID corresponding to the managed device based on the terminal location information.
(Appendix 5)
the managed device is connectable using a second ID different from the first ID,
The terminal transmits authentication information corresponding to the second ID and the terminal location information to the control device;
A management system as described in any one of Appendix 1 to 4, wherein when the ID usage management unit receives the authentication information, it requests the managed device to authenticate the authentication information, and when the managed device authenticates the authentication information sent from the terminal, it determines whether to allow the terminal to use the first ID based on the terminal location information and the usage judgment time when the terminal location information was received.
(Appendix 6)
Controlling a managed device that can be operated using a first ID having a predetermined authority;
A control device comprising an ID usage management unit that requests the managed device to authenticate a terminal, and if the managed device authenticates the terminal, determines whether to permit the terminal to use the first ID based on terminal location information indicating the location of the terminal and the usage judgment time.
(Appendix 7)
acquiring terminal location information indicating a location of the terminal;
a step of requesting authentication of the terminal from a managed device that is operable using a first ID having a predetermined authority;
if the terminal is authenticated, determining whether or not to permit the terminal to use the first ID based on the terminal location information and a usage determination time;
A management method executed by a computer that controls a control device, comprising:
(Appendix 8)
receiving terminal location information indicating a location of the terminal from the terminal;
A process of requesting authentication of a terminal to a managed device that is operable using a first ID having a predetermined authority;
a process of determining whether or not to permit the terminal to use the first ID based on the terminal location information and a usage determination time when the terminal is authenticated;
A program for causing a computer that controls a control device to execute the above.
The present invention can also be described in the following forms.
(Form 1)
a management target device that can be operated using a first ID having a predetermined authority;
A control device that controls the managed device;
A terminal that transmits terminal location information indicating a location of the terminal to the control device;
Including,
The control device requests the managed device to authenticate a second ID in order to use the first ID, and if the managed device authenticates the second ID, determines whether to permit the terminal to use the first ID based on a first time at which terminal location information is received from the terminal.
(Form 2)
a management target device that can be operated using a first ID having a predetermined authority;
A control device that controls the managed device;
A terminal that transmits terminal location information indicating a location of the terminal to the control device;
Including,
The control device requests the managed device to authenticate a second ID in order to use the first ID, and if the managed device authenticates the second ID, determines whether to permit the terminal to use the first ID based on terminal location information received from the terminal at a first time.
(Form 3)
when terminal location information is not received from the terminal within a first time interval after the control device has permitted the terminal to use the first ID, the control device disables the first ID that has been permitted to be used.
3. The management system according to aspect 1 or 2.
(Form 4)
the control device stores a start time and an end time that are a time range in which use of the first ID is permitted;
If the first time is outside the range between the start time and the end time of the previous period, it is determined that the first ID is not to be used.
The management system according to any one of aspects 1 to 3.
(Form 5)
when the current time exceeds the end time after the control device has permitted the terminal to use the first ID, the control device disables the first ID that has been permitted to be used.
5. The management system according to aspect 4.
(Form 6)
Controlling a managed device that is operable using a first ID having a predetermined authority;
receiving terminal location information indicating a location of the terminal from the terminal;
A control device that requests the managed device to authenticate a second ID in order to use the first ID, and if the managed device authenticates the second ID, determines whether or not to permit the terminal to use the first ID based on a first time at which terminal location information is received from the terminal.
(Form 7)
Controlling a managed device that is operable using a first ID having a predetermined authority;
receiving terminal location information indicating a location of the terminal from the terminal;
A control device that requests the managed device to authenticate a second ID in order to use the first ID, and if the managed device authenticates the second ID, determines whether or not to permit the terminal to use the first ID based on terminal location information received from the terminal at a first time.
(Form 8)
when terminal location information is not received from the terminal within a first time interval after the control device has permitted the terminal to use the first ID, the control device disables the first ID that has been permitted to be used.
The control device according to aspect 6 or 7.
(Mode 9)
storing a start time and an end time of a time range during which the use of the first ID is permitted;
If the first time is outside the range between the start time and the end time of the previous period, it is determined that the first ID is not to be used.
9. The control device according to any one of aspects 6 to 8.
(Form 10)
when the current time exceeds the end time after the control device has permitted the terminal to use the first ID, the control device disables the first ID that has been permitted to be used.
A control device as described in aspect 9.
(Form 11)
receiving terminal location information indicating a location of the terminal from the terminal;
a step of requesting a managed device, which is operable using a first ID having a predetermined authority, to authenticate a second ID for using the first ID;
if the second ID is authenticated, determining whether or not to permit the terminal to use the first ID based on a first time when terminal location information is received from the terminal;
A management method executed by a computer that controls a control device, comprising:
(Form 12)
receiving terminal location information indicating a location of the terminal from the terminal;
a step of requesting a managed device, which is operable using a first ID having a predetermined authority, to authenticate a second ID for using the first ID;
if the second ID is authenticated, determining whether or not to permit the terminal to use the first ID based on terminal location information received from the terminal at a first time;
A management method executed by a computer that controls a control device, comprising:
(Form 13)
a step of disabling the first ID that has been permitted to be used when terminal location information is not received from the terminal within a first time interval after the terminal is permitted to use the first ID;
13. The management method according to claim 11 or 12, comprising:
(Form 14)
determining that the first ID is not to be used when the first time is outside a range of a start time and an end time that is a time range in which the use of the first ID is permitted;
14. The management method according to any one of aspects 11 to 13, comprising:
(Form 15)
a step of disabling the first ID that has been permitted for use when the current time has passed the end time after the use of the first ID has been permitted for the terminal;
The management method according to aspect 14, comprising:
(Form 16)
A process of receiving terminal location information indicating a location of the terminal from the terminal;
A process of requesting a managed device, which is operable using a first ID having a predetermined authority, to authenticate a second ID for using the first ID;
If the second ID is authenticated, a process of determining whether or not to permit the terminal to use the first ID based on a first time when terminal location information is received from the terminal;
A program for causing a computer that controls a control device to execute the above.
(Form 17)
A process of receiving terminal location information indicating a location of the terminal from the terminal;
A process of requesting a managed device, which is operable using a first ID having a predetermined authority, to authenticate a second ID for using the first ID;
if the second ID is authenticated, determining whether or not to permit the terminal to use the first ID based on terminal location information received from the terminal at a first time;
A program for causing a computer that controls a control device to execute the above.

The disclosures of the above patent documents are incorporated herein by reference. Within the framework of the entire disclosure of the present invention (including the scope of claims), and further based on the basic technical ideas, modifications and adjustments of the embodiments are possible. Furthermore, within the framework of the entire disclosure of the present invention, various combinations or selections of the various disclosed elements (including each element of each claim, each element of each embodiment, each element of each drawing, etc.) are possible. In other words, the present invention naturally includes various modifications and corrections that a person skilled in the art would be able to make in accordance with the entire disclosure, including the scope of claims, and the technical ideas. In particular, with regard to the numerical ranges described in this document, any numerical value or subrange included within the range should be interpreted as being specifically described even if not otherwise specified. When an algorithm, software, or flow chart or automated process steps are shown in the present invention, it is self-evident that a computer is used, and that a processor and a memory or storage device are attached to the computer. Therefore, even if there is no explicit indication, it is understood that these elements are naturally described in this application.

1, 1000 Management system 100 Management server 101 Management server storage unit 102 ID management database 103 Use application management unit 104 Management server control unit 105 Use application information table 106 Managed server table 107 Work user table 200, 1030 Terminal 201 ID management relay unit 202 Position information acquisition unit 300, 1020 Control device 301, 1021 ID use management unit 310, 310a, 310b Managed server 400 Managed server network 1010 Managed device

Claims (18)

The control device,
receiving authentication information, a first ID , and location information of the terminal from the terminal;
requesting authentication of the terminal from a managed device that is operable using the first ID;
if the terminal is authenticated, determining whether or not to permit the terminal to use the first ID based on location information of the terminal;
Control methods. The authentication information includes a second ID;
The managed device performs authentication using the authentication information.
The control method according to claim 1 . The control device stores a predetermined condition related to a position,
making a determination based on the condition and the location information;
The control method according to claim 2 . The conditions include information about the location.
The control method according to claim 3 . The condition further includes distance information regarding an allowable distance from the point.
The control method according to claim 4 . The control device,
receiving authentication information and a first ID from the terminal;
storing the received time;
requesting authentication of the terminal from a managed device that is operable using the first ID;
if the terminal is authenticated, determining whether or not to permit the terminal to use the first ID based on the time of the authentication;
Control methods. The authentication information includes a second ID;
The managed device performs authentication using the authentication information.
The control method according to claim 6. The time of the authentication is any one of the time of the determination, the time of the reception, and the current time.
The control method according to claim 6. storing in advance a time condition for permitting use of the first ID;
making a determination based on the time and the condition;
The control method according to claim 6 . The conditions include a start time and an end time for permitting use,
permitting use if the received time is between the start time and the end time;
The control method according to claim 9 . The first ID is a privileged user.
The control method according to any one of claims 1 to 10 . receiving authentication information, a first ID , and location information of the terminal from the terminal;
requesting authentication of the terminal from a managed device that is operable using the first ID;
if the terminal is authenticated, determining whether or not to permit the terminal to use the first ID based on location information of the terminal;
Control device . The authentication information includes a second ID;
The managed device performs authentication using the authentication information.
The control device according to claim 12 . receiving authentication information and a first ID from the terminal;
storing the received time;
requesting authentication of the terminal from a managed device that is operable using the first ID;
if the terminal is authenticated, determining whether or not to permit the terminal to use the first ID based on the time of the authentication;
Control device . The authentication information includes a second ID;
The managed device performs authentication using the authentication information.
The control device according to claim 14 . The time of the authentication is any one of the time of the determination, the time of the reception, and the current time.
The control device according to claim 14. The control device includes:
receiving authentication information, a first ID , and location information of the terminal from the terminal;
requesting authentication of the terminal from a managed device that is operable using the first ID;
if the terminal is authenticated, determining whether or not to permit the terminal to use the first ID based on location information of the terminal;
A program that executes a process. The control device includes:
receiving authentication information and a first ID from the terminal;
storing the received time;
requesting authentication of the terminal from a managed device that is operable using the first ID;
if the terminal is authenticated, determining whether or not to permit the terminal to use the first ID based on the time of the authentication;
A program that executes a process.

Images