Sensitive data import and export system and method based on baseboard management controller

Abstract

The present application discloses a sensitive data import and export system and method based on a baseboard management controller, which relates to the field of information security technology, including: an encryption algorithm selection module, which is used to select a target encryption algorithm based on a context-aware intelligent encryption algorithm negotiation strategy; corresponding encryption, decryption and communication operations are performed through an encryption module, a decryption module and a communication module; a zero-trust adaptation module, which is used to dynamically adjust the import and export operation permissions based on a zero-trust strategy; the security level of the system is improved through key management, authentication and data integrity verification modules; a plug-in module, which is used to load each module in the form of a plug-in, and reserve an interface for future algorithm replacement and encryption strategy expansion, thereby solving the technical problems in related technologies such as limited export functions, inability to perform complete backup, lack of flexible encryption capabilities, lack of client encryption capabilities and algorithm negotiation mechanisms, and difficulty in adapting to different encryption compliance requirements.

Description

Technical Field

[0001] The present application relates to the field of information security technology, and in particular to a system and method for importing and exporting sensitive data based on a baseboard management controller. Background Art

[0002] The current industry-wide security mechanism uses functional restrictions to achieve data protection. For example, some baseboard management controller (BMC) implementations prohibit the export of configuration files containing user authentication information and block the import of encrypted sensitive data. While this security strategy effectively reduces the risk of data leakage, it creates significant functional conflicts in actual operations and maintenance. This imbalance between security and convenience severely restricts operational efficiency, creating a significant conflict between security management and business needs, especially in scenarios such as large-scale data center automated operations and maintenance, cross-room configuration migration, and rapid reconstruction of disaster recovery systems.

[0003] The existing technical architecture lacks a middleware system with algorithm negotiation capabilities to securely coordinate the transmission and processing of sensitive data between clients and servers. This is specifically manifested in the following three aspects:

[0004] 1. At the encryption mechanism level, there is a lack of a standardized encryption and decryption protocol framework between the client and the server, which makes it impossible for both ends to establish a unified encryption processing process and difficult to achieve end-to-end secure data exchange.

[0005] 2. At the key management level, the existing solution lacks a dynamic key negotiation and management module and cannot support key functions such as the generation, exchange, and rotation of security keys, which directly restricts the system's ability to process sensitive data.

[0006] 3. At the algorithm selection level, the system lacks a flexible encryption algorithm selection mechanism. It can neither intelligently match symmetric or asymmetric encryption methods according to data types, nor adapt to changing requirements in scenarios with different security levels.

[0007] In the field of BMC configuration management, existing technologies mainly use the following two methods to process sensitive information:

[0008] 1. Restrict the export of sensitive data: The exported content is processed compulsorily through the preset security policy, that is, when generating the configuration file, sensitive fields are automatically erased or replaced;

[0009] 2. Static encryption mode: This mode uses a pre-set encryption algorithm to automatically encrypt sensitive fields. However, in this mode, the encryption algorithm and key management policy are fixed in the system firmware. There are no user-configurable encryption parameter options, and the protection strength cannot be dynamically adjusted according to different security requirements.

[0010] In addition, there are widespread security gaps in the configuration import process. Even if users update sensitive information locally, due to the lack of standardized client encryption modules and secure transmission protocols, these key data are often temporarily stored in plain text in the local environment, making the configuration file editing and transmission process a potential attack surface, making it difficult for BMC configuration management to strike a balance between security and functionality.

[0011] Existing BMC configuration import and export methods have the following main defects:

[0012] 1. Functional integrity defects: Due to mandatory restrictions of security policies, the system cannot completely export configuration files containing sensitive fields, seriously affecting the reliability of system migration and disaster recovery.

[0013] 2. Rigid encryption mechanism: Existing encryption schemes are implemented using pre-fixed algorithms, making it difficult to switch between symmetric encryption, asymmetric encryption, and other strategies based on actual user needs.

[0014] 3. No client-side encryption capability: From user input to server receipt, sensitive data lacks necessary encryption protection measures on the client side, posing a huge risk of data leakage.

[0015] 4. Lack of negotiation mechanism: There is a lack of a negotiation mechanism for encryption algorithms and keys between the client and the server, which makes it impossible to dynamically negotiate encryption and decryption strategies, lacks a secure channel for key exchange, and makes it difficult to ensure version compatibility.

[0016] 5. Lack of security verification: The existing import and export processes cannot verify data integrity and identity authenticity, making it difficult to detect configuration tampering and unable to identify illegal requests, exposing the system to high-risk threats such as man-in-the-middle attacks and data forgery.

[0017] 6. Scalability bottleneck: Existing encryption methods cannot adapt to new encryption algorithms, are difficult to meet regional compliance requirements, and do not support user-customized security policies.

[0018] In summary, the export function of existing technologies is limited, and they cannot perform complete backups. They lack flexible encryption capabilities and client encryption capabilities and algorithm negotiation mechanisms. In addition, existing technologies do not have data integrity and authentication mechanisms, have poor scalability, and are difficult to adapt to different encryption compliance requirements, which urgently need to be resolved. Summary of the Invention

[0019] The present application provides a sensitive data import and export system and method based on a baseboard management controller to at least solve the technical problems in related technologies, such as limited export functions, inability to perform complete backup, lack of flexible encryption capabilities, and lack of client encryption capabilities and algorithm negotiation mechanisms. In addition, the existing technology does not have data integrity and authentication mechanisms, has poor scalability, and is difficult to adapt to different encryption compliance requirements.

[0020] The present application also provides a sensitive data import and export system based on a baseboard management controller, comprising: an encryption algorithm selection module, which is used to collect corresponding context information through a target client and a target server respectively, to generate a list of encryption algorithms supported by the target client and the target server according to the context information, and to score the encryption algorithm list, and to negotiate and select the encryption algorithm list after scoring to obtain a corresponding target encryption algorithm, and to determine a key corresponding to the target encryption algorithm; an encryption module, which is used to obtain the original plaintext sensitive data input by the client user in the sensitive data import stage, or to obtain the corresponding exported sensitive data from the baseboard management controller of the target server in the sensitive data export stage, and to use the target encryption algorithm and the key to encrypt the original plaintext sensitive data or the exported sensitive data. Sensitive data is encrypted to obtain corresponding sensitive encrypted data; a decryption module is used to decrypt the sensitive encrypted data using the key through the encryption and decryption system of the target server during the sensitive data import phase to obtain sensitive decrypted data; a communication module is used to export the sensitive encrypted data that has passed the preset data integrity verification operation to the target client application during the sensitive data export phase, or to import the sensitive decrypted data that has passed the preset data integrity verification operation to the baseboard management controller of the target server during the sensitive data import phase; a zero trust adaptation module is used to perform dynamic identity authentication, real-time policy engine decision-making, session persistence verification and context verification operations based on the preset zero trust policy during the sensitive data export phase and the sensitive data import phase to dynamically adjust the import and export operation permissions.

[0021] The present application provides a sensitive data import and export method based on a baseboard management controller, which is applied in the sensitive data import stage, and includes the following steps: sending a configuration import request to the encryption and decryption system of the target client through a target client application, so that the encryption and decryption system of the target client obtains a list of encryption algorithms supported by the target server according to the configuration import request; based on the encryption algorithm list, performing an encryption algorithm negotiation operation between the encryption and decryption system of the target server and the encryption and decryption system of the target client, so as to determine the corresponding target encryption algorithm and the key corresponding to the target encryption algorithm on the target server; obtaining plaintext sensitive data input by the client user, and encrypting the plaintext sensitive data using the target encryption algorithm through the encryption and decryption system of the target client to obtain corresponding sensitive encrypted data, and performing data integrity verification on the sensitive encrypted data to obtain sensitive encrypted data that passes the data integrity verification; decrypting the sensitive encrypted data using the key in the encryption and decryption system of the target server to obtain corresponding sensitive decrypted data, and performing data integrity verification on the sensitive decrypted data, and importing the sensitive decrypted data that passes the data integrity verification into the baseboard management controller of the target server.

[0022] The present application provides a sensitive data import and export method based on a baseboard management controller, which is applied in the sensitive data export stage, and includes the following steps: sending a configuration export request to the encryption and decryption system of the target client through a target client application, so that the encryption and decryption system of the target client obtains a list of encryption algorithms supported by the encryption and decryption system of the target server according to the configuration export request; performing an encryption algorithm negotiation operation between the encryption and decryption system of the target server and the encryption and decryption system of the target client based on the encryption algorithm list, so as to determine a corresponding target encryption algorithm and a key corresponding to the target encryption algorithm on the target server; sending a sensitive data request to the baseboard management controller of the target server through the target client application, so that the baseboard management controller obtains corresponding exported sensitive data, and sends the exported sensitive data to the encryption and decryption system of the target server, so that the exported sensitive data is encrypted using the target encryption algorithm in the encryption and decryption system of the target server, and the encrypted exported sensitive data is sent to the encryption and decryption system of the target client; combining the encrypted sensitive data and preset configuration data in the encryption and decryption system of the target client to obtain corresponding target configuration information, and exporting the target configuration information to the target client application.

[0023] The present application also provides an electronic device, comprising: a memory for storing a computer program; and a processor for implementing the steps of any of the above-mentioned methods for importing and exporting sensitive data based on a baseboard management controller when executing the computer program.

[0024] The present application also provides a computer-readable storage medium, in which a computer program is stored. When the computer program is executed by a processor, the steps of any of the above-mentioned sensitive data import and export methods based on the baseboard management controller are implemented.

[0025] The present application also provides a computer program product, including a computer program, which, when executed by a processor, implements the steps of any of the above-mentioned sensitive data import and export methods based on a baseboard management controller.

[0026] Through this application, sensitive data can be safely exported in encrypted form, ensuring the integrity of configuration files without leaking sensitive information; users can perform local encryption on plain text input of sensitive fields when importing configurations to ensure transmission security; in addition, this application designs a set of encryption and decryption modules independent of the BMC system, deployed on the client and server, to achieve local encryption and remote decryption of data; and introduces an encryption algorithm negotiation mechanism to support multiple strategies such as symmetric encryption and asymmetric encryption, which users can choose freely; at the same time, this application provides key management, authentication and data integrity verification modules to improve the security level of the overall system; in addition, this application builds a standardized communication protocol to ensure customer It enables secure communication between the encryption and decryption systems of the end and the server, and encrypts and verifies each step of the data interaction process, and reserves interfaces for future algorithm replacement and encryption strategy expansion, with good scalability and compatibility. Therefore, it can solve the problems in related technologies such as limited export functions, inability to perform complete backups, lack of flexible encryption capabilities, and lack of client encryption capabilities and algorithm negotiation mechanisms. In addition, the existing technology does not have data integrity and authentication mechanisms, poor scalability, and difficulty in adapting to different encryption compliance requirements. It overcomes the difficulty of secure processing of sensitive data in the process of BMC configuration import and export, and effectively improves the technical effect of the integrity, security and flexibility of configuration management. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] In order to more clearly illustrate the embodiments of the present application, the following is a brief introduction to the drawings required for use in the embodiments. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0028] Figure 1 This is an example diagram of a sensitive data import and export system based on a baseboard management controller provided according to an embodiment of the present application;

[0029] Figure 2 A schematic diagram of an encryption algorithm selection module architecture provided for one embodiment of the present application;

[0030] Figure 3 A schematic diagram of an encryption module architecture provided for one embodiment of the present application;

[0031] Figure 4 A schematic diagram of collaboration between an encryption module and other modules provided in one embodiment of the present application;

[0032] Figure 5 A schematic diagram of a decryption module architecture provided for one embodiment of the present application;

[0033] Figure 6 A schematic diagram of a decryption module cooperating with other modules provided in one embodiment of the present application;

[0034] Figure 7 A schematic diagram of a communication module architecture provided for one embodiment of the present application;

[0035] Figure 8 A schematic diagram of a key management module architecture provided for one embodiment of the present application;

[0036] Figure 9 A schematic diagram of collaboration between a key management module and other modules provided in one embodiment of the present application;

[0037] Figure 10 A schematic diagram of a data integrity verification module architecture provided for one embodiment of the present application;

[0038] Figure 11 A schematic diagram of the collaboration between a data integrity check module and other modules provided in one embodiment of the present application;

[0039] Figure 12 A schematic diagram of an authentication module architecture provided for one embodiment of the present application;

[0040] Figure 13 A schematic diagram of an authentication module and other modules cooperating in accordance with an embodiment of the present application;

[0041] Figure 14 A schematic diagram of the overall architecture of a sensitive information encryption and decryption system provided for one embodiment of the present application;

[0042] Figure 15 A flowchart of a sensitive data import and export method based on a baseboard management controller applied in the sensitive data import stage is provided in one embodiment of the present application;

[0043] Figure 16 A schematic diagram of a sensitive data configuration import timing provided by one embodiment of the present application;

