Universal method for automatic desensitization based on data dictionary development state

By uniformly managing the data dictionary desensitization attributes and codes during the design, development and operation stages, the problem of data desensitization in the existing technology is solved, and the security management and efficiency of data throughout the entire life cycle is achieved. desensitization treatment.

CN118965425AInactive Publication Date: 2024-11-15RURAL CREDIT BANKS FUNDS CLEARING CENT CO LTD

Patent Information

Application Number
CN202410974415.2
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-07-19
Publication Date
2024-11-15
Estimated Expiration
Not applicable · inactive patent

AI Technical Summary

Technical Problem

Existing data desensitization technologies cannot be managed uniformly at all stages of system design, development and operation, rely on project documentation quality and developer subjective initiative, resulting in low efficiency and error-proneness, lack of universality and scalability.

Method used

By configuring the data dictionary desensitization attributes during the design stage, generating association annotations and desensitization codes, linking data dictionary services during the development stage, realizing data modeling and desensitization code generation, and automatically performing desensitization processing during the operation stage, supporting multiple desensitization Responsive rules and methods.

Benefits of technology

It realizes the security management of data throughout the life cycle, reduces project document dependence, improves coding quality and test coverage, enhances data security and flexibility, and adapts to different application scenarios.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118965425A_ABST
    Figure CN118965425A_ABST
Patent Text Reader

Abstract

The invention is suitable for the technical field of data processing, and provides a universal method for automatic desensitization based on a data dictionary development state, which comprises the following steps: a design stage: configuring a data dictionary desensitization attribute; identifying a business field with a high security level, performing desensitization attribute maintenance by using a data dictionary related tool, and storing the business field in a database through a research and development asset management module of the unified development platform; in the development stage, associated annotations and desensitization codes are generated; data dictionary services are linked in the micro-service application development process, and preprocessing is provided for subsequent stages through application data modeling, data model reference and desensitization code generation; in the operation stage, the associated annotation and the desensitization code are analyzed and processed; and when the micro-service runs, automatically performing desensitization processing according to the desensitization annotation and the code. According to the method, the security of application data is remarkably improved, the system design and implementation process are optimized, the development and maintenance cost is reduced, and meanwhile, a good foundation is provided for future extension and self-definition.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention belongs to the field of data processing technology, and in particular relates to a general method for automatic desensitization based on data dictionary development. Background Art

[0002] There are generally two existing technical solutions for desensitizing sensitive data. One solution is to perform data desensitization during the system development and operation stages. During the development process, the data items that need to be desensitized are desensitized in a hard-coded manner in the log output link based on the requirements or design documents. This method lacks flexibility and has too high code intrusion. Or dynamic desensitization during operation is achieved through DTO / PO annotation declarations to avoid hard coding. Regardless of the method, it fails to be combined with the design stage, relies on the subjective initiative of developers, and increases the mental burden and time cost during the development and code review process. The other method is mainly to solve the log desensitization during the storage, aggregation and statistics process after the system log is generated. Generally, the big data platform extracts unstructured log data into the corresponding storage system, and then desensitizes the log through data cleaning conversion or AI tools. This solution cannot solve the log desensitization processing during the system operation.

[0003] The existing data desensitization solutions have the following disadvantages: (1) They cannot cover all stages of system design, development, and operation, can only solve local problems, cannot combine data dictionary and desensitization processing, and cannot form closed-loop management. (2) They rely on the writing quality of project documents and the sophistication of project management, and have high requirements on the coding quality, code review, and test coverage of the development and testing links, resulting in low efficiency and prone to errors. (3) They are used in a single way and lack versatility and extensibility. To this end, the present invention proposes a general method for automatic desensitization based on data dictionary development. Summary of the invention

[0004] The purpose of the present invention is to provide a general method for automatic desensitization based on data dictionary development, aiming to solve the problems raised in the above background technology.

[0005] To achieve the above object, the present invention provides the following technical solutions:

[0006] A general method for automatic desensitization based on data dictionary development includes the following steps:

[0007] Step 1, Design phase: Configure the data dictionary desensitization attributes; identify high-security business fields according to financial data specifications, use data dictionary related tools to maintain desensitization attributes, and then store business metadata in the data dictionary library;

[0008] Step 2, Development phase: Generate associated annotations and desensitized codes; Link the data dictionary service in the microservice application development process, and provide pre-processing for subsequent stages through application data modeling, data model reference, and desensitized code generation;

