Saviynt unveils its cutting-edge Intelligence Suite products to revolutionize Identity Security!
Click HERE to see how Saviynt Intelligence is transforming the industry.
Saviynt Copilot Icon

Correlation Rule Logic

sandeepverma3
New Contributor
New Contributor

Hi Experts,

I just wanted to understand one scenario that I am getting from Endpoint team.
we have a correlation logic for an endpoint as per the below:

upper(trim(users.customproperty2)) = upper(trim(accounts.name)) # upper(trim(USERS.CUSTOMPROPERTY59))=upper(trim(ACCOUNTS.NAME)) # upper(trim(USERS.CUSTOMPROPERTY60))=upper(trim(ACCOUNTS.NAME)) # upper(trim(USERS.CUSTOMPROPERTY61))=upper(trim(ACCOUNTS.NAME)) # upper(trim(USERS.CUSTOMPROPERTY62))=upper(trim(ACCOUNTS.NAME)) # upper(trim(USERS.CUSTOMPROPERTY63))=upper(trim(ACCOUNTS.NAME)) # upper(trim(USERS.CUSTOMPROPERTY64))=upper(trim(ACCOUNTS.NAME)) # upper(trim(USERS.CUSTOMPROPERTY65))=upper(trim(ACCOUNTS.NAME))

Here correlation logic is working fine but endpoint team has given three accounts that is already matching with user's CP2 (as per the above logic) but endpoint team is looking that account's should be correlated based on user's CP23 matching attribute.
Can we achieve this scenario in Saviynt?

Thanks

Sandeep

4 REPLIES 4

rushikeshvartak
All-Star
All-Star

You can achive 

upper(trim(users.customproperty23)) = upper(trim(accounts.name))#

upper(trim(users.customproperty2)) = upper(trim(accounts.name)) # upper(trim(USERS.CUSTOMPROPERTY59))=upper(trim(ACCOUNTS.NAME)) # upper(trim(USERS.CUSTOMPROPERTY60))=upper(trim(ACCOUNTS.NAME)) # upper(trim(USERS.CUSTOMPROPERTY61))=upper(trim(ACCOUNTS.NAME)) # upper(trim(USERS.CUSTOMPROPERTY62))=upper(trim(ACCOUNTS.NAME)) # upper(trim(USERS.CUSTOMPROPERTY63))=upper(trim(ACCOUNTS.NAME)) # upper(trim(USERS.CUSTOMPROPERTY64))=upper(trim(ACCOUNTS.NAME)) # upper(trim(USERS.CUSTOMPROPERTY65))=upper(trim(ACCOUNTS.NAME))


Regards,
Rushikesh Vartak
If this helped you move forward, click 'Kudos'. If it solved your query, select 'Accept As Solution'.

sandeepverma3
New Contributor
New Contributor

1) Can we map two accounts with single user for one endpoint using correlation logic?

2) and As per the exceptional case if we require this for 4 accounts so can we achieve this in any way?

Thanks

  • Yes you can map many accounts to one user
  • you can have multiple correlations rule

Regards,
Rushikesh Vartak
If this helped you move forward, click 'Kudos'. If it solved your query, select 'Accept As Solution'.

stalluri
Valued Contributor
Valued Contributor

@sandeepverma3 

Using the correlation rule, you can correlate 1(user)—N number of accounts by adding multiple conditions.

BasicSQL###(users.username) = accounts.customproperty6 # (users.username) = accounts.name # (users.username) = accounts.customproperty20 # (users.customproperty13) = accounts.name # (users.customproperty15) = accounts.customproperty24
AdvancedADV:users.username = SUBSTRING_INDEX(accounts.name, '-', -1) or users.customproperty27 = SUBSTRING_INDEX(accounts.name, '-', -1) or users.customproperty28 = SUBSTRING_INDEX(accounts.name, '-', -1) or users.email = accounts.customproperty4
 
 




Best Regards,
Sam Talluri
If you find this a helpful response, kindly consider selecting Accept As Solution and clicking on the kudos button.