JP5294347B2 - Privilege management system and privilege management method - Google Patents

Description

  The present invention relates to a privilege management system and a privilege management method.

  Patent Document 1 describes a computer system that can grant privileges to general users. A user who has been granted a privilege in the computer system described in Patent Document 1 can log in to the server using a user terminal and perform a specific task.

  In an environment in which a user logs in to a server using a user terminal and performs work, the server may be tracked and audited for unauthorized operations.

  Further, even in a situation where the authorization for each account is strictly managed, when a user who is granted a privilege from the computer system described in Patent Document 1 works on the server, the privilege is used. In many cases, audits are required at a later date.

  A centralized management method using a directory service such as LDAP (Lightweight Directory Access Protocol) is known as an efficient mechanism for confirming the purpose of acquiring the privilege and approving the privilege grant when the privilege is acquired. .

JP 2006-27786 A

  However, when a user acquires a privilege, if a computer system failure, a network failure, or an LDAP management server failure described in Patent Document 1 occurs, the privilege may not be acquired. Therefore, there is a problem that there is a possibility that the privilege cannot be acquired when the privilege is urgently required.

  An object of the present invention is to provide a privilege management system and a privilege management method capable of facilitating auditing while solving the problem that privileges cannot be acquired.

  The privilege management system of the present invention is a privilege management system including a predetermined server that can communicate with a worker terminal, and a management server that can communicate with the worker terminal and the predetermined server. When receiving an application for performing a predetermined work requiring privilege to the predetermined server from the worker terminal, identification information corresponding to the application is transmitted to the worker terminal, and the identification is performed. Issuing means for transmitting information to the predetermined server, the predetermined server comprising: first storage means; second storage means; communication means for communicating with the management server and the worker terminal; and the communication means When the identification information is received from the management server, the processing means for storing the identification information in the first storage means, and the communication means includes the work information from the worker terminal. When receiving the request to obtain, the granting means for granting the privilege to the worker terminal, and when the work information matches the identification information in the first storage means, the work information is audited and identified. Information stored in the second storage means in association with the first information, and the same information as the work information does not exist in the first storage means and the work information is different from the identification information. Is stored in the second storage means in association with second audit identification information different from the first information, and the same information as the work information is stored in the first information. When the work information does not exist in the storage unit and the work information is different from the predetermined information, the work information is associated with third information for audit identification that is different from the first information and the second information. Control means for storing in the second storage means; Including the.

  The privilege management method of the present invention is a privilege management method in a privilege management system including a predetermined server capable of communicating with a worker terminal, and a management server capable of communicating with the worker terminal and the predetermined server, When the management server receives, from the worker terminal, an application for performing a predetermined task requiring privilege to the predetermined server, the management server transmits identification information corresponding to the request to the worker terminal. And an issuing step for transmitting the identification information to the predetermined server, and a processing step for storing the identification information in a first storage means when the predetermined server receives the identification information from the management server; When the predetermined server receives from the worker terminal a request for acquiring the privilege including work information, the granting step of granting the privilege to the worker terminal; When the work information matches the identification information in the first storage means, the server stores the work information in association with the first information for audit identification in the second storage means, and If the same information as the information does not exist in the first storage means and the work information matches the predetermined information different from the identification information, the work information is audited different from the first information. When the same information as the work information does not exist in the first storage means and is associated with the second information for identification, and the work information is different from the predetermined information Includes a control step of storing the work information in the second storage unit in association with third information for audit identification that is different from the first information and the second information.

  According to the present invention, it is possible to facilitate auditing while solving the problem that privileges cannot be acquired.