[0009] Step 3, Operation phase: parse and process associated annotations and desensitized codes; when the microservice is running, desensitization is automatically performed based on the desensitized annotations and codes.

[0010] Furthermore, the specific process of step 1 is as follows:

[0011] Step 11: Data dictionary structure design: Add desensitization attributes to the description of business metadata in the data dictionary, including data classification, desensitization flags, and desensitization rules;

[0012] Step 12, Data dictionary management terminal design: provide an independent management page, use VUE technology to achieve data dictionary template generation, data import, addition, deletion, modification, batch maintenance, approval, release and audit;

[0013] Step 13: Data dictionary backend service design: provide backend functions for data dictionary maintenance, including metadata query, metadata addition, and metadata modification;

[0014] Step 14: Business metadata maintenance: Based on the financial data specifications and combined with the business model, identify the business metadata that needs to be desensitized and configure the desensitization flag and desensitization rule attributes, and persist the business metadata to the data dictionary library through the data dictionary management terminal and the data dictionary background service.

[0015] Furthermore, the desensitization flag indicates whether desensitization is required, 1 means desensitization, and 0 means no desensitization; the desensitization rule values ​​are: base64, des, 3des, aes, sm4, default and custom extension.

[0016] Furthermore, the specific process of step 2 is as follows:

[0017] Step 21, Application Data Modeling: Abstract business data based on the data dictionary, determine the business attributes, field types and constraint rules of the database and interface data, and finally form the business entity object DTO / PO, where the constraint rules include data masking related information;

[0018] Step 22, data model reference: The low-code development platform selects the established business entity object DTO / PO to develop business logic; obtains the desensitization flag and desensitization rules defined by the dictionary metadata;

[0019] Step 23, desensitizing code generation: First, the low-code development platform calls the data dictionary background service during the DTO / PO creation process, and creates data entities based on the metadata content, including desensitizing annotation declarations; then, the low-code development platform identifies the log record logic scenario, parses it and generates desensitizing processing code.

[0020] Furthermore, the specific process of step 23 is as follows:

[0021] Step 231, generate desensitizing annotation: When generating DTO / PO, the low-code platform first generates an intermediate Json file based on the data dictionary, and then generates Java code; the desensitizing annotation is @MaskField, which is marked on the specific field of the DTO / PO data entity;

[0022] Step 232, generate local (coding method) desensitization processing code: identify the log record logic scenario, parse it, and when printing the log, the low-code platform automatically generates explicit call Mask.of method code according to the annotation information for unified desensitization processing;

[0023] Step 233, global desensitization processing mechanism: It also supports global desensitization of log records under the Logger object by configuring the log name (Logger object).

[0024] Furthermore, the step 3 comprises the following steps:

[0025] Step 31, Mask.of design;

[0026] Step 32, Mask.of executes;

[0027] Step 33: Global desensitization logic.

[0028] Furthermore, the specific process of step 3 is as follows:

[0029] Step 31: Mask.of design, including:

[0030] Step 311: Use Jackson to convert the object to a Json string;

[0031] Step 312: Use a customized Jackson serializer to process fields modified by @MaskField.

[0032] Step 313: The field content processed by the customized Jackson desensitizing serializer will call the mask rule specified by @MaskField for desensitization;

[0033] Step 314: Use the desensitized content as the value corresponding to the field key;

[0034] Step 315: Finally, the Json string content of the desensitized object is sent to Slf4j for log output;

[0035] Step 32: Mask.of is executed, specifically including:

[0036] Step 321, internally generate a MaskObject object according to the entity value passed in;

[0037] Step 322, MaskObject rewrites the toString method, and the log engine triggers the desensitization process by calling toString;

[0038] Step 323: The rewritten toString triggers desensitization processing for the entity value object type;

[0039] Step 33: Global desensitization logic, specifically including:

[0040] Step 331, extend the RewritePolicy interface of log4j2 to intercept the LogEvent object, the object contains DTO / PO information;

[0041] Step 332: Match the corresponding LoggerName object and the corresponding desensitization rule based on the ant style according to loggerName;

[0042] Step 333: pass the desensitized information parameter to the desensitization rule;

[0043] Step 334: perform desensitization processing according to the configured rules, call the doMask method specifically implemented by the desensitization rules to process and return the desensitized content;

[0044] Step 335: Reconstruct the desensitized content into a new LogEvent and pass it to the appender for log output printing.

