Salary payment system and method based on data security management

Abstract

The invention discloses a salary payment system and method based on data security management, and relates to the technical field of enterprise salary management and data security, and the system comprises a data collection and encryption module which uses AES-256 to encrypt salary basic data, transmits the data through SSL / TLS, and verifies the data integrity; the salary calculation module performs calculation according to preset logic after decrypting the data, and starts triple verification; the permission management module divides four types of role distribution permissions according to an RBAC model; the secure storage module stores data through double encryption and needs multi-factor authentication access; the issuing execution module supports three issuing channels and sends issuing notifications; the audit tracing module records an operation log by using a block chain; the central control module coordinates all the modules and manages secret keys and early warning. According to the method, data security is guaranteed through multi-layer encryption and dynamic desensitization, and efficiency is improved through automatic calculation; the disaster recovery backup ensures service continuity, adapts to different scales of enterprises, and improves the salary management safety and efficiency.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of enterprise salary management and data security, and particularly relates to a salary payment system and method based on data security management. BACKGROUND

[0002] The current enterprise salary payment system has multiple dimensional short boards in data security management, and the core problem is concentrated in the insufficient security protection of data collection and transmission links. Most systems only use a single encryption algorithm to process the salary basic data, and do not establish a data integrity verification mechanism. During the transmission of data from the attendance system, the performance platform to the salary calculation module, data tampering and loss may occur due to network attacks or transmission interruptions, and the tampering behavior is difficult to be discovered in time. For example, part of the salary system of small and medium-sized enterprises directly transmits the unencrypted bank account number and salary details of employees through the HTTP protocol, which has the risk of data leakage after interception, and lacks abnormal transmission monitoring, which cannot identify high-frequency and abnormal IP address data access requests, further amplifying the data security risks.

[0003] The lack of refinement of permission management and sensitive data protection is another core defect of the existing system. Traditional salary systems mostly use a simple "account-password" authentication mode, without clearly dividing the permission boundaries based on roles. In some scenarios, the salary accountants can view the complete salary details of employees in other departments, and the financial payers can modify the confirmed salary calculation results, with a high risk of abuse of authority. At the same time, the sensitive data desensitization processing method is fixed, such as using a fixed character replacement rule for employee ID numbers and bank account numbers, without dynamically adjusting the desensitization degree according to the access role. When an employee views his / her own information, he / she still needs to apply for the complete data, which affects the user experience, while external auditors may access the sensitive information that is not sufficiently desensitized when they access, leading to an out-of-control exposure range of data. In addition, the lack of full-process recording of permission changes makes it difficult to trace the responsible person when there is an abuse of authority, further reducing the controllability of the system.

[0004] Audit traceability and business continuity guarantee capability are weak, which restricts the reliability of the existing system. The operation log of most systems only records the basic operator and operation time, without including data access track and operation result verification information, and the log is stored in a single local server, which may be deleted or tampered with by humans, and cannot form an unalterable audit link. In terms of data storage and disaster recovery, some systems do not deploy off-site backup mechanisms, but only rely on local hard disk to store salary data. Once a hardware failure, natural disaster or other sudden situation occurs, the data cannot be recovered quickly after loss, leading to the interruption of the salary payment process. Even a few systems that deploy backups also have problems such as long backup period and lack of backup data integrity verification, which cannot guarantee the availability of backup data, and further affect the timeliness of enterprise salary payment, and harm the rights and interests of employees and the reputation of enterprises. SUMMARY

[0005] The present application provides a salary payment system and method based on data security management to solve the above-mentioned problems in the prior art.

[0006] To achieve the above object, the present application adopts the following technical scheme: a salary payment system based on data security management, comprising the following modules: A data acquisition and encryption module acquires basic data required for salary calculation, uses an AES-256 encryption algorithm to encrypt the original data during the acquisition process, and transmits the encrypted data to the subsequent module through an SSL / TLS protocol, while verifying the integrity of the collected data through a hash value comparison; A salary calculation module receives encrypted basic data, applies for a decryption key to the central control module and completes decryption, performs salary calculation according to a preset salary calculation logic, starts a three-way verification mechanism after generating preliminary salary details, and returns an abnormal prompt and suspends the calculation process if the verification fails; A permission management module divides system users into four core roles of administrator, salary accountant, financial distributor, and employee inquirer, each role corresponding to exclusive operation permissions, the permission allocation adopting a role-based access control model, and the permission change log being recorded synchronously; A secure storage module is used to store encrypted basic data, salary calculation results, permission configuration information, and audit logs, the storage medium adopting an encrypted hard disk, the stored data being double-encrypted, and an access control strategy being set to allow only authorized roles to access the corresponding data after multi-factor authentication, and unauthorized access triggering an alarm; A payment execution module is used to execute salary payment operations, supports three payment channels of bank transfer, electronic wallet payment, and paper check, completes permission verification of the financial distributor through the central control module before payment, sends a notification containing the payment amount, payment time, and query link to the employee during the payment process, receives feedback results from the payment channel after the payment is completed, and stores the encrypted feedback results in the secure storage module; An audit tracing module is used to record all operation behaviors in the system, records are stored using blockchain technology, and logs can be queried by operation person, operation time, and operation type, and the query results can only be viewed by administrators and auditors, and the query process records logs synchronously; A central control module receives state feedback from each module, performs early warning on abnormal states, manages system keys, and maintains system basic parameters.

[0007] Further, it also includes a data desensitization module. The sensitive data includes employee ID number, bank account number, and complete salary details that are not for personal viewing. The desensitization rules cover partial character replacement, data format conversion, dynamic desensitization, and dynamic adjustment of desensitization strategies according to the type of sensitive data and access scenarios. When abnormal access frequency of sensitive data is detected, the desensitization level is dynamically improved to control the exposure range of sensitive data.

[0008] Further, it also includes an abnormality monitoring module for monitoring data operation abnormalities and salary payment abnormalities in the system. During the abnormality monitoring process, the abnormal risk value is quantified by the formula R = a x D + b x T + g x F, where R is the abnormal risk value, a is the data operation abnormality weight, D is the data operation abnormality degree, b is the salary payment abnormality weight, T is the salary payment abnormality degree, g is the historical abnormality correlation weight, and F is the historical abnormality correlation degree. The abnormality level is determined by the quantification result, and corresponding processing measures are triggered according to the level.

[0009] Further, the permission management module also supports dynamic permission adjustment function. When the system detects changes in user operation scenarios, the administrator initiates a temporary permission adjustment application. After the application is submitted and approved by the auditor, it takes effect. The validity period of temporary permission is no more than 72 hours, and the original permission is automatically restored after the validity period ends. The whole process of application, review, effectiveness, and invalidity of temporary permission is recorded in the audit log. In addition, the permission management module regularly checks the compliance of all user permissions, and non-compliant permissions are automatically frozen and notified to the administrator.

[0010] Further, the security storage module adopts a dual storage architecture of "local encrypted storage + off-site disaster recovery backup". Local storage is used for daily data access, and RAID5 disk array is used to realize hardware-level data reliability. Off-site disaster recovery backup is deployed in the backup center. The backup data is synchronized with the local storage data in real time. The synchronization process uses IPsec protocol for encrypted transmission. The off-site backup center uses the same access control strategy as the local one. In addition, the security storage module performs life cycle management on the stored data. The retention period of basic data is 3 years, and the retention period of salary calculation results and payment records is 10 years. Data exceeding the retention period is deleted by administrators after being audited and supervised by auditors. The deletion process is recorded in the audit log.