[0044] Figure 17A flowchart of a sensitive data import and export method based on a baseboard management controller applied in the sensitive data export stage is provided in one embodiment of the present application;

[0045] Figure 18 A schematic diagram of a sensitive data configuration export timing is provided for an embodiment of the present application.

[0046] Among them, 10-Sensitive data import and export system based on baseboard management controller, 100-Encryption algorithm selection module, 200-Encryption module, 300-Decryption module, 400-Communication module, 500-Zero Trust Adaptation Module, 600-Authentication and Authorization Module, 700-Key Management Module, 800-Data Integrity Verification Module, 900-Plug-in Module. DETAILED DESCRIPTION

[0047] The following will be combined with the accompanying drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0048] It should be noted that, in the description of this application, the terms "comprises," "includes," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article, or device. The terms "first," "second," etc., in this application are used to distinguish similar objects, and are not used to describe a particular order or sequence.

[0049] In order to enable those skilled in the art to better understand the present application, the present application is further described in detail below with reference to the accompanying drawings and specific implementation methods.

[0050] In conjunction with the specific application environment architecture or specific hardware architecture on which the execution of the sensitive data import and export method based on the baseboard management controller depends, the specific application environment architecture or specific hardware architecture is described herein.

[0051] An embodiment of the present application provides a sensitive data import and export system based on a baseboard management controller.

[0052] like Figure 1As shown, this is an example diagram of a sensitive data import and export system based on a baseboard management controller according to an embodiment of the present application, wherein the sensitive data import and export system 10 based on a baseboard management controller includes: an encryption algorithm selection module 100, an encryption module 200, a decryption module 300, a communication module 400, and a zero-trust adaptation module 500.

[0053] Among them, the encryption algorithm selection module 100 is used to collect corresponding context information through the target client and the target server respectively, to generate a list of encryption algorithms supported by the target client and the target server according to the context information, and to score the encryption algorithm list, and to negotiate and select the encryption algorithm list after scoring to obtain the corresponding target encryption algorithm and determine the key corresponding to the target encryption algorithm.

[0054] The embodiment of the present application can first obtain a list of encryption algorithms supported by the server, and then perform an encryption algorithm negotiation operation between the server and the client through the encryption algorithm list, thereby selecting a consistent encryption algorithm (i.e., the target encryption algorithm) in the communication between the client and the BMC, and determining the key assurance algorithm corresponding to the target encryption algorithm.

[0055] Specifically, the embodiment of the present application can select a consistent encryption algorithm based on context-aware intelligent encryption algorithm negotiation. The specific process is as follows:

[0056] 1. Context information collection phase:

[0057] When establishing the initial connection, the client and server collect the following real-time environment parameters:

[0058] (1) Device capabilities: CPU (Central Processing Unit) performance, memory usage, hardware acceleration support (such as AES-NI (Advanced Encryption Standard New Instructions), national encryption chips);

[0059] (2) Network status: current latency, bandwidth stability, and packet loss rate;

[0060] (3) Security strategy: compliance requirements (such as GDPR (General Data Protection Regulation), SME Security 2.0), data sensitivity level;

[0061] (4) Threat intelligence: recent attack incidents targeting specific algorithms (such as AES (Advanced Encryption Standard) side channel attack warning).

[0062] This data is exchanged through a lightweight encrypted channel to ensure transmission security and integrity.

[0063] 2. Candidate algorithm generation and scoring

[0064] Based on the collected contextual information, each party generates a list of candidate algorithms (i.e., a list of encryption algorithms) and scores them based on multiple dimensions:

[0065] (1) Security score: algorithm strength (e.g., 256-bit key is better than 128-bit key), quantum resistance;

[0066] (2) Performance scoring: computational overhead, memory usage, and network adaptability;

[0067] (3) Compliance score: whether the corresponding data compliance requirements are met.

[0068] 3. Negotiation and selection:

[0069] The client and server exchange the scored candidate lists and reach consensus through the following steps:

[0070] (1) Prioritized intersection screening: select the three algorithms that are supported by both parties and have the highest scores;

[0071] (2) Environmental adaptation adjustment: Eliminate inapplicable options based on real-time network fluctuations (such as sudden increase in latency);

[0072] (3) Final confirmation: Confirm the selected algorithm combination through digital signature to prevent tampering by middlemen.

[0073] If a disagreement arises (e.g., the client prioritizes performance while the server enforces compliance), a hierarchical fallback mechanism is initiated:

[0074] Priority 1: Solutions that meet all hard requirements (such as regulatory compliance);

[0075] Second priority: solutions that optimize primary metrics (such as security or performance);

[0076] Third priority: emergency algorithms to ensure basic communications.

[0077] 4. Dynamic optimization during the session:

[0078] Continuously monitor environmental changes during communication and trigger the following adaptive behaviors:

[0079] (1) When the network deteriorates: automatically switch to the lightweight algorithm;

[0080] (2) Detecting an attack: Immediately enable the quantum-resistant temporary algorithm;

[0081] (3) Insufficient device resources: Downgrade encryption strength but maintain the minimum security threshold.

[0082] Each adjustment requires re-verification of device integrity and user permissions.

[0083] 5. Termination and Audit:

[0084] Perform safe cleanup at the end of the session:

[0085] (1) Destroy the temporary session key;

[0086] (2) Record the algorithm usage log (including selection reasons and environmental parameters);

[0087] (3) Generate encrypted summaries for compliance audits.

[0088] Therefore, the embodiments of the present application break the fixed priority through multi-factor dynamic weights, adjust the decision-making weights of security / performance / compliance according to real-time scenarios, and can maintain secure communications in scenarios such as network jitter and device degradation. The decision logic can be traced back for each algorithm selection, and the algorithm negotiation messages can be disguised as regular business data to resist traffic analysis attacks.

[0089] Optionally, in one embodiment of the present application, the encryption algorithm selection module 100 includes: a policy management unit, an algorithm capability identification unit, a negotiation processing unit and an interface service unit.

[0090] The policy management unit is used to dynamically adjust the security level of each encryption algorithm in the encryption algorithm list based on the preset current security policy, and configure the algorithm list to be enabled or disabled.

[0091] The algorithm capability identification unit is used to obtain the encryption algorithm list supported by the target server and query the enabled or disabled algorithm list to obtain the corresponding algorithm query result.

[0092] The negotiation processing unit is used to send an encryption algorithm list to a target client, select an encryption algorithm from the encryption algorithm list at the target client, and negotiate the encryption algorithm based on the algorithm query result and the security level to generate a target encryption algorithm.

[0093] The interface service unit is used to output the target encryption algorithm to the encryption module 200 and provide an interface for the encryption algorithm selection module 100 so that the key management module 700 and the communication module 400 call the encryption algorithm selection module 100.

[0094] In the actual implementation process, Figure 2 As shown, the encryption algorithm selection module 100 in the embodiment of the present application is mainly composed of a policy management unit, an algorithm capability identification unit, a negotiation processing unit and an interface service unit.

[0095] Specifically, the policy management unit in the embodiment of the present application is mainly used to set the default priority encryption algorithm (such as giving priority to safer or faster algorithms) by configuring the preferred algorithm through the user, and the system administrator can configure the algorithm enable or disable list to prevent the use of unsafe algorithms; in addition, the policy management unit can also support policy ID (auditable / rollback), that is, a unique identifier that identifies and distinguishes different policies, and can dynamically adjust the algorithm security level.

[0096] The algorithm capability identification unit can obtain the list of encryption algorithms supported by the local end (i.e., the client or server) and query the system policy to enable or disable algorithms. In the embodiment of the present application, the encryption algorithm list (i.e., the multiple encryption algorithms supported) includes symmetric encryption algorithms (such as AES-128, AES-256, etc.); asymmetric encryption algorithms (such as RSA (Rivest-Shamir-Adleman, asymmetric encryption algorithm), SM2, etc.); hybrid encryption algorithms, such as ECHD (Elliptic Curve Diffie-Hellman, key exchange algorithm) combined with AES (symmetric encryption is used after the key is negotiated).

[0097] The negotiation processing unit may be used to send a list of encryption algorithms supported by this segment to the peer end, receive the encryption algorithm selected by the peer end, and perform verification on it to confirm the final negotiation result, thereby obtaining the target encryption algorithm.

[0098] The interface service unit is used to output the currently selected encryption algorithm (i.e., the target encryption algorithm) to the encryption module 200 and provide the API (Application Programming Interface) of the encryption algorithm selection module 100 so that the subsequent key management module 700 and the communication module 400 can call the encryption algorithm selection module 100 to select the encryption path and determine the method for generating and transmitting the key.

[0099] Therefore, the embodiment of the present application constructs an encryption algorithm selection module 100, so that a consistent encryption algorithm can be selected between the client and the server, effectively ensuring the accuracy and security of encrypting and decrypting sensitive data.

[0100] Optionally, in one embodiment of the present application, the negotiation processing unit is specifically used to: obtain the target encryption algorithm in the encryption algorithm list selected by the client user through the front-end interface of the target client application, and send the target encryption algorithm to the encryption and decryption system of the target client; send the target encryption algorithm to the encryption and decryption system of the target server through the encryption and decryption system of the target client, so as to determine whether the target server supports the target encryption algorithm through the encryption and decryption system of the target server; if the target server does not support the target encryption algorithm, reselect a new target encryption algorithm from the target encryption algorithm list through the target client; if the target server supports the target encryption algorithm, determine the type of the target encryption algorithm; when the type of the target encryption algorithm is symmetric encryption, obtain the shared key corresponding to the symmetric encryption through the key management module 700, and generate confirmation information that supports the target encryption algorithm; when the type of the target encryption algorithm is asymmetric encryption, call the key management module 700 through the encryption and decryption system of the target server to generate a key pair corresponding to the target encryption algorithm, return the public key in the key pair, and generate confirmation information that supports the target encryption algorithm.

[0101] It should be noted that the process of encryption algorithm negotiation in the embodiment of the present application is as follows:

[0102] 1. The client sends a request to import or export BMC configuration to the locally installed EDS (Encryption-Decryption System).

[0103] 2. After receiving the corresponding request, the local EDS system updates the list of encryption algorithms it supports;

[0104] 3. After the update is completed, the corresponding encryption algorithm list is returned to the client for selection;

[0105] 4. The client user can select an encryption algorithm (i.e., the target encryption algorithm) from the encryption algorithm list that complies with the current security policy through the front-end interface of the target client application and send the algorithm to the local EDS;

[0106] 5. After receiving the encryption algorithm request, the local EDS remotely sends the encryption algorithm to the EDS system on the server side;

[0107] 6. The server-side EDS system determines whether it supports the encryption algorithm. If it does, it determines the type of the encryption algorithm. If it is a symmetric encryption algorithm, it directly returns confirmation that the algorithm is supported. If it is an asymmetric encryption algorithm, it returns the public key in the key pair and confirms the algorithm. The client will proceed with subsequent operations after confirmation. If it does not support the encryption algorithm, the client-side embodiment can directly return that the encryption algorithm is not supported, allowing the client to reselect an encryption algorithm.

[0108] 7. The client receives the algorithm confirmation information and directly performs subsequent operations. If the algorithm is not supported, the client directly repeats the above encryption algorithm negotiation process.

[0109] Therefore, the embodiments of the present application can support multiple strategies such as symmetric encryption (such as AES) and asymmetric encryption (such as RSA) by introducing an encryption algorithm negotiation mechanism. Users can freely choose to switch between symmetric encryption, asymmetric encryption and other strategies according to their own needs, making the encryption method more flexible, so as to realize the encryption algorithm and key negotiation mechanism between the client and the server, and ensure that both parties adopt consistent and compatible encryption and decryption strategies.

[0110] During actual implementation, those skilled in the art may also perform encryption algorithm negotiation operations in other ways. As an achievable approach, the embodiment of the present application may also implement an encryption algorithm negotiation method based on a dynamic environment perception strategy. The specific process is as follows:

[0111] 1. Initial capability exchange phase:

[0112] When establishing a connection, the client and server first exchange their respective encryption capability declaration files. This file contains:

[0113] (1) List of supported encryption algorithms (such as AES-256, SM4, etc.);

[0114] (2) Hardware acceleration capabilities (such as whether the AES-NI instruction set is supported);

[0115] (3) Current device status (CPU load, memory remaining, battery level, etc.);

[0116] (4) Compliance requirements (e.g., FIPS 140-3, GDPR, etc.);

[0117] Both parties use digital signatures to ensure document integrity and prevent tampering.

[0118] 2. Environmental assessment and candidate algorithm generation:

[0119] Based on the received capability declaration, the client and server each perform:

[0120] (1) Network quality detection: measuring the current round-trip delay, bandwidth and packet loss rate;

