CN-122023039-A - Financial data security management method and system

CN122023039ACN 122023039 ACN122023039 ACN 122023039ACN-122023039-A

Abstract

The invention relates to the technical field of financial information security, in particular to a financial data security management method and system. The method takes a safe bill as a core, generates the bill by responding to high-sensitivity operation, performs pre-triple verification, dynamically verifies compliance of an operation sequence, triggers safety confirmation of bill binding according to requirements, links and handles abnormal states, and automatically clears authority and consolidates export files after the life cycle of the bill is finished. The system comprises a security bill generating module, a prepositive verification engine, a behavior compliance analyzer, a security confirmation agent, a state linkage controller and a life cycle management unit. The invention provides a financial data security management method and system, and aims to solve the problem that high-sensitivity operation risks are uncontrollable caused by permission control and behavior monitoring cutting, security intervention and audit tracing and disjointing.

Inventors

SHI JING
SHI JING
FAN KE
YAN RUI
SONG BAOHONG
BAI LEI

Assignees

河南建筑职业技术学院
郑州大学

Dates

Publication Date: 20260512
Application Date: 20260126

Claims (10)

1. A financial data security management method, comprising the steps of: responding to a high-sensitivity operation request, generating or multiplexing a security bill and binding the high-sensitivity operation request with the security bill; Executing three legality checks of a user, an operation type and a data range based on the security bill; starting operation sequence compliance dynamic verification, and detecting illegal behaviors according to the embedded behavior rules of the security bill; triggering a safety confirmation process bound with the safety bill as required, and verifying the consistency of the bill identifier in the confirmation response; when the security bill state is changed into abnormal behavior or abnormal confirmation, executing state linkage treatment; And after the life cycle of the security bill is finished, the session binding is released, the temporary permission is recovered, and watermark injection and encryption reinforcement are carried out on the related export file.
2. The method of claim 1, wherein the security ticket comprises a unique ticket identifier, a list of authorized users, a set of allowed operations, a target data range, a validity period, a current state, an anomaly counter, and an audit field, the current state value comprising activation, behavioral anomalies, validation anomalies, completed or failed; The high sensitivity operation includes at least one of deriving all customer data, modifying bank account information, deleting a credential record.
3. A financial data security management method according to claim 1, wherein in the step of responding to the request for a hypersensitive operation, if a security ticket exists in a valid state for the current session and the authorized range covers the current operation, the security ticket is multiplexed, and otherwise a new security ticket is created.
4. The financial data security management method of claim 1, wherein the three validity checks are specifically checking whether a current user is in an authorized user list of the security ticket, whether a current operation type is in an allowed operation set, and whether a data object related to the current operation falls within a target data range.
5. The financial data security management method of claim 1, wherein the embedded behavior rules include an operational sequence constraint that prohibits simultaneous occurrence of query blacklist and batch export during the same security ticket lifecycle, and that a large transfer must be performed after balance verification is completed.
6. The financial data security management method of claim 1, wherein the on-demand triggering of the security validation process in which the validation request includes a security ticket identifier, a type of operation, a destination data identification, a device fingerprint, and a timestamp, and is transmitted via end-to-end encryption, includes operations involving a full amount of data export or funds change, the current terminal device not being registered in the trusted device list.
7. The financial data security management method of claim 1, wherein the state linkage handling comprises temporarily disabling write rights of a current session to sensitive financial data, superimposing an irremovable identity watermark on a user interface, appending an exception event record in an audit field of the security ticket, updating the security ticket state to spent when an exception counter reaches a threshold, the encryption reinforcement specifically applying an enterprise-level encryption lock to an unencrypted associated export file.
8. A financial data security management system, comprising: the security bill generation module is used for responding to the high-sensitivity operation request to generate or multiplex security bills and establishing the binding relation between the operation and the bills; The front-end verification engine is used for executing three legality verifications of a user, an operation type and a data range; a behavior compliance analyzer for dynamically verifying compliance of the sequence of operations; The security confirmation agent is used for triggering a security confirmation process bound with the bill according to the requirement; the state linkage controller is used for executing linkage treatment when the bill state is abnormal; and the life cycle management unit is used for executing automatic cleaning operation after the bill life cycle is finished.
9. The financial data security management system of claim 8, wherein the pre-verification engine communicates with the behavioral compliance analyzer via a shared memory buffer, the pre-verification engine writing the verification results to the shared memory buffer in the form of status flags, the behavioral compliance analyzer initiating a sequence analysis task only if the status flags indicate verification passes.
10. The financial data security management system of claim 8, wherein the lifecycle management unit invokes a distributed file system interface to perform a file scanning task and invokes an enterprise key management system through an encryption service middleware to complete a file encryption lock application operation, and wherein the security ticket creation, modification, querying, and destruction operations are protected by an operating system level access control policy.

