A data security management method, device, equipment and storage medium

Abstract

The application discloses a data security management method, device and equipment and a storage medium, and relates to the technical field of computers.The method comprises the following steps: evaluating the risk value of current power data in a current scene; determining a to-be-called security capability according to the risk value, and generating a calling instruction of the to-be-called security capability; converting the calling instruction into a target instruction that can be recognized by a security device through a preset adapter, and sending the target instruction to the security device; and receiving state information of the security device executing the target instruction through the preset adapter.The technical scheme of the embodiment of the application realizes dynamic risk quantification, ensures that the security protection matches the power data risk, and converts the calling instruction into an instruction that can be recognized by the security device through the adapter, thereby realizing seamless integration, smooth iteration and collaborative work of old security capabilities and new security capabilities, and reducing the transformation cost.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of computer technology, and in particular to a data security management method, device, equipment and storage medium. BACKGROUND

[0002] With the deepening of the construction of new power systems, power data circulation and sharing has become an inevitable trend. As the core production factor supporting efficient operation of the power grid, high-quality development of enterprises and high-quality supply of services, power data is increasingly flowing in the links of power generation, power transmission, power transformation, power distribution and power utilization, and cross-organizational and cross-regional data transmission and sharing is increasing.

[0003] The power data security capability refers to the technical and management measures taken by the power industry in the process of data collection, storage, processing, transmission and use to prevent data leakage, tampering, destruction or illegal access. However, the current technical solutions for power data security have the problem that the interfaces between different new and old security devices and systems are not unified, resulting in great integration difficulty, poor interoperability, and difficulty in collaborative scheduling of new and old security capabilities. SUMMARY

[0004] The present application provides a data security management method, device, equipment and storage medium to solve the problem of collaborative scheduling of new and old security capabilities.

[0005] In a first aspect, the present application provides a data security management method, comprising:

[0006] evaluating a risk value of current power data in a current scenario;

[0007] determining a to-be-called security capability according to the risk value, and generating a calling instruction of the to-be-called security capability;

[0008] converting the calling instruction into a target instruction recognizable by a security device through a preset adapter, and sending the target instruction to the security device, wherein the target instruction is used to instruct the security device to execute the to-be-called security capability on the current power data;

[0009] receiving state information of the security device executing the target instruction through the preset adapter.

[0010] In a second aspect, the present application provides a data security management device, comprising:

[0011] an evaluation module configured to evaluate a risk value of current power data in a current scenario;

[0012] an instruction generation module configured to determine a to-be-called security capability according to the risk value, and generate a calling instruction of the to-be-called security capability;

[0013] The instruction sending module is configured to convert the calling instruction into a target instruction recognizable by the security device through a preset adapter and send the target instruction to the security device, where the target instruction is used to instruct the security device to execute the to-be-called security capability on the current power data.

[0014] The information receiving module is configured to receive state information of the security device executing the target instruction through the preset adapter.

[0015] In a third aspect, the present application provides an electronic device, which comprises:

[0016] at least one processor;

[0017] and a memory in communication connection with the at least one processor;

[0018] The memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor to enable the at least one processor to execute the data security management method of the first aspect.

[0019] In a fourth aspect, the present application provides a computer readable storage medium, which stores a computer instruction, and the computer instruction is used to enable a processor to implement the data security management method of the first aspect when executed.

[0020] The data security management scheme provided by the present application evaluates the risk value of the current power data in the current scenario, determines the to-be-called security capability according to the risk value, generates a calling instruction of the to-be-called security capability, converts the calling instruction into a target instruction recognizable by a security device through a preset adapter, sends the target instruction to the security device, where the target instruction is used to instruct the security device to execute the to-be-called security capability on the current power data, and receives state information of the security device executing the target instruction through the preset adapter. By adopting the above technical scheme, the static strategy of "one-size-fits-all" is replaced, the to-be-called security capability is accurately determined according to the evaluated risk value, dynamic risk quantification is realized, the security protection is ensured to match the power data risk, a collaborative architecture of new and old security capabilities is constructed, the encryption gateway and other inventory security devices of the old security capability that have been deployed are converted into target instructions recognizable by the security device through the adapter, seamless integration, smooth iteration and collaborative work of the old security capability and the new security capability are realized, and the transformation cost is reduced.

[0021] It should be understood that the content described in this part is not intended to identify key or important features of the present application, nor is it used to limit the scope of the present application. Other features of the present application will become apparent from the following description. BRIEF DESCRIPTION OF DRAWINGS

[0022] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the embodiments description will be briefly introduced as follows. Obviously, the drawings in the following description are only some embodiments of the present application, and all other drawings obtained by those of ordinary skill in the art without creative effort based on these drawings should be within the protection scope of the present application.

[0023] Figure 1 is a flow chart of a data security management method according to an embodiment of the present application;

[0024] Figure 2 is a flow chart of a data security management method according to an embodiment of the present application;

[0025] Figure 3 is a structural schematic diagram of a data security management device according to an embodiment of the present application;

[0026] Figure 4 is a structural schematic diagram of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0027] In order to make the person in the art better understand the present application, the technical solutions in the embodiments of the present application will be described clearly and completely in the following with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only some embodiments of the present application, but not all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort should be within the protection scope of the present application.

[0028] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and do not necessarily describe a specific order or sequence. It should be understood that the data thus used can be interchanged under appropriate circumstances, so that the embodiments of the application described herein can be implemented in an order other than that illustrated or described herein. In the description of the present application, "a plurality of" means two or more, unless otherwise specified. The association relationship of the associated objects is described, and "and / or" indicates that there can be three relationships, for example, A and / or B, which can represent the three cases of A alone, A and B together, and B alone. The character " / " generally represents an "or" relationship between the associated objects before and after it. In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion, for example, a process, method, system, product or device that includes a series of steps or units does not necessarily limit to those steps or units clearly listed, but can include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0029] Embodiment one

[0030] Figure 1 A flowchart of a data security management method is provided for the first embodiment of the present application. The present embodiment can be applied to the case of managing data security capabilities. The method can be executed by a data security management device, which can be realized in the form of hardware and / or software. The data security management device can be configured in an electronic device, which can be composed of two or more physical entities or one physical entity.

[0031] As Figure 1 shown, the data security management method provided by the first embodiment of the present application can be applied to the field of power data cross-domain circulation, and specifically includes the following steps:

[0032] S101, evaluating the risk value of the current power data in the current scenario.

[0033] In the present embodiment, the risk value of the current power data can be determined according to the use, processing or transmission scenario of the current power data. For example, if the importance of the current power data is high in the current scenario, the risk value of the current power data in the current scenario is also high.

[0034] S102, determining the security capability to be called according to the risk value, and generating the calling instruction of the security capability to be called.

[0035] In this embodiment, different risk values ​​can correspond to different security capabilities to be invoked. For example, a high risk value can correspond to a security capability with high protection effectiveness, while a low risk value can correspond to a security capability with moderate protection effectiveness. The security capability corresponding to the current risk value can be determined as the security capability to be invoked, and an invocation instruction for that security capability can be generated.

