CN107070881B - Key management method, system and user terminal - Google Patents
Key management method, system and user terminal Download PDFInfo
- Publication number
- CN107070881B CN107070881B CN201710091734.9A CN201710091734A CN107070881B CN 107070881 B CN107070881 B CN 107070881B CN 201710091734 A CN201710091734 A CN 201710091734A CN 107070881 B CN107070881 B CN 107070881B
- Authority
- CN
- China
- Prior art keywords
- key
- level
- terminal
- current
- subordinate
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/06—Network architectures or network communication protocols for network security for supporting key management in a packet data network
Landscapes
- Engineering & Computer Science (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Storage Device Security (AREA)
Abstract
The invention provides a key management method, a system and a user terminal, which relate to the technical field of information security and comprise the steps of obtaining a plurality of subordinate keys; encrypting each lower-level key by using the current-level key; and storing the encrypted lower-level key to a key manager. In addition, the present level key may also be saved to the key manager. The invention solves the problem of low security of the existing key keeping mode by using the method of encrypting and storing the lower-level key by using the current-level key.
Description
Technical Field
The present invention relates to the field of information security technologies, and in particular, to a method, a system, and a user terminal for managing a secret key.
Background
The key, i.e. the key, refers to various encryption technologies applied in production and life, and can effectively supervise the data of each person and the secret of an enterprise, and the key management refers to the actions of managing the key, such as encryption, decryption, cracking and the like. It is mainly represented by the management system, the generation, distribution, replacement and injection of management protocols and keys.
Employees at each level of a company own a system or cloud application authority, each corresponding employee has a key, and at present, each level of employee stores the key in a key storage system of the employee. The situation is easy to be attacked by an attacker, so that the attacker can easily acquire the key of the employee from the key storage system of the employee, and irreparable loss is caused to a company. Therefore, the conventional key keeping method has the problem of low security.
Disclosure of Invention
In view of the above, the present invention provides a key management method, a system and a user terminal, so as to solve the problem of low security in the existing key keeping method.
In a first aspect, an embodiment of the present invention provides a key management method, where the method includes:
acquiring a plurality of lower-level keys;
encrypting each lower-level key by using the current-level key;
and storing the encrypted lower-level key to a key manager.
With reference to the first aspect, an embodiment of the present invention provides a first possible implementation manner of the first aspect, where the key manager is configured to prohibit a network read right.
With reference to the first aspect, an embodiment of the present invention provides a second possible implementation manner of the first aspect, where the method further includes:
and storing the current-level key to the key manager.
With reference to the first aspect, an embodiment of the present invention provides a third possible implementation manner of the first aspect, where the method further includes:
and sending the key of the current level to a superior user terminal.
With reference to the first aspect, an embodiment of the present invention provides a fourth possible implementation manner of the first aspect, where the method further includes:
and storing the key of the current level to the key management device.
With reference to the fourth possible implementation manner of the first aspect, an embodiment of the present invention provides a fifth possible implementation manner of the first aspect, where the storing the current-level key to the key management device specifically includes:
splitting the key of the current level into at least two key fragments according to a certain splitting rule;
and storing the at least two key fragments in at least two key management devices respectively.
With reference to the first aspect, an embodiment of the present invention provides a sixth possible implementation manner of the first aspect, where the method further includes:
receiving a key acquisition request from a subordinate user terminal;
judging whether the subordinate user terminal has corresponding authority;
if the subordinate user terminal has corresponding authority, sending a corresponding key to the subordinate user terminal;
and if the subordinate user terminal does not have the corresponding authority, not sending the corresponding key.
In a second aspect, an embodiment of the present invention further provides a user terminal, including:
an obtaining module, configured to obtain a plurality of lower-level keys;
the encryption module is used for encrypting each lower-level key by using the current-level key;
and the communication module is used for storing the encrypted lower-level key to the key manager.
With reference to the second aspect, an embodiment of the present invention provides a first possible implementation manner of the second aspect, where the communication module is further configured to store the current-level key to the key manager.
With reference to the second aspect, an embodiment of the present invention provides a second possible implementation manner of the second aspect, where the key manager is provided with a network read prohibition authority.
With reference to the second aspect, an embodiment of the present invention provides a third possible implementation manner of the second aspect, where the user terminal further includes:
the splitting module is used for splitting the current-level key into at least two key fragments according to a certain splitting rule;
the communication module is further configured to store the at least two key fragments in at least two key management devices, respectively.
With reference to the second aspect, an embodiment of the present invention provides a fourth possible implementation manner of the second aspect, where the user terminal further includes:
the receiving and sending module is used for receiving a key acquisition request from a subordinate user terminal;
the judging module is used for judging whether the subordinate user terminal has corresponding authority;
if the subordinate user terminal has corresponding authority, the transceiver module sends a corresponding key to the subordinate user terminal;
and if the subordinate user terminal does not have the corresponding authority, not sending the corresponding key.
In a third aspect, an embodiment of the present invention further provides a key management system, where the system includes a plurality of user terminals as described in the second aspect.
With reference to the third aspect, an embodiment of the present invention provides a first possible implementation manner of the third aspect, where the system further includes a plurality of key management apparatuses, and each key management apparatus is communicatively connected to one or more user terminals.
The embodiment of the invention has the following beneficial effects: the invention provides a key management method, a system and a user terminal, which comprises the steps of obtaining a plurality of subordinate keys; encrypting each lower-level key by using the current-level key; and storing the encrypted lower-level key to a key manager. The invention uses the key to encrypt the lower key and stores the encrypted lower key, so that the attacker can obtain the lower key only after attacking the key, thereby solving the problem of low security of the existing key keeping mode.
Additional features and advantages of the invention will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. The objectives and other advantages of the invention will be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.
In order to make the aforementioned and other objects, features and advantages of the present invention comprehensible, preferred embodiments accompanied with figures are described in detail below.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and other drawings can be obtained by those skilled in the art without creative efforts.
Fig. 1 is a schematic flowchart of a key management method according to an embodiment of the present invention;
fig. 2 is a schematic diagram of a secondary user terminal according to an embodiment of the present invention;
fig. 3 is a schematic diagram of a three-level user terminal situation provided in an embodiment of the present invention;
fig. 4 is a schematic diagram of key cloud storage according to an embodiment of the present invention;
FIG. 5 is a flowchart illustrating a first manner of storing the current-level key in the key management device according to the embodiment of the present invention;
fig. 6 is a schematic diagram of multi-cloud storage of a secret key according to an embodiment of the present invention;
FIG. 7 is a diagram of a key splitting storage according to an embodiment of the present invention;
FIG. 8 is a flowchart illustrating a second manner of storing the current-level key in the key management device according to the embodiment of the present invention;
fig. 9 is a schematic structural diagram of a user terminal according to an embodiment of the present invention;
fig. 10 is a schematic structural diagram of a key management system according to an embodiment of the present invention.
Detailed Description
To make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings, and it is apparent that the described embodiments are some, but not all embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
At present, every level of staff of a company stores a key in a key keeping system of the company, and the key keeping mode has the problem of low security. Based on this, the key management method, the system and the user terminal provided in the embodiments of the present invention can solve the problem of low security in the existing key keeping manner by using the method of encrypting and storing the lower-level key by using the current-level key.
For the convenience of understanding the present embodiment, a detailed description will be given to a key management method disclosed in the present embodiment.
The first embodiment is as follows:
fig. 1 shows a flowchart of a key management method according to an embodiment of the present invention. As shown in fig. 1, the method includes:
step S11, acquiring a plurality of lower keys;
step S12, using the key of the current level to encrypt each lower-level key;
in step S13, the encrypted lower key is stored in the key manager.
Specifically, the method provided by the embodiment of the present invention is applicable to a multi-level user terminal, and according to the administrative level, the multi-level user terminal may be an employee user terminal, a department manager user terminal, and a general manager user terminal, which are hereinafter referred to as an employee terminal, a department manager terminal, and a general manager terminal. Taking fig. 2 and fig. 3 as examples, fig. 2 shows a schematic diagram of a secondary user terminal situation provided by the embodiment of the present invention, and fig. 3 shows a schematic diagram of a tertiary user terminal situation provided by the embodiment of the present invention.
As shown in fig. 2, the department manager 1 serves as a local terminal, obtains two lower-level keys, namely, keys of the employee 1 and the employee 2, encrypts the keys of the employee 1 and the employee 2 by using the local key of the department manager 1, and stores the encrypted two lower-level keys, namely, the keys of the employee 1 and the employee 2, in a key manager of the department manager 1, wherein the key manager is a local storage. In addition, the department manager 1 can also store the key of the current level to the key manager, so that the key of the current level is protected.
As a preferred solution, the key manager is provided with a network read disable right. That is, in the case of accessing the key manager simply through a network, the key stored therein cannot be read. But must be read by specific local operations, such as insertion of a U-shield, fingerprint unlocking, etc., to read the key stored therein, and also only in a local manner. By setting the permission of forbidding network reading, the key in the key manager can be prevented from being stolen when the user terminal is attacked by the network, thereby improving the security of key management.
As shown in fig. 3, the key storage method of the department manager 2 as the current-level terminal is the same as the key storage method of the middle-level door manager 1 as the current-level terminal in fig. 2, and the key of the lower-level employee 3 corresponding to the current-level door manager is obtained, stored by applying the current-level key, and stored in the current-level key manager. When the head manager serves as a local terminal, two lower-level keys, namely keys of a department manager 1 and a department manager 2, are obtained, the local keys of the local terminal, namely the head manager, are used for encrypting the keys of the head manager 1 and the head manager 2, and the encrypted keys of the head manager 1 and the head manager 2 are stored in a key manager of the head manager.
Furthermore, the key management method for the situation of the user terminal with four or more levels is obtained by analogy in sequence.
In summary, the present invention provides a key management method, including obtaining a plurality of lower-level keys; encrypting each lower-level key by using the current-level key; and storing the encrypted lower-level key to a local key manager. The invention solves the problem of low security of the existing key keeping mode by using the method of encrypting and storing the lower-level key by using the current-level key.
Further, in one implementation, in order to enhance the security effect, as shown in fig. 1, the method further includes the following steps:
in step S14, the present-level key is transmitted to the upper-level user terminal.
Specifically, taking fig. 2 or fig. 3 as an example, the employee 1 side and the employee 2 side send the local-level key to the department manager 1 side, the employee 3 side sends the local-level key to the department manager 2 side, and the department manager 1 side encrypts the keys of the employee 1 side and the employee 2 side by using the local-level key and then sends the local-level key to the general manager side. And the department manager 2 encrypts the key of the employee 3 by using the key of the current level and sends the key of the current level to the general manager. Preferably, the key of the employee side can be encrypted by the key of the corresponding department manager side and then automatically uploaded to the key manager corresponding to the department manager side when the superior level of the employee, namely the department manager, logs in the system or the cloud. When a general manager logs in the cloud disk or the system, the keys of the subordinate managers, namely the multiple department managers, of the general manager are encrypted through the keys of the general manager and then automatically uploaded to the key manager of the general manager. Therefore, only when the lower stage is fully registered, the key of the lower stage can be submitted to the upper stage by stage.
Further, considering that the local storage is vulnerable to the attack of the attacker, as shown in fig. 1, the method further includes the following steps:
in step S15, the present-level key is stored in the key management device.
Specifically, in an implementation manner, as shown in fig. 4, after obtaining all the keys, the manager stores the key of the current level to the key management device on the network side, and after obtaining all the keys of the staff in the department, the manager may also store the key of the current level to the key management device, where the key management device is a cloud storage.
Further, the number of the key management devices may be plural. The present-level key can be stored in the key management device in the following two ways.
As shown in fig. 5, the first method specifically includes:
and step S151, splitting the key of the current level into at least two key fragments according to a certain splitting rule.
The user terminal firstly obtains the name and address of at least two different key management devices from the cloud management system, or the user terminal (staff user terminal, department manager user terminal or general manager user terminal) directly accesses the at least two key management devices, and then the user terminal can cut and split a complete key into at least two parts according to a certain splitting rule, namely into at least two key fragments.
Step S152 stores the at least two key fragments in the at least two key management devices, respectively.
In this embodiment, the key fragments are stored in at least two different key management apparatuses according to the name addresses of the key management apparatuses, and are stored in the different key management apparatuses, for example, a part of keys are stored in the key management apparatus of the first service provider, and another part of keys are stored in the key management apparatus of the second service provider. The key is stored in different places by the above mechanism.
The key management device is a network system specially used for managing keys, and is higher in security than a common cloud storage.
S153: each key management device is connected and passes the identity authentication of each key management device.
When using the key, the user terminal connects to each key management device, inputs the authentication information of each key management device, and passes the identity authentication of each key management device.
S154: each key fragment is acquired from each key management apparatus, respectively.
Since the user terminal acquires the corresponding key fragment from each of the corresponding key management apparatuses, it is possible to acquire all of the plurality of key fragments from the plurality of key management apparatuses.
S155: and combining the acquired key fragments into a key according to the splitting rule.
After the user terminal acquires all the key fragments from each key management device, the acquired key fragments may be recombined into a complete key according to the splitting rule in step S151. Only when all the key fragments are taken, the complete key can be obtained, and the data in the key management device is unlocked by using the key.
For example, when the key is "10084567", the key may be split into "1008" and "4567" and stored in the key management apparatus 1 and the key management apparatus 2, respectively. In this way, the whole key can be obtained only after all the fragments are obtained through the identity authentication of the key management device 1 and the key management device 2, and the security of key storage is enhanced. As shown in fig. 6, the manager acquires all the keys and stores the keys of the current level in the key management apparatus 1 and the key management apparatus 2.
As shown in fig. 7, after the keys of the user terminals in each administrative level of the company are all split into multiple fragments, a part of the fragments may be stored in multiple key management devices, and the other fragments are stored in a manner of uploading step by step, that is, after a manager needs to log in all lower levels to obtain a part of the fragments, the manager accesses multiple key management devices to obtain the rest of the fragments, and finally obtains all the keys, thereby further enhancing the security of key storage.
As shown in fig. 8, a second way to store the current-level key to the key management device is specifically as follows:
step S161, according to a certain splitting rule, splits the current-level key into at least two key fragments.
The user terminal firstly obtains the name and address of at least two different key management devices from the cloud management system, or the user terminal (staff user terminal, department manager user terminal or general manager user terminal) directly accesses the at least two key management devices, and then the user terminal can cut and split a complete key into at least two parts according to a certain splitting rule, namely into at least two key fragments.
Step S162, storing at least two key fragments in at least two key management devices, respectively.
In this embodiment, the key fragments are stored in at least two different key management apparatuses according to the name addresses of the key management apparatuses, and are stored in the different key management apparatuses, for example, a part of keys are stored in the key management apparatus of the first service provider, and another part of keys are stored in the key management apparatus of the second service provider. The key is stored in different places by the above mechanism.
The cloud storage can be a network system specially used for managing keys, and is higher in security than ordinary cloud storage.
S163: and generating splitting and storing record information according to the splitting rule and the addresses of the at least two key management devices.
When the user terminal splits and stores according to the established rule, the splitting and storing record is automatically recorded, and then a splitting and storing record is generated according to the record.
S164: and storing the splitting and storing record information to a cloud management system.
Specifically, the user terminal records the splitting rule in step S161 and the address of the key management device to which each key fragment is saved, generates a splitting and storing record, and saves the splitting and storing record in the cloud management system.
S165: and connecting the cloud management system and performing identity authentication through the cloud management system.
When the key needs to be used, the splitting and storing records are firstly retrieved, so that the user terminal needs to be authenticated through the cloud management system.
S166: and acquiring splitting and storing record information from the cloud management system.
And the cloud management system sends the splitting and storing records to the user terminal, wherein the splitting records comprise splitting rules of the key fragments and storing addresses of the key fragments.
S167: and according to the splitting and storing record information, respectively obtaining each key fragment from each key management device, and combining the obtained key fragments into a key.
Because the splitting and storing record information contains the splitting rule of the key fragments, the key fragments can be automatically combined into a complete key according to the splitting rule after all the key fragments are obtained, and a user does not need to perform combination operation.
It should be noted that all key users (including various employees, department managers, and general managers) can be authenticated according to the administrative level, after all key users log in, the actively generated keys are split and then actively stored in at least two key management devices and managed by two independent administrators, the two independent key management devices both have independent authentication modes, and the two independent key management devices can be a combination of inside and inside, a combination of inside and outside, and a combination of outside and outside. Each independent key management device has an authentication function, and can distribute split keys according to the identity and authorized authority of a key user, and the user can combine and use the keys after obtaining the keys.
The key management device 1 and the key management device 2 can automatically generate a half of the key in accordance with the organization structure established by the user and distribute the generated key to the corresponding key user, and the corresponding key user can re-encrypt the data information of the key generated by the key management device 1 and the key management device 2.
In the two modes, the key management device accesses a plurality of key management devices to obtain and gather a complete key, so that the key can be stored and obtained more safely.
As another embodiment, while the keys at each level are uploaded step by step, the keys may also be uploaded to a key management end (e.g., a private public platform) outside the company as a backup to prevent inconvenience caused by key loss during the uploading process. For example, the key management apparatus 1 in fig. 7 is a key management side inside a company, and the key management apparatus 2 is a key management side outside the company.
Or, the staff of each administrative level can store the own key to the terminals of two administrators of the company at the same time, so that two persons manage the key inside the company at the same time, and the key is prevented from being lost or easily attacked due to one person missing, thereby causing unnecessary loss to the company.
Further, for the secure transmission of the key without leakage, as shown in fig. 1, the method further includes the following steps:
in step S16, a request for acquiring a key is received from a subordinate user terminal.
Step S17, determining whether the subordinate user terminal has the corresponding authority.
If the lower user terminal has the corresponding authority, the corresponding key is sent to the lower user terminal; if the subordinate user terminal does not have the corresponding authority, the corresponding key is not sent.
Taking fig. 3 as an example, when the employee 1 wants to access the user terminal of the employee 2, and the employee 1 needs to submit an application to the department manager 1, after the department manager receives the application, it queries that the employee 1 has a corresponding authority according to the administrative level of the employee, and then sends the key of the employee 2 to the employee 1. If the employee 1 wants to access the user terminal of the employee 3, an application needs to be firstly made to a department manager 1, after the department manager receives the application, the corresponding authority of the employee 1 is inquired according to the administrative level of the employee, the application is sent to a general manager, after the general manager receives the application, a secret key of the employee 3 is requested to a department manager 2 and sent to the general manager, the general manager sends the secret key of the employee 3 to the department manager 1, and finally the department manager 1 sends the secret key of the employee 3 to the employee 1.
Through the step-by-step application and the step-by-step sending mode, the mutual access of the user terminals of each administrative level is realized, the authority enjoyed by each user terminal is verified, and the safety of the mutual access of each user terminal is ensured.
Example two:
fig. 9 shows a schematic structural diagram of a user terminal according to an embodiment of the present invention, and as shown in fig. 9, the user terminal includes:
an obtaining module 51, configured to obtain a plurality of lower-level keys.
And an encryption module 52 for encrypting each lower-level key by using the current-level key.
And a communication module 53, configured to store the encrypted lower-level key to the key manager.
Similarly, taking fig. 2 as an example, the user terminal of the department manager 1 is used as a home terminal, two subordinate keys, that is, keys of the employee 1 user terminal and the employee 2 user terminal are obtained, the keys of the employee 1 user terminal and the employee 2 user terminal are encrypted by using the home key of the department manager 1 user terminal, and the encrypted two subordinate keys, that is, keys of the employee 1 terminal and the employee 2 terminal are stored in a key manager of the department manager 1 user terminal, where the key manager is a local storage. In addition, the communication module 53 is further configured to store the current-level key to the key manager, so that the current-level key is protected.
As a preferred solution, the key manager is provided with a network read disable right. That is, in the case of accessing the key manager simply through a network, the key stored therein cannot be read. But must be read by specific local operations, such as insertion of a U-shield, fingerprint unlocking, etc., to read the key stored therein, and also only in a local manner. By setting the permission of forbidding network reading, the key in the key manager can be prevented from being stolen when the user terminal is attacked by the network, thereby improving the security of key management.
Further, in order to enhance the security effect, as shown in fig. 7, the user terminal further includes: and a sending module 54, configured to send the current-level key to the upper-level user terminal. Only when all the lower levels are logged in, the keys of the lower levels can be submitted to the upper levels step by step.
Further, in view of the fact that the local storage is vulnerable to attack by an attacker, as shown in fig. 9, the user terminal further includes: and the cloud storage module 55 is configured to store the current-level key to the key management device on the network side. The key management device is a cloud storage.
Further, the number of the key management devices may be plural. The user terminal further includes: the splitting module 56 is configured to split the current-level key into at least two key fragments according to a certain splitting rule; the communication module 53 is further configured to store at least two key fragments in at least two key management devices, respectively.
For example, when the key is "100845678", the key may be divided into "100", "845", and "678", and stored in the key management apparatus 1, the key management apparatus 2, and the key management apparatus 3, respectively. Therefore, the whole key can be obtained only after all fragments stored in the three key management devices are obtained, and the security of key storage is enhanced.
The user terminal further comprises a first authentication module and a first combination module. The first authentication module is used for being connected with each key management device and performing identity authentication through the identity authentication of each key management device, and when the key is used, the first authentication module can be connected with each key management device and performs identity authentication through authentication information of each key management device input by a user.
The communication module 53 is further configured to obtain each key fragment from each key management device, and the communication module 53 can obtain the corresponding key fragment from the corresponding key management device, so that all of the plurality of key fragments can be obtained from the plurality of key management devices.
The first combination module is used for combining the acquired key fragments into the key according to the splitting rule. After the communication module 53 acquires all the key fragments from each key management device, the first combining module can recombine the acquired key fragments into a complete key according to the splitting rule of the splitting module 56, the complete key can be acquired only by taking all the key fragments, and the data in the key management device is decrypted by using the key.
The user terminal in the embodiment of the invention further comprises: the system comprises an information generation module, a second authentication module and a second combination module. The information generating module is used for generating splitting and storing record information according to the splitting rule and the addresses of the at least two key management devices. When the splitting module splits and stores according to the established rule, the information generating module can automatically record the splitting and storing record and generate a splitting and storing record according to the record.
The communication module 53 is further configured to store the splitting and storing record information to the cloud management system.
The second authentication module is used for connecting the cloud management system and authenticating the identity through the cloud management system. When the key is used, the second authentication module can perform identity authentication through authentication information input by a user, and retrieve the splitting and storing records.
The communication module 53 is further configured to obtain splitting and storing record information from the cloud management system, and obtain each key fragment from each key management device according to the splitting and storing record information;
the second combination module is used for combining the acquired key fragments into a key, and after all the key fragments are acquired, the second combination module can automatically combine the key fragments into a complete key according to a splitting rule.
Further, in order to ensure the security of mutual access of the user terminals, the secret key may be sent securely without being leaked, and the user terminal further includes: a transceiver module 57, configured to receive a key obtaining request from a subordinate user terminal; a judging module 58, configured to judge whether the subordinate user terminal has a corresponding right; if the subordinate user terminal has corresponding authority, the receiving and transmitting module sends a corresponding key to the subordinate user terminal; if the subordinate user terminal does not have the corresponding authority, the corresponding key is not sent.
The embodiment of the invention realizes the mutual access of the user terminals of each administrative level in a step-by-step application and step-by-step transmission mode, verifies the authority enjoyed by each user terminal and ensures the safety of the mutual access of each user terminal.
The user terminal provided by the embodiment of the present invention has the same technical features as the key management method provided by the above embodiment, so that the same technical problems can be solved, and the same technical effects can be achieved.
Example three:
the embodiment of the invention provides a key management system, which comprises the user terminal in the second embodiment.
Further, the system comprises a plurality of key management devices, wherein each key management device is in communication connection with one or more user terminals.
Specifically, as shown in fig. 10 (taking a three-level user terminal as an example), a plurality of employee user terminals are in communication connection with a plurality of department manager user terminals and a plurality of key management devices, and a plurality of department manager user terminals are in communication connection with a plurality of key management devices and a general manager user terminal.
Furthermore, the key management system also comprises a redundant backup memory, which is used for backing up the key fragments stored in any key management device and backing up the splitting and storing record information.
In another embodiment, after the keys are stored in the key management devices, a single key management device automatically performs redundant backup to another key management device space, wherein the backup is a key fragment, so that when one key management device has a problem, the situation of key loss does not occur, and it is ensured that a plurality of key management devices can mutually backup each other.
The invention provides a key management system, which comprises a plurality of user terminals and a plurality of key management devices, wherein the user terminals corresponding to each administrative level acquire a plurality of lower-level keys according to the administrative levels of a company, each lower-level key is encrypted by using the current-level key, and the encrypted lower-level keys are stored in a local key manager. The system of the invention solves the problem of low security of the existing key keeping mode by using the method of encrypting and storing the lower-level key by using the current-level key.
The key management method, system and computer program product of the user terminal provided in the embodiments of the present invention include a computer readable storage medium storing a program code, where instructions included in the program code may be used to execute the method described in the foregoing method embodiments, and specific implementation may refer to the method embodiments, and will not be described herein again.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the system and the apparatus described above may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
Finally, it should be noted that: the above-mentioned embodiments are only specific embodiments of the present invention, which are used for illustrating the technical solutions of the present invention and not for limiting the same, and the protection scope of the present invention is not limited thereto, although the present invention is described in detail with reference to the foregoing embodiments, those skilled in the art should understand that: any person skilled in the art can modify or easily conceive the technical solutions described in the foregoing embodiments or equivalent substitutes for some technical features within the technical scope of the present disclosure; such modifications, changes or substitutions do not depart from the spirit and scope of the embodiments of the present invention, and they should be construed as being included therein. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.
Claims (14)
1. A key management method is applicable to a plurality of user terminals, each user terminal comprises a key manager for storing a lower-level key, each user terminal comprises at least a local terminal and a lower-level terminal, the local terminal is a terminal of a user at the administrative level of the local level, the lower-level terminal is a terminal of a user at the administrative level subordinate to the administrative level of the local level, and the method is applied to the local terminal and comprises the following steps:
when the current-level terminal and all the subordinate terminals subordinate to the current-level terminal are in the login state, acquiring subordinate keys of all the subordinate terminals subordinate to the current-level terminal;
encrypting each lower-level key of a lower-level terminal subordinate to the current-level terminal by using the current-level key of the current-level terminal;
and storing the encrypted lower-level key to a key manager of the terminal at the current level, wherein the key manager is a local memory.
2. The method of claim 1, further comprising:
and storing the key of the current level to a key manager of the current level terminal.
3. Method according to claim 1 or 2, characterized in that the key manager is provided with a network read-prohibited right.
4. The method of claim 1, further comprising:
and sending the key of the current level to the superior terminal.
5. The method of claim 1, further comprising:
and storing the key of the current level to the key management device.
6. The method according to claim 5, wherein the storing the current-level key to the key management device specifically comprises:
splitting the key of the current level into at least two key fragments according to a certain splitting rule;
and storing the at least two key fragments in at least two key management devices respectively.
7. The method of claim 1, further comprising:
receiving a key acquisition request from a subordinate terminal;
judging whether the subordinate terminal has corresponding authority;
if the subordinate terminal has the corresponding authority, sending a corresponding secret key to the subordinate terminal;
and if the lower terminal does not have the corresponding authority, not sending the corresponding key.
8. A user terminal, wherein the user terminal includes a key manager for storing a lower-level key, the user terminal includes at least a current-level terminal and a lower-level terminal, the current-level terminal is a terminal of a user at a current-level administrative level, the lower-level terminal is a terminal of a user at a lower-level administrative level subordinate to the current-level administrative level, and the user terminal is a current-level terminal and includes:
an obtaining module, configured to obtain lower keys of all lower terminals subordinate to the current terminal when the current terminal and all lower terminals subordinate to the current terminal are in a login state;
the encryption module is used for encrypting the lower-level secret key of each lower-level terminal by using the current-level secret key of the current-level terminal;
and the communication module is used for storing the encrypted lower-level key of the lower-level terminal to a key manager of the terminal, wherein the key manager is a local memory.
9. The ue of claim 8, wherein the communication module is further configured to save the current-level key to a key manager of the current-level terminal.
10. A user terminal according to claim 8 or 9, characterized in that the key manager is provided with a network read-inhibit right.
11. The user terminal according to claim 8, further comprising:
the splitting module is used for splitting the current-level key into at least two key fragments according to a certain splitting rule;
the communication module is further configured to store the at least two key fragments in at least two key management devices, respectively.
12. The user terminal according to claim 8, further comprising:
the receiving and sending module is used for receiving a key acquisition request from a subordinate terminal;
the judging module is used for judging whether the subordinate terminal has corresponding authority;
if the subordinate terminal has the corresponding authority, the transceiver module sends a corresponding key to the subordinate terminal;
and if the lower terminal does not have the corresponding authority, not sending the corresponding key.
13. A key management system comprising a plurality of user terminals according to any one of claims 8 to 12.
14. The key management system of claim 13, further comprising a plurality of key management devices, each of the key management devices being communicatively coupled to one or more of the user terminals.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710091734.9A CN107070881B (en) | 2017-02-20 | 2017-02-20 | Key management method, system and user terminal |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710091734.9A CN107070881B (en) | 2017-02-20 | 2017-02-20 | Key management method, system and user terminal |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107070881A CN107070881A (en) | 2017-08-18 |
| CN107070881B true CN107070881B (en) | 2020-11-27 |
Family
ID=59622286
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710091734.9A Active CN107070881B (en) | 2017-02-20 | 2017-02-20 | Key management method, system and user terminal |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107070881B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108259471B (en) * | 2017-12-27 | 2021-10-08 | 新华三技术有限公司 | Encryption method, decryption method and device for proprietary information and processing equipment |
| CN108833336A (en) * | 2018-04-18 | 2018-11-16 | 北京百度网讯科技有限公司 | Data processing method, device, computer equipment and storage medium |
| CN115118490B (en) * | 2022-06-24 | 2024-04-30 | 北方兵装技术(辽宁)有限公司 | Data confidentiality transmission method and system based on Internet of things |
| CN115549907B (en) * | 2022-11-24 | 2023-03-24 | 北京智芯微电子科技有限公司 | Root key management system, backup method, recovery method, device and electronic equipment |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101174942A (en) * | 2006-10-31 | 2008-05-07 | 华为技术有限公司 | Method and system for implementing cryptographic key protection |
| CN102236766A (en) * | 2011-05-10 | 2011-11-09 | 桂林电子科技大学 | Security data item level database encryption system |
| CN102365839A (en) * | 2009-04-06 | 2012-02-29 | 松下电器产业株式会社 | key installation system |
| CN102487503A (en) * | 2010-12-06 | 2012-06-06 | 中国航空工业集团公司第六三一研究所 | Method for managing multi-stage security dynamic group security keys |
| CN102647273A (en) * | 2012-03-31 | 2012-08-22 | 深圳数字电视国家工程实验室股份有限公司 | Generation methods and devices of user root key and user key for trusted computing platform |
| CN106301774A (en) * | 2015-05-29 | 2017-01-04 | 联芯科技有限公司 | Safety chip, its encryption key generate method and encryption method |
Family Cites Families (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1320798C (en) * | 2003-03-07 | 2007-06-06 | 广东亿业科技有限公司 | Cipher key creating and distributing method and the computer network system therewith |
| JP4546231B2 (en) * | 2004-12-09 | 2010-09-15 | 株式会社日立製作所 | ID-based signature and encryption system and method |
| US20080263363A1 (en) * | 2007-01-22 | 2008-10-23 | Spyrus, Inc. | Portable Data Encryption Device with Configurable Security Functionality and Method for File Encryption |
| CN101132276A (en) * | 2007-09-27 | 2008-02-27 | 中兴通讯股份有限公司 | Method and system for symmetrical encryption of terminal data by SAM card |
| CN101686123B (en) * | 2008-09-24 | 2012-01-25 | 中国移动通信集团公司 | Method and system for managing key, method and device for generating and authenticating key |
| CN103530578B (en) * | 2013-10-18 | 2016-01-27 | 武汉大学 | The construction method of a kind of soft structure credible platform module STPM of Android system |
| CN105656621A (en) * | 2014-11-12 | 2016-06-08 | 江苏威盾网络科技有限公司 | Safety management method for cryptographic device |
| CN105681030B (en) * | 2015-12-31 | 2017-12-19 | 腾讯科技（深圳）有限公司 | key management system, method and device |
-
2017
- 2017-02-20 CN CN201710091734.9A patent/CN107070881B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101174942A (en) * | 2006-10-31 | 2008-05-07 | 华为技术有限公司 | Method and system for implementing cryptographic key protection |
| CN102365839A (en) * | 2009-04-06 | 2012-02-29 | 松下电器产业株式会社 | key installation system |
| CN102487503A (en) * | 2010-12-06 | 2012-06-06 | 中国航空工业集团公司第六三一研究所 | Method for managing multi-stage security dynamic group security keys |
| CN102236766A (en) * | 2011-05-10 | 2011-11-09 | 桂林电子科技大学 | Security data item level database encryption system |
| CN102647273A (en) * | 2012-03-31 | 2012-08-22 | 深圳数字电视国家工程实验室股份有限公司 | Generation methods and devices of user root key and user key for trusted computing platform |
| CN106301774A (en) * | 2015-05-29 | 2017-01-04 | 联芯科技有限公司 | Safety chip, its encryption key generate method and encryption method |
Non-Patent Citations (1)
| Title |
|---|
| "云计算访问控制技术研究综述";王于丁;《软件学报》;20150515;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107070881A (en) | 2017-08-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11036869B2 (en) | Data security with a security module | |
| US8196186B2 (en) | Security architecture for peer-to-peer storage system | |
| EP3398073B1 (en) | Securely storing and distributing sensitive data in a cloud-based application | |
| EP2957063B1 (en) | Policy enforcement with associated data | |
| US20200082110A1 (en) | Automatic key rotation | |
| US10057060B2 (en) | Password-based generation and management of secret cryptographic keys | |
| US20200259637A1 (en) | Management and distribution of keys in distributed environments | |
| Kumar et al. | A systematic review of the security in cloud computing: data integrity, confidentiality and availability | |
| JP2009514072A (en) | Method for providing secure access to computer resources | |
| CN107070881B (en) | Key management method, system and user terminal | |
| CN104392405A (en) | Electronic medical record safety system | |
| CN109981255A (en) | The update method and system of pool of keys | |
| Manthiramoorthy et al. | Comparing several encrypted cloud storage platforms | |
| GB2489676A (en) | Overlay network comprising management node controlling access of subordinate nodes | |
| Sundari et al. | Secure multi-party computation in differential private data with Data Integrity Protection | |
| KR100286904B1 (en) | System and method for security management on distributed PC | |
| US10805079B2 (en) | Method for securing an automated system | |
| CN112787996B (en) | Password equipment management method and system | |
| JP2005286402A (en) | Server and program for encryption key management terminal and program for acquiring encryption key system and method for encryption key management | |
| WO2015034407A1 (en) | Performing an operation on a data storage | |
| KR101996317B1 (en) | Block chain based user authentication system using authentication variable and method thereof | |
| Sathana et al. | Three level security system for dynamic group in cloud | |
| CN113454968B (en) | Method and system for secure transactions | |
| CN105391723A (en) | Hardware-based multilevel key negotiation method | |
| WO2015004327A1 (en) | Method and device for file encryption |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |