WO2024044965A1 - 安全管理系统及安全管理方法 - Google Patents

安全管理系统及安全管理方法 Download PDF

Info

Publication number
WO2024044965A1
WO2024044965A1 PCT/CN2022/115847 CN2022115847W WO2024044965A1 WO 2024044965 A1 WO2024044965 A1 WO 2024044965A1 CN 2022115847 W CN2022115847 W CN 2022115847W WO 2024044965 A1 WO2024044965 A1 WO 2024044965A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal device
information
key
server
access
Prior art date
Application number
PCT/CN2022/115847
Other languages
English (en)
French (fr)
Inventor
张洋
李晗
杨久霞
马明园
踪家双
孙玉海
Original Assignee
京东方科技集团股份有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 京东方科技集团股份有限公司 filed Critical 京东方科技集团股份有限公司
Priority to CN202280002935.6A priority Critical patent/CN117957813A/zh
Priority to PCT/CN2022/115847 priority patent/WO2024044965A1/zh
Publication of WO2024044965A1 publication Critical patent/WO2024044965A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/04—Key management, e.g. using generic bootstrapping architecture [GBA]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06—Authentication

Definitions

  • the present disclosure relates to the field of security, and in particular, to a security management system and a security management method.
  • the security management system includes a first server.
  • the first server is configured to obtain access information of the terminal device. If the access information of the terminal device meets the access conditions, a first key is generated based on the registration time of the terminal device, the identification information of the terminal device and the fingerprint information of the terminal device; wherein the fingerprint information is related to the time when the terminal device installs the application program. .
  • the first key is encrypted using a second key, the first key and the second key being different.
  • the encrypted first key is sent to the terminal device, so that the terminal device uses the second key to decrypt the encrypted first key.
  • the security management system further includes: a gateway, the gateway is configured to: receive an access request from a second server, the second server is a server of the supplier, the access request includes access information, the second server The access information is encrypted using the public key corresponding to the supplier.
  • the access information includes the identification information of the second server and the access request time. Use the private key corresponding to the supplier to decrypt the access request and obtain the access information. Send an access request to the first server corresponding to the supplier based on the access information.
  • the gateway is further configured to: receive an encrypted access request sent from the terminal device.
  • the encrypted access request includes first encrypted information and second encrypted information, using the private key corresponding to the public key to pair the first
  • the encrypted information is decrypted to obtain the first information.
  • the second encrypted information is sent to the first server.
  • the first server is further configured to: receive the second encrypted information, use the first key to decrypt the second encrypted information, and obtain the second information.
  • the first encrypted information is obtained by the terminal device using a public key to encrypt the first information in the access request; the second encrypted information is obtained by the terminal device using the first key to encrypt the second information in the access request.
  • the first server is further configured to: obtain and store identification information and registration information of the terminal device.
  • the identification information of the terminal device includes the media access control address and/or international mobility of the terminal device.
  • Device identification code the registration information of the terminal device includes the fingerprint information of the terminal device.
  • the access information of the terminal device satisfies the access condition, including: the registration information of at least one terminal device stored by the first server includes the same fingerprint information as the fingerprint information in the access information of the terminal device.
  • the first server is further configured to: send response information to the terminal device, where the response information is used to indicate that the access information of the terminal device satisfies the access condition.
  • Receive a key request from the terminal device the key request is used to request the first key; wherein the registration time of the terminal device is related to the time when the terminal device sends the key request.
  • the security management system further includes: a terminal device, the terminal device is configured to: send access information to the first server. Receive the encrypted first key, and use the second key to decrypt the encrypted first key to obtain the first key.
  • the second key is generated through a hash operation based on the first salt value information, the fingerprint information of the terminal device, and the registration time of the terminal device.
  • the terminal device is further configured to: if the terminal device reinstalls the application or the terminal device is refreshed, the terminal device re-sends the access information to the first server.
  • the terminal device is further configured to: generate a third key through a hash operation based on the fingerprint information of the terminal device and the second salt value information.
  • the third key is used to encrypt the first key, and the encrypted first key is stored.
  • the terminal device is further configured to: based on the identification information of the terminal device, the hardware information of the terminal device, the information of the application program installed by the terminal device, and the time when the terminal device installed the application program, adopt The hash algorithm generates fingerprint information of the terminal device.
  • the first server is also configured to add the terminal device to the blacklist when the number of abnormal accesses to the terminal device is greater than or equal to the threshold number; wherein the abnormal access includes access by the terminal device.
  • the information does not meet the access conditions.
  • the security management method includes: the first server obtains access to a terminal device. If the access information of the terminal device meets the access conditions, the first server generates a first key based on the registration time of the terminal device, the identification information of the terminal device and the fingerprint information of the terminal device; wherein the fingerprint information is related to the application installed on the terminal device. related to the time.
  • the first server uses a second key to encrypt the first key, and the first key is different from the second key.
  • the first server sends the encrypted first key to the terminal device, so that the terminal device uses the second key to decrypt the encrypted first key.
  • the security management method further includes: the gateway receives an access request from a second server, the second server is a server of the supplier, the access request includes access information, and the second server uses the public key pair corresponding to the supplier.
  • the access information is encrypted, and the access information includes the identification information of the second server and the access request time.
  • the gateway uses the private key corresponding to the supplier to decrypt the access request and obtain the access information.
  • the gateway sends an access request to the first server corresponding to the supplier based on the access information.
  • the security management method further includes: the gateway receiving an encrypted access request sent from the terminal device, where the encrypted access request includes first encrypted information and second encrypted information.
  • the gateway uses the private key corresponding to the public key to decrypt the first encrypted information to obtain the first information.
  • the gateway sends the second encrypted information to the first server based on the first information.
  • the first server receives the second encrypted information and uses the first key to decrypt the second encrypted information to obtain the second information.
  • the first encrypted information is obtained by the terminal device using a public key to encrypt the first information in the access request; the second encrypted information is obtained by the terminal device using the first key to encrypt the second information in the access request.
  • the security management method further includes: the first server obtains and stores identification information and registration information of the terminal device.
  • the identification information of the terminal device includes the media access control address and/or the International Mobile Equipment Identity of the terminal device.
  • the registration information of the terminal device includes the fingerprint information of the terminal device.
  • the access information of the terminal device satisfies the access condition, including: the registration information of at least one terminal device stored by the first server includes the same fingerprint information as the fingerprint information in the access information of the terminal device.
  • the security management method further includes: the first server sending response information to the terminal device, where the response information is used to indicate that the access information of the terminal device satisfies the access condition.
  • the first server receives a key request from the terminal device, and the key request is used to request the first key.
  • the registration time of the terminal device is related to the time when the terminal device sends the key request.
  • the security management method further includes: the terminal device sends access information to the first server.
  • the terminal device receives the encrypted first key and uses the second key to decrypt the encrypted first key to obtain the first key.
  • the second key is generated through a hash operation based on the first salt value information, the fingerprint information of the terminal device, and the registration time of the terminal device.
  • the security management method further includes: if the terminal device reinstalls the application program or the terminal device is refreshed, the terminal device re-sends access information to the first server.
  • the security management method further includes: the terminal device generates a third key through a hash operation based on the fingerprint information of the terminal device and the second salt value information.
  • the terminal device uses the third key to encrypt the first key and stores the encrypted first key.
  • the security management method also includes: the terminal device uses a hash algorithm based on the identification information of the terminal device, the hardware information of the terminal device, the information of the application program installed by the terminal device, and the time when the terminal device installed the application program. Generate fingerprint information of the terminal device.
  • a non-transitory computer-readable storage medium stores computer program instructions.
  • the computer program instructions When the computer program instructions are run on a computer (for example, a security management system), the computer executes the security management method as described in any of the above embodiments. .
  • a computer program product includes computer program instructions.
  • the computer program instructions When the computer program instructions are executed on a computer (eg, a security management system), the computer program instructions cause the computer to execute the security management method as described in any of the above embodiments.
  • a computer program is provided.
  • the computer program When the computer program is executed on a computer (for example, a security management system), the computer program causes the computer to execute the security management method as described in any of the above embodiments.
  • Figure 1 is a schematic diagram of a security management system according to some embodiments.
  • FIG. 2 is a schematic diagram of another security management system according to some embodiments.
  • Figure 3 is a schematic diagram of the information interaction process of a security management system according to some embodiments.
  • Figure 4 is a schematic diagram of a gateway encryption process according to some embodiments.
  • FIG. 5 is a schematic diagram of yet another security management system according to some embodiments.
  • Figure 6 is a flow chart of a security management method according to some embodiments.
  • FIG. 7 is a flowchart of another security management method according to some embodiments.
  • first and second are used for descriptive purposes only and cannot be understood as indicating or implying relative importance or implicitly indicating the quantity of indicated technical features. Therefore, features defined as “first” and “second” may explicitly or implicitly include one or more of these features. In the description of the embodiments of the present disclosure, unless otherwise specified, "plurality" means two or more.
  • At least one of A, B and C has the same meaning as “at least one of A, B or C” and includes the following combinations of A, B and C: A only, B only, C only, A and B The combination of A and C, the combination of B and C, and the combination of A, B and C.
  • a and/or B includes the following three combinations: A only, B only, and a combination of A and B.
  • the term “if” is optionally interpreted to mean “when” or “in response to” or “in response to determining” or “in response to detecting,” depending on the context.
  • the phrase “if it is determined" or “if [stated condition or event] is detected” is optionally interpreted to mean “when it is determined" or “in response to the determination" or “on detection of [stated condition or event]” or “in response to detection of [stated condition or event]”.
  • bank branches are providing more and more application services for terminal devices.
  • the terminal device needs to access the bank's intranet through wireless network access, but the bank's intranet cannot provide wireless network. Therefore, the mobile terminal accesses the bank's intranet through the Internet to access related application services. This is the bank's intranet. security challenges.
  • security challenges At present, in the solutions for terminal equipment to connect to the bank's intranet through the Internet, most of them only consider the security protection of the data transmission process, and do not consider the security of the entire link, making the process of terminal equipment accessing the bank's intranet a certain degree of security. Hidden danger.
  • embodiments of the present disclosure provide a full-link secure access solution, which performs processes such as terminal device access, information interaction between the terminal device and the bank's intranet, and information interaction between the supplier and the bank's intranet.
  • Security protection strengthen the security control of the bank’s intranet.
  • FIG. 1 is a schematic diagram of a security management system provided by an embodiment of the present disclosure.
  • the security management system 10 includes a first server 11 .
  • the first server 11 is a server deployed in an internal network environment (also called an intranet).
  • the internal network environment can be a network environment deployed in any area.
  • the embodiment of the disclosure takes a bank intranet as an example for illustrative explanation.
  • the first server 11 may be a server deployed on a bank's intranet, and various applications (applications, APPs) may be deployed on the first server 11 .
  • the number of the first server 11 may be one or multiple; the first server 11 may be a physical server or a virtual server; the embodiment of the present disclosure does not limit the type and quantity of the first server 11 .
  • the security management system 10 further includes a terminal device 12 .
  • the terminal device 12 includes, for example, a mobile phone, a notebook computer, a tablet computer (such as a PAD device), a smart wearable device (such as a watch), and the like.
  • the number of terminal devices 12 may be one or multiple devices.
  • the embodiment of the present disclosure does not limit the type and number of terminal devices 12 connected to the bank's intranet.
  • the terminal device 12 After the terminal device 12 is connected to the bank's intranet, it can access the application services deployed on the first server 11 .
  • the terminal device 12 When the PAD is connected to the bank's intranet, users (for example, bank managers) can conduct relevant business processing or information inquiries through the relevant APP installed on the PAD.
  • the terminal device 12 is configured to: send a registration request to the first server 11, where the registration request includes registration information.
  • the first server is configured to receive a registration request from the terminal device 12 .
  • the first server 11 is further configured to obtain and store the identification information and registration information of the terminal device 12 .
  • the identification information of the terminal device 12 is information that can uniquely identify the terminal device 12.
  • the identification information of the terminal device 12 includes but is not limited to: the media access control address (Media Access Control Address, MAC) of the terminal device 12 and/or Or International Mobile Equipment Identity (IMEI).
  • MAC Media Access Control Address
  • IMEI International Mobile Equipment Identity
  • the first server 11 obtains the identification information of the terminal device 12 , including: the first server 11 enters the identification information of the terminal device 12 . After obtaining the identification information of the terminal device 12, the first server 11 stores the identification information.
  • a management and control platform 23 is deployed on the first server 11 of the bank's intranet.
  • the management and control platform 23 is used to perform the process of accessing the first server 11 by the terminal device 12 (for example, including a watch device 21 and a PAD device 22). manage.
  • the management and control platform 23 is also used to manage bank branch equipment, such as branch equipment 24, branch equipment 25, and branch equipment 26.
  • the identification information of the terminal device 12 can be entered into the management and control platform 23.
  • the identification information of the terminal device 12 may be entered manually.
  • the first server 11 stores the identification information of the terminal device 12.
  • the terminal device 12 After completing the entry of the identification information of the terminal device 12, the terminal device 12 can perform device registration. Only the terminal device 12 that has completed device registration has the authority to access the first server 11 . For example, the prerequisite for the terminal device 12 to perform device registration is that the identification information of the terminal device 12 is stored in the first server 11 .
  • the terminal device 12 Before the terminal device 12 registers the device, it needs to download and install the relevant APP in advance. Taking the Android application package (APK) as an example, the user downloads and installs the APK on the terminal device 12 Afterwards, the terminal device 12 will check its network access status to check whether the terminal device 12 has accessed the first server 11 . If the check result is that the terminal device 12 has not yet accessed the first server 11, continue to complete the device registration process.
  • API Android application package
  • the device registration of the terminal device 12 can be completed at any time after the identification information is entered. For example, it can be performed immediately after the identification information is entered, or it can be performed after a period of time after the identification information is entered.
  • Device registration by the terminal device 12 includes: the terminal device 12 sending a registration request to the first server 11 .
  • the terminal device 12 sends a registration request to the first server 11 by calling the registration interface 31, and the registration request includes registration information.
  • the registration information of the terminal device 12 includes identification information of the terminal device 12 , fingerprint information of the terminal device 12 , version information of the APP installed on the terminal device 12 , etc.
  • the first server 11 After the terminal device 12 sends a registration request to the first server 11, the first server 11 receives the registration request and obtains the registration information of the terminal device 12 at the same time. Since the registration information includes the identification information of the terminal device 12 , after obtaining the identification information of the terminal device 12 that sent the registration request, the first server 11 verifies whether the identification information is stored in the first server 11 . That is to say, the first server 11 needs to verify whether the terminal device 12 that sends the registration request is the terminal device 12 that has completed the entry of the identification information. If the first server 11 stores the identification information of the terminal device 12 that sent the registration request, it indicates that the terminal device 12 is an registered terminal device. In this case, the terminal device 12 has the authority to continue device registration. .
  • the first server 11 stores the identification information of the terminal device 12 that sent the registration request
  • the first server 11 stores the obtained registration information of the terminal device 12 .
  • the management and control platform 23 updates the received registration information of the terminal device 12 to the information of the terminal device 12 in the first server 11 . That is to say, at this time, the identification information, fingerprint information, etc. corresponding to the terminal device 12 are stored in the first server 11 .
  • the fingerprint information of the terminal device 12 is based on the identification information of the terminal device 12, the hardware information of the terminal device 12, the information of the APP installed by the terminal device 12, and the time when the terminal device 12 installed the APP. Obtained by Hash algorithm.
  • the hardware information of the terminal device 12 may be information that is not easily changed on the terminal device 12, such as device model information, storage space information, etc. of the terminal device 12.
  • the time when the terminal device 12 installs the APP includes the time when the terminal device 12 installs the APP for the first time, or the time when the terminal device 12 reinstalls the APP.
  • the terminal device 12 uninstalls and reinstalls the APP
  • the information of the APP installed by the terminal device 12 and the time when the APP was installed have changed, so the fingerprint information of the terminal device 12 will also change.
  • the terminal The device 12 will re-send a new registration request to the first server 11, and the first server 11 will re-obtain the new registration information of the terminal device 12, and the new registration information includes the new fingerprint information.
  • the hash algorithm in the implementation of this disclosure can adopt MD 5 (Message-Digest 5) algorithm, or other hash algorithms, such as SHA 1 algorithm, SHA 256 algorithm, etc.
  • MD 5 Message-Digest 5
  • SHA 1 algorithm SHA 1 algorithm
  • SHA 256 algorithm etc.
  • the type is not limited.
  • the terminal device 12 can start to access the first server 11 .
  • the first server 11 is also configured to: obtain the access information of the terminal device 12 and determine whether the access information of the terminal device 12 meets the access conditions; if the access information of the terminal device 12 meets the access conditions, based on the access information of the terminal device 12
  • the registration time, the identification information of the terminal device 12 and the fingerprint information of the terminal device 12 are used to generate a first key.
  • the access information of the terminal device 12 satisfies the access conditions, including: the registration information of at least one terminal device stored in the first server 11 includes the same fingerprint information as the fingerprint information in the access information of the terminal device 12 .
  • the first server 11 When the terminal device 12 accesses the first server 11 for the first time, the first server 11 will conduct a device audit on the terminal device 12 .
  • the embodiment of the present disclosure does not limit the method of auditing the terminal device 12 of the first server 11.
  • manual review can be used, or system automatic review can be used.
  • the device audit of the terminal device 12 by the first server 11 includes: checking whether the access information of the terminal device 12 meets the access conditions. If the access conditions are met, the audit passes, otherwise the audit fails.
  • the access information of the terminal device 12 is the access information of the terminal device 12 sent to the first server 11 when the terminal device 12 accesses the first server 11.
  • the access information may include the terminal device to be accessed. 12 identification information, fingerprint information, etc.
  • the first server 11 determines whether the terminal device 12 to be accessed is a terminal device stored in the first server 11 based on the access information.
  • the first server 11 Since the first server 11 stores the registration information of one or more terminal devices that have completed the entry of identification information, the first server 11 can check whether the fingerprint information stored by the first server 11 includes the terminal device to be accessed.
  • the fingerprint information in the access information of 12 is used to determine whether the terminal device 12 to be accessed has the authority to access the first server 11. If the fingerprint information in the registration information stored in the first server 11 includes the fingerprint information in the access information of the terminal device 12, then the access information of the terminal device 12 meets the access conditions and can access the first server 11, On the contrary, the access information of the terminal device 12 does not meet the access conditions, and therefore the first server 11 cannot be accessed.
  • the access information of the watch device 21 (including the fingerprint information of the watch device 21) can be seen on the management and control platform 23.
  • the administrator can check (or the system automatically checks ) whether the fingerprint information matches the fingerprint information stored in the first server 11. If the fingerprint information in the access information of the watch device 21 successfully matches the fingerprint information stored in the first server 11 , the review is passed and the watch device 21 successfully accesses the first server 11 . If the fingerprint information in the access information of the watch device 21 does not successfully match the fingerprint information stored in the first server 11 , the audit fails and the watch device 21 cannot access the first server 11 .
  • the first server 11 receives the registration request and performs device audit on the terminal device 12 .
  • the results of the device audit include passing the audit and failing the audit. Only the terminal device 12 that passes the audit can access the first server 11. If the audit fails, the first server 11 returns abnormal information to the terminal device 12.
  • the terminal device 12 is further configured to: if the terminal device 12 reinstalls the application or the terminal device 12 is refreshed, the terminal device 12 resends the access information to the first server 11 .
  • the terminal device 12 After the terminal device 12 is successfully registered, it cannot directly perform repeated registration.
  • the terminal device 12 When the terminal device 12 reinstalls the APK or performs operations such as flashing, the terminal device 12 will re-send a registration request to the first server 11 to re-register the device.
  • the first server 11 will re-verify the registration request of the terminal device 12 and re-audit the access information resent by the terminal device 12 .
  • the terminal device 12 makes a registration request, the first server 11 first checks the registration status of the terminal device 12. If the registration status of the terminal device 12 is registered, the first server 11 needs to register the terminal device 12 before auditing. The status is cleared, for example, the registration status is changed to unregistered, so that the terminal device 12 can re-register and access the first server 11 .
  • the first server 11 is also configured to send response information to the terminal device 12, where the response information is used to indicate that the access information of the terminal device 12 satisfies the access condition.
  • the terminal device 12 is also configured to receive response information from the first server 11 and send a key request to the first server 11, where the key request is used to request the first key.
  • the first key is a key used to encrypt communication messages during communication between the terminal device 12 and the first server 11 .
  • the first server 11 is further configured to receive a key request from the terminal device 12, the key request being used to request the first key.
  • the first server 11 will send response information to the terminal device 12 to indicate that the terminal device 12 has accessed the first server 11 .
  • the terminal device 12 After receiving the response information sent by the first server 11, the terminal device 12 sends a key request to the first server 11 to request the first key for encrypting the communication message.
  • the first server 11 After receiving the key request sent by the terminal device 12, the first server 11 generates the first key based on the registration time of the terminal device 12, the identification information of the terminal device 12, and the fingerprint information of the terminal device 12.
  • the registration time of the terminal device 12 is related to the time when the terminal device 12 sends the key request to the first server 11 .
  • the registration time of the terminal device 12 may be the time when the terminal device 12 sends a key request to the first server 11, or the registration time of the terminal device 12 may also be the time when the first server 11 receives the key request sent by the terminal device 12. time. Determining the registration time of the terminal device 12 by the time when the first server 11 sends the key request can ensure that the terminal device 12 has successfully accessed the first server 11 at the registration time.
  • the first server 11 can perform the verification based on the MAC address or IMEI of the terminal device 12, the fingerprint information of the terminal device 12, the registration time of the terminal device 12, and the audit information of the terminal device 12 (such as auditor information, audit time, etc.)
  • the hash operation yields the first key. Since the generation factor of the first key includes the fingerprint information and registration time of the terminal device 12, that is, the generation mechanism of the first key is related to both the fingerprint information of the terminal device 12 and the time factor, so it is difficult to be detected afterwards. Imitation and hacking. That is to say, for each terminal device 12, the first server 11 will generate a unique first key to implement a one-machine-one-key dynamic distribution mechanism.
  • the first server 11 After the first server 11 generates the first key, it stores the first key and issues the first key to the terminal device 12 at the same time, so that the first server 11 and the terminal device 12 use the first key respectively when communicating. Perform encryption and decryption to implement the encryption mechanism of symmetric encryption.
  • the first server 11 is further configured to encrypt the first key using the second key.
  • the first server 11 can encrypt the first key using the second key, and download the encrypted first key. Send it to the terminal device 12, thereby ensuring that the first key issuance process is safe and reliable.
  • the first server 11 When issuing the first key, the first server 11 first dynamically generates the second key, then uses the second key to encrypt the first key, and sends the encrypted first key to the terminal device 12 . Since the second key will only be used when the first server 11 issues the first key, in some examples, after completing the delivery of the first key, the first server 11 will not use the second key. for storage.
  • the first server 11 may use a salt encryption algorithm to generate the second key.
  • the first server 11 may perform a hash operation on the first salt value information, the fingerprint information of the terminal device 12 and the registration time of the terminal device 12 to obtain the second key.
  • the first salt value information may be a set of character strings stored internally by the first server 11 , or a set of character strings temporarily generated by the first server 11 . This disclosure does not limit the specific content of the first salt value information.
  • the generation information of the second key may also include the MAC address of the terminal device, the ownership information of the terminal device 12 , the serial number ID of the APP installed on the terminal device 12 , etc.
  • the belonging information of the terminal device 12 may include information about the region to which the terminal device 12 belongs, or information about the user to which the terminal device 12 belongs, etc.
  • the second key is different from the first key.
  • the generation factors of the first key and the second key are different, so the second key is different from the first key; for another example, the generation factor of the second key includes salt value information, and the generation factor of the first key is different.
  • the generation factor does not include salt value information, so the second key is different from the first key; for another example, the generation factors of the first key and the second key both include salt value information, but the two salt value information are different,
  • the second key is therefore different from the first key. For example, after the first server 11 generates the second key, if it is found that the second key is the same as the first key, the second key can be regenerated.
  • the first server 11 is further configured to: send the encrypted first key to the terminal device 12, so that the terminal device 12 uses the second key to decrypt the encrypted first key.
  • the first server 11 will return the first key encrypted with the second key to the terminal device 12, and the terminal device 12 receives the encrypted first key. After decrypting the key, decrypt and store the first key.
  • the terminal device 12 receives the encrypted first key and uses the second key to decrypt the encrypted first key to obtain the first key.
  • the terminal device 12 uses the same generation mechanism as the first server 11 to generate the second key, thereby realizing a symmetric encryption mechanism between the terminal device 12 and the first server 11 and improving encryption efficiency.
  • the same mechanism as the first server 11 generating the second key the terminal device 12 can also use a hash operation to obtain the second key based on the first salt value information, the fingerprint information of the terminal device 12, and the registration time of the terminal device 12, Ensure the consistency of the second key.
  • the first salt value information in the terminal device 12 may be the first salt value information sent to the terminal device 12 by the first server 11 (for example, the first server 11 may encrypt the first salt value information and send it to The terminal device 12) may also be the first salt value information generated by the terminal device 12 using the same generation mechanism as the first server 11.
  • the terminal device 12 After the terminal device 12 obtains the first key by decrypting the second key, it needs to store the first key for use in encrypting the service request during subsequent service communications with the first server 11 .
  • the terminal device 12 sends a service request encrypted with a first key to the first server 11 by calling the communication interface 32.
  • the first server 11 receives the encrypted service request and uses the first key to decrypt the service. request, if the decryption is successful, the first server 11 returns the response value corresponding to the service request to the terminal device 12; if the decryption fails, the first server 11 rejects the service request of the terminal device 12.
  • the terminal device 12 is also configured to: use a salt value algorithm to generate a third key based on the fingerprint information of the terminal device 12; use the third key The three keys encrypt the first key and store the encrypted first key.
  • the terminal device 12 may perform a hash operation on the second salt value information and the fingerprint information of the terminal device 12 to obtain the third key.
  • the second salt value may be a set of character strings stored internally by the terminal device 12 , or a set of character strings temporarily generated by the terminal device 12 .
  • the second salt value information is different from the first salt value information.
  • the third key generation information may also include the MAC address of the terminal device, the ownership information of the terminal device 12 , the serial number ID of the APP installed on the terminal device 12 , etc.
  • the third key can also be generated by other valid encryption strategies.
  • the terminal device 12 uses the generated third key to encrypt and store the first key, thereby ensuring the storage security of the first key.
  • the same generation mechanism is used to generate the third key for decryption, thereby realizing the symmetry of the third key.
  • the terminal device 12 can use the same generation mechanism to generate the same second salt value information again.
  • the third key is obtained based on the second salt value information, thereby ensuring the security of the third key. consistency.
  • the terminal device 12 can replace the second salt value information after a preset time has elapsed, thereby ensuring dynamic management of the third key. For example, the terminal device 12 can regenerate the second salt value information every month, thereby regenerating the third key, and use the new third key to encrypt and store the first key; for another example, the terminal device 12 can also The second salt value information can be regenerated from time to time, thereby regenerating the third key, and using the new third key to encrypt and store the first key.
  • the terminal device 12 is further configured to use packing technology to provide security protection for applications installed on the terminal device 12 .
  • the embodiment of the present disclosure adopts the packing technology of Android to protect the program source code of the terminal device 12, further strengthening the security protection of the terminal device 12. For example, you can wrap another piece of code outside the APP program to protect the core code inside from being illegally modified. This disclosed embodiment does not limit another piece of code in the package.
  • the first server 11 is also configured to: when the number of abnormal accesses of the terminal device 11 is greater than or equal to the threshold number, add the terminal device 12 to the blacklist; where the abnormal access includes that the access information of the terminal device 12 does not satisfy Access conditions.
  • the abnormal access of the terminal device 11 to the first server 11 may include: the terminal device 12 sends registration requests to the first server 11 multiple times in succession, and the access information each time does not meet the access conditions; and the terminal device 12 has already After accessing the first server 11, and in the process of communicating with the first server 11, the terminal device 12 continuously calls the interface of the first server 11 abnormally.
  • the threshold number of times can be set according to requirements, and the embodiment of the present disclosure does not limit the threshold number of times.
  • the threshold number is 5
  • the access interface of the first server 11 is continuously abnormally called by the terminal device 12 for more than 5 times
  • the first server 11 will add the terminal device 12 to the blacklist.
  • the terminal device 12 cannot Visit the first server 11 again. If the terminal device needs to access the first server 11 again, it needs to register again.
  • attackers can be prevented from attacking the first server 11 in a trial and error manner.
  • the first server 11 may use the HyperText Transfer Protocol over Secure Socket Layer (HTTPS) interface communication method to enhance the security of information transmission.
  • HTTPS HyperText Transfer Protocol over Secure Socket Layer
  • the terminal device 12 calls the interface of the first server 11, it needs to include a digital signature.
  • the first server 11 can verify the legitimacy of the terminal device 12 through the signature.
  • the security management system 10 provided by the embodiment of the present disclosure strictly controls the security of the process of the terminal device 12 accessing the first server 11, and conducts equipment audit on the terminal device 12 through the fingerprint information of the terminal device 12, thereby strengthening the terminal Security authentication and access authorization of device 12.
  • the embodiment of the present disclosure provides further security protection for the data transmission process between the terminal device 12 and the first server 11.
  • the security management system 10 provided in the example uses a symmetric encryption mechanism (for example, Advanced Encryption Standard (AES) encryption) to realize the distribution of the first key between the terminal device 12 and the first server 11, the encryption of communication messages, and the encryption of the first key.
  • AES Advanced Encryption Standard
  • the encryption of the stored process with one key has the characteristics of fast encryption speed and higher security.
  • the access process of the terminal device 12 requires authorization.
  • the process for each terminal device 12 to obtain the first key is dynamic and unique, and the first key, the second key and the third key are
  • the generation mechanisms are all related to the time factor. Therefore, they are difficult to be imitated and cracked afterwards, ensuring the security of the security management system 10.
  • the embodiment of the present disclosure does not limit the application scenarios of the management system 10, and the following is an exemplary explanation taking a bank as an example.
  • the key system of the first key, the second key and the third key is managed by the supplier that provides products and services to the bank.
  • the bank generally uses code security scanning, code management or contract constraints to manage the key system. Restricting suppliers makes it difficult to effectively manage and monitor the confidentiality of keys by suppliers.
  • the security management system 10 also includes a gateway.
  • the gateway 13 can be a central operation mode and be uniformly controlled by the bank.
  • the gateway 13 is used to manage and monitor the access requests sent by the supplier, and forward the screened access requests to the corresponding first server 11, thereby ensuring the security of the access process to the first server 11.
  • the gateway 13 is configured to: receive an access request from the second server 20.
  • the second server 20 is the server of the supplier.
  • the access request includes access information.
  • the second server 20 uses the public key pair corresponding to the supplier.
  • the access information is encrypted, and the access information includes the identification information of the second server 20 and the access request time.
  • the second server 20 is a server of a supplier.
  • the supplier provides application services to the bank through the second server 20, and the application services are deployed on the first server 11 of the bank's intranet.
  • Different application services can be provided by different suppliers, or they can be provided by the same supplier.
  • the same supplier can provide application services for banks through at least one second server 20 , and the number of suppliers and second servers 20 is not limited in this embodiment of the disclosure.
  • the application services of the bank's intranet are provided by Supplier A, Supplier B, and Supplier C respectively.
  • Application A, Application B, and Application C can be deployed on the same computer. on the first server 11, or may be deployed on different first servers 11 respectively.
  • applications provided by different suppliers can be deployed on different first servers 11 to achieve physical isolation between different suppliers.
  • asymmetric encryption may be used for information transmission between the second server 20 and the first server 11.
  • the private key in the asymmetric encryption algorithm is mastered and managed by the bank, and the public key is mastered by each supplier.
  • public keys corresponding to different suppliers are different, and different suppliers store their own public keys.
  • the gateway 13 stores relevant information about the second server 20 of each supplier, and the information includes the private key information corresponding to the second server 20 and the identification information of the second server 20 .
  • This disclosed embodiment does not limit the storage method of the private key.
  • the private key can be stored in an encrypted storage method using a third key as in the above implementation.
  • the gateway 13 can separately store the private keys corresponding to each supplier to further ensure the security of the private keys of each supplier.
  • the public key of supplier A is public key A
  • the public key of supplier B is public key B
  • the public key of supplier C is public key C
  • public key A public key B
  • public key C public key C
  • public key A public key B
  • public key C public key C
  • the access request sent by the second server 20 to the first server 11 uniformly calls the gateway 13, and the access request includes access information.
  • the access information may include the APP serial number (Serial ID) of the application service provided by the supplier, the access request time, the identification information of the second server 20 (such as the MAC address of the second server 20), etc., the second server 20
  • the access information is encrypted using the public key, and the encrypted access request is sent to the gateway 13.
  • supplier A that is, the second server 20 corresponding to supplier A
  • the gateway 13 is also configured to decrypt the access request using the private key corresponding to the supplier to obtain the access information.
  • the gateway 13 After receiving the access request sent by the second server 20, the gateway 13 uses the private key corresponding to the public key of the supplier to decrypt the access request and obtain the access information.
  • the access request sent by the second server 20 may include the device IMIE number of the second server 20, and the gateway 13 may store the private key corresponding to the IMEI number of the second server 20. Then when the gateway 13 receives the access request , the corresponding private key can be found based on the IMIE number, thereby decrypting the access information in the access request.
  • the gateway 13 after receiving the access request encrypted with the public key A sent by the supplier A, the gateway 13 decrypts the encrypted access request using the stored private key A to obtain the access request, thus obtaining Access information.
  • the gateway 13 is further configured to: send an access request to the first server 11 corresponding to the supplier based on the access information.
  • the access information includes the supplier's APP Serial ID, and the APP Serial ID can determine the first server 11 corresponding to the application provided by the supplier. Therefore, the gateway 13 can forward the access request sent by the second server 20 to the corresponding first server 11 according to the APP Serial ID. As shown in Figure 4, the gateway 13 sends the access request decrypted by the private key A to the application A corresponding to the supplier A.
  • the gateway 13 can also control access to the second server 20 based on information such as the access request time and the MAC address of the second server 20 . For example, whether the second server 20 is in a normal access state can be determined by whether the gateway 13 can use the private key corresponding to the second server 20 to decrypt the access request sent by the second server 20 . Alternatively, after the gateway 13 decrypts the message information, it can determine whether the second server 20 is in a normal access state based on whether the device identifier in the access information is consistent with the device identifier of the second server 20 stored in the gateway 13 . If the second server 20 is in a normal access state, the access request sent by the second server 20 is forwarded to the first server 11 .
  • the gateway 13 can also monitor the number of abnormal accesses of the second server 20. For example, when the number of consecutive abnormal accesses of the second server 20 is greater than or equal to a preset number of times, the gateway 13 can prohibit the second server 20 from continuing to send. Access request.
  • the security management system 10 provided by the embodiment of the present disclosure can effectively control the content of supplier access requests, the number of requests, and the source of the requests, monitor and provide early warning for supplier access requests, thereby effectively preventing suppliers from improper management. Damage to the safety mechanism caused by other reasons.
  • the asymmetric encryption method between the second server 20 and the gateway 13 can be used for business communication between the terminal device 12 and the first server 11 .
  • a gateway 13 can be added between the terminal device 12 and the first server 11 .
  • the gateway 13 is also configured to: receive an encrypted access request sent from the terminal device 12.
  • the encrypted access request includes first encrypted information and second encrypted information, using a private key pair corresponding to the public key.
  • the first encrypted information is decrypted to obtain the first information.
  • the second encrypted information is sent to the first server 11 .
  • the first server 11 is further configured to: receive the second encrypted information, use the first key to decrypt the second encrypted information, and obtain the second information.
  • the first encrypted information is obtained by the terminal device 12 encrypting the first information in the access request using a public key; the second encrypted information is obtained by the terminal device 12 using the first key to encrypt the second information in the access request. .
  • the first public key when the terminal device 12 sends an access request to the first server 11, the first public key may be used to encrypt part of the information in the access request, for example, the first public key may be used to encrypt the first information in the access request. Encrypt; then use the first key to encrypt another part of the information in the access request, for example, use the first key to encrypt the second information in the access request, thereby realizing the connection between the terminal device 12 and the first server 11
  • the double-layer encryption of communication further improves the security of information transmission between the terminal device 12 and the first server 11 .
  • the encryption method using the first public key can be called the gateway encryption method
  • the encryption method using the first key can be called the platform policy encryption method.
  • the access request sent by the terminal device 12 to the first server 11 includes key information and business information.
  • the key information includes, for example, the identification information of the terminal device 12, the access request sending time, the Serial ID of the APP that needs to be accessed, etc.
  • the business information includes, for example, the specific request information sent by the terminal device 12 to the first server 11.
  • the first information includes key information
  • the second information includes business information.
  • the terminal device 12 can encrypt the key information in the access request using the first public key and the business information using the first key, thereby further improving the security of information transmission between the terminal device 12 and the first server 11
  • the first public key is used to encrypt key information with a small amount of information
  • the first key is used to encrypt business information with a large amount of information. This can also avoid the encryption by the first public key (asymmetric encryption). The problem of low encryption efficiency arises.
  • a gateway 13 is provided between the terminal device 12 and the first server 11 .
  • the access request sent by the terminal device 12 includes information A (key information) and information B (business information).
  • the terminal device 12 uses the first public key to perform gateway encryption on information A, uses the first key to perform platform policy encryption on information B, and sends the encrypted access request to the gateway 13 first.
  • the gateway 13 uses the first private key corresponding to the first public key in gateway encryption to perform gateway decryption on the encrypted access request to obtain information A. Then, the gateway 13 forwards the information B to the corresponding first server 11 according to the APP Serial ID in the information A.
  • the first server 11 receives the encrypted information B, uses the first key to decrypt the encrypted information B according to the platform policy, and obtains the information B, that is, the specific content of the access request sent by the terminal device 12.
  • the process of the first server 11 sending an access request to the terminal device 12 is also similar and will not be described again here.
  • Figure 6 provides a security management method according to an embodiment of the present disclosure. As shown in Figure 6, the security management method includes steps 611 to 623.
  • Step 611 The terminal device 12 sends a registration request to the first server 11.
  • Step 612 The first server 11 receives a registration request from the terminal device 12, where the registration request includes registration information.
  • Step 613 The first server 11 obtains the access information of the terminal device 12.
  • Step 614 Determine whether the access information of the terminal device 12 meets the access conditions.
  • Step 615 The first server 11 sends response information to the terminal device 12.
  • the response information is used to indicate that the access information of the terminal device 12 meets the access conditions.
  • Step 616 The terminal receiver 12 receives the response information sent by the first server 11.
  • Step 617 The terminal device 12 sends a key request to the first server 11.
  • the key request is used to request the first key; wherein, the registration time of the terminal device 12 is related to the time when the terminal device 12 sends the key request.
  • Step 618 The first server 11 receives the key request sent by the terminal device 12.
  • Step 619 The first server 11 generates a first key based on the registration time of the terminal device 12, the identification information of the terminal device 12, and the fingerprint information of the terminal device 12.
  • the fingerprint information is related to the time when the application is installed on the terminal device.
  • Step 620 The first server uses the second key to encrypt the first key.
  • the first key and the second key are different.
  • the second key is generated through a hash operation based on the first salt value information, the fingerprint information of the terminal device, and the registration time of the terminal device.
  • Step 621 The first server 11 sends the encrypted first key to the terminal device 12.
  • Step 622 The terminal device 12 receives the encrypted first key.
  • Step 623 The terminal device 12 uses the second key to decrypt the encrypted first key to obtain the first key.
  • the security management method also includes: the first server 11 obtains and stores the identification information and registration information of the terminal device 12 .
  • the identification information of the terminal device 12 includes the MAC address and/or IMEI of the terminal device 12 .
  • the terminal device 12 The registration information includes the fingerprint information of the terminal device 12; the access information of the terminal device 12 satisfies the access conditions, including: the registration information of the terminal device stored by the first server includes the same fingerprint as the fingerprint information in the access information of the terminal device. information.
  • the security management method further includes: the terminal device 12 generates a third key through a hash operation based on the fingerprint information of the terminal device 12 and the second salt value information; the terminal device 12 uses the third key to pair the first password.
  • the key is encrypted and the encrypted first key is stored.
  • the security management method also includes: if the terminal device 12 reinstalls the application or the terminal device is refreshed, the terminal device 12 re-sends access information to the first server 11 .
  • the security management method further includes: the terminal device 12 based on the identification information of the terminal device 12 , the hardware information of the terminal device 12 , the information of the application program installed by the terminal device 12 , and the time when the terminal device 12 installed the application program. At least one item uses a hash algorithm to generate fingerprint information of the terminal device.
  • the security management method also includes: when the number of abnormal accesses of the terminal device 12 is greater than or equal to the threshold number, the first server 11 adds the terminal device 12 to the blacklist; wherein the abnormal access includes access information of the terminal device 12 Access conditions are not met.
  • Figure 7 provides another security management method according to an embodiment of the present disclosure. As shown in Figure 7, the security management method includes steps 71 to 76.
  • Step 71 The second server 20 uses the public key corresponding to the supplier to encrypt the access information and obtains the access request.
  • the second server 20 is a server of the supplier, and the access information includes the identification information of the second server 20 and the access request time.
  • Step 72 The second server 20 sends an access request to the gateway 13.
  • Step 73 Gateway 13 receives the access request.
  • Step 74 The gateway 13 uses the private key corresponding to the supplier to decrypt the access request and obtain the access information.
  • Step 75 The gateway 13 sends an access request to the first server 11 corresponding to the supplier based on the access information.
  • Step 76 The first server 11 receives the access request sent by the gateway 13.
  • the security management method further includes: the gateway 13 receives an encrypted access request sent from the terminal device 12, where the encrypted access request includes first encrypted information and second encrypted information.
  • the gateway 13 uses the private key corresponding to the public key to decrypt the first encrypted information to obtain the first information.
  • the gateway 13 sends the second encrypted information to the first server based on the first information.
  • the first server 11 receives the second encrypted information, uses the first key to decrypt the second encrypted information, and obtains the second information.
  • the first encrypted information is obtained by the terminal device 12 encrypting the first information in the access request using a public key; the second encrypted information is obtained by the terminal device 12 using the first key to encrypt the second information in the access request. .
  • Some embodiments of the present disclosure provide a computer-readable storage medium (e.g., a non-transitory computer-readable storage medium) having computer program instructions stored therein, and the computer program instructions are stored in a computer (e.g., a secure computer).
  • a computer e.g., a secure computer
  • the computer When running on the management system), the computer is caused to execute the security management method described in any of the above embodiments.
  • the above-mentioned computer-readable storage media may include, but are not limited to: magnetic storage devices (such as hard disks, floppy disks or tapes, etc.), optical disks (such as CD (Compact Disk, compressed disk), DVD (Digital Versatile Disk, etc.) Digital versatile disk), etc.), smart cards and flash memory devices (e.g., EPROM (Erasable Programmable Read-Only Memory, Erasable Programmable Read-Only Memory), cards, sticks or key drives, etc.).
  • the various computer-readable storage media described in this disclosure may represent one or more devices and/or other machine-readable storage media for storing information.
  • the term "machine-readable storage medium" may include, but is not limited to, wireless channels and various other media capable of storing, containing and/or carrying instructions and/or data.
  • Some embodiments of the present disclosure also provide a computer program product, for example, the computer program product is stored on a non-transitory computer-readable storage medium.
  • the computer program product includes computer program instructions.
  • the computer program instructions When the computer program instructions are executed on a computer (for example, a security management system), the computer program instructions cause the computer to execute the security management method as described in the above embodiments.
  • Some embodiments of the present disclosure also provide a computer program.
  • the computer program When the computer program is executed on a computer (for example, a security management system), the computer program causes the computer to execute the security management method as described in the above embodiment.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Telephonic Communication Services (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

一种安全管理系统，所述安全管理系统包括第一服务器。所述第一服务器，被配置为：获取终端设备的接入信息。若终端设备的接入信息满足接入条件，基于终端设备的注册时间、终端设备的标识信息和终端设备的指纹信息，生成第一密钥。采用第二密钥对第一密钥进行加密，该第一密钥和第二密钥不同。向终端设备发送加密后的第一密钥，以使终端设备采用第二密钥对加密后的第一密钥进行解密。

Description

安全管理系统及安全管理方法 技术领域
本公开涉及安全领域，尤其涉及一种安全管理系统及安全管理方法。
背景技术
在银行智慧网点建设中，移动终端需要接入到银行的内网，从而对相应的银行应用服务进行访问。由于银行的内网无法提供无线网络的投放，因此，移动终端需要通过互联网接入到银行内网。但是，移动终端通过互联网接入银行内网是存在一定安全隐患的。
发明内容
一方面，提供一种安全管理系统。该安全管理系统包括第一服务器。第一服务器被配置为：获取终端设备的接入信息。若终端设备的接入信息满足接入条件，基于终端设备的注册时间、终端设备的标识信息和终端设备的指纹信息，生成第一密钥；其中，指纹信息与终端设备安装应用程序的时间有关。采用第二密钥对第一密钥进行加密，该第一密钥和第二密钥不同。向终端设备发送加密后的第一密钥，以使终端设备采用第二密钥对加密后的第一密钥进行解密。
在一些实施例中，该安全管理系统还包括：网关，该网关被配置为：接收来自第二服务器的访问请求，该第二服务器为供应商的服务器，该访问请求包括访问信息，第二服务器采用供应商对应的公钥对访问信息进行加密，访问信息包括第二服务器的标识信息、访问请求时间。采用供应商对应的私钥对访问请求进行解密，得到访问信息。基于访问信息向供应商对应的第一服务器发送访问请求。
在一些实施例中，网关还被配置为：接收来自终端设备发送的加密后的访问请求，加密后的访问请求包括第一加密信息和第二加密信息，采用公钥对应的私钥对第一加密信息进行解密，得到第一信息。根据第一信息，将第二加密信息发送给第一服务器。第一服务器还被配置为：接收第二加密信息，采用第一密钥对第二加密信息进行解密，得到第二信息。其中，第一加密信息为终端设备采用公钥对访问请求中的第一信息进行加密得到的；第二加密信息为终端设备采用第一密钥对访问请求中的第二信息进行加密得到。
在一些实施例中，该安全管理系统中，第一服务器还被配置为：获取并存储终端设备的标识信息和注册信息，终端设备的标识信息包括终端设备的介质访问控制地址和/或国际移动设备识别码，所述终端设备的注册信息包括 所述终端设备的指纹信息。终端设备的接入信息满足接入条件，包括：第一服务器存储的至少一个终端设备的注册信息包括与终端设备的接入信息中的指纹信息相同的指纹信息。
在一些实施例中，该安全管理系统中，第一服务器还被配置为：向终端设备发送响应信息，响应信息用于指示终端设备的接入信息满足接入条件。接收来自终端设备的密钥请求，该密钥请求用于请求第一密钥；其中，终端设备的注册时间与终端设备发送密钥请求的时间有关。
在一些实施例中，该安全管理系统还包括：终端设备，该终端设备被配置为：向第一服务器发送接入信息。接收加密后的第一密钥，并采用第二密钥对加密后的第一密钥进行解密，得到第一密钥。其中，第二密钥基于第一盐值信息、终端设备的指纹信息和终端设备的注册时间，通过哈希运算生成的。
在一些实施例中，终端设备还被配置为：若终端设备重新安装应用程序或终端设备刷机后，终端设备重新向第一服务器发送接入信息。
在一些实施例中，该安全管理系统中，终端设备还被配置为：基于终端设备的指纹信息和第二盐值信息，通过哈希运算生成第三密钥。采用第三密钥对第一密钥进行加密，并存储加密后的第一密钥。
在一些实施例中，该安全管理系统中，终端设备还被配置为：基于终端设备的标识信息、终端设备的硬件信息、终端设备安装的应用程序的信息、终端设备安装应用程序的时间，采用哈希算法生成终端设备的指纹信息。
在一些实施例中，该安全管理系统中，第一服务器还被配置为：在终端设备异常访问次数大于或等于阈值次数时，将终端设备加入黑名单；其中，异常访问包括终端设备的接入信息不满足接入条件。
另一方面，提供一种安全管理方法。所述安全管理方法包括：第一服务器获取终端设备的接入。若终端设备的接入信息满足接入条件，第一服务器基于终端设备的注册时间、终端设备的标识信息和终端设备的指纹信息，生成第一密钥；其中，指纹信息与终端设备安装应用程序的时间有关。第一服务器采用第二密钥对第一密钥进行加密，该第一密钥和所述第二密钥不同。第一服务器向终端设备发送加密后的第一密钥，以使终端设备采用第二密钥对加密后的第一密钥进行解密。
在一些实施例中，该安全管理方法，还包括：网关接收来自第二服务器的访问请求，第二服务器为供应商的服务器，访问请求包括访问信息，第二服务器采用供应商对应的公钥对访问信息进行加密，访问信息包括所述第二 服务器的标识信息和访问请求时间。网关采用供应商对应的私钥对访问请求进行解密，得到访问信息。网关基于访问信息向供应商对应的第一服务器发送访问请求。
在一些实施例中，该安全管理方法，还包括：网关接收来自终端设备发送的加密后的访问请求，加密后的访问请求包括第一加密信息和第二加密信息。网关采用公钥对应的私钥对第一加密信息进行解密，得到第一信息。网关根据第一信息，将第二加密信息发送给第一服务器。第一服务器接收第二加密信息，采用第一密钥对第二加密信息进行解密，得到第二信息。其中，第一加密信息为终端设备采用公钥对访问请求中的第一信息进行加密得到的；第二加密信息为终端设备采用第一密钥对访问请求中的第二信息进行加密得到。
在一些实施例中，该安全管理方法，还包括：第一服务器获取并存储终端设备的标识信息和注册信息，终端设备的标识信息包括终端设备的介质访问控制地址和/或国际移动设备识别码，终端设备的注册信息包括终端设备的指纹信息。其中，终端设备的接入信息满足接入条件，包括：第一服务器存储的至少一个终端设备的注册信息包括与终端设备的接入信息中的指纹信息相同的指纹信息。
在一些实施例中，该安全管理方法，还包括：第一服务器向终端设备发送响应信息，响应信息用于指示终端设备的接入信息满足接入条件。第一服务器接收来自终端设备的密钥请求，密钥请求用于请求第一密钥。其中，终端设备的注册时间与终端设备发送密钥请求的时间有关。
在一些实施例中，该安全管理方法，还包括：终端设备向第一服务器发送接入信息。终端设备接收加密后的第一密钥，并采用第二密钥对加密后的第一密钥进行解密，得到第一密钥。其中，第二密钥基于第一盐值信息、终端设备的指纹信息和终端设备的注册时间，通过哈希运算生成的。
在一些实施例中，该安全管理方法，还包括：若终端设备重新安装应用程序或终端设备刷机后，终端设备重新向第一服务器发送接入信息。
在一些实施例中，该安全管理方法，还包括：终端设备基于终端设备的指纹信息和第二盐值信息，通过哈希运算生成第三密钥。终端设备采用第三密钥对第一密钥进行加密，并存储加密后的第一密钥。
在一些实施例中，该安全管理方法，还包括：终端设备基于终端设备的标识信息、终端设备的硬件信息、终端设备安装的应用程序的信息、终端设备安装应用程序的时间，采用哈希算法生成终端设备的指纹信息。
再一方面，提供一种非暂态计算机可读存储介质。所述非暂态计算机可读存储介质存储计算机程序指令，所述计算机程序指令在计算机(例如，安全管理系统)上运行时，使得所述计算机执行如上述任一实施例所述的安全管理方法。
又一方面，提供一种计算机程序产品。所述计算机程序产品包括计算机程序指令，在计算机(例如，安全管理系统)上执行所述计算机程序指令时，所述计算机程序指令使计算机执行如上述任一实施例所述的安全管理方法。
又一方面，提供一种计算机程序。当所述计算机程序在计算机(例如，安全管理系统)上执行时，所述计算机程序使计算机执行如上述任一实施例所述的安全管理方法。
附图说明
为了更清楚地说明本公开中的技术方案，下面将对本公开一些实施例中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本公开的一些实施例的附图，对于本领域普通技术人员来讲，还可以根据这些附图获得其他的附图。此外，以下描述中的附图可以视作示意图，并非对本公开实施例所涉及的产品的实际尺寸、方法的实际流程、信号的实际时序等的限制。
图1为根据一些实施例的一种安全管理系统的示意图；
图2为根据一些实施例的另一种安全管理系统的示意图；
图3为根据一些实施例的一种安全管理系统的信息交互过程的示意图；
图4为根据一些实施例的一种网关加密过程的示意图；
图5为根据一些实施例的又一种安全管理系统的示意图；
图6为根据一些实施例的一种安全管理方法的流程图；
图7为根据一些实施例的另一种安全管理方法的流程图。
具体实施方式
下面将结合附图，对本公开一些实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本公开一部分实施例，而不是全部的实施例。基于本公开所提供的实施例，本领域普通技术人员所获得的所有其他实施例，都属于本公开保护的范围。
除非上下文另有要求，否则，在整个说明书和权利要求书中，术语“包括(comprise)”及其其他形式例如第三人称单数形式“包括(comprises)”和现在分词形式“包括(comprising)”被解释为开放、包含的意思，即为“包 含，但不限于”。在说明书的描述中，术语“一个实施例(one embodiment)”、“一些实施例(some embodiments)”、“示例性实施例(exemplary embodiments)”、“示例(example)”、“特定示例(specific example)”或“一些示例(some examples)”等旨在表明与该实施例或示例相关的特定特征、结构、材料或特性包括在本公开的至少一个实施例或示例中。上述术语的示意性表示不一定是指同一实施例或示例。此外，所述的特定特征、结构、材料或特点可以以任何适当方式包括在任何一个或多个实施例或示例中。
以下，术语“第一”、“第二”仅用于描述目的，而不能理解为指示或暗示相对重要性或者隐含指明所指示的技术特征的数量。由此，限定有“第一”、“第二”的特征可以明示或者隐含地包括一个或者更多个该特征。在本公开实施例的描述中，除非另有说明，“多个”的含义是两个或两个以上。
在描述一些实施例时，可能使用了“耦接”和“连接”及其衍伸的表达。例如，描述一些实施例时可能使用了术语“连接”以表明两个或两个以上部件彼此间有直接物理接触或电接触。又如，描述一些实施例时可能使用了术语“耦接”以表明两个或两个以上部件有直接物理接触或电接触。然而，术语“耦接”或“通信耦合(communicatively coupled)”也可能指两个或两个以上部件彼此间并无直接接触，但仍彼此协作或相互作用。这里所公开的实施例并不必然限制于本文内容。
“A、B和C中的至少一个”与“A、B或C中的至少一个”具有相同含义，均包括以下A、B和C的组合：仅A，仅B，仅C，A和B的组合，A和C的组合，B和C的组合，及A、B和C的组合。
“A和/或B”，包括以下三种组合：仅A，仅B，及A和B的组合。
如本文中所使用，根据上下文，术语“如果”任选地被解释为意思是“当……时”或“在……时”或“响应于确定”或“响应于检测到”。类似地，根据上下文，短语“如果确定……”或“如果检测到[所陈述的条件或事件]”任选地被解释为是指“在确定……时”或“响应于确定……”或“在检测到[所陈述的条件或事件]时”或“响应于检测到[所陈述的条件或事件]”。
本文中“适用于”或“被配置为”的使用意味着开放和包容性的语言，其不排除适用于或被配置为执行额外任务或步骤的设备。
另外，“基于”的使用意味着开放和包容性，因为“基于”一个或多个所述条件或值的过程、步骤、计算或其他动作在实践中可以基于额外条件或超出所述的值。
随着银行智慧网点的建设，银行网点为终端设备所提供的应用服务越来 越多。终端设备需要通过无线网接入方式接入到银行内网，但是银行内网无法提供无线网，因而，移动终端通过互联网接入到银行内网，从而访问相关的应用服务，这为银行内网的安全性带来挑战。目前，在终端设备通过互联网接入银行内网的方案中，大部分只考虑到了数据传输过程的安全防护，没有考虑整个链路上的安全，使得终端设备接入银行内网过程存在一定的安全隐患。
为此，本公开实施例提供一种全链路的安全接入方案，对终端设备接入、终端设备与银行内网之间信息交互、供应商与银行内网之间信息交互等过程都进行安全防护，加强对银行内网的安全管控。
图1为本公开实施例提供的一种安全管理系统的示意图。如图1所示，安全管理系统10包括第一服务器11。
第一服务器11为部署在内部网络环境(也称为内网)的服务器，内部网络环境可以为任意区域部署的网络环境，本公开实施例以银行内网为例进行示例性说明。例如，第一服务器11可以为部署在银行内网的服务器，第一服务器11上可以部署有各种应用程序(application，APP)。
第一服务器11的数量可以为一台，也可以为多台；第一服务器11可以为物理服务器，也可以为虚拟服务器；本公开实施例对第一服务器11的类型和数量不作限定。
在一些实施例中，如图1所示，安全管理系统10还包括终端设备12。
终端设备12，例如包括手机、笔记本电脑、平板电脑(如PAD设备)、智能可穿戴设备(如手表)等。终端设备12可以为一台，也可以为多台，本公开实施例对接入银行内网的终端设备12的类型和数量不作限定。
终端设备12接入到银行内网后，可以访问到第一服务器11上部署的应用服务。例如，当PAD接入到银行内网后，用户(例如，银行管理人员)可以通过PAD上安装的相关APP，进行相关业务办理或信息查询。
在一些实施例中，终端设备12被配置为：向第一服务器11发送注册请求，该注册请求包括注册信息。
第一服务器被配置为：接收来自终端设备12的注册请求。
在一些实施例中，第一服务器11还被配置为：获取并存储终端设备12的标识信息和注册信息。
示例性地，终端设备12的标识信息为终端设备12可以被唯一识别的信息，终端设备12的标识信息包括但不限于：终端设备12的介质访问控制地址(Media Access Control Address，MAC)和/或国际移动设备识别码 (International Mobile Equipment Identity，IMEI)。
第一服务器11获取终端设备12的标识信息，包括：第一服务器11对终端设备12的标识信息进行录入。第一服务器11获取到终端设备12的标识信息后，会对该标识信息进行存储。
如图2所示，银行内网的第一服务器11上部署有管控平台23，管控平台23用于对终端设备12(例如包括手表设备21和PAD设备22)接入第一服务器11的过程进行管理。管控平台23还用于对银行网点设备，如网点设备24、网点设备25、网点设备26进行管理。在终端设备12接入第一服务器11之前，可以将终端设备12的标识信息录入到管控平台23。例如，可以通过人工录入的方式对终端设备12的标识信息进行录入。当管控平台23中录入了终端设备12的标识信息后，第一服务器11存储该终端设备12的标识信息。
在完成终端设备12的标识信息录入后，终端设备12可以进行设备注册。只有完成设备注册的终端设备12才有接入第一服务器11的权限。示例性地，终端设备12进行设备注册的前提是第一服务器11中存储了该终端设备12的标识信息。
需要说明的是，终端设备12在进行设备注册之前，需要预先完成相关APP的下载和安装，以Android应用程序包(Android application package，APK)为例，用户在终端设备12上下载并安装好APK后，终端设备12会对其网络接入情况检查，以检查该终端设备12是否已接入到第一服务器11。若检查结果为该终端设备12还未接入到第一服务器11，则继续完成设备注册过程。
终端设备12进行设备注册可以在完成标识信息录入之后的任何时间完成，如可以在标识信息录入后立即进行，也可以在标识信息录入后的一段时间后进行。
终端设备12进行设备注册包括，终端设备12向第一服务器11发送注册请求。如图3所示，终端设备12通过调用注册接口31向第一服务器11发送注册请求，注册请求中包括注册信息。
示例性地，终端设备12的注册信息包括终端设备12的标识信息、终端设备12的指纹信息、终端设备12安装的APP的版本信息等。
当终端设备12向第一服务器11发送注册请求后，第一服务器11接收该注册请求，同时获取终端设备12的注册信息。由于注册信息中包括终端设备12的标识信息，第一服务器11获取到该发送注册请求的终端设备12的标识信息后，验证该标识信息是否存储在第一服务器11中。也就是说，第一服务器11需要验证该发送注册请求的终端设备12是否是为已完成标识信息录入 的终端设备12。若第一服务器11中存储了该发送注册请求的终端设备12的标识信息，则表明该终端设备12为已录入的终端设备，这种情况下，该终端设备12才有继续进行设备注册的权限。
若第一服务器11中存储了该发送注册请求的终端设备12的标识信息，第一服务器11对获取到的终端设备12的注册信息进行存储。如图2所示，管控平台23将接收到的终端设备12的注册信息对应更新至第一服务器11中该终端设备12的信息中。也就是说，此时，第一服务器11中存储了终端设备12对应的标识信息、指纹信息等。
在一些实施例中，终端设备12的指纹信息是终端设备12基于终端设备12的标识信息、终端设备12的硬件信息、终端设备12安装的APP的信息以及终端设备12安装APP的时间，采用哈希(Hash)算法得到的。
需要说明的是，终端设备12的硬件信息可以为终端设备12上不容易改变的信息，如终端设备12的设备型号信息、存储空间信息等。终端设备12安装APP的时间包括终端设备12第一次安装APP的时间，或者终端设备12重新安装APP的时间。例如，当终端设备12卸载并重新安装该APP时，终端设备12安装的APP的信息和安装APP的时间都发生了改变，因而终端设备12的指纹信息也会发生改变，这种情况下，终端设备12会重新向第一服务器11发送新的注册请求，第一服务器11重新获取该终端设备12的新的注册信息，该新的注册信息中包括了新的指纹信息。
示例性地，本公开实施中的哈希算法可以采用MD 5(Message-Digest 5)算法，也可采用其他哈希算法，如SHA 1算法、SHA 256算法等，本公开实施例对哈希算法的类型不作限定。
当第一服务器11对终端设备12的标识信息验证通过，并获取到该终端设备的注册信息后，终端设备12可以开始接入到第一服务器11。
第一服务器11还被配置为：获取终端设备12的接入信息，判断终端设备12的接入信息是否满足接入条件；若终端设备12的接入信息满足接入条件，基于终端设备12的注册时间、终端设备12的标识信息和终端设备12的指纹信息，生成第一密钥。
在一些实施例中，终端设备12接入信息满足接入条件，包括：第一服务器11中存储的至少一个终端设备的注册信息包括与终端设备12的接入信息中的指纹信息相同的指纹信息。
在终端设备12第一次接入第一服务器11时，第一服务器11会对终端设备12进行设备审核。本公开实施例对第一服务器11的审核终端设备12的方 式不作限定。例如，可以采用人工审核的方式，又或者，可以采用系统自动审核的方式。示例性地，第一服务器11对终端设备12的设备审核包括：检查终端设备12的接入信息是否满足接入条件，若满足接入条件，则审核通过，否则审核不通过。
需要说明的是，终端设备12的接入信息为终端设备12接入第一服务器11时，向第一服务器11发送的终端设备12的接入信息，该接入信息可以包括待接入终端设备12的标识信息、指纹信息等。第一服务器11接收到该待接入终端设备12的接入信息后，根据该接入信息，判断该待接入终端设备12是否为第一服务器11中已存储的某一台终端设备。
由于第一服务器11中存储了已完成标识信息录入的一个或多个终端设备的注册信息，因而，第一服务器11可以通过检查第一服务器11存储的指纹信息中是否包括该待接入终端设备12的接入信息中的指纹信息，来判断待接入终端设备12是否有权限接入到第一服务器11。如果第一服务器11中存储的注册信息中的指纹信息包括了终端设备12的接入信息中的指纹信息，则终端设备12的接入信息满足接入条件，可以接入到第一服务器11，反之，则终端设备12的接入信息就不满足接入条件，因而也无法接入到第一服务器11。
如图2所示，当手表设备21接入第一服务器11时，管控平台23上可以看到手表设备21的接入信息(包括手表设备21的指纹信息)，管理员检查(或系统自动检查)该指纹信息与第一服务器11中存储的指纹信息是否匹配。若手表设备21的接入信息中的指纹信息与第一服务器11中存储的指纹信息匹配成功，则审核通过，手表设备21成功接入第一服务器11。若手表设备21的接入信息中的指纹信息与第一服务器11中存储的指纹信息匹配不成功，则审核失败，手表设备21无法接入第一服务器11。
如图3所示，终端设备12通过调用注册接口31向第一服务器11发送注册请求后，第一服务器11接收该注册请求，并对终端设备12进行设备审核。设备审核的结果包括审核通过和审核不通过，审核通过的终端设备12才能接入到第一服务器11，若审核不通过，第一服务器11向终端设备12返回异常信息。
在一些实施例中，终端设备12还被配置为：若终端设备12重新安装应用程序或终端设备12刷机后，终端设备12重新向第一服务器11发送所述接入信息。
示例性地，终端设备12注册成功后无法直接进行重复注册。当终端设备12重新安装APK或进行刷机等操作后，终端设备12会重新向第一服务器11 发送注册请求，重新进行设备注册。在此情况下，第一服务器11会对终端设备12的注册请求重新进行验证，并对终端设备12重新发送的接入信息重新进行审核。在终端设备12提出注册请求时，第一服务器11先检查该终端设备12的注册状态，若该终端设备12的注册状态为已注册，则第一服务器11在审核之前需要对终端设备12的注册状态进行清除，例如将注册状态改为未注册，这样，终端设备12才可以重新注册，并接入到第一服务器11。
第一服务器11还被配置为：向终端设备12发送响应信息，该响应信息用于指示终端设备12的接入信息满足接入条件。
终端设备12还被配置为：接收来自第一服务器11的响应信息，向第一服务器11发送密钥请求，该密钥请求用于请求第一密钥。示例性地，第一密钥是终端设备12和第一服务器11之间进行通信时，对通信报文进行加密的密钥。
第一服务器11还被配置为：接收来自终端设备12的密钥请求，该密钥请求用于请求第一密钥。
在终端设备12通过设备审核后，第一服务器11会向终端设备12发送响应信息，指示终端设备12已接入到第一服务器11。终端设备12在接收到第一服务器11发送的该响应信息后，向第一服务器11发送密钥请求，以请求对通信报文加密的第一密钥。
第一服务器11接收到终端设备12发送的密钥请求后，基于终端设备12的注册时间、终端设备12的标识信息和终端设备12的指纹信息，生成第一密钥。
在一些实施例中，终端设备12的注册时间与终端设备12向第一服务器11发送密钥请求的时间有关。
例如，终端设备12的注册时间可以为终端设备12向第一服务器11发送密钥请求的时间，或者，终端设备12的注册时间也可以为第一服务器11接收到终端设备12发送的密钥请求的时间。通过第一服务器11发送密钥请求的时间来确定终端设备12的注册时间，能够保证终端设备12在该注册时间时已经成功接入到第一服务器11。
示例性的，第一服务器11可以根据终端设备12的MAC地址或IMEI、终端设备12的指纹信息、终端设备12的注册时间以及终端设备12的审核信息(例如审核员信息、审核时间等)进行哈希运算得到第一密钥。由于第一密钥的生成因子中包括了终端设备12的指纹信息和注册时间，即第一密钥的生成机制既和终端设备12的指纹信息有关，又和时间因子有关，因此很难被 事后模仿和破解。也就是说，针对每台终端设备12，第一服务器11都会生成唯一的第一密钥，实现一机一密钥的动态分发机制。
第一服务器11生成第一密钥后，对第一密钥进行存储，同时向终端设备12下发第一密钥，以使第一服务器11和终端设备12通信时，分别采用第一密钥进行加解密，实现对称加密的加密机制。
第一服务器11还被配置为：采用第二密钥对第一密钥进行加密。
为了保证第一服务器11向终端设备12下发第一密钥的过程的安全性，第一服务器11可以采用第二密钥对第一密钥进行加密，并将加密后的第一密钥下发给终端设备12，从而保证第一密钥下发过程安全可靠。
第一服务器11在下发第一密钥时，先动态生成第二密钥，再用第二密钥对第一密钥进行加密，并向终端设备12发送加密后的第一密钥。由于第二密钥只有在第一服务器11下发第一密钥时会使用到，因而，在一些示例中，在完成第一密钥下发后，第一服务器11不会对第二密钥进行存储。
示例性地，第一服务器11可以采用盐值加密算法生成第二密钥。例如，第一服务器11可以对第一盐值信息、终端设备12的指纹信息、终端设备12的注册时间通过哈希运算得到第二密钥。其中，第一盐值信息可以为第一服务器11内部存储的一组字符串，或者为第一服务器11临时生成的一组字符串，本公开对第一盐值信息的具体内容不作限定。第二密钥的生成信息还可以包括终端设备的MAC地址、终端设备12的归属信息、终端设备12安装的APP的序列号ID等。例如，终端设备12的归属信息可以包括终端设备12所属地区的信息，或者终端设备12所属用户的信息等。
在一些实施例中，第二密钥与第一密钥不同。例如，第一密钥和第二密钥的生成因子不同，因而第二密钥与第一密钥不同；再例如，第二密钥的生成因子中包括盐值信息，而第一密钥的生成因子不包括盐值信息，因而第二密钥与第一密钥不同；又例如，第一密钥和第二密钥的生成因子中均包括盐值信息，但两个盐值信息不同，因而第二密钥与第一密钥不同。示例性地，当第一服务器11生成第二密钥后，若发现第二密钥与第一密钥相同，可以重新生成第二密钥。
第一服务器11还被配置为：向终端设备12发送加密后的第一密钥，以使终端设备12采用第二密钥对加密后的第一密钥进行解密。
如图3所示，当终端设备12通过设备审核后，第一服务器11会向终端设备12返回采用第二密钥加密后的第一密钥，终端设备12接收到该加密后的第一密钥后，解密并存储第一密钥。
示例性地，终端设备12接收到加密后的第一密钥，采用第二密钥对加密后的第一密钥进行解密，得到第一密钥。作为一种实现方式，终端设备12采用与第一服务器11相同的生成机制生成第二密钥，实现终端设备12和第一服务器11之间的对称加密机制，提高加密效率。与第一服务器11生成第二密钥的机制相同，终端设备12也可以基于第一盐值信息、终端设备12的指纹信息、终端设备12的注册时间，采用哈希运算得到第二密钥，保证第二密钥的一致性。需要说明的是，终端设备12中的第一盐值信息可以是第一服务器11发送给终端设备12的第一盐值信息(例如，第一服务器11可以对第一盐值信息加密后发送给终端设备12)，也可以是终端设备12采用与第一服务器11相同的生成机制生成的第一盐值信息。
终端设备12通过第二密钥解密得到第一密钥后，需要对第一密钥进行存储，用于后续与第一服务器11之间进行业务通信时对业务请求的加密。
如图3所示，终端设备12通过调用通信接口32向第一服务器11发送通过第一密钥加密后的业务请求，第一服务器11接收该加密后的业务请求并采用第一密钥解密业务请求，若解密成功，第一服务器11向终端设备12返回该业务请求对应的响应值；若解密失败，第一服务器11拒绝终端设备12的该业务请求。
为了进一步提高终端设备12本地存储第一密钥的安全性，在一些实施例中，终端设备12还被配置为：基于终端设备12的指纹信息，采用盐值算法生成第三密钥；采用第三密钥对第一密钥进行加密，并存储加密后的第一密钥。
示例性地，终端设备12可以对第二盐值信息、终端设备12的指纹信息进行哈希运算得到第三密钥。其中，第二盐值可以为终端设备12内部存储的一组字符串，或者为终端设备12临时生成的一组字符串。第二盐值信息与第一盐值信息不同。
作为一种实现方式，第三密钥的生成信息还可以包括终端设备的MAC地址、终端设备12的归属信息、终端设备12安装的APP的序列号ID等。第三密钥也可以由其他有效的加密策略生成。
终端设备12采用生成的第三密钥对第一密钥进行加密存储，保证了第一密钥的存储安全。当终端设备12需要调用第一密钥时，采用相同的生成机制生成第三密钥来进行解密，从而实现第三密钥的对称性。例如，当终端设备12生成第二盐值信息后，对第二盐值信息进行存储，当需要调用第一密钥时，根据第二盐值信息得到第三密钥进行解密。又或者，终端设备12可以采用相 同的生成机制再次生成相同的第二盐值信息，当需要调用第一密钥时，根据第二盐值信息得到第三密钥，从而保证第三密钥的一致性。
为了进一步保证第一密钥存储的安全性，终端设备12可以在经过预设时间后对第二盐值信息进行更换，从而保证第三密钥的动态管理。例如，终端设备12可以每隔一个月，重新生成第二盐值信息，从而重新生成第三密钥，采用新的第三密钥对第一密钥进行加密存储；再例如，终端设备12也可以不定期的重新生成第二盐值信息，从而重新生成第三密钥，采用新的第三密钥对第一密钥进行加密存储。
在一些实施例中，终端设备12还被配置为：采用加壳技术对终端设备12安装的应用程序进行安全防护。
对于终端设备12中安装的APP的程序本身的安全保护，本公开实施例采用安卓(android)的加壳技术来对终端设备12进行程序源码的保护，进一步加强对终端设备12的安全防护。例如，可以在该APP的程序的外面再包裹另外一段代码，从而保护里面的核心代码不会被非法修改。本公开实施例对该包裹的另一段代码不作限定。
在一些实施例中，第一服务器11还被配置为：在终端设备11异常访问次数大于或等于阈值次数时，将终端设备12加入黑名单；其中异常访问包括终端设备12的接入信息不满足接入条件。
示例性地，终端设备11异常访问第一服务器11可以包括：终端设备12连续多次向第一服务器11发送注册请求，且每次的接入信息都不满足接入条件；以及终端设备12已经接入到第一服务器11，并且在与第一服务器11进行通信的过程中，终端设备12连续异常调用第一服务器11的接口。在此情况下，若异常访问的次数超过阈值次数时，第一服务器11会限制终端设备12的访问请求。阈值次数可以根据需求进行设置，本公开实施例对阈值次数不作限定。例如，阈值次数为5时，当第一服务器11的访问接口被终端设备12连续异常调用的次数超过5次时，第一服务器11会将终端设备12加入黑名单，此时，终端设备12不能再访问第一服务器11。如果终端设备需要重新访问第一服务器11，则需要重新进行注册。通过异常监控的方式，能够防止攻击者采用试错的方式来对第一服务器11进行攻击。
在一些实施例中，第一服务器11可以采用超文本传输安全协议(Hyper Text Transfer Protocol over Secure Socket Layer，HTTPS)的接口通讯方式对信息传输的安全性进行加强。
示例性地，终端设备12在对第一服务器11的接口调用时，均需包括数 字签名，第一服务器11可以通过签名验证终端设备12的合法性。
综上，本公开实施例提供的安全管理系统10对终端设备12接入第一服务器11的过程进行严格的安全管控，通过终端设备12的指纹信息来对终端设备12进行设备审核，强化了终端设备12的安全认证和接入授权。其次，本公开实施例对终端设备12与第一服务器11之间数据传输过程进行了进一步的安全防护，相比于现有的加密过程存在的加密效率低，安全性低的问题，本公开实施例提供的安全管理系统10采用对称加密机制(例如，高级加密标准(Advanced Encryption Standard，AES)加密)实现终端设备12和第一服务器11之间第一密钥的分发、通信报文加密以及第一密钥的存储过程的加密，具有加密速度快，安全性更高的特点。同时，本公开实施例中终端设备12的接入过程需要授权，每台终端设备12获取第一密钥的过程是动态且唯一的，且第一密钥、第二密钥和第三密钥的生成机制都是与时间因子相关，因而，也很难被事后模仿和破解，保证了安全管理系统10的安全性。
本公开实施例对管理系统10的应用场景不作限定，下面以银行为例进行示例性说明。一般情况下，第一密钥、第二密钥和第三密钥的密钥体系是由为银行提供产品服务的供应商进行管理，银行一般通过代码安全扫描、代码管理或合同约束等手段来限制供应商，很难有效的管理和监控供应商对密钥的保密管理。
为此，本公开实施例提供的安全管理系统10中还包括网关。如图1所述，网关13可以为中心运行方式，由银行方统一管控。网关13用于对供应商发送的访问请求进行管理和监控，将筛查后的访问请求转发给对应的第一服务器11，从而保证对第一服务器11访问过程的安全。
在一些实施例中，网关13被配置为：接收来自第二服务器20的访问请求，第二服务器20为供应商的服务器，访问请求包括访问信息，第二服务器20采用供应商对应的公钥对访问信息进行加密，访问信息包括第二服务器20的标识信息、访问请求时间。
示例性地，第二服务器20为供应商的服务器，供应商通过第二服务器20为银行提供应用服务，该应用服务部署在银行内网的第一服务器11上。不同的应用服务可以由不同的供应商所提供的，也可以由同一个供应商提供。同一个供应商可以通过至少一台第二服务器20为银行提供应用服务，本公开实施例对供应商和第二服务器20的数量不作限定。
如图4所示，银行内网的应用服务：应用A、应用B、应用C分别由供应商A、供应商B和供应商C来提供，应用A、应用B、应用C可以部署在 同一台第一服务器11上，也可以分别部署在不同的第一服务器11上。例如，可以将不同供应商提供的应用部署在不同的第一服务器11上，实现不同供应商之间的物理隔离。
为了进一步提高供应商与网关13之间信息交互的安全性，第二服务器20与第一服务器11之间可以采用非对称加密的方式进行信息传输。其中，非对称加密算法中的私钥由银行方统一掌握和管理，公钥由各个供应商掌握。
在一些实施例中，不同供应商所对应的公钥不同，不同供应商对各自的公钥进行存储。示例性地，网关13中存储了各个供应商的第二服务器20的相关信息，该信息包括第二服务器20对应的私钥信息以及第二服务器20的标识信息等。本公开实施例对私钥的存储方式不作限定，例如可以采用如上述实施中的采用第三密钥进行加密存储方式来对该私钥进行存储。网关13可以分开对各个供应商所对应的私钥进行存储，进一步保证各个供应商的私钥的安全性。如图4所示，供应商A的公钥为公钥A，供应商B的公钥为公钥B，供应商C的公钥为公钥C，公钥A、公钥B、公钥C对应的私钥A、私钥B、私钥C均由网关13管理和存储。
第二服务器20向第一服务器11发出的访问请求统一调用网关13，访问请求包括访问信息。示例性地，访问信息可以包括供应商提供的应用服务的APP序列号(Serial ID)、访问请求时间、第二服务器20的标识信息(如第二服务器20的MAC地址)等，第二服务器20采用公钥对访问信息进行加密，并将加密后的访问请求发送给网关13。如图4所示，供应商A(即供应商A对应的第二服务器20)采用公钥A对发送的访问请求进行加密后，发送给网关13。
在一些实施例中，网关13还被配置为：采用供应商对应的私钥对访问请求进行解密，得到访问信息。
网关13接收第二服务器20发送的访问请求后，采用与该供应商的公钥所对应的私钥，对访问请求进行解密，得到访问信息。例如，第二服务器20发送的访问请求中可以包含了第二服务器20的设备IMIE号，网关13可以按照第二服务器20的IMEI号来对应存储私钥，那么当网关13接收到该访问请求时，可以根据该IMIE号查找对应的私钥，从而对访问请求中的访问信息进行解密。如图4所示，网关13在接收到供应商A发送的采用公钥A加密后的访问请求后，通过存储的私钥A对该加密后的访问请求进行解密，得到该访问请求，从而得到访问信息。
在一些实施例中，网关13还被配置为：基于访问信息向供应商对应的第 一服务器11发送访问请求。
访问信息中包括供应商的APP Serial ID，APP Serial ID能够确定供应商所提供的应用所对应的第一服务器11。因而，网关13可以根据APP Serial ID将第二服务器20发送的访问请求转发到对应的第一服务器11上。如图4所示，网关13将通过私钥A解密后得到的访问请求发送给供应商A对应的应用A。
网关13还可以根据访问请求时间和第二服务器20的MAC地址等信息对第二服务器20的访问进行管控。例如，可以通过网关13是否能够采用第二服务器20对应的私钥对第二服务器20发送的访问请求进行解密，来判断第二服务器20是否处于正常访问的状态。又或者，网关13对报文信息解密后，可以根据访问信息中的设备标识，与网关13中存储的第二服务器20的设备标识是否一致，来判断第二服务器20是否处于正常访问状态。若所述第二服务器20处于正常的访问状态，则将第二服务器20发送的访问请求转发给第一服务器11。
示例性地，网关13还可以对第二服务器20的异常访问次数进行监控，例如，当第二服务器20连续异常访问的次数大于或等于预设次数时，网关13可以禁止第二服务器20继续发送访问请求。
因此，本公开实施例提供的安全管理系统10，能够有效的控制供应商访问请求的内容、请求的次数，请求来源，对供应商的访问请求进行监控和预警，从而有效预防供应商因为管理不当等原因造成的安全机制的破坏。
示例性地，第二服务器20与网关13之间的非对称加密方式可以用于终端设备12与第一服务器11之间的业务通信。例如，可以在终端设备12与第一服务器11之间增加网关13。
在一些实施例中，网关13还被配置为：接收来自终端设备12发送的加密后的访问请求，加密后的访问请求包括第一加密信息和第二加密信息，采用公钥对应的私钥对第一加密信息进行解密，得到第一信息。根据第一信息，将第二加密信息发送给第一服务器11。第一服务器11还被配置为：接收第二加密信息，采用第一密钥对第二加密信息进行解密，得到第二信息。其中，第一加密信息为终端设备12采用公钥对访问请求中的第一信息进行加密得到的；第二加密信息为终端设备12采用第一密钥对访问请求中的第二信息进行加密得到。
作为一种实现方式，终端设备12向第一服务器11发送访问请求时，可以采用第一公钥对该访问请求中的部分信息进行加密，例如采用第一公钥对 访问请求中的第一信息进行加密；再采用第一密钥对该访问请求中的另一部分信息进行加密，例如，例如采用第一密钥对访问请求中的第二信息进行加密，从而实现终端设备12与第一服务器11之间通信的双层加密，进一步提高终端设备12与第一服务器11之间信息传输的安全性。需要说明的是，可以将采用第一公钥加密的方式称为网关加密方式，将采用第一密钥加密的方式称为平台策略加密方式。
示例性地，终端设备12向第一服务器11发送的访问请求中包括关键信息和业务信息。关键信息例如包括终端设备12的标识信息，访问请求发送时间、需要访问的APP的Serial ID等；业务信息例如包括终端设备12向第一服务器11发送的具体请求的信息。例如，第一信息包括关键信息，第二信息包括业务信息。终端设备12可以对访问请求中的关键信息采用第一公钥进行加密，对业务信息采用第一密钥进行加密，从而在进一步提升了终端设备12与第一服务器11之间信息传输的安全性的同时，采用第一公钥对信息量较少的关键信息进行加密，采用第一密钥对信息量较大的业务信息进行加密，也可以避免由第一公钥加密(非对称加密)带来的加密效率低的问题。
如图5所示，终端设备12与第一服务器11之间设置有网关13。当终端设备12与第一服务器11之间的进行业务通信时，终端设备12发送的访问请求包括信息A(关键信息)和信息B(业务信息)。终端设备12采用第一公钥对信息A进行网关加密，采用第一密钥对信息B进行平台策略加密，并将加密后的访问请求先向网关13发送。网关13接收来自终端设备12发送的加密后的访问请求后，采用与网关加密中第一公钥相对应的第一私钥对加密后的访问请求进行网关解密，得到信息A。然后，网关13根据信息A中的APP Serial ID将信息B转发给对应的第一服务器11。第一服务器11接收到加密后的信息B，采用第一密钥对加密后的信息B进行平台策略解密，得到信息B，也就是得到终端设备12发送的访问请求具体内容。第一服务器11向终端设备12发送访问请求的过程也是类似的，此处不在赘述。
图6为本公开实施例提供一种安全管理方法，如图6所示，安全管理方法包括步骤611到步骤623。
步骤611，终端设备12向第一服务器11发送注册请求。
步骤612，第一服务器11接收来自终端设备12的注册请求，注册请求包括注册信息。
步骤613，第一服务器11获取终端设备12的接入信息。
步骤614，判断终端设备12的接入信息是否满足接入条件。
若满足，继续执行步骤615。
步骤615，第一服务器11向终端设备12发送响应信息。
其中，该响应信息用于指示终端设备12的接入信息满足接入条件。
步骤616，终端接收12接收第一服务器11发送的响应信息。
步骤617，终端设备12向第一服务器11发送密钥请求。
该密钥请求用于请求第一密钥；其中，终端设备12的注册时间与终端设备12发送所述密钥请求的时间有关。
步骤618，第一服务器11接收终端设备12发送的密钥请求。
步骤619，第一服务器11基于终端设备12的注册时间、终端设备12的标识信息和终端设备12的指纹信息，生成第一密钥。
其中，指纹信息与终端设备安装应用程序的时间有关。
步骤620，第一服务器采用第二密钥对第一密钥进行加密。
其中，该第一密钥和第二密钥不同。第二密钥根据第一盐值信息、终端设备的指纹信息、终端设备的注册时间通过哈希运算生成。
步骤621，第一服务器11向终端设备12发送加密后的第一密钥。
步骤622，终端设备12接收加密后的第一密钥。
步骤623，终端设备12采用第二密钥对加密后的第一密钥进行解密，得到第一密钥。
在一些实施例中，安全管理方法还包括：第一服务器11获取并存储终端设备12的标识信息和注册信息，终端设备12的标识信息包括终端设备12的MAC地址和/或IMEI，终端设备12的注册信息包括终端设备12的指纹信息；终端设备12的接入信息满足接入条件，包括：第一服务器存储的终端设备的注册信息包括与终端设备的接入信息中的指纹信息相同的指纹信息。
在一些实施例中，安全管理方法还包括：终端设备12基于终端设备12的指纹信息和第二盐值信息通过哈希运算生成第三密钥；终端设备12采用第三密钥对第一密钥进行加密，并存储加密后的第一密钥。
在一些实施例中，安全管理方法还包括：若终端设备12重新安装应用程序或终端设备刷机后，终端设备12重新向第一服务器11发送接入信息。
在一些实施例中，安全管理方法还包括：终端设备12基于终端设备12的标识信息、终端设备12的硬件信息、终端设备12安装的应用程序的信息、终端设备12安装应用程序的时间中的至少一项，采用哈希算法生成终端设备的指纹信息。
在一些实施例中，安全管理方法还包括：在终端设备12异常访问次数大 于或等于阈值次数时，第一服务器11将终端设备12加入黑名单；其中，异常访问包括终端设备12的接入信息不满足接入条件。
图7为本公开实施例提供另一种安全管理方法，如图7所述，该安全管理方法包括步骤71到步骤76。
步骤71，第二服务器20采用供应商对应的公钥对访问信息加密，得到访问请求。
其中，第二服务器20为供应商的服务器，访问信息包括第二服务器20的标识信息和访问请求时间。
步骤72，第二服务器20向网关13发送访问请求。
步骤73，网关13接收访问请求。
步骤74，网关13采用供应商对应的私钥对访问请求进行解密，得到访问信息。
步骤75，网关13基于访问信息向供应商对应的第一服务器11发送访问请求。
步骤76，第一服务器11接收网关13发送的访问请求。
在一些实施例中，该安全管理方法，还包括：网关13接收来自终端设备12发送的加密后的访问请求，加密后的访问请求包括第一加密信息和第二加密信息。网关13采用公钥对应的私钥对第一加密信息进行解密，得到第一信息。网关13根据第一信息，将第二加密信息发送给第一服务器。第一服务器11接收第二加密信息，采用第一密钥对第二加密信息进行解密，得到第二信息。其中，第一加密信息为终端设备12采用公钥对访问请求中的第一信息进行加密得到的；第二加密信息为终端设备12采用第一密钥对访问请求中的第二信息进行加密得到。
本公开的一些实施例提供了一种计算机可读存储介质(例如，非暂态计算机可读存储介质)，该计算机可读存储介质中存储有计算机程序指令，计算机程序指令在计算机(例如，安全管理系统)上运行时，使得计算机执行如上述实施例中任一实施例所述的安全管理方法。
示例性的，上述计算机可读存储介质可以包括，但不限于：磁存储器件(例如，硬盘、软盘或磁带等)，光盘(例如，CD(Compact Disk，压缩盘)、DVD(Digital Versatile Disk，数字通用盘)等)，智能卡和闪存器件(例如，EPROM(Erasable Programmable Read-Only Memory，可擦写可编程只读存储器)、卡、棒或钥匙驱动器等)。本公开描述的各种计算机可读存储介质可代表用于存储信息的一个或多个设备和/或其它机器可读存储介质。术语“机 器可读存储介质”可包括但不限于，无线信道和能够存储、包含和/或承载指令和/或数据的各种其它介质。
本公开的一些实施例还提供了一种计算机程序产品，例如，该计算机程序产品存储在非瞬时性的计算机可读存储介质上。该计算机程序产品包括计算机程序指令，在计算机(例如，安全管理系统)上执行该计算机程序指令时，该计算机程序指令使计算机执行如上述实施例所述的安全管理方法。
本公开的一些实施例还提供了一种计算机程序。当该计算机程序在计算机(例如，安全管理系统)上执行时，该计算机程序使计算机执行如上述实施例所述的安全管理方法。
上述计算机可读存储介质、计算机程序产品及计算机程序的有益效果和上述一些实施例所述的安全管理方法的有益效果相同，此处不再赘述。
以上所述，仅为本公开的具体实施方式，但本公开的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本公开揭露的技术范围内，想到变化或替换，都应涵盖在本公开的保护范围之内。因此，本公开的保护范围应以所述权利要求的保护范围为准。

Claims (20)

  1. 一种安全管理系统，包括：
    第一服务器，被配置为：
    获取终端设备的接入信息；
    若所述终端设备的接入信息满足接入条件，基于所述终端设备的注册时间、所述终端设备的标识信息和所述终端设备的指纹信息，生成第一密钥，其中，所述指纹信息与所述终端设备安装应用程序的时间有关；
    采用第二密钥对所述第一密钥进行加密，所述第一密钥和所述第二密钥不同；
    向所述终端设备发送加密后的第一密钥，以使所述终端设备采用所述第二密钥对所述加密后的第一密钥进行解密。
  2. 根据权利要求1所述的安全管理系统，还包括：
    网关，被配置为：
    接收来自第二服务器的访问请求，所述第二服务器为供应商的服务器，所述访问请求包括访问信息，所述第二服务器采用所述供应商对应的公钥对所述访问信息进行加密，所述访问信息包括所述第二服务器的标识信息、访问请求时间；
    采用所述供应商对应的私钥对所述访问请求进行解密，得到所述访问信息；
    基于所述访问信息向所述供应商对应的所述第一服务器发送所述访问请求。
  3. 根据权利要求2所述的安全管理系统，其中，
    所述网关还被配置为：接收来自所述终端设备发送的加密后的访问请求，所述加密后的访问请求包括第一加密信息和第二加密信息，采用所述公钥对应的私钥对所述第一加密信息进行解密，得到第一信息；根据所述第一信息，将所述第二加密信息发送给所述第一服务器；
    其中，所述第一加密信息为所述终端设备采用所述公钥对所述访问请求中的第一信息进行加密得到的；所述第二加密信息为所述终端设备采用所述公钥对所述访问请求中的第二信息进行加密得到；
    所述第一服务器还被配置为：接收所述第二加密信息，采用所述第一密钥对所述第二加密信息进行解密，得到第二信息。
  4. 根据权利要求1-3中任一项所述的安全管理系统，其中，所述第一服务器，还被配置为：
    获取并存储所述终端设备的标识信息和注册信息，所述终端设备的标识信息包括所述终端设备的介质访问控制地址和/或国际移动设备识别码，所述终端设备的注册信息包括所述终端设备的指纹信息；
    所述终端设备的接入信息满足接入条件，包括：所述第一服务器存储的至少一个终端设备的注册信息包括与所述终端设备的接入信息中的指纹信息相同的指纹信息。
  5. 根据权利要求1-4中任一项所述的安全管理系统，其中，所述第一服务器，还被配置为：
    向所述终端设备发送响应信息，所述响应信息用于指示所述终端设备的接入信息满足所述接入条件；
    接收来自所述终端设备的密钥请求，所述密钥请求用于请求所述第一密钥；其中，所述终端设备的注册时间与所述终端设备发送所述密钥请求的时间有关。
  6. 根据权利要求1-5中任一项所述的安全管理系统，还包括：
    所述终端设备，被配置为：
    向所述第一服务器发送所述接入信息；
    接收所述加密后的第一密钥，并采用所述第二密钥对所述加密后的第一密钥进行解密，得到所述第一密钥；
    其中，所述第二密钥是基于第一盐值信息、所述终端设备的指纹信息和所述终端设备的注册时间，通过哈希运算生成的。
  7. 根据权利要求6所述的安全管理系统，其中，所述终端设备，还被配置为：
    若所述终端设备重新安装应用程序或所述终端设备刷机后，所述终端设备重新向所述第一服务器发送所述接入信息。
  8. 根据权利要求6所述的安全管理系统，其中，所述终端设备，还被配置为：
    基于所述终端设备的指纹信息和第二盐值信息，通过哈希运算生成第三密钥；
    采用所述第三密钥对所述第一密钥进行加密，并存储加密后的第一密钥。
  9. 根据权利要求1-8中任一项所述的安全管理系统，其中，所述终端设备，还被配置为：
    基于所述终端设备的标识信息、所述终端设备的硬件信息、所述终端设备安装的应用程序的信息、所述终端设备安装应用程序的时间，采用哈希算 法生成所述终端设备的指纹信息。
  10. 根据权利要求1-9中任一项所述的安全管理系统，其中，所述第一服务器，还被配置为：
    在所述终端设备异常访问次数大于或等于阈值次数时，将所述终端设备加入黑名单；其中，所述异常访问包括所述终端设备的接入信息不满足接入条件。
  11. 一种安全管理方法，包括：
    所述第一服务器获取终端设备的接入信息；
    若所述终端设备的接入信息满足接入条件，所述第一服务器基于所述终端设备的注册时间、所述终端设备的标识信息和所述终端设备的指纹信息，生成第一密钥，其中，所述指纹信息与所述终端设备安装应用程序的时间有关；
    所述第一服务器采用第二密钥对所述第一密钥进行加密，所述第一密钥和所述第二密钥不同；
    所述第一服务器向所述终端设备发送加密后的第一密钥，以使所述终端设备采用所述第二密钥对所述加密后的第一密钥进行解密。
  12. 根据权利要求11所述的安全管理方法，还包括：
    网关接收来自第二服务器的访问请求，所述第二服务器为供应商的服务器，所述访问请求包括访问信息，所述第二服务器采用所述供应商对应的公钥对所述访问信息进行加密，所述访问信息包括所述第二服务器的标识信息和访问请求时间；
    所述网关采用所述供应商对应的私钥对所述访问请求进行解密，得到所述访问信息；
    所述网关基于所述访问信息向所述供应商对应的所述第一服务器发送所述访问请求。
  13. 根据权利要求12所述的安全管理方法，还包括：
    所述网关接收来自所述终端设备发送的加密后的访问请求，所述加密后的访问请求包括第一加密信息和第二加密信息；
    所述网关采用所述公钥对应的私钥对所述第一加密信息进行解密，得到第一信息；
    所述网关根据所述第一信息，将所述第二加密信息发送给所述第一服务器；
    所述第一服务器接收所述第二加密信息；
    所述第一服务器采用所述第一密钥对所述第二加密信息进行解密，得到第二信息；
    其中，所述第一加密信息为所述终端设备采用所述公钥对所述访问请求中的第一信息进行加密得到的；所述第二加密信息为所述终端设备采用所述第一密钥对所述访问请求中的第二信息进行加密得到。
  14. 根据权利要求11-13中任一项所述的安全管理方法，还包括：
    所述第一服务器获取并存储所述终端设备的标识信息和注册信息，所述终端设备的标识信息包括所述终端设备的介质访问控制地址和/或国际移动设备识别码，所述终端设备的注册信息包括所述终端设备的指纹信息；
    其中，所述终端设备的接入信息满足接入条件，包括：所述第一服务器存储的至少一个终端设备的注册信息包括与所述终端设备的接入信息中的指纹信息相同的指纹信息。
  15. 根据权利要求11-14中任一项所述的安全管理方法，还包括：
    所述第一服务器向所述终端设备发送响应信息，所述响应信息用于指示所述终端设备的接入信息满足所述接入条件；
    所述第一服务器接收来自所述终端设备的密钥请求，所述密钥请求用于请求所述第一密钥；其中，所述终端设备的注册时间与所述终端设备发送所述密钥请求的时间有关。
  16. 根据权利要求11-15中任一项所述的安全管理方法，还包括：
    所述终端设备向所述第一服务器发送所述接入信息；
    所述终端设备接收所述加密后的第一密钥，并采用所述第二密钥对所述加密后的第一密钥进行解密，得到所述第一密钥；
    其中，所述第二密钥是基于第一盐值信息、所述终端设备的指纹信息和所述终端设备的注册时间，通过哈希运算生成的。
  17. 根据权利要求16所述的安全管理方法，还包括：
    若所述终端设备重新安装应用程序或所述终端设备刷机后，所述终端设备重新向所述第一服务器发送所述接入信息。
  18. 根据权利要求16所述的安全管理方法，还包括：
    所述终端设备基于所述终端设备的指纹信息和第二盐值信息，通过哈希运算生成第三密钥；
    所述终端设备采用所述第三密钥对所述第一密钥进行加密，并存储加密后的第一密钥。
  19. 根据权利要求11-18中任一项所述的安全管理方法，还包括：
    所述终端设备基于所述终端设备的标识信息、所述终端设备的硬件信息、所述终端设备安装的应用程序的信息、所述终端设备安装应用程序的时间，采用哈希算法生成所述终端设备的指纹信息。
  20. 一种非暂态计算机可读存储介质，所述非暂态计算机可读存储介质存储计算机程序指令，所述计算机程序指令被所述安全管理系统执行时实现如权利要11-19中任一项所述的安全管理方法。
PCT/CN2022/115847 2022-08-30 2022-08-30 安全管理系统及安全管理方法 WO2024044965A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202280002935.6A CN117957813A (zh) 2022-08-30 2022-08-30 安全管理系统及安全管理方法
PCT/CN2022/115847 WO2024044965A1 (zh) 2022-08-30 2022-08-30 安全管理系统及安全管理方法

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/115847 WO2024044965A1 (zh) 2022-08-30 2022-08-30 安全管理系统及安全管理方法

Publications (1)

Publication Number Publication Date
WO2024044965A1 true WO2024044965A1 (zh) 2024-03-07

Family

ID=90100134

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/115847 WO2024044965A1 (zh) 2022-08-30 2022-08-30 安全管理系统及安全管理方法

Country Status (2)

Country Link
CN (1) CN117957813A (zh)
WO (1) WO2024044965A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103906052A (zh) * 2012-12-26 2014-07-02 中国移动通信集团公司 一种移动终端认证方法、业务访问方法及设备
CN106101068A (zh) * 2016-05-27 2016-11-09 宇龙计算机通信科技(深圳)有限公司 终端通信方法及系统
CN111464486A (zh) * 2019-01-22 2020-07-28 阿里巴巴集团控股有限公司 信息交互方法、装置以及计算设备
CN111835752A (zh) * 2020-07-09 2020-10-27 国网山西省电力公司信息通信分公司 基于设备身份标识的轻量级认证方法及网关

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103906052A (zh) * 2012-12-26 2014-07-02 中国移动通信集团公司 一种移动终端认证方法、业务访问方法及设备
CN106101068A (zh) * 2016-05-27 2016-11-09 宇龙计算机通信科技(深圳)有限公司 终端通信方法及系统
CN111464486A (zh) * 2019-01-22 2020-07-28 阿里巴巴集团控股有限公司 信息交互方法、装置以及计算设备
CN111835752A (zh) * 2020-07-09 2020-10-27 国网山西省电力公司信息通信分公司 基于设备身份标识的轻量级认证方法及网关

Also Published As

Publication number Publication date
CN117957813A (zh) 2024-04-30

Similar Documents

Publication Publication Date Title
US9996679B2 (en) Methods and apparatus for device authentication and secure data exchange between a server application and a device
CN110120869B (zh) 密钥管理系统及密钥服务节点
TWI475899B (zh) 用以儲存電子存取用戶之設備及方法
EP3258663B1 (en) Verification method, apparatus and system for network application access
US20180082050A1 (en) Method and a system for secure login to a computer, computer network, and computer website using biometrics and a mobile computing wireless electronic communication device
US8978125B2 (en) Identity controlled data center
TWI791050B (zh) 資料傳輸方法及系統
TW201814496A (zh) 資料儲存方法、資料獲取方法、裝置及系統
CN110489996B (zh) 一种数据库数据安全管理方法及系统
US10824744B2 (en) Secure client-server communication
JP2015531928A (ja) セキュアな計算環境を提供するシステム及び方法
CN103731395A (zh) 文件的处理方法及系统
CN103973715B (zh) 一种云计算安全系统和方法
CN111130798B (zh) 一种请求鉴权方法及相关设备
US20220417241A1 (en) Methods, Systems, and Devices for Server Control of Client Authorization Proof of Possession
CN113395406B (zh) 一种基于电力设备指纹的加密认证方法及系统
JP2012191270A (ja) 認証システム、端末装置、認証サーバ、およびプログラム
CN104243452B (zh) 一种云计算访问控制方法及系统
JP2017152880A (ja) 認証システム、鍵処理連携方法、および、鍵処理連携プログラム
CN104767766A (zh) 一种Web Service接口验证方法、Web Service服务器、客户端
CN111585995A (zh) 安全风控信息传输、处理方法、装置、计算机设备及存储介质
CN107342963A (zh) 一种虚拟机安全控制方法、系统及网络设备
CN113647051A (zh) 用于安全电子数据传输的系统和方法
WO2024044965A1 (zh) 安全管理系统及安全管理方法
WO2022227799A1 (zh) 设备注册方法及装置、计算机设备、存储介质

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 202280002935.6

Country of ref document: CN

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22956797

Country of ref document: EP

Kind code of ref document: A1