Protect sensitive data, such as social security numbers, through obfuscation
Sensitive identity data, such as social security numbers, must be managed with respect for personal integrity and in compliance with national regulations. Such data should never be stored in plain text.
This document outlines how to create, edit, and read obfuscated ("hashed") social security number values. The functionality is pipes-based and can be used across all Fortified ID products. The same approach may be applied to other types of sensitive identity data, excluding passwords.
Create
Add these valves to the pipe responsible for creating the identity object.
In the example below, Entra ID serves as the user store, with the scrambled value saved in the user attribute faxNumber
. The user has authenticated via BankID, resulting in the export variable personalNumber
containing the user’s social security number.
Adjust the final valve to match your user store, attribute name, or other specific properties as needed.
Edit
Add these valves to the pipe responsible for editing the identity object.
In the example below, Entra ID serves as the user store, with the scrambled value saved in the user attribute faxNumber
. The user has authenticated via BankID, resulting in the export variable personalNumber
containing the user’s social security number.
Adjust the final valve to match your user store, attribute name, or other specific properties as needed.
Read (lookup)
Add these valves to the pipe responsible for reading the identity object.
In the example below, Entra ID serves as the user store, with the scrambled value saved in the user attribute faxNumber
. The user has authenticated via BankID, resulting in the export variable personalNumber
containing the user’s social security number.
Adjust the final valve to match your user store, attribute name, or other specific properties as needed.
Last updated