[0121] (2) Security requirements analysis: Determine the required encryption strength based on the data type (e.g., payment data, plain text);

[0122] (3) Performance constraint calculation: Combined with the device status, exclude algorithms that exceed the computing load;

[0123] (4) Then, each party generates the top 3 candidate algorithm combinations and sorts them by priority. For example, AES-256-GCM (high security, medium performance), ChaCha20-Poly1305 (medium security, high performance), and SM4-CBC (compliance priority, low latency).

[0124] 3. Two-way negotiation based on merit:

[0125] The client and server exchange lists of candidate algorithms and determine the final selection through a weighted voting mechanism:

[0126] (1) Security weight (70%): algorithm strength, key length, and authentication method;

[0127] (2) Performance weight (30%): encryption speed, memory usage, and network adaptability;

[0128] Both parties calculate the combined scores of the candidate algorithms and select the one with the highest score and mutual support. In the event of a tie, an alternative negotiation strategy is used (e.g., prioritizing more energy-efficient algorithms).

[0129] 4. Quantum-safe hybrid mode activation:

[0130] After determining the main algorithm, the system detects whether it supports post-quantum cryptography. If both parties support post-quantum cryptography (such as Kyber or Dilithium), a hybrid encryption channel is automatically enabled: 90% of the traffic uses traditional algorithms (such as AES) and 10% of the traffic uses post-quantum cryptography algorithms (test run). The stability of the post-quantum cryptography algorithm is regularly evaluated, and its traffic share is gradually increased.

[0131] 5. Dynamic adjustment and emergency switching:

[0132] During a communication session, continuously monitor:

[0133] (1) Changes in the network environment (e.g., automatically downgrading to ChaCha20 when switching to a mobile network);

[0134] (2) Security threat detection (e.g., switching to SM4 when identifying a man-in-the-middle attack);

[0135] (3) Fluctuations in device status (e.g., disabling high-energy-consuming algorithms when battery is low).

[0136] If the adjustment conditions are triggered, both parties quickly switch to the backup algorithm through a lightweight negotiation protocol to ensure uninterrupted communication.

[0137] 6. Session termination and key destruction:

[0138] At the end of the communication, the temporary session key is immediately destroyed, the algorithm usage log is recorded (for optimizing subsequent negotiations), and a session summary is generated (for auditing purposes).

[0139] Therefore, the embodiment of the present application can dynamically adapt to real-time changes in equipment, network and security requirements by negotiating encryption algorithms based on dynamic environment perception strategies, and ensure the selection of the optimal solution for both parties through weighted voting. Hybrid encryption takes into account both current security and future threats, and the negotiation process is concealed and can support emergency switching.

[0140] The encryption module 200 is used to obtain the original plaintext sensitive data input by the client user during the sensitive data import phase, or to obtain the corresponding exported sensitive data from the baseboard management controller of the target server during the sensitive data export phase, and to encrypt the original plaintext sensitive data or the exported sensitive data using the target encryption algorithm and key to obtain the corresponding sensitive encrypted data.

[0141] Furthermore, the embodiments of the present application can also obtain the original plaintext sensitive data input by the client user through the encryption module 200 during the sensitive data import stage, or obtain the corresponding sensitive data from the baseboard management controller of the server (i.e., export sensitive data) during the sensitive data export stage, and use the target encryption algorithm and key to encrypt the original plaintext sensitive data or all fields marked as "sensitive information" in the exported sensitive data to obtain the corresponding sensitive encrypted data.

[0142] Therefore, the embodiments of the present application can ensure that this information will not be exposed in plain text during transmission or storage; in addition, the encryption module 200 in the embodiments of the present application can also provide a standard encryption interface to the outside world and support multiple encryption algorithms, thereby meeting the encryption needs of users in data import and export scenarios.

[0143] Optionally, in one embodiment of the present application, the encryption module 200 includes: an encryption parameter management unit, an encryption algorithm execution unit, an encryption data packaging unit and a security interface unit.

[0144] Among them, the encryption parameter management unit is used to call the key pair generated by the key management module 700 and manage the algorithm parameters corresponding to the target encryption algorithm.

[0145] The encryption algorithm execution unit is used to obtain the original plaintext sensitive data in the sensitive data import stage, or the exported sensitive data in the sensitive data export stage, and use the target encryption algorithm and key pair to encrypt the original plaintext sensitive data or the sensitive fields in the exported sensitive data to obtain the corresponding sensitive encrypted data.

[0146] The encrypted data packaging unit is used to encapsulate sensitive encrypted data into a unified format structure.

[0147] The security interface unit is used to provide a standard calling interface so that the encryption algorithm selection module 100 and the communication module 400 can call the encryption module 200.

[0148] In the specific implementation process, the encryption module 200 of the embodiment of the present application is mainly composed of an encryption parameter management unit, an encryption algorithm execution unit, an encryption data packaging unit and a security interface unit.

[0149] Specifically, if Figure 3 As shown, the security interface unit can provide a standard calling interface Encrypt(data) and verify whether the input is legal (such as non-empty, format, etc.).

[0150] The encryption parameter management unit can manage the relevant parameters of the encryption algorithm (such as IV (Initialization Vector), random number, etc.), and can call the subsequent key management module 700 to obtain the key pair or public key corresponding to the encryption algorithm.

[0151] The encryption algorithm execution unit can execute algorithms such as AES, RSA, and ECC (Elliptic Curve Cryptography), and receive the current algorithm instruction from the encryption algorithm selection module 100 .

[0152] For example, during the sensitive data import phase, when a client user enters sensitive information (such as a password) in the UI (User Interface), the encryption algorithm execution unit of the embodiment of the present application may first receive the corresponding original plaintext sensitive data; secondly, the embodiment of the present application may call the encryption algorithm selection module 100 to determine the encryption method to be used (such as RSA public key encryption); thereafter, the embodiment of the present application may call the key management module 700, such as Figure 4 As shown, to obtain the public key or symmetric key and IV; finally, the encryption algorithm execution unit can execute the encryption algorithm, that is, encrypt the sensitive field using the selected target encryption algorithm.

[0153] The encrypted data packaging unit can encapsulate the encryption result (i.e., sensitive encrypted data) into a unified format structure, which includes data such as version number, algorithm identifier, ciphertext, and random factor.

[0154] As an achievable method, the encrypted data packaging unit in the embodiment of the present application can encapsulate the encryption result into a unified format structure, which is as follows:

[0155] {

[0156] "alg": "AES-256-CBC",

[0157] "iv": "randomIV==",

[0158] "ciphertext": "base64EncodedCipher==",

[0159] "version": "1.0"

[0160] }

[0161] Afterwards, the embodiment of the present application can call the communication module 400, such as Figure 4 As shown, the encapsulated sensitive encrypted data is passed to the communication module 400, so that the communication module 400 transmits the packaged data to the remote end.

[0162] Therefore, the embodiments of the present application allow sensitive data to be securely exported in encrypted form, thereby ensuring the integrity of the configuration file without leaking sensitive information, and enabling users to locally encrypt plaintext input of sensitive fields when importing configurations, ensuring transmission security.

[0163] The decryption module 300 is used to decrypt the sensitive encrypted data using the key through the encryption and decryption system of the target server during the sensitive data import phase to obtain the sensitive decrypted data.

[0164] Afterwards, the decryption module 300 in the embodiment of the present application can securely decrypt the received sensitive encrypted information, restore the sensitive encrypted information to the original plaintext sensitive field, and output it to the server application (such as BMC) for configuration update.

[0165] In addition, the decryption module 300 in the embodiment of the present application generally exists in pair with the encryption module 200, and supports the parsing and decryption execution of multiple encryption algorithms, and can simultaneously ensure key security, integrity verification and error control.

[0166] It should be noted that if Figure 5 As shown, the decryption module 300 is mainly composed of an encryption format parsing unit, a decryption algorithm execution unit, a decryption parameter management unit and a decryption interface control unit.

[0167] Among them, the encryption format parsing unit can receive encapsulated sensitive encrypted data and parse the corresponding encryption algorithm, IV, ciphertext, etc. according to its ciphertext structure. The encryption format parsing unit supports multiple encapsulation formats such as JSON (JavaScript Object Notation) / XML (Extensible Markup Language) / base64.

[0168] The decryption algorithm execution unit can perform decryption according to a specified corresponding algorithm (such as AES, RSA, etc.) and maintain algorithm compatibility with the encryption module 200.

[0169] The decryption parameter management unit can obtain a private key or a symmetric key to verify whether the initialization vector (IV) and the one-time number (Nonce) in asymmetric encryption meet security requirements.

[0170] The decryption interface control unit provides a unified interface Decrypt(data) to the outside world and verifies whether the input ciphertext structure complies with the protocol.

[0171] As a feasible method, taking the sensitive data import stage as an example, the embodiment of the present application can transmit the encrypted data packet (i.e., sensitive encrypted data) through the client EDS to the server EDS for decryption, thereby updating the BMC configuration.

[0172] Specifically, the decryption module 300 of the embodiment of the present application may first receive the ciphertext structure data corresponding to the sensitive encrypted data through the encryption format parsing unit. The data format is as follows:

[0173] {

[0174] "alg": "AES-256-CBC",

[0175] "iv": "base64IV==",

[0176] "ciphertext": "ciphertext content",

[0177] "version": "1.0"

[0178] };

[0179] Secondly, the embodiment of the present application can use the encryption format parsing unit to read the algorithm identifier (such as AES-256-CBC (Cipher Block Chaining, cipher block chaining)), IV, ciphertext and other fields to parse the above ciphertext structure; again, such as Figure 6 As shown, the embodiment of the present application can pull the key through the decryption algorithm execution unit, that is, call the subsequent key management module 700 to obtain the corresponding key (symmetric key or private key). If the encryption algorithm is symmetric encryption (such as AES), the pre-distributed key is pulled; if the encryption algorithm is asymmetric encryption (such as RSA), the local private key is pulled.

[0180] Then, the embodiment of the present application can utilize the decryption algorithm execution unit to call the corresponding library for decryption operation according to the encryption algorithm selection; for AES-CBC, the IV and key can be used to initialize the Cipher, and then decryption and removal of the padding part can be performed to restore the original data.

[0181] Afterwards, if Figure 6 As shown, the embodiment of the present application can verify the HMAC (Hash-based Message Authentication Code) or check code of the sensitive encrypted data before decryption when the decryption module 300 is linked with the subsequent data integrity verification module 800 to ensure that it has not been tampered with; finally, the embodiment of the present application can send the plaintext data (i.e., sensitive decrypted data) to the server (such as BMC) after successful decryption to continue configuration update.

[0182] Therefore, the embodiments of the present application can realize closed-loop processing by enabling the server application to decrypt the incoming configuration, perform integrity verification, and provide feedback on the import results.

[0183] The communication module 400 is used to export the sensitive encrypted data that has passed the preset data integrity verification operation to the target client application during the sensitive data export phase, or to import the sensitive decrypted data that has passed the preset data integrity verification operation to the baseboard management controller of the target server during the sensitive data import phase.

[0184] Furthermore, the embodiments of the present application can also construct a communication module 400 to manage the communication between the local application (such as the client application) and the local EDS (such as the client EDS), and manage the secure data exchange between the local EDS and the remote EDS (such as the server EDS); at the same time, the communication module 400 cooperates with the subsequent authentication module 600 and the data integrity verification module 800 to ensure the security and reliability of the communication and make it tamper-resistant; in addition, the communication module 400 plays a central role in message scheduling and data transmission in the import and export processes.

[0185] Therefore, the embodiment of the present application provides reliable technical support for the implementation of importing and exporting sensitive data by constructing the communication module 400.

[0186] Optionally, in one embodiment of the present application, the communication module 400 includes: an interface calling unit, an encapsulation and decapsulation unit, a secure communication management unit, and a protocol negotiation unit.

[0187] The interface calling unit is used to provide a corresponding calling interface to the target client application or the baseboard management controller of the target server to receive a corresponding import configuration request or export configuration request.

[0188] The encapsulation and decapsulation unit is used to provide an encapsulation data packet structure to perform encapsulation or decapsulation operations on sensitive encrypted data through the encapsulation data packet structure.

[0189] The secure communication management unit is used to establish a secure channel with the encryption and decryption system of the target client or the encryption and decryption system of the target server.

[0190] The protocol negotiation unit is used to perform corresponding encryption algorithm negotiation operations in conjunction with the encryption algorithm selection module 100 to obtain a corresponding target encryption algorithm.

[0191] It should be noted that the communication module 400 in the embodiment of the present application is mainly composed of an interface calling unit, an encapsulation and decapsulation unit, a secure communication management unit and a protocol negotiation unit. Figure 7 shown.

[0192] Specifically, the interface calling unit may provide a corresponding calling interface to the client application or the server BMC, and receive an import configuration request or an export configuration request.

