A unified framework, method, and storage medium for fulfilling security obligations across multiple interfaces.

By adopting the same set of obligations, cryptographic resources, and evidence specifications across multiple data interfaces, the problem of inconsistent data protection strategies is solved, achieving unified protection and compliance verification across interfaces, and simplifying component modification and key management.

CN123122897APending Publication Date: 2026-11-17BEIJING ZIXINDA INFORMATION TECHNOLOGY CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611263786.5
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-08-19
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

In existing technologies, the lack of a unified protection framework for various data interfaces leads to inconsistent policies, fragmented key management, and different log formats, making it impossible to achieve complete protection and compliance verification of the same data object on different interfaces.

Method used

By using the same set of obligations as the source of the strategy, the same cryptographic resources for computation, and the same evidence standards for recording, unified protection and evidence association of multiple boundaries can be achieved.

Benefits of technology

It achieves consistency and verifiability of multi-type boundary protection, reduces the expansion of security boundaries, and eliminates the need to modify existing components when adding new boundaries, with centralized key management.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123122897A_ABST
    Figure CN123122897A_ABST
Patent Text Reader

Abstract

This invention discloses a unified security obligation fulfillment framework, method, and storage medium with multiple interfaces, relating to the field of information security technology. The method includes: receiving and verifying the signature of obligation policy packets grouped according to trigger boundaries; initializing execution components of various boundaries (network, storage, database, file, terminal) with a unified policy mode and unified evidence specification; after any boundary execution component intercepts the data stream, it identifies the data object and data state and matches the obligation, routes the execution request to the corresponding boundary executor, and invokes unified cryptographic resources to complete the security function on behalf of the application; and generates an evidence record containing an obligation identifier according to the unified evidence specification. This invention unifies previously independent single-point transparent protection technologies under a single obligation-driven framework, allowing multiple boundaries to share the obligation source, cryptographic resources, and evidence specification, thereby achieving consistent and verifiable security capabilities across boundaries while maintaining zero application modification.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the field of information security technology, and in particular to a multi-interface unified security obligation fulfillment framework, method, and computer-readable storage medium. Background Technology

[0002] Transparent data encryption, transport layer proxy encryption, and transparent file encryption are single-point transparent protection technologies that can apply protection without modification to a single interface such as a database, network, or file. However, these technologies operate independently: each has its own independent policy configuration source, independent key management, and independent log format, resulting in a lack of a unified framework between different interfaces such as networks, storage, databases, and terminals.

[0003] The consequences are as follows: the same data object is protected by different products with different policies on different interfaces, and there is no guarantee of consistency between the policies; keys are managed in a decentralized manner, expanding the security boundary; log formats vary, making it impossible to form unified evidence that can be linked to compliance requirements. In addition, the protection actions of each single point technology are determined by static configuration rather than driven by compliance obligations, making it impossible to prove that the same data object has received consistent and complete protection on all interfaces it passes through. Summary of the Invention

[0004] The technical problem to be solved by this invention is to provide a framework and method for unifying the protection of multiple types of data interfaces without modification under the same obligation-driven framework, so that multiple boundaries can share the source of obligations, cryptographic resources and evidence specifications.

[0005] The concept of this invention is to use the same set of obligations as the common policy source for all boundary execution components, the same cryptographic resources as the common computation and key services for all boundaries, and the same evidence standard as the common structure for all boundary evidence records, so that the protection of different interfaces becomes a consistent projection of the same compliance obligation on different trigger boundaries.

[0006] To address the aforementioned technical problems, this invention provides the framework, method, and storage medium as described in the claims. The beneficial effects of this invention include: protection of multiple boundaries is driven by the same set of obligations, operated on by the same cryptographic resources, and presented according to the same evidence standard, ensuring the consistency and verifiability of cross-boundary protection for the same data object; adding new boundaries only requires issuing corresponding policies without modifying existing components and applications; key centralization and convergence lead to a contraction of security boundaries. Attached Figure Description

[0007] Figure 1 This is a flowchart illustrating the substitute performance method provided in an embodiment of the present invention.

[0008] Figure 2 This is a schematic diagram of the structure of the multi-interface unified proxy framework provided in the embodiments of the present invention. Detailed Implementation

[0009] The embodiments of the present invention will be further described below with reference to the accompanying drawings.

[0010] like Figure 2 As shown, the multi-interface unified execution framework 400 includes a policy distribution unit 401, multiple types of boundary execution components, a unified cryptographic resource 407, and a unified evidence specification unit 408. The boundary execution components include at least two of the following: network boundary execution components, storage boundary execution components, database boundary execution components, file boundary execution components, and terminal presentation boundary execution components. Each execution component is configured with a unified policy interpretation mode and evidence specification.

