A critical aspect of providing a simple end-user experience for access requests and ensuring that only compliant access can be requested is controlling which items different types of users see and may request. Suppose all end users are presented with the same catalog of requestable items. In that case, the user experience quickly becomes overwhelming and confusing as users must filter through large amounts of data to find the access they are looking for want that would be relevant for them to request. Exposing unnecessary data also creates a severe security vulnerability, as external users or potentially malicious actors may browse the entire catalog of the organization’s most sensitive roles and resources. Also crucial for regulatory compliance is to blacklist or explicitly deny the ability of certain groups of users ever to see or request specific roles and resources to enforce country-specific restrictions such as the International Traffic in Arms Regulations (ITAR).
...
Eligibility policies can be defined as either inclusion rules or exclusion rules. Inclusion rules define the items a user is authorized to see and request in the IT Shop and ensure these are only the ones that would make sense for them to request. An application example could be rules that filter resources available for Field Sales employees and developers. The catalog of requestable roles and resources available to each of those employees should be different to ensure that unwarranted access requests are not generated, creating unnecessary approval tasks. Additionally, inclusion and exclusion rules help organizations provide employees with a more pleasant user shopping experience as they are shielded from viewing resources that they cannot request.
Inclusion rules include the following:
Eligible – Users can request items in the IT Shop, and the request will go request a resource in the IAM Shop, which creates what is known as a Business Request. All business requests are routed for approval unless the requesting person has the RBAC delegations needed to grant the access being requestedis a designated approver and no additional approvals are needed.
Pre-Approved – Users assigned the policies are Users are pre-approved for the items to which the policy is applicable. When the IT Shop user later requests access, it will not require an approval step before being fulfilled. Suggested – The IT Shop item will show a “Suggested” additional item they may request because of their existing roles or in the context of a role they are currently requesting. The item will still follow standard approval resource and presented with an Activate button in the IAM Shop. To gain immediate access, users click the Activate button. Business Requests are not created as no approvals are needed.
Suggested – Users will see resources where this rule has been applied as suggested items they may want to request. Submitted requests for suggested items follow standard approval routing rules.
...
Eligibility Policy types applied to a personspecific resource type
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
...