List of Key Performance Indicators
Expand the following sections to learn more about each KPI:
# non-certified assignments
| Parameter | Description |
|---|---|
| KPI name | # non-certified assignments |
| KPI goal | Shows the open recertification for access rights to allow for planning the next survey campaign. |
| Priority | 120 |
| Short description | The KPI gives a direct number of assignments that have not been recertified. The KPI directly delivers the assignments that should be included in the next access review survey campaign. |
| Stakeholder to be addressed | IGA Team Managers Audit |
| Classification | Risk & Compliance |
| Method of measurement | All CRAs without a survey verdict that has compliance state: Explicitly Approved Orphan Assignment Not Approved In Violation Pending Deprovisioning CRAs with the compliance states Implicitly assigned, Implicitly Approved, or None are not counted. |
| Baseline | The baseline is 0. No thresholds have been configured in the Omada Identity portal, but an administrator can add these in the Key Performance Indicator configuration. |
| Available to user groups | System administrators Auditors Managers (filter on managed identities/context) |
| Configuration options | Non-certified Resource Assignment |
# assignments granted without desired state
| Parameter | Description |
|---|---|
| KPI name | # assignments granted without desired state |
| KPI goal | Identify unnecessary access rights |
| Priority | 140 |
| Short description | This KPI helps to enforce the need-to-know principle. If a system administration can grant access rights without approval in Omada Identity, it is possible that Identity gets unnecessary access rights. This KPI supports evaluation of the risk associated with unnecessary access rights. |
| Stakeholder to be addressed | IGA Team Managers Audit |
| Classification | Risk & Compliance |
| Method of measurement | All resource assignments in the Data Warehouse with status “Not Approved”, excluding indirect resource assignments. |
| Baseline | - |
| Available to user groups | System administrators Auditors Managers (filter on managed identities/context) |
| Configuration options | - |
# orphan accounts
| Parameter | Description |
|---|---|
| KPI name | # orphan accounts |
| KPI goal | Measures orphan accounts to ensure governance and improve internal processes to prevent orphan accounts |
| Priority | 150 |
| Short description | This KPI measured the accounts Omada Identity cannot assign an owner to. The reasons for such a situation are, for example: An employee left the company, but the account is not deleted yet. A technical account has no person assigned to it. To assign orphan accounts you can either update the Account rules for the system or run an Orphan account survey to assign the orphaned accounts to an owner. |
| Stakeholder to be addressed | IGA Team Managers Audit |
| KPI ID | KPI.GOV.03.02 |
| Classification | Risk & Compliance |
| Method of measurement | Number of Accounts in Data Warehouse that are not matched to an actual identity (orphan assignment). |
| Baseline | There should be 0 orphan accounts. Default thresholds defined: OK: lower than 100 Monitor: between 100 and 200 Take action: above 200 |
| Available to user groups | System administrators Auditors System owners (filter on owned systems) |
| Configuration options | - |
# accounts belonging to inactive identities
| Parameter | Description |
|---|---|
| KPI name | # accounts belonging to inactive identities |
| KPI goal | Measures orphan accounts to ensure governance and improve internal processes to prevent orphan accounts. |
| Priority | 170 |
| Short description | This KPI measured the accounts that are not assigned to an active identity. The reason for such a situation may be, for example: An employee left the company, but the account is not deleted yet. You should also ensure that your offboarding processes works as expected. |
| Stakeholder to be addressed | IGA Team Managers Audit |
| Classification | Risk & Compliance |
| Method of measurement | Number of Accounts in Data Warehouse that are matched to identities that are terminated, inactive or disabled. No thresholds have been configured in the Omada Identity portal, but an administrator can add these in the Key Performance Indicator configuration. |
| Baseline | There should be 0 orphan accounts. |
| Available to user groups | System administrators Auditors System owners (filter on owned systems) |
| Configuration options | Identity Active Status |
# resources without owners
| Parameter | Description |
|---|---|
| KPI name | # resources without owners |
| KPI goal | Measures orphan resources to ensure governance and improve internal processes to prevent orphan accounts. |
| Priority | 160 |
| Short description | This KPI measured the resources that Omada Identity cannot assign an owner to. You can use the Control Policy “Resources without owners” to assign owners to the resources. |
| Stakeholder to be addressed | IGA Team Resource owners Audit |
| Classification | Risk & Compliance |
| Method of measurement | Resources in the Data Warehouse where there is no owner on the resource or its resource folder. It does not count account resources, or resources internal to Enterprise Server. |
| Baseline | There should be 0 orphan groups. No thresholds have been configured in the Omada Identity portal, but an administrator can add these in the Key Performance Indicator configuration. |
| Available to user groups | System administrators Auditors System owners (filter on owned systems) Resource owners (filter on owned resources) |
| Configuration options | - |
# resources owned by inactive identities
| Parameter | Description |
|---|---|
| KPI name | # resources owned by inactive identities |
| KPI goal | Measures orphan resource to reinstall governance and improve internal processes to prevent orphan resources. |
| Priority | 330 |
| Short description | This KPI measured the resources that are owned by one or more inactive identity. Note that the resource may have other active owners. Ensure that you have processes in place that transfers ownership when an identity leaves the organization. |
| Stakeholder to be addressed | IGA Team Resource owners Audit |
| Classification | Risk & Compliance |
| Method of measurement | Resources where at least one owning identity has an identity status that is not active. It is possible to change which statuses count as active. The resource may have other owners that are active. |
| Baseline | There should be 0 orphan groups. |
| Available to user groups | System administrators Auditors System owners (filter on owned systems) Resource owners (filter on owned resources) |
| Configuration options | Identity Active Status |
# resources without assignments
| Parameter | Description |
|---|---|
| KPI name | # resources without assignments |
| KPI goal | Measures unused resources to reinstall governance and improve internal processes. |
| Priority | 180 |
| Short description | This KPI measures the resources that do not have any active assignments. Newly created resources may be without assignments for a period. |
| Stakeholder to be addressed | IGA Team Resource owners Audit |
| Classification | Efficiency |
| Method of measurement | Resources that have no matching assignments in the Data Warehouse. |
| Baseline | There should be 0 continuously unused resources |
| Available to user groups | System administrators Auditors System owners (filter on owned systems) Resource owners (filter on owned resources) |
| Configuration options | - |
# stale accounts (unused accounts)
| Parameter | Description |
|---|---|
| KPI name | # stale accounts (unused accounts) |
| KPI goal | Measures unused accounts to reinstall governance and improve internal processes to prevent orphan accounts. |
| Priority | 190 |
| Short description | This KPI measures unused accounts to enable a review to validate the need of these accounts. |
| Stakeholder to be addressed | IGA Team Managers Audit |
| Classification | Risk & compliance |
| Method of measurement | Accounts that have not been used for a period. The parameter is by default 60 days but can be configured in the configuration object Analysis Services Configuration, using the parameter Stale account logon days. Accounts that do not have a value for “LastLogon” are not counted. As Omada Identity can only have this information if Omada Identity has a transparent view into the target systems, in most installations this KPI will measure AD accounts only. |
| Baseline | The baseline is 0. No thresholds have been configured in the Omada Identity portal, but an administrator can add these in the Key Performance Indicator configuration. |
| Available to user groups | System administrators Operation administrators Managers (filter on owned systems) System owners (filter on owned systems) |
| Configuration options | Parameter Stale account logon days that is used to configure how many days are counted. Default: 60 days. |
% compliant assignments
| Parameter | Description |
|---|---|
| KPI name | % compliant assignments |
| KPI goal | Give an overview of the compliance level of the IGA solution. |
| Priority | 200 |
| Short description | The KPI calculates the percentage of compliant assignments based on their compliance status. |
| Stakeholder to be addressed | IGA Team Managers Audit |
| Classification | Risk & Compliance |
| Method of measurement | All CRAs with status: Compliant: Explicitly approved Implicitly approved None Not compliant: Pending deprovisioning Not approved In violation Orphan assignments |
| Baseline | Default thresholds: OK: above 20 Monitor: between 1-20 Take Action: lower than 1. |
| Available to user groups | System administrators Auditors Managers (filter on managed Identities/Contexts) |
| Configuration options | Resource Assignment Compliance State |
# identities with high risk level
| Parameter | Description |
|---|---|
| KPI name | # identities with high risk level |
| KPI goal | Enable organization to monitor risk and act if unusual changes occur. Increases in the number of assignments should be monitored and mitigated if necessary. |
| Priority | 210 |
| Short description | The number of identities with a high risk-level is an indication of the risk and compliance level of the organization. |
| Stakeholder to be addressed | IGA Team Managers Audit |
| Classification | Risk & Compliance |
| Method of measurement | Number of identities with a risk level “high”. |
| Baseline | - |
| Available to user groups | System administrators Managers (filtered on owned identities) Auditors Security Officers |
| Configuration options | Identity Active Status mapping that maps which identity statuses are counted Risk Level text mapping that maps which risk levels are counted |
# resources with high risk level
| Parameter | Description |
|---|---|
| KPI name | # resources with high risk level |
| KPI goal | Enable organization to monitor risk and act if unusual changes occur. |
| Priority | 220 |
| Short description | The number of resources with a “high” risk level. is an indicator of the risk and compliance status of the organization. Increases in the number of assignments should be monitored and mitigated if necessary. |
| Stakeholder to be addressed | IGA Team Managers Audit System owners Security & Compliance |
| Classification | Risk & Compliance |
| Method of measurement | Number of CRAs with a “high” risk level. It excludes indirect resource assignments in the Data Warehouse. |
| Baseline | - |
| Available to user groups | System administrators Resource owners (filtered on owned resources) Auditors Security Officers |
| Configuration options | Risk Level text mapping that maps which risk levels are counted. |
# assignments with high risk level
| Parameter | Description |
|---|---|
| KPI name | # assignments with high risk level |
| KPI goal | Enable organization to monitor risk and act if unusual changes occur. |
| Priority | 230 |
| Short description | The number of assignments with a “high” risk level. is an indicator of the risk and compliance status of the organization. Increases in the number of assignments should be monitored and mitigated if necessary. |
| Stakeholder to be addressed | IGA Team Managers Auditors System owners Security & Compliance |
| Classification | Risk & Compliance |
| Method of measurement | Number of assignments in the Data Warehouse with a risk level “high”. |
| Baseline | - |
| Available to user groups | System administrators Managers (filtered on owned identities) Auditors Security Officers |
| Configuration options | Risk Level text mapping |
# identities created via import
| Parameter | Description |
|---|---|
| KPI name | # identities created via import |
| KPI goal | Provide information about new Identities coming from HR Systems. |
| Priority | 240 |
| Short description | The Key Figure counts identities imported to Omada Identity. The large increases should reflect business events like reorganizations, Merger and Acquisition activities |
| Stakeholder to be addressed | IGA Team Operations HR |
| Classification | Master data |
| Method of measurement | Counts identities where the OISID is greater than 1000000000. These identities originate from an external system and are imported via the Data Warehouse. |
| Baseline | - |
| Available to user groups | System administrators Operation administrators Data administrators |
| Configuration options | - |
# identities created manually
| Parameter | Description |
|---|---|
| KPI name | # identities created manually |
| KPI goal | Provide information about Identities not contained in delivery of any HR system but still needed in Omada Identity. |
| Priority | 250 |
| Short description | The Key Figure counts identities created via an Omada Identity. The large increases should reflect business events like reorganizations, Merger and Acquisition activities |
| Stakeholder to be addressed | IGA Team Operations HR |
| Classification | Master data |
| Method of measurement | Counts identities where the OISID is lower than 1000000000. These identities originate from an internal Omada Identity process, including those created through API integration, CIAM, and data exchange. It includes identities created from the CIAM module as well as through Omada Identity processes. |
| Baseline | - |
| Available to user groups | System administrators Operation administrators Data administrators |
| Configuration options | - |
# all identities
| Parameter | Description |
|---|---|
| KPI name | # all identities |
| KPI goal | Provide information about al Identities in the IGA solution. |
| Priority | 260 |
| Short description | The KPI is a Key figure that measure the total number of identities. The fluctuations of the time series should reflect business events like reorganizations, M&A activities. In a stable environment there should be no large fluctuations. |
| Stakeholder to be addressed | IGA Team Operations HR |
| Classification | Master data |
| Method of measurement | Counts all identities in the Data Warehouse. |
| Baseline | - |
| Available to user groups | System administrators Operation administrators Data administrators |
| Configuration options | - |
# active identities
| Parameter | Description |
|---|---|
| KPI name | # active identities |
| KPI goal | Provide information about active Identities in the IGA solution. |
| Priority | 270 |
| Short description | The Key Figure counts the total number of active identities. |
| Stakeholder to be addressed | IGA Team Operations HR |
| Classification | Master data |
| Method of measurement | Count active identities in the Data Warehouse. |
| Baseline | - |
| Available to user groups | System administrators Operation administrators Data administrators |
| Configuration options | Identity Active Status |
# external identities
| Parameter | Description |
|---|---|
| KPI name | # external identities |
| KPI goal | Provide stakeholder with a number as a starting point to verify all checks against contracts, Non-Disclosure agreements and other compliance requirements. |
| Priority | 280 |
| Short description | The number of external identities is the number of identities flagged as “external” in some way. This number reflects the external users in Omada Identity only. The definition of “external” can vary from customer to customer. The KPI give the number of these external Identities. All these identities must be checked against contracts, Non-Disclosure agreements and other compliance requirements to keep them as valid Identities in Omada Identity. |
| Stakeholder to be addressed | IGA Team Procurement HR or other units responsible for managing externals for the company |
| Classification | Master data |
| Method of measurement | All identities with Identity category: Contractor or Customer with identity status: Active or Pending. |
| Baseline | - |
| Available to user groups | System administrators Operation administrators Data administrators |
| Configuration options | Identity Active Status Identity Category |
# technical identities
| Parameter | Description |
|---|---|
| KPI name | # technical identities |
| KPI goal | Provide information about the volatility of the lifecycle of technical Identity. |
| Priority | 290 |
| Short description | The number of requests for a technical Identity is an indication of the volatility of the lifecycle of technical Identities. If there are no reorganizations, no M&A activities and similar events the volatility should be low and show no large fluctuations. |
| Stakeholder to be addressed | IGA Team Operations Auditors |
| Classification | Master data |
| Method of measurement | All identities with Identity type: Machine. It counts both active and terminated identities. |
| Baseline | - |
| Available to user groups | IGA Team Operation administrators Auditors |
| Configuration options | - |
# SoD constraint violations
| Parameter | Description |
|---|---|
| KPI name | # SoD constraint violations |
| KPI goal | The KPI delivers a direct number which is for direct use for audit and management. |
| Priority | 110 |
| Short description | This Key Figure measures the total number of resource assignments that are in violation to a Constraint policy. This KPI does not give an indication about associated risks. |
| Stakeholder to be addressed | IGA Team Audit Management |
| Classification | Risk & Compliance |
| Method of measurement | All CRAs with status in violation or “overridden”. |
| Baseline | Default thresholds: OK: lower than 100 Monitor: between 100 and 200 Take action: above 200 |
| Available to user groups | System administrators Auditors Security Officers Managers (filter on managed identities/context) |
| Configuration options | - |
# managed identities
| Parameter | Description |
|---|---|
| KPI name | # managed identities |
| KPI goal | Give managers an overview of managed identities |
| Priority | 130 |
| Short description | This Key Figure measures the identities owned or managed by you. It includes both active and terminated identities. |
| Stakeholder to be addressed | Managers |
| Classification | Master data |
| Method of measurement | Shows the content of the Portal view "My identities". |
| Baseline | - |
| Available to user groups | Managers |
| Configuration options | - |
# owned resources
| Parameter | Description |
|---|---|
| KPI name | # owned resources |
| KPI goal | Give resources owners an overview of resources |
| Priority | 100 |
| Short description | This Key Figure measures shows the resources owned or managed by you. It includes resources in Folders and systems you are an owner of. It includes both active and terminated resources. |
| Stakeholder to be addressed | Resource and Resource Folder owners |
| Classification | Master data |
| Method of measurement | Shows the content of the Portal view "My resources". |
| Baseline | - |
| Available to user groups | Resource owners |
| Configuration options | - |
# owned systems
| Parameter | Description |
|---|---|
| KPI name | # owned systems |
| KPI goal | Give system owners an overview of managed systems. |
| Priority | 90 |
| Short description | This Key Figure measures shows that you are the owner of. It does not include applications. |
| Stakeholder to be addressed | System owners |
| Classification | Master data |
| Method of measurement | Shows the content of the Portal view "My systems". |
| Baseline | - |
| Available to user groups | System owners |
| Configuration options | - |
# identities with violations pending evaluation
| Parameter | Description |
|---|---|
| KPI name | # identities with violations pending evaluation |
| KPI goal | Give an overview of outstanding Violations. |
| Priority | 40 |
| Short description | This Key Figure measures the number of Assignments that is in violation to a Constraint policy but have not been evaluated yet. |
| Stakeholder to be addressed | IGA Team |
| Classification | Risk & Compliance |
| Method of measurement | Measures assignments in the Role and Policy Engine that has a violation that is pending evaluation. |
| Baseline | - |
| Available to user groups | Operation administrators |
| Configuration options | - |
# identities with calculation warnings
| Parameter | Description |
|---|---|
| KPI name | # identities with calculation warnings |
| KPI goal | Give an overview of the status of the Role and Policy Engine. |
| Priority | 50 |
| Short description | This Key Figure counts the identities for which the Role and Policy Engine reported a warning. |
| Stakeholder to be addressed | IGA Team |
| Classification | Operations |
| Method of measurement | Identities with a calculation warning in the Role and Policy Engine. |
| Baseline | - |
| Available to user groups | Operation administrators |
| Configuration options | - |
# identities with a calculation error
| Parameter | Description |
|---|---|
| KPI name | # identities with a calculation error |
| KPI goal | Give an overview of the status of the Role and Policy Engine. |
| Priority | 60 |
| Short description | This Key Figure counts the identities for which the Role and Policy Engine reported an error. |
| Stakeholder to be addressed | IGA Team |
| Classification | Operations |
| Method of measurement | Identities with a calculation error in the Role and Policy Engine. |
| Baseline | - |
| Available to user groups | Operation administrators |
| Configuration options | - |
# identities processed within the last 24 hours
| Parameter | Description |
|---|---|
| KPI name | # identities processed within the last 24 hours |
| KPI goal | Give an overview of the status of the Role and Policy Engine. |
| Priority | 70 |
| Short description | This Key Figure counts the number of identities that have been calculated by the Role and Policy Engine in the last 24 hours. |
| Stakeholder to be addressed | IGA Team |
| Classification | Operations |
| Method of measurement | Identities processed in the Role and Policy Engine in the last 24 hours. |
| Baseline | - |
| Available to user groups | Operation administrators |
| Configuration options | - |
# identities pending calculation
| Parameter | Description |
|---|---|
| KPI name | # identities pending calculation |
| KPI goal | Give an overview of the status of the Role and Policy Engine. |
| Priority | 80 |
| Short description | This Key Figure counts the number of identities that are queued for being processed by the Role and Policy Engine. |
| Stakeholder to be addressed | IGA Team |
| Classification | Operations |
| Method of measurement | Identities in the Role and Policy Engine queue. |
| Baseline | - |
| Available to user groups | Operation administrators |
| Configuration options | - |
My work items
| Parameter | Description |
|---|---|
| KPI name | My work items |
| KPI goal | Give users an overview of his open tasks. |
| Priority | 20 |
| Short description | This Key Figure shows the number of open tasks that you are assigned to. |
| Stakeholder to be addressed | All users |
| Classification | My data |
| Method of measurement | Counts the content of the view "My tasks". |
| Baseline | - |
| Available to user groups | All user groups |
| Configuration options | - |
My recent self-service requests
| Parameter | Description |
|---|---|
| KPI name | My recent self-service requests |
| KPI goal | Give the user an overview to recent activity within Omada Identity. |
| Priority | 30 |
| Short description | This Key Figure shows the number of Self-service requests that you have submitted within the past 30 days. |
| Stakeholder to be addressed | All users |
| Classification | My data |
| Method of measurement | Counts the content of the view "My recent self-service requests". |
| Baseline | - |
| Available to user groups | All user groups |
| Configuration options | - |
# identities not enrolled to password reset
| Parameter | Description |
|---|---|
| KPI name | # identities not enrolled to password reset |
| KPI goal | Give an overview of the level of adoption of the password reset process in the organization. Allows administrators to ensure all identities enroll to password reset. |
| Priority | 300 |
| Short description | This Key Figure shows the number of identities that have not yet enrolled themselves to the self-service password reset service. |
| Stakeholder to be addressed | IGA Team |
| Classification | Operations |
| Method of measurement | Counts the content of the view "Identities not enrolled to password reset". |
| Baseline | - |
| Available to user groups | Operation administrators |
| Configuration options | - |
# identities enrolled to password reset
| Parameter | Description |
|---|---|
| KPI name | # identities enrolled to password reset |
| KPI goal | Give an overview of the level of adoption of the password reset process in the organization. |
| Priority | 310 |
| Short description | This Key Figure shows the number of identities that have enrolled themselves to the self-service password reset service. |
| Stakeholder to be addressed | IGA Team |
| Classification | Operations |
| Method of measurement | Counts the content of the view "Identities enrolled to password reset". |
| Baseline | - |
| Available to user groups | Operation administrators |
| Configuration options | - |
Omada Provisioning Service status
| Parameter | Description |
|---|---|
| KPI name | Omada Provisioning Service status |
| KPI goal | Show the status of Omada Provisioning Service in the dashboard. |
| Priority | 10 |
| Short description | This KPI shows the status of OPS. Green (0) indicates that the status is OK. Yellow (1) indicates that one or more jobs are being retried due to transient failures. Red (2) indicates one or more jobs have failed to be processed. You can also go to each system and check the provisioning status and see individual provisioning jobs. |
| Stakeholder to be addressed | IGA Team Operation administrators |
| Classification | Operations |
| Method of measurement | Shows the result of the Scalar-valued Function "GetDashboard" in the Provisioning Service database. |
| Baseline | - |
| Available to user groups | Operation administrators |
| Configuration options | - |
# contractors expiring soon
| Parameter | Description |
|---|---|
| KPI name | # contractors expiring soon |
| KPI goal | Show the status number of contractors in the dashboard. |
| Priority | 285 |
| Short description | This Key Figure counts the Contractors managed by you that will expire within the next 60 days. Data is sorted by the Valid To column ascending. Contractors with the shortest expiration date are on top of the list. |
| Stakeholder to be addressed | Managers |
| Classification | Master data |
| Method of measurement | Counts contractors that are expiring soon. Already expired contractors are excluded. Contractors without Valid To date set are excluded. |
| Baseline | - |
| Available to user groups | Managers |
| Configuration options | Parameter ContractorsDaysToExpire that is used to configure how many days are counted. Default: 60 days. This is available in the Configuration object Analysis Services Configuration. |
# open recertifications
| Parameter | Description |
|---|---|
| KPI name | # open recertifications |
| KPI goal | Show number of assignments currently being recertified. |
| Priority | 51 |
| Short description | This Key Figure counts assignments included in access review surveys. |
| Stakeholder to be addressed | IGA Team Auditors Managers |
| Classification | Recertification |
| Method of measurement | Assignments in the Data Warehouse which have been included in access review surveys, regardless of whether the answer has been submitted or not. Assignments which are included in multiple surveys are only counted once. |
| Baseline | - |
| Available to user groups | System owners Auditors Managers (filter on managed identities/context) |
| Configuration options | - |
# open recertification campaigns
| Parameter | Description |
|---|---|
| KPI name | # open recertification campaigns |
| KPI goal | Show number of access review surveys currently in progress. |
| Priority | 301 |
| Short description | This Key Figure counts identities included in access review surveys. |
| Stakeholder to be addressed | IGA Team Auditors |
| Classification | Recertification |
| Method of measurement | Active identities that are included in access review surveys currently initiated or in progress. |
| Baseline | - |
| Available to user groups | Auditors |
| Configuration options | - |
% completed recertifications
| Parameter | Description |
|---|---|
| KPI name | % completed recertifications |
| KPI goal | Show completion status of running access review surveys. |
| Priority | 303 |
| Short description | This KPI calculates the percentage of completed recertifications in access review surveys. |
| Stakeholder to be addressed | IGA Team Auditors |
| Classification | Recertification |
| Method of measurement | Show completion status of currently running access review surveys by comparing number of answered questions to total number of survey questions. |
| Baseline | - |
| Available to user groups | Auditors |
| Configuration options | - |
# identities in active campaigns
| Parameter | Description |
|---|---|
| KPI name | # identities in active campaigns |
| KPI goal | Show number of identities whose access is being currently reviewed. |
| Priority | 53 |
| Short description | This Key Figure counts identities included in access review surveys. |
| Stakeholder to be addressed | IGA Team Managers |
| Classification | Recertification |
| Method of measurement | Active identities that are included in access review surveys currently initiated or in progress. |
| Baseline | - |
| Available to user groups | Managers |
| Configuration options | - |
# resources in recertification campaigns
| Parameter | Description |
|---|---|
| KPI name | # resources in recertification campaigns |
| KPI goal | Show number of resources whose access is being currently reviewed. |
| Priority | 53 |
| Short description | This Key Figure counts resources included in access review surveys. |
| Stakeholder to be addressed | IGA Team |
| Classification | Recertification |
| Method of measurement | Resources that are included in access review surveys currently in progress. |
| Baseline | - |
| Available to user groups | System owners |
| Configuration options | - |
# high risk identities in recertification campaigns
| Parameter | Description |
|---|---|
| KPI name | # high risk identities in recertification campaigns |
| KPI goal | Show number of identities with high risk classification which are currently being reviewed. |
| Priority | 52 |
| Short description | This Key Figure counts high risk identities included in access review surveys. |
| Stakeholder to be addressed | IGA Team Auditors Managers |
| Classification | Recertification |
| Method of measurement | High risk identities that are included in access review surveys currently initiated or in progress. Recertification of assignments in Data Warehouse are included. |
| Baseline | - |
| Available to user groups | Managers Auditors |
| Configuration options | - |
# high risk resources in recertification campaigns
| Parameter | Description |
|---|---|
| KPI name | # high risk resources in recertification campaigns |
| KPI goal | Show number of resources with high risk classification which are currently being reviewed. |
| Priority | 52 |
| Short description | This Key Figure counts high risk resources included in access review surveys. |
| Stakeholder to be addressed | IGA Team Auditors |
| Classification | Recertification |
| Method of measurement | High risk resources that are included in access review surveys currently initiated or in progress. Recertification of assignments in Data Warehouse are included. |
| Baseline | - |
| Available to user groups | System owners Auditors |
| Configuration options | - |
% Access Requests completed within day
| Parameter | Description |
|---|---|
| KPI name | % Access Requests completed within day |
| KPI goal | Show the percentage of completed Access Requests out of all requested accesses within 24 hours. |
| Priority | 350 |
| Short description | This KPI shows the percentage of completed Access Requests out of all requested accesses within 24 hours. The time range of Access Requests is 180 days. |
| Stakeholder to be addressed | Auditors Managers System owners |
| Classification | Process efficiency |
| Method of measurement | Completed Access Requests are Access Requests where the approval process has been completed. This KPI shows the percentage of Access Requests completed within 24 hours. |
| Baseline | - |
| Available to user groups | Managers System owners Auditors |
| Configuration options | - |
% Access Requests completed within week
| Parameter | Description |
|---|---|
| KPI name | % Access Requests completed within week |
| KPI goal | Show the percentage of completed Access Requests out of all requested accesses within 7 days. |
| Priority | 352 |
| Short description | This KPI shows the percentage of completed Access Requests out of all requested accesses within 7 days. The time range of Access Requests is 180 days. |
| Stakeholder to be addressed | Auditors Managers System owners |
| Classification | Process efficiency |
| Method of measurement | Completed Access Requests are Access Requests where the approval process has been completed. This KPI shows the percentage of Access Requests completed within 7 days. |
| Baseline | - |
| Available to user groups | Managers System owners Auditors |
| Configuration options | - |
% Access Requests completed within month
| Parameter | Description |
|---|---|
| KPI name | % Access Requests completed within month |
| KPI goal | Show the percentage of completed Access Requests out of all requested accesses within 7 days. |
| Priority | 354 |
| Short description | This KPI shows the percentage of completed Access Requests out of all requested accesses within 30 days. The time range of Access Requests is 180 days. |
| Stakeholder to be addressed | Auditors Managers System owners |
| Classification | Process efficiency |
| Method of measurement | Completed Access Requests are Access Requests where the approval process has been completed. This KPI shows the percentage of Access Requests completed within 30 days. |
| Baseline | - |
| Available to user groups | Managers System owners Auditors |
| Configuration options | - |
# Access Requests completed within day
| Parameter | Description |
|---|---|
| KPI name | # Access Requests completed within day |
| KPI goal | Show the number of completed Access Requests out of all requested accesses within 24 hours. |
| Priority | 356 |
| Short description | This KPI shows the number of completed Access Requests out of all requested accesses within 24 hours. The time range of Access Requests is 180 days. |
| Stakeholder to be addressed | Auditors Managers System owners |
| Classification | Process efficiency |
| Method of measurement | Completed Access Requests are Access Requests where the approval process has been completed. This KPI shows the percentage of Access Requests completed within 24 hours. |
| Baseline | - |
| Available to user groups | Managers System owners Auditors |
| Configuration options | - |
# Access Requests completed within week
| Parameter | Description |
|---|---|
| KPI name | # Access Requests completed within week |
| KPI goal | Show the number of completed Access Requests out of all requested accesses within 7 days. |
| Priority | 358 |
| Short description | This KPI shows the number of completed Access Requests out of all requested accesses within 7 days. The time range of Access Requests is 180 days. |
| Stakeholder to be addressed | Auditors Managers System owners |
| Classification | Process efficiency |
| Method of measurement | Completed Access Requests are Access Requests where the approval process has been completed. This KPI shows the percentage of Access Requests completed within 7 days. |
| Baseline | - |
| Available to user groups | Managers System owners Auditors |
| Configuration options | - |
# Access Requests completed within month
| Parameter | Description |
|---|---|
| KPI name | # Access Requests completed within month |
| KPI goal | Show the number of completed Access Requests out of all requested accesses within 30 days. |
| Priority | 360 |
| Short description | This KPI shows the number of completed Access Requests out of all requested accesses within 30 days. The time range of Access Requests is 180 days. |
| Stakeholder to be addressed | Auditors Managers System owners |
| Classification | Process efficiency |
| Method of measurement | Completed Access Requests are Access Requests where the approval process has been completed. This KPI shows the percentage of Access Requests completed within 30 days. |
| Baseline | - |
| Available to user groups | Managers System owners Auditors |
| Configuration options | - |
% Access Request questions completed within day
| Parameter | Description |
|---|---|
| KPI name | % Access Request questions completed within day |
| KPI goal | Show percentage of Access Request questions completed within a day of all questions within a time range from initiation. |
| Priority | 362 |
| Short description | This KPI shows the number of completed Access Request questions out of all questions within 24 hours. The time range of Access Requests is 180 days. |
| Stakeholder to be addressed | Auditors Managers System owners |
| Classification | Process efficiency |
| Method of measurement | Access Request questions are survey questions that occur in the resource assignment approval process. One question is usually a combination of one identity and one resource from Access Request. It depends on the approval process. Access Request can have zero questions or more if the approval process has many steps. Not answered questions are not counted. Day is counted as 24 hours. |
| Baseline | - |
| Available to user groups | Managers System owners Auditors |
| Configuration options | - |
% Access Request questions completed within week
| Parameter | Description |
|---|---|
| KPI name | % Access Request questions completed within week |
| KPI goal | Show the percentage of Access Request questions completed within a week of all questions within a time range from initiation. |
| Priority | 364 |
| Short description | This KPI shows the percentage of completed Access Request questions out of all questions within 7 days. The time range of Access Requests is 180 days. |
| Stakeholder to be addressed | Auditors Managers System owners |
| Classification | Process efficiency |
| Method of measurement | Access Request questions are survey questions that occur in the resource assignment approval process. One question is usually a combination of one identity and one resource from Access Request. It depends on the approval process. Access Request can have zero questions or more if the approval process has many steps. Not answered questions are not counted. Week is counted as 7 calendar days. |
| Baseline | - |
| Available to user groups | Managers System owners Auditors |
| Configuration options | - |
% Access Request questions completed within month
| Parameter | Description |
|---|---|
| KPI name | % Access Request questions completed within month |
| KPI goal | Show percentage of Access Request questions completed within a month of all questions within a time range from initiation. |
| Priority | 366 |
| Short description | This KPI shows the percentage of completed Access Request questions out of all questions within 30 days. The time range of Access Requests is 180 days. |
| Stakeholder to be addressed | Auditors Managers System owners |
| Classification | Process efficiency |
| Method of measurement | Access Request questions are survey questions that occur in the resource assignment approval process. One question is usually a combination of one identity and one resource from Access Request. It depends on the approval process. Access Request can have zero questions or more if the approval process has many steps. Not answered questions are not counted. Month is counted as 30 calendar days. |
| Baseline | - |
| Available to user groups | Managers System owners Auditors |
| Configuration options | - |
# Access Request questions approved within day
| Parameter | Description |
|---|---|
| KPI name | # Access Request questions approved within day |
| KPI goal | Show the number of completed Access Request questions of all answered within 24 hours. |
| Priority | 368 |
| Short description | This KPI shows the number of approved Access Request questions out of all questions within 24 hours. The time range of Access Requests is 180 days. |
| Stakeholder to be addressed | Auditors Managers System owners |
| Classification | Process efficiency |
| Method of measurement | Approved Access Requests questions are questions that have the approval process finished. This KPI shows the percentage of Access Requests questions approved within 24 hours. |
| Baseline | - |
| Available to user groups | Managers System owners Auditors |
| Configuration options | - |
# Access Request questions approved within week
| Parameter | Description |
|---|---|
| KPI name | # Access Request questions approved within week |
| KPI goal | Show the number of approved Access Request questions of all answered within 7 days. |
| Priority | 370 |
| Short description | This KPI shows the number of approved Access Request questions out of all questions within 7 days. The time range of Access Requests is 180 days. |
| Stakeholder to be addressed | Auditors Managers System owners |
| Classification | Process efficiency |
| Method of measurement | Approved Access Requests questions are questions that have the approval process finished. This KPI shows the percentage of Access Requests questions approved within 7 days. |
| Baseline | - |
| Available to user groups | Managers System owners Auditors |
| Configuration options | - |
# Access Request questions approved within month
| Parameter | Description |
|---|---|
| KPI name | # Access Request questions approved within month |
| KPI goal | Show the number of approved Access Request questions of all answered within 30 days. |
| Priority | 372 |
| Short description | This KPI shows the number of approved Access Request questions out of all questions within 30 days. The time range of Access Requests is 180 days. |
| Stakeholder to be addressed | Auditors Managers System owners |
| Classification | Process efficiency |
| Method of measurement | Approved Access Requests questions are questions that have the approval process finished. This KPI shows the number of Access Request questions approved within 30 days. |
| Baseline | - |
| Available to user groups | Managers System owners Auditors |
| Configuration options | - |
# Access Request questions rejected within day
| Parameter | Description |
|---|---|
| KPI name | # Access Request questions rejected within day |
| KPI goal | Show the number of rejected Access Request questions of all answered within 24 hours. |
| Priority | 374 |
| Short description | This KPI shows the number of rejected Access Requests questions out of all answered questions within 24 hours. The time range of Access Requests is 180 days. |
| Stakeholder to be addressed | Auditors Managers System owners |
| Classification | Process efficiency |
| Method of measurement | Rejected Access Requests questions are questions that have been rejected during the approval process. This KPI shows the number of Access Requests questions rejected within 24 hours. |
| Baseline | - |
| Available to user groups | Managers System owners Auditors |
| Configuration options | - |
# Access Request questions rejected within week
| Parameter | Description |
|---|---|
| KPI name | # Access Request questions rejected within week |
| KPI goal | Show the number of rejected Access Request questions of all answered within 7 days. |
| Priority | 376 |
| Short description | This KPI shows the number of rejected Access Requests out of all answered questions within 7 days. The time range of Access Requests is 180 days. |
| Stakeholder to be addressed | Auditors Managers System owners |
| Classification | Process efficiency |
| Method of measurement | Rejected Access Requests questions are questions that have been rejected during the approval process. This KPI shows the number of Access Requests questions rejected within 7 days. |
| Baseline | - |
| Available to user groups | Managers System owners Auditors |
| Configuration options | - |
# Access Request questions rejected within month
| Parameter | Description |
|---|---|
| KPI name | # Access Request questions rejected within month |
| KPI goal | Show the number of rejected Access Request questions of all answered within 30 days. |
| Priority | 378 |
| Short description | This KPI shows the number of rejected Access Request questions out of all answered questions within 30 days. The time range of Access Requests is 180 days. |
| Stakeholder to be addressed | Auditors Managers System owners |
| Classification | Process efficiency |
| Method of measurement | Rejected Access Requests questions are questions that have been rejected during the approval process. This KPI shows the number of Access Requests questions rejected within 30 days. |
| Baseline | - |
| Available to user groups | Managers System owners Auditors |
| Configuration options | - |
% Access Request questions rejected within day
| Parameter | Description |
|---|---|
| KPI name | % Access Request questions rejected within day |
| KPI goal | Show the number of rejected Access Request questions of all completed within 24 hours. |
| Priority | 380 |
| Short description | This KPI shows the percentage of rejected Access Request questions out of all answered questions within 24 hours. The time range of Access Requests is 180 days. |
| Stakeholder to be addressed | Auditors Managers System owners |
| Classification | Process efficiency |
| Method of measurement | Rejected Access Requests questions are questions that have been rejected during the approval process. This KPI shows the number of Access Requests questions rejected within 24 hours. |
| Baseline | - |
| Available to user groups | Managers System owners Auditors |
| Configuration options | - |
% Access Request questions rejected within week
| Parameter | Description |
|---|---|
| KPI name | % Access Request questions rejected within week |
| KPI goal | Show the percentage of rejected Access Request questions of all answered within 7 days. |
| Priority | 382 |
| Short description | This KPI shows the percentage of rejected Access Request questions out of all answered questions within 7 days. The time range of Access Requests is 180 days. |
| Stakeholder to be addressed | Auditors Managers System owners |
| Classification | Process efficiency |
| Method of measurement | Rejected Access Requests questions are questions that have been rejected during the approval process. This KPI shows the number of Access Requests questions rejected within 7 days. |
| Baseline | - |
| Available to user groups | Managers System owners Auditors |
| Configuration options | - |
% Access Request questions rejected within month
| Parameter | Description |
|---|---|
| KPI name | % Access Request questions rejected within month |
| KPI goal | Show the percentage of rejected Access Request questions of all answered within 30 days. |
| Priority | 384 |
| Short description | This KPI shows the percentage of rejected Access Request questions out of all answered questions within 30 days. The time range of Access Requests is 180 days. |
| Stakeholder to be addressed | Auditors Managers System owners |
| Classification | Process efficiency |
| Method of measurement | Rejected Access Requests questions are questions that have been rejected during the approval process. This KPI shows the number of Access Requests questions rejected within 30 days. |
| Baseline | - |
| Available to user groups | Managers System owners Auditors |
| Configuration options | - |
# Open access approvals
| Parameter | Description |
|---|---|
| KPI name | # Open access approvals |
| KPI goal | The number of Access Requests that are open and have not been completed yet. You can see proper data for the context. |
| Priority | 386 |
| Short description | This KPI shows the number of Access Requests that are open and have not been completed yet. You can see proper data for the context. Managers can see their Access Requests, system owners see their system and auditors the entire company. |
| Stakeholder to be addressed | Auditors Managers System owners |
| Classification | Process efficiency |
| Method of measurement | Access approvals in the Data Warehouse which have been included in access review surveys, regardless of whether the answer has been submitted or not. Access approvals which are included in multiple surveys are only counted once. |
| Baseline | - |
| Available to user groups | Managers System owners Auditors |
| Configuration options | - |