[0036] S103. The invocation instruction is converted into a target instruction that can be recognized by the security device, and the target instruction is sent to the security device, wherein the target instruction is used to instruct the security device to execute the security capability to be invoked on the current power data.

[0037] In this embodiment, an adapter layer can be pre-built. The preset adapter in this layer can convert standardized calling instructions (such as RESTful API, gRPC) into proprietary protocol instructions (such as CLI commands, SNMPTrap, proprietary SDK calls) that can be recognized by existing security devices. For example, the preset adapter can perform key management and encryption / decryption operations on traditional hardware encryption gateways by encapsulating expect scripts or calling vendor SDKs.

[0038] S104. Receive status information of the security device executing the target instruction through the preset adapter.

[0039] In this embodiment, the preset adapter can also be used to parse the unique status outputs of existing security devices (such as LED light status, Syslog messages and performance counters) or through dedicated monitoring interfaces (such as SNMPOID and JMX) to convert the status information of the security device executing the target instruction into standardized status information, such as health status and performance indicators (such as CPU, memory, throughput and latency information).

[0040] For example, taking a cross-provincial power grid data sharing scenario, Province A is the sender and Province B is the receiver. The specific implementation process of this method is as follows:

[0041] First, determine the security capabilities to be invoked based on the risk value: DLP capability, encryption gateway capability, and digital watermarking capability. Then, generate an invocation instruction for the security capability to be invoked and distribute the instruction and the information of the security capability to be invoked to the API gateway, specifically including:

[0042] 1) DLP capability execution parameters: Sensitive rule base version V3.0, recognition accuracy threshold 95%;

[0043] 2) Encryption gateway capability execution parameters: Encryption algorithm SM4, key length 128 bits;

[0044] 3) Digital watermarking capability execution parameters: The watermarking algorithm is based on blockchain, and the watermark information includes the data source and circulation path.

[0045] Then the API gateway receives new energy power generation prediction data, calls the DLP capability to identify sensitive information of the data, marks sensitive fields, transmits the marked sensitive data to the encryption gateway for SM4 encryption, transmits the encrypted data to the digital watermarking capability, embeds the blockchain watermark, and finally transmits the processed data to the B province power grid through a secure channel. Through the adapter, the state information of the target instructions executed by each security device is received, specifically including:

[0046] 1) DLP capability execution time: 35ms, 5 sensitive fields are identified;

[0047] 2) Encryption gateway execution time: 20ms, the size of the encrypted data increases by 10%;

[0048] 3) Digital watermarking execution time: 40ms, watermark embedding is successful;

[0049] 4) Generate execution logs and audit records to record the complete process of data flow.

[0050] The technical scheme of the embodiment of the application accurately determines the to-be-called security capability according to the evaluated risk value, realizes dynamic risk quantification, ensures that the security protection matches the power data risk, and builds a collaborative architecture of new and old security capabilities, so that the existing security devices such as the encryption gateway of the old security capability are converted into target instructions that can be recognized by the security device through the adapter, realizing seamless integration, smooth iteration and collaborative work of the old security capability and the new security capability, and reducing the transformation cost.

[0051] Optionally, before the generation of the calling instruction of the to-be-called security capability, the method further includes: generating a security capability scheduling instruction; setting a priority for different to-be-called security capabilities according to a real-time requirement of the security capability scheduling instruction and current power data; wherein the generation of the calling instruction of the to-be-called security capability includes: generating the calling instruction of the to-be-called security capability according to the priority, the real-time requirement and a system resource occupancy rate.

[0052] Specifically, a security capability scheduling instruction can be generated first, and then priorities of different to-be-called security capabilities can be set according to real-time requirements of the instruction and current power data. For example, if the real-time requirements of the instruction and current power data are high, the to-be-called security capability (corresponding to the instruction and current power data) is set to have a high priority to ensure a fast response. For non-real-time instructions and current power data, i.e., the real-time requirements of the instruction and current power data are low, the to-be-called security capability can be set to have a low priority. The calling instruction of the to-be-called security capability can be generated according to the priorities, real-time requirements and system resource occupancy. For example, if the to-be-called security capabilities include a and b, the priority of a is higher than that of b, the real-time requirement of a is higher than that of b, and the current system occupancy is high, the generated calling instruction is: a is called preferentially, and b is called with a delay.

[0053] Optionally, the generating the calling instruction of the to-be-called security capability according to the priority, the real-time requirement and the system resource occupancy includes: when the system resource occupancy is greater than a preset threshold or the real-time requirement is a first real-time requirement, generating a first calling instruction of the to-be-called security capability, wherein the first calling instruction includes an instruction of calling a to-be-called security capability with a priority greater than a preset priority threshold; when the system resource occupancy is less than or equal to the preset threshold or the real-time requirement is a second real-time requirement, generating a second calling instruction of the to-be-called security capability, wherein the second calling instruction includes an instruction of calling a to-be-called security capability with a priority less than the preset priority threshold, and the first real-time requirement is higher than the second real-time requirement.

[0054] For example, when processing a scheduling instruction for an object (with a delay tolerance of ≤50 ms), the information included in the calling instruction of the to-be-called security capability can be: hardware encryption (priority = 90). When processing historical power statistics (with a delay tolerance of >100 ms), the information included in the calling instruction of the to-be-called security capability can be: software encryption (priority = 30).

[0055] When processing a scheduling instruction for an object and a power encryption operation, the information included in the calling instruction of the to-be-called security capability can be: scheduling instruction operation (priority = 100) preemptive execution (completed within 20 ms), and power encryption operation (priority = 20) suspended waiting (executed after resource release).

[0056] When processing data desensitization, the information included in the calling instruction of the to-be-called security capability can be: only execute real-time transaction (priority = 80) desensitization during power peak (CPU occupancy = 90%), and suspend log operation. Automatically start log batch desensitization (priority = 10) during early morning idle time (CPU usage = 25%).

[0057] Optionally, before the priority of different to-be-invoked security capabilities is set according to the real-time requirement of the security capability scheduling instruction and the current power data, further comprising: constructing a time delay cost function and a risk cost function, wherein the time delay cost function is used to determine the time delay cost of the different priorities of the to-be-invoked security capabilities, and the risk cost function is used to determine the risk cost of the different priorities of the to-be-invoked security capabilities; constructing an expectation function about the priority of the to-be-invoked security capabilities by using the time delay cost function and the risk cost function; when the time delay cost function is a convex function and the risk cost function is a piecewise linear function, determining an explicit analytic function of the expectation function, wherein the explicit analytic function contains the correlation between the priority of the to-be-invoked security capability and the risk value, the security capability scheduling instruction weight, the current load of the to-be-invoked security capability, the maximum load capacity of the to-be-invoked security capability and the resource usage threshold of the to-be-invoked security capability, and the security capability scheduling instruction weight is determined according to the real-time requirement of the security capability scheduling instruction;

[0058] wherein the priority of different to-be-invoked security capabilities is set according to the real-time requirement of the security capability scheduling instruction and the current power data, comprising:

[0059] With the minimum time delay cost and risk cost as the target, the priority of different to-be-invoked security capabilities is determined by using the explicit analytic function and the real-time requirement of the security capability scheduling instruction and the current power data.

[0060] For example, based on the risk assessment result and the business demand, the risk level, the business real-time requirement and the resource usage are comprehensively considered, so that the average delay + risk cost is as small as possible. The optimization target is as follows:

[0061]

[0062] wherein D(P) is a time delay cost function (such as the cost of message delay and scheduling response time), which is generally a convex function. R(P) is a risk cost function, which can be a piecewise linear function, and which can quantify the cost that the system may pay in the "extreme bad case". λ is a weighting parameter, which represents the degree of attention to risk. When λ takes a small value, it means that the efficiency is prioritized (low delay, risk-taking). When λ takes a large value, it means that the safety is prioritized (low risk, tolerant to large delay). P represents the priority of the security capability. E[ ] represents the expectation function. E is the cost in the minimum average sense, rather than the value at a certain time.

[0063] When D(P) is a convex function and R(P) is a piecewise linear function, the function E has an explicit analytic solution. A Lagrange function can be constructed first:

[0064]

[0065] And apply the KKT optimality condition, let , get the following explicit analytic function, so as to ensure the solvability and real-time of function E:

[0066]

[0067] Where: the greater the value of P represents the higher priority, R represents the risk value, Indicates the security capability scheduling instruction weight, LC indicates the current load of the security capability to be called, reflecting the amount of resources required for security capability execution, Indicates the maximum load capacity of the security capability to be called, that is, the maximum amount of resources that the security capability can handle, Indicates the resource usage threshold of the security capability to be called, the value range is 0 to 1.

[0068] The advantage of this setting is that by multiplying the risk value and the business weight, it ensures that high-risk and high-real-time requirement businesses can obtain higher priority. At the same time, by introducing the influence of resource usage, it realizes the optimal allocation of resources and avoids resource competition and bottlenecks.

[0069] Where, in order to adapt to the time-varying nature of the power system operating state and various sudden abnormal conditions, a dynamic weight adjustment mechanism can be further introduced:

[0070]

[0071] This mechanism can adaptively correct the security capability scheduling instruction weight according to the real-time running frequency deviation of the security capability. This mechanism ensures that critical businesses can obtain higher security priority in the case of security capability exception, significantly enhancing the risk response capability and operation stability of the system.

[0072] Optionally, after receiving the state information of the security device executing the target instruction through the preset adapter, it further includes: weighting the actual load in the state information at the first time and the ideal load at the second time to obtain the ideal load at the first time, and adjusting the calling instruction according to the ideal load at the first time, wherein the first time is later than the second time.

[0073] Specifically, in various resource invocation scenarios, resource fluctuations are a key challenge affecting system stability and decision effectiveness. To solve this problem and improve the stability and robustness of invocation decisions, an anti-oscillation invocation mechanism can be introduced. The core design philosophy of this mechanism is to weaken the interference of short-term resource fluctuations on decision-making through a dynamic smoothing strategy, while taking into account the adaptability of the system to long-term trends. Among them, the smoothing coefficient, as a key regulatory parameter of the mechanism, plays a core role in balancing "immediate response" and "stable continuation".

[0074] The introduced anti-oscillation invocation mechanism can reduce the impact of resource fluctuations on invocation decisions through the smoothing coefficient, and the ideal load determination method is as follows:

[0075]

[0076] Among them, represents the smoothed load at time t (i.e., the first time), represents the actual load at time t, represents the smoothed load at time t-1 (i.e., the second time).

[0077] For example, the smoothing factor = 0.7. This value can achieve a good balance between tracking load changes and suppressing jitter.

[0078] Specifically, the mechanism of the smoothing coefficient is reflected in the following aspects: first, it constructs a multi-time window smoothing processing model by weighting and fusing historical invocation data and real-time resource status. For example, the smoothing coefficient gives reasonable weight to recent data to reflect the current trend, while moderately weighting long-term data to filter out high-frequency noise interference and avoid excessive adjustment of decisions due to transient fluctuations. Second, the value of the smoothing coefficient can be dynamically adapted according to the system fluctuation intensity. When the resource fluctuation amplitude is small, the coefficient value tends to enhance the immediacy of the response, ensuring that the decision can quickly adapt to small changes. When the fluctuation exceeds the preset threshold, the coefficient will automatically adjust to increase the smoothing strength, by extending the decision adjustment period and reducing the single adjustment amplitude, to reduce the impact of frequent changes on the system.

[0079] The convergence of the smoothing mechanism is proved from the perspective of control theory as follows:

[0080] Define the smoothed load sequence:

[0081]

[0082] Among them, represents the actual load at time t, represents the smoothed load at time t.

[0083] Define the load tracking error:

[0084]

[0085] Construct Lyapunov function:

[0086]

[0087] Where, Monotonically decreases over time, then the system converges.

[0088] From the smoothing formula:

[0089]

[0090] Then the error satisfies:

[0091]

[0092] Where, .

[0093] The difference can be expressed as:

[0094]

[0095] After bringing in Simplify:

[0096]

[0097] From the Cauchy-Schwarz inequality:

[0098]

[0099] We can get:

[0100]

[0101] Where, when =0.7, the convergence term coefficient =0.91, indicating that the error converges exponentially, and eventually converges. That is, the calling system will not lose control, but will become more and more stable. The system has good stability.

[0102] Through this mechanism, the calling decision can show the characteristics of "buffer adjustment" when dealing with resource fluctuations, neither over-sensitive to short-term disturbances and falling into oscillation, nor losing tracking ability of real trend due to excessive smoothing. In practice, this mechanism can effectively reduce the frequency of decision adjustment, reduce the invalid loss of resource allocation, and at the same time guarantee the long-term stability of the system in complex fluctuation environment, providing reliable decision support for efficient operation of various scenarios such as energy internet, intelligent manufacturing, transportation and logistics, etc.

[0103] Embodiment Two

[0104] Figure 2 A flowchart of a data security management method provided for Embodiment Two of the present application, the technical solution of the present application is further optimized on the basis of the above-mentioned optional technical solutions, and the specific way of managing data security capabilities is given.

[0105] Optionally, the risk value of the current power data in the current scenario is evaluated, including: determining the correlation indicators of the current power data, wherein the correlation indicators at least include data security level indicators, business importance indicators, circulation range indicators, receiver trust level indicators, and environment security indicators; performing weighted summation operation on the indicators in the correlation indicators to obtain the risk value of the current power data in the current scenario; wherein the importance of the power business corresponding to the current power data is positively correlated with the business importance indicator, the circulation range of the current power data is positively correlated with the circulation range indicator, the trust level of the receiver of the current power data is negatively correlated with the receiver trust level indicator, and the harshness of the environment of the current power data is positively correlated with the environment security indicator.