[0045] Furthermore, the specific process of step 323 is as follows:

[0046] a. ObjectMapper#writeValueAsString based on Jackson;

[0047] b.writeValueAsString uses Jackson internally to convert the object into a Json string;

[0048] c. During the conversion process, the changeProperties of Jackson's BeanSerializerModifier scans the field annotation properties of the desensitized entity value object, and uses a customized desensitizing JsonSerializer for the marked annotated fields. The JsonSerializer is bound to the desensitizing rules specified in @MaskField;

[0049] d. When the marked annotated field is serialized in Json, the corresponding desensitization rule IMaskRule in @MaskField in JsonSerializer is called, and the desensitized value is passed in to call the IMaskRule#mask method to get the desensitized value;

[0050] e. The field content processed by JsonSerializer is anonymized.

[0051] Compared with the prior art, the present invention has the following beneficial effects:

[0052] The present invention ensures the security of data throughout the entire life cycle and forms a closed-loop management by implementing data desensitization in each stage of design, development and operation. Due to the unified definition and maintenance of the data dictionary, the dependence on the quality of project document writing and the sophistication of project management is reduced, the efficiency of coding quality, code review and test coverage is improved, and the error rate is reduced. By supporting a variety of desensitization rules and usage methods, the solution has better versatility and extensibility, and can adapt to different application scenarios and needs. Based on the pre-definition and release of data dictionary metadata on the management side, the management problems in the system design stage are solved, and the loopholes in design management are made up in combination with the user system, and data security is enhanced. Combined with the development platform, the workload of developers in data desensitization is greatly reduced, and the influence of subjective and objective factors of developers on log desensitization operations is shielded. Supports user-defined desensitization rules, and seamlessly integrates these rules into the desensitization system, providing higher flexibility and adaptability. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] Figure 1 It is a flow chart of the present invention.

[0054] Figure 2 This is a page diagram of the data dictionary management terminal in the present invention. DETAILED DESCRIPTION

[0055] In order to make the purpose, technical solution and advantages of the present invention more clearly understood, the present invention is further described in detail below in conjunction with the accompanying drawings and examples. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not intended to limit the present invention.

[0056] The specific implementation of the present invention is described in detail below in conjunction with specific embodiments.

[0057] like Figure 1 As shown, a general method for automatic desensitization based on data dictionary development state provided by an embodiment of the present invention includes the following steps:

[0058] Step 1, design phase: configure data dictionary desensitization attributes; mainly to manage and implement business metadata, identify high-security business fields according to financial data specifications, and use data dictionary related tools to maintain desensitization attributes, and store them in the database through the R&D asset management module of the unified development platform for use in subsequent development stages. The specific process of step 1 is as follows:

[0059] Step 11, Data dictionary structure design: Add desensitization attributes to the description of business metadata, including data classification, desensitization flag and desensitization rules; the desensitization flag value is: 1- desensitization; 0- no desensitization. The desensitization rule value is: base64, des, 3des, aes, sm4, default and custom extension. The complete description of metadata is shown in Table 1:

[0060] Table 1

[0061]

[0062]

[0063] In the data dictionary structure, the reference specifications are as follows:

[0064] "Bank Data Standard Definition Specification" P4 Chinese name, English name, data type;

[0065] "Personal Financial Information Protection Technical Specifications" P17 Anti-tampering;

[0066] "Financial Data Security Data Security Grading Guide" Overview of P2 and P6 security levels.

[0067] Step 12, Data dictionary management terminal design: The data dictionary provides an independent management page, which can be embedded in the development platform and user management system. Based on the mainstream front-end VUE technology, it can realize data dictionary template generation, data import, addition, deletion, modification, batch maintenance and approval and release; the data dictionary management terminal page is as follows Figure 2 shown.

[0068] Step 13. Design of data dictionary background service: The data dictionary background service is an independent public microservice that provides background functions for data dictionary maintenance, including metadata query, metadata addition, and metadata modification. The dictionary service interface is as follows:

[0069] Metadata query: GET / amdp-portal / businessDict / findByDictId;

[0070] Metadata query: GET / amdp-portal / businessDict / findByTitle;

[0071] Metadata addition: POST / amdp-portal / businessDict / save;

[0072] Metadata modification: PUT / amdp-portal / businessDict / update.

