When a user has failed to authenticate due to a high risk score, you can create an override to allow that user access for a specified time period.
|
IMPORTANT: To avoid allowing a malicious user access to applications, only create an override when you are positive the user is legitimate. |
|
IMPORTANT: Since adding an override causes the Security Analytics Engine to return a risk score of 0, alerts will not be sent for the user until the override has expired. |
To add a policy override
The name of the user appears in the User Name field. Verify that this is the correct user for the override.
|
NOTE: This field cannot be edited. |
|
NOTE: Once created, policy overrides can also be managed from the Policy Overrides page which lists all active policy overrides. |
|
IMPORTANT: Since adding an override causes the Security Analytics Engine to return a risk score of 0, alerts will not be sent for the user until the override has expired. |
To edit a policy override
Last Updated By: <nn> - The username of the administrator or help desk operator that last created or modified the override.
NOTE: This field cannot be edited. |
User Name - The name of the user to whom the override applies.
NOTE: This field cannot be edited. |
Expires In - The time left before the override expires. The override must last a minimum of 30 minutes.
Make any necessary changes to the override.
|
NOTE: Once created, policy overrides can also be managed from the Policy Overrides page which lists all active policy overrides. |
To delete a policy override
© ALL RIGHTS RESERVED. Conditions d’utilisation Confidentialité Cookie Preference Center