It is a block diagram showing privilege management system 1 of one embodiment of the present invention. It is the figure which showed work ID registration information. It is the figure which showed work ID registration confirmation information. It is the figure which showed work ID information. It is a figure showing privilege grant information. It is a sequence diagram for demonstrating operation | movement of the privilege management system. It is the figure which showed an example of the work ID registration screen. It is the figure which showed an example of the approval screen. It is the figure which showed an example of the privilege acquisition screen.

  Hereinafter, an embodiment of the present invention will be described with reference to the drawings.

  FIG. 1 is a block diagram showing a privilege management system 1 according to an embodiment of the present invention.

  In FIG. 1, the privilege management system 1 includes a management server 2, an approver terminal 3, a work target server 4, and an audit terminal 5. The work target server 4 may be one or a plurality of servers.

  The management server 2 and the work target server 4 can communicate with each other. Moreover, the management server 2 and the work target server 4 can communicate with the worker terminal 6 used by the worker.

  The management server 2 includes an issuing unit 21 and a storage unit 22.

  Issuing unit 21 can be generally referred to as issuing means.

  The issuing unit 21 has an internal clock that indicates the date and time. The issuing unit 21 makes an application (hereinafter referred to as “operation application”) for performing a predetermined operation requiring privilege (for example, an operation for changing confidential information) to the operation target server 4 from the worker terminal 6. Receive. The predetermined work requiring the privilege is not limited to the work for changing the confidential information but can be changed as appropriate.

  The issuing unit 21 receives the work ID registration information including the worker account ID (hereinafter simply referred to as “account ID”), the worker name, and the work target server identifier transmitted from the worker terminal 6 as a work application. Receive.

  FIG. 2 is a diagram showing work ID registration information.

  In FIG. 2, the work ID registration information 201 includes an account ID 202, a worker name 203, and a work target server identifier 204. The work target server identifier 204 is an identifier for identifying the work target server 4 on which a predetermined work requiring privilege is performed.

  Upon receiving the work ID registration information 201, the issuing unit 21 transmits a work ID (identification information) corresponding to the work ID registration information 201 to the worker terminal 6, and the work ID is sent to the work target server identifier 204. To the work target server 4 specified.

  In the present embodiment, when receiving the work ID registration information 201, the issuing unit 21 transmits the work ID registration information 201 to the approver terminal 3 used by the approver who approves the work application (work ID registration information 201). To do. When receiving the approval information indicating approval for the work ID registration information 201 from the approver terminal 3, the issuing unit 21 issues a work ID and transmits the work ID to the worker terminal 6.

  Note that when the work ID registration information 201 is received, the issuing unit 21 issues a work ID without sending the work ID registration information 201 to the approver terminal 3 and sends the work ID to the worker terminal 6. May be.

  Further, the issuing unit 21 creates work ID registration confirmation information by adding approval date / time information indicating the approval date / time and the work ID to the work ID registration information 201. The approval date and time is included in a period (hereinafter referred to as “issue period”) from the time when the issuing unit 21 receives the work ID registration information 201 to the time when the issuing unit 21 transmits the work ID to the worker terminal 6. It is an example of 1 timing. The first timing is not limited to the approval date and time, and can be changed as appropriate depending on the purpose of the audit as long as it is within the issuance period.

  FIG. 3 is a diagram showing work ID registration confirmation information. In FIG. 3, the same components as those shown in FIG.

  In FIG. 3, the work ID registration confirmation information 301 includes an account ID 202, a worker name 203, a work target server identifier 204, a work ID 302, and approval date / time information 303.

  The issuing unit 21 stores the work ID registration confirmation information 301 in the storage unit 22.

  Storage unit 22 can generally be referred to as third storage means. The storage unit 22 stores work ID registration confirmation information 301.

  Further, the issuing unit 21 transmits the work ID registration confirmation information 301 to the work target server 4 specified by the work target server identifier 204 in the work ID registration confirmation information 301.

  The approver terminal 3 is used by an approver who approves a work application from the worker terminal 6.

  The work target server 4 can generally be called a predetermined server.

  The work target server 4 includes a storage unit 41, a storage unit 42, a communication unit 43, a processing unit 44, a granting unit 45, and a control unit 46.

  Storage unit 41 can generally be referred to as first storage means. Storage unit 42 can generally be referred to as second storage means.

  In addition, the memory | storage part 41 and the memory | storage part 42 may be provided in one memory | storage part (for example, one hard disk), and may be provided separately.

  Communication unit 43 can be generally referred to as communication means.

  The communication unit 43 communicates with the management server 2 and the worker terminal 6. The communication unit 43 may communicate with the audit terminal 5.

  Processing unit 44 can generally be referred to as processing means.

  When the communication unit 43 receives the work ID 302 from the management server 2, the processing unit 44 stores the work ID 302 in the storage unit 41.

  For example, when the communication unit 43 receives the work ID registration confirmation information 301 from the management server 2, the processing unit 44 stores the work ID registration confirmation information 301 in the storage unit 41.

  When a communication failure occurs between the work target server 4 (specifically, the communication unit 43) and the management server 2, the work ID registration confirmation information 301 transmitted to the work target server 4 is the communication It is not received by the unit 43. In this case, the processing unit 44 cannot store the work ID registration confirmation information 301 in the storage unit 41.

  Giving unit 45 can generally be referred to as a granting means.

  When the communication unit 43 receives a request (hereinafter referred to as “work request”) from the worker terminal 6 to acquire a privilege necessary for the communication unit 43 to perform a predetermined work, the granting unit 45, more specifically, the worker terminal 6. A privilege is given to the worker who is using the worker terminal 6. For example, the granting unit 45 can only operate (read, write, execute, etc.) the flags associated with the account ID of the worker in the storage unit 41 only for some commands and information (such as directories and files). By changing the flag corresponding to the authority to the flag corresponding to the privilege that can operate the target command or information, the privilege is given to the worker terminal 6 (worker). Note that the control unit 46 permits or rejects a command or information operation from the worker (worker terminal 6) specified by the account ID using a flag associated with the account ID.

  The work request includes work information. The work information is, for example, a work ID 302 input to the worker terminal 6 by a worker who is a user of the worker terminal 6.

  In a situation where the work ID 302 is obtained from the management server 2, the worker operates the input unit 61 in the worker terminal 6 and inputs the work ID 302 to the worker terminal 6 as work information.

  On the other hand, for example, when a communication failure occurs between the worker terminal 6 and the management server 2, the management server 2 cannot receive the work ID registration information 201 transmitted from the worker terminal 6, or A situation occurs in which the worker terminal 6 cannot receive the work ID 302 transmitted from the management server 2. In this case, the worker cannot obtain the work ID 302.

  In such a situation, the worker operates the input unit 61 and inputs the special ID given in advance from the management server 2 to the worker terminal 6 as work information. The special case ID indicates information different from the work ID.

  For example, the grant unit 45 receives work ID information including an account ID 202, a worker name 203, and work information 402 transmitted as a work request from the worker terminal 6.

  FIG. 4 is a diagram showing work ID information. In FIG. 4, the same components as those shown in FIG.

  In FIG. 4, the work ID information 401 includes an account ID 202, a worker name 203, and work information 402.

  When the granting unit 45 receives the work ID information 401, among the account IDs in the storage unit 41, the granting unit 45 grants a flag corresponding to the privilege to the same account ID 202 as the account ID 202 indicated in the work ID information 401. The privilege is given to the worker terminal 6 (worker). If the account ID 202 is not the same as the account ID 202 in the work ID information 401 in the storage unit 41, the granting unit 45 stores the account ID 202 in the work ID information 401 in the storage unit 41, and the account A flag corresponding to the privilege is assigned to ID202.

  Control unit 46 can generally be referred to as control means.

  The control unit 46 has an internal clock that indicates the date and time. When the work information 402 in the work ID information 401 matches the work ID 302 in the storage unit 41, the control unit 46 stores the work information 402 in association with the state information indicating normality in the storage unit 42. To do. The state information indicating normality can be generally called first information for audit identification.

  In addition, the control unit 46 does not have the same information as the work information 402 in the work ID information 401 in the storage unit 41 and the work information 402 matches the special case ID, that is, the work When the work information 402 represents a special case ID, the work information 402 is stored in the storage unit 42 in association with the state information representing the special case. Note that the state information representing a special case can be generally called second information for audit identification. Further, the special case ID can be generally referred to as predetermined information.

  Further, when the same information as the work information 402 in the work ID information 401 does not exist in the storage unit 41 and the work information 402 is different from the special case ID, the control unit 46, for example, When the work information 402 represents the work ID 302 but the work ID 302 is not stored in the storage unit 41, the work information 402 is stored in the storage unit 42 in association with the state information representing the delay. Note that the state information indicating the delay can be generally called third information for audit identification.

  For example, the control unit 46 compares the worker names between the work ID information 401 (see FIG. 4) received by the communication unit 43 and the work ID registration confirmation information 301 (see FIG. 3) in the storage unit 41. Further, the work ID is compared with the work information.

  The worker name in the work ID information 401 matches the worker name in the work ID registration confirmation information 301, and the work information 402 in the work ID information 401 matches the work ID in the work ID registration confirmation information 301. Then, the control unit 46 includes the account ID 202, the worker name 203, and the work information 402 in the work ID information 401, and privilege acquisition date and time information indicating the date and time when the grant unit 45 grants the privilege according to the work ID information 401. And privilege grant information including normal state information.

  FIG. 5 shows privilege grant information. In FIG. 5, the same components as those shown in FIG.

  In FIG. 5, the privilege grant information 501 includes an account ID 202, a worker name 203, work information 402, privilege acquisition date / time information 502, and status information 503. Note that the date and time indicated by the privilege acquisition date and time information 502 is an example of the second timing.

  On the other hand, the worker name 203 in the work ID information 401 is not in the work ID registration confirmation information 301, the same information as the work information 402 in the work ID information 401 is not in the work ID registration confirmation information 301, and When the work information 402 in the work ID information 401 is a special case ID, the control unit 46 determines the account ID 202, the worker name 203 and the work information 402 in the work ID information 401, the privilege acquisition date / time information 502, and the special case. And privilege grant information 501 including state information 503 representing the This situation occurs, for example, when a failure of the management server 2 occurs.

  On the other hand, the worker name 203 in the work ID information 401 is not in the work ID registration confirmation information 301, the same information as the work information 402 in the work ID information 401 is not in the work ID registration confirmation information 301, and If the work information 402 in the work ID information 401 is not a special case ID, the control unit 46 displays the account ID 202, the worker name 203 and the work information 402 in the work ID information 401, the privilege acquisition date / time information 502, and the delay. Privilege grant information 501 including state information 503 to be created is created. This situation occurs, for example, when transmission of the work ID registration confirmation information 301 from the management server 2 to the work target server 4 fails.

  The audit terminal 5 is used by an auditor. The audit terminal 5 includes an audit unit 51 and a display unit 52.

  Audit unit 51 can generally be referred to as an auditing means.

  The auditing unit 51 determines whether the state information 503 associated with the work information 402 in the privilege grant information 501 stored in the storage unit 42 in the work target server 4 is state information indicating normality or state information indicating a special case. Check whether the status information represents delay. The audit unit 51 outputs audit information corresponding to the confirmation result.

  For example, when the work information 402 in the storage unit 42 is associated with state information indicating normality, the auditing unit 51 outputs audited information indicating audited as audit information.

  Further, when the work information 402 in the privilege grant information 501 stored in the storage unit 42 is associated with state information representing a special case, the audit unit 51 needs to confirm the work content as the audit information. Output the information required for confirmation.

  Further, when the work information 402 in the privilege grant information 501 stored in the storage unit 42 is associated with the state information indicating the delay, the audit unit 51 stores the information in the storage unit 22 in the management server 2. The date and time indicated by the approved date and time information 303 is compared with the date and time indicated by the privilege acquisition date and time information 502 stored in the storage unit 42 in the work target server 4.

  When the date / time indicated by the approval date / time information 303 is earlier than the date / time indicated by the privilege acquisition date / time information 502, the auditing unit 51 outputs audited information as audit information.

  On the other hand, when the date / time indicated by the approval date / time information 303 is not earlier than the date / time indicated by the privilege acquisition date / time information 502, confirmation necessary information is output as audit information.

  The display unit 52 displays audit information from the audit unit 51.

  Worker terminal 6 includes an input unit 61, a control unit 62, a communication unit 63, and a display unit 64.

  The input unit 61 receives an operator input. The control unit 62 controls the operation of the worker terminal 6. The communication unit 63 communicates with the management server 2 and the work target server 4. The display unit 64 performs various displays.

  Next, the operation will be described.

  FIG. 6 is a sequence diagram for explaining the operation of the privilege management system 1. Hereinafter, the operation of the privilege management system 1 will be described with reference to FIG.

  When the input unit 61 in the worker terminal 6 receives an instruction to connect to the management server 2, the control unit 62 connects to the management server 2 using the communication unit 63 and transmits the account ID 202 to the management server 2. (Step S601). It is assumed that the control unit 62 stores an account ID 202. The input unit 61 may receive an account ID from the worker.

  In the management server 2, when the issuing unit 21 receives the account ID 202, the issuing unit 21 performs an authentication process using the account ID 202 (step S602).

  If the account ID 202 is registered in advance, the issuing unit 21 authenticates the account ID 202 and transmits work ID registration screen information for representing the work ID registration screen to the worker terminal 6 (step S603). If the account ID 202 is not registered in advance, the issuing unit 21 does not authenticate the account ID 202 and transmits information indicating authentication failure to the worker terminal 6.

  In the worker terminal 6, when the communication unit 63 receives the work ID registration screen information, the control unit 62 displays a work ID registration screen corresponding to the work ID registration screen information on the display unit 64 (step S604).

  FIG. 7 is a diagram illustrating an example of a work ID registration screen.

  In FIG. 7, an account ID 202 is displayed on a work ID registration screen 701, and an input field 702 for inputting a worker name 203 and an input field 703 for inputting a work target server identifier 204 are provided. ing.

  The account ID 202 may be input on the work ID registration screen 701.

  Further, when the issuing unit 21 has a database showing the correspondence between the account ID and the worker name, the issuing unit 21 reads the worker name 203 corresponding to the account ID 202 from the database, and the work The person name 203 may be placed on the work ID registration screen 701. In this case, the input field 702 is unnecessary.