[0073] Step 14, business metadata maintenance: According to the "Technical Specifications for the Protection of Personal Financial Information" and "Financial Data Security Classification Guidelines" and combined with the business model, identify the business metadata that needs to be desensitized and configure the desensitization flag and desensitization rule attributes. Finally, the business metadata will be persisted in the data dictionary library through the data dictionary management end and the data dictionary background service, providing a data foundation for subsequent unified automated processing.

[0074] Step 2, development phase: Generate associated annotations and desensitized codes; Link the data dictionary service in the microservice application development process, and provide pre-processing for subsequent stages through application data modeling, data model reference, and desensitized code generation; The specific process of step 2 is as follows:

[0075] Step 21, Application Data Modeling: Data modeling refers to the abstraction of business data, determining the scope of database and interface data, data organization and constraints, etc., and then converting it into physical data objects (DTO / PO). The full name of PO is persistent object, and the full name of DTO is data transfer object.

[0076] The basis of data modeling on the Taichu Platform (Taichu Platform of the Rural Credit Bank Center) is the data dictionary, and all data entities come from the metadata of the data dictionary. Simply put, the process of applying data modeling is to select the metadata in the data dictionary to form a complete business data entity, and finally form a business entity object DTO / PO for program interaction processing.

[0077] Step 22, data model reference: During application development, data model reference is performed based on business characteristics. Technically, this process uses the low-code development platform to select the established business entity object DTO / PO for business logic development; since the member data of the business entity object DTO / PO all come from the data dictionary metadata, the desensitization flags and desensitization rules defined in the dictionary metadata can be obtained. The desensitization annotation technology is used to pass it back to the operation stage for unified processing.

[0078] Step 23, desensitized code generation: First, the low-code development platform calls the data dictionary background service during the DTO / PO creation process, and creates data entities based on the metadata content, including desensitized annotation declarations; then, when the low-code development platform recognizes the logging logic or the developer actively calls the platform logging component, it will perform annotation parsing; in addition, it also supports specifying the Logger object through the configuration file, thereby achieving global desensitization of all logging behaviors in the class where the Logger object is located.

[0079] The specific process of step 23 is as follows:

[0080] Step 231, generate desensitized annotations: When generating DTO / PO, the low-code development platform first generates an intermediate Json (JavaScript Object Notation) file based on the data dictionary, and then generates Java code. The generated Json file is as follows:

[0081] Table 2

[0082]

[0083] The masking annotation is @MaskField, which will be marked on the specific field of the DTO / PO data entity; as shown below:

[0084] Table 3

[0085]

[0086] The generated Java code is as follows:

[0087] Table 4

[0088]

[0089] The following is an example of the automatic desensitization code for the log output user entity data information automatically generated by the low-code development tool:

[0090] Table 5

[0091]

[0092] Step 232, generate encoding method desensitization processing code: When generating code, the low-code development platform uses the encoding method by default for data entities that need to be desensitized. This method explicitly calls the Mask.of(DTO / PO data entity) method to perform unified desensitization processing when printing logs.

[0093] The Mask.of method is as follows:

[0094] Table 6

[0095]

[0096] The following is an example of the automatic desensitization code for the log output user entity data information automatically generated by the low-code development tool:

[0097] Table 7

[0098]

[0099] Step 233, configure the desensitization processing of log name matching method: Considering the versatility and non-intrusiveness, the platform also supports the configuration of Logger method to achieve global desensitization of log records under the Logger object. This method is the same as the coding method at the DTO / PO level. Developers only need to configure the desensitization target Logger object name, and the logging statement can achieve desensitization without any intrusive code, but the cost is the performance overhead of traversing object fields.

[0100] The configuration content is as follows (example in yaml format):

[0101] Table 8

[0102]

[0103] Step 3, Operation phase: parse and process associated annotations and desensitized codes; when the microservice is running, desensitization is automatically performed based on the desensitized annotations and codes.

[0104] The specific process of step 3 is as follows:

[0105] Step 31: Mask.of design, including:

[0106] Step 311: Use Jackson to convert the object to a Json string;

[0107] Step 312: Use a customized Jackson serializer to process fields modified by @MaskField.

[0108] Step 313: The field content processed by the customized Jackson desensitizing serializer will call the mask rule specified by @MaskField for desensitization;

[0109] Step 314: Use the desensitized content as the value corresponding to the field key;

[0110] Step 315: Finally, the Json string content of the desensitized object is sent to Slf4j for log output;