[0011] Further, the payment execution module also has a payment result secondary verification function. After the payment is completed, the system automatically sends a confirmation notification containing a random verification code to the employee. The employee needs to input the verification code through the system query interface within 24 hours to complete the payment confirmation. If the employee does not confirm on time, the system will send a reminder notification again after 12 hours. If the employee still does not confirm after 48 hours, the payment execution module triggers an abnormal warning and suspends the employee's next salary payment until the confirmation is completed. In addition, the payment execution module also supports the salary payment revocation function. When an error is found in the payment and the payment channel supports revocation, the financial payment staff initiates a revocation application. The revocation operation is executed within 2 hours after the payment is completed. If it exceeds 2 hours, it needs to be handled through manual intervention. The revocation process and results are recorded in the audit log.

[0012] Further, the audit tracing module also has a log analysis and risk warning function. It performs multi-dimensional analysis on the audit log, and the analysis results generate an audit report. The report identifies high-frequency operation roles, abnormal operation time periods, and high-risk operation types, providing data support for administrators to optimize permission configuration and adjust security strategies. In addition, the audit log uses tamper-proof storage technology. Administrators and auditors can only view the log and cannot modify or delete it.

[0013] Further, the following steps are included: Data collection and encryption step, collect employee attendance data, performance data, social security fund contribution standard, individual tax deduction rules, employee salary structure data, encrypt all collected raw data using AES-256 encryption algorithm, calculate the hash value of the raw data, and transmit the encrypted data and hash value to the salary calculation module through SSL / TLS protocol. The salary calculation module verifies the hash value after receiving it, completing data integrity verification; Salary calculation step, the salary calculation module applies for a decryption key to the central control module, decrypts the received encrypted basic data, performs salary calculation according to the preset salary calculation logic, generates employee personal salary details, starts a three-way verification mechanism, including logic verification, historical data comparison verification, and cross-data verification. If the verification is passed, the final salary details are generated. If the verification fails, an exception prompt is returned to the central control module, and the calculation process is suspended; Permission verification step, when the salary accountant initiates a salary details submission request, the financial payment staff initiates a payment execution request, and the employee initiates a salary query request, the permission management module receives the request and obtains the identity information of the request user. According to the RBAC model, the user's role is verified for the corresponding permission. If the verification is passed, the operation is allowed to continue. If the verification fails, the operation is denied and an abnormal access log is recorded in the audit tracing module; The security storage step is that the salary calculation module transmits the final salary details and encrypted basic data to the security storage module, the security storage module encrypts the data by using an SM4 algorithm, performs file-level encryption by using an RSA-2048 algorithm, stores the encrypted data into a local RAID5 disk array, and synchronizes the data to an off-site disaster recovery backup center, generates a storage record after the storage is completed, and sends the storage record to the central control module and the audit trace module; The payment execution step is that, after the permission verification is passed, the financial payment staff selects a salary payment channel by using the payment execution module, inputs account information required for payment, the payment execution module calls the final salary details in the security storage module, compares the consistency of the payment account and the employee account, initiates a payment request to the corresponding payment channel after the consistency is passed, the payment execution module encrypts and stores the result into the security storage module, and sends a notification of a query link to the employee, the employee receives the notification and completes payment confirmation through the system. The audit record step is that the audit trace module receives operation data of each module in real time, arranges the operation data into audit log entries, generates a unique hash value for the log entries and links the log entries to a blockchain distributed ledger, and stores the audit log into a specified area of the security storage module for administrators and auditors to query.

[0014] Further, the dynamic permission adjustment step is further included, when the system detects a change in the user operation scene, the user initiates a temporary permission adjustment application, the temporary permission is configured by the administrator after the application is approved, the priority of the temporary permission is determined by a formula P = λ × S + μ × I + ν × U, wherein P is the priority of the temporary permission, λ is a business urgency weight, S is a business urgency, μ is a data sensitivity weight, I is a data sensitivity degree, ν is a historical permission record weight, and U is a historical permission compliance record, after the temporary permission is configured according to the priority, the permission management module records the configuration process to the audit log, the temporary permission is automatically invalidated and the original permission is restored after the validity period of the temporary permission ends, and the invalidation process is also recorded in the log.

[0015] Further, the data disaster recovery and recovery step is further included, in this step, the security storage module performs local full backup and off-site incremental backup according to a preset period, the local backup is stored by ZIP compression and SM4 encryption, and the integrity is verified by hash value comparison; the off-site backup only synchronizes newly added or modified data, and the data is transmitted by IPsec encryption, the off-site backup center updates the version or re-synchronizes after hash verification; when the local data is damaged / lost, the administrator initiates a recovery request after multi-factor authentication by the auditors, the data is extracted from the local full backup, the off-site data is called when the local backup is unavailable, the integrity and accuracy are verified by comparison with the historical log after decryption, the recovery result is recorded in the audit trace module and the administrator is notified, the security storage module carries out a disaster recovery drill every quarter, simulates a local data full loss scene, records the index and generates a report.

[0016] Compared with the prior art, the present application has the beneficial effects that: In the data acquisition and transmission link, the AES-256 encryption algorithm is adopted in combination with the hash value comparison to realize the original data encryption and integrity double check, and the SSL / TLS protocol transmission is adopted to effectively block the data tampering and interception risk; the data desensitization module supports the dynamic desensitization strategy based on the access role, which not only ensures that the employee himself can view the complete personal information, but also limits the access range of other roles to the sensitive data, balances the data security and the use convenience. At the same time, the abnormal monitoring module can identify the risk behaviors such as unauthorized access and high-frequency query in real time, trigger the corresponding processing measures through risk quantization grading, and prevent data security threats in advance.

[0017] The fine design of the permission management system greatly improves the rigor and traceability of the system permission control. Based on the RBAC model, four core roles are divided and the permission boundary is clear, which avoids overstepping operation; the dynamic permission adjustment function supports the whole process record of temporary permission application, review, validity and invalidity, combined with regular permission compliance inspection, which not only meets the temporary permission needs such as cross-department cooperation, but also prevents long-term abuse of permissions. The permission change can be traced back to the specific operator and operation time, and the responsible person can be quickly located in case of problems.

[0018] The audit traceability and disaster recovery backup design strengthens the reliability and business continuity of the system. The audit traceability module uses blockchain technology to store operation logs, records all-dimensional information including operator, operation track and result verification, and the logs are tamper-proof and support multi-dimensional query, forming a complete audit link to provide reliable basis for security audit and problem traceability. The "local encrypted storage + off-site disaster recovery backup" architecture of the secure storage module, combined with real-time synchronization and regular backup strategy, ensures that data is not lost in scenarios such as hardware failure and natural disaster; the data recovery process includes integrity and availability verification to ensure that the recovered data can be directly used for salary calculation and payment, avoiding salary payment interruption due to data loss, and maintaining the timeliness of enterprise salary payment and employee rights. At the same time, the functions of payment result secondary verification and payment revocation audit improve the accuracy of salary payment, reduce disputes caused by payment errors, and enhance the trust of employees in enterprise salary management. BRIEF DESCRIPTION OF DRAWINGS