[0193] The protocol encapsulation and decapsulation unit provides an encapsulation data packet structure to encapsulate the encrypted data and meta-information into a data packet structure supported by the communication module 400, such as {header, algorithm, payload, hash}, etc., and can perform corresponding decapsulation operations.

[0194] The secure communication management unit can establish a secure channel with a remote EDS (such as a server-side EDS), such as a TLS (Transport Layer Security) / SSH (Secure Shell) secure channel, to prevent man-in-the-middle attacks or session replay, and can dynamically adjust the security level of the encryption algorithm.

[0195] The protocol negotiation unit can cooperate with the encryption algorithm selection module 100 to complete the encryption algorithm negotiation operation and manage the handshake and state machine in the encryption algorithm negotiation stage.

[0196] In the specific implementation process, the embodiment of the present application uses the communication module 400 constructed by the above-mentioned units to perform two types of communication processes, namely, sensitive data import and sensitive data export, as described below:

[0197] 1. Sensitive data export communication process:

[0198] (1) Send an export configuration request to the client EDS through the client application;

[0199] (2) The client EDS negotiates the encryption algorithm with the server EDS to obtain the target encryption algorithm;

[0200] (3) The server-side EDS requests the server-side application (i.e., BMC) for sensitive data that needs to be encrypted;

[0201] (4) Encrypt sensitive data using the target encryption algorithm in the server-side EDS and generate an integrity check value;

[0202] (5) The encrypted configuration content (i.e., sensitive encrypted data, etc.) is returned to the server application (BMC) through the server EDS.

[0203] 2. Communication process for importing sensitive data:

[0204] (1) Client users can fill in original plaintext sensitive data in the client application;

[0205] (2) The client EDS negotiates the encryption algorithm with the server EDS to obtain the target encryption algorithm and the key corresponding to the algorithm;

[0206] (3) On the client side, EDS uses the target encryption algorithm to encrypt the original plaintext sensitive data and generate an integrity check value;

[0207] (4) The client EDS sends encrypted data (i.e., sensitive encrypted data) to the server EDS;

[0208] (5) On the server side, the EDS uses the key to decrypt the sensitive encrypted data to obtain the corresponding sensitive decrypted data, and calls the data integrity verification module 800 to verify the integrity of the sensitive decrypted data;

[0209] (6) The server-side EDS updates the configuration of the server-side BMC.

[0210] Therefore, the embodiment of the present application establishes a communication module 400 through an interface calling unit, an encapsulation and decapsulation unit, a secure communication management unit and a protocol negotiation unit to construct a standardized communication protocol, thereby ensuring secure communication between the client EDS and the server EDS, and encrypting and verifying each step in the data interaction process, effectively ensuring the security and reliability of importing and exporting sensitive data.

[0211] Optionally, in one embodiment of the present application, the sensitive data import and export system 10 based on the baseboard management controller of the embodiment of the present application also includes: an authentication module 600, a key management module 700, a data integrity verification module 800 and a plug-in module 900.

[0212] The authentication module 600 is used to perform authentication operations on a client user or entity accessing the system before importing or exporting sensitive data, so that the client user or entity can only perform authorized operations.

[0213] The key management module 700 is used to generate, store and distribute the key corresponding to the target encryption algorithm.

[0214] The data integrity check module 800 is used to generate an integrity check value corresponding to sensitive encrypted data or sensitive decrypted data, and perform a data integrity check on the sensitive encrypted data or sensitive decrypted data based on the integrity check value, so that when the sensitive encrypted data or sensitive decrypted data passes the data integrity check, the corresponding sensitive encrypted data or sensitive decrypted data is output; otherwise, data exception information corresponding to the sensitive encrypted data or sensitive decrypted data is generated and recorded.

[0215] The plug-in module 900 is used to load the encryption algorithm selection module 100, encryption module 200, decryption module 300, authentication module 600, data integrity verification module 800 and key management module 700 in the form of plug-ins, and run in a preset isolation sandbox, and supports hot loading or unloading of algorithm plug-ins during the running process.

[0216] In addition, before importing or exporting sensitive data, the embodiment of the present application can also ensure through the authentication module 600 that the client user or entity accessing the system is trustworthy and can only perform authorized operations; the authentication operation involved in the authentication module 600 is the first step in the security line of the entire encryption system. Before importing or exporting sensitive data, authentication and permission verification must be completed first to prevent security issues such as unauthorized access, spoofing attacks, and unauthorized operations.

[0217] Secondly, the embodiments of the present application can also be responsible for the generation, storage, distribution, rotation, access control, auditing and destruction of keys in the entire system through the key management module 700. Both symmetric and asymmetric keys can be managed in a unified manner, and key support can be provided for the encryption module 200 and the decryption module 300.

[0218] Afterwards, the embodiment of the present application can also construct a data integrity verification module 800 to detect whether sensitive data has been tampered with or damaged during network transmission or storage, and prevent man-in-the-middle attacks, data tampering or unexpected bit errors; at the same time, the data integrity verification module 800 can also cooperate with the authentication module 600 and the key management module 700 to ensure that the data comes from a trusted party and has not been changed.

[0219] Furthermore, those skilled in the art should understand that the encryption / integrity algorithms of existing import and export solutions are basically hard-coded, making it difficult to support subsequent customized algorithms and lacking scalability. Therefore, the embodiments of the present application can construct a plug-in model to establish a modular, plug-in algorithm management framework, thereby supporting encryption, decryption, integrity, and authentication algorithms to be loaded as plug-ins, as well as hot loading or unloading algorithm plug-ins at runtime, and can provide standardized plug-in interface specifications to facilitate third-party development of extension plug-ins; at the same time, plug-ins can run in an isolated sandbox to prevent affecting the stability of the main system.

[0220] Therefore, the embodiments of the present application improve the security level of the overall system by providing a key management module 700, an authentication module 600 and a data integrity verification module 800, and can further enhance the security and adaptability of the system through a plug-in module 900.

[0221] Optionally, in one embodiment of the present application, the key management module 700 includes: a key generator, a key storage, a key negotiator, a key rotator, an access controller, an audit recorder, and a key destroyer.

[0222] Among them, the key generator is used to determine the symmetric key or asymmetric key corresponding to the target encryption algorithm according to the type of the target encryption algorithm, and automatically generate a key pair corresponding to the symmetric key or asymmetric key.

[0223] The key storage is used to store key pairs based on a preset key security access policy.

[0224] The key negotiator is used to perform key negotiation operations between the target client and the target server to generate the corresponding shared key.

[0225] The key rotator is used to switch key pairs based on a preset rotation period.

[0226] Access controller, used to manage key pair usage permissions.

[0227] Audit recorder, used to record the operation data corresponding to all operation behaviors corresponding to the key pair.

[0228] The key destroyer is used to destroy the key pair, generate the corresponding destruction record, and save the destruction record in the audit recorder.

[0229] It should be noted that if Figure 8 As shown, the key management module 700 in the embodiment of the present application mainly includes multiple components such as a key generator, a key storage, a key negotiator, a key rotator, an access controller, an audit recorder and a key destroyer.

[0230] Specifically, the main functions of each component are as follows:

[0231] 1. The key generator mainly has the following functions:

[0232] (1) Symmetric key support:

[0233] 1) Support AES-128 / 192 / 256;

[0234] 2) Use CSPRNG (Cryptographically Secure Pseudo-Random Number Generator) to generate keys.

[0235] (2) Asymmetric key support:

[0236] 1) Support RSA (2048 / 3072 / 4096 bits) and ECC (P-256, P-384).

[0237] (3) Automatically generate public and private key pairs;

[0238] (4) Configuration interface:

[0239] 1) Client users can specify the algorithm type, key length, and whether to export the public key.

[0240] 2. The key storage can realize local secure storage (file encryption storage can be used) and key encryption storage (business keys can be wrapped with master keys), and can support labeled key access, such as obtaining keys based on key_id.

[0241] 3. The key negotiation device is mainly used to negotiate a shared key (mainly a symmetric key) between the client and the server, as described below:

[0242] (1) Algorithm support:

[0243] 1) Diffie-Hellman (key exchange protocol / algorithm, DH) / Elliptic Curve DH (ECDH, elliptic curve Diffie-Hellman key exchange);

[0244] 2) TLS (Transport Layer Security) 1.3 Pre-Shared Key (PSK) mode.

[0245] (2) Negotiation steps:

[0246] 1) The client and server negotiate the key algorithm;

[0247] 2) Both parties generate key material (i.e., public key exchange);

[0248] 3) Generate a shared key for subsequent encrypted communication.

[0249] 4. The key rotator supports key lifecycle management and can perform the following functions:

[0250] (1) Automatic rotation:

[0251] 1) Time-based: such as rotating every 30 days;

[0252] 2) Based on the number of times used: for example, rotation after every N encryption times.

[0253] (2) Manual rotation:

[0254] 1) Triggered through the management API or interface.

[0255] 5. The access controller is mainly used to manage the use rights of keys, and can perform operations such as role division and permission authentication mechanism, as described below:

[0256] (1) Role division:

[0257] 1) Administrator (generate, delete, export);

[0258] 2) Application (for encryption and decryption).

[0259] (2) Authority authentication mechanism:

[0260] like Figure 9 As shown, the embodiment of the present application can call the token / session / certificate authentication provided by the authentication module 600 to confirm the legitimacy of the operator, and can distribute the corresponding key to the encryption module 200, decryption module 300 and communication module 400. The specific strategy is as follows:

[0261] rules:

[0262] - user: "admin"

[0263] allow: ["generate", "rotate"]

[0264] - user: "app"

[0265] allow: ["encrypt", "decrypt"]

[0266] 6. The audit logger can record all key-related operations to facilitate security audits. The specific record contents are as follows:

[0267] (1) Operation type (e.g., generate, export, rotate);

[0268] (2) Identity of the initiator;

[0269] (3) Operation time, IP (Internet Protocol), key ID (Identifier);

[0270] (4) Secure storage;

[0271] (5) Write to the database and encrypt the signature to prevent tampering (such as HMAC or signature chain).

[0272] The recorded log is as follows:

[0273] {

[0274] "event": "KEY_GENERATE",

[0275] "key_id": "user_cfg_key",

[0276] "operator": "admin1",

[0277] "timestamp": "2025-05-07T12:01:23Z",

[0278] "result": "success"

[0279] }

[0280] 7. The key destroyer can support manual destruction or automatic destruction upon expiration:

[0281] (1) Encrypted storage destruction: file-level secure erasure (overwriting multiple times);

[0282] (2) Memory clearing: Call the encryption library interface to clean up the heap memory.

[0283] In an embodiment of the present application, the destruction record may be retained in the audit log.

[0284] Therefore, the embodiments of the present application can cover the entire life cycle through the constructed key management module 700 to achieve full process control such as key generation, distribution, storage, rotation, and destruction, and support key access permission management.

[0285] Optionally, in one embodiment of the present application, the data integrity verification module 800 includes: a hash generation unit, a digest comparison unit, an abnormality alarm unit and a log recording unit.

[0286] Among them, the hash generation unit is used to calculate the sending end hash value and the receiving end hash value corresponding to the sensitive encrypted data at the sending end and the receiving end respectively based on the preset hash algorithm, and determine whether the sending end hash value and the receiving end hash value meet the preset data matching requirements. When the sending end hash value and the receiving end hash value meet the preset data matching requirements, it is determined that the sensitive encrypted data has passed the data integrity verification.

[0287] The digest comparison unit is used to generate a digest corresponding to the sensitive decrypted data, sign the digest using the private key of the sender, and send the signed digest and the sensitive decrypted data to the receiver to determine whether the digest meets the preset signature legitimacy requirements using the public key of the receiver. If the digest meets the signature legitimacy requirements, the sensitive decrypted data is determined to have passed the data integrity verification.

[0288] The abnormality alarm unit is used to perform corresponding data abnormality alarm operations and record corresponding data abnormality information when the hash value of the sending end and the hash value of the receiving end do not meet the preset data matching requirements, or the summary does not meet the signature legitimacy requirements.

[0289] The logging unit is used to record data integrity verification information of sensitive encrypted data.

[0290] In the specific implementation process, the data integrity verification module 800 in the embodiment of the present application is mainly composed of the following main components: a hash generator, a digest verifier, a signature verifier, a timestamp binder, and an integration interface, which are described in detail as follows:

[0291] 1. Hash generator:

[0292] 1) Responsible for calculating hash values ​​for original or encrypted data;

[0293] 2) Supported hash algorithms include SHA (Secure Hash Algorithm)-256, SHA-3 series, BLAKE2, or SM3;

[0294] 3) Data processing granularity: can be processed as a whole segment or by block (to prevent memory issues with large files).

[0295] 2. Digest Verifier:

[0296] (1) Verify data integrity at the receiving end:

[0297] (2) The receiving end recalculates the hash of the received data;