[0106] Optionally, before the security capability to be called is determined according to the risk value, it further includes: constructing a micro-service scheduling framework; abstracting the security capabilities of the security devices into security capability micro-services in the micro-service scheduling framework, and storing the metadata of the security capabilities to a first preset database under the micro-service scheduling framework to realize the registration of the security capability micro-services; creating associated interfaces of the security capability micro-services, wherein the associated interfaces at least include a security capability query interface, a security capability metadata update interface, a security capability deregistration interface, a security capability state monitoring interface, a security capability registration interface, and a security capability calling interface; wherein the security capability to be called is determined from the security capability micro-services according to the risk value.

[0107] Optionally, before the calling instruction is converted into a target instruction recognizable by the security device through a preset adapter, it further includes: configuring a preset adapter corresponding to each security device, and storing the metadata of the preset adapter to a second preset database under the micro-service scheduling framework to realize the registration of the preset adapter; wherein the state information of the security device executing the target instruction is received through the preset adapter, including: receiving standardized state information recognizable by the micro-service scheduling framework through the preset adapter, wherein the standardized state information is information obtained by converting the state information of the security device executing the target instruction through the preset adapter.

[0108] As Figure 2As shown, the data security management method provided by the second embodiment of the present application specifically comprises the following steps:

[0109] S201, constructing a micro-service scheduling framework.

[0110] Specifically, the micro-service scheduling framework comprises a micro-service layer and an adapter layer. The micro-service layer comprises a plurality of micro-services, and the adapter layer comprises a plurality of preset adapters.

[0111] S202, abstracting the security capabilities of the security device into security capability micro-services in the micro-service scheduling framework, and storing the metadata of the security capabilities into a first preset database under the micro-service scheduling framework to realize the registration of the security capability micro-services.

[0112] Exemplarily, the metadata of the security capabilities comprises:

[0113] 1) security capability identifier: uniquely identifying a security capability, used for identification and calling in the system;

[0114] 2) security capability type: describing the function type of the security capability, such as encryption, authentication, authorization, and auditing;

[0115] 3) input and output interface: defining the format and type of the input parameters and output results of the security capability;

[0116] 4) capability description: natural language description of the function and characteristics of the security capability, facilitating the understanding and use of the security administrator;

[0117] 5) execution parameter: describing the parameters required for the execution of the security capability and the value range thereof;

[0118] 6) resource requirement: defining the resource requirements of the security capability execution, such as CPU, memory, and network bandwidth;

[0119] 7) performance index: describing the performance indexes of the security capability, such as processing capacity, response time, and throughput.

[0120] S203, creating an associated interface of the security capability micro-service.

[0121] The associated interface at least comprises a security capability query interface, a security capability metadata update interface, a security capability deregistration interface, a security capability state monitoring interface, a security capability registration interface, and a security capability calling interface.

[0122] Specifically, the security capability query interface is used to support searching for security capabilities that meet requirements according to conditions such as a security capability type and a function description. The security capability metadata update interface is used to receive an update request submitted by a security capability provider and update related information in a security capability database. The security capability deregistration interface is used to receive a deregistration request submitted by a security capability provider and delete corresponding security capability information from the security capability database. The security capability state monitoring interface is used to monitor a running state and performance indicators of a registered security capability to provide a basis for security capability scheduling. The security capability registration interface is used to define an interface specification for security capability registration, update, and deregistration to support dynamic management of security capabilities. The security capability invocation interface is used to define an interface specification for security capability execution, including input parameters, output results, and error handling. Security capabilities include DLP (data leak prevention), encryption gateway, watermarking, and access control capabilities.

[0123] For example, taking typical security capabilities in the power industry as an example, metadata involved in microservice abstraction and registration of the security capabilities includes the following:

[0124] 1) DLP capability:

[0125] Security capability identifier: dlp-001;

[0126] Security capability type: data identification and protection;

[0127] Input interface: power data message;

[0128] Output interface: sensitive field marking result, such as identifying dispatching instruction ID and user identity card number;

[0129] Execution parameter: sensitive rule library version and identification accuracy threshold;

[0130] Resource requirement: CPU occupancy ≤ 10%, memory occupancy ≤ 512 MB;

[0131] Performance indicator: response time ≤ 50 ms, identification accuracy ≥ 95%;

[0132] 2) Encryption gateway capability:

[0133] Security capability identifier: encryption-gateway-001;

[0134] Security capability type: data encryption and decryption;

[0135] Input interface: plaintext data, encryption algorithm type, and key ID;

[0136] Output interface: ciphertext data;

[0137] Execution parameter: encryption algorithm type and key length

[0138] Resource requirement: CPU occupancy ≤ 20%, memory occupancy ≤ 256 MB;

[0139] Performance index: encryption speed ≥ 100 MB / s, decryption speed ≥ 100 MB / s;

[0140] 3) Digital watermarking capability:

[0141] Security capability identifier: digital-watermark-001;

[0142] Security capability type: data traceability and tracking;

[0143] Input interface: raw data, watermark information, including data source and circulation path, etc.

[0144] Output interface: data after watermark embedding;

[0145] Execution parameter: watermark algorithm type and watermark strength;

[0146] Resource requirement: CPU occupancy ≤ 15%, memory occupancy ≤ 128 MB;

[0147] Performance index: embedding speed ≥ 50 MB / s, detection accuracy ≥ 99%.

[0148] S204, configure a preset adapter corresponding to each security device, and store the metadata of the preset adapter to a second preset database under a micro-service scheduling framework, to realize registration of the preset adapter.

[0149] Specifically, a corresponding special adapter can be developed or configured for the inventory security device to be accessed (such as an old version of hardware DLP device). The adapter is deployed on an edge node or a special server close to the inventory security device, to ensure low-delay communication. The metadata of the adapter includes the capability description, input and output interfaces, resource requirement and performance index of the inventory security device it proxies. When the inventory security device executes timeout or fails, the adapter automatically retries ≤ 2 times (with an interval of 100 ms). If it still fails, an error code ‘ERR_LEGACY_DEVICE_FAIL’ is returned, and the scheduling engine is triggered to switch to a backup security capability (such as a software encryption micro-service). The calling mode of the adapter is completely consistent with calling the native micro-service (through a standard interface).

[0150] S205, determine the correlation index of the current power data.

[0151] The correlation index at least includes a data security level index, a business importance index, a circulation range index, a receiver trust level index, and an environment security index.

[0152] S206, performing a weighted sum operation on the indicators in the correlation indicators to obtain a risk value of the current power data under the current scenario.

[0153] wherein the importance of the power business corresponding to the current power data is positively correlated with the business importance indicator, the circulation range of the current power data is positively correlated with the circulation range indicator, the trust level of the recipient of the current power data is negatively correlated with the recipient trust level indicator, and the harshness of the environment safety of the current power data is positively correlated with the environment safety indicator.

[0154] For example, the data security level indicator can be directly mapped from a preset security level, such as the power industry data security classification requirement, and the indicator reflects the inherent security requirements of the data based on its content sensitivity and damage consequences. The business importance indicator can be determined according to the importance of the power business, such as dispatching instructions and user power consumption information, etc. The more important the business, the higher the risk indicator. The business importance indicator represents the value and influence in a specific business activity. The circulation range indicator can be determined according to the range of data circulation, such as cross-provincial circulation, cross-departmental circulation and internal circulation, etc. The wider the circulation range, the higher the potential exposure and loss of control, i.e. the higher the risk indicator. The recipient trust level indicator can be determined according to factors such as the recipient's security management level and historical security records. The lower the trust level, the higher the risk indicator. The environment safety indicator can be determined according to factors such as the current network security situation and attack frequency. The more severe the environment, the higher the risk indicator.

