Data management system and method for identifying data security policy based on knowledge management
By establishing a security knowledge base and implementing workbench collaboration in the data governance system, identifying and recommending data security policies, the problem of inefficient data security management in the existing technology is solved, and efficient execution and reuse of data security policies is achieved.
Patent Information
- Application Number
- CN202411059426.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-03
- Publication Date
- 2024-12-03
- Estimated Expiration
- 2044-08-03
AI Technical Summary
The existing data governance system consumes time and cannot effectively reuse experience in data security management, resulting in low data security policy identification efficiency and inefficient inheritance.
Adopt a data governance system based on knowledge management to establish a security knowledge base in advance. Through the collaboration between the data security knowledge base and the implementation workbench, data security policies are identified and recommended, updated policies are generated and synchronized to the data governance subsystem to improve data security The efficiency of the execution of the strategy.
It improves the execution efficiency of data security policies, realizes policy reuse and inheritance of the same type of data, and reduces waste in the data governance process.
Smart Images

Figure CN119066659A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of data security technology, and in particular to a data governance system and method based on knowledge management to identify data security policies. Background Art
[0002] The content of data security management in the data governance system includes managing data security, preventing data leakage, damage, tampering and unauthorized access. Data security management implements data protection measures through certain data security strategies. Data protection strategies mainly include data desensitization, data classification and data operation. Through data protection strategies, sensitive and confidential data can be protected.
[0003] In the existing data governance system, data security management first involves identifying the data security policy for each table field, and then executing corresponding data protection measures based on these policies. It is necessary to identify the meaning of each table field and determine and execute the corresponding data protection policy. This process is time-consuming, and for similar data security management needs, a large amount of data governance experience cannot be inherited and reused, resulting in great waste.
[0004] Therefore, based on the above situation, it is very necessary to provide a data governance system and method based on knowledge management to identify data security policies, establish a security knowledge base in advance, summarize and organize security policy knowledge and policies, perform targeted processing on classified data, and improve the execution efficiency of security policies. Summary of the invention
[0005] In view of this, the present invention proposes a data governance system and method based on knowledge management to identify data security policies for secure processing of specific data and prevent data leakage, tampering or destruction.
[0006] In one aspect, the present invention provides a data governance system for identifying data security policies based on knowledge management, comprising:
[0007] Data governance subsystem, used to collect metadata;
[0008] Data security knowledge base, used to store data security policies and provide data security policy recommendation results to the implementation workbench;
[0009] The implementation workbench interacts with the data governance subsystem and the data security knowledge base respectively; it is used to observe and mark the metadata that needs to add data security policies, obtain the data security policy recommendation results from the data security knowledge base, and further generate updated data security policies. The updated data security policies are synchronized to the data governance subsystem and the data security knowledge base respectively;
[0010] Among them, the data governance subsystem also implements updated data security policies.
[0011] Based on the above technical solutions, preferably, the metadata collected by the data governance subsystem includes the first source data of the external system and the second source data of the data warehouse of the data governance subsystem; wherein the first source data includes supplier, system, version, data source type, IP, port, user and password fields; the second source data includes schema name, table English name, table comment, field English name, field comment, data type, whether it is required and whether it is a primary key field.
[0012] Preferably, a workbench is implemented to observe and mark the metadata to which data security policies need to be added. This is to observe the metadata collected by all data governance subsystems and mark the acquired vendor, system, version, user name, password, table English name, table comment and field English name fields; the marked fields are the fields of the recommended results of the data security policy to be added.
[0013] Further preferably, the data security knowledge base presets mutually related supplier system tables, security protection data tables and data security policy relationship tables; wherein the supplier system table includes, in sequence, a first system number column, a supplier column, a system number column and a version number column; the security protection data table includes a second system number column, a data warehouse layering column, a first data table coding column, a database mode column, a table English name column and a table Chinese name column; the data security policy relationship table includes a third system number column, a second data table coding column, a field English name column, a field Chinese name column and a data security policy coding column; the contents of the marked fields of the implementation workbench are compared with the contents of each row of the supplier system table, the security protection data table and the data security policy relationship table preset in the data security knowledge base, and the data security policy recommendation results are obtained from the data security knowledge base; the contents of the first system number column, the second system number column and the third system number column are only used as sequence numbers; the contents of the first data table coding column and the second data table coding column correspond to each other.
[0014] Further preferably, obtaining the data security policy recommendation result from the data security knowledge base is performed by querying the marked supplier field:
[0015] 1) If the supplier field, system number field and version field of the metadata all exist in the supplier system table of the data security knowledge base, then further query the corresponding first data table code column, second data table code column and data security policy code column in the data security policy relationship table. If the content of the first data table code column corresponding to the supplier field is the same as the content of the second data table code column, and there is valid data in the data security policy code column, then select the data corresponding to the data security policy code as the data security policy recommendation result;
[0016] 2) If the supplier field, system number field and version field of the metadata all exist in the supplier system table of the data security knowledge base, then further query the corresponding first data table code column, second data table code column and data security policy code column in the data security policy relationship table. If the content of the first data table code column corresponding to the supplier field is the same as that of the second data table code column, but there is no valid data in the data security policy code column, or the content of the first data table code column corresponding to the supplier field is different from that of the second data table code column, then select the data corresponding to the lowest level data security policy code as the data security policy recommendation result; and fill the currently generated lowest level data security policy code into the data security policy code column of the data security policy relationship table;
[0017] 3) If the supplier field, system number field and version field of the metadata do not exist in the supplier system table of the data security knowledge base, the data corresponding to the lowest level data security policy code is automatically selected or manually selected as the data security policy recommendation result; and the currently generated lowest level data security policy code is filled in the data security policy code column of the data security policy relationship table.
[0018] More preferably, the data security policy recommendation results are in ascending order of level, including data classification strategy, data operation strategy and desensitization strategy;
[0019] The data classification strategy is to classify metadata into level 1, level 2, and level 3 according to the importance of metadata from small to large;
[0020] Desensitization strategy is to change sensitive information in metadata through masking, hashing, truncation or encryption operations;
[0021] Data operation strategies include two categories: querying metadata and publishing metadata.
[0022] Still further preferably, the published metadata in the data operation strategy is to further classify the metadata into three categories: unconditional sharing, conditional sharing and non-sharing after executing the data classification strategy, and set a desensitizing algorithm for the conditionally shared metadata above level 2.
[0023] More preferably, the further generation of the updated data security policy is that after the implementation workbench obtains the data security policy recommendation result, it adds or deletes the content of the data warehouse hierarchical column of the security protection data table in combination with the system field of the metadata.
[0024] Further preferably, the updated data security policy is synchronized to the data governance subsystem and the data security knowledge base respectively. On the one hand, after the updated data security policy is generated, the data security policy knowledge corresponding to the updated data security policy is saved and merged into the preset supplier system table, security protection data table and data security policy relationship table of the data security knowledge base. The data security policy knowledge includes the supplier, system number, version number, data warehouse layer, data table code, database model, table English name, table Chinese name, field English name, field Chinese name and data security policy code field set in sequence. Each field of the data security policy knowledge corresponds one by one to the non-system number column of the supplier system table, security protection data table and data security policy relationship table.
[0025] On the other hand, the present invention also provides a data governance method based on knowledge management to identify data security policies, which is configured with the above-mentioned data governance system based on knowledge management to identify data security policies. The method comprises the following steps:
[0026] S1: Collect metadata: Call the data governance subsystem to collect metadata;
[0027] S2: Implement the workbench to observe the metadata obtained by the data governance subsystem and identify the metadata that needs to add data security policies;
[0028] S3: The implementation workbench obtains data security policy recommendation results from the data security knowledge base;
[0029] S4: adjust and supplement the data security policy to obtain an updated data security policy;
[0030] S5: Save the updated data security policy to the data security knowledge base;
[0031] S6: Synchronize the updated data security policy to the data governance subsystem;
[0032] S7: The data governance subsystem implements the updated data security policy.
[0033] The data governance system and method for identifying data security policies based on knowledge management provided by the present invention have the following beneficial effects compared with the prior art:
[0034] (1) The present invention establishes a data security knowledge base, pre-configures interrelated supplier system tables, security protection data tables, and data security policy relationship tables, covers various fields in the metadata that require recommended data security policies, and facilitates identification by the implementation workbench and further processing by the data security knowledge base;
[0035] (2) In the process of obtaining data security policies, the present invention implements collaboration between the workbench and the data security knowledge base to generate data security policy knowledge corresponding to the updated data security policies. The data security policy knowledge is stored in the data security knowledge base so that it can be shared and reused when security policies are subsequently adopted for the same type of metadata, thereby improving work efficiency. BRIEF DESCRIPTION OF THE DRAWINGS
[0036] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.
[0037] Figure 1 This is a system architecture diagram of a data governance system and method based on knowledge management to identify data security policies in the present invention;
[0038] Figure 2 This is an overall flow chart of a data governance system and method based on knowledge management to identify data security policies in the present invention;
[0039] Figure 3 A flowchart of a data governance system and method for executing a desensitization strategy based on knowledge management to identify data security policies according to the present invention;
[0040] Figure 4 This is a flow chart of the data operation strategy of a data governance system and method based on knowledge management to identify data security strategies in the present invention. DETAILED DESCRIPTION
[0041] The following will be combined with the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.
[0042] like Figure 1 As shown, on the one hand, the present invention provides a data governance system for identifying data security policies based on knowledge management, comprising:
[0043] Data governance subsystem, used to collect metadata;
[0044] Data security knowledge base, used to store data security policies and provide data security policy recommendation results to the implementation workbench;
[0045] The implementation workbench interacts with the data governance subsystem and the data security knowledge base respectively; it is used to observe and mark the metadata that needs to add data security policies, obtain the data security policy recommendation results from the data security knowledge base, and further generate updated data security policies. The updated data security policies are synchronized to the data governance subsystem and the data security knowledge base respectively;
[0046] Among them, the data governance subsystem also implements the updated data security policy, that is, realizes the collection, processing, use and supervision of metadata.
[0047] Depend on Figure 1 It can be seen that the implementation workbench and data governance subsystem are independently deployed on each data governance project. The implementation workbench provides independent tenants for each project to achieve isolation of the implementation work of each project. The data security knowledge base is centrally deployed to provide SaaS services for each project; the data security knowledge base is oriented to all data governance projects and provides knowledge sharing for project implementation work.
[0048] The metadata collected by the data governance subsystem includes the first source data of the external system and the second source data of the data warehouse of the data governance subsystem. The first source data includes the supplier, system, version, data source type, IP, port, user and password fields; the second source data includes the schema name, table English name, table comment, field English name, field comment, data type, whether it is required and whether it is a primary key field.
[0049] The implementation workbench observes and marks the metadata that needs to add data security policies. This is to observe the metadata collected by all data governance subsystems, and mark the obtained vendor, system, version, user name, password, table English name, table comment, and field English name fields; the marked fields are the fields of the recommended results of the data security policy to be added.
[0050] The data security knowledge base presets interrelated supplier system tables, security protection data tables and data security policy relationship tables; wherein the supplier system table includes the first system number column, supplier column, system number column and version number column in sequence; the security protection data table includes the second system number column, data warehouse layering column, the first data table coding column, the database mode column, the table English name column and the table Chinese name column; the data security policy relationship table includes the third system number column, the second data table coding column, the field English name column, the field Chinese name column and the data security policy coding column; the contents of the marked fields of the implementation workbench are compared with the contents of each row of the supplier system table, security protection data table and data security policy relationship table preset in the data security knowledge base, and the data security policy recommendation results are obtained from the data security knowledge base; the contents of the first system number column, the second system number column and the third system number column are only used as serial numbers; the contents of the first data table coding column and the second data table coding column correspond to each other.
[0051] The following table shows an example of a supplier system table.
[0052] SYSID PROVIDER_CODE SYSTEM_CODE VERSION 100001 Yunqi Datamiddleplatform V1.0.0 100002 Yunqi Smartform V2.0.0
[0053] SYSID in the supplier system table is the first system number column; PROVIDER_CODE is the supplier column; SYSTEM_CODE is the system number column; VERSION is the version number column.
[0054] The following table shows an example of a security protection data table.
[0055] SYSID DATAWAREHOUSE TABLE_ID SCHEMA TABLENAME_EN TABLENAME_CHN 100001 ODS 800001 I Staffinfo Faculty and Staff Information Sheet 100001 ODS 800002 I Userinfo User Information Table 100001 ODS 800003 I Schoolinfo School Information Sheet 100001 DWD 900001 I DWD_STAFFINFO Faculty and Staff Information Sheet
[0056] SYSID in the security protection data table is the second system number column; DATAWAREHOUSE is the data warehouse hierarchical column, ODS represents the source layer, and DWD represents the standard layer; TABLE_ID is the first data table code column; SCHEMA is the database mode column; TABLENAME_EN is the table English name column; TABLENAME_CHN is the table Chinese name column.
[0057] The following table shows an example of a data security policy relationship table.
[0058] SYSID TABLE_ID COLUMN_EN COLUMN_CHN POLICY_ID 100001 800001 XM Name 4000101 100001 800001 DHMH telephone number 4000102 100001 800001 JbXj ID number 4000103
[0059] SYSID in the data security policy relationship table is the third system number column; TABLE_ID is the second data table code column; COLUMN_EN is the field English name column; COLUMN_CHN is the field Chinese name column; POLICY_ID is the data security policy code column, and different codes in this column correspond to different data security policies.
[0060] like Figure 3 and Figure 4 As shown in the figure, the recommended results of data security policies are arranged in ascending order of level, including data classification policy, data operation policy and desensitization policy;
[0061] The data classification strategy is to classify metadata into level 1, level 2 and level 3 according to the importance of metadata. The classification examples are as follows: Level 1 data: once the data is leaked, tampered, damaged, or illegally obtained, illegally used, or illegally shared, it will cause general harm or no harm to the rights and interests of individuals and organizations; Level 2 data: once the data is leaked, tampered, damaged, or illegally obtained, illegally used, or illegally shared, it will cause serious harm to the rights and interests of individuals and organizations; Level 3 data: once the data is leaked, tampered, damaged, or illegally obtained, illegally used, or illegally shared, it will cause particularly serious harm to the rights and interests of individuals and organizations, or cause general harm to economic operations, social order, and public interests.
[0062] The desensitization strategy is to change the sensitive information in the metadata through masking, hashing, truncation or encryption operations. Among them, masking operations include date type masking, phone number masking, MAC address masking, IPv4 masking, IPv6 masking, IMEI mobile device identification masking, email masking, bank card number masking, ID card number masking, retaining the first n and then m, masking the first n and then m, retaining from x to y, masking from x to y, name masking, etc., replacing part of the sensitive data with a mask to hide part of the sensitive data; hashing operations include MD5, SHA-1, SHA-256, HMAC and other algorithms for processing sensitive information, which can replace the content of sensitive data and replace the original sensitive data with a fixed-length hash value, which is convenient for storage and can reduce the risk of sensitive data leakage; truncation operations include date type truncation, vertical type truncation and character displacement processing to achieve truncation of part or all of the sensitive data and limit the access scope of sensitive data; encryption operations include DES algorithm encryption or AES algorithm encryption to protect the confidentiality of data.
[0063] Data operation strategies include query metadata and release metadata. The release metadata in the data operation strategy is to further classify metadata into three categories: unconditional sharing, conditional sharing, and non-sharing after executing the data classification strategy, and set a desensitization algorithm for conditional sharing metadata above level 2.
[0064] Get data security policy recommendations from the data security knowledge base by querying the marked supplier fields:
[0065] 1) If the supplier field, system number field and version field of the metadata all exist in the supplier system table of the data security knowledge base, then further query the corresponding first data table code column, second data table code column and data security policy code column in the data security policy relationship table. If the content of the first data table code column corresponding to the supplier field is the same as the content of the second data table code column, and there is valid data in the data security policy code column, then select the data corresponding to the data security policy code as the data security policy recommendation result;
[0066] 2) If the supplier field, system number field and version field of the metadata all exist in the supplier system table of the data security knowledge base, then further query the corresponding first data table code column, second data table code column and data security policy code column in the data security policy relationship table. If the content of the first data table code column corresponding to the supplier field is the same as that of the second data table code column, but there is no valid data in the data security policy code column, or the content of the first data table code column corresponding to the supplier field is different from that of the second data table code column, then select the data corresponding to the lowest level data security policy code as the data security policy recommendation result; and fill the currently generated lowest level data security policy code into the data security policy code column of the data security policy relationship table;
[0067] 3) If the supplier field, system number field and version field of the metadata do not exist in the supplier system table of the data security knowledge base, the data corresponding to the lowest-level data security policy code is automatically selected or manually selected as the data security policy recommendation result; and the currently generated lowest-level data security policy code is filled in the data security policy code column of the data security policy relationship table. If there is a corresponding data security policy recommendation result in the data security knowledge base, the data corresponding to the data security policy code is selected; if there is a corresponding data security policy recommendation result in the data security knowledge base, the system automatically generates or manually selects and enters it, which can also form the corresponding data security policy recommendation result.
[0068] After the implementation workbench obtains the recommended results of the data security policy, it further generates an updated data security policy. This is to add or delete the content of the data warehouse hierarchical column of the security protection data table in combination with the system fields of the metadata after obtaining the recommended results of the data security policy. The adding operation here is to store the field content corresponding to the data security policy recommendation result in the security protection data table. If there is no completely identical historical record in the security protection data table, the current data security policy recommendation result is added to the content of the data warehouse hierarchical column; if it is found that there is a historical record in the security protection data table that is completely identical to the data security policy recommendation result, the deletion operation is taken to delete the completely identical historical record and save the current data security policy recommendation result to the content of the data warehouse hierarchical column.
[0069] Reference Figure 1 On the one hand, the updated data security policy is synchronized to the data governance subsystem and the data security knowledge base respectively. After the updated data security policy is generated, the data security policy knowledge corresponding to the updated data security policy is saved and merged into the preset supplier system table, security protection data table and data security policy relationship table of the data security knowledge base. The data security policy knowledge includes the supplier, system number, version number, data warehouse layer, data table encoding, database mode, table English name, table Chinese name, field English name, field Chinese name and data security policy encoding field set in sequence. Each field of the data security policy knowledge corresponds to the non-system number column of the supplier system table, security protection data table and data security policy relationship table. The obtained data security policy knowledge generates corresponding records in the supplier system table, security protection data table and data security policy relationship table as a reference for subsequent data governance of the same type of project, thereby realizing knowledge reuse.
[0070] On the other hand, the present invention also provides a data governance method for identifying data security policies based on knowledge management, which is configured with the above-mentioned data governance system for identifying data security policies based on knowledge management, and the method comprises the following steps:
[0071] S1: Collect metadata: Call the data governance subsystem to collect metadata;
[0072] S2: Implement the workbench to observe the metadata obtained by the data governance subsystem and identify the metadata that needs to add data security policies;
[0073] S3: The implementation workbench obtains data security policy recommendation results from the data security knowledge base;
[0074] S4: adjust and supplement the data security policy to obtain an updated data security policy;
[0075] S5: Save the updated data security policy to the data security knowledge base;
[0076] S6: Synchronize the updated data security policy to the data governance subsystem;
[0077] S7: The data governance subsystem implements the updated data security policy.
[0078] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the protection scope of the present invention.
Claims
1. A data governance system based on knowledge management to identify data security policies, characterized in that: include: Data governance subsystem, used to collect metadata; Data security knowledge base, used to store data security policies and provide data security policy recommendation results to the implementation workbench; Implement a workbench to interact with the data governance subsystem and data security knowledge base respectively; It is used to observe and mark metadata that needs to add data security policies, obtain data security policy recommendation results from the data security knowledge base, and further generate updated data security policies. The updated data security policies are synchronized to the data governance subsystem and the data security knowledge base respectively; Among them, the data governance subsystem also implements updated data security policies.
2. According to claim 1, a data governance system based on knowledge management to identify data security policies is characterized in that: The metadata collected by the data governance subsystem includes the first source data of the external system and the second source data of the data warehouse of the data governance subsystem; the first source data includes the supplier, system, version, data source type, IP, port, user and password fields; the second source data includes the schema name, table English name, table comment, field English name, field comment, data type, whether it is required and whether it is a primary key field.
3. A data governance system based on knowledge management to identify data security policies according to claim 2, characterized in that: The implementation workbench observes and marks the metadata that needs to add data security policies. This is to observe the metadata collected by all data governance subsystems, and mark the obtained vendor, system, version, user name, password, table English name, table comment, and field English name fields; the marked fields are the fields of the recommended results of the data security policy to be added.
4. A data governance system based on knowledge management to identify data security policies according to claim 3, characterized in that: The data security knowledge base presets mutually related supplier system tables, security protection data tables and data security policy relationship tables; wherein the supplier system table includes a first system number column, a supplier column, a system number column and a version number column in sequence; the security protection data table includes a second system number column, a data warehouse layering column, a first data table coding column, a database mode column, a table English name column and a table Chinese name column; the data security policy relationship table includes a third system number column, a second data table coding column, a field English name column, a field Chinese name column and a data security policy coding column; the contents of the marked fields of the implementation workbench are compared with the contents of each row of the supplier system table, the security protection data table and the data security policy relationship table preset in the data security knowledge base, and the data security policy recommendation results are obtained from the data security knowledge base; the contents of the first system number column, the second system number column and the third system number column are only used as sequence numbers; the contents of the first data table coding column and the second data table coding column are the same.
5. A data governance system based on knowledge management to identify data security policies according to claim 3, characterized in that: The data security policy recommendation results are obtained from the data security knowledge base by querying the marked supplier fields: 1) If the supplier field, system number field and version field of the metadata all exist in the supplier system table of the data security knowledge base, then further query the corresponding first data table code column, second data table code column and data security policy code column in the data security policy relationship table. If the content of the first data table code column corresponding to the supplier field is the same as the content of the second data table code column, and there is valid data in the data security policy code column, then select the data corresponding to the data security policy code as the data security policy recommendation result; 2) If the supplier field, system number field and version field of the metadata all exist in the supplier system table of the data security knowledge base, then further query the corresponding first data table code column, second data table code column and data security policy code column in the data security policy relationship table. If the content of the first data table code column corresponding to the supplier field is the same as the content of the second data table code column, but there is no valid data in the data security policy code column, or the content of the first data table code column corresponding to the supplier field is different from the content of the second data table code column, then select the data corresponding to the lowest level of data security policy code as the data security policy recommendation result; And fill the currently generated lowest-level data security policy code into the data security policy code column of the data security policy relationship table; 3) If the vendor field, system number field, and version field of the metadata do not exist in the vendor system table of the data security knowledge base, the data corresponding to the lowest-level data security policy code is automatically selected or manually selected as the data security policy recommendation result; And fill the currently generated data security policy code with the lowest level into the data security policy code column of the data security policy relationship table.
6. A data governance system based on knowledge management to identify data security policies according to claim 5, characterized in that: The recommended results of data security policies are arranged in ascending order of level, including data classification policy, data operation policy and desensitization policy; The data classification strategy is to classify metadata into level 1, level 2, and level 3 according to the importance of metadata from small to large; Desensitization strategy is to change sensitive information in metadata through masking, hashing, truncation or encryption operations; Data operation strategies include two categories: querying metadata and publishing metadata.
7. A data governance system based on knowledge management to identify data security policies according to claim 6, characterized in that: The published metadata in the data operation strategy is to further classify the metadata into three categories: unconditional sharing, conditional sharing, and non-sharing after executing the data classification strategy, and set a desensitizing algorithm for conditional sharing metadata above level 2.
8. The data governance system based on knowledge management and data security policy identification according to claim 5 is characterized in that: The further generation of the updated data security policy is that after the implementation workbench obtains the data security policy recommendation result, it combines the system field of the metadata to add or delete the content of the data warehouse hierarchical column of the security protection data table.
9. A data governance system based on knowledge management to identify data security policies according to claim 8, characterized in that: The updated data security policy is synchronized to the data governance subsystem and the data security knowledge base respectively. On the one hand, after the updated data security policy is generated, the data security policy knowledge corresponding to the updated data security policy is saved and merged into the preset supplier system table, security protection data table and data security policy relationship table of the data security knowledge base. The data security policy knowledge includes the supplier, system number, version number, data warehouse layer, data table encoding, database model, table English name, table Chinese name, field English name, field Chinese name and data security policy encoding field set in sequence. Each field of the data security policy knowledge corresponds one by one to the non-system number column of the supplier system table, security protection data table and data security policy relationship table.
10. A data governance method based on knowledge management to identify data security policies, configured with a data governance system based on knowledge management to identify data security policies according to any one of claims 1 to 9, characterized in that: The method comprises the following steps: S1: Collect metadata: Call the data governance subsystem to collect metadata; S2: Implement the workbench to observe the metadata obtained by the data governance subsystem and identify the metadata that needs to add data security policies; S3: The implementation workbench obtains data security policy recommendation results from the data security knowledge base; S4: adjust and supplement the data security policy to obtain an updated data security policy; S5: Save the updated data security policy to the data security knowledge base; S6: Synchronize the updated data security policy to the data governance subsystem; S7: The data governance subsystem implements the updated data security policy.
Citation Information
Patent Citations
Data security intelligent reinforcement system and method
CN113032793A
Big data platform data desensitization system
CN115664785A
Data asset management method and system
CN116541372A
Data management system for identifying master data based on knowledge management
CN117992443A
Data management system for formulating data standard based on knowledge management
CN118427181A
