Does Reltio support Data Masking for certain attributes?

Question

Does Reltio support Data Masking? We would want to mask specific attributes.

Answer

There are several options to consider when performing the requirements you are asking for.

Option 1: For vertical and business configurations of attributes, you can use "hidden=true" in the attribute configuration.  This property is optional. It allows marking an attribute as hidden. The hidden attributes will only be present in the response when the sendHidden option is used in the request. This flag can be used by applications to determine when to display characteristics of attributes. For example, the Hub does not display attributes marked as hidden. Default: false.

{
    "uri": "configuration/entityTypes/HCP/attributes/Name",
    "label": "Name",
    "name": "Name",
    "description": "Name",
    "type": "String",
    "hidden": true,
    "important": false,
    "searchable": true,
    "attributeOrdering": {
        "orderType": "ASC",
        "orderingStrategy": "LUD"
    },
    "skipInDataAccess": true
}

Option 2: We can add property masking for vertical and business configuration of attributes. NOTE: This feature is an "as-is" feature as it is not fully implemented.

Example:

• If maskMatched = true, then we need to find a value matching regexPattern and apply the mask to this part of the value.
• If maskMatched = false, then we need to find a value matching regexPattern and apply the mask to the rest of the value.

"attributes": [ 
                { 
                    "uri": "configuration/entityTypes/HCP/attributes/FullName", 
                    "name": "FullName", 
                    "label": "Full Name", 
                    "type": "String", 
                    "hidden": false, 
                    "masking": { 
                        "regexPattern": ".*", 
                        "maskMatched": true 
                    } 
                },

• The sendMasked option can mask attribute values in the GET API response if the attribute has a "masking" property in the L2 or L3 configuration.  
   
  Attributes that can be masked include:
  
  • String attributes (e.g., FullName, Name)
  • Boolean attributes (e.g., BooleanAttr)
  • Integer attributes (e.g., NumberAttr)
  • Date attributes (e.g., DateAttr)
  • Nested attributes (e.g., NestedAttr, Email)
  • Specific attributes like CardNumber2, CardNumber3, EmptyMaskingAttr, NotMatchedAttr, AllMatchedAttr, and Address.

Include the sendMasked option in an API GET entity/<id> call as part of the options parameter in your request.

Example Usage

Request:

GET {TenantURL}/entities/{entityId}?options=sendMasked