[0155] For example, each indicator needs to be quantitatively assigned, quantified as:

[0156] Data security level indicator and business importance indicator: extremely high / fourth level = 5, high / third level = 4, medium / second level = 3, low / first level = 2, extremely low = 1.

[0157] Circulation range indicator: cross-border / international = 5, cross-provincial circulation = 4, cross-city circulation = 3, cross-departmental circulation = 2, internal circulation = 1.

[0158] Recipient trust level indicator: extremely low trust = 5, low trust = 4, medium trust = 3, high trust = 2, extremely high trust = 1.

[0159] Environment safety indicator: extremely high risk = 5, high risk = 4, medium risk = 3, low risk = 2, extremely low risk = 1.

[0160] The risk value can be represented as:

[0161] Risk value = α × data security level indicator + β × business importance indicator + γ × circulation range indicator + δ × recipient trust level indicator + ε × environment safety indicator.

[0162] Wherein, a, b, g, d, e are the weight coefficients of each index, the value range is 0 to 1, and a+b+g+d+e=1.

[0163] Take the power data flow scenario as an example, the specific application is as follows:

[0164] 1) Cross-regional power grid data sharing scenario:

[0165] Data type: new energy power generation prediction data;

[0166] Basic data security level index: three (high);

[0167] Business importance: high;

[0168] Flow range: cross-provincial flow;

[0169] Recipient trust level: medium;

[0170] Security environment: the current network security situation is medium risk;

[0171] Weight distribution:

[0172] a=0.4, b=0.3, g=0.2, d=0.05, e=0.05;

[0173] Risk value calculation:

[0174] Risk value=0.4x4+0.3x4+0.2x5+0.05x3+0.05x3=4.1.

[0175] 2) Electricity business data sharing scenario:

[0176] Data type: user electricity data;

[0177] Basic data security level index: two (medium);

[0178] Business importance: medium;

[0179] Flow range: cross-departmental flow;

[0180] Recipient trust level: high;

[0181] Security environment: the current network security situation is low risk;

[0182] Risk value calculation:

[0183] Weight distribution:

[0184] a=0.35, b=0.25, g=0.2, d=0.15, e=0.05;

[0185] Risk value = 0.35x3 + 0.25x3 + 0.2x4 + 0.15x2 + 0.05x2 = 3.0.

[0186] S207, determine the security capability to be called from the security capability microservice according to the risk value.

[0187] Exemplarily, taking the power data flow scene under different risk levels as an example, the security capability to be called can be:

[0188] 1) High-risk scenario (risk value >= 4):

[0189] Security capability combination: DLP capability, encryption gateway capability, digital watermarking capability and access control capability;

[0190] Execution order: chain execution;

[0191] Execution parameters:

[0192] DLP capability: sensitive rule library version V3.0, recognition accuracy threshold 95%;

[0193] Encryption gateway capability: encryption algorithm SM4, key length 128 bits;

[0194] Digital watermarking capability: watermarking algorithm based on blockchain, watermarking strength medium;

[0195] Access control capability: role-based access control, principle of least privilege;

[0196] 2) Medium risk scenario (risk >= 3 and < 4):

[0197] Security capability combination: DLP capability, encryption gateway capability and access control capability;

[0198] Execution order: chain execution;

[0199] Execution parameters:

[0200] DLP capability: sensitive rule library version V2.0, recognition accuracy threshold 90%;

[0201] Encryption gateway capability: encryption algorithm AES-128, key length 128 bits;

[0202] Access control capability: attribute-based access control, dynamic authorization;

[0203] 3) Low-risk scenario (risk value < 3):

[0204] Security capability combination: DLP capability and access control capability;

[0205] Execution order: chain execution;

[0206] Execution parameters:

[0207] DLP capabilities: sensitive rule library version V1.0, identification accuracy threshold 85%;

[0208] Access control capabilities: identity-based access control, static authorization.

[0209] When there are multiple security capabilities to be called, the security capabilities to be called can be converted into an executable instruction sequence, and the execution order includes:

[0210] 1) Chain mode: security capabilities are executed in order, and the output of the previous security capability is the input of the next security capability.

[0211] 2) Parallel aggregation mode: multiple security capabilities are executed in parallel, each processing a different data part, and finally the results are combined.

[0212] 3) Branch mode: different security capability execution paths are selected according to condition judgment.

[0213] For security operations that require strong consistency, synchronous execution mode is adopted to ensure the consistency of security policies. For security operations that can be weakly consistent, asynchronous execution mode is adopted to improve system processing efficiency. A verification mechanism for designing security capability execution order is designed to ensure that the execution order of security policies meets expectations.

[0214] S208, generating a security capability scheduling instruction; with the minimum time delay cost and risk cost as the target, using an explicit analytic function and the real-time requirement of the security capability scheduling instruction and the current power data, determining the priority of different security capabilities to be called.

[0215] S209, when the system resource occupancy rate is greater than a preset threshold or the real-time requirement is a first real-time requirement, generating a first calling instruction of the security capability to be called; when the system resource occupancy rate is less than or equal to the preset threshold or the real-time requirement is a second real-time requirement, generating a second calling instruction of the security capability to be called.

[0216] Among them, the first calling instruction includes instructions for calling security capabilities to be called with a priority greater than a preset priority threshold, and the second calling instruction includes instructions for calling security capabilities to be called with a priority less than the preset priority threshold, and the first real-time requirement is higher than the second real-time requirement.

[0217] Specifically, the distribution of instructions supports distribution through RESTful API and message queues, etc., to ensure reliable transmission of instructions.

[0218] S210, converting the calling instruction into a target instruction recognizable by the security device through a preset adapter, and sending the target instruction to the security device.

[0219] The target instruction is used to instruct the security device to execute the to-be-called security capability on current power data.

[0220] S211, receiving standardized state information recognizable by the micro-service scheduling framework through the preset adapter.

[0221] The standardized state information is information obtained by converting state information of the security device executing the target instruction through the preset adapter.

[0222] Specifically, the preset adapter can also convert the original result (such as binary encrypted data and specific format log files) returned by the inventory security device into the standardized output format (such as the ciphertext field in JSON and structured log events) defined by the micro-service interface.

[0223] In order to realize the automatic processing and recovery of security capability execution exceptions and ensure the stability of the system, the state information that can be received through the preset adapter includes:

[0224] 1) the execution state of the security capability, including execution success, execution failure, execution timeout, etc.

[0225] 2) the execution state (success / failure / timeout) and performance indicators (latency, resource consumption) of the native micro-service;

[0226] 3) the execution state and performance indicators (resource consumption of the adapter itself, communication state with the inventory device) of the adapter;

