JP4812456B2 - Password management method, password management system, and password management program - Google Patents

Description

  The present invention relates to a password management method, a password management system, and a password management program, and more particularly to a password management method, a password management system, and a password management program for managing privileged passwords.

  In order to manage the computer system, privileges are given to the system administrator. As a result, the administrator can take all measures necessary for system operation, but if you turn it back, the administrator will leave the computer system security, operational stability, and safety decisions unrestrictedly and unconditionally, Safety and security depended on managers' individual skills and insights.

  Therefore, it is necessary to manage the password of privileged users with a plurality of members, and to make the enforcement of the privilege a controversial system and stop it.

  An access right management system has been proposed that permits access when a plurality of users who have access rights request access in order to suppress the sole use of privileges (see Patent Document 1).

Also, an authority transfer system has been proposed in which a score is assigned to an administrator and an access right is given by transferring the score (see Patent Document 2).
JP 2005-293004 A JP 2002-328907 A

  However, since the conventional system is not based on password management, it is necessary to construct an access right management system in addition to widely used password authentication.

  Moreover, even if the method is based on a score or the like, the process of assigning the score has to be performed in advance, and the operability is poor.

  The present invention has been made in view of the above points, and can be easily applied to a conventional password authentication system. A password management method capable of exercising privileges without sacrificing safety or security by a simple operation, Another object of the present invention is to provide a password management system and a password management program.

  The present invention provides a password management method for managing passwords, wherein the password is configured by combining a plurality of divided passwords in a predetermined connection order, and manages the plurality of divided passwords and the connection order in association with a plurality of users. It is characterized by that.

  Further, the present invention is characterized in that a plurality of divided passwords and a connection order are automatically updated and notified to the plurality of users.

  The automatic update is performed when the user logs in.

  According to the present invention, since the password is divided into a plurality of divided passwords and managed by a plurality of members, it is necessary to agree on the plurality of members in order to exercise the privileges, so that the privileges depend on individual morals. There is no. In addition, the safety at the time of failure will be improved because multiple people will consider and agree to deal with it.

〔System configuration〕
FIG. 1 shows a system configuration diagram of an embodiment of the present invention.

  The computer system 100 of the present embodiment is configured such that user terminal devices 111-1 to 111 -m and a server 112 are communicably connected via a network 113.

  The user terminal devices 111-1 to 111 -m are configured from computers, and are terminal devices used by users who use the server 112. The user ID and password required for login from the terminal device are managed by the server 112.

  FIG. 2 shows a block diagram of the server 112.

  The server 112 includes a communication unit 121, a processing unit 122, a system file unit 123, a password management file unit 124, and a user file unit 125.

  The communication unit 121 communicates with the user terminal devices 111-1 to 111 -m via the network 113.

  The processing unit 122 manages the system by the system program stored in the system file unit 123 and controls access to the user file unit 125. Further, the processing unit 122 performs access control to the system file unit 123 and the user file unit 125 based on the password management program 131 stored in the password management file unit 124 and the database stored in the password management database unit 132. Yes.

[Password management database 132]
FIG. 3 shows a data configuration diagram of the password management database unit 132.

  The password management database unit 132 includes a management ID registration file 141, a divided password management file 142, and a password management file 143.

[Management ID registration file 141]
FIG. 4 shows a data configuration diagram of the management ID registration file 141.

  The management ID registration file 141 includes a management target ID storage unit 151 and a management member list storage unit 152.

  The management target ID storage unit 151 stores user IDs to be managed by a plurality of people among the user IDs managed by the password management file 143. The management member list storage unit 152 stores user IDs of members who have passwords obtained by dividing the passwords of the management target IDs.

  FIG. 4 shows that the users ID User11 and User12 belong to the members of the management target ID Root, and the users ID User21, User22, and User23 belong to the members of the management target IDSys. Note that the same user ID may be included in the management member list of different management target IDs.

  By referring to the management ID registration file 141, it is possible to recognize the management target ID managed by dividing the password and to recognize the manager.

[Split password management file 142]
FIG. 5 shows a data configuration diagram of the divided password management file 142.

  The management target ID storage unit 161, the user ID storage unit 162, the next password storage unit 163, and the connection order storage unit 164 are configured.

  The management target ID storage unit 161 stores user IDs to be managed by a plurality of people. The user ID storage unit 162 stores user IDs of members who manage the management target ID. The next password storage unit 163 stores a divided password to be applied to the management target ID next time for each management member. The concatenation order storage unit 164 stores the concatenation order of the divided passwords to be applied next time. The connection order may be determined and set in a fixed order in advance, or may be reset every time the password of the management target ID is updated.

  In FIG. 5, the user ID User 11 is the first management member of the management target ID Root, the divided password to be applied next time is “Abc1”, and the concatenation order is the first. The user of IDUser12 is the second management member of the management target IDRoot, the divided password to be applied next time is “23% &”, and the connection order is the second.

  In addition, the user ID User 21 is the first management member of the management target ID Sys, the divided password to be applied next time is “# a3B”, and the concatenation order is second, indicating that the user ID User 22 The user is the second management member of the management target IDSys, the divided password to be applied next time is “58Hu”, the connection order is No. 1, and the user of the user ID User23 is the third management member of the management target IDSys. The divided password to be applied next time is “A! Qq”, and the connection order is No. 3.

  By referring to the divided password management file 142, it is possible to recognize the next divided password corresponding to each management target ID and its connection order.

  Since the management target ID can be identified by the divided password management file 142, the management member list storage unit 152 of the management ID registration file 141 can be omitted.

[Password management file 143]
FIG. 6 shows a data configuration diagram of the password management file 143.

  The password management file 143 includes an ID storage unit 171, a password storage unit 172, and an update time limit storage unit 173.

  The ID storage unit 171 stores a user ID.

  The password storage unit 172 stores a password set corresponding to the user ID stored in the ID storage unit 171. The update time limit storage unit 173 stores the update time limit of the password stored in the password storage unit 172.

  FIG. 6 shows that the password of the user ID Root is “Abc123% &” and the update deadline is December 1, 2005, and the password of the user IDSys is “58Hu # a3BA! Qq”. This indicates that the update deadline is December 1, 2005.

  In this embodiment, the validity period of the password is managed by the renewal deadline, but it may be managed by the validity period after it is issued.

  FIG. 7 shows a data configuration diagram of a modified example of the password management file 143.

  The password management file 151 includes an ID storage unit 181, a password storage unit 182, an update time storage unit 183, and an effective period storage unit 184.

  The ID storage unit 181 stores a user ID.

  The password storage unit 182 stores a password set corresponding to the user ID stored in the ID storage unit 181. The update time storage unit 183 stores the time when the password stored in the password storage unit 172 was last updated, and the validity period storage unit 184 stores the validity period of the password stored in the password storage unit 182. Stored.

  In FIG. 7, the password of the user ID Root is “Abc123% &”, and its valid period is one month from the last update time November 1, 2005, and the password of the user ID Sys is “ 58Hu # a3BA! Qq ", which indicates that the valid period is one month from the last update time November 1, 2005.

[Password management program]
Next, the processing operation of the password management program will be described.

  FIG. 8 shows a process flowchart of the password management program. The program is periodically executed in the server 112, for example, once an hour.

  The processing unit 122 sequentially selects users who are currently logged in to the server 112 in step S1-1, and performs split password acquisition processing in step S1-3 until all the users logged in in step S1-2 are processed. Execute for the selected user. When the split password acquisition process is executed for all the users who are logged in at step S1-2, the processing unit 122 executes a process of updating the password at step S1-4 based on the acquired password.

  FIG. 9 shows a processing flowchart of another example of the password management program. The program is executed on the server 112 for the user every time the user logs in.

  FIG. 9 shows a password management program when the password management file 151 shown in FIG. 7 is used. In step S1-11, the divided password acquisition process is executed for the target user, and the password acquired in step S1-2 is updated. To do.

  Next, the divided password acquisition process in steps S1-3 and S1-11 will be described.

  FIG. 10 shows a process flowchart of the split password acquisition process.

  When the processing unit 122 acquires the user ID passed from the calling side in step S2-1, the processing unit 122 performs member registration confirmation processing in step S2-2, and searches each record of the divided password management file 142 that matches the user ID. Then, the management target ID is acquired. In step S2-3, the management target IDs are sequentially selected.

  In step S2-4, if there is a management target ID selected by the sequential selection process, the processing unit 122 determines that the user with the user ID passed from the caller is a management member of the management target ID, and manages the management target ID. If there is no target ID, it is determined that all selection processes have been completed, the process is terminated, and control is returned to the caller. If it is confirmed that the user is a management member, the divided password management file 142 is referred to in step S2-5 to confirm the presence or absence of the next divided password, and the record having the management target ID and the user ID is checked. Check whether the password is stored next time. If it is determined in step S2-5 that the next split password has not been input in step S2-6, the processing unit 122 requests the next split password to be input in step S2-7. As a result, a process of displaying the input request screen on the user terminal device to which the target user is logged in and waiting for the user's input is executed.

  When there is a password input from the selected user of the user terminal devices 111-1 to 111 -m in step S 2-8, the processing unit 122 divides the concatenation order of the input passwords in step S 2-9 to manage divided passwords. Acquired from the corresponding record of the file 142, stores the password in the record and saves it in the divided password management file 142, notifies the corresponding user terminal device of the connection order, and returns to step S2-3. The same processing is performed for the management target ID. If the connection order is a fixed order, notification of the connection order to the user terminal device may be omitted.

  If there is no password input in step S2-8, the processing unit 122 returns to step S2-3 as it is.

  As described above, the split password is determined. At this time, the split password may remain as it is without being determined.

