JSON File Masking
This feature offers standard functionalities for masking JSON files. Users will now be able to configure and run Continuous Compliance jobs specific to JSON files, assigning algorithms to any field of a JSON file using their respective JSON paths. This feature overcomes the shortfalls of the existing algorithm-based workaround by providing users with a simplified way to assign Continuous Compliance algorithms. This feature also supports masking JSON files of large sizes.
These features are not yet supported:
- Profiling Job for JSON File Rulesets
- Tokenization and Re-Identification for JSON File Rulesets
- Multi-Column Algorithms for JSON File Formats
|POST /file-formats||Added support to upload a Json file to create JSON File Format.|
|PUT /file-formats/||Added validations to stop creating headers and footers for JSON File Formats.|
|POST /file-connectors||Added support to create a new file connector of type
|POST /file-field-metadata||Added support to create a new JSON File field, specifying its JSON path identifier and assigning algorithms to it.|
|PUT /file-field-metadata||Added support to update JSON File field to assign or unassign algorithms to it.|
In the Continuous Compliance interface, navigate to Settings > File Format. Import the JSON file to create JSON File Formats.
In the Create Connection screen, choose File - JSON from the Type dropdown and configure the appropriate details.
The Inventory tab for JSON File Formats is used to configure algorithms to JSON Paths.
Navigate to Monitor > Processing to access the Job Process Monitoring page. This page shows data in byte format for JSON file masking.
Constructing a JSON File Path¶
A JsonPath expression begins with the dollar sign ($) character, which refers to the root element. The dollar sign is followed by a sequence of child elements, which are separated by the square brackets ([‘’]) containing the name of each JSON field. If the field is inside an array, a star character is used to represent all elements of the array ([*]).