and more in a single search tool across platforms. Read the announcement here. |
05/08/2023 03:58 AM
Hi Team,
I have tried to raise access which should cause SOD violation to below highlighted risks only. But we can see the huge no of other risks too are getting evaluated which may cause a performance issue.
Attached is the logs printed during the use case.
Please help me to understand this behavior that why Saviynt is running all the risks evaluation even though the SOD violation is for single risk.
Thanks,
Amit Aware
05/08/2023 08:03 AM
Saviynt's SOD engine picks the access the user has or has been requested and it evaluates all the risks in the ruleset to identify which of the risks are valid and flagged. The process is usually very fast and it takes a couple of seconds. All the risks need to be scanned through to identify that one risk for SOD violation.
05/09/2023 01:02 AM
So it means, when we raise an access which leads the SOD violation then saviynt will scan the corresponding risks as well as it will scan the risks for all the other existing users who already has accesses with violation. is it ?
Thanks,
Amit Aware
05/09/2023 07:14 AM
@SriRanga No, It will just scan for that one user for whom the access is being requested against all his access. Not for all the other users.