[0111] Step 32, Mask.of (DTO / PO data entity) execution, including:

[0112] Step 321, internally generate a MaskObject object according to the entity value passed in;

[0113] Step 322, MaskObject rewrites the toString method, and the log engine triggers the desensitization process by calling toString;

[0114] Step 323: The rewritten toString triggers the desensitization process for the entity value object type. The specific process is as follows:

[0115] a. ObjectMapper#writeValueAsString based on Jackson;

[0116] b.writeValueAsString uses Jackson internally to convert the object into a Json string;

[0117] c. During the conversion process, the changeProperties of Jackson's BeanSerializerModifier scans the field annotation attributes of the desensitized entity value object, and uses a customized desensitizing JsonSerializer for the marked annotated fields (JsonSerializer will be bound to the desensitization rules specified in @MaskField);

[0118] d. When the marked annotated field is serialized in Json, the corresponding desensitization rule IMaskRule in @MaskField in JsonSerializer is called, and the desensitized value is passed in to call the IMaskRule#mask method to get the desensitized value;

[0119] e. The field content processed by JsonSerializer is the desensitized content

[0120] Step 33: Basic desensitization rules and corresponding processing methods are as follows:

[0121] Table 9

[0122]

[0123] Step 34: Global desensitization logic, including:

[0124] Step 341, extend the RewritePolicy interface of log4j2 to intercept the LogEvent object, which contains DTO / PO information;

[0125] Step 342, matching the corresponding LoggerName object and the corresponding desensitization rule (IMaskRule specific implementation) based on the ant style according to loggerName;

[0126] Step 343: pass the desensitized information parameters (DTO / PO) to the desensitization rules;

[0127] Step 344: perform desensitization processing according to the configured rules, call the doMask method specifically implemented by the desensitization rules to process and return the desensitized content;

[0128] Step 345: Reconstruct the desensitized content into a new LogEvent and pass it to the appender for log output printing.

[0129] In the embodiment of the present invention, desensitization rules are replaced: this solution presets encryption desensitization (base64, des, 3des, aes, sm4), full desensitization (default), semi-desensitization (custom extension) and other methods, and other desensitization rules can also be used.

[0130] Annotation declaration alternative: This solution uses the annotation mode, and can also be in the form of a configuration file or database. All DTO / PO are placed in the medium and processed during code generation.

[0131] ToString method replacement: This solution uses the reconstructed toString method. Other methods can also be used to handle desensitization.

[0132] Json and Jackson alternatives: This solution parses DTO / PO objects by converting them into Json and processing them using the Jackson framework. It can also use other data structures such as key:value, map, etc., or use other Json frameworks such as Gson.

[0133] The above are only preferred embodiments of the present invention. It should be pointed out that, for those skilled in the art, several modifications and improvements can be made without departing from the concept of the present invention. These should also be regarded as the protection scope of the present invention. These will not affect the effect of the implementation of the present invention and the practicality of the patent.

Claims

1. A general method for automatic desensitization based on data dictionary development, characterized in that: The following steps are involved: Step 1, Design phase: Configure data dictionary desensitization attributes; According to financial data specifications, identify business fields with high security levels, use data dictionary related tools to maintain desensitized attributes, and then store business metadata in the data dictionary library; Step 2, Development phase: Generate associated annotations and desensitized codes; In the process of microservice application development, the data dictionary service is linked to provide pre-processing for subsequent stages through application data modeling, data model reference, and desensitized code generation; Step 3, running stage: parse and process associated annotations and desensitized codes; When the microservice is running, desensitization is automatically performed based on the desensitization annotations and codes.

2. The general method for automatic desensitization based on data dictionary development state according to claim 1 is characterized in that: The specific process of step 1 is as follows: Step 11: Data dictionary structure design: Add desensitization attributes to the description of business metadata in the data dictionary, including data classification, desensitization flags, and desensitization rules; Step 12, Data dictionary management terminal design: provide an independent management page, use VUE technology to achieve data dictionary template generation, data import, addition, deletion, modification, batch maintenance, approval, release and audit; Step 13: Data dictionary backend service design: provide backend functions for data dictionary maintenance, including metadata query, metadata addition, and metadata modification; Step 14: Business metadata maintenance: Based on the financial data specifications and combined with the business model, identify the business metadata that needs to be desensitized and configure the desensitization flag and desensitization rule attributes, and persist the business metadata to the data dictionary library through the data dictionary management terminal and the data dictionary background service.

