A trusted authentication method and system for mobile terminal equipment based on the Internet of Things
By allocating unique identifiers and hardware fingerprint information in IoT devices, generating keys, designing SSL/TLS authentication protocols, selecting encryption algorithms, implementing device integrity checks and user multi-factor authentication, and deploying log management systems, traditional technology is solved The security issues of device identity authentication and communication encryption in the middle realize efficient and secure authentication and data transmission between devices and users.
Patent Information
- Application Number
- CN202410883962.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-03
- Publication Date
- 2024-11-22
- Estimated Expiration
- 2044-07-03
AI Technical Summary
Traditional device identity authentication and communication encryption have security and reliability problems, and are susceptible to password cracking and man-in-the-middle attacks, and device integrity is difficult to verify, resulting in unauthorized device access or data leakage, user identity theft, and lack of detailed Equipment activity recording and audit mechanisms increase the risk of system attack or abuse.
Through the IoT device management platform, each mobile terminal device is assigned unique identifiers and hardware fingerprint information, a key generation algorithm is used to generate asymmetric or symmetric keys, an authentication protocol based on SSL/TLS is designed, and AES or ECC encryption algorithm is selected. Implement device integrity checks and user multi-factor authentication, deploy log management systems and digital certificate management to ensure the security of device and user identity authentication and data transmission.
Effectively solve the problems of device identity authentication and secure communication, device integrity and user authentication, audit and management, enhance the security and reliability of the system, ensure the confidentiality and integrity of data and equipment, and promptly identify and respond to potential security incidents.
Smart Images