Description

Financial data security management method and system Technical Field The invention relates to the technical field of financial information security, in particular to a financial data security management method and system. Background In the context of the current rapid development of digital economics, financial data has become a critical carrier for enterprise core assets and regulatory compliance, and its security has become a serious issue in information system construction. Therefore, a security audit system which can support refinement, traceability and strong controllability is introduced into a service system with high aging requirements, and the normal operation of a modern financial system can be ensured. Most of the current financial data security prevention and control systems adopt role-based access control or task-based temporary authorization management, and aim to prevent users from unauthorized access to sensitive data by defining clear authority boundaries. Generally, after the user passes the authentication, the financial system grants corresponding data read-write permission and starts an audit function module (such as audit log, post-accountability, etc.) according to the organization role the user belongs to or the business task born. And then the system grants necessary data read-write authority according to the organization role the user belongs to or the task born after the user authentication is passed. If the user is assigned with the accounting authority of a certain client, the system only opens the inquiry and read-write authority of the user to the client data, and records the operation behavior of the user through an auditing module. In the application scene at the time, the scheme effectively solves the problem of coarse-granularity unauthorized access, and improves the standardization and maintainability of authority management. For example, a financial staff is given the accounting authority of a customer, and the system only opens the relevant data inquiry and read-write interface of the customer to the staff, so that the minimum authority principle is realized at the static level. However, with the exponential growth of enterprise data size, remote office normalization, and frequent internal threat events, the above architecture has a fundamental logical contradiction in principle that 1. Rights granting and behavioral auditing are independent chains, and any reasonable rights risk being unreasonably used. Although the system has previously specified that data from client a is allowed to be exported, after the rights are validated, the user can use the rights to export data from the entire library in batches in a concealed manner, resulting in theft of the asset. 2. The safety blocking measure is not linked with the audit link, and a closed loop cannot be formed. After the attacker or the inside ghost bypasses the identity authentication, the data are stolen by utilizing the permission, the system blocks the behavior after detecting the abnormality, and the event is finally recorded by the auditing system, but the auditing result does not comprise the action details executed by the permission, so that the attacker or the inside ghost cannot prove that the attacker or the inside ghost steals all the data; in addition, after blocking, the rights are not recovered, the residual risk still exists, and when the historical record is audited and called, the process that the rights are stolen cannot be restored. The root cause of the contradiction is that the prior proposal considers the authority as an irreversible and one-time granted effective certificate, and can not set a life cycle, state perception and abnormal trigger mechanism for the authority, thus being incapable of meeting the requirements of behavior compliance verification and state compliance verification under a highly sensitive operation scene. Worse still, the above-mentioned inadequacies result in the enterprise requiring additional behavioral analysis engines or manual checks to cover the blind spot, which both reduces the effectiveness of the system and invalidates delayed interventions, and because the event and privilege credentials do not match, the security team has to laboriously splice among multiple unconnected systems while conducting the follow-up investigation, greatly reducing audit efficiency, and making it difficult for critical context loss to determine responsibility. Compliance issues for industry (e.g., financial and medical) organizations involving cross-border data flow or strict supervision have become a major source. Therefore, how to construct a novel security mechanism capable of fusing authority control, operation verification, security intervention and audit trail depth under the architecture of the existing financial system, and to realize transition from static authorization to dynamic compliance, has become a key challenge and a technical problem to be solved in the current face of