[0298] (3) Compare with the original hash attached by the sender. If they match, it means that the data has not been tampered with. Otherwise, it prompts an integrity error.

[0299] 3. The signature verifier can add a digital signature to the data hash in sensitive operation scenarios to prevent data from being forged, as described below:

[0300] (1) Signature process (sending end, such as local client):

[0301] Generate a summary of the data, sign it with the private key, and send the signature along with the data to the receiving end;

[0302] (2) Verification process (receiving end, such as the server):

[0303] Use the sender's public key to verify the legitimacy of the signature. If the signature verification fails, the data will be refused to be processed.

[0304] 4. Timestamp binder:

[0305] The timestamp binder can be used to bind the generation time of data to avoid replay attacks. A timestamp field is included with each import / export, and the timestamp is also included in the hash signature. The receiving end verifies whether the timestamp is within the allowed range, and rejects it if it exceeds the range.

[0306] 5. Integration interface:

[0307] The integrated interface can provide a unified interface for the encryption module 200, the decryption module 300, and the communication module 400. The embodiment of the present application can perform corresponding import or export processes based on the integrated interface, as described below:

[0308] (1) Export process:

[0309] 1) Before exporting, the client encrypts the sensitive data and generates the corresponding hash value (i.e., the sending end hash value) and the receiving end hash value;

[0310] (2) Digitally sign the hash value;

[0311] (3) Send the sensitive encrypted data, hash and corresponding digital signature to the server.

[0312] (2) Import process:

[0313] 1) The server receives the data (i.e., sensitive encrypted data, hash, and corresponding digital signature);

[0314] 2) Use the public key to verify the digital signature and verify the hash value;

[0315] 3) If the hash value at the sender and the hash value at the receiver are consistent and the digital signature verification is successful, it can be determined that the sensitive encrypted data has not been tampered with;

[0316] 4) Send the sensitive encrypted data to the decryption module 300 for decryption processing.

[0317] In combination with the functional logic of the above-mentioned main components, the embodiment of the present application can determine multiple logical units in the specific implementation process, such as a logical hash generation unit, a digest comparison unit, an abnormality alarm unit and a log recording unit, such as Figure 10 As shown, the details are as follows:

[0318] 1. Hash generation unit: Calculates the digest based on algorithms such as SHA-256

[0319] In the embodiment of the present application, a hash generation unit may first calculate a sending-end hash value and a receiving-end hash value corresponding to the sensitive encrypted data at the sending end and the receiving end of the sensitive encrypted data based on a hash algorithm, and determine whether the corresponding hash values ​​meet the data matching requirements (such as whether the sending-end hash value and the receiving-end hash value are consistent). Thus, when the sending-end hash value and the receiving-end hash value meet the data matching requirements, it is determined that the sensitive encrypted data has passed the data integrity verification.

[0320] 2. Summary comparison unit: Verify whether the received data has been tampered with

[0321] Secondly, the embodiments of the present application can generate a summary corresponding to the sensitive decrypted data, sign it with the private key of the sender, and send the signed summary and sensitive decrypted data to the receiving end, so as to determine whether the summary meets the signature legitimacy requirements through the public key of the receiving end, and thus determine that the sensitive decrypted data passes the data integrity verification when the summary meets the signature legitimacy requirements.

[0322] 3. Abnormal alarm unit: data abnormality alarm and recording

[0323] In addition, the embodiment of the present application can issue a data anomaly alarm to record data anomaly information when the hash value of the sending end and the hash value of the receiving end do not meet the data matching requirements, or the summary does not meet the signature legitimacy requirements.

[0324] 4. Logging unit: integrity verification log tracking

[0325] Finally, embodiments of the present application may record data integrity verification information for sensitive encrypted data.

[0326] In summary, if Figure 11 As shown, the embodiment of the present application calls the encryption module 200 through the data integrity verification module 800 to obtain the corresponding sensitive encrypted data, and generates the digest corresponding to the sensitive encrypted data through the above-mentioned logical hash generation unit, digest comparison unit, abnormal alarm unit and log recording unit, and verifies whether the digests of the sending end and the receiving end are consistent. If they are inconsistent, data abnormality alarm and log recording are performed, and the sensitive decrypted data that has passed the data integrity verification is input into the decryption module 300.

[0327] Therefore, the embodiment of the present application embeds a hash verification mechanism in the data integrity verification module 800 to perform hash value comparison and verification on the imported data, thereby ensuring that the content has not been tampered with, so as to protect the credibility of the entire encryption and decryption system during the import, export, transmission and storage of sensitive data.

[0328] Optionally, in one embodiment of the present application, the plug-in module 900 includes: a plug-in management unit and a hot loading unit.

[0329] Among them, the plug-in management unit is used to provide a plug-in loading interface and a plug-in unloading interface, and register to the encryption algorithm selection module 100 through the plug-in loading interface, so that the encryption algorithm selection module 100 calls the plug-in loading interface to perform encryption and decryption operations.

[0330] Hot loading unit, used to dynamically update policies for configuration files or interfaces.

[0331] In actual implementation, the embodiment of the present application defines the algorithm plug-in interface specification in the plug-in module 900. Each algorithm plug-in must implement a unified interface (e.g., pseudo-C code), as shown below:

[0332] struct AlgoPlugin {

[0333] char name

[64] ; / / plugin name

[0334] char version

[16] ; / / plugin version

[0335] int (*init)(void); / / Initialization

[0336] int (*encrypt)(const uint8_t* in, uint32_t in_len, uint8_t* out, uint32_t* out_len);

[0337] int (*decrypt)(const uint8_t* in, uint32_t in_len, uint8_t* out, uint32_t* out_len);

[0338] int (*integrity)(const uint8_t* in, uint32_t in_len, uint8_t*digest);

[0339] int (*cleanup)(void); / / Clean up resources

[0340] };

[0341] Plugins are compiled into shared libraries (Linux: .so / Windows: .dll) and loaded dynamically.

[0342] Secondly, the plug-in module 900 in the embodiment of the present application mainly includes a plug-in management unit and a hot loading unit, which are described in detail as follows:

[0343] 1. Plug-in management unit:

[0344] (1) Provide plug-in loading and unloading interface;

[0345] (2) Verify the plugin signature and integrity (to prevent loading of malicious plugins);

[0346] (3) Failure to load the plug-in does not affect the operation of the main system;

[0347] (4) The plug-in runs in a sandbox isolation environment (to prevent memory and exceptions from polluting the main process).

[0348] 2. Thermal loading unit:

[0349] (2) Support loading new plug-ins without restarting the system.

[0350] (3) Configuration files or APIs can dynamically update policies (enable / disable specific algorithm plug-ins).

[0351] As an achievable method, the embodiment of the present application performs the following operations through the plug-in module 900:

[0352] 1. The administrator deploys the SM4 encryption plug-in to the plug-in directory.

[0353] 2. The system loads the plug-in through the API and registers it to the encryption algorithm selection module 100.

[0354] 3. Users select SM4 encryption algorithm when importing or exporting.

[0355] 4. The encryption algorithm selection module 100 calls the plug-in interface to perform encryption or decryption operations.

[0356] Therefore, the embodiments of the present application can enable users to flexibly expand custom algorithms and meet corresponding compliance requirements through the plug-in module 900; in addition, the plug-in module 900 supports smooth algorithm upgrades, reduces the risk of restart due to version changes, and enhances system security and adaptability.

[0357] Optionally, in one embodiment of the present application, the authentication module 600 includes: an identity authentication unit, a permission identification unit, a session management unit and a security audit unit.

[0358] The identity authentication unit is used to obtain the identity information, token or certificate corresponding to the client user or entity, and to authenticate the client user or entity through the identity information, token or certificate to obtain the corresponding identity authentication result.

[0359] The permission identification unit is used to map the corresponding role according to the identity authentication result and query the preset permission rules to determine whether the role is allowed to perform the import or export operation. If the role is allowed to perform the import or export operation, the corresponding sensitive data export or sensitive data export operation is performed; otherwise, the corresponding authentication failure information is returned.

[0360] The session management unit is used to generate a corresponding session token when the role is allowed to perform an import or export operation, so as to perform a corresponding session management operation based on the session token.

[0361] The security audit unit is used to record the authentication failure information in a preset security audit log and send the security audit log to a target mailbox.

[0362] It should be noted that if Figure 12 As shown, the embodiment of the present application can construct a corresponding authentication module 600 through an identity authentication unit, a permission identification unit, a session management unit and a security audit unit.

[0363] Among them, the identity authentication unit supports passwords, tokens, two-factor authentication, biometrics, etc., and provides login, session initialization and identity verification.

[0364] The authority authentication unit can analyze user identities, assign authority roles, and verify user permissions.

[0365] The session management unit manages user session status, token expiration, and logout.

[0366] The security audit unit can record authentication, authentication failure and access logs.

[0367] The following takes the import of sensitive data as an example and describes the execution process of each unit in the authentication module 600 in conjunction with the accompanying drawings.

[0368] Figure 13 FIG. 6 is a schematic diagram showing the collaboration between the authentication module 600 and other modules. Figure 13 As shown, the specific process of authentication and authorization in this embodiment of the application is as follows:

[0369] 1. The client application initiates a session request and calls the communication module 400 to send the user identity information, token or certificate along with the session request (i.e., authentication request) to the server EDS;

[0370] 2. In the server-side EDS, identity authentication is performed based on the authentication module 600 through methods such as password and username, token or TLS certificate (two-way authentication);

[0371] 3. Map roles (such as administrator or read-only user) based on the authentication results, and query whether the permission rules allow the configuration import operation. If not, return authentication failure. Otherwise, proceed to the next step to perform the corresponding permission identification or permission verification operation;

[0372] 4. After successful authentication (i.e., successful permission verification), a session token is generated for subsequent interactive verification, and the session information is encrypted and saved in the local cache;

[0373] 5. The embodiments of the present application also need to record all authentication attempts, failures, and permission errors in the log, and the logs must be synchronized regularly or sent to the target mailbox via SMTP (Simple Mail Transfer Protocol) function to achieve security auditing.

[0374] Afterwards, the embodiment of the present application can send the authenticated sensitive data to the corresponding client EDS or server EDS.

[0375] Therefore, the embodiment of the present application integrates a two-factor authentication mechanism through the authentication module 600, and supports multi-factor verification based on tokens, certificates, passwords, time windows, etc.; in addition, the embodiment of the present application can also collaboratively design the client EDS and the server EDS to configure and allow EDS to lead encryption and decryption, key negotiation, algorithm synchronization and other functions to enhance data processing consistency.

[0376] It can be understood that the embodiments of the present application can well support the multi-level feedback mechanism of import status, and the import process includes detailed feedback status such as algorithm confirmation failure, decryption failure, and service import failure, which is convenient for users to locate problems; in addition, the embodiments of the present application are designed with an error knowledge base and a log system to facilitate problem location and subsequent tracing, thereby improving system operation and maintenance and auditing capabilities.

[0377] The zero trust adaptation module 500 is used to perform dynamic identity authentication, real-time policy engine decision-making, session persistence verification and context verification operations based on preset zero trust policies during the sensitive data export stage and the sensitive data import stage to dynamically adjust the import and export operation permissions.

[0378] Those skilled in the art should understand that the zero-trust security architecture requires re-verification and authorization for each operation to prevent internal threats, session hijacking or lateral movement attacks; while existing import and export technologies usually default to trust within the session after a single authentication.

[0379] Therefore, the embodiment of this application introduces a zero-trust policy for import and export operations to achieve dynamic authentication, dynamic authorization with minimum privileges, real-time risk assessment and policy engine decision-making, continuous session verification, and context verification. The specific implementation process is as follows:

[0380] 1. Dynamic identity authentication mechanism: In this embodiment, each import and export operation requires re-authentication. The specific process is as follows:

[0381] (1) The import and export request triggers the zero trust identity module (i.e., the zero trust adaptation module 500);

[0382] (2) The zero-trust identity module combines environmental context (such as IP, geographic location, and device fingerprint) to conduct risk assessment;

[0383] (3) If the risk is high, require stronger authentication (e.g., tokens, biometric authentication, and SMS OTP (One-Time Password));

[0384] (4) The verification result generates a session token in real time, which is only used for the current import and export session.

[0385] In addition, in the actual implementation process, the embodiments of the present application can also implement the above-mentioned dynamic authentication mechanism based on the zero-trust dynamic authentication method, as described below:

[0386] 1. Sensitive operation triggering stage:

[0387] When a user or system initiates a sensitive data import / export request:

[0388] (1) The operation is intercepted and marked as a high-sensitivity action;

[0389] (2) The system automatically freezes the current data flow and enters the verification preparation state;

[0390] (3) Generate a unique operation ID and record the operation context (such as data type, target system, and timestamp).

[0391] 2. Multi-dimensional identity re-verification:

[0392] Perform three-tier progressive authentication:

[0393] (1) Device fingerprint verification

[0394] 1) Detect the current device hardware characteristics (such as the TPM (Trusted Platform Module) chip ID);

[0395] 2) Verify whether the network access location complies with the preset security policy;

[0396] 3) Compare device behavior baselines (such as mouse movement patterns).

[0397] (2) Dynamic biometric authentication

[0398] 1) Triggering real-time liveness detection (such as blinking in front of the screen);

[0399] 2) Collect behavioral biometrics (such as keyboard tapping rhythm);

[0400] 3) Use voiceprint recognition to verify the operator's identity.

[0401] (3) Contextual authority confirmation

[0402] 1) Check whether the current session meets the principle of least privilege;

[0403] 2) Verify that the operation time is within the preset safety window;

[0404] 3) Confirm whether the data flow complies with workflow rules.

[0405] 3. Micro-segmentation strategy execution:

[0406] Dynamically build a temporary data channel based on the verification results:

[0407] (1) Isolate transmission paths through SDN (Software-Defined Networking) technology;

[0408] (2) Automatically apply encryption strategies (e.g., encrypt sensitive fields separately);

[0409] (3) Limit the scope of accessible API endpoints.

[0410] 4. Operation process monitoring:

[0411] Implementing real-time behavioral analytics:

[0412] (1) Monitoring abnormal data flow patterns (such as sudden large traffic transmission);

[0413] (2) Tracking the integrity of the operation chain (preventing man-in-the-middle attacks);

[0414] (3) Record the complete audit trail (traceable to specific commands).

[0415] 5. Session automatic fuse:

[0416] To set up a double termination mechanism:

[0417] (1) Destroy the temporary access credentials immediately after the operation is completed;

[0418] (2) Force refresh of session key;

[0419] (3) Clear sensitive data cache in memory.

[0420] 6. Intelligent feedback optimization:

[0421] The system automatically analyzes this verification process:

[0422] (1) Calculate risk score and update user trust value;

[0423] (2) Optimize the challenge difficulty of the next verification;

[0424] (3) Flag unusual patterns for review by the security team.

[0425] Therefore, the embodiments of the present application break the traditional session persistence mechanism through continuous identity confirmation, behavior chain integrity, dynamic micro-isolation and adaptive verification, re-authenticate each sensitive operation, and create temporary data channels on demand to achieve nano-level isolation.

[0426] 2. The least privilege policy takes effect dynamically:

[0427] (1) Generate a minimum set of permissions in real time for each import and export request (such as the type of configuration item to be imported and the scope of data to be exported);

[0428] (2) The permission policy is generated in real time by the policy engine based on the sensitivity of the configuration item, user role, and operation context;

[0429] (3) When importing or exporting, if any super-privileged operation request is found, it will be rejected immediately and an alarm will be issued.

[0430] 3. Real-time strategy engine decision-making:

[0431] (1) System integration policy engine, where decision factors include current user identity and role, session context (device, location, time), historical behavior baseline (refer to anomaly detection module), and current request sensitivity;

[0432] (2) The engine outputs decisions based on factors, such as allow, strengthen verification, block, and require manual approval.

[0433] 4. Continuous session verification and context verification:

[0434] (1) Continuously verify the session context during import and export;

[0435] (2) If there is a major change in the session environment (such as IP mutation or device mutation), the session will be interrupted or secondary authentication will be triggered.

[0436] Therefore, the embodiments of the present application can re-verify identity and permissions during each import and export operation through the zero-trust adaptation module 500 to prevent internal threats and session hijacking; in addition, the embodiments of the present application can also automatically and dynamically adjust operation permissions to reduce the risk of data leakage, and can support real-time policy updates, thereby improving the system's ability to respond to dynamic threats.

[0437] In summary, the embodiment of the present application can be composed of an encryption algorithm selection module 100, a communication module 400, an encryption module 200, a decryption module 300, an authentication module 600, a key management module 700 and a data integrity verification module 800 to form an encryption and decryption system EDS independent of the BMC system and deployed on the client and server. The overall architecture of the encryption and decryption system is as follows: Figure 14 As shown, the encryption and decryption system is the interaction layer; the encryption algorithm selection module 100, the communication module 400, the encryption module 200, the decryption module 300, the authentication module 600 and the key management module 700 constitute the core processing layer; the data integrity verification module 800 is the data verification layer, thereby constructing a multi-module layered security architecture, so that the encryption module 200, the decryption module 300, the key management module 700, the authentication module 600, the data integrity module, etc. work together to form a system-level security protection system, realize local encryption and remote decryption of data, and reserve interfaces for future algorithm replacement and encryption strategy expansion, with good scalability and compatibility.

[0438] An embodiment of the present application also provides a method for importing and exporting sensitive data based on a baseboard management controller.

[0439] like Figure 15 FIG. 1 is a flow chart of a sensitive data import and export method based on a baseboard management controller applied in the sensitive data import phase according to an embodiment of the present application, wherein the sensitive data import and export method based on a baseboard management controller includes the following steps:

[0440] In step S1501, a configuration import request is sent to the encryption and decryption system of the target client through the target client application, so that the encryption and decryption system of the target client obtains the encryption algorithm list supported by the target server according to the configuration import request.

[0441] In step S1502, based on the encryption algorithm list, an encryption algorithm negotiation operation is performed between the encryption and decryption system of the target server and the encryption and decryption system of the target client to determine the corresponding target encryption algorithm and the key corresponding to the target encryption algorithm on the target server.

[0442] During the sensitive data import phase, that is, when the BMC imports configuration files containing sensitive information, the operation sequence is as follows: Figure 16 shown.

[0443] During the actual execution process, the embodiment of the present application can first send a configuration import request to the client EDS through the client application, so that the EDS of the target client updates the list of supported encryption algorithms according to the configuration import request to obtain the list of encryption algorithms supported by the server, and return the list of encryption algorithms supported by the server to the client application, so as to perform encryption algorithm negotiation operations between the EDS of the target server and the EDS of the client, thereby determining the corresponding target encryption algorithm and the key corresponding to the target encryption algorithm on the server.

[0444] Therefore, the encryption algorithm selection strategy of the embodiment of the present application has a certain degree of intelligence and can optimize the algorithm based on strategy, priority, security level, and performance indicators.

[0445] Optionally, in one embodiment of the present application, based on the encryption algorithm list, an encryption algorithm negotiation operation is performed between the encryption and decryption system of the target server and the encryption and decryption system of the target client to determine the corresponding target encryption algorithm and the key corresponding to the target encryption algorithm on the target server, including: obtaining the target encryption algorithm in the encryption algorithm list selected by the client user through the front-end interface of the target client application, and sending the target encryption algorithm to the encryption and decryption system of the target client; sending the target encryption algorithm to the encryption and decryption system of the target server through the encryption and decryption system of the target client, so as to determine whether the target server supports the target encryption algorithm through the encryption and decryption system of the target server; if the target server does not support the target encryption algorithm, reselecting a new target encryption algorithm from the encryption algorithm list through the target client; if the target server supports the target encryption algorithm, determining the type of the target encryption algorithm; when the type of the target encryption algorithm is symmetric encryption, obtaining the shared key corresponding to the symmetric encryption, and generating confirmation information that supports the target encryption algorithm; when the type of the target encryption algorithm is asymmetric encryption, generating a key pair corresponding to the target encryption algorithm through the encryption and decryption system of the target server, returning the public key in the key pair, and generating confirmation information that supports the target encryption algorithm.

[0446] It should be noted that if Figure 16 As shown, the user can select the corresponding target encryption algorithm in the encryption algorithm list through the front-end interface of the client application, and send the target encryption algorithm and the corresponding configuration import file to the client EDS, so as to request the server EDS to use the required encryption algorithm (i.e., the target encryption algorithm) through the client EDS, and determine whether the target encryption algorithm is included in the encryption algorithm list supported by the server EDS. If the target encryption algorithm is included in the encryption algorithm list, the type of the target encryption algorithm is determined.

[0447] When the target encryption algorithm is symmetric encryption, the shared key (i.e., public key) is used directly; when the target encryption algorithm is asymmetric encryption, an asymmetric key pair is generated by the server and the public key (i.e., the corresponding shared public key in symmetric encryption) is returned.

[0448] It can be understood that the embodiments of the present application can support dynamically negotiated encryption algorithms and automatic switching mechanisms between symmetric and asymmetric encryption, so that the client and the server can determine the commonly supported encryption algorithms through negotiation, thereby improving the system compatibility and flexibility, and can dynamically select the encryption method according to the data sensitivity or server capabilities, thereby improving the compatibility balance between security and performance; in addition, the embodiments of the present application also support front-end friendly interactive design, such as real-time algorithm visual selection, error feedback display, status visual tracking, etc., to enhance the system operability.

[0449] In step S1503, the plaintext sensitive data input by the client user is obtained, and the plaintext sensitive data is encrypted using the target encryption algorithm through the encryption and decryption system of the target client to obtain the corresponding sensitive encrypted data, and the sensitive encrypted data is verified for data integrity to obtain sensitive encrypted data that passes the data integrity verification.

[0450] Furthermore, the embodiments of the present application also need to obtain encryption algorithm confirmation on the client EDS so that the imported file and sensitive data can be sent to the client EDS through the client application; the client EDS can use the target encryption algorithm to encrypt the sensitive data in the imported configuration file to obtain the corresponding sensitive encrypted data; thereafter, the embodiments of the present application can perform data integrity verification on the sensitive encrypted data, thereby obtaining sensitive encrypted data that passes the data integrity verification.

[0451] Optionally, in one embodiment of the present application, data integrity verification is performed on sensitive encrypted data to obtain sensitive encrypted data that has passed the data integrity verification, including: based on a preset hash algorithm, calculating the sending end hash value and the receiving end hash value corresponding to the sensitive encrypted data at the sending end and the receiving end of the sensitive encrypted data, respectively; judging whether the sending end hash value and the receiving end hash value meet the preset data matching requirements; if the sending end hash value and the receiving end hash value meet the preset data matching requirements, then determining that the sensitive encrypted data has passed the data integrity verification; if the sending end hash value and the receiving end hash value do not meet the preset data matching requirements, then executing a corresponding data anomaly alarm operation, and recording the corresponding data anomaly information.

[0452] As a feasible method, when performing data integrity verification on sensitive encrypted data, the embodiments of the present application can first use a hash algorithm to calculate the sending end hash value and the receiving end hash value corresponding to the sensitive encrypted data at the sending end and the receiving end (i.e., the client and the server) of the sensitive encrypted data respectively.

[0453] Secondly, the embodiment of the present application can determine whether the hash value of the sending end and the hash value of the receiving end meet the data matching requirements, such as whether the hash value of the sending end and the hash value of the receiving end are consistent. If the hash value of the sending end and the hash value of the receiving end meet the data matching requirements, it is determined that the sensitive encrypted data passes the data integrity verification; otherwise, the corresponding data anomaly alarm operation is executed, and the corresponding data anomaly information is recorded.

[0454] Therefore, the embodiments of the present application introduce a hash verification mechanism to perform hash value comparison and verification on the imported data, thereby achieving data integrity verification of sensitive encrypted data, effectively ensuring the reliability and integrity of the encrypted content.

[0455] In step S1504, the sensitive encrypted data is decrypted using the key in the encryption and decryption system of the target server to obtain the corresponding sensitive decrypted data, and the sensitive decrypted data is verified for data integrity, and the sensitive decrypted data that passes the data integrity verification is imported into the baseboard management controller of the target server.

[0456] Afterwards, the embodiment of the present application can use the key to decrypt the sensitive encrypted data. If the decryption fails, the import failure state is immediately returned; if the decryption is successful, a decrypted configuration file is generated, that is, the sensitive decrypted data.

[0457] Furthermore, the embodiments of the present application can perform data integrity verification on the sensitive decrypted data, thereby importing the sensitive decrypted data that has passed the data integrity verification into the baseboard management controller of the server.

[0458] Therefore, the embodiments of the present application ensure that sensitive data in the configuration import and export process is always in an encrypted state, and encryption protection is performed on it throughout its life cycle, thereby effectively preventing leakage in the intermediate links.

[0459] Optionally, in one embodiment of the present application, data integrity verification is performed on sensitive decrypted data, including: generating a summary corresponding to the sensitive decrypted data, signing the summary with the private key of the sending end, and sending the signed summary and sensitive decrypted data to the receiving end; judging whether the summary meets the preset signature legitimacy requirements through the public key of the receiving end; if the summary meets the signature legitimacy requirements, then determining that the sensitive decrypted data passes the data integrity verification; if the summary does not meet the signature legitimacy requirements, executing the corresponding data anomaly alarm operation, and recording the corresponding data anomaly information.

[0460] It should be noted that the process of verifying the integrity of sensitive decrypted data in this embodiment of the application is as follows:

[0461] 1. Generate a digest corresponding to the sensitive decrypted data and sign the digest with the sender's private key;

[0462] 2. Send the signed summary and sensitive decrypted data to the receiving end;

[0463] 3. Use the public key of the receiving end to determine whether the summary meets the signature legitimacy requirements;

[0464] 4. If the summary meets the signature legitimacy requirements, the sensitive decrypted data is determined to have passed the data integrity verification. Otherwise, the corresponding data anomaly alarm operation is executed and the corresponding data anomaly information is recorded.

[0465] Therefore, the embodiments of the present application verify the data integrity of sensitive decrypted data to check whether the received data has been tampered with, thereby ensuring the data integrity and security of sensitive data during the import process.

[0466] Optionally, in one embodiment of the present application, a key is used to decrypt sensitive encrypted data in the encryption and decryption system of the target server to obtain corresponding sensitive decrypted data, and data integrity verification is performed on the sensitive decrypted data, and the sensitive decrypted data that passes the data integrity verification is imported into the baseboard management controller of the target server, including: parsing the ciphertext structure corresponding to the sensitive encrypted data through the encryption and decryption system of the target server to obtain parsed data corresponding to the sensitive encrypted data; obtaining a shared key or private key corresponding to the sensitive encrypted data, and decrypting the parsed data through the shared key or private key, and judging whether the sensitive encrypted data is decrypted successfully; if the sensitive encrypted data is decrypted successfully, the corresponding sensitive decrypted data is generated, otherwise import failure status information is returned; constructing a configuration file corresponding to the sensitive decrypted data through the target client application, and sending the configuration file to the target server application, so that the target server application executes the import operation of the sensitive encrypted data according to the configuration file, and judges whether the sensitive encrypted data is imported successfully; if the sensitive encrypted data is imported successfully, import success status information is returned, otherwise import failure status information is returned.

[0467] During the actual execution process, the embodiments of the present application can first parse the ciphertext structure corresponding to the sensitive encrypted data through the server-side EDS to obtain the corresponding parsed data; secondly, the embodiments of the present application can decrypt the parsed data through a shared key or a private key, and determine whether the sensitive encrypted data is decrypted successfully. If the decryption is successful, the corresponding sensitive decrypted data is generated, otherwise the import failure status information is returned.

[0468] Again, the embodiment of the present application can send the assembled configuration file to the server application through the client application to perform the import operation on the server application and determine whether the import is successful; if the import is successful, the import success status is returned, otherwise the import failure status is returned, so that after the client receives the execution status of the import operation, the entire import operation process is completed.

[0469] Therefore, the embodiments of the present application can ensure the efficiency and reliability of data decryption by parsing and decrypting the corresponding encryption algorithm.

[0470] like Figure 17 FIG. 1 is a flowchart of a sensitive data import and export method based on a baseboard management controller applied in the sensitive data export stage according to an embodiment of the present application, wherein the sensitive data import and export method based on a baseboard management controller includes the following steps:

[0471] In step S1701, a configuration export request is sent to the encryption and decryption system of the target client via the target client application, so that the encryption and decryption system of the target client obtains the encryption algorithm list supported by the encryption and decryption system of the target server according to the configuration export request.

[0472] In step S1702, based on the encryption algorithm list, an encryption algorithm negotiation operation is performed between the encryption and decryption system of the target server and the encryption and decryption system of the target client to determine the corresponding target encryption algorithm and the key corresponding to the target encryption algorithm on the target server.

[0473] In step S1703, a sensitive data request is sent to the baseboard management controller of the target server through the target client application, so that the baseboard management controller obtains the corresponding exported sensitive data, and sends the exported sensitive data to the encryption and decryption system of the target server, so that the exported sensitive data is encrypted using the target encryption algorithm in the encryption and decryption system of the target server, and the encrypted exported sensitive data is sent to the encryption and decryption system of the target client.

[0474] In step S1704, the encrypted sensitive data and the preset configuration data are combined in the encryption and decryption system of the target client to obtain corresponding target configuration information, and the target configuration information is exported to the target client application.

[0475] During the sensitive data export phase, that is, when the BMC exports configuration files containing sensitive information, the operation sequence is as follows: Figure 18 The specific process is as follows:

[0476] 1. Start an export request:

[0477] (1) The client application initiates a configuration export request;

[0478] (2) After receiving the request, the client EDS requests the server EDS for a list of supported encryption algorithms.

[0479] 2. Algorithm negotiation:

[0480] (1) The server EDS returns a list of supported encryption algorithms;

[0481] (2) The client displays the algorithm selection interface, and the user selects a target encryption algorithm;

[0482] (3) The client EDS sends the selected target encryption algorithm to the server EDS and requests confirmation.

[0483] 3. Server algorithm confirmation and key preparation:

[0484] (1) The server EDS checks whether it contains the target encryption algorithm;

[0485] (2) If the target encryption algorithm is not supported, a request is returned to reselect the algorithm, and the client needs to reselect;

[0486] (3) If supported, further determine whether the target encryption algorithm is symmetric encryption;

[0487] (4) If it is symmetric encryption, a shared key is used. If it is asymmetric encryption, the server generates a key pair (public key, private key) and returns the public key to the client.

[0488] 4. Sensitive data encryption process:

[0489] (1) After receiving the confirmation, the client EDS will use the selected target encryption algorithm as the final confirmation;

[0490] (2) The client application initiates a request for sensitive data;

[0491] (3) The server application (such as BMC) obtains sensitive data from the storage and transmits it to the server EDS;

[0492] (4) The server EDS encrypts the sensitive data and returns it to the client EDS;

[0493] (5) The client EDS combines the encrypted sensitive data with the configuration data;

[0494] (6) Finally, the complete configuration content including sensitive encrypted data is returned.

[0495] 5. Output results:

[0496] The exported data that the client ultimately obtains is the configuration data and encrypted sensitive fields (that is, sensitive encrypted data, and the target encryption algorithm and key mechanism are determined by the encryption algorithm and key negotiation).

[0497] It can be understood that the embodiments of the present application can support encrypted export and secure reorganization import of sensitive configuration items, so as to partially encrypt sensitive fields in the exported configuration data and then reorganize them into a complete configuration when imported; in addition, the embodiments of the present application also support cross-environment configuration migration and encryption protection mechanisms, so that configuration data can be securely migrated between different servers or systems, and support heterogeneous environment configuration import and export.

[0498] Optionally, in one embodiment of the present application, it also includes: before sending a configuration import request or a configuration export request to the encryption and decryption system of the target client through the target client application, obtaining the identity information, token or certificate corresponding to the client user or entity; authenticating the client user or entity through the identity information, token or certificate to obtain a corresponding authentication result; mapping the corresponding role according to the authentication result, and judging whether the role is allowed to perform the corresponding import or export operation based on the role and preset permission rules; if the role is allowed to perform the import or export operation, performing the corresponding sensitive data export or sensitive data export operation, otherwise returning the corresponding authentication failure information.

[0499] It should be noted that before sending a configuration import request or a configuration export request to the client EDS through the client application, the embodiment of the present application also needs to obtain the identity information, token or certificate corresponding to the client user or entity to authenticate the client user or entity, map the corresponding role, and based on the role and the corresponding permission rules, determine whether the role is allowed to perform the corresponding import or export operation;

[0500] If the role is allowed to perform the import or export operation, the corresponding sensitive data export or sensitive data export operation is performed; otherwise, the corresponding authentication failure information is returned.

[0501] Therefore, the embodiments of the present application can complete authentication and permission verification before importing and exporting sensitive data, thereby preventing security issues such as unauthorized access, spoofing attacks, and unauthorized operations.

[0502] An embodiment of the present application also provides an electronic device, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to execute the steps in any of the above-mentioned embodiments of the sensitive data import and export method based on the baseboard management controller.

[0503] An embodiment of the present application also provides a computer-readable storage medium, which stores a computer program, wherein the computer program is configured to execute the steps of any of the above-mentioned sensitive data import and export method embodiments based on the baseboard management controller when running.

[0504] In an exemplary embodiment, the computer-readable storage medium may include, but is not limited to, various media that can store computer programs, such as a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk, or an optical disk.

[0505] An embodiment of the present application further provides a computer program product, which includes a computer program. When the computer program is executed by a processor, the steps in any of the above-mentioned sensitive data import and export method embodiments based on a baseboard management controller are implemented.

[0506] An embodiment of the present application also provides another computer program product, including a non-volatile computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, it implements the steps of any of the above-mentioned sensitive data import and export method embodiments based on the baseboard management controller.

[0507] Professionals may further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the above description has generally described the components and steps of each example according to their functions. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0508] The above is a detailed introduction to the sensitive data import and export method, device, equipment and medium based on the baseboard management controller provided by this application. This article uses specific examples to illustrate the principles and implementation methods of this application. The description of the above embodiments is only used to help understand the method of this application and its core idea. It should be pointed out that for ordinary technicians in this technical field, without departing from the principles of this application, several improvements and modifications can be made to this application, and these improvements and modifications also fall within the scope of protection of the claims of this application.

Claims

1. A sensitive data import and export system based on a baseboard management controller, characterized in that: include: An encryption algorithm selection module is configured to collect corresponding context information from a target client and a target server respectively, generate a list of encryption algorithms supported by the target client and the target server according to the context information, score the list of encryption algorithms, negotiate and select the best encryption algorithm from the scored list of encryption algorithms to obtain a corresponding target encryption algorithm, and determine a key corresponding to the target encryption algorithm; an encryption module, configured to obtain original plaintext sensitive data input by a client user during a sensitive data import phase, or obtain corresponding exported sensitive data from a baseboard management controller of the target server during a sensitive data export phase, and encrypt the original plaintext sensitive data or the exported sensitive data using the target encryption algorithm and the key to obtain corresponding sensitive encrypted data; a decryption module, configured to decrypt the sensitive encrypted data using the key via the encryption and decryption system of the target server during the sensitive data import phase to obtain sensitive decrypted data; a communication module configured to export the sensitive encrypted data that has passed the preset data integrity verification operation to the target client application during the sensitive data export phase, or to import the sensitive decrypted data that has passed the preset data integrity verification operation to the baseboard management controller of the target server during the sensitive data import phase; A zero-trust adaptation module, configured to perform dynamic identity authentication, real-time policy engine decision-making, session persistence verification, and context verification operations based on a preset zero-trust policy during the sensitive data export phase and the sensitive data import phase, so as to dynamically adjust import and export operation permissions; The sensitive data import and export system based on the baseboard management controller further includes: An authentication module is used to perform authentication operations on client users or entities accessing the system before importing or exporting sensitive data, so that the client users or entities can only perform authorized operations; A key management module, used to generate, store and distribute keys corresponding to the target encryption algorithm; a data integrity verification module, configured to generate an integrity check value corresponding to the sensitive encrypted data or the sensitive decrypted data, and perform a data integrity check on the sensitive encrypted data or the sensitive decrypted data according to the integrity check value, so as to output the corresponding sensitive encrypted data or the sensitive decrypted data if the sensitive encrypted data or the sensitive decrypted data passes the data integrity check; otherwise, generate and record data anomaly information corresponding to the sensitive encrypted data or the sensitive decrypted data; A plug-in module is used to load the encryption algorithm selection module, the encryption module, the decryption module, the authentication module, the data integrity verification module and the key management module in the form of a plug-in, and run in a preset isolated sandbox, and support hot loading or unloading of algorithm plug-ins during the running process.

2. The sensitive data import and export system based on the baseboard management controller according to claim 1 is characterized in that: The encryption algorithm selection module includes: A policy management unit, configured to dynamically adjust the security level of each encryption algorithm in the encryption algorithm list based on a preset current security policy, and to configure an enabled or disabled algorithm list; an algorithm capability identification unit, configured to obtain the list of encryption algorithms supported by the target server, and query the list of enabled or disabled algorithms to obtain corresponding algorithm query results; a negotiation processing unit, configured to send the encryption algorithm list to the target client, select an encryption algorithm from the encryption algorithm list at the target client, and perform encryption algorithm negotiation on the encryption algorithm based on the algorithm query result and the security level to generate the target encryption algorithm; An interface service unit is used to output the target encryption algorithm to the encryption module and provide an interface of the encryption algorithm selection module so that the key management module and the communication module call the encryption algorithm selection module.