[0227] 4) adapter state: when the adapter reports that the inventory device is unreachable, the instruction execution fails or returns an abnormal state, it is considered that the security capability execution fails, triggering the alarm and the fault switching / retry mechanism of the scheduling engine;

[0228] 5) record the execution log of the security capability, including input parameters, output results, execution time, etc.

[0229] The execution result of the security capability can be fed back as the basis for subsequent policy adjustment. The execution result is analyzed and evaluated, the combination strategy and execution order of the security capability are optimized, and a security audit report is generated, which provides a basis for compliance check.

[0230] For example, if the current scenario involves cross-provincial sharing of existing equipment, assuming that the power grid in Province A is still using a batch of older hardware encryption gateways (i.e., existing security equipment), the need to invoke encryption capabilities is determined based on the risk value. Considering the performance requirements of cross-regional transmission and the load of the encryption gateway, the capability identified as legacy-enc-gw-asa5500-001 (i.e., the hardware gateway accessed via an adapter) is determined to be invoked. The encryption command (including plaintext data, algorithm parameters, and key name) is sent to the adapter corresponding to this capability (deployed within Province A). The adapter receives the standardized command and connects to the management IP of the specified hardware encryption gateway via SSH / Telnet. It constructs and executes a hardware encryption gateway-specific CLI command (such as cryptoipsec encrypt...). The adapter monitors the command execution status, parses the encryption result or error information from the hardware encryption gateway output or logs, standardizes the result (ciphertext data or error code), and returns it.

[0231] The records returned by the adapter include:

[0232] Adapter call time (including network and hardware encryption gateway processing time).

[0233] The status returned by the adapter (success, returned in encrypted form).

[0234] The adapter itself consumes low resources.

[0235] S212. The actual load in the state information at the first moment and the ideal load at the second moment are weighted and summed to obtain the ideal load at the first moment, and the calling instruction is adjusted according to the ideal load at the first moment.

[0236] The first moment is later than the second moment.

[0237] The data security management method provided by the embodiment of the application abstracts security functions into callable security capability microservices, stores metadata, defines a unified interface, and realizes unified management and scheduling of security capabilities. Based on data security levels and factors such as trust of a receiver, a risk value of a circulation link is generated, providing a basis for dynamic scheduling of security capabilities. According to the risk value, a security capability combination is selected from a capability library, a scheduling instruction is generated, and the security capabilities are combined in a "modular" manner on demand and dynamically quantified in terms of risk, ensuring that the security protection matches the data value. By setting priorities for the security capabilities to be called, the "high real-time performance and dynamic risk" characteristics of power data are adapted, and the "security protection" and "circulation efficiency" are balanced. Finally, by using the collaborative architecture of the "old capability adaptation layer + new capability microservice layer", through the standardized adaptation layer, the heterogeneous and closed inventory security capabilities are transparently accessed to the unified scheduling framework, the old and new capabilities are "unconsciously" mixed and arranged, and the collaborative execution is realized, and the execution state is monitored, ensuring the collaborative execution of the security capabilities, avoiding repeated investment in hardware, accessing new security capabilities without interrupting the power business process, reducing the complexity and cost of system transformation, and achieving smooth iteration of the security protection system.

[0238] Embodiment three

[0239] Figure 3 A structural schematic diagram of a data security management device provided by the third embodiment of the application is shown in FIG. 3. Figure 3 As shown in the figure, the device comprises an evaluation module 301, an instruction generation module 302, an instruction sending module 303, and an information receiving module 304, wherein:

[0240] The evaluation module is configured to evaluate a risk value of current power data in a current scenario.

[0241] The instruction generation module is configured to determine a security capability to be called according to the risk value, and generate a calling instruction of the security capability to be called.

[0242] The instruction sending module is configured to convert the calling instruction into a target instruction recognizable by a security device through a preset adapter, and send the target instruction to the security device, wherein the target instruction is used to instruct the security device to execute the security capability to be called on the current power data.

[0243] The information receiving module is configured to receive state information of the security device executing the target instruction through the preset adapter.

[0244] The data security management device provided by the embodiment of the application accurately determines the to-be-called security capability according to the evaluated risk value, realizes dynamic risk quantification, ensures that the security protection matches the power data risk, and builds a collaborative architecture of new and old security capabilities, so that the existing security devices such as the encryption gateway of the deployed old security capability are converted into target instructions that can be recognized by the security devices through the adapter, and the seamless integration, smooth iteration and collaborative work of the old security capability and the new security capability are realized, and the transformation cost is reduced.

[0245] Optionally, the evaluation module comprises:

[0246] The association index determination unit is configured to determine an association index of the current power data, wherein the association index at least comprises a data security level index, a business importance index, a circulation range index, a receiver trust level index and an environment security index.

[0247] The risk value determination unit is configured to perform a weighted summation operation on the indexes in the association index to obtain a risk value of the current power data in the current scenario, wherein the importance of the power business corresponding to the current power data is positively correlated with the business importance index, the circulation range of the current power data is positively correlated with the circulation range index, the trust level of the receiver of the current power data is negatively correlated with the receiver trust level index, and the harshness of the environment security of the current power data is positively correlated with the environment security index.

[0248] Optionally, the device further comprises:

[0249] The scheduling framework construction module is configured to construct a micro-service scheduling framework before the security capability to be called is determined according to the risk value.

[0250] The first registration module is configured to abstract the security capability of the security device into a security capability micro-service in the micro-service scheduling framework, and store the metadata of the security capability to a first preset database under the micro-service scheduling framework, so as to realize the registration of the security capability micro-service.

[0251] The interface creation module is configured to create an associated interface of the security capability micro-service, wherein the associated interface at least comprises a security capability query interface, a security capability metadata update interface, a security capability deregistration interface, a security capability state monitoring interface, a security capability registration interface and a security capability calling interface.

[0252] The instruction generation module comprises:

[0253] The capability determination unit is configured to determine the security capability to be called from the security capability micro-service according to the risk value.

[0254] Optionally, the device further comprises:

[0255] a second registration module, configured to configure a preset adapter corresponding to each security device before the preset adapter converts the calling instruction into the target instruction recognizable by the security device, and store metadata of the preset adapter into a second preset database under the micro-service scheduling framework to realize registration of the preset adapter;

[0256] The information receiving module is specifically configured to receive standardized state information recognizable by the micro-service scheduling framework through the preset adapter, wherein the standardized state information is information obtained by converting state information of the security device executing the target instruction through the preset adapter.

[0257] Optionally, the apparatus further includes:

[0258] a first instruction generating module, configured to generate a security capability scheduling instruction before the calling instruction of the to-be-called security capability is generated;

[0259] a priority setting module, configured to set priorities for different to-be-called security capabilities according to real-time requirements of the security capability scheduling instruction and current power data;

[0260] The instruction generating module includes:

[0261] a second instruction generating unit, configured to generate the calling instruction of the to-be-called security capability according to the priorities, the real-time requirements and system resource occupancy.

