Encrypted and hashed custom attribute usage to hide user attributes

[ashachakraborty]

Hi,

If we want to use encrypted/hashed customproperty for few user attributes(e.g.birthday). Can we use those in the rules and also if there is an update on these values how we will take care of that?

I went through few of the forum posts regarding that but still has some questions around this.

It will be great if someone share  any document available for encrypted/hashed customproperty.

[Dhruv_S]

We acknowledge your request. We are looking into relevant documentation and provide you with the links for the same shortly.

[rushikeshvartak]

use hcp1 -5 from users table

HCP

hcp

tinytext

“H” stands for hashing. Specifies that after the data is added in EIC, it is automatically hashed when it is stored in the database and cannot be decrypted. You can use HCP attributes for storing very sensitive information like SSN. As the data is hashed, the only option to validate it is by using the validateUserData API.

https://docs.saviyntcloud.com/bundle/EIC-Database-Schema-Reference/page/Content/Database-Schema-Refe...

[armaanzahir]

Hi @ashachakraborty ,

Conditions on hashed and encrypted attributes are supported in rules as they are available in the dropdown for user attributes in the rules.

You can update these attributes using the updateUser API or when you have a source system mapping for user import if that was your question.

Database Schema Reference (saviyntcloud.com)

Saviynt Security Manager API Reference v2021.0.4 (getpostman.com)

[ashachakraborty]

We use birthday attribte as aa primary attribute for Identity match and merge feature. Can using the hashed attribute affect that ?

[Dhruv_S]

Hi @ashachakraborty , this need to be tested in lower environment.