[0019] Figure 1 The schematic block diagram of the salary payment system based on data security management proposed by the present application; Figure 2 The schematic block diagram of the salary payment method based on data security management proposed by the present application; Figure 3 The comparison line graph of salary calculation time consumption under different employee scales; Figure 4 The comparison bar graph of approval periods of different permission operation types; Figure 5 A comparison line graph of processing response time for different abnormal types. DETAILED DESCRIPTION

[0020] The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative work fall within the scope of protection of the present application.

[0021] In the description of the present application, it should be understood that the orientations or positional relationships indicated by the terms "center", "longitudinal", "lateral", "length", "width", "thickness", "upper", "lower", "front", "rear", "left", "right", "vertical", "horizontal", "top", "bottom", "inner", "outer", "clockwise", "counterclockwise" and the like are based on the orientations or positional relationships shown in the drawings, and are only for the convenience of describing the present application and simplifying the description, and therefore cannot be understood as indicating or implying that the devices or elements indicated must have a particular orientation, be constructed and operated in a particular orientation, and therefore cannot be understood as limiting the present application.

[0022] In addition, the terms "first" and "second" are only for descriptive purposes, and cannot be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Therefore, the features defined with "first" and "second" can explicitly or implicitly include one or more of the features. In the description of the present application, the meaning of "multiple" is two or more, unless otherwise specifically limited. In addition, the terms "mounting", "connecting", "connection" should be broadly understood, for example, it can be fixed connection, or detachable connection, or integrally connected; it can be mechanical connection, or electrical connection; it can be directly connected, or indirectly connected through an intermediate medium, or the communication between two elements. For those skilled in the art, the specific meaning of the above terms in the present application can be understood according to the specific circumstances, and the present application will be further described in detail below with reference to the drawings.

[0023] Reference Figures 1 to 5 A salary payment system based on data security management includes the following modules: A data acquisition and encryption module is used to acquire basic data required for salary calculation, which covers employee attendance data, performance data, social security and public accumulation fund payment standards, individual tax deduction rules and salary structure data. The acquisition process uses AES-256 encryption algorithm to encrypt the original data, and the encrypted data is transmitted to the subsequent module through SSL / TLS protocol, while the data integrity is verified by comparing the hash value, realizing tamper-proofing in the data transmission process; The salary calculation module is connected with the data acquisition and encryption module, receives the encrypted basic data, applies for a decryption key to the central control module after receiving the encrypted basic data and completes decryption, executes salary calculation according to a preset salary calculation logic, specifically includes basic salary accounting, performance bonus calculation, social security and public accumulation fund deduction, individual income tax calculation and other subsidy and subsidy addition and subtraction rules, starts a three-fold verification mechanism after generating a preliminary salary detail, and is respectively a logic verification, a historical data comparison verification and a cross data verification, returns an abnormal prompt and suspends the calculation process when the verification fails; The permission management module is used for distributing system operation permissions, divides system users into four core roles of administrators, salary accountants, financial payers and employee inquirers, each role corresponds to exclusive operation permissions, the administrators have full module operation permissions, the salary accountants only have data viewing and salary calculation permissions, the financial payers only have payment execution and payment result viewing permissions, and the employee inquirers only have personal salary detail inquiry permissions, the permission distribution adopts a role-based access control (RBAC) model, and a permission change log is recorded synchronously; The secure storage module is connected with the salary calculation module and the permission management module, and is used for storing encrypted basic data, salary calculation results, permission configuration information and audit logs, a storage medium adopts an encrypted hard disk, double encryption is executed when data is stored, a storage encryption algorithm is SM4, file-level encryption is RSA-2048, an access control strategy is set at the same time, only authorized roles can access corresponding data after multi-factor authentication (including at least two of password, dynamic token and biometric identification), and unauthorized access triggers an alarm; The payment execution module is connected with the salary calculation module and the secure storage module, and is used for executing salary payment operations, supports three payment channels of bank transfer, electronic wallet payment and paper check, completes permission verification of the financial payers through the central control module before payment, sends a notification containing a payment amount, a payment time and a query link to the employees during the payment process, the notification mode includes a short message, an enterprise WeChat and an email, receives feedback results of the payment channel after the payment is completed, and stores the feedback results after encryption to the secure storage module; The audit tracing module is connected with all modules of the system, and is used for recording all operation behaviors in the system. The operation record includes an operator, an operation time, an operation module, an operation content, an operation result and a data access track. The record is stored by using a block chain technology, supports log query according to the operator, the operation time and the operation type, the query result can be viewed only by the administrators and the auditors, and a log is recorded synchronously during the query process; The central control module, as a system core coordination unit, is connected with the data acquisition and encryption module, the salary calculation module, the permission management module, the secure storage module, the distribution execution module and the audit traceability module, coordinates data interaction and function execution of each module, receives state feedback of each module, specifically including data processing progress, abnormal information and operation results, executes early warning on abnormal states, the early warning methods include system pop-up window, administrator SMS notification, manages system keys at the same time, the keys are periodically rotated and the rotation period is configurable, maintains system basic parameters, specifically including salary calculation rule update, permission template adjustment and storage strategy configuration.

[0024] In the application, the data desensitization module is connected with the data acquisition and encryption module and the secure storage module, and is used for performing desensitization processing on sensitive data stored and transmitted in the system. The sensitive data specifically includes employee ID number, bank account number and complete salary details that are not viewed by the employee himself. The desensitization rules specifically include partial character replacement, data format conversion and dynamic desensitization. The dynamic desensitization adjusts the desensitization degree according to the access role. When the employee himself views, the complete data is displayed. When other authorized roles view, the desensitized data is displayed. At the same time, the desensitization strategy can be dynamically adjusted according to the sensitive data type and the access scene. When the access frequency of the sensitive data is detected to be abnormal, the desensitization level is dynamically improved to control the exposure range of the sensitive data.

[0025] In the application, the abnormality monitoring module is connected with the central control module and the audit traceability module, and is used for monitoring data operation abnormality and salary distribution abnormality in the system. The data operation abnormality specifically includes unauthorized access attempt, high-frequency data query, abnormal IP address login and permission change abnormality. The salary distribution abnormality specifically includes distribution amount and calculation result deviation, distribution account and employee account mismatch and high frequency of distribution channel feedback failure. In the abnormality monitoring process, the abnormal risk value is quantified by the formula R = a x D + b x T + g x F, wherein R is the abnormal risk value, the value range is 0-100, R >= 80 is determined as high risk, 60 <= R < 80 is determined as medium risk, and R < 60 is determined as low risk; a is the data operation abnormality weight, the value range is 0.3-0.5; D is the data operation abnormality degree, the value range is 0-100, which is quantified according to the number of abnormal times and the influence range; b is the salary distribution abnormality weight, the value range is 0.3-0.5; T is the salary distribution abnormality degree, the value range is 0-100, which is quantified according to the deviation amount and the failure frequency; g is the historical abnormality correlation weight, the value range is 0.1-0.2; F is the historical abnormality correlation degree, the value range is 0-100, which is quantified according to the similarity between the current abnormality and the historical high-risk abnormality. The abnormality level is accurately determined by the quantification result, and corresponding processing measures are triggered according to the level. The high-risk immediately suspends the related operation and notifies the administrator. The medium-risk limits the operation permission and warns. The low-risk records the log and continuously monitors.

