Skip to content

HASH MASK

Description

The HASH MASK processor is designed to apply hash masking to data points during the consolidation phase of data processing. This processor is particularly useful for securing sensitive information such as passwords by applying a hash function to the data, ensuring that the original data cannot be easily retrieved. It supports all primitive data types, making it highly adaptable for various data processing needs.


Config Location

To configure the HASH MASK processor, you need to define it within the consDPProcessors section of your data point configuration within the schema. This involves specifying the processor name and entity.


Supported Data Types

  • Double
  • Integer
  • String

Config Requirements

Config ({}) options are required for the HASH MASK processor. If no configuration is provided or if the configuration is improperly set up, a block violation will be thrown. For more information on Apiro violations and their appearance in the Apiro UI or logs, refer to the violations section.


Example Config

Below is an example of how to configure the HASH MASK processor in XML format:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
<dataPoint name="PASSWORD" dataType="STRING">
    <consDPProcessors>
        <consDPProcessor name="HASH_DATA" entity="HASH_MASK">
            <config>
                <![CDATA[
                    {
                        "inputValue":"password12345",
                        "maskingSalt":"aqQwSxXcfgdejhbJhdygjyfdghjHGYYIdh!66gydshasGY!"
                    }
                ]]>
            </config>
        </consDPProcessor>
    </consDPProcessors>
</dataPoint>

Example Result

Upon successful configuration and execution, the HASH MASK processor will apply a hash function to the "PASSWORD" data point using the provided salt, ensuring that the original password is securely masked.


Config Parameters

name acceptable values comment
inputValue The original value to be hashed. This is the data that will be masked.
maskingSalt A string used as a salt for the hash function. This enhances the security of the hashed value.

Common Mistakes

  • Ensure that the processor name and entity are correctly defined in the configuration to ensure that the processor is correctly identified and applied during the data processing pipeline.
  • Verify that the configuration parameters within the <config> tag are correctly written and match the expected format and values.
  • Remember that the configuration for the HASH MASK processor is required. If no configuration, or improper configuration is provided then a block violation will be thrown.