In the worker terminal 6, when the input unit 61 accepts input to the input fields 702 and 703 by the worker, that is, input of the worker name 203 and the work target server identifier 204 (step S605), the control unit 62 Work ID registration information 201 including ID 202, worker name 203, and work target server identifier 204 is created, and work ID registration information 201 is transmitted to management server 2 using communication unit 63 (step S606).
When receiving the work ID registration information 201, the issuing unit 21 in the management server 2 notifies the approver terminal 3 that the work ID registration information 201 has arrived, and then sends the work ID registration information to the approver terminal 3. Approval screen information for representing an approval screen including 201 and an approval / non-approval selection column is transmitted (step S607).

  The approver terminal 3 may be determined in advance. Further, when the issuing unit 21 has a database indicating the correspondence between the account ID and the approver terminal, the issuing unit 21 refers to the database and identifies the approver terminal corresponding to the account ID 202. May be.

  Upon receiving the approval screen information, the approver terminal 3 displays an approval screen corresponding to the approval screen information.

  FIG. 8 is a diagram showing an example of an approval screen.

  In FIG. 8, the approval screen 801 includes work ID registration information 201 (account ID 202, worker name 203, and work target server identifier 204), and an approval presence / absence selection column 802.

  The approver operates the input unit (not shown) of the approver terminal 3 and inputs approval / disapproval in the approval / non-approval selection column 802. The approver terminal 3 performs an approval process (a process for specifying approval or no approval) according to the input of the approver (step S608).

  When the approver terminal 3 completes the approval process, the approver terminal 3 transmits the result of the approval process to the management server 2 (step S609).

  When receiving the approval process result (approval information) indicating approval from the approver terminal 3, the issuing unit 21 in the management server 2 issues a work ID 302 and transmits the work ID 302 to the worker terminal 6 (steps). S610).

  Subsequently, the issuing unit 21 creates the work ID registration confirmation information 301 by adding the approval date information 303 and the work ID 302 to the work ID registration information 201 (step S611).

  When creating the work ID registration confirmation information 301, the issuing unit 21 stores the work ID registration confirmation information 301 in the storage unit 22 (step S612).

  When the issue unit 21 stores the work ID registration confirmation information 301 in the storage unit 22, the issue unit 21 identifies the work target server 4 (hereinafter simply referred to as “work target server 4”) identified by the work target server identifier 204 in the work ID registration confirmation information 301. The work ID registration confirmation information 301 is transmitted (refer to step S613).

  In the work target server 4, when the communication unit 43 receives the work ID registration confirmation information 301 from the management server 2, the processing unit 44 stores the work ID registration confirmation information 301 in the storage unit 41 (step S614).

  When a communication failure occurs between the work target server 4 and the management server 2, the work ID registration confirmation information 301 transmitted to the work target server 4 is not received by the work target server 4. In this case, the processing unit 44 cannot store the work ID registration confirmation information 301 in the storage unit 41.

  In the first place, when a communication failure occurs between the worker terminal 6 and the management server 2, the management server 2 cannot receive the work ID registration information 201 transmitted from the worker terminal 6, or A situation occurs in which the worker terminal 6 cannot receive the work ID 302 transmitted from the management server 2. In this case, the worker cannot obtain the work ID 302. In this case, since the management server 2 does not create the work ID registration confirmation information 301, the processing unit 44 in the work target server 4 cannot store the work ID registration confirmation information 301 in the storage unit 41.

  In the worker terminal 6, when the input unit 61 receives an instruction to connect to the work target server 4 after the communication unit 63 receives the work ID 302, the control unit 62 uses the communication unit 63 to perform the work target server. 4, the account ID 202 and authentication key information are transmitted to the work target server 4.

  In the work target server 4, when the communication unit 43 receives the account ID 202 and the key information for authentication, the grant unit 45 performs an authentication process using the account ID 202 and the key information for authentication.

  When the granting unit 45 authenticates the worker terminal 6 by the authentication process using the account ID 202 and the key information for authentication, the control unit 62 in the worker terminal 6 has a general authority (an authority without privileges). The user logs in to the work target server 4 and transmits a privilege acquisition request to the work target server 4 (step S615).

  In the work target server 4, when the communication unit 43 receives the privilege acquisition request, the grant unit 45 transmits privilege acquisition screen information representing the privilege acquisition screen to the worker terminal 6 (step S616).

  In the worker terminal 6, when the communication unit 63 receives the privilege acquisition screen information, the control unit 62 displays a privilege acquisition screen corresponding to the privilege acquisition screen information on the display unit 64 (step S617).

  FIG. 9 is a diagram showing an example of the privilege acquisition screen.

  In FIG. 9, the privilege acquisition screen 901 includes a work information (work ID) input field 902 and an operator name input field 903.

  When the input unit 61 accepts input to the input fields 902 and 903 by the worker, that is, input of the work information 402 and the worker name 203, the control unit 62 performs the account ID 202, the worker name 203, and the work information 402. Is created, and the work ID information 401 is transmitted to the work target server 4 using the communication unit 63 (step S618).

  The control unit 62 may add the authentication password held in the control unit 62 to the work ID information 401.

  When the communication unit 43 receives the work ID information 401, the granting unit 45 of the work target server 4 corresponds to the privilege to the account ID 202 that is the same as the account ID 202 in the work ID information 401 among the account IDs in the storage unit 41. By giving the flag to do, the privilege is given to the worker terminal 6 (worker) (step S619).

  When a password for authentication is added to the work ID information 401, the granting unit 45 performs an authentication process using the password for authentication and authenticates the worker terminal 6, and then the worker terminal 6 (worker ).

  Subsequently, the control unit 46 of the work target server 4 determines the work ID information 401 (see FIG. 4) received by the communication unit 43 and the work ID registration confirmation information 301 (see FIG. 3) in the storage unit 41. The names are compared, and the work ID is compared with the work information (step S620).

  Subsequently, the control unit 46 creates privilege grant information 501 based on the comparison result (step S621).

  In this embodiment, the worker name 203 in the work ID information 401 matches the worker name 203 in the work ID registration confirmation information 301, and the work information 402 in the work ID information 401 is the work ID registration confirmation information. If it matches the work ID 302 in 301, the control unit 46 gives the account ID 202, worker name 203 and work information 402 in the work ID information 401, and the date and time when the granting unit 45 grants privileges according to the work ID information 401. Privilege acquisition information 501 including privilege acquisition date / time information 502 indicating status information 503 indicating normality is created.

  On the other hand, the worker name 203 in the work ID information 401 is not in the work ID registration confirmation information 301, the same information as the work information 402 in the work ID information 401 is not in the work ID registration confirmation information 301, and When the work information 402 in the work ID information 401 is a special case ID, the control unit 46 determines the account ID 202, the worker name 203 and the work information 402 in the work ID information 401, the privilege acquisition date / time information 502, and the special case. And privilege grant information 501 including state information 503 representing the This situation occurs, for example, when a failure occurs in the management server 2.

  On the other hand, the worker name 203 in the work ID information 401 is not in the work ID registration confirmation information 301, the same information as the work information 402 in the work ID information 401 is not in the work ID registration confirmation information 301, and If the work information 402 in the work ID information 401 is not a special case ID, the control unit 46 displays the account ID 202, the worker name 203 and the work information 402 in the work ID information 401, the privilege acquisition date / time information 502, and the delay. Privilege grant information 501 including state information 503 to be created is created. This situation occurs, for example, when transmission of the work ID registration confirmation information 301 from the management server 2 to the work target server 4 fails.

  When creating the privilege grant information 501, the control unit 46 stores the privilege grant information 501 in the storage unit 42 (step S622).

  In the worker terminal 6, when the input unit 61 receives an instruction from the worker for a work that requires privilege (hereinafter referred to as “privileged work”), the control unit 62 passes through the communication unit 63 according to the instruction. The privileged work is performed on the work target server 4 (step S623).

  In the work target server 4, when the privileged work is performed at the worker terminal 6 (worker) to which the privilege is granted, the control unit 46 stores the privileged work log in the storage unit 42 in association with the account ID 202. (Step S624).

  On the other hand, the issuing unit 21 in the management server 2 transmits a privilege grant information request for requesting the privilege grant information 501 to each work target server 4 at predetermined time intervals (step S625).

  In each work target server 4, when the communication unit 43 receives the privilege grant information request, the control unit 46 adds the work target server identifier 204 for identifying the own server to the privilege grant information 501 in the storage unit 42. The privilege grant information 501 to which the target server identifier 204 is added is transmitted to the management server 2 (step S626).

  Here, even if there is no privilege grant information request, the control unit 46 in the work target server 4 displays the privilege grant information 501 to which the task target server identifier 204 for identifying the own server is added every predetermined time. 2 may be transmitted.

  Upon receiving the privilege grant information 501 to which the work target server identifier 204 is added, the issuing unit 21 in the management server 2 stores the privilege grant information 501 to which the work target server identifier 204 is added in the storage unit 22 (Step S627). ).

  Upon receipt of an audit instruction from the auditor, the audit unit 51 in the audit terminal 5 connects to the management server 2 and reads the privilege grant information 501 to which the work target server identifier 204 is added in the storage unit 22 (step S628). ).

  When reading the privilege grant information 501 to which the work target server identifier 204 is added, the audit unit 51 outputs the audit information based on the privilege grant information 501 (step S629).

  In this embodiment, when the status information 503 in the privilege grant information 501 to which the work target server identifier 204 is added represents normal, the audit unit 51 outputs audited information indicating audited to the display unit 52. When receiving the audited information, the display unit 52 displays an image indicating audited.

  On the other hand, when the status information 503 in the privilege grant information 501 to which the work target server identifier 204 is added represents a special case, the auditing unit 51 uses the privilege grant information 501 as confirmation required information indicating that the work content needs to be confirmed. Are displayed on the display unit 52.

  Subsequently, the auditing unit 51 logs the privileged work associated with the account ID 202 in the privilege grant information 501 with respect to the work target server 4 specified by the work target server identifier 204 added to the privilege grant information 501. Is transmitted (hereinafter referred to as “transmission request”).

  Upon receiving the transmission request, the work target server 4 reads the privileged work log requested by the transmission request from the storage unit 42 and transmits the privileged work log to the monitoring terminal 5.

  In the monitoring terminal 5, upon receiving the privileged work log, the auditing unit 51 displays the privileged work log on the display unit 52. For this reason, it becomes possible to easily confirm the privilege content performed by the worker who has acquired the privilege using the special case ID.

  Further, when the status information 503 in the privilege grant information 501 to which the work target server identifier 204 is added represents a delay, the auditing unit 51 stores the worker in the privilege grant information 501 in the storage unit 22 in the management server 2. Work ID registration confirmation information 301 (hereinafter referred to as “corresponding work ID”) including name 203 and approval date / time information 303 indicating the date / time included in the specified period before the date / time indicated by the privilege acquisition date / time information 502 in the privilege grant information 501. The registration confirmation information ”is present, and the confirmation result is displayed on the display unit 52.

  Here, the auditing unit 51 outputs the audited information to the display unit 52 when the corresponding work ID registration confirmation information exists. When receiving the audited information, the display unit 52 displays an image indicating audited.

  On the other hand, when the corresponding work ID registration confirmation information does not exist, the auditing unit 51 displays the worker name 203 in the privilege granting information 501 on the display unit 52 as confirmation necessary information indicating that the work content needs to be confirmed.

  Subsequently, the auditing unit 51 transmits a transmission request to the work target server 4 specified by the work target server identifier 204 added to the privilege grant information 501.

  When receiving the transmission request, the work target server 4 transmits the privileged work log requested by the transmission request to the monitoring terminal 5.

  In the monitoring terminal 5, upon receiving the privileged work log, the auditing unit 51 displays the privileged work log on the display unit 52. For this reason, it becomes possible to easily confirm the contents of the privileged work performed by the worker who has acquired the privilege using the work information that is not stored in the storage unit 41 as well as the special ID.

  In the above embodiment, the account ID may also serve as the worker name, or the worker name may concurrently serve as the account ID.

  According to the present embodiment, when receiving the work ID registration information 201 (work application) from the worker terminal 6, the issuing unit 21 transmits the work ID (identification information) to the worker terminal 6, and the work The work ID registration confirmation information 301 including the ID is transmitted to the work target server 4.

  When the communication unit 43 receives the work ID registration confirmation information 301 from the management server 2, the processing unit 44 stores the work ID registration confirmation information 301 in the storage unit 41.

  When the communication unit 43 receives the work ID information 401 (work request) from the worker terminal 6, the grant unit 45 grants the privilege to the worker terminal 6 (worker).

  For this reason, even in a situation where the worker terminal 6 cannot obtain the task ID 302 from the management server 2, it is possible to grant privileges to the worker terminal 6 (worker). Therefore, it is possible to solve the problem that the privilege cannot be acquired.

  When the work information 402 in the work ID information 401 matches the work ID 302 in the storage unit 41, that is, when the work information 402 represents the work ID 302, the control unit 46 Information 402 is stored in the storage unit 42 in association with state information indicating normality.

  In addition, the control unit 46 does not have the same information as the work information 402 in the work ID information 401 in the storage unit 41 and the work information 402 matches the special case ID, that is, the work When the work information 402 represents a special case ID, the work information 402 is stored in the storage unit 42 in association with the state information representing the special case.

  Further, when the same information as the work information 402 in the work ID information 401 does not exist in the storage unit 41 and the work information 402 is different from the special case ID, the control unit 46, for example, When the work information 402 represents the work ID 302 but the work ID 302 is not yet stored in the storage unit 41, the work information 402 is stored in the storage unit 42 in association with the state information representing the delay.

  For this reason, based on the state information associated with the work information 402, it is possible to determine the situation when the privilege is acquired. Therefore, auditing according to the situation when the privilege is acquired can be performed, and auditing can be facilitated.

  Therefore, according to the present embodiment, it is possible to minimize the influence of a system failure, and privilege acquisition itself from the work target server 4 is possible, so that privileged work can be efficiently audited. become.

  In the present embodiment, the auditing unit 51 determines whether the state information 503 associated with the work information 402 stored in the storage unit 42 in the work target server 4 is state information indicating normality or state information indicating a special case, Check if the status information indicates a delay. The audit unit 51 outputs audit information corresponding to the confirmation result.

  In this case, the audit information becomes information indicating a situation when the privilege is acquired, and the audit can be facilitated by using the audit information.

  In the present embodiment, when the work information 402 in the storage unit 42 is associated with state information indicating normality, the auditing unit 51 outputs audited information indicating audited as audit information.

  Further, when the work information 402 in the storage unit 42 is associated with state information indicating a special case, the audit unit 51 outputs confirmation necessary information indicating that the work content needs to be confirmed as audit information.

  In addition, when the work information 402 in the storage unit 42 is associated with state information indicating delay, the auditing unit 51 indicates the date and time indicated by the approval date and time information 203 stored in the storage unit 22 in the management server 2. And the date and time indicated by the privilege acquisition date and time information 502 stored in the storage unit 42 in the work target server 4 are compared.

  When the date / time indicated by the approval date / time information 203 is earlier than the date / time indicated by the privilege acquisition date / time information 502, the auditing unit 51 outputs audited information as audit information.

  On the other hand, when the date / time indicated by the approval date / time information 203 is not earlier than the date / time indicated by the privilege acquisition date / time information 502, confirmation necessary information is output as audit information.

  For this reason, the auditing unit 51 can specify work that needs to be audited. For this reason, it becomes possible to make auditing easy.

  In the embodiment described above, the illustrated configuration is merely an example, and the present invention is not limited to the configuration.

  For example, the audit terminal 5 may be included in the management server 2. Further, the audit terminal 5 may acquire the privilege grant information 501 directly from each work target server 4.