3. The general method for automatic desensitization based on data dictionary development state according to claim 2 is characterized in that: The desensitization flag indicates whether desensitization is required, 1 means desensitization, and 0 means no desensitization; the desensitization rule values ​​are: base64, des, 3des, aes, sm4, default and custom extension.

4. The general method for automatic desensitization based on data dictionary development state according to claim 1 is characterized in that: The specific process of step 2 is as follows: Step 21, Application Data Modeling: Abstract business data based on the data dictionary, determine the business attributes, field types and constraint rules of the database and interface data, and finally form the business entity object DTO / PO, where the constraint rules include data masking related information; Step 22, data model reference: The low-code development platform selects the established business entity object DTO / PO to develop business logic; obtains the desensitization flag and desensitization rules defined by the dictionary metadata; Step 23, desensitized code generation: First, the low-code development platform calls the data dictionary background service during the DTO / PO creation process to create data entities based on the metadata content, including desensitized annotation declarations; The low-code development platform then identifies the logging logic scenarios, parses them and generates desensitized processing code.

5. The general method for automatic desensitization based on data dictionary development state according to claim 4 is characterized in that: The specific process of step 23 is as follows: Step 231, generate desensitized annotations: When generating DTO / PO, the low-code platform first generates an intermediate Json file based on the data dictionary, and then generates Java code; The desensitization annotation is @MaskField, which is marked on the specific field of the DTO / PO data entity; Step 232, generate local desensitization processing code: identify the log record logic scenario, parse it, and when printing the log, the low-code platform automatically generates explicit call Mask.of method code according to the annotation information for unified desensitization processing; Step 233, global desensitization processing mechanism: supports global desensitization of log records under the Logger object by configuring the Logger object.

6. The general method for automatic desensitization based on data dictionary development state according to claim 1 is characterized in that: The step 3 comprises the following steps: Step 31, Mask.of design; Step 32, Mask.of executes; Step 33: Global desensitization logic.

7. The general method for automatic desensitization based on data dictionary development state according to claim 6 is characterized in that: The specific process of step 3 is as follows: Step 31: Mask.of design, including: Step 311: Use Jackson to convert the object to a Json string; Step 312: Use a customized Jackson serializer to process fields modified by @MaskField. Step 313: The field content processed by the customized Jackson desensitizing serializer will call the mask rule specified by @MaskField for desensitization; Step 314: Use the desensitized content as the value corresponding to the field key; Step 315: Finally, the Json string content of the desensitized object is sent to Slf4j for log output; Step 32: Mask.of is executed, specifically including: Step 321, internally generate a MaskObject object according to the entity value passed in; Step 322, MaskObject rewrites the toString method, and the log engine triggers the desensitization process by calling toString; Step 323: The rewritten toString triggers desensitization processing for the entity value object type; Step 33: Global desensitization logic, specifically including: Step 331, extend the RewritePolicy interface of log4j2 to intercept the LogEvent object, the object contains DTO / PO information; Step 332: Match the corresponding LoggerName object and the corresponding desensitization rule based on the ant style according to loggerName; Step 333: pass the desensitized information parameter to the desensitization rule; Step 334: perform desensitization processing according to the configured rules, call the doMask method specifically implemented by the desensitization rules to process and return the desensitized content; Step 335: Reconstruct the desensitized content into a new LogEvent and pass it to the appender for log output printing.

8. The general method for automatic desensitization based on data dictionary development state according to claim 7 is characterized in that: The specific process of step 323 is as follows: a. ObjectMapper#writeValueAsString based on Jackson; b.writeValueAsString uses Jackson internally to convert the object into a Json string; c. During the conversion process, the changeProperties of Jackson's BeanSerializerModifier scans the field annotation properties of the desensitized entity value object, and uses a customized desensitizing JsonSerializer for the marked annotated fields. The JsonSerializer is bound to the desensitizing rules specified in @MaskField; d. When the marked annotated field is serialized in Json, the corresponding desensitization rule IMaskRule in @MaskField in JsonSerializer is called, and the desensitized value is passed in to call the IMaskRule#mask method to get the desensitized value; e. The field content processed by JsonSerializer is anonymized.

Citation Information

Patent Citations

  • Data desensitization method, server and storage medium

    CN107679418A

  • Database modeling system based on data dictionary

    CN114238263A

Cited By

  • High-security software input and output configuration method based on functional module

    CN121255152A