8.3
Will sailpoint take into consideration the spoof attack on the GUI created using Angular JS for the plugin? Or there should be an external check which needs to be done?
FYI, the GUI is only accessible when the user logs into Sailpoint and access it via quicklink.
SP creates a record in case the Impersonate configuration is active and someone try to impersonate violating the rules:
In every cases in SP you can configure SSO or MFA for improve the security. Add an external security layer is a good practice.
SailPoint will create an audit event when a user logs in. So you’ll have user login info when some is doing something, and plugins will start executing only when the user has logged in. I tried to play with the regexPattern in the manifest file to execute on the login page, but even the JS files are not executing until the user logs in.
Thanks @enistri_devo for the suggestion. We already have the SSO configured, but was curious to know. If Sailpoint is taking care of it, then we do not have to think of putting other layers to it.
Thanks @vedeepak . But auditing is a heavy process and it is not recommended to use it for all the users. And thus checking users from logging, will create the process even slower, if I understand correctly. But it is good to know that Sailpoint creates a layer of its own to the GUI and hence it helps from attacks. SSO or MFA also helps I suppose.