[0011] like Figure 1 As shown, the method includes steps S401 to S405. Step S401: The policy distribution unit receives and verifies the signature of obligation policy packets grouped by trigger boundaries; the policy packet is compiled from an obligation set with elements of (security function, data object, data state, trigger boundary). Step S402: Each boundary execution component initializes with a unified policy mode and unified evidence specification. Step S403: Any boundary execution component intercepts the data stream, identifies the data object and data state, and matches the obligations. Step S404: The execution request is routed to the corresponding boundary executor according to the matched obligation, and the unified cryptographic resource 407 is invoked to perform the security function on behalf of the application system. Step S405: An evidence record containing an obligation identifier is generated according to the unified evidence specification and reported to the same evidence chain.

[0012] Example: A data object, during its lifecycle, is first transmitted through the network boundary, then written to disk through the database boundary, and finally exported through the file boundary. The execution components at these three boundaries obtain the transmission confidentiality, storage confidentiality, and file storage confidentiality obligations for the object from the same set of obligations, respectively, and encrypt them using the same cryptographic resource, generating structurally consistent and mutually correlated evidence. When an organization adds a non-repudiation requirement for the terminal presentation boundary, it only needs to issue the corresponding policy to the terminal presentation boundary execution component; existing network, database, and file execution components, as well as all application systems, do not require modification.

[0013] This framework requires zero code and zero configuration changes to the served application system; the modification only involves the deployment of boundary execution components and policy distribution. The above description is merely a preferred embodiment of the present invention. All equivalent substitutions and improvements made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.

Claims

1. A unified, multi-interface framework for fulfilling security obligations, characterized in that, include: The policy distribution unit receives obligation policy packets grouped by trigger boundaries and distributes them to each boundary execution component; The execution components are deployed at at least two types of trigger boundaries. Each execution component is configured with a unified policy interpretation mode and a unified evidence specification. It is used to intercept the data flow, identify its data objects and data states, match obligations, and call unified cryptographic resources to replace the application system to complete the corresponding security functions, and return the results with semantics consistent with the original interface. The unified cryptographic resources provide cryptographic operations and key services for each boundary execution component. The unified evidence specification unit specifies the unified structure of the evidence records generated by each boundary execution component. The at least two types of trigger boundaries include at least two of the following: network boundary, storage boundary, database boundary, file boundary, and terminal presentation boundary.

2. The framework according to claim 1, characterized in that, The obligation policy package is compiled from a set of obligations consisting of security functions, data objects, data states, and trigger boundaries. The same set of obligations drives all boundary execution components.

3. The framework according to claim 1, characterized in that, Each boundary execution component generates an evidence record containing an obligation identifier, a data object identifier, an execution action, an execution result, and the execution component's signature, and these are written into the same evidence chain.

4. The framework according to claim 1, characterized in that, The unified cryptographic resource centrally provides domestic cryptographic algorithm operations, and each boundary execution component does not store its own key.

5. The framework according to claim 1, characterized in that, The policy of any boundary execution component is loaded in the form of a cryptographically signed policy package, and the loading receipt is added to the evidence chain.

6. The framework according to claim 1, characterized in that, When a task fails to be performed, each boundary execution component is handled according to a unified failure semantic classification and evidence records are generated.

7. The framework according to claim 1, characterized in that, The routing is executed with trigger boundary type and security function as the two keys, and multiple obligations triggered by the same data flow are routed to the corresponding executors respectively.

8. The framework according to claim 1, characterized in that, Each boundary execution component periodically reports its health status to the unified monitoring system. If any component malfunctions, the execution level of its assigned task is adjusted to a more conservative direction.

9. The framework according to claim 1, characterized in that, The new boundary execution component is registered and certified to access the framework. After access, the policy distribution unit issues corresponding policy groups according to its boundary type.

10. A method for substitute performance of security obligations based on the framework of claim 1, characterized in that, include: Receive and verify the loading of the obligation policy package grouped by trigger boundary; each boundary execution component initializes with a unified policy mode and evidence specification; intercepts the data stream and identifies the data object and data state to match the obligation; routes the execution request to the corresponding boundary executor and invokes the unified cryptographic resource to perform the obligation; generates evidence records containing obligation identifiers according to the unified evidence specification and reports them.

11. The method according to claim 10, characterized in that, When a new type of trigger boundary is added, the framework is extended by issuing the corresponding group's obligation policy package, without having to change the existing boundary execution components and the application systems being served.

12. The framework according to claim 1, characterized in that, The framework requires zero code and zero configuration changes to the application systems it serves.

13. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the method of claim 10 or 11.