DESCRIPTION OF SYMBOLS 1 Privilege management system 2 Management server 21 Issuing part 22 Storage part 3 Approver terminal 4 Work object server 41 Storage part 42 Storage part 43 Communication part 44 Processing part 45 Giving part 46 Control part 5 Audit terminal 51 Auditing part 52 Display part

Claims (6)

A privilege management system including a predetermined server capable of communicating with a worker terminal, and a management server capable of communicating with the worker terminal and the predetermined server,
The management server transmits identification information corresponding to the application to the worker terminal when receiving an application from the worker terminal for performing a predetermined task requiring privilege to the predetermined server. And issuing means for transmitting the identification information to the predetermined server,
The predetermined server is:
First storage means;
A second storage means;
Communication means for communicating with the management server and the worker terminal;
When the communication unit receives the identification information from the management server, the processing unit stores the identification information in the first storage unit;
When the communication means receives a request to acquire the privilege including work information from the worker terminal, a granting means for granting the privilege to the worker terminal;
When the work information matches the identification information in the first storage means, the work information is stored in the second storage means in association with the first information for audit identification, and the work information and If the same information does not exist in the first storage means and the work information matches predetermined information different from the identification information, the work information is for audit identification different from the first information. If the same information as the work information does not exist in the first storage means and the work information is different from the predetermined information, the second information is stored in the second storage means. And a control means for storing the work information in the second storage means in association with third information for audit identification different from the first information and the second information. The privilege management system according to claim 1,
Audit means for confirming whether the information associated with the work information in the second storage means is the first information, the second information, or the third information, and outputting audit information according to the result of the confirmation A privilege management system further including an audit terminal including: In the privilege management system according to claim 2,
The management server includes third storage means,
The issuing means stores, in the third storage means, a first timing included in a period from the time when the application is received to the time when the identification information is transmitted to the worker terminal,
The control means stores, in the second storage means, a second timing that is a time when the grant means grants the privilege,
The audit means includes
When the work information in the second storage means is associated with the first information, the audited information indicating audited is output as the audit information,
When the work information in the second storage means is associated with the second information, as the audit information, confirmation information indicating that the work content needs to be confirmed is output,
When the work information in the second storage means is associated with the third information, when the first timing is before the second timing, the audited information is used as the audit information. A privilege management system that outputs and outputs the confirmation necessary information as the audit information when the first timing is not earlier than the second timing. A privilege management method in a privilege management system including a predetermined server capable of communicating with an operator terminal, and a management server capable of communicating with the worker terminal and the predetermined server,
When the management server receives, from the worker terminal, an application for performing a predetermined task requiring privilege on the predetermined server, the identification information corresponding to the request is transmitted to the worker terminal. And an issuing step of transmitting the identification information to the predetermined server;
When the predetermined server receives the identification information from the management server, a processing step of storing the identification information in a first storage unit;
When the predetermined server receives a request to acquire the privilege including work information from the worker terminal, an granting step of granting the privilege to the worker terminal;
The predetermined server stores the work information in the second storage means in association with the first information for audit identification when the work information matches the identification information in the first storage means, If the same information as the work information does not exist in the first storage means and the work information matches the predetermined information different from the identification information, the work information is referred to as the first information. The second storage means is associated with different audit identification second information, the same information as the work information does not exist in the first storage means, and the work information is the predetermined information. A control step of storing the work information in the second storage means in association with the third information for audit identification different from the first information and the second information, if different. In the privilege management method according to claim 4,
The privilege management system further includes an audit terminal,
The audit terminal confirms whether the information associated with the work information in the second storage means is the first information, the second information, or the third information, and the audit information according to the result of the confirmation A privilege management method, further comprising an auditing step for outputting. In the privilege management method according to claim 5,
In the issuing step, a first timing included in a period from a time when the application is received to a time when the identification information is transmitted to the worker terminal is stored in a third storage unit;
In the control step, a second timing that is a point in time when the privilege is granted is stored in the second storage means,
In the audit step,
When the work information in the second storage means is associated with the first information, the audited information indicating audited is output as the audit information,
When the work information in the second storage means is associated with the second information, as the audit information, confirmation information indicating that the work content needs to be confirmed is output,
When the work information in the second storage means is associated with the third information, when the first timing is before the second timing, the audited information is used as the audit information. A privilege management method for outputting the confirmation necessary information as the audit information when the first timing is not earlier than the second timing.

Images