[0262] Optionally, the generating the calling instruction of the to-be-called security capability according to the priorities, the real-time requirements and system resource occupancy includes: when the system resource occupancy is greater than a preset threshold or the real-time requirement is a first real-time requirement, generating a first calling instruction of the to-be-called security capability, wherein the first calling instruction includes an instruction of a to-be-called security capability with a calling priority greater than a preset priority threshold; and when the system resource occupancy is less than or equal to the preset threshold or the real-time requirement is a second real-time requirement, generating a second calling instruction of the to-be-called security capability, wherein the second calling instruction includes an instruction of a to-be-called security capability with a calling priority less than the preset priority threshold, and the first real-time requirement is higher than the second real-time requirement.

[0263] Optionally, the apparatus further includes:

[0264] The expected function construction module is configured to construct a time delay cost function and a risk cost function before setting priorities of different to-be-invoked security capabilities according to the real-time requirement of the security capability scheduling instruction and current power data, wherein the time delay cost function is used to determine a time delay cost of the to-be-invoked security capability under different priorities, and the risk cost function is used to determine a risk cost of the to-be-invoked security capability under different priorities.

[0265] The expected function construction module is configured to construct an expected function about the priority of the to-be-invoked security capability by using the time delay cost function and the risk cost function.

[0266] The explicit analytic function of the expected function is determined when the time delay cost function is a convex function and the risk cost function is a piecewise linear function, wherein the explicit analytic function contains a correlation between the priority of the to-be-invoked security capability and the risk value, a security capability scheduling instruction weight, a current load of the to-be-invoked security capability, a maximum load capacity of the to-be-invoked security capability, and a resource usage threshold of the to-be-invoked security capability, and the security capability scheduling instruction weight is determined according to the real-time requirement of the security capability scheduling instruction.

[0267] The priority setting module is specifically configured to determine the priorities of different to-be-invoked security capabilities by using the explicit analytic function and the real-time requirement of the security capability scheduling instruction and current power data, with the objective of minimizing the time delay cost and the risk cost.

[0268] Optionally, the apparatus further comprises:

[0269] The calling instruction adjustment module is configured to weight and sum an actual load in state information at a first time and an ideal load at a second time to obtain an ideal load at the first time, and adjust the calling instruction according to the ideal load at the first time after receiving state information of the security device executing the target instruction through the preset adapter, wherein the first time is later than the second time.

[0270] The data security management apparatus provided in the embodiments of the present application can execute the data security management method provided in any of the embodiments of the present application, and has the corresponding function modules and beneficial effects of the execution method.

[0271] Embodiment Four

[0272] Figure 4A structural diagram of an electronic device 40 that can be used to implement embodiments of the present application is shown. The electronic device is intended to represent various forms of digital computers, such as laptops, desktops, tablets, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device can also represent various forms of mobile devices, such as personal digital assistants, cellular telephones, smartphones, wearable devices (e.g., headsets, glasses, watches, etc.), and other similar computing devices. The components shown here, their connections and relationships, and their functions, are meant to be examples only, and are not meant to limit implementations of the present application described and / or claimed in this document.

[0273] As shown in Figure 4 The electronic device 40 includes at least one processor 41, and a memory, such as a read-only memory (ROM) 42, a random access memory (RAM) 43, etc., connected to the at least one processor 41 in communication, where the memory stores computer programs executable by the at least one processor. The processor 41 can perform various appropriate actions and processes according to the computer programs stored in the read-only memory (ROM) 42 or loaded from the storage unit 48 into the random access memory (RAM) 43. In the RAM 43, various programs and data required for the operation of the electronic device 40 can also be stored. The processor 41, the ROM 42, and the RAM 43 are connected to each other through a bus 44. An input / output (I / O) interface 45 is also connected to the bus 44.

[0274] Various components in the electronic device 40 are connected to the I / O interface 45, including an input unit 46, such as a keyboard, a mouse, etc., an output unit 47, such as various types of displays, speakers, etc., a storage unit 48, such as a magnetic disk, an optical disk, etc., and a communication unit 49, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 49 allows the electronic device 40 to exchange information / data with other devices through a computer network, such as the Internet, and / or various telecommunications networks.

[0275] The processor 41 can be various general and / or special purpose processing components with processing and computing capabilities. Some examples of the processor 41 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any appropriate processor, controller, microcontroller, etc. The processor 41 performs various methods and processes described above, such as the data security management method.

[0276] In some embodiments, the data security management method can be implemented as a computer program tangibly embodied in a computer readable storage medium, e.g., storage unit 48. In some embodiments, parts or all of the computer program can be loaded and / or installed onto electronic device 40 via, e.g., ROM 42 and / or communication unit 49. When the computer program is loaded onto RAM 43 and executed by processor 41, one or more steps of the data security management method described above can be performed. Alternatively, in other embodiments, processor 41 can be configured to perform the data security management method by way of other means, e.g., with the aid of firmware.

[0277] Various implementations of the systems and techniques described above can be realized in digital electronic circuitry, integrated circuitry, a system on a chip, a complex programmable logic device (CPLD), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), a system level chip (SOC), a computer hardware, firmware, software, and / or combinations thereof. These various implementations can include implementation in one or more computer programs that are executable and / or interpretable on a programmable system including at least one programmable processor, which can be special or general purpose, coupled to receive data and instructions from, and to transmit data and instructions to, a storage system, at least one input device, and at least one output device.

[0278] Computer programs used to implement the methods of the application can be written in any combination of one or more programming languages. These computer programs can be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the computer program, when executed by the processor of the machine, implements the functions / acts specified in the flow diagrams and / or block diagrams. The computer program can be executed entirely on a machine, partially on a machine and partially on a remote machine or entirely on a remote machine or server.

[0279] The computer device provided above can be used to execute the data security management method provided by any of the embodiments above, and has the corresponding functions and advantages.

[0280] Embodiment Five

[0281] In the context of the present application, the computer readable storage medium can be a tangible medium, the computer executable instructions of which, when executed by a computer processor, serve to perform a data security management method, the method comprising:

[0282] evaluating a risk value of the current power data under the current scenario;

[0283] determining a security capability to be invoked according to the risk value, and generating an invocation instruction of the security capability to be invoked;

[0284] converting the invocation instruction into a target instruction recognizable by a security device through a preset adapter, and sending the target instruction to the security device, wherein the target instruction is used to instruct the security device to execute the security capability to be invoked on current power data;

[0285] receiving, by the preset adapter, state information of the security device executing the target instruction.

[0286] In the context of the present application, a computer-readable storage medium can be a tangible medium which can contain or store a computer program for use by or in connection with an instruction execution system, apparatus, or device. The computer-readable storage medium can include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. Alternatively, the computer-readable storage medium can be a machine-readable signal medium. More specific examples of the machine-readable storage medium will include one or more wires, portable computer disks, hard disk drives, random access memories (RAM), read-only memories (ROM), erasable programmable read-only memories (EPROM or flash memory), optical fibers, portable compact disc read-only memories (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0287] The computer device provided above can be used to execute the data security management method provided by any of the embodiments above, and has the corresponding functions and advantages.

[0288] It is worth noting that the above-mentioned embodiments of the data security management device include various units and modules, which are only divided according to the functional logic, but are not limited to the above-mentioned division, as long as the corresponding functions can be realized; in addition, the specific names of each functional unit are only for the convenience of mutual differentiation, and do not limit the protection scope of the present application.