Figure CN118631570B_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the technical field of Internet of Things, and in particular to a trusted authentication method and system for mobile terminal equipment based on the Internet of Things. Background Art
[0002] With the rapid development of Internet of Things technology, security issues have become increasingly prominent. The widespread use of mobile terminal devices has made device identity recognition and data transmission security an important focus.
[0003] However, traditional device authentication methods usually rely on simple usernames and passwords, which are vulnerable to security threats such as password cracking and man-in-the-middle attacks. In addition, the use of communication encryption algorithms may have loopholes or weaknesses, making data susceptible to eavesdropping or tampering during transmission. Therefore, traditional device authentication and communication encryption have security and reliability issues, which may lead to unauthorized device access or communication data leakage; moreover, the difficulty in verifying the software and hardware integrity of the device may lead to the implantation of malicious software or device tampering, thereby endangering system security. The user authentication method is single and lacks security, which may lead to the theft or forgery of user identities, and then access to unauthorized resources or malicious operations; at the same time, there is a lack of detailed records and audit mechanisms for device activities, resulting in the inability to timely discover and track security incidents, increasing the risk of system attacks or abuse. Summary of the invention
[0004] In order to solve the above-mentioned technical problems, the present invention provides a method and system for trusted authentication of mobile terminal devices based on the Internet of Things.
[0005] The technical solution of the present invention is achieved in this way:
[0006] A trusted authentication method for a mobile terminal device based on the Internet of Things comprises the following steps:
[0007] S1. Assign device identity: Assign a unique identifier to each mobile terminal device through the IoT device management platform, and register its hardware fingerprint information, including device ID and MAC address, and track the identity of the device through these identifiers;
[0008] S2. Generate security keys: Use a key generation algorithm to generate a pair of asymmetric keys or a set of symmetric keys for each mobile terminal device, which are used for subsequent device authentication and communication encryption to ensure that the key distribution is random and unpredictable;
[0009] S3. Design authentication protocol: Design an authentication protocol suitable for mobile terminal devices based on the device capabilities and authentication requirements, adopt an authentication mechanism based on SSL / TLS, define the communication process and handshake mechanism between devices, and ensure encryption and identity authentication during the transmission process;
[0010] S4. Implement encryption technology: Select encryption algorithm AES or ECC to encrypt the communication data between devices to ensure the confidentiality and integrity of the data during transmission. The encryption process uses the previously generated security key;
[0011] S5. Perform device integrity check: Verify that the software and hardware of the mobile terminal device have not been modified without authorization through secure boot or remote authentication technology to ensure that the device is in a known and secure state;
[0012] S6. Verify user authentication: Deploy a user authentication mechanism that combines the device owner's identity verification information, including passwords or biometric data, to perform multi-factor authentication to ensure that only authorized users can operate the device;
[0013] S7. Implement permission control: Obtain the role information of devices and users, assign appropriate access rights to devices and users through access control lists or role-based access control, and restrict access to sensitive data and resources;
[0014] S8. Configure audit and log system: Deploy a log management system to record the authentication process and device activities in detail. Logs are used for monitoring, post-analysis and auditing, which helps identify potential security issues.
[0015] S9. Implement certificate issuance and management: Through the digital certificate management system, collaborate with the digital certificate issuing authority to issue digital certificates for mobile terminal devices and establish a trust chain. Digital certificates are used to strengthen the device's identity authentication process.
[0016] Preferably, S1 includes the following sub-steps:
[0017] S11. Assign device identifier: Generate a unique device ID for each mobile terminal device through the IoT device management platform to ensure that each device can be individually identified in the system;
[0018] S12. Record device hardware information: Use automated tools to read the MAC address, CPU model, memory size, and storage space hardware specifications of the terminal device to form a device hardware fingerprint;
[0019] S13. Register other device attributes: obtain the device type, serial number, firmware / software version, and associate this information with the device ID to build a complete device profile;
[0020] S14. Configure network information: Set the device to automatically report its network type and IP address network information when connected to the IoT platform to facilitate remote access and management of the device;
[0021] S15. Storage of location and status data: The device’s built-in GPS module positioning technology is used to regularly update the device’s location information and detect the device’s status information, including power level and operating status, and record it on the platform;
[0022] S16. Install security certificate: Push and install the security certificate to the device to facilitate encrypted communication of the device and to authenticate the legitimacy of the device;
[0023] S17. Set up a status monitoring mechanism: Build an equipment status monitoring system to capture and analyze the equipment's operating data in real time. If the equipment status is abnormal, trigger an early warning mechanism;
[0024] S18. Logs and operation records: Design a log system to capture the operation records of the device, including instruction execution and data transmission records, for auditing and troubleshooting;
[0025] S19. Implement subscription service management: Automatically assign appropriate services to devices based on device type and user needs, and monitor service status to ensure service continuity and reliability.
[0026] Preferably, S2 includes the following sub-steps:
[0027] S21. Select RSA as the asymmetric encryption algorithm through the cryptography library OpenSSL. If the library provides multiple algorithms, determine the most suitable algorithm based on performance and security requirements;
[0028] S22. Using the library function, obtain the currently recommended key length parameter, and for RSA, obtain its 2048-bit parameter setting;
[0029] S23. Use the random number generator and RSA algorithm in the cryptography library to generate an asymmetric key pair and determine whether the generation process meets the requirements of randomness and uniqueness;
[0030] S24. The private key is stored in a confidential area of the mobile terminal device through an encrypted storage mechanism, and a hardware security module HSM is used to prevent unauthorized access;
[0031] S25. Obtain the public key and send it to the server through the device registration process, so that in subsequent communications, the server can use the public key to verify the identity of the device or encrypt messages to the device;
[0032] S26. Select AES as the symmetric encryption algorithm and obtain a 256-bit key length setting to meet high security requirements;
[0033] S27. Generate a symmetric key using the CSPRNG in the cryptography library and determine whether the key meets the standards of randomness and uniqueness;
[0034] S28. The symmetric key is encrypted using the public key of the device through asymmetric encryption, and then the encrypted symmetric key is sent to the mobile terminal to ensure the security of the key distribution process;
[0035] S29. For the received encrypted symmetric key, the mobile terminal uses its private key to decrypt it and obtains the symmetric key, which is ready for device authentication and communication encryption.
[0036] Preferably, S3 includes the following sub-steps:
[0037] S31. Based on the processing capability of the mobile terminal device, adopt appropriate encryption algorithms and security parameter configurations to achieve effective execution of SSL / TLS operations, and select encryption algorithms that can run efficiently on the device and lightweight encryption algorithms to reduce processing delays;
[0038] S32. Obtain storage capacity information of the device to determine whether there is enough space to store the digital certificate and private key. If the storage space is insufficient, perform storage optimization, including compressing the certificate storage or using a smaller key size;
[0039] S33. Through the network connection test, determine whether the mobile terminal device can establish and maintain a stable data transmission connection. The network connection test result determines whether additional network optimization measures are needed, including adjusting the data packet size or selecting a more stable network protocol;
[0040] S34. Design a two-way authentication process where both the client and the server need to confirm each other's identity through mutual verification of digital certificates, including embedding certificate verification steps in the authentication protocol and determining the validity and credibility of the certificate chain;
[0041] S35. Implement certificate management strategies to ensure that digital certificates can be safely installed and updated on mobile devices, and that the devices have certificate management capabilities so that digital certificates can be updated in a timely manner before they expire or when they are revoked;
[0042] S36. Design access control mechanisms to allow only authenticated devices to obtain access rights to protected resources, and assign permissions and control resources to devices based on authentication results;
[0043] S37. For the handshake mechanism, formulate a process that adapts to the performance of mobile devices. From the client Hello to the server Finished message, each step takes into account efficiency and security. The algorithm selection during the handshake process affects the performance of the authentication protocol.
[0044] S38. During the communication process, use message authentication code MAC or digital signature to implement encryption and integrity protection measures to ensure the confidentiality and integrity of data;
[0045] S39. Select an efficient encryption algorithm and the latest TLS version. By testing the performance of different algorithms and protocol versions, determine the most suitable combination for mobile devices. The performance test results determine the encryption algorithm and TLS version that are ultimately adopted.
[0046] Preferably, S4 includes the following sub-steps:
[0047] S41. Based on the sensitivity and protection requirements of the communication data, if the data requires extremely high security, select the AES algorithm and use a 256-bit key; if the communicating parties need to use asymmetric encryption for secure key exchange and digital signature, select ECC and use an appropriate key length to ensure equivalent security strength;
[0048] S42. When using a high-quality random number generator to generate a key, if it is an AES symmetric key, ensure that the generated key is sufficiently random to prevent predictable attacks; if it is an ECC asymmetric key pair, generate a pair of private and public keys at the same time, the private key is highly confidential, and the public key is used to exchange encrypted information with other communication entities;
[0049] S43. When distributing keys through a secure channel, if an AES key is used, the security of the channel is guaranteed to prevent the key from being intercepted during transmission; if an ECC key is used, only the private key needs to be distributed securely, and the public key can be made public;
[0050] S44. After obtaining the key, keep the key safe through a secure storage mechanism. If it is an AES key, use a hardware security module HSM or other forms of secure storage; for ECC private keys, also use HSM or encrypted software storage containers to ensure that the private key is not accessed by unauthorized persons;
[0051] S45. When updating keys regularly, the keys are updated through an automated key management system. For AES keys, the keys are replaced periodically to avoid security risks caused by long-term use of the same key; for ECC keys, updating the private key also regenerates the corresponding public key and distributes it to relevant communication entities;
[0052] S46. When the key needs to be invalidated and destroyed, it should be processed through a professional key destruction program. For AES keys, ensure that the key is completely deleted from all systems and cannot be recovered; for ECC keys, destroy the private key to avoid any possible leakage;
[0053] S47. If the ECC algorithm is selected, the ECDH protocol is used for key negotiation, and the shared key material is obtained by elliptic curve arithmetic calculation, thereby allowing the communicating parties to establish a shared key without directly exchanging private information;
[0054] S48. When selecting the AES algorithm mode, if the communication data contains fixed-mode content, avoid using the ECB mode to prevent mode leakage; when using the CBC mode, pad the data to meet the requirements of block encryption to ensure that all data blocks can be correctly encrypted;
[0055] S49. Verify that the data has not been tampered with through integrity and authentication mechanisms. For data encrypted using AES, the message authentication code MAC is combined to provide data integrity and source verification; for data encrypted using ECC, a digital signature is attached to the message to provide authentication and non-repudiation.
[0056] Preferably, S5 includes the following sub-steps:
[0057] S51. According to the public key information provided by the manufacturer of the mobile terminal device, obtain the root certificate used by the device in the secure boot process to ensure that the basis for subsequent verification is officially certified;
[0058] S52. If the root certificate matches, chain verification is performed on the firmware, and the digital signature of each startup component is checked layer by layer to ensure that each link from the boot loader to the operating system kernel has not been tampered with;
[0059] S53. Use a remote server to issue an authentication request to the device, requiring the device to provide proof of its current state, including a measured startup log and a certificate signed by the device's private key;
[0060] S54. For the received startup log and certificate, the remote server uses the corresponding public key to verify whether the device is in a known and secure state;
[0061] S55. Obtain the integrity protection status of the operating system level, including system file protection and application isolation, to ensure that key system files have not been modified without authorization;
[0062] S56. Perform mandatory access control checks through the SELinux policy provided by the operating system to restrict and monitor the behavior of processes to ensure that they do not exceed the preset permissions;
[0063] S57. Verify the encryption status of stored data and communication security through the encryption module of the device to ensure the protection of data during transmission and static storage;
[0064] S58. Obtain the latest software update and patch records for the device, compare the update logs released by the manufacturer or developer, and check whether there are any important security patches that have not been applied;
[0065] S59. Through the audit and logging system, extract the system's key operations and event logs and analyze whether there are abnormal behaviors in order to discover potential security threats or inconsistencies.
[0066] Preferably, S6 includes the following sub-steps:
[0067] S61. Obtain user device information and identify the device holder based on the device's unique identifier;
[0068] S62. Use encrypted communication protocols to ensure the security of data when users enter passwords or PIN codes;
[0069] S63. If the password or PIN code verification is successful, a request is sent to the server for secondary verification;
[0070] S64. After the server-side verification is passed, a one-time password OTP is generated and sent to the user's mobile phone through a secure channel;
[0071] S65. After receiving the OTP, the user enters it into the authentication system. If the OTP matches, the biometric data collection process is triggered;
[0072] S66. Use biometric hardware modules, including fingerprint and facial recognition sensors, to collect biometric data of users;
[0073] S67. Compare the biometric data with the user biometric template stored on the server to determine whether the user is an authorized user;
[0074] S68. If the biometric data verification is successful, the final authorization decision is made in combination with the user's geographic location information.
[0075] Preferably, the S7 includes the following sub-steps:
[0076] S71. Obtain user identity information and device information: Through the authentication service, collect the user's username, user ID and device ID information. If the user identity authentication is successful, continue processing; if it fails, deny access;
[0077] S72. Determine the user role: According to the user ID and organizational information, query the role management database to obtain the user's role name and its corresponding permission set;
[0078] S73. Determine the device security status: query the device information database based on the device ID to determine whether the device meets the security configuration requirements. If the device is not secure, restrict access; if the device is secure, continue the process;
[0079] S74. Retrieve access control list: query ACL information based on resource identifier to determine whether the user and his device are in the user list allowed to access;
[0080] S75. Apply permissions through role-based access control rules: If the user and device are in the access control list, combined with the user role information, the RBAC system applies the access rights corresponding to the role to the user;
[0081] S76. Application context information: Refer to the current time and the user's network location information, and use the access control policy to determine whether the user meets the access conditions, including access rights during working hours;
[0082] S77. Determine resource access level: Use different permissions to restrict or allow user operations on resources based on the sensitivity level and location of the resource;
[0083] S78. Application strategy and audit: Based on the set access control strategy and audit strategy, the user's access behavior is recorded, and on this basis, monitoring and auditing are carried out;
[0084] S79. Audit log analysis: Perform analysis based on user access behavior recorded in the audit log. If abnormal behavior is found, the security response mechanism is triggered; if the analysis is normal, the access control process is completed.
[0085] Preferably, the S8 includes the following sub-steps:
[0086] S81. Configure a central log management system and use time synchronization protocols such as NTP to ensure that the timestamps of each system are accurate and consistent;
[0087] S82. Set the marking rules for the log source, obtain the identification information of each system and device, and include this information in the log message;
[0088] S83. Implement log encryption and access control mechanisms to encrypt and store sensitive log data;
[0089] S84. Build rules and policies to classify and tag logs according to event types;
[0090] S85. Develop and apply user authentication and tracking policies, and indicate the identity of users in log records;
[0091] S86. Integrate advanced log analysis tools to conduct in-depth analysis of collected log data;
[0092] S87. Implement real-time monitoring and alert mechanisms to trigger alerts when suspicious activities occur;
[0093] S88. Establish data retention and backup strategies to ensure persistent storage and recovery capabilities of log data in accordance with regulations and business requirements;
[0094] S89. Deploy a scale-adaptive log collection and normalization system to support processing of high data volumes and multiple log formats.
[0095] A trusted authentication system for mobile terminal devices based on the Internet of Things, including a device identity allocation module, a security key generation module, an authentication protocol design module, an encryption technology implementation module, a device integrity check execution module, a user authentication verification module, an authority control implementation module, an audit and log system configuration module, and a certificate issuance and management implementation module;
[0096] The device identity allocation module is used to allocate a unique identifier to each mobile terminal device through the IoT device management platform, and register its hardware fingerprint information, including device ID and MAC address, and track the identity of the device through these identifiers;
[0097] The security key generation module is used to generate a pair of asymmetric keys or a group of symmetric keys for each mobile terminal device using a key generation algorithm for subsequent device authentication and communication encryption, ensuring that the key distribution is random and unpredictable;
[0098] The authentication protocol design module is used to design an authentication protocol suitable for mobile terminal devices according to the capabilities and authentication requirements of the devices, adopt an authentication mechanism based on SSL / TLS, define the communication process and handshake mechanism between devices, and ensure encryption and identity authentication during the transmission process;
[0099] The encryption technology implementation module is used to select the encryption algorithm AES or ECC to encrypt the communication data between devices to ensure that the confidentiality and integrity of the data are protected during the transmission process, and the previously generated security key is used in the encryption process;
[0100] The device integrity check execution module is used to verify whether the software and hardware of the mobile terminal device have been modified without authorization through secure boot or remote authentication technology, ensuring that the device is in a known and secure state;
[0101] The user authentication verification module is used to deploy a user authentication mechanism, combining the identity verification information of the device holder, including password or biometric data, to perform multi-factor authentication to ensure that only authorized users can operate the device;
[0102] The permission control implementation module is used to obtain the role information of the device and the user, and assign appropriate access rights to the device and the user through the access control list or the role-based access control, so as to restrict the access to sensitive data and resources;
[0103] The audit and log system configuration module is used to deploy a log management system to record the authentication process and device activities in detail. The logs are used for monitoring, post-analysis and auditing, which helps to identify potential security issues.
[0104] The certificate issuance and management implementation module is used to cooperate with the digital certificate issuing authority through the digital certificate management system to issue digital certificates to mobile terminal devices and establish a trust chain. The digital certificate is used to strengthen the identity authentication process of the device.
[0105] Compared with the prior art, the present invention has the following beneficial effects:
[0106] The present invention allocates a unique identifier to each mobile terminal device through an Internet of Things device management platform, registers its hardware fingerprint information to track the identity of the device, and adopts a key generation algorithm to generate a pair of asymmetric keys or a group of symmetric keys for each mobile terminal device, designs an authentication protocol suitable for mobile terminal devices, adopts an authentication mechanism based on SSL / TLS, defines the communication process and handshake mechanism between devices, and solves the problems of device identity authentication and secure communication; verifies whether the software and hardware of the mobile terminal device have been modified without authorization through secure startup or remote authentication technology, deploys a user authentication mechanism, and performs multi-factor authentication in combination with the identity authentication information of the device holder, and solves the problems of device integrity and user authentication; deploys a log management system to record the authentication process and device activities in detail, cooperates with a digital certificate issuing authority to issue digital certificates to mobile terminal devices, establishes a trust chain, and solves the problems of auditing and management. BRIEF DESCRIPTION OF THE DRAWINGS
[0107] Figure 1 It is a general flow chart of a trusted authentication method for a mobile terminal device based on the Internet of Things of the present invention;
[0108] Figure 2 It is one of the sub-flow charts of a trusted authentication method for a mobile terminal device based on the Internet of Things of the present invention;
[0109] Figure 3 This is the second sub-flow chart of a trusted authentication method for a mobile terminal device based on the Internet of Things of the present invention;
[0110] Figure 4 This is the third sub-flow chart of a trusted authentication method for a mobile terminal device based on the Internet of Things of the present invention;
[0111] Figure 5 This is the fourth sub-flow chart of a trusted authentication method for a mobile terminal device based on the Internet of Things of the present invention;
[0112] Figure 6 This is the fifth sub-flow chart of a trusted authentication method for a mobile terminal device based on the Internet of Things of the present invention;
[0113] Figure 7 This is the sixth sub-flow chart of a trusted authentication method for a mobile terminal device based on the Internet of Things of the present invention;
[0114] Figure 8 This is the seventh sub-flow chart of a trusted authentication method for a mobile terminal device based on the Internet of Things of the present invention;
[0115] Fig. 9 This is the eighth sub-flow chart of a trusted authentication method for a mobile terminal device based on the Internet of Things of the present invention;
[0116] Fig.10 It is a framework diagram of a trusted authentication system for mobile terminal equipment based on the Internet of Things of the present invention. DETAILED DESCRIPTION
[0117] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present disclosure. Instead, they are merely examples of devices consistent with some aspects of the present disclosure as detailed in the appended claims.
[0118] The technical solutions in the embodiments of the present invention will be described clearly and completely below in conjunction with the accompanying drawings in the embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.
[0119] Embodiment 1:
[0120] like Figure 1-9 As shown, an embodiment of the present invention provides a trusted authentication method for a mobile terminal device based on the Internet of Things, comprising the following steps.
[0121] S1. Assign device identity: Assign a unique identifier to each mobile terminal device through the IoT device management platform, and register its hardware fingerprint information, including device ID and MAC address, and track the identity of the device through these identifiers;
[0122] The device hardware fingerprint information can be combined with blockchain technology to obtain an unalterable device identity authentication record;
[0123] Obtaining device hardware features By reading the device's serial number, MAC address, CPU ID, motherboard ID and other hardware features, determine the device's unique fingerprint information, ensure that each device has a unique identification, and provide a basis for subsequent identity authentication; Using an encryption algorithm to process the obtained unique hardware fingerprint information using a secure encryption algorithm, encryption protects the privacy and security of the hardware fingerprint, and prevents unauthorized third-party access during storage and transmission; According to the smart contract rules, write predetermined identity authentication rules and logic through smart contracts to determine whether the device meets the requirements for participating in the network. Smart contracts support automatic execution of these rules to ensure the consistency of device identity authentication and reduce human operation errors; Through blockchain technology, based on the verification results of the smart contract, the encrypted hardware fingerprint information and verification results of the device are written into the blockchain. With the help of the blockchain's immutability and timestamp function, the device identity record is ensured to be permanent and traceable; Obtain distributed ledger storage Store the written device identity information in the distributed ledger of the blockchain to ensure that the information is stored in multiple nodes in the network There is redundant storage on the point, which improves the reliability of information and the system's anti-attack ability; Determine the verifiability of the device. Since the device identity information is stored on an open and transparent blockchain, any authorized participant can obtain the verification record of the device hardware fingerprint through the blockchain network, ensuring its verifiability and increasing credibility; Obtain cross-border verification capabilities. Utilize the global nature of the blockchain to ensure that device identity authentication can span different organizations and regions. The device's identity information and verification results can be accessed and verified by users worldwide due to the borderless nature of the blockchain, thereby meeting the cross-border requirements; Through the implementation of the above steps one by one, a device identity authentication record system can be built that not only guarantees the uniqueness and immutability of the device, but also provides verifiability, encryption, smart contract support, distributed storage, timestamps and cross-border. This system provides solid technical support for the security management of IoT devices, effectively prevents device identity fraud and tampering, and enhances the security and trust of the entire network.
[0124] S2. Generate security keys: Use a key generation algorithm to generate a pair of asymmetric keys or a set of symmetric keys for each mobile terminal device for subsequent device authentication and communication encryption, ensuring that the key distribution is random and unpredictable.
[0125] S3. Design authentication protocol: Design an authentication protocol suitable for mobile terminal devices based on the device capabilities and authentication requirements, adopt an authentication mechanism based on SSL / TLS, define the communication process and handshake mechanism between devices, and ensure encryption and identity authentication during the transmission process.
[0126] S4. Implement encryption technology: Select encryption algorithm AES or ECC to encrypt the communication data between devices to ensure the confidentiality and integrity of the data during transmission. The encryption process uses the previously generated security key;
[0127] Dynamic encryption strategies and algorithms can be used to determine the best data protection solution under the current network environment;
[0128] Specifically, based on the sensitivity of the data, obtain data classification standards and protection level requirements, including analyzing the type of data, such as personal identity information, financial records or business secrets, and determining the possible consequences of data threats; obtain data classification for different protection levels to lay the foundation for the subsequent selection of encryption algorithms; use performance requirements as parameters to obtain the system's processing power and the performance standards of the application, and evaluate the utilization rate and performance indicators of system resources, such as the actual measured values of CPU, memory and network bandwidth; determine the appropriate encryption method and degree to ensure that encryption measures are implemented without exceeding the performance threshold; obtain the current number of system users and expected growth, taking into account the key management and distribution challenges that a large number of users may bring; obtain key management strategies for user scale, such as using key hierarchy or group key management technology to adapt to changes in the number of users; obtain detailed information about bandwidth limitations, delays and packet loss rates through the specific characteristics of the network environment; determine how these network characteristics affect encryption strategies, for example, in In cases where bandwidth is limited, it may be necessary to select a more efficient encryption algorithm; adopt availability requirements to obtain the access and usage patterns of authorized users in the system; ensure high availability of encrypted data while optimizing user access control and authentication mechanisms to meet business continuity needs; obtain detailed requirements of relevant laws, regulations and industry standards based on compliance requirements; determine the necessary encryption measures to meet these requirements, while taking into account how compliance changes affect future encryption strategies; obtain currently available encryption technologies and tools through an understanding of encryption algorithm types; determine which encryption algorithm (symmetric, asymmetric or hash algorithm) is most suitable for the established data protection goals; obtain current key management practices and strategies, and adopt the latest encryption standards and best practices; obtain a key lifecycle management plan, including generation, storage, distribution, rotation and destruction; obtain potential security threats to the current network environment based on threat model analysis; determine response strategies, such as strengthening encryption algorithms or adopting additional security measures to guard against identified threats;
[0129] Use knowledge of encryption protocols to obtain information about mature protocols such as SSL / TLS and IPSec; ensure the security of data transmission while taking into account the performance of different protocols under different network conditions; obtain detailed configuration and performance parameters of hardware resources by considering resource limitations; determine the impact of these limitations on the selection of encryption strategies, and upgrade or optimize resources when necessary to meet encryption needs; obtain details of backup and recovery plans, and use these plans to test encrypted data; ensure the feasibility of backup and recovery mechanisms to avoid encryption measures affecting data integrity and recoverability; obtain system logs and security incident reports based on audit and monitoring requirements; obtain audit strategies and monitoring mechanisms for encryption operations to respond to security incidents in a timely manner; obtain partners' security strategies and capabilities through the integration of cloud services with third parties; determine whether the encryption and security measures of these services are consistent with the company's security goals, and take necessary integration measures; obtain the system's dynamic adaptability, using real-time monitoring and automatic adjustment mechanisms; obtain a set of encryption strategies that can be dynamically adjusted according to changes in the network environment to improve the flexibility and efficiency of data protection.
[0130] S5. Perform device integrity check: Verify whether the software and hardware of the mobile terminal device have been modified without authorization through secure boot or remote authentication technology to ensure that the device is in a known and secure state.
[0131] S6. Verify user authentication: Deploy a user authentication mechanism that combines the device owner's identity verification information, including passwords or biometric data, to perform multi-factor authentication to ensure that only authorized users can operate the device;
[0132] It can obtain multi-dimensional data based on user behavior and biometrics to determine reliable user authentication strategies;
[0133] Specifically, according to the scenario in which the user attempts to authenticate their identity, biometric feature acquisition technology, such as fingerprint or facial recognition equipment, is used to obtain the user's biometric information; the raw data obtained by the biometric scanning device is used as the first step of authentication, ensuring that the user is an individual with a biological identity; the uniqueness of the user is determined through the above-mentioned raw biometric data; the algorithm is applied to match the biometric template pre-stored in the database to determine whether the user is a legitimate user identified by the system; this matching process is a key link in the multi-dimensional user authentication strategy, which ensures the accuracy of biometric authentication; the behavioral analysis data of the user when logging in, such as login time, usage habits, etc., is obtained, and these behavioral features are analyzed and analyzed. The user's behavior pattern can be analyzed; this can assist biometric information and improve the overall security of the authentication system, because even if someone can copy biometric information, it is difficult to completely imitate a user's behavior habits; through the user's behavior pattern, determine whether there is abnormal behavior. For example, if the user is usually inactive after midnight, and now there is such a login situation, the system can further increase vigilance and require additional authentication steps; obtain the environmental feature data of the user when logging in, such as IP address, connection type, etc., and obtain the context of the user's login environment through this information, which helps to identify whether the user is operating in a regular security environment; through the user's login environment context, determine the legitimacy of the user's identity authentication request Legitimacy. For example, if the user usually logs in from a specific IP address, and the current login attempt comes from a different geographical location, the system may need to introduce additional authentication steps to verify the user's identity; obtain the user's device feature information, such as hardware ID, device configuration, etc., through which the fingerprint of the device used by the user can be obtained, which helps to identify the authenticity of the device and whether it is authorized; by analyzing the device feature information, determine whether the device is a device commonly used by the user. If so, this will increase the legitimacy of the user's login request; if not, the system may increase security requirements, such as requiring the entry of a verification code, sending a notification to a trusted device, or performing other forms of verification; obtain other authentication factors of the user, such as knowledge factors (password, PIN code) or holding factors (security token), through which a comprehensive authentication score can be obtained to evaluate whether the user's authentication request meets security standards; through the comprehensive authentication score, it is determined whether the user's identity authentication request is acceptable. If the score reaches the system preset threshold, the user is allowed to access; if the score is lower than the threshold, access is denied, and further security measures may be taken, such as prompting the user to perform secondary authentication or locking the account to prevent potential security risks; through the above steps, the user authentication strategy based on multi-dimensional data can effectively improve the security of the system, and at the same time, by integrating multiple authentication information, it reduces the possibility of misjudgment and provides users with a safe and convenient authentication experience.
[0134] S7. Implement permission control: obtain role information of devices and users, assign appropriate access rights to devices and users through access control lists or role-based access control, and limit access to sensitive data and resources.
[0135] S8. Configure audit and log system: Deploy a log management system to record the authentication process and device activities in detail. Logs are used for monitoring, post-analysis and auditing, which helps identify potential security issues.
[0136] S9. Implement certificate issuance and management: Through the digital certificate management system, collaborate with the digital certificate issuing authority to issue digital certificates for mobile terminal devices and establish a trust chain. Digital certificates are used to strengthen the device's identity authentication process.
[0137] Preferably, S1 includes the following sub-steps:
[0138] S11. Assign device identifier: Generate a unique device ID for each mobile terminal device through the IoT device management platform to ensure that each device can be individually identified in the system;
[0139] S12. Record device hardware information: Use automated tools to read the MAC address, CPU model, memory size, and storage space hardware specifications of the terminal device to form a device hardware fingerprint;
[0140] S13. Register other device attributes: obtain the device type, serial number, firmware / software version, and associate this information with the device ID to build a complete device profile;
[0141] S14. Configure network information: Set the device to automatically report its network type and IP address network information when connected to the IoT platform to facilitate remote access and management of the device;
[0142] S15. Storage of location and status data: The device’s built-in GPS module positioning technology is used to regularly update the device’s location information and detect the device’s status information, including power level and operating status, and record it on the platform;
[0143] S16. Install security certificate: Push and install the security certificate to the device to facilitate encrypted communication of the device and to authenticate the legitimacy of the device;
[0144] Based on the device security certificate, a digital certificate verification mechanism is used to obtain certificate details, including the certificate issuer (CA), certificate validity period and other information, to obtain the validity status of the certificate; through the validity status of the security certificate, determine whether the certificate has been revoked, and obtain the certificate revocation information by querying the certificate revocation list (CRL) or using the online certificate status protocol (OCSP) for verification; obtain the certificate's public key information and certificate transparency (CT) log records to determine whether the certificate information has been recorded in the public certificate transparency log, increase public auditing and supervision, and avoid opaque certificate issuance behavior; use digital fingerprint technology to compare the certificate fingerprint with the fingerprint pre-stored in the system to obtain the certificate Verify the authenticity and integrity of the certificate to prevent impersonation or man-in-the-middle attacks; obtain the certificate's public key infrastructure (PKI) related information to determine whether the certificate complies with the organization's PKI policy and structure, and determine the compliance of the certificate; obtain the device's behavior pattern through the device's usage history and configuration files, including historical usage patterns, geographic location, time patterns, and network attributes, to determine whether the device's behavior is consistent with its normal behavior pattern; obtain the device's current geographic location and access time information, and determine whether the device is in the expected usage area and reasonable activity time by comparing the preset geographic location and time pattern; use network monitoring tools to obtain the device's network connection attributes and analyze the network trust level Determine whether the device is accessed from a trusted network; obtain the device's operating system and software version information, and determine whether the device configuration meets security requirements by comparing it with organizational standards; use the principle of least privilege based on the level of permission requested by the device and work needs to determine whether the device only requests permissions that meet its work needs; obtain detailed information on network segmentation and isolation through network architecture diagrams and access control policies to determine whether the device can access the appropriate part of the network and perform appropriate isolation; obtain user authentication information associated with the device, and determine whether the user has successfully passed the authentication process through the security authentication process; use terminal security management tools to obtain security patches and anti-malware software for the device Software status, to determine whether the device is running the latest security patches and anti-malware programs; through behavioral analysis tools, obtain the device's behavior patterns and activity logs to determine whether the device behavior is inconsistent with the baseline behavior or the normal behavior patterns of similar devices; obtain real-time monitoring data of device activities, and use anomaly detection algorithms to determine whether abnormal activities are detected, such as frequent failed login attempts or abnormal data transmission; use compliance checking tools to obtain the device's regulatory compliance and organizational policy compliance, and determine whether the device meets relevant industry standards and regulatory requirements; through all the above verification and judgment processes, obtain the comprehensive security and compliance assessment results of the device, and ultimately determine whether to grant the device corresponding access rights;
[0145] S17. Set up a status monitoring mechanism: Build an equipment status monitoring system to capture and analyze the equipment's operating data in real time. If the equipment status is abnormal, trigger an early warning mechanism;
[0146] Based on the performance indicator data such as speed, temperature, pressure, flow, voltage, current, frequency, power, vibration and noise level obtained by sensors, real-time data monitoring technology is used to capture the immediate working status of the equipment; the real-time performance status of the equipment is determined through the performance indicator data, and compared with the preset performance threshold to determine whether the equipment has performance deviation or exceeds the normal working range; the status indicators such as the start / stop status, on / off status, error code and alarm status of the equipment are obtained, and the logic analysis algorithm is used to determine whether the operating status of the equipment is normal, and timely warning information is obtained when an abnormal state occurs; a comprehensive evaluation of the equipment operation status is obtained through status indicators and real-time performance indicators, and it is determined whether further measures are needed. The equipment can be used to determine the equipment's health status and development trend; obtain historical data and trends, including past performance data, fault history, maintenance records, and consumable replacement records; use data mining technology to analyze past and present data changes to determine the equipment's health status and development trend; obtain potential problems that may exist in the equipment through historical data and trend analysis, and determine the equipment's remaining useful life (RUL) and loss rate in combination with information such as frequency of use; obtain environmental factor data, such as ambient temperature, humidity, pollution level, and air quality; use environmental impact analysis algorithms to analyze the impact of environmental variables on equipment performance and determine whether it is necessary to adjust operating parameters or take other measures; obtain the predicted maintenance of the equipment through the analysis results of environmental factors and real-time performance indicators. Maintenance indicators, such as abnormal mode detection, determine whether the equipment is about to fail and intervene in advance; obtain the operating parameters of the equipment, such as equipment set points, control parameters and process variables, and use control theory models to optimize the operating conditions of the equipment to ensure that the equipment operates at the best performance state; through operating parameter optimization and maintenance indicator analysis, obtain the best strategy for equipment maintenance and operation, and obtain solutions to prevent equipment failures in advance; obtain network and communication status data, including network connection status, data transmission speed and communication protocol, use network status monitoring technology to ensure accurate transmission of equipment data, and determine whether the network connection is stable; through network and communication status monitoring, obtain reliability assessment of equipment remote monitoring and data transmission, and determine whether it is necessary to take Take measures to improve communication efficiency; obtain the software and firmware version information and update logs of the device, and use version management tools to ensure that the device runs the latest software and firmware to obtain improved functions and security updates in a timely manner; obtain the needs of device software upgrades and firmware updates through software and firmware version analysis, and determine whether updates need to be performed to fix potential software problems or improve device functions; obtain the safety feature data of the device, such as the emergency stop button status, safety door switch status, and leakage detection, and use safety monitoring algorithms to ensure that the safety features of the device are activated and provide early warnings when safety hazards are detected; obtain safety risk assessments of the device through monitoring and early warning of safety features, and determine whether additional safety protection measures need to be taken;Obtain user operation data, including operation logs, user input and interface cloud records, use user behavior analysis technology to evaluate the possible risk of misoperation during operation, and provide suggestions for standardized operation; obtain standardized guidance and improvement measures during the operation through behavioral analysis of user operations, and obtain solutions to improve the accuracy and efficiency of equipment operation;
[0147] S18. Logs and operation records: Design a log system to capture the operation records of the device, including instruction execution and data transmission records, for auditing and troubleshooting;
[0148] S19. Implement subscription service management: Automatically assign appropriate services to devices based on device type and user needs, and monitor service status to ensure service continuity and reliability.
[0149] Preferably, S2 includes the following sub-steps:
[0150] S21. Select RSA as the asymmetric encryption algorithm through the cryptography library OpenSSL. If the library provides multiple algorithms, determine the most suitable algorithm based on performance and security requirements;
[0151] According to the security requirements of different applications and organizations, first determine the required security level. For example, for financial institutions that need to process highly confidential data, a key length of 4096 bits may be required, while for internal systems of small businesses, a key length of 2048 bits may be sufficient. By evaluating potential threats and the sensitivity of the data to be protected, an expected key length requirement is obtained. Using this expected key length requirement, further evaluate computing power. If it is an environment with limited computing resources, such as mobile devices or IoT devices, the key length may need to be reconsidered to keep system performance and response time within an acceptable range. By comparing performance test results under different key lengths, the best key length selection under current computing power conditions is obtained. Obtain detailed information about network conditions, such as bandwidth limitations and latency requirements. If the application runs in a bandwidth-limited or latency-sensitive network environment, an increase in key length may have a negative impact on data transmission. Determine the appropriate key length by simulating network performance under different key lengths to ensure that neither security is sacrificed nor communication efficiency is excessively affected. By examining future technology development trends, such as the progress of quantum computing, estimate the challenges that existing key lengths may face in the future. Security challenges; If data needs to be protected for a long time, a longer key may be required to achieve forward security; By analyzing the potential impact of quantum computing on existing encryption algorithms, determine and select a key length that can resist future threats; Use industry regulations or standards as a reference to check whether there are specific key length requirements, such as some government agencies may require the use of at least 3072-bit key lengths; Determine the minimum key length requirements that need to be met by comparing relevant regulations and standards; Ensure that the selected key length is compatible with existing software and hardware devices by testing and verifying the compatibility of existing systems; In some cases, if the system or device software is not updated, it may not support longer key lengths; Determine whether the selected key length is suitable for the existing environment by performing encryption and decryption tests on these systems; Based on the above considerations, determine a key length that meets security requirements without excessively affecting performance and compatibility. Such a key length can not only provide sufficient security, but also ensure the normal operation of the system and a good user experience; Get the final key length through comprehensive analysis; Generate an RSA key pair using the OpenSSL library and the determined key length parameters; For example, by executing `openssl genpkey-algorithm RSA-out private_key.The pem-pkeyopt rsa_keygen_bits:2048 command generates an RSA private key with a 2048-bit key length. If the previous evaluation process recommends a longer key length, you can replace 2048 with 3072 or 4096 to obtain a key pair with stronger security protection. Finally, review the key length selection regularly to respond to new threats and technological developments. Through continuous monitoring and evaluation, ensure that the key length always meets current and expected security standards.
[0152] S22. Using the library function, obtain the currently recommended key length parameter, and for RSA, obtain its 2048-bit parameter setting;
[0153] S23. Use the random number generator and RSA algorithm in the cryptography library to generate an asymmetric key pair and determine whether the generation process meets the requirements of randomness and uniqueness;
[0154] S24. The private key is stored in a confidential area of the mobile terminal device through an encrypted storage mechanism, and a hardware security module HSM is used to prevent unauthorized access;
[0155] Based on the organization's physical security needs, the use of hardware security modules (HSMs) can provide passive tamper-resistant device housings, automatically delete stored keys when physically invaded, and obtain a basic key protection mechanism to ensure the security of keys in the event of unauthorized physical access attempts; use the HSM's built-in role-based access control to obtain the ability to perform advanced configurations on the device, thereby ensuring that only users with the correct permissions can access the keys. Even inside the device, access to private keys can be strictly restricted to strengthen protection against unauthorized access; through the HSM's cryptographic protection measures, all key operations are guaranteed to be executed within a secure boundary, ensuring that the keys will never be read or modified by external processes during use, thereby obtaining a reliable defense against software attacks. Rely on barriers; use the multi-factor authentication technology supported by HSM to obtain more verification steps for key access. Even if someone has certain access credentials, they cannot obtain the right to use the key without verification of other factors, which greatly increases security; obtain detailed records of all key operations through the audit and logging functions of HSM. For enterprise security policies, it allows any improper access attempts to be tracked and audited, enhancing the ability of post-analysis and accountability; use the built-in side channel attack protection measures of HSM to obtain the function of monitoring power consumption and electromagnetic radiation, judge and reduce the risk of information leakage due to physical radiation, and obtain a safer key operation environment; obtain natural isolation from malware and network attacks through the independence of HSM;
[0156] S25. Obtain the public key and send it to the server through the device registration process, so that in subsequent communications, the server can use the public key to verify the identity of the device or encrypt messages to the device;
[0157] S26. Select AES as the symmetric encryption algorithm and obtain a 256-bit key length setting to meet high security requirements;
[0158] S27. Generate a symmetric key using the CSPRNG in the cryptography library and determine whether the key meets the standards of randomness and uniqueness;
[0159] According to the entropy property, the entropy source is evaluated to ensure that it can provide sufficient randomness, the entropy of the entropy source is measured to ensure that it can provide sufficient unpredictability, the output data of the entropy source is collected, and its entropy value is calculated using an entropy estimation algorithm such as Shannonentropy. The obtained entropy value will be used as input for entropy unpredictability analysis. Using the unpredictability property of entropy, the entropy value is analyzed to determine the quality of its randomness; by using tools such as the NIST randomness test suite, the statistical properties of the entropy source output data and their correlation with previous data are obtained; it is determined whether the data that pass these tests show sufficient unpredictability; such as If it passes, it means that the output of the entropy source is random and has no obvious pattern or association; obtain the uniformity property of entropy and further analyze the output data of the entropy source whose unpredictability has been determined; determine whether the distribution of the entropy source output data is uniform through statistical analysis methods, such as frequency testing; after obtaining the data distribution analysis results, determine whether the entropy source outputs random data uniformly to ensure that all possible values of the CSPRNG output have the same probability; through the independence property of entropy, further verify whether the values of the entropy source output data sequence are independent of each other; use methods such as binary sequence testing and autocorrelation analysis to obtain the correlation information between the values in the data sequence; obtain the correlation analysis After obtaining the results of the analysis, determine whether the data values output by the entropy source are independent, ensuring that the appearance of a value is not affected by the previous value; obtain the reliability attribute of the entropy source and evaluate the environmental adaptability of the entropy source; collect data samples under different environmental conditions, such as different time, temperature, and electromagnetic state; determine whether the entropy source can still reliably provide high-quality entropy under these conditions; use the verifiability attribute of the entropy source to implement inspection and verification of the entropy source output; track and record the performance indicators of the entropy source output by building a monitoring and detection mechanism; after obtaining the monitoring data, determine whether the entropy source meets the required randomness and uniqueness standards; through the real-time attribute of the entropy source, ensure At the moment of key generation, the entropy source can provide high-quality entropy instantly. By implementing dynamic tests, the state of the entropy source outputting data at the time of demand is obtained to determine whether the entropy source can provide the necessary entropy value at the critical moment; the continuity property of the entropy source is obtained to evaluate whether the entropy source can continue to provide high-quality entropy, the output of the entropy source is monitored for a long time, and its stability over time is checked; after obtaining the long-term monitoring results, it is determined whether the entropy source can maintain the high-quality randomness of its output throughout the life cycle; through this series of steps, combined with relevant business attribute considerations, a symmetric key generation system is established to provide highly random and unique keys to ensure the security of information transmission and storage;
[0160] S28. The symmetric key is encrypted using the public key of the device through asymmetric encryption, and then the encrypted symmetric key is sent to the mobile terminal to ensure the security of the key distribution process;
[0161] S29. For the received encrypted symmetric key, the mobile terminal uses its private key to decrypt it and obtains the symmetric key, which is ready for device authentication and communication encryption.
[0162] Preferably, S3 includes the following sub-steps:
[0163] S31. Based on the processing capability of the mobile terminal device, adopt appropriate encryption algorithms and security parameter configurations to achieve effective execution of SSL / TLS operations, and select encryption algorithms that can run efficiently on the device and lightweight encryption algorithms to reduce processing delays;
[0164] Based on the limitations of the CPU performance of mobile devices, the AES-128 algorithm is used as the initial encryption scheme; AES-128 has a low computational complexity, which can reduce the demand for CPU resources while maintaining security; by performing tests and benchmarks, we obtain the number of CPU cycles of AES-128 on a specific mobile device; using the memory usage data of the AES-128 encryption algorithm, we can obtain its memory usage when it is executed on a mobile device; since lightweight algorithms are designed to use less memory, it can be determined whether AES-128 meets the requirements of lightweight algorithms and whether it is an encryption scheme suitable for mobile devices; by monitoring the energy consumption of the AES-128 algorithm when it runs on a mobile device, the energy consumption data of the encryption operation is obtained; energy efficiency is a very critical attribute on mobile devices, and it is determined whether the energy consumption of AES-128 is within an acceptable range to ensure that it does not consume the battery excessively; based on known attack methods and security vulnerabilities, security analysis is used to evaluate the security strength of the AES-128 algorithm to determine whether AES-128 can effectively resist threats such as man-in-the-middle attacks, replay attacks, and password cracking to ensure data on mobile devices Transmission security; obtain encryption strength information related to the key length and cryptographic complexity of the AES-128 algorithm to evaluate its actual ability to protect data. Encryption strength is a key factor in measuring whether an encryption algorithm can resist attacks in the long term. Determine whether AES-128 provides sufficient protection to prevent data leakage; obtain compatibility data by analyzing the client and server software on mobile devices to determine whether the AES-128 algorithm is compatible with mainstream web browsers and web servers, so as to determine whether it can be widely supported in actual applications; use comparative analysis methods to analyze the standardization and implementation of AES-128. Standardized algorithms can better obtain community support and optimization. Determine whether AES-128 has broad implementation and community support to ensure its reliable and efficient application on mobile devices; obtain information on the scalability and flexibility of the AES-128 algorithm by evaluating its ability to support different encryption levels; mobile devices require different levels of security protection in different application scenarios, so the scalability and flexibility of the algorithm are very important. Determine whether AES-128 can adjust the encryption strength as needed to adapt to changing security needs;
[0165] S32. Obtain storage capacity information of the device to determine whether there is enough space to store the digital certificate and private key. If the storage space is insufficient, perform storage optimization, including compressing the certificate storage or using a smaller key size;
[0166] S33. Through the network connection test, determine whether the mobile terminal device can establish and maintain a stable data transmission connection. The network connection test result determines whether additional network optimization measures are needed, including adjusting the data packet size or selecting a more stable network protocol;
[0167] According to the real-time requirements of the business, obtain the test results of network delay and measure the round-trip time of the data packet in milliseconds; after obtaining the delay value, determine whether it meets the response speed requirements of the real-time business; use network monitoring tools to obtain packet loss rate data and obtain the percentage by comparing the number of lost data packets with the total number of sent data packets; after determining the packet loss rate, determine the impact on real-time communication or business continuity; obtain the current network bandwidth usage and determine the network's transmission capacity by measuring the amount of data flow within a certain period of time. The bandwidth data obtained can help determine whether there is network congestion and whether the bandwidth needs to be upgraded to support business volume; obtain the quantitative value of network jitter through network testing tools. The jitter value reflects the fluctuation of network delay; after determining the jitter level, evaluate the impact on real-time audio and video services and decide whether measures need to be taken to reduce jitter; obtain relevant data on connection stability through long-term network status monitoring, including connectivity rate and connection duration; after obtaining the stability assessment, determine whether the network is stable enough to meet the business requirements for connection availability Reliability requirements; obtain network error rate test results to determine the ratio of erroneous data packets during data transmission; after obtaining the specific value of the error rate, determine whether network optimization is needed to reduce retransmission and delay caused by errors; obtain actual data transmission volume through network throughput test; after obtaining throughput data, evaluate whether the network can cope with current business needs; obtain network availability data to record the proportion of time that network services can be used normally; after determining the high availability level, ensure the continuous operation of key businesses and formulate appropriate redundancy or failover plans based on business continuity requirements; obtain response time data through testing to record the time consumed from the user sending a request to the service responding to the request; determine whether the response time is within an acceptable range to ensure user experience and business efficiency; obtain changes in data packet routing and stability data of path selection through network routing stability monitoring; after determining routing stability, decide whether routing strategies need to be optimized to ensure that data packets can reach their destinations through the optimal and most stable paths;
[0168] S34. Design a two-way authentication process where both the client and the server need to confirm each other's identity through mutual verification of digital certificates, including embedding certificate verification steps in the authentication protocol and determining the validity and credibility of the certificate chain;
[0169] The public key infrastructure system is used to initialize the authentication process. Both the client and the server have their own public and private key pairs, and have obtained a valid X.509 certificate from a trusted certificate authority. The handshake process of the two-way authentication protocol is started through the TLS protocol. The client first sends a client hello message to the server, which contains the TLS version supported by the client, the encryption suite option, and a client random number. The server's response to the client hello is obtained, including a server random number and the server's certificate, which contains the server's public key. The client uses the public key to verify the server's identity and check the validity of the certificate, such as the trust chain of the issuing authority, the expiration time, and the certificate revocation list. After passing the server's certificate verification, the client obtains the server's public key and uses it to encrypt a pre-master key, which is then sent to the server. Only the server with the matching private key can decrypt and obtain this pre-master key. The server generates a session key based on the pre-master key and returns an encrypted message to the client to prove that it has correctly decrypted the pre-master key. The client decrypts the message to determine whether the server has successfully obtained the pre-master key, completing the key negotiation process. Both the client and the server obtain the same session key to encrypt subsequent communications; a strong random number generator is used to generate keys for identity authentication to ensure the strength and unpredictability of the keys, and the keys are stored on the client and server to prevent key leakage; multi-factor authentication is performed as needed, for example, the client can use a one-time password or biometric verification to further ensure the authenticity of the identity authentication; after the authentication process, a secure communication channel is obtained, and the client and server can exchange data; at the same time, all key steps in the authentication process are recorded in the audit log for monitoring and subsequent audit analysis; the principle of least privilege is determined to be applied to the system to ensure that the client and server only have the necessary permissions to perform communication, reducing potential security risks; after obtaining the construction of a secure channel, a performance evaluation is performed to determine whether the identity authentication process has an adverse impact on system performance; through user experience feedback, the transparency and ease of use of the two-way authentication process are determined, so as to improve user satisfaction and acceptance of the authentication process without sacrificing security; finally, ensure that the entire two-way authentication process complies with data protection regulations, such as GDPR or HIPAA, to protect user privacy and sensitive data;
[0170] S35. Implement certificate management strategies to ensure that digital certificates can be safely installed and updated on mobile devices, and that the devices have certificate management capabilities so that digital certificates can be updated in a timely manner before they expire or when they are revoked;
[0171] S36. Design access control mechanisms to allow only authenticated devices to obtain access rights to protected resources, and assign permissions and control resources to devices based on authentication results;
[0172] S37. For the handshake mechanism, formulate a process that adapts to the performance of mobile devices. From the client Hello to the server Finished message, each step takes into account efficiency and security. The algorithm selection during the handshake process affects the performance of the authentication protocol.
[0173] S38. During the communication process, use message authentication code MAC or digital signature to implement encryption and integrity protection measures to ensure the confidentiality and integrity of data;
[0174] S39. Select an efficient encryption algorithm and the latest TLS version. By testing the performance of different algorithms and protocol versions, determine the most suitable combination for mobile devices. The performance test results determine the encryption algorithm and TLS version that are ultimately adopted.
[0175] Preferably, S4 includes the following sub-steps:
[0176] S41. Based on the sensitivity and protection requirements of the communication data, if the data requires extremely high security, select the AES algorithm and use a 256-bit key; if the communicating parties need to use asymmetric encryption for secure key exchange and digital signature, select ECC and use an appropriate key length to ensure equivalent security strength;
[0177] S42. When using a high-quality random number generator to generate a key, if it is an AES symmetric key, ensure that the generated key is sufficiently random to prevent predictable attacks; if it is an ECC asymmetric key pair, generate a pair of private and public keys at the same time, the private key is highly confidential, and the public key is used to exchange encrypted information with other communication entities;
[0178] According to the thermal noise in the circuit, the randomness of electronic components or quantum phenomena, etc., the original random data of the high entropy source is obtained. The high entropy data source is the key to true randomness and unpredictability, ensuring that there is no identifiable pattern or association between the random numbers generated each time; the original random data is processed by digital signal processing technology to obtain a statistically uniformly distributed random bit stream, ensuring the unbiased and uniform distribution of random numbers, which means that the probability of each bit appearing 0 or 1 is equal, thereby ensuring that any specific AES key has an equal chance of being selected in theory; the processed random bit stream is obtained and verified through a series of statistical tests, such as the NIST statistical test suite, to check the quality of the random numbers and ensure independence and unbiasedness; the previously verified random data is used as a seed or entropy input through a cryptographically secure pseudo-random number generator to generate the final key material, ensuring that even with exactly the same entropy input, the output key sequence will be highly unpredictable and non-reproducible; after obtaining the output key sequence, it is further subject to compliance checks to ensure that the generated key meets relevant industry or national standards, such as FIPS140-2 or NIST SP 800-90A, Enhanced anti-attack capabilities; Only use the generated AES key for encryption or other security-related business processes after ensuring that it meets all of the above properties;
[0179] S43. When distributing keys through a secure channel, if an AES key is used, the security of the channel is guaranteed to prevent the key from being intercepted during transmission; if an ECC key is used, only the private key needs to be distributed securely, and the public key can be made public;
[0180] S44. After obtaining the key, keep the key safe through a secure storage mechanism. If it is an AES key, use a hardware security module HSM or other forms of secure storage; for ECC private keys, also use HSM or encrypted software storage containers to ensure that the private key is not accessed by unauthorized persons;
[0181] S45. When updating keys regularly, the keys are updated through an automated key management system. For AES keys, the keys are replaced periodically to avoid security risks caused by long-term use of the same key; for ECC keys, updating the private key also regenerates the corresponding public key and distributes it to relevant communication entities;
[0182] Design the key lifecycle management process, including key creation, distribution, use, storage, archiving and destruction, and determine the security requirements and control measures for each link in the process to ensure the security and compliance of the key throughout its lifecycle; adopt risk assessment methods, combine business needs and security standards, analyze and determine the frequency of key updates, obtain the security level and data sensitivity information of the current business system, and use this information to obtain a reasonable key replacement cycle to ensure that the key will not increase security risks due to long-term use; obtain high-quality key materials by using strong random number generators and certified encryption algorithms to ensure that the generated keys have sufficient strength and unpredictability, so as to determine whether they can resist external attacks and internal threats; obtain the security requirements of keys during storage and transmission, and use encryption and other protection measures to store and transmit keys securely. Through these measures, the ability to ensure that keys are not accessed by unauthorized persons at any time is obtained; obtain the identity information of authorized users through access control policies, and implement the principle of least privilege to determine and restrict only necessary users to access and use keys, thereby reducing security risks caused by excessive privileges; obtain key usage records and Activity logs are used to identify abnormal behaviors in the system, ensure that key abuse or other security incidents are detected in a timely manner, and take appropriate response measures; obtain the disaster recovery capabilities and backup strategies of the current key management system, adopt necessary redundancy and backup measures, ensure that key materials can be quickly restored in the event of failure or data corruption, and maintain business continuity; evaluate the existing IT infrastructure, obtain the compatibility requirements of the system, adopt key management solutions that support industry standards and best practices, and ensure that the new system can be seamlessly integrated into the company's existing security architecture; obtain the manual operation links in the current key management process, use automation technology to achieve automatic key updates and management, identify and reduce risks caused by human operation errors, and improve overall management efficiency; based on the growth and future development forecasts of the business, obtain the expansion capabilities required by the key management system, adopt modular design and scalable architecture, and determine that the system can support more users, more complex business scenarios, and new encryption requirements in the future; through the above steps, it can be ensured that the automated key management system is not only closely integrated with the business attributes of the enterprise, but also can effectively manage the entire life cycle of the key, improve security, while maintaining flexibility and scalability to adapt to the continuous development of the business;
[0183] S46. When the key needs to be invalidated and destroyed, it should be processed through a professional key destruction program. For AES keys, ensure that the key is completely deleted from all systems and cannot be recovered; for ECC keys, destroy the private key to avoid any possible leakage;
[0184] S47. If the ECC algorithm is selected, the ECDH protocol is used for key negotiation, and the shared key material is obtained by elliptic curve arithmetic calculation, thereby allowing the communicating parties to establish a shared key without directly exchanging private information;
[0185] S48. When selecting the AES algorithm mode, if the communication data contains fixed-mode content, avoid using the ECB mode to prevent mode leakage; when using the CBC mode, pad the data to meet the requirements of block encryption to ensure that all data blocks can be correctly encrypted;
[0186] S49. Verify that the data has not been tampered with through integrity and authentication mechanisms. For data encrypted using AES, the message authentication code MAC is combined to provide data integrity and source verification; for data encrypted using ECC, a digital signature is attached to the message to provide authentication and non-repudiation.
[0187] Preferably, S5 includes the following sub-steps:
[0188] S51. According to the public key information provided by the manufacturer of the mobile terminal device, obtain the root certificate used by the device in the secure boot process to ensure that the basis for subsequent verification is officially certified;
[0189] S52. If the root certificate matches, chain verification is performed on the firmware, and the digital signature of each startup component is checked layer by layer to ensure that each link from the boot loader to the operating system kernel has not been tampered with;
[0190] S53. Use a remote server to issue an authentication request to the device, requiring the device to provide proof of its current state, including a measured startup log and a certificate signed by the device's private key;
[0191] S54. For the received startup log and certificate, the remote server uses the corresponding public key to verify whether the device is in a known and secure state;
[0192] S55. Obtain the integrity protection status of the operating system level, including system file protection and application isolation, to ensure that key system files have not been modified without authorization;
[0193] S56. Perform mandatory access control checks through the SELinux policy provided by the operating system to restrict and monitor the behavior of processes to ensure that they do not exceed the preset permissions;
[0194] S57. Verify the encryption status of stored data and communication security through the encryption module of the device to ensure the protection of data during transmission and static storage;
[0195] S58. Obtain the latest software update and patch records for the device, compare the update logs released by the manufacturer or developer, and check whether there are any important security patches that have not been applied;
[0196] S59. Through the audit and logging system, extract the system's key operations and event logs and analyze whether there are abnormal behaviors in order to discover potential security threats or inconsistencies.
[0197] Preferably, S6 includes the following sub-steps:
[0198] S61. Obtain user device information and identify the device holder based on the device's unique identifier;
[0199] S62. Use encrypted communication protocols to ensure the security of data when users enter passwords or PIN codes;
[0200] S63. If the password or PIN code verification is successful, a request is sent to the server for secondary verification;
[0201] S64. After the server-side verification is passed, a one-time password OTP is generated and sent to the user's mobile phone through a secure channel;
[0202] S65. After receiving the OTP, the user enters it into the authentication system. If the OTP matches, the biometric data collection process is triggered;
[0203] S66. Use biometric hardware modules, including fingerprint and facial recognition sensors, to collect biometric data of users;
[0204] According to the type of biometric feature selected by the user, such as fingerprint or face, the corresponding sensor is used for data collection; high-quality biometric original images are obtained according to the sensor resolution and sampling speed; through the obtained original image, a feature extraction algorithm is used to obtain key biometric points, such as the detail points of the fingerprint and the key feature points of the face, so as to obtain a feature template, which will be used for matching later; through the feature template, a pattern matching algorithm is used to compare with the pre-stored biometric templates in the database, and the comparison algorithm is used to determine whether there is a matching user. In this process, the false acceptance rate and false rejection rate need to be considered to obtain the result of user authentication; after obtaining the authentication result, the user's authority level is judged through the security protocols and standards in the database to determine the user's access rights and operating scope; according to the system's ability to resist damage and deception attacks, a security assessment is used to obtain the system's overall security score, which reflects the system's security protection level and provides support for subsequent security upgrades and improvements. Provides a basis; through the system's security score, determine whether it is necessary to upgrade hardware equipment or software algorithms to achieve higher security performance; obtain user experience feedback from the system, and determine user experience satisfaction through recognition speed and user acceptance; obtain a comprehensive evaluation of user experience and provide user feedback for system optimization; through the evaluation of user experience, use the system upgrade capability to decide whether to adjust the system to improve user experience; based on the performance of the system after the upgrade, through environmental adaptability assessment, obtain the system's reliability score under different light and temperature changes to ensure the stability of the biometric system under various conditions and the consistency of long-term performance; after obtaining the reliability score, use a regulatory compliance audit to determine whether the system complies with local privacy regulations and international biometric standards; through the results of regulatory compliance, obtain the final deployment and operation and maintenance plan of the system, consider privacy protection measures, such as anonymization of biometric information and cancellation and deletion mechanisms for biometric data, to ensure the privacy of user data;
[0205] S67. Compare the biometric data with the user biometric template stored on the server to determine whether the user is an authorized user;
[0206] S68. If the biometric data verification is successful, the final authorization decision is made in combination with the user's geographic location information;
[0207] Obtain device information and the user's software environment based on the user's device ID and user agent string; use multiple location sources, such as GPS, Wi-Fi, cellular data, IP address, and Bluetooth beacons, combined with other sensor data, such as accelerometers and gyroscopes, to obtain the user's location coordinates and location accuracy; obtain the movement speed and current timestamp of the user's device; determine the rationality of the current location through the user's historical geographic location data and normal login location habits; obtain the user's network environment information, including whether to use public Wi-Fi, VPN, or mobile network operators, to determine the current network security status; authenticate based on the username / account and password provided by the user, and require the user to complete two-factor authentication, such as entering a text message Verification code or email verification code, as well as possible biometric data verification, ensure that the user is a legitimate identity; determine whether the user allows the use of location information in the current business scenario through the user's privacy settings and location sharing preferences; combine authorization rules, including the allowed location range, location-based access control policies and permissions, and time limits to determine whether the user has authorization to operate; obtain regulatory requirements information, such as GDPR regulations and data security standards, to ensure that the acquisition, processing and storage of all location information comply with legal and regulatory requirements; comprehensively consider factors such as user device information, location information, user verification information, authorization rules, user behavior patterns, and network environment, and ultimately determine whether the user has the authority to perform the requested operation.
[0208] Preferably, the S7 includes the following sub-steps:
[0209] S71. Obtain user identity information and device information: Through the authentication service, collect the user's username, user ID and device ID information. If the user identity authentication is successful, continue processing; if it fails, deny access;
[0210] S72. Determine the user role: According to the user ID and organizational information, query the role management database to obtain the user's role name and its corresponding permission set;
[0211] S73. Determine the device security status: query the device information database based on the device ID to determine whether the device meets the security configuration requirements. If the device is not secure, restrict access; if the device is secure, continue the process;
[0212] S74. Retrieve access control list: query ACL information based on resource identifier to determine whether the user and his device are in the user list allowed to access;
[0213] S75. Apply permissions through role-based access control rules: If the user and device are in the access control list, combined with the user role information, the RBAC system applies the access rights corresponding to the role to the user;
[0214] S76. Application context information: Refer to the current time and the user's network location information, and use the access control policy to determine whether the user meets the access conditions, including access rights during working hours;
[0215] S77. Determine resource access level: Use different permissions to restrict or allow user operations on resources based on the sensitivity level and location of the resource;
[0216] S78. Application strategy and audit: Based on the set access control strategy and audit strategy, the user's access behavior is recorded, and on this basis, monitoring and auditing are carried out;
[0217] S79. Audit log analysis: Perform analysis based on user access behavior recorded in the audit log. If abnormal behavior is found, the security response mechanism is triggered; if the analysis is normal, the access control process is completed.
[0218] Preferably, the S8 includes the following sub-steps:
[0219] S81. Configure a central log management system and use time synchronization protocols such as NTP to ensure that the timestamps of each system are accurate and consistent;
[0220] S82. Set the marking rules for the log source, obtain the identification information of each system and device, and include this information in the log message;
[0221] S83. Implement log encryption and access control mechanisms to encrypt and store sensitive log data;
[0222] S84. Build rules and policies to classify and tag logs according to event types;
[0223] S85. Develop and apply user authentication and tracking policies, and indicate the identity of users in log records;
[0224] S86. Integrate advanced log analysis tools to conduct in-depth analysis of collected log data;
[0225] S87. Implement real-time monitoring and alert mechanisms to trigger alerts when suspicious activities occur;
[0226] S88. Establish data retention and backup strategies to ensure persistent storage and recovery capabilities of log data in accordance with regulations and business requirements;
[0227] S89. Deploy a scale-adaptive log collection and normalization system to support processing of high data volumes and multiple log formats.
[0228] Compared with the prior art, the present invention has the following beneficial effects:
[0229] The present invention allocates a unique identifier to each mobile terminal device through an Internet of Things device management platform, registers its hardware fingerprint information to track the identity of the device, and adopts a key generation algorithm to generate a pair of asymmetric keys or a group of symmetric keys for each mobile terminal device, designs an authentication protocol suitable for mobile terminal devices, adopts an authentication mechanism based on SSL / TLS, defines the communication process and handshake mechanism between devices, and solves the problems of device identity authentication and secure communication; verifies whether the software and hardware of the mobile terminal device have been modified without authorization through secure startup or remote authentication technology, deploys a user authentication mechanism, and performs multi-factor authentication in combination with the identity authentication information of the device holder, and solves the problems of device integrity and user authentication; deploys a log management system to record the authentication process and device activities in detail, cooperates with a digital certificate issuing authority to issue digital certificates to mobile terminal devices, establishes a trust chain, and solves the problems of auditing and management.
[0230] Embodiment 2:
[0231] like Fig.10 As shown, an embodiment of the present invention provides a trusted authentication system for mobile terminal devices based on the Internet of Things, including a device identity allocation module, a security key generation module, an authentication protocol design module, an encryption technology implementation module, a device integrity check execution module, a user authentication verification module, an authority control implementation module, an audit and log system configuration module, and a certificate issuance and management implementation module;
[0232] The device identity allocation module is used to allocate a unique identifier to each mobile terminal device through the IoT device management platform, and register its hardware fingerprint information, including device ID and MAC address, and track the identity of the device through these identifiers;
[0233] The security key generation module is used to generate a pair of asymmetric keys or a group of symmetric keys for each mobile terminal device using a key generation algorithm for subsequent device authentication and communication encryption, ensuring that the key distribution is random and unpredictable;
[0234] The authentication protocol design module is used to design an authentication protocol suitable for mobile terminal devices according to the capabilities and authentication requirements of the devices, adopt an authentication mechanism based on SSL / TLS, define the communication process and handshake mechanism between devices, and ensure encryption and identity authentication during the transmission process;
[0235] The encryption technology implementation module is used to select the encryption algorithm AES or ECC to encrypt the communication data between devices to ensure that the confidentiality and integrity of the data are protected during the transmission process, and the previously generated security key is used in the encryption process;
[0236] The device integrity check execution module is used to verify whether the software and hardware of the mobile terminal device have been modified without authorization through secure boot or remote authentication technology, ensuring that the device is in a known and secure state;
[0237] The user authentication verification module is used to deploy a user authentication mechanism, combining the identity verification information of the device holder, including password or biometric data, to perform multi-factor authentication to ensure that only authorized users can operate the device;
[0238] The permission control implementation module is used to obtain the role information of the device and the user, and assign appropriate access rights to the device and the user through the access control list or the role-based access control, so as to restrict the access to sensitive data and resources;
[0239] The audit and log system configuration module is used to deploy a log management system to record the authentication process and device activities in detail. The logs are used for monitoring, post-analysis and auditing, which helps to identify potential security issues.
[0240] The certificate issuance and management implementation module is used to cooperate with the digital certificate issuing authority through the digital certificate management system to issue digital certificates to mobile terminal devices and establish a trust chain. The digital certificate is used to strengthen the identity authentication process of the device.
[0241] The foregoing examples are merely illustrative and are used to explain some features of the method of the present invention. The appended claims are intended to claim the widest possible range that can be conceived, and the embodiments presented herein are only illustrations of selected implementations according to the combination of all possible embodiments. Therefore, it is the applicant's intention that the appended claims are not limited by the selection of examples that illustrate the features of the present invention. Some numerical ranges used in the claims also include sub-ranges within them, and changes in these ranges should also be interpreted as being covered by the appended claims where possible.
Claims
1. A trusted authentication method for mobile terminal devices based on the Internet of Things, characterized in that: The following steps are involved: S1. Assign device identity: Assign a unique identifier to each mobile terminal device through the IoT device management platform, and register its hardware fingerprint information, including device ID and MAC address, and track the identity of the device through these identifiers; S2. Generate security keys: Use a key generation algorithm to generate a pair of asymmetric keys or a set of symmetric keys for each mobile terminal device, which are used for subsequent device authentication and communication encryption to ensure that the key distribution is random and unpredictable; S3. Design authentication protocol: Design an authentication protocol suitable for mobile terminal devices based on the device capabilities and authentication requirements, adopt an authentication mechanism based on SSL / TLS, define the communication process and handshake mechanism between devices, and ensure encryption and identity authentication during the transmission process; S4. Implement encryption technology: Select encryption algorithm AES or ECC to encrypt the communication data between devices to ensure the confidentiality and integrity of the data during transmission. The encryption process uses the previously generated security key; S5. Perform device integrity check: Verify that the software and hardware of the mobile terminal device have not been modified without authorization through secure boot or remote authentication technology to ensure that the device is in a known and secure state; S6. Verify user authentication: Deploy a user authentication mechanism that combines the device owner's identity verification information, including passwords or biometric data, to perform multi-factor authentication to ensure that only authorized users can operate the device; S7. Implement permission control: Obtain the role information of devices and users, assign appropriate access rights to devices and users through access control lists or role-based access control, and restrict access to sensitive data and resources; S8. Configure audit and log system: Deploy a log management system to record the authentication process and device activities in detail. Logs are used for monitoring, post-analysis and auditing, which helps identify potential security issues. S9. Implement certificate issuance and management: Through the digital certificate management system, collaborate with the digital certificate issuing authority to issue digital certificates for mobile terminal devices and establish a trust chain. Digital certificates are used to strengthen the identity authentication process of the device; The S1 includes the following sub-steps: S11. Assign device identifier: Generate a unique device ID for each mobile terminal device through the IoT device management platform to ensure that each device can be individually identified in the system; S12. Record device hardware information: Use automated tools to read the MAC address, CPU model, memory size, and storage space hardware specifications of the terminal device to form a device hardware fingerprint; S13. Register other device attributes: obtain the device type, serial number, firmware / software version, and associate this information with the device ID to build a complete device profile; S14. Configure network information: Set the device to automatically report its network type and IP address network information when connected to the IoT platform to facilitate remote access and management of the device; S15. Storage of location and status data: The device’s built-in GPS module positioning technology is used to regularly update the device’s location information and detect the device’s status information, including power level and operating status, and record it on the platform; S16. Install security certificate: Push and install the security certificate to the device to facilitate encrypted communication of the device and to authenticate the legitimacy of the device; S17. Set up a status monitoring mechanism: Build an equipment status monitoring system to capture and analyze the equipment's operating data in real time. If the equipment status is abnormal, trigger an early warning mechanism; S18. Logs and operation records: Design a log system to capture the operation records of the device, including instruction execution and data transmission records, for auditing and troubleshooting; S19. Implement subscription service management: automatically assign appropriate services to devices based on device type and user needs, and monitor service status to ensure service continuity and reliability; The S2 includes the following sub-steps: S21. Select RSA as the asymmetric encryption algorithm through the cryptography library OpenSSL. If the library provides multiple algorithms, determine the most suitable algorithm based on performance and security requirements; S22. Using the library function, obtain the currently recommended key length parameter, and for RSA, obtain its 2048-bit parameter setting; S23. Use the random number generator and RSA algorithm in the cryptography library to generate an asymmetric key pair and determine whether the generation process meets the requirements of randomness and uniqueness; S24. The private key is stored in a confidential area of the mobile terminal device through an encrypted storage mechanism, and a hardware security module HSM is used to prevent unauthorized access; S25. Obtain the public key and send it to the server through the device registration process, so that in subsequent communications, the server can use the public key to verify the identity of the device or encrypt messages to the device; S26. Select AES as the symmetric encryption algorithm and obtain a 256-bit key length setting to meet high security requirements; S27. Generate a symmetric key using the CSPRNG in the cryptography library and determine whether the key meets the standards of randomness and uniqueness; S28. The symmetric key is encrypted using the public key of the device through asymmetric encryption, and then the encrypted symmetric key is sent to the mobile terminal to ensure the security of the key distribution process; S29. For the received encrypted symmetric key, the mobile terminal uses its private key to decrypt and obtain the symmetric key, which is ready for device authentication and communication encryption; The S3 includes the following sub-steps: S31. Based on the processing capability of the mobile terminal device, adopt appropriate encryption algorithms and security parameter configurations to achieve effective execution of SSL / TLS operations, and select encryption algorithms that can run efficiently on the device and lightweight encryption algorithms to reduce processing delays; S32. Obtain storage capacity information of the device to determine whether there is enough space to store the digital certificate and private key. If the storage space is insufficient, perform storage optimization, including compressing the certificate storage or using a smaller key size; S33. Through the network connection test, determine whether the mobile terminal device can establish and maintain a stable data transmission connection. The network connection test result determines whether additional network optimization measures are needed, including adjusting the data packet size or selecting a more stable network protocol; S34. Design a two-way authentication process where both the client and the server need to confirm each other's identity through mutual verification of digital certificates, including embedding certificate verification steps in the authentication protocol and determining the validity and credibility of the certificate chain; S35. Implement certificate management strategies to ensure that digital certificates can be safely installed and updated on mobile devices. Devices are equipped with certificate management functions to enable digital certificates to be updated in a timely manner before expiration or when revoked. S36. Design access control mechanisms to allow only authenticated devices to obtain access rights to protected resources, and assign permissions and control resources to devices based on authentication results; S37. For the handshake mechanism, formulate a process that adapts to the performance of mobile devices. From the client Hello to the server Finished message, each step takes into account efficiency and security. The algorithm selection during the handshake process affects the performance of the authentication protocol. S38. During the communication process, use message authentication code MAC or digital signature to implement encryption and integrity protection measures to ensure the confidentiality and integrity of data; S39. Select efficient encryption algorithms and the latest TLS versions. Determine the most suitable combination for mobile devices by testing the performance of different algorithms and protocol versions. The performance test results determine the encryption algorithm and TLS version that are ultimately adopted. The S4 includes the following sub-steps: S41. Based on the sensitivity and protection requirements of the communication data, if the data requires extremely high security, select the AES algorithm and use a 256-bit key; If the communicating parties need to use asymmetric encryption for secure key exchange and digital signature, select ECC and use an appropriate key length to ensure equivalent security strength; S42. When using a high-quality random number generator to generate a key, if it is an AES symmetric key, ensure that the generated key is sufficiently random to prevent predictable attacks; if it is an ECC asymmetric key pair, generate a pair of private and public keys at the same time, the private key is highly confidential, and the public key is used to exchange encrypted information with other communication entities; S43. When distributing keys through a secure channel, if an AES key is used, the security of the channel is guaranteed to prevent the key from being intercepted during transmission; if an ECC key is used, only the private key needs to be distributed securely, and the public key can be made public; S44. After obtaining the key, keep the key safe through a secure storage mechanism. If it is an AES key, use a hardware security module HSM or other forms of secure storage; for ECC private keys, also use HSM or encrypted software storage containers to ensure that the private key is not accessed by unauthorized persons; S45. When updating keys regularly, the keys are updated through an automated key management system. For AES keys, the keys are replaced periodically to avoid security risks caused by long-term use of the same key; for ECC keys, updating the private key also regenerates the corresponding public key and distributes it to relevant communication entities; S46. When the key needs to be invalidated and destroyed, it should be processed through a professional key destruction program. For AES keys, ensure that the key is completely deleted from all systems and cannot be recovered; for ECC keys, destroy the private key to avoid any possible leakage; S47. If the ECC algorithm is selected, the ECDH protocol is used for key negotiation, and the shared key material is calculated by elliptic curve arithmetic, thereby allowing the communicating parties to establish a shared key without directly exchanging private information; S48. When selecting the AES algorithm mode, if the communication data contains fixed-mode content, avoid using the ECB mode to prevent mode leakage; when using the CBC mode, pad the data to meet the requirements of block encryption to ensure that all data blocks can be correctly encrypted; S49. Verify that the data has not been tampered with through integrity and authentication mechanisms. For data encrypted using AES, the message authentication code MAC is combined to provide data integrity and source verification; for data encrypted using ECC, a digital signature is attached to the message to provide authentication and non-repudiation; The S5 includes the following sub-steps: S51. According to the public key information provided by the manufacturer of the mobile terminal device, obtain the root certificate used by the device in the secure boot process to ensure that the basis for subsequent verification is officially certified; S52. If the root certificate matches, chain verification is performed on the firmware, and the digital signature of each startup component is checked layer by layer to ensure that each link from the boot loader to the operating system kernel has not been tampered with; S53. Use a remote server to issue an authentication request to the device, requiring the device to provide proof of its current state, including a measured startup log and a certificate signed by the device's private key; S54. For the received startup log and certificate, the remote server uses the corresponding public key to verify whether the device is in a known and secure state; S55. Obtain the integrity protection status of the operating system level, including system file protection and application isolation, to ensure that key system files have not been modified without authorization; S56. Perform mandatory access control checks through the SELinux policy provided by the operating system to restrict and monitor the behavior of processes to ensure that they do not exceed the preset permissions; S57. Verify the encryption status of stored data and communication security through the encryption module of the device to ensure the protection of data during transmission and static storage; S58. Obtain the latest software update and patch records for the device, compare the update logs released by the manufacturer or developer, and check whether there are any important security patches that have not been applied; S59. Through the audit and logging system, extract the system key operation and event logs, analyze whether there are abnormal behaviors, so as to find potential security threats or inconsistencies; The S6 includes the following sub-steps: S61. Obtain user device information and identify the device holder based on the device's unique identifier; S62. Use encrypted communication protocols to ensure the security of data when users enter passwords or PIN codes; S63. If the password or PIN code verification is successful, a request is sent to the server for secondary verification; S64. After the server-side verification is passed, a one-time password OTP is generated and sent to the user's mobile phone through a secure channel; S65. After receiving the OTP, the user enters it into the authentication system. If the OTP matches, the biometric data collection process is triggered; S66. Use biometric hardware modules, including fingerprint and facial recognition sensors, to collect biometric data of users; S67. Compare the biometric data with the user biometric template stored on the server to determine whether the user is an authorized user; S68. If the biometric data verification is successful, the final authorization decision is made in combination with the user's geographic location information.
2. The method for authenticating a mobile terminal device based on the Internet of Things according to claim 1, characterized in that: The S7 includes the following sub-steps: S71. Obtain user identity information and device information: Through the authentication service, collect the user's username, user ID and device ID information. If the user identity authentication is successful, continue processing; if it fails, deny access; S72. Determine the user role: According to the user ID and organizational information, query the role management database to obtain the user's role name and its corresponding permission set; S73. Determine the device security status: query the device information database based on the device ID to determine whether the device meets the security configuration requirements. If the device is not secure, restrict access; if the device is secure, continue the process; S74. Retrieve access control list: query ACL information based on resource identifier to determine whether the user and his device are in the user list allowed to access; S75. Apply permissions through role-based access control rules: If the user and device are in the access control list, combined with the user role information, the RBAC system applies the access rights corresponding to the role to the user; S76. Application context information: Refer to the current time and the user's network location information, and use the access control policy to determine whether the user meets the access conditions, including access rights during working hours; S77. Determine resource access level: Use different permissions to restrict or allow user operations on resources based on the sensitivity level and location of the resource; S78. Application strategy and audit: Based on the set access control strategy and audit strategy, the user's access behavior is recorded, and on this basis, monitoring and auditing are carried out; S79. Audit log analysis: Perform analysis based on user access behavior recorded in the audit log. If abnormal behavior is found, the security response mechanism is triggered; if the analysis is normal, the access control process is completed.
3. The method for authenticating a mobile terminal device based on the Internet of Things according to claim 2, characterized in that: The S8 includes the following sub-steps: S81. Configure a central log management system and use the time synchronization protocol NTP to ensure that the timestamps of each system are accurate and consistent; S82. Set the marking rules for the log source, obtain the identification information of each system and device, and include this information in the log message; S83. Implement log encryption and access control mechanisms to encrypt and store sensitive log data; S84. Build rules and policies to classify and tag logs according to event types; S85. Develop and apply user authentication and tracking policies, and indicate the identity of users in log records; S86. Integrate advanced log analysis tools to conduct in-depth analysis of collected log data; S87. Implement real-time monitoring and alert mechanisms to trigger alerts when suspicious activities occur; S88. Establish data retention and backup strategies to ensure persistent storage and recovery capabilities of log data in accordance with regulations and business requirements; S89. Deploy a scale-adaptive log collection and normalization system to support processing of high data volumes and multiple log formats.
4. A trusted authentication system for mobile terminal devices based on the Internet of Things, characterized in that: A trusted authentication method for a mobile terminal device based on the Internet of Things for implementing any one of claims 1 to 3 above, comprising a device identity allocation module, a security key generation module, an authentication protocol design module, an encryption technology implementation module, a device integrity check execution module, a user authentication verification module, an authority control implementation module, an audit and log system configuration module, and a certificate issuance and management implementation module; The device identity allocation module is used to allocate a unique identifier to each mobile terminal device through the IoT device management platform, and register its hardware fingerprint information, including device ID and MAC address, and track the identity of the device through these identifiers; The security key generation module is used to generate a pair of asymmetric keys or a group of symmetric keys for each mobile terminal device using a key generation algorithm, which is used for subsequent device authentication and communication encryption, ensuring that the key distribution is random and unpredictable; The authentication protocol design module is used to design an authentication protocol suitable for mobile terminal devices according to the capabilities and authentication requirements of the devices, adopt an authentication mechanism based on SSL / TLS, define the communication process and handshake mechanism between devices, and ensure encryption and identity authentication during the transmission process; The encryption technology implementation module is used to select the encryption algorithm AES or ECC to encrypt the communication data between devices to ensure that the confidentiality and integrity of the data are protected during the transmission process, and the previously generated security key is used in the encryption process; The device integrity check execution module is used to verify whether the software and hardware of the mobile terminal device have been modified without authorization through secure boot or remote authentication technology, ensuring that the device is in a known and secure state; The user authentication verification module is used to deploy a user authentication mechanism, combining the identity verification information of the device holder, including password or biometric data, to perform multi-factor authentication to ensure that only authorized users can operate the device; The permission control implementation module is used to obtain the role information of the device and the user, and assign appropriate access rights to the device and the user through the access control list or the role-based access control, so as to restrict the access to sensitive data and resources; The audit and log system configuration module is used to deploy a log management system to record the authentication process and device activities in detail. The logs are used for monitoring, post-analysis and auditing, which helps to identify potential security issues. The certificate issuance and management implementation module is used to cooperate with the digital certificate issuing authority through the digital certificate management system to issue digital certificates to mobile terminal devices and establish a trust chain. The digital certificate is used to strengthen the identity authentication process of the device.
