7 docs tagged with "Risk"

If there are no violations found during the policy check, you receive a confirmation message. You can choose to approve or reject requests. The policy and risk checks should be used as a guide to the user.

The Policy & Risk checks help you spot rule violations before submitting and approving access requests. Organizations can enable the policy check simulation feature to avoid that user request access to resources that they should not have access to by checking for violations and or risks when users request access to resources. This provides transparency of the policies that the organization has implemented and gives a higher compliance level.

The Risk Concept functionality enables the calculation of Risk scores for resources and identities based on how data is classified. A Risk score expresses how risky a given resource or identity is from a security perspective. It is expressed as a number.

You can calculate the risk score for any:

Omada Identity calculates risk scores of resources and identities based on which classification tags are associated with Systems, Resources, Resource folders, Identities and Business contexts (such as Org. units).

Risk scores of resources and identities are calculated in RoPE and thus do not happen simultaneously, for example, when an analyst modifies the classification tags of a resource or the risk weight of a category in the Omada Identity portal.

Running policy & risk checks in Access Request