[0026] In the application, the authority management module also supports dynamic authority adjustment function, when the system detects the change of user operation scene, the administrator can initiate temporary authority adjustment application, the application needs to fill in adjustment reason, adjustment authority range and adjustment validity period, the application can take effect after being audited by the auditor, the validity period of temporary authority is not more than 72 hours at most, and the original authority is automatically restored after the validity period ends, the whole process of application, audit, taking effect and invalidation of temporary authority is recorded in the audit log, so that the authority change can be traced back; in addition, the authority management module periodically performs compliance check on all user authorities, the check content includes authority and role matching, whether there is long-term unused authority, and whether there is out-of-range authority, the check result generates a compliance report, and the non-compliant authority is automatically frozen and the administrator is notified.

[0027] In the application, the security storage module adopts a dual storage architecture of "local encrypted storage + off-site disaster recovery backup", the local storage is used for daily data access, the RAID5 disk array is used to realize hardware-level data reliability, the off-site disaster recovery backup is deployed in a backup center at least 50 kilometers away from the local storage, the backup data is synchronized with the local storage data in real time (the synchronization delay is not more than 10 seconds), the synchronization process adopts IPsec protocol encryption transmission, the off-site backup center adopts the same access control strategy as the local one, so that the backup data is not leaked; in addition, the security storage module performs life cycle management on the stored data, the retention period of basic data (attendance, performance, etc.) is 3 years, the retention period of salary calculation result and payment record is 10 years, and the data exceeding the retention period is deleted by crushing after being audited by the administrator and supervised by the auditor, and the deletion process is recorded in the audit log.

[0028] In the application, the payment execution module also has a secondary verification function of payment result, after the payment is completed and the payment channel feedback is successful, the system automatically sends a confirmation notification containing a random verification code to the employee, the employee needs to input the verification code through the system query interface within 24 hours to complete the payment confirmation, the employee who does not confirm in time will be reminded again by the system after 12 hours, and the employee who does not confirm after 48 hours will trigger an abnormal alarm and suspend the next salary payment of the employee until the confirmation is completed; in addition, the payment execution module also supports the function of salary payment revocation, when the payment error is found and the payment channel supports revocation, the financial payment staff can initiate a revocation application, the application needs to be audited by the administrator, the revocation operation can be executed within 2 hours after the payment is completed, and the revocation process and result are recorded in the audit log.

[0029] In the application, the audit traceability module also has log analysis and risk early warning functions, can perform multi-dimensional analysis on audit logs, specifically including operation frequency analysis, permission use analysis, abnormal operation trend analysis, the analysis period can be configured, and the default is once a day, the analysis result generates an audit report, and the report identifies high-frequency operation roles, abnormal operation concentration period and high-risk operation types, providing data support for administrators to optimize permission configuration and adjust security strategies.In addition, the audit log adopts tamper-proof storage technology, specifically a distributed ledger based on a blockchain, a unique hash value is generated for each log entry and linked to the previous entry, and modifying any entry will cause the hash chain to break, administrators and auditors can only view the log, cannot modify or delete the log, and log queries require multi-factor authentication, and the query record is also stored as part of the audit log, achieving traceability of the audit process.

[0030] In the application, the following steps are included: The data acquisition and encryption step, the data acquisition and encryption module obtains employee attendance data, performance data, social security fund payment standards and individual tax deduction rules from enterprise attendance systems, performance evaluation systems, social security fund management platforms and individual tax declaration systems, and obtains employee salary structure data from human resource systems, encrypts all collected raw data using an AES-256 encryption algorithm, calculates the hash value of the raw data, and transmits the encrypted data and the hash value to the salary calculation module through an SSL / TLS protocol, and the salary calculation module verifies the hash value after receiving it, and completes data integrity verification; The salary calculation step, the salary calculation module applies for a decryption key to the central control module, decrypts the received encrypted basic data, performs salary calculation according to a preset salary calculation logic (basic salary = post salary + job level salary, performance bonus = performance coefficient x performance base, social security fund deduction = payment base x payment rate, individual tax = (wage to be paid - threshold - special additional deduction) x tax rate - quick deduction number, actual wage = wage to be paid - social security fund deduction - individual tax - other deduction items), generates employee personal salary details, and starts a three-way verification mechanism: logic verification: check the accuracy of formula parameter calling; historical data comparison verification: compare whether the deviation between the current salary and the last month's salary is within the preset threshold; cross data verification: check the consistency of the social security fund deduction amount and the social security platform data; if the verification is passed, the final salary details are generated, and if the verification is not passed, an exception prompt is returned to the central control module, and the calculation process is suspended; The permission checking step, when the salary accountant initiates a salary detail submission request, the financial distributor initiates a distribution execution request, and the employee initiates a salary query request, the permission management module receives the request and obtains the identity information of the request user, checks the permission corresponding to the user role according to the RBAC model, the check content includes whether the operation permission is owned and whether the operation range is within the authorized range, and the check is passed. Continue to operate, the check is not passed, and the operation is rejected and the abnormal access log is recorded to the audit tracing module; The secure storage step, the salary calculation module transmits the final salary details and encrypted basic data to the secure storage module, the secure storage module uses the SM4 algorithm to perform storage encryption on the data, uses the RSA-2048 algorithm to perform file-level encryption, stores the encrypted data to the local RAID5 disk array, and synchronizes the data to the off-site disaster recovery backup center through the IPsec protocol. After the storage is completed, a storage record is generated, including the storage time, storage location, access permission, and the storage record is sent to the central control module and the audit tracing module; The distribution execution step, after the permission check is passed, the financial distributor selects the salary distribution channel through the distribution execution module, enters the account information required for distribution, and the distribution execution module calls the final salary details in the secure storage module. Compare the consistency of the distribution account and the employee account, and if the consistency is passed, initiate a distribution request to the corresponding payment channel. After the payment channel feedbacks the distribution result, the distribution execution module stores the result in the secure storage module, and sends a notification containing the distribution amount, distribution time, query link to the employee. The notification method is preset by the employee. After receiving the notification, the employee completes the distribution confirmation through the system; The audit record step, the audit tracing module receives the operation data of each module in real time, including the data source of data collection, encryption process, parameter call and result of salary calculation, request and result of permission check, operation and synchronization of secure storage, channel selection and result of distribution execution. The operation data is arranged into audit log entries, including operator, operation time, operation module, operation content, operation result, IP address, identity verification method, and a unique hash value is generated for the log entry and linked to the blockchain distributed ledger. At the same time, the audit log is stored in the specified area of the secure storage module for administrators and auditors to query.