[0289] Note that the above merely describes preferred embodiments of the present application and the principles of the technology applied. Those skilled in the art will understand that the present application is not limited to the specific embodiments described herein, and that various obvious changes, modifications and substitutions can be made without departing from the scope of the present application. Therefore, although the present application has been described in detail through the above embodiments, the present application is not limited to the above embodiments, and can include more other equivalent embodiments without departing from the concept of the present application, and the scope of the present application is determined by the scope of the claims.

Claims

1. A data security management method, characterized in that, include: Assess the risk value of current power data in the current scenario; The security capabilities to be invoked are determined based on the risk value, and an invocation instruction for the security capabilities to be invoked is generated. The invocation instruction is converted into a target instruction that can be recognized by the security device through a preset adapter, and the target instruction is sent to the security device, wherein the target instruction is used to instruct the security device to execute the security capability to be invoked on the current power data; The system receives status information about the security device executing the target instruction via the preset adapter. The assessment of the risk value of the current power data in the current scenario includes: Determine the relevant indicators for the current power data, wherein the relevant indicators include at least data security level indicators, business importance indicators, circulation scope indicators, recipient trust level indicators, and environmental security indicators; The indicators in the related indicators are weighted and summed to obtain the risk value of the current power data in the current scenario; Among them, the importance of the power business corresponding to the current power data is positively correlated with the business importance index, the circulation scope of the current power data is positively correlated with the circulation scope index, the trust level of the recipient of the current power data is negatively correlated with the recipient trust level index, and the environmental security severity of the current power data is positively correlated with the environmental security index.

2. The method according to claim 1, characterized in that, Before determining the security capability to be invoked based on the risk value, the method further includes: Build a microservice scheduling framework; The security capabilities of security devices are abstracted into security capability microservices in the microservice scheduling framework, and the metadata of the security capabilities is stored in the first preset database under the microservice scheduling framework to realize the registration of the security capability microservices. Create associated interfaces for the security capability microservice, wherein the associated interfaces include at least a security capability query interface, a security capability metadata update interface, a security capability deregistration interface, a security capability status monitoring interface, a security capability registration interface, and a security capability invocation interface; The step of determining the security capability to be invoked based on the risk value includes: The security capabilities to be invoked are determined from the security capability microservices based on the risk value.

3. The method according to claim 1 or 2, characterized in that, Before converting the invocation instruction into a target instruction recognizable by the security device via a preset adapter, the method further includes: Configure a preset adapter for each security device and store the metadata of the preset adapter in a second preset database under the microservice scheduling framework to realize the registration of the preset adapter; The status information received via the preset adapter regarding the execution of the target instruction by the security device includes: The preset adapter receives standardized status information that can be recognized by the microservice scheduling framework, wherein the standardized status information is the information obtained after the security device executes the target instruction and the status information is transformed by the preset adapter.

4. The method according to claim 1, characterized in that, Before generating the invocation instruction for the security capability to be invoked, the method further includes: Generate security capability scheduling instructions; Based on the real-time requirements of the security capability scheduling instructions and current power data, priorities are set for different security capabilities to be called. The step of generating the invocation instruction for the security capability to be invoked includes: Based on the priority, the real-time requirements, and the system resource utilization rate, a call instruction for the security capability to be invoked is generated.

5. The method according to claim 4, characterized in that, The step of generating the invocation instruction for the security capability to be invoked based on the priority, the real-time requirements, and the system resource utilization rate includes: When the system resource utilization rate is greater than a preset threshold or the real-time requirement is the first real-time requirement, a first call instruction for the security capability to be called is generated, wherein the first call instruction includes an instruction to call a security capability to be called with a priority greater than a preset priority threshold. When the system resource utilization rate is less than or equal to the preset threshold or the real-time requirement is the second real-time requirement, a second invocation instruction for the security capability to be invoked is generated. The second invocation instruction includes an instruction to invoke a security capability to be invoked with a priority lower than the preset priority threshold, and the first real-time requirement is higher than the second real-time requirement.

6. The method according to claim 4, characterized in that, Before setting priorities for different security capabilities to be called based on the real-time requirements of the security capability scheduling instructions and current power data, the method further includes: Construct a latency cost function and a risk cost function, wherein the latency cost function is used to determine the latency cost under different priorities of the security capability to be invoked, and the risk cost function is used to determine the risk cost under different priorities of the security capability to be invoked; An expectation function regarding the priority of the security capabilities to be invoked is constructed using the latency cost function and the risk cost function; When the latency cost function is a convex function and the risk cost function is a piecewise linear function, an explicit analytical function of the expected function is determined. The explicit analytical function contains the correlation between the priority of the security capability to be invoked and the risk value, the weight of the security capability scheduling instruction, the current load of the security capability to be invoked, the maximum load capacity of the security capability to be invoked, and the resource usage threshold of the security capability to be invoked. The weight of the security capability scheduling instruction is determined according to the real-time requirements of the security capability scheduling instruction. The step of setting priorities for different security capabilities to be invoked based on the real-time requirements of the security capability scheduling instructions and current power data includes: With the goal of minimizing delay and risk costs, the priority of different security capabilities to be invoked is determined by using the explicit analytical function and the real-time requirements of the security capability scheduling instructions and current power data.

7. The method according to claim 1, characterized in that, After receiving the status information of the security device executing the target instruction via the preset adapter, the method further includes: The actual load in the state information at the first moment and the ideal load at the second moment are weighted and summed to obtain the ideal load at the first moment, and the calling instruction is adjusted according to the ideal load at the first moment, wherein the first moment is later than the second moment.

8. A data security management device, characterized in that, include: The assessment module is used to evaluate the risk value of the current power data in the current scenario; The instruction generation module is used to determine the security capability to be invoked based on the risk value, and generate an invocation instruction for the security capability to be invoked; The instruction sending module is used to convert the calling instruction into a target instruction that can be recognized by the security device through a preset adapter, and send the target instruction to the security device, wherein the target instruction is used to instruct the security device to execute the security capability to be invoked on the current power data; The information receiving module is used to receive status information of the security device executing the target instruction through the preset adapter; The evaluation module includes: The correlation indicator determination unit is used to determine the correlation indicators of the current power data, wherein the correlation indicators include at least data security level indicators, business importance indicators, circulation scope indicators, recipient trust level indicators, and environmental security indicators. The risk value determination unit is used to perform a weighted summation operation on the indicators in the associated indicators to obtain the risk value of the current power data in the current scenario; wherein, the importance of the power business corresponding to the current power data is positively correlated with the business importance indicator, the circulation scope of the current power data is positively correlated with the circulation scope indicator, the trust level of the recipient of the current power data is negatively correlated with the recipient trust level indicator, and the environmental security severity of the current power data is positively correlated with the environmental security indicator.

9. An electronic device, characterized in that, The electronic device includes: At least one processor; and A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform the data security management method according to any one of claims 1-7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that cause a processor to execute the data security management method according to any one of claims 1-7.

Images