[Password update process]
Next, the password update process in steps S1-4 and S1-12 will be described.

  FIG. 11 shows a process flowchart of the password update process.

  The processing unit 122 sequentially reads records from the management ID registration file 141 in step S3-1 to acquire the management target ID, and determines whether the management target ID is acquired in step S3-2. If it is determined in step S3-2 that the management target ID has been acquired, the processing unit 122 acquires the current time in step S3-3, and the corresponding ID record in the password management file 143 in step S3-4. In step S3-5, it is determined whether or not the password has expired with reference to the password expiration date or validity period. If it is determined in step S3-2 that the management target ID has not been acquired, it is determined that all the records in the management ID registration file have been processed, the process ends, and control is returned to the caller.

  If the password has expired in step S3-5, the processing unit 122 sequentially reads records from the divided password management file 142 in steps S3-6 and S3-7. At that time, only the record having the management target ID acquired in step S3-1 is read. As a result, if it is determined in step S3-7 that it is EOD (End Of Data), the process proceeds to step S3-8, and in the same order as stored in step S3-13, which will be described later, in the same order as step S3-13 A new password is synthesized by concatenating the divided passwords stored in (1). The processing unit 122 registers the new password synthesized in step S3-9 as the password of the record whose ID in the password management file 143 matches the management target ID, and sets the update deadline of the record. The update deadline may be set, for example, as a fixed time after one month, or may be set based on information on the validity period in the data configuration shown in FIG.

  For example, in FIG. 5, the password “Abc123% &” obtained by concatenating the divided password “Abc1” of the concatenation order “1” of the management target IDRoot and the divided password “23% &” of the concatenation order “2” in the order of the concatenation order. 6 is registered as the IDRoot password in No. 6, and the update deadline is set, for example, on January 1, 2006.

  Next, the process part 122 resets the next password acquired by the said password update process of the division | segmentation password management file 142 at step S3-10, and resets a connection order. For example, in FIG. 5, the divided password “Abc1” and the divided password “23% &” of the management target IDRoot are reset, and the connection order “1” and “2” are recalculated and set, for example, “2” and “1” "Is set. The connection order may be a fixed order at all times, and in that case, the connection order may not be reset.

  Further, the processing unit 122 proceeds to step S3-11 when it is not EOD in step S3-7, refers to the next password and the concatenation order of the divided password management record read in step S3-6, and if the next password is empty. In step S3-12, a split password is automatically generated and stored as a pair with the connection order in step S3-13. If it is not empty, the next password and connection order pair are stored. Further, in step S3-13, the stored divided password and connection order are notified by e-mail or the like to the user of the user ID stored in the divided password management record. Note that the automatic generation of the divided password in step S3-12 is realized by, for example, a process of cutting an arbitrary part from an arbitrary random character string. In addition, in step S3-13, as a means for notifying the user of the divided password and the connection order, the divided password and the connection order are described in a file in which access permission authority is set only for the notification destination user, for example, You may store in the predetermined place of the user file part 125 of the server 112. FIG. In addition, when the connection order is a fixed order, it is good also as a process which does not notify a user of a connection order.

  As described above, the password can be divided and managed by a plurality of persons.

  Next, the operation at the time of accessing the system and the like will be described.

  When one of the management members becomes a privileged user when accessing the system, all the other management members are contacted, explained the reason, and given the split password and the connection order, and the system as a privileged user. Can be accessed.

〔effect〕
According to the password management program of the present embodiment, the password for the computer user ID can be divided into a plurality of pieces and managed in association with a predetermined plurality of users. As a result, the password is divided into a plurality of parts, and a plurality of persons manage a part of each, whereby password management that cannot be a privileged user alone can be performed. In other words, since the system cannot be accessed unless the password is obtained from a plurality of users, privilege abuse and unauthorized use can be suppressed.

  In addition, it is possible to automatically perform update management of passwords that are divided and managed for the associated users. Therefore, it can prevent using the same password continuously.

  Furthermore, a part or all of the divided and managed password can be automatically generated and notified to the associated user. The user can confirm the split password and its connection order.

  The associated user can specify a part of the update password to be divided and managed when using the computer. As a result, the divided password can be freely determined by the management member.

  As described above, according to the present embodiment, since the passwords of privileged users are managed by a plurality of persons, it is necessary to agree with a plurality of members in order to exercise the privileges, and it is possible to prevent depending on a particular individual's morals. . In addition, safety is improved because an emergency response is considered by multiple people and agreed.