[0031] In the application, a dynamic permission adjustment step is further included. When the system detects a change in the user operation scene, the user initiates a temporary permission adjustment application. The application content specifically includes an application role, an adjustment permission type, an adjustment range, an adjustment reason, and an adjustment validity period. After the application is submitted, the permission management module sends the application to an auditor for review. The auditor reviews the reasonableness of the application, specifically including whether there is a cross-department collaboration demand and whether the adjustment range is necessary. If the review is passed, the administrator configures temporary permissions. The priority of the temporary permission is determined by the formula P = λ × S + μ × I + ν × U, where P is the priority of the temporary permission, the value range is 0-10, the higher the P, the higher the priority configuration; λ is the business urgency weight, the value range is 0.4-0.6; S is the business urgency, the value range is 0-10, which is quantified according to the project deadline and the urgency of the collaboration demand; μ is the data sensitivity weight, the value range is 0.2-0.3; I is the data sensitivity, the value range is 0-10, the cross-department salary data sensitivity is 8-10, and the single-department non-core data is 3-7; ν is the historical permission record weight, the value range is 0.1-0.2; U is the historical permission compliance record, the value range is 0-10, no permission abuse record is 10, slight violation record is 5-9, and serious violation record is 0-4. After the priority is completed, the permission management module records the configuration process to the audit log, and the temporary permission is automatically invalidated and restored to the original permission after the validity period ends. The invalidation process is also logged.

[0032] In the present application, the data disaster recovery and backup steps are also included. In the steps, the secure storage module triggers local data full backup and off-site data incremental backup at a preset period (the period can be configured, and the default is every day at 2-4 am to avoid the peak period of business). The local full backup is compressed and encrypted by using the ZIP compression algorithm and the SM4 encryption algorithm, the hash value of the backup file is calculated after the backup is completed, and the hash value is compared with the original data hash value to complete the backup data integrity verification; the off-site incremental backup only synchronizes the newly added or modified data in the local storage, the synchronization process uses IPsec protocol encryption transmission to ensure the security of the data in the off-site transmission process, and after the synchronization is completed, the off-site backup center performs hash value verification on the incremental data, and if the verification is passed, the backup data version of the off-site storage is updated, and if the verification fails, the synchronization request is reinitiated; when the local storage has data damage or loss, the administrator initiates a data recovery request through the central control module, the request needs to be confirmed by the multi-factor authentication of the auditor, after the confirmation, the secure storage module preferentially extracts the corresponding data from the local full backup, and if the local backup is unavailable, the data is retrieved from the off-site disaster recovery center, the decryption algorithm (SM4, RSA-2048) consistent with the storage is used to decrypt the backup data during the recovery process, after the recovery is completed, the recovered data is compared with the data record in the historical operation log to verify the data integrity and accuracy, the recovery result is synchronized to the audit tracing module, and a recovery completion notification is sent to the administrator; in addition, the secure storage module performs a disaster recovery drill once a quarter, simulates the scenario of complete loss of local data, recovers the full data from the off-site backup center, records the recovery time consumption, data integrity compliance rate and other drill indicators, generates a disaster recovery drill report, analyzes the problems in the drill process in the report and proposes optimization schemes to ensure the effectiveness of the disaster recovery backup mechanism and the recoverability of the system data in extreme cases.

[0033] The specific embodiments of the present application are further illustrated by two embodiments as follows: Embodiment 1: Application of large manufacturing enterprise salary payment system This embodiment is applied to a large manufacturing enterprise with 5000 employees, including 12 production workshops and 8 functional departments, and needs to process differentiated salary structures of multiple departments (piecework wages of production positions, fixed salaries of functional positions, project bonuses of technical positions). The system module deployment and running details are as follows.

[0034] I. System module deployment and parameter configuration Data collection and encryption module: interface with enterprise fingerprint attendance system, performance evaluation system, social security and public accumulation fund management platform, individual income tax declaration system and human resource system, collect 120,000 punch card records per day, count production and qualified rate by team, update payment base every month, synchronize special additional deduction information, store post wage, job level wage and length of service subsidy data. The original data is encrypted by AES-256 encryption algorithm, the hash value is calculated by SHA-256, and the encrypted data is transmitted by SSL / TLS1.3 protocol, with transmission delay controlled within 500ms.

[0035] Salary calculation module: preset three types of salary calculation logic, production post actual wage = (piecework unit price x output x qualified rate) + length of service subsidy - (social security base x 16% + public accumulation fund base x 12%) - individual income tax - accommodation deduction; functional post actual wage = (post wage + job level wage) x attendance coefficient + performance bonus - (social security + public accumulation fund) - individual income tax; technical post actual wage = fixed salary + project bonus x contribution coefficient - (social security + public accumulation fund) - individual income tax. In the triple verification mechanism, logical verification checks the accuracy of parameter calling, such as whether the output data is associated with the corresponding workshop; the historical data comparison threshold is set to ±15%; cross verification interfaces with social security platform API to check the amount of deduction in real time.

[0036] Permission management module: divide into 4 types of roles, 10 administrators (headquarters HR director, IT director), 20 salary accountants (assigned by department, each responsible for 1-2 departments), 5 financial disbursement employees (divided into bank interface group), 5000 employee query employees (all employee accounts). In the RBAC permission template, salary accountants can only view attendance and performance data of the departments they are responsible for, and cannot modify individual income tax rules; financial disbursement employees can only initiate transfers, and cannot view salary calculation details. The key rotation period is set to the 1st of each month, triggered automatically by the central control module.

[0037] Secure storage module: locally use 6-disk RAID5 disk array, total storage capacity 20TB, SM4 storage encryption key length 128 bits, RSA-2048 file-level encryption key kept by administrator and auditor; off-site disaster recovery backup center is deployed in a city disaster recovery room 60 kilometers away from the factory, with a synchronization delay of 8 seconds, and a backup period of full backup at 3 am every day + incremental backup every 2 hours.

[0038] Abnormality monitoring module: deploy 10 abnormality detection nodes, monitoring frequency is 1 per second, unauthorized access attempt threshold is 5 times per minute, abnormal IP determination standard is non-enterprise intranet IP (enterprise intranet segment 192.168.0.0 / 16), disbursement amount deviation threshold is ±500 yuan, and disbursement failure frequency threshold is 3 times per employee.

[0039] Disbursement execution module: interface with 6 major bank APIs (supporting batch transfers), enterprise WeChat electronic wallet (for small subsidy disbursement), check printing system (for paper disbursement of retired employees), disbursement notification preferably uses enterprise WeChat, with a 98% reach rate and a 2-hour readout before a supplementary SMS is sent. Disbursement confirmation verification code is valid for 24 hours, and if not confirmed within that time, a financial review is triggered.

[0040] Audit traceability module: uses a consortium chain architecture, with 3 accounting nodes deployed in the HR, finance, and IT departments. Log entries include operator account, MAC address, operation duration, and data modification before and after comparison values. Queries support filtering by "department + month + operation type" combinations, and logs are retained for 10 years.

[0041] Central control module: uses an industrial-grade PLC, supports 500 data interfaces, and displays real-time data processing progress on a 15-inch touch screen, such as "attendance data encryption complete 98%". Abnormal warnings are pushed through the administrator's enterprise WeChat robot and trigger system pop-ups. Key storage uses a hardware encryption machine (prevents physical disassembly).

[0042] II. Control process and formula application Data collection and encryption steps: On the 25th of each month at 18:00, the module automatically pulls data from various sources, encrypts the attendance data after deduplication (removes duplicate punches), and generates a hash value, such as "a3f2d4e5...". The encrypted data is transmitted to the payroll calculation module, which verifies the hash value before receiving the data.