3. The sensitive data import and export system based on the baseboard management controller according to claim 2 is characterized in that: The negotiation processing unit is specifically configured to: Obtaining a target encryption algorithm from the encryption algorithm list selected by the client user through the front-end interface of the target client application, and sending the target encryption algorithm to the encryption and decryption system of the target client; Sending the target encryption algorithm to the encryption and decryption system of the target server through the encryption and decryption system of the target client, so as to determine whether the target server supports the target encryption algorithm through the encryption and decryption system of the target server; If the target server does not support the target encryption algorithm, reselecting a new target encryption algorithm from the target encryption algorithm list through the target client; If the target server supports the target encryption algorithm, determining the type of the target encryption algorithm; When the target encryption algorithm is symmetric encryption, obtaining a shared key corresponding to the symmetric encryption through the key management module and generating confirmation information that supports the target encryption algorithm; When the target encryption algorithm is asymmetric encryption, the encryption and decryption system of the target server calls the key management module to generate a key pair corresponding to the target encryption algorithm, returns the public key in the key pair, and generates confirmation information that supports the target encryption algorithm.

4. The sensitive data import and export system based on the baseboard management controller according to claim 1 is characterized in that: The key management module includes: A key generator, configured to determine a symmetric key or an asymmetric key corresponding to the target encryption algorithm according to the type of the target encryption algorithm, and automatically generate a key pair corresponding to the symmetric key or the asymmetric key; A key storage device for storing the key pair based on a preset key security access policy; A key negotiator, configured to perform a key negotiation operation between the target client and the target server to generate a corresponding shared key; A key rotator, configured to switch the key pair based on a preset rotation period; An access controller, configured to manage the use rights of the key pair; An audit recorder, used to record operation data corresponding to all operation behaviors corresponding to the key pair; A key destroyer is used to destroy the key pair, generate a corresponding destruction record, and save the destruction record in the audit recorder.

5. The sensitive data import and export system based on baseboard management controller according to claim 1, characterized in that: The encryption module includes: An encryption parameter management unit, configured to call the key pair generated by the key management module and manage the algorithm parameters corresponding to the target encryption algorithm; an encryption algorithm execution unit, configured to obtain the original plaintext sensitive data in the sensitive data import phase, or the exported sensitive data in the sensitive data export phase, and encrypt the original plaintext sensitive data or the sensitive fields in the exported sensitive data using the target encryption algorithm and the key pair to obtain corresponding sensitive encrypted data; An encrypted data packaging unit, used for packaging the sensitive encrypted data into a unified format structure; The security interface unit is used to provide a standard calling interface so that the encryption algorithm selection module and the communication module can call the encryption module.

6. The sensitive data import and export system based on baseboard management controller according to claim 1, characterized in that: The data integrity verification module includes: a hash generation unit, configured to calculate, based on a preset hash algorithm, a sending-end hash value and a receiving-end hash value corresponding to the sensitive encrypted data at a sending end and a receiving end, respectively, and determine whether the sending-end hash value and the receiving-end hash value meet a preset data matching requirement, wherein when the sending-end hash value and the receiving-end hash value meet the preset data matching requirement, it is determined that the sensitive encrypted data passes the data integrity verification; a digest comparison unit, configured to generate a digest corresponding to the sensitive decrypted data, sign the digest using the private key of the sending end, and send the signed digest and the sensitive decrypted data to the receiving end, so as to determine whether the digest meets a preset signature legitimacy requirement using the public key of the receiving end; wherein, if the digest meets the signature legitimacy requirement, the sensitive decrypted data is determined to have passed data integrity verification; an abnormality alarm unit, configured to execute a corresponding data abnormality alarm operation and record corresponding data abnormality information when the hash value of the sending end and the hash value of the receiving end do not meet the preset data matching requirement, or when the digest does not meet the signature legitimacy requirement; A log recording unit is used to record data integrity verification information of the sensitive encrypted data.

7. The sensitive data import and export system based on baseboard management controller according to claim 1, characterized in that: The communication module includes: An interface calling unit, configured to provide a corresponding calling interface to the target client application or the baseboard management controller of the target server to receive a corresponding import configuration request or export configuration request; an encapsulation and decapsulation unit, configured to provide an encapsulation data packet structure, so as to perform encapsulation or decapsulation operations on the sensitive encrypted data through the encapsulation data packet structure; A secure communication management unit, configured to establish a secure channel with the encryption and decryption system of the target client or the encryption and decryption system of the target server; The protocol negotiation unit is used to perform corresponding encryption algorithm negotiation operations in conjunction with the encryption algorithm selection module to obtain the corresponding target encryption algorithm.

8. The sensitive data import and export system based on baseboard management controller according to claim 1, characterized in that: The plug-in module includes: A plug-in management unit, configured to provide a plug-in loading interface and a plug-in unloading interface, and register with the encryption algorithm selection module through the plug-in loading interface, so that the encryption algorithm selection module calls the plug-in loading interface to perform encryption and decryption operations; Hot loading unit, used to dynamically update policies for configuration files or interfaces.

9. The sensitive data import and export system based on baseboard management controller according to claim 1, characterized in that: The authentication module includes: an identity authentication unit, configured to obtain identity information, a token, or a certificate corresponding to the client user or the entity, and perform identity authentication on the client user or the entity using the identity information, the token, or the certificate to obtain a corresponding identity authentication result; A permission identification unit is used to map the corresponding role according to the identity authentication result and query the preset permission rules to determine whether the role is allowed to perform the import or export operation. If the role is allowed to perform the import or export operation, the corresponding sensitive data export or sensitive data export operation is performed; otherwise, the corresponding authentication failure information is returned; a session management unit, configured to generate a corresponding session token when the role is allowed to perform an import or export operation, so as to perform a corresponding session management operation based on the session token; The security audit unit is used to record the authentication failure information in a preset security audit log and send the security audit log to a target mailbox.

10. A sensitive data import and export method based on a baseboard management controller, applied in the sensitive data import stage, characterized in that: The following steps are involved: Sending a configuration import request to the encryption and decryption system of the target client through the target client application, so that the encryption and decryption system of the target client obtains the encryption algorithm list supported by the target server according to the configuration import request; Based on the encryption algorithm list, performing an encryption algorithm negotiation operation between the encryption and decryption system of the target server and the encryption and decryption system of the target client to determine a corresponding target encryption algorithm and a key corresponding to the target encryption algorithm on the target server; Obtaining plaintext sensitive data input by a client user, encrypting the plaintext sensitive data using the target encryption algorithm through the encryption and decryption system of the target client to obtain corresponding sensitive encrypted data, and performing data integrity verification on the sensitive encrypted data to obtain sensitive encrypted data that passes the data integrity verification; decrypting the sensitive encrypted data using the key in the encryption and decryption system of the target server to obtain corresponding sensitive decrypted data, performing data integrity verification on the sensitive decrypted data, and importing the sensitive decrypted data that passes the data integrity verification into the baseboard management controller of the target server; The performing of data integrity verification on the sensitive encrypted data to obtain sensitive encrypted data that passes the data integrity verification includes: Based on a preset hash algorithm, calculating a sending-end hash value and a receiving-end hash value corresponding to the sensitive encrypted data at a sending end and a receiving end of the sensitive encrypted data, respectively; Determine whether the sending end hash value and the receiving end hash value meet a preset data matching requirement; If the sending end hash value and the receiving end hash value meet the preset data matching requirement, determining that the sensitive encrypted data passes the data integrity verification; If the sending end hash value and the receiving end hash value do not meet the preset data matching requirement, a corresponding data anomaly alarm operation is performed and corresponding data anomaly information is recorded.

11. The sensitive data import and export method based on the baseboard management controller according to claim 10, characterized in that: The performing of an encryption algorithm negotiation operation between the encryption and decryption system of the target server and the encryption and decryption system of the target client based on the encryption algorithm list to determine a corresponding target encryption algorithm and a key corresponding to the target encryption algorithm on the target server includes: Obtaining a target encryption algorithm from the encryption algorithm list selected by the client user through the front-end interface of the target client application, and sending the target encryption algorithm to the target client encryption and decryption system; Sending the target encryption algorithm to the encryption and decryption system of the target server through the encryption and decryption system of the target client, so as to determine whether the target server supports the target encryption algorithm through the encryption and decryption system of the target server; If the target server does not support the target encryption algorithm, reselecting a new target encryption algorithm from the encryption algorithm list through the target client; If the target server supports the target encryption algorithm, determining the type of the target encryption algorithm; When the target encryption algorithm is symmetric encryption, obtaining a shared key corresponding to the symmetric encryption and generating confirmation information that supports the target encryption algorithm; When the target encryption algorithm is asymmetric encryption, the encryption and decryption system of the target server generates a key pair corresponding to the target encryption algorithm, returns the public key in the key pair, and generates confirmation information that supports the target encryption algorithm.

12. The sensitive data import and export method based on the baseboard management controller according to claim 10, characterized in that: The performing data integrity verification on the sensitive decrypted data includes: Generate a digest corresponding to the sensitive decrypted data, sign the digest using the private key of the sending end, and send the signed digest and the sensitive decrypted data to the receiving end; Determining whether the summary meets the preset signature legitimacy requirements through the public key of the receiving end; If the digest meets the signature legitimacy requirement, determining that the sensitive decrypted data passes the data integrity verification; If the summary does not meet the signature validity requirement, the corresponding data anomaly alarm operation is performed and the corresponding data anomaly information is recorded.

13. The sensitive data import and export method based on the baseboard management controller according to claim 10, characterized in that: Decrypting the sensitive encrypted data using the key in the encryption and decryption system of the target server to obtain corresponding sensitive decrypted data, performing data integrity verification on the sensitive decrypted data, and importing the sensitive decrypted data that passes the data integrity verification into the baseboard management controller of the target server, including: Parsing the ciphertext structure corresponding to the sensitive encrypted data through the encryption and decryption system of the target server to obtain parsed data corresponding to the sensitive encrypted data; Obtaining a shared key or a private key corresponding to the sensitive encrypted data, decrypting the parsed data using the shared key or the private key, and determining whether the sensitive encrypted data is successfully decrypted; If the sensitive encrypted data is decrypted successfully, the corresponding sensitive decrypted data is generated; otherwise, an import failure status message is returned; Constructing a configuration file corresponding to the sensitive decrypted data through the target client application, and sending the configuration file to the target server application, so that the target server application performs an import operation of the sensitive encrypted data according to the configuration file, and determines whether the sensitive encrypted data is successfully imported; If the sensitive encrypted data is imported successfully, import success status information is returned; otherwise, import failure status information is returned.

14. A sensitive data import and export method based on a baseboard management controller, in the sensitive data export stage, characterized in that: The following steps are involved: Sending a configuration export request to the encryption and decryption system of the target client through the target client application, so that the encryption and decryption system of the target client obtains the encryption algorithm list supported by the encryption and decryption system of the target server according to the configuration export request; Based on the encryption algorithm list, performing an encryption algorithm negotiation operation between the encryption and decryption system of the target server and the encryption and decryption system of the target client to determine a corresponding target encryption algorithm and a key corresponding to the target encryption algorithm on the target server; Sending a sensitive data request to a baseboard management controller of the target server through the target client application, so that the baseboard management controller obtains corresponding exported sensitive data, and sends the exported sensitive data to an encryption and decryption system of the target server, so that the exported sensitive data is encrypted using the target encryption algorithm in the encryption and decryption system of the target server, and based on a preset hash algorithm, respectively calculating a sending-end hash value and a receiving-end hash value corresponding to the encrypted exported sensitive data at a sending end and a receiving end; Determine whether the sending end hash value and the receiving end hash value meet a preset data matching requirement; If the sending end hash value and the receiving end hash value do not meet the preset data matching requirement, a corresponding data anomaly alarm operation is performed and corresponding data anomaly information is recorded; if the sending end hash value and the receiving end hash value meet the preset data matching requirement, it is determined that the encrypted exported sensitive data passes the data integrity verification, and the encrypted exported sensitive data is sent to the encryption and decryption system of the target client; The encrypted sensitive data and the preset configuration data are combined in the encryption and decryption system of the target client to obtain corresponding target configuration information, and the target configuration information is exported to the target client application.

15. The sensitive data import and export method based on the baseboard management controller according to claim 14, characterized in that: Also includes: Before sending the configuration import request or the configuration export request to the encryption and decryption system of the target client through the target client application, obtaining identity information, token or certificate corresponding to the client user or entity; authenticating the client user or the entity using the identity information, the token, or the certificate to obtain a corresponding authentication result; Mapping the corresponding role according to the identity authentication result, and based on the role and preset permission rules, determining whether the role is allowed to perform the corresponding import or export operation; If the role is allowed to perform the import or export operation, the corresponding sensitive data export or sensitive data export operation is performed, otherwise the corresponding authentication failure information is returned.

16. An electronic device, characterized in that: include: memory for storing computer programs; A processor is used to implement the steps of the sensitive data import and export method based on the baseboard management controller as described in any one of claims 10 to 15 when executing the computer program.

17. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, wherein the computer program, when executed by a processor, implements the steps of the sensitive data import and export method based on the baseboard management controller as described in any one of claims 10 to 15.

18. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the sensitive data import and export method based on the baseboard management controller as described in any one of claims 10 to 15 are implemented.

Images