[Others]
The password management tool program may be configured by only “password update processing”, and the partial password created by the system may be automatically notified to the management member.

It is a system configuration figure of one example of the present invention. 2 is a block configuration diagram of a server 112. FIG. 4 is a data configuration diagram of a password management database unit 132. FIG. 4 is a data configuration diagram of a management ID registration file 141. FIG. 6 is a data configuration diagram of a divided password management file 142. FIG. 4 is a data configuration diagram of a password management file 143. FIG. FIG. 10 is a data configuration diagram of a modified example of a password management file 143. It is a processing flowchart of a password management program. It is a process flowchart of another example of a password management program. It is a process flowchart of a division | segmentation password acquisition process. It is a process flowchart of a password update process.

Explanation of symbols

100 system 111-1 to 111 -m user terminal device 112 server, 113 network 121 communication unit, 122 processing unit, 123 system file unit 124 powered management file unit, 125 user file unit 131 password management program, 132 password management database unit 141 Management ID registration file, 142 Split password management file 143 Password management file

Claims (10)

A password management method in a password management system for managing a concatenated password formed by combining multiple members password of a predetermined connecting order,
The password management system is
A reading procedure for reading out the concatenated password, the update period of the concatenated password, and the next password for each of the plurality of members and the concatenation order of the next password from the storage means;
The next password acquisition procedure for acquiring the next password input by the member and storing it in the storage means;
When the renewal period of the concatenated password expires, the next password for the plurality of members and the concatenation order of the next password are acquired from the storage means, the next password is concatenated according to the concatenation order, Update the linked password to the linked password of
A linked password update procedure for resetting a next password of the plurality of members of the storage means, and resetting a linkage order of the next password;
Have
After the connection password is updated, login authentication is permitted when the new connection password is input,
Password management method characterized by. 2. The password management method according to claim 1 , further comprising a notification procedure for notifying the next password for each member to each of the plurality of members when the linked password is updated by the linked password update means. . When the member logs in, the password management method according to claim 1, characterized in that it comprises a request procedure for requesting an input of the next password update to the members. 2. The password management method according to claim 1, wherein the linked password update procedure automatically generates a next password that cannot be acquired when the next password for the plurality of members cannot be acquired from the storage unit . A password management system for managing a concatenated password by combining a plurality of member passwords in a predetermined concatenation order,
Storage means for storing the concatenated password and the update period of the concatenated password, and the next password for each of the plurality of members and the concatenation order of the next password;
Next time password acquisition means for acquiring the next password input by the member and storing it in the storage means;
When the renewal period of the concatenated password expires, the next password for the plurality of members and the concatenation order of the next password are acquired from the storage means, the next password is concatenated according to the concatenation order, Update the linked password to the linked password of
A linked password updating unit for resetting a next password of the plurality of members of the storage unit and resetting a coupling order of the next password ;
Have
After the connection password is updated, login authentication is permitted when the new connection password is input,
A password management system. 6. The password management system according to claim 5 , further comprising a notification means for notifying the next password for each member to each of the plurality of members when the linked password is updated by the linked password update means. . 6. The password management system according to claim 5 , wherein when the member logs in, the member is requested to input the next password update . The linked password update means automatically generates a next password that cannot be obtained when the next password for the plurality of members cannot be obtained from the storage means;
The password management system according to claim 5. On the computer,
Storage means for storing a concatenated password formed by combining passwords of a plurality of members in a predetermined concatenation order, an update deadline of the concatenated password, a next password for each of the plurality of members, and a concatenation order of the next password;
Next time password acquisition means for acquiring the next password input by the member and storing it in the storage means;
When the renewal period of the concatenated password expires, the next password for the plurality of members and the concatenation order of the next password are acquired from the storage means, the next password is concatenated according to the concatenation order, and the new Update the linked password to the linked password of
Reset the next password of the plurality of members of the storage means, and function as a connected password update means for resetting the next password connection order;
After the connection password is updated, login authentication is permitted when the new connection password is input,
Password management program characterized by On the computer,
10. The password management according to claim 9 , wherein when the linked password is updated by the linked password update unit , the password management unit functions as a notification unit that notifies the next password for each member to each of the plurality of members. program.

Images