[0043] Payroll calculation steps: On the 26th at 9:00, the payroll calculation module applies for decryption keys to the central control module (keys are dynamically generated by a hardware encryption machine). After decryption, the corresponding calculation logic is called by department to generate preliminary details, such as employee Zhang San's piecework salary of 8500 yuan and seniority allowance of 300 yuan in production workshop A. Three verification checks are initiated: logic verification finds that "technical position Li Si's project bonus is not associated with a project number", returns an abnormal prompt, and after the accounting staff supplements the project information, the calculation is recalculated. Upon passing the verification, the final details are generated.

[0044] Permission verification and dynamic adjustment step: At 10 o'clock on the 27th, the payroll accountant of workshop B applied to view the performance data across workshop C (due to collaborative production to check production), initiated a temporary permission application, the reason is "cross-workshop collaborative production check", the effective period is 24 hours, after the audit personnel pass the audit, the administrator configures the permission to call the abnormal risk value formula R = a x D + b x T + g x F, a = 0.4 (data operation abnormal weight), D = 60 (the accountant has no abnormal operation in the past 30 days, the abnormal degree is 60); b = 0.4 (salary payment abnormal weight), T = 50 (no abnormal payment in workshop C this month, abnormal degree 50); g = 0.2 (historical correlation weight), F = 70 (no historical high-risk correlation, correlation degree 70), calculate R = 0.4 x 60 + 0.4 x 50 + 0.2 x 70 = 24 + 20 + 14 = 58 (low risk), grant temporary viewing permission, record to audit log after permission takes effect.

[0045] Payment execution and audit steps: At 15 o'clock on the 28th, the financial payment employee selects the bank transfer channel, enters 1200 employee bank account numbers, and after the module compares the account numbers with the employee information library, initiates a batch transfer request, 30 minutes later receives bank feedback (1198 successful, 2 failed), the reason for failure is "account frozen", the system triggers an abnormal warning, the financial personnel contact the employee to update the account number and reissue; At the same time, push the enterprise WeChat notice to the employee, the employee clicks the link to input the verification code to complete the confirmation, and the confirmation record is stored in the secure storage module. The audit traceability module records the whole process of "payment employee Wang Wu initiates transfer-1198 successful-2 failed-reissue" in real time, and generates a blockchain log entry.

[0046] III. Data representation and interpretation Table 1 Comparison of key indicators between traditional payroll system of large manufacturing enterprise and this system Comparison index Conventional system Inventive system Data leakage incident rate 1.2 times / year 0 times / year Number of complaints of abuse of authority 8 times / year 0 times / year Salary calculation error rate 2.5% 0.1% Abnormal processing response time 4 hours 15 minutes Data recovery success rate 75% 100% Table 1 shows that the traditional system has 1.2 times of data leakage and 8 times of permission abuse complaints per year due to single encryption mechanism and loose permission control, the error rate of payroll calculation is 2.5% due to reliance on manual checking, and the abnormal processing needs 4 hours (manual log checking), the data recovery success rate is only 75% due to no off-site backup of local storage. This system realizes zero data leakage and zero permission abuse through AES-256 encryption, RBAC permission model and blockchain audit; threefold verification reduces the calculation error rate to 0.1%; the abnormal monitoring module locates and handles the problem within 15 minutes; "local + off-site" dual storage ensures the data recovery success rate of 100%, which fully meets the security payroll management needs of large manufacturing enterprises with multiple departments and high data volume.

[0047] Example 2: Application of payroll payment system of small and medium-sized internet companies This embodiment is applied to a small and medium-sized Internet company with 300 employees, mainly in the form of projects (including product, research and development, and operation three core departments), which needs to support remote office permission application and real-time project bonus accounting. The system module is adapted to the lightweight demand as follows.

[0048] I. System module deployment and parameter configuration Data acquisition and encryption module: interface with WeChat remote attendance system, Jira project management system, third-party social security payment platform, individual tax APP and Feishu HR system, collect 300 check-in data every day, statistics of R&D personnel task completion rate, monthly payment details, synchronization of employee special additional deductions, storage of basic salary and job level subsidies. AES-256 encryption is transmitted through SSL / TLS1.3 protocol, transmission delay is controlled within 300ms, and SHA-256 is used for hash value verification.

[0049] Salary calculation module: two types of calculation logic are preset, R&D position real wage = basic salary + (task completion rate x project bonus base) - (social security + public accumulation fund) - individual tax; operation position real wage = basic salary + (KPI score x performance coefficient) - (social security + public accumulation fund) - individual tax. In threefold verification, the historical data comparison threshold is set to ±20%, and the cross verification is connected with Jira API to check the task completion rate.

[0050] Permission management module: divide into 4 types of roles, 3 administrators (CEO, HR supervisor, IT specialist), 2 salary accountants (responsible for accounting for the whole company), 1 financial payment employee, and 300 employee query employees. In the RBAC template, accountants can view all company data but cannot modify the project bonus base, and financial payment employees can only operate electronic wallets and bank transfers. The key rotation period is set to every 2 weeks, which is manually triggered by the central control module.

[0051] Secure storage module: locally using 4-disk RAID5 disk array, total storage capacity 5TB, SM4 encryption key 128 bits, RSA-2048 key managed by HR supervisor and financial director; off-site disaster recovery backup center is deployed in a cloud server 30 kilometers away from the company, with a synchronization delay of 10 seconds, and a backup period of full backup every morning at 2 o'clock + incremental backup every 4 hours.

[0052] Abnormal monitoring module: deploy 3 abnormal detection nodes, monitoring frequency 1 times per second, unauthorized access threshold 3 times / minute, abnormal IP non-company VPN sIP (VPN segment 10.0.0.0 / 8), deviation threshold of payment amount ±200 yuan, failure frequency threshold 2 times / employee.

[0053] Disbursement execution module: interface with 2 bank APIs (supporting small batch transfers), enterprise WeChat electronic wallet (main distribution channel, 100% reach rate), distribution notification priority is enterprise WeChat, 1-hour unread supplementary email. Confirm the validity period of the verification code is 12 hours, and trigger HR review if it exceeds the time limit.

[0054] Audit traceability module: adopt lightweight consortium chain, 2 accounting nodes are deployed in HR and finance department respectively, log contains operator account, login device model, operation content summary, query supports "project + employee" screening, log retention period is 5 years.

[0055] Central control module: adopt commercial PLC, support 100 data interfaces, 10-inch touch screen display real-time progress, abnormal warning through administrator enterprise WeChat and SMS double push, key storage adopts software encryption container (binds company intranet IP).

[0056] II. Control process and formula application Data collection and encryption steps: every month at 12:00 on the 20th, the module automatically pulls data (Jira task data is grouped by project), generates a hash value after encryption, and transmits it to the payroll calculation module, which receives it after verifying the hash consistency.

[0057] Payroll calculation steps: 10:00 on the 21st, the module applies for decryption key, decrypts, and calls logic according to post, such as research and development Li Si's task completion rate is 95%, project bonus base is 8000 yuan, and calculated bonus is 7600 yuan. Three times of verification found that "operation Wang Wu KPI score is not audited", returned abnormal, operation supervisor reviewed and recalculated, generated final details.

[0058] Dynamic permission adjustment steps: 9:00 on the 22nd, research and development personnel Zhao Liu applied to view product department project bonus data (validity period 12 hours) due to cross-project cooperation. After the application was initiated, the audit personnel approved, and the administrator configured the temporary permission priority formula P=λ×S+μ×I+ν×U, λ=0.5 (business urgency weight), S=8 (project online countdown 3 days, urgency 8); μ=0.3 (data sensitivity weight), I=9 (product department bonus data sensitivity 9); ν=0.2 (historical record weight), U=10 (Zhao Liu has no violation record, compliance record 10), calculate P=0.5×8+0.3×9+0.2×10=0.5×8+0.3×9+0.2×10=4+2.7+2=8.7 (high priority), complete permission configuration within 10 minutes, record to audit log.

[0059] Salary distribution execution and disaster recovery steps: At 14:00 on the 23rd, the financial distribution staff distributed the salary through the enterprise WeChat electronic wallet, 298 successful, 2 failed (reason "account not bound"), after the system warning, HR contacted the employee to bind the account and reissue; At the same time, trigger off-site backup, cloud server synchronizes the latest distribution record. The next day at 10:00, the local storage hard disk failed, the central control module automatically recovered data from off-site backup, after recovery, verify the consistency of salary details and distribution records, 15 minutes to restore normal operation of the system.

[0060] III. Data representation and interpretation Table 2 Comparison of key indicators between traditional salary system of small Internet companies and the system Comparison index Conventional system Inventive system Salary calculation time 8 hours 1.5 hours Remote authority application cycle 24 hours 30 minutes Notification reach rate 85% 100% Data backup time 2 hours 10 minutes Employee query satisfaction 65% 98% Table 2 shows that the traditional system relies on manual input and Excel calculation, and the salary calculation takes 8 hours; Remote permission application needs to be signed across departments, and the cycle is 24 hours; The distribution notice relies only on SMS, and the reach rate is 85%; Data backup is manually executed, and it takes 2 hours; Employees need to contact HR to query the salary, and the satisfaction is only 65%. The system reduces the time-consuming to 1.5 hours through automatic calculation; Dynamic permissions are configured within 30 minutes; Enterprise WeChat notification achieves 100% reach; Automatic backup is completed in 10 minutes; Employees can query details by themselves, and the satisfaction is improved to 98%, which adapts to the business characteristics of small and medium-sized Internet companies "light, efficient, remote collaboration", while ensuring data security and improving the efficiency of salary management.

[0061] Reference Figure 3 The line chart directly shows the influence law of employee size growth on salary calculation efficiency. The traditional system relies on manual input and Excel accounting, and the time-consuming increases linearly with the number of employees. When the scale is 5000, the time-consuming is 10 hours, and the scale expansion directly leads to a cliff-like decline in efficiency; The system of the invention relies on automatic data collection, batch calculation logic and module cooperation, and it only takes 0.5 hours when the scale is 500, even if the scale is 5000, it only takes 1.5 hours, and the time-consuming increases by less than 200%. This difference proves that the automatic architecture of the invention can adapt to different scale enterprises, especially for large enterprises with multiple departments and high data volume salary accounting scenarios, through algorithm optimization to avoid the efficiency bottleneck of manual operation, to ensure the timeliness of large-scale salary accounting.

[0062] Reference Figure 4The histogram clearly presents the efficiency difference of the permission management process. The traditional system permission operation relies on offline manual signature approval, and temporary cross-department viewing needs 24 hours, and abnormal permission unblocking even reaches 36 hours, which is cumbersome and easy to cause business delay; the system of the application quantitatively evaluates the temporary cross-department viewing only needs 0.5 hours and the abnormal permission unblocking can be completed in 4 hours through automatic permission verification, online audit process and temporary permission priority formula. While improving the efficiency of approval, the system records audit logs for the whole process of permission operation, which not only meets the business needs of enterprises to flexibly adjust permissions, but also avoids the compliance risks brought by simplifying the process.

[0063] Referring to Figure 5 The line chart presents the core difference of abnormal disposal efficiency. The traditional system relies on manual log checking to locate abnormalities, and the response to log tampering type of abnormality needs 300 minutes, and data tampering also needs 240 minutes, and inefficient disposal is easy to expand the loss; the system of the application quantitatively evaluates the abnormal level through the risk value formula of the abnormal monitoring module, quickly locates the root cause of the abnormality, and responds to the account error type of abnormality in only 5 minutes, and the log tampering can be quickly traced due to the block chain storage, and the processing is completed in 20 minutes. The abnormal monitoring module scans the system state in real time, automatically suspends the related operation of high-risk abnormality and pushes the early warning, and minimizes the influence of abnormality on the salary payment process.

[0064] The above is only the preferred specific embodiment of the application, but the protection scope of the application is not limited to this, any person skilled in the art can make equivalent replacement or change according to the technical scheme and the inventive concept of the application within the technical range disclosed by the application, which should be covered in the protection scope of the application.

Claims

1. A payroll system based on data security management, characterized in that, Includes the following modules: The data acquisition and encryption module collects the basic data required for salary calculation. The original data is encrypted using the AES-256 encryption algorithm during the acquisition process. The encrypted data is then transmitted to subsequent modules via the SSL / TLS protocol. At the same time, the integrity of the collected data is verified by comparing hash values. The payroll calculation module receives encrypted basic data, requests a decryption key from the central control module and completes the decryption, performs payroll calculation according to the preset payroll calculation logic, generates preliminary payroll details and then starts a triple verification mechanism. If the verification fails, it returns an error message and pauses the calculation process. The access control module divides system users into four core roles: administrator, payroll clerk, financial disbursement clerk, and employee query clerk. Each role has exclusive operation permissions, and the permission allocation adopts a role-based access control model, which synchronously records permission change logs. The secure storage module is used to store encrypted basic data, salary calculation results, permission configuration information and audit logs. The storage medium is an encrypted hard disk. Data is double-encrypted when stored. At the same time, access control policies are set so that only authorized roles can access the corresponding data after passing multi-factor authentication. Unauthorized access will trigger an alarm. The payroll disbursement module is used to perform payroll disbursement operations. It supports three disbursement channels: bank transfer, e-wallet payment, and paper check. Before disbursement, the central control module verifies the financial disbursement staff's permissions. During the disbursement process, it sends a notification to employees containing the disbursement amount, disbursement time, and query link. After disbursement, it receives feedback results from the payment channels. The feedback results are encrypted and stored in the secure storage module. The audit traceability module is used to record all operations within the system. The records are stored using blockchain technology and support querying logs by operator, operation time, and operation type. The query results are only visible to administrators and auditors, and the query process is recorded in the logs simultaneously. The central control module receives status feedback from each module, issues early warnings for abnormal states, manages system keys, and maintains basic system parameters.

2. The payroll system based on data security management according to claim 1, characterized in that, It also includes a data anonymization module. Sensitive data includes employee ID numbers, bank account numbers, and complete salary details that are not viewed by the individual. The anonymization rules cover partial character replacement, data format conversion, and dynamic anonymization. At the same time, the anonymization strategy is dynamically adjusted according to the type of sensitive data and the access scenario. When abnormal access frequency of sensitive data is detected, the anonymization level is dynamically increased to control the scope of sensitive data exposure.

3. The payroll system based on data security management according to claim 1, characterized in that, It also includes an anomaly monitoring module, which is used to monitor data operation anomalies and salary payment anomalies within the system. During the anomaly monitoring process, the anomaly risk value is quantified using the formula R=α×D+β×T+γ×F, where R is the anomaly risk value, α is the weight of the data operation anomaly, D is the degree of the data operation anomaly, β is the weight of the salary payment anomaly, T is the degree of the salary payment anomaly, γ is the weight of the historical anomaly correlation, and F is the degree of the historical anomaly correlation. The anomaly level is determined by the quantification result, and corresponding handling measures are triggered according to the level.

4. A payroll system based on data security management according to claim 1, characterized in that, The access control module also supports dynamic access control adjustment. When the system detects a change in user operation scenario, the administrator initiates a temporary access control adjustment request. After the request is submitted and approved by the auditors, it takes effect. The validity period of temporary access control is no more than 72 hours. After the validity period expires, the original access control will be automatically restored. The entire process of application, review, activation and expiration of temporary access control is recorded in the audit log. In addition, the access control module regularly performs compliance checks on all user access control. Non-compliant access control is automatically frozen and the administrator is notified.

5. A payroll system based on data security management according to claim 1, characterized in that, The secure storage module adopts a dual storage architecture of "local encrypted storage + off-site disaster recovery backup". Local storage is used for daily data access and uses RAID5 disk array to achieve hardware-level data reliability. Off-site disaster recovery backup is deployed in the backup center. Backup data is synchronized with local storage data in real time. The synchronization process uses IPsec protocol for encrypted transmission. The off-site backup center adopts the same access control policy as the local one. In addition, the secure storage module performs lifecycle management on the stored data. The basic data is retained for 3 years, and the salary calculation results and payment records are retained for 10 years. Data that exceeds the retention period is deleted by shredding after being reviewed by the administrator and supervised by the auditor. The deletion process is recorded in the audit log.

6. A payroll system based on data security management according to claim 1, characterized in that, The payroll execution module also features a secondary verification function for payroll results. After payroll is completed, the system automatically sends a confirmation notification containing a random verification code to the employee. The employee must enter the verification code through the system query interface within 24 hours to complete the payroll confirmation. For employees who fail to confirm within the specified time, the system will send a reminder notification again after 12 hours. If the employee still fails to confirm after 48 hours, the payroll execution module will trigger an abnormal warning and suspend the employee's next payroll payment until confirmation is completed. In addition, the payroll execution module also supports a payroll cancellation function. If a payroll error is found and the payment channel supports cancellation, the finance payroll clerk will initiate a cancellation request. The cancellation operation will be executed within 2 hours after the payroll is completed. If it exceeds 2 hours, manual intervention is required. The cancellation process and results are recorded in the audit log.

7. A payroll system based on data security management according to claim 1, characterized in that, The audit traceability module also has log analysis and risk warning functions. It performs multi-dimensional analysis on audit logs and generates audit reports based on the analysis results. The reports identify high-frequency operation roles, periods of concentrated abnormal operations, and high-risk operation types, providing data support for administrators to optimize permission configurations and adjust security policies. In addition, the audit logs use immutable storage technology, so administrators and auditors can only view the logs and cannot modify or delete them.

8. A method for using a payroll system based on data security management as described in any one of claims 1-7, characterized in that, Includes the following steps: The data collection and encryption steps involve collecting employee attendance data, performance data, social security and housing provident fund payment standards, individual income tax deduction rules, and employee salary structure data. All collected raw data is encrypted using the AES-256 encryption algorithm, and the hash value of the raw data is calculated. The encrypted data and hash value are transmitted to the payroll calculation module via the SSL / TLS protocol. After receiving the data, the payroll calculation module verifies the hash value to complete the data integrity verification. The salary calculation process involves the salary calculation module requesting a decryption key from the central control module, decrypting the received encrypted basic data, performing salary calculations according to the preset salary calculation logic, generating individual employee salary details, and initiating a triple verification mechanism: logical verification, historical data comparison verification, and cross-data verification. If the verification passes, the final salary details are generated; if the verification fails, an error message is returned to the central control module, and the calculation process is paused. In the permission verification process, when a payroll clerk initiates a payroll details submission request, a finance disbursement clerk initiates a disbursement execution request, or an employee initiates a payroll query request, the permission management module receives the request and obtains the identity information of the requesting user. Based on the RBAC model, it verifies the permissions corresponding to the user role. If the verification passes, the operation is allowed to continue; if the verification fails, the operation is rejected and the abnormal access log is recorded to the audit traceability module. In the secure storage process, the payroll calculation module transmits the final payroll details and encrypted basic data to the secure storage module. The secure storage module uses the SM4 algorithm to encrypt the data and the RSA-2048 algorithm to perform file-level encryption. The encrypted data is then stored in the local RAID5 disk array and synchronized to the off-site disaster recovery backup center. After storage is completed, a storage record is generated and sent to the central control module and the audit traceability module. In the payroll execution process, after the financial payroll clerk passes the authorization verification, they select the payroll channel through the payroll execution module and enter the account information required for payroll. The payroll execution module calls the final payroll details in the secure storage module and compares the payroll account with the employee's account. If the consistency is successful, a payroll request is initiated to the corresponding payment channel. The payroll execution module encrypts and stores the result in the secure storage module and sends a notification with a query link to the employee. After receiving the notification, the employee completes the payroll confirmation through the system. The audit logging process involves the audit traceability module receiving operational data from each module in real time, organizing the data into audit log entries, generating a unique hash value for each log entry and linking it to the blockchain distributed ledger, and storing the audit logs in a designated area of ​​the secure storage module for administrators and auditors to query.

9. A method for a payroll system based on data security management according to claim 8, characterized in that, It also includes a dynamic permission adjustment step. When the system detects a change in the user's operation scenario, the user initiates a temporary permission adjustment request. If approved, the administrator configures the temporary permissions. The priority of the temporary permissions is determined by the formula P=λ×S+μ×I+ν×U, where P is the temporary permission priority, λ is the business urgency weight, S is the business urgency, μ is the data sensitivity weight, I is the data sensitivity level, ν is the historical permission record weight, and U is the historical permission compliance record. After the temporary permission is configured according to the priority, the permission management module records the configuration process to the audit log. The temporary permission expires automatically and the original permission is restored after the expiration of the validity period. The expiration process is also recorded in the log.

10. A method for a payroll system based on data security management according to claim 8, characterized in that, It also includes data disaster recovery backup and recovery steps. In this step, the secure storage module performs local full backup and off-site incremental backup according to a preset cycle. The local backup is compressed with ZIP and encrypted with SM4. The integrity is verified by comparing hash values. Off-site backups only synchronize newly added or modified data, transmitted with IPsec encryption. The off-site backup center updates the version or resynchronizes after hash verification. When local data is damaged or lost, the administrator initiates a recovery request after multi-factor authentication by auditors. Data is retrieved from the local full backup first. If the local backup is unavailable, off-site data is retrieved. After decryption, the integrity and accuracy are verified by comparing with historical logs. The recovery result is recorded in the audit traceability module and the administrator is notified. The secure storage module conducts disaster recovery drills every quarter, simulating the scenario of complete loss of local data, recording indicators and generating reports.

Images