The policy includes information on the type of rights, data about the access rights of which people will be evaluated, and how the reviews align with the organization's policies and regulations. A recertification audit can have multiple recertification policies associated with it. EmpowerID provides various policy types that determine what kind of access recertification is done in a policy.
EmpowerID recertification policies have the following types.
Policy Type | Recertifies | Business Request | Decision |
|---|---|---|---|
Account Validity | Account validity recertification is a method of determining whether or not accounts are still required. Specific actions must be made if the accounts are no longer required. In other words, an account validity recertification policy to certify whether an account should exist or not. | The recertification engine bundles the recertification items into business requests as per the responsible party assigned. I fno responsible party has been assigned, it bundles them into one business request as per the fall-back assignee. | certify, disable or delete |
Business Role and Location Membership | |||
Recertification Policy Type | Description |
|---|---|
Account Validity | Account validity recertification is a method of determining whether or not accounts are still required. Certain actions must be made if the accounts are no longer required. In other words, an account validity recertification policy to certify whether an account should exist or not. In the account validity recertification process, a responsible person (manager, responsible party, or other designated person) checks the user's account and decides whether this account should continue to exist. For the recertification, a recertification policy is created, a recertification audit is created, and the recertification policy is added to the audit. The audit is compiled, which generates business requests that are sent for approval. In the case of account validity recertification, the recertification engine bundles the recertification items into business requests as per the responsible party assigned. For any item being recertified where its responsible party is null, it bundles them into one business request as per the fall-back assignee. The possible decisions for the business requests are generally set as certify, disable or delete. However, these decisions are configurable. |
Business Role and Location Membership | The business role and location membership recertification process validates whether the membership of a business role and location is still required for a valid business purpose. Certain actions must be made if membership is no longer required. In other words, the business role and location membership recertification policy is to certify whether membership should exist. For the recertification, a recertification policy is created, a recertification audit is created, and the recertification policy is added to the audit. The audit is compiled, which generates business requests that are sent for approval. The engine bundles the recertification items into business requests based on the object itself. Therefore, in this case, the business role and location are the bundles for the business requests, and its members are items. The possible decisions for the business requests are generally set to certify or revoke the business role and location membership. However, these decisions are configurable. |
Direct Reports | The Direct Reports recertification process validates if the managers and their direct reports are still required for a valid business purpose. Certain actions must be made if the direct report is no longer required or changed. In other words, the direct reports recertification policy is to certify whether a direct report for a particular manager should exist. To complete creating a recertification policy, add Targets to define who or what to recertify and add Item Type Scope to limit which data/access to recertify. For the recertification, a recertification policy is created, a recertification audit is created, and the recertification policy is added to the audit. The audit is compiled, which generates business requests that are sent for approval. |
Group Membership | The group membership recertification process validates whether the membership of a group is still required for a valid business purpose. Certain actions must be made if membership is no longer required. In other words, the group membership recertification policy is to certify whether membership should exist or not. For the recertification, a recertification policy is created, a recertification audit is created, and the recertification policy is added to the audit. The audit is compiled, which generates business requests that are sent for approval. The engine bundles the recertification items into business requests based on the object itself. Therefore, in this case, the group is the bundle for the business requests, and its members are items. The possible decisions are generally set to certify or revoke the group membership. However, these decisions are configurable. |
Group Owner | The Group Owner membership recertification process validates whether an account as a group owner is still required for a valid business purpose. Certain actions must be made if the account should no longer own the group. In other words, the Group Owner recertification policy is to certify whether an account should own a group. To complete creating a recertification policy, add Targets to define who or what to recertify and add Item Type Scope to limit which data/access to recertify. For the recertification, a recertification policy is created, a recertification audit is created, and the recertification policy is added to the audit. The audit is compiled, which generates business requests that are sent for approval. |
Group Validity | Group validity recertification is a method of determining whether or not groups are still required. Certain actions must be made if the groups are no longer required. In other words, the group validity recertification policy certifies whether a group should exist. In the group validity recertification process, a responsible person (group owner, responsible party, or other designated person) checks the group and decides whether this group should continue to exist. For the recertification, a recertification policy is created, a recertification audit is created, and the recertification policy is added to the audit. The audit is compiled, which generates business requests that are sent for approval. In the case of group validity recertification, the recertification engine bundles the recertification items into business requests as per the responsible party assigned. For any item being recertified where its responsible party is null, it bundles them into one business request as per the fall-back assignee. The possible decisions are generally set to certify, disable or delete. However, these decisions are configurable. |
Management Role Access Assignment | The management role access assignment recertification process validates whether the access granted to a management role is still required for a valid business purpose. Certain actions must be made if access is no longer required. In other words, the management role access recertification policy is to certify whether an access grant should exist. For the recertification, a recertification policy is created, a recertification audit is created, and the recertification policy is added to the audit. The audit is compiled, which generates business requests that are sent for approval. The engine bundles the recertification items into business requests based on the object itself. Therefore, in this case, the management role is the bundle for the business request, and the access already granted is items. |
Management Role Membership | The management role membership recertification process validates whether the membership of a management role is still required for a valid business purpose. Certain actions must be made if membership is no longer required. In other words, the management role membership recertification policy is to certify whether membership should exist. For the recertification, a recertification policy is created, a recertification audit is created, and the recertification policy is added to the audit. The audit is compiled, which generates business requests that are sent for approval. The engine bundles the recertification items into business requests based on the object itself. Therefore, in this case, the management role is the bundle for the business requests, and its members are items. The possible decisions are generally set to certify or revoke the management role membership. However, these decisions are configurable. |
Management Role Validity | The management role validity recertification is a method of determining whether or not management roles are still required. Certain actions must be made if the management roles are no longer required. In other words, the management role validity recertification policy certifies whether a management role should exist. In the management role validity recertification process, a responsible person (owner, responsible party, or other designated person) checks the management role and decides whether this management role should continue to exist or not. For the recertification, a recertification policy is created, a recertification audit is created, and the recertification policy is added to the audit. The audit is compiled, which generates business requests that are sent for approval. In the case of management role validity recertification, the recertification engine bundles the recertification items into business requests according to the responsible party assigned. For any item being recertified where its responsible party is null, it bundles them into one business request as per the fall-back assignee. The possible decisions for the business requests are generally set as certify, disable or delete. However, these decisions are configurable. |
Person Access Summary | The person access summary policy validates the person with all types of access assignments currently granted to a Person. Simply, this policy is to certify if a person should have the access that the person currently possesses. The person access summary recertifies
To complete creating a recertification policy, add Targets to define who or what to recertify and add Item Type Scope to limit which data/access to recertify. For the recertification, a recertification policy is created, a recertification audit is created, and the recertification policy is added to the audit. The audit is compiled, which generates business requests that are sent for approval. |
Person Validity | The person validity recertification is a method of determining whether or not the person is still required. Certain actions must be made if the persons are no longer required. In other words, the person validity recertification policy is to certify whether a person should exist or not. In the person validity recertification process, a responsible person (manager, responsible party, or other designated person) checks the person and decides whether this person should continue to exist. For the recertification, a recertification policy is created, a recertification audit is created, the recertification policy is added to the audit, then the audit is compiled, which generates business requests that are sent for approval. In case of person validity recertification, the recertification engine bundles the recertification items into business requests as per the responsible party assigned. For any item being recertified where its responsible party is null, it bundles them into one business request as per the fall-back assignee. The possible decisions for the business requests are generally set as certify, disable or delete. However, these decisions are configurable. |
Each Recertification policy is targeted or scoped to apply only to specific people, roles, or resources using EmpowerID query-based collections. These are comprised of sets, primarily SQL queries or code-based queries in some cases. These sets are re-evaluated by the EmpowerID engine on a scheduled basis and can group collections of people. They can be based on questions written against the EmpowerID identity warehouse or external systems in a customer's environment.
EmpowerID also supports real-time risk-based recertification of group membership changes as they are detected. This feature can be enabled per Account Store basis and is targeted to monitor only those groups defined in a Query-Based Collection per Account Store. More information is provided in the doc Continuous Group Membership Change Recertifications