Line Manager Recertifications (Process - IAM)

LM Recertification: Revocations per LM

1.0

Given that:

• is the set of all line managers in the organization

• is the subset of line managers that have not completed their recertification

• is the subset of line managers that have completed their recertification and revoked 0 access rights

• is the access right revocation threshold above which revocations are considered abnormally high

• is the subset of line managers that have completed their recertification and revoked between 1 and access rights inclusive

• is the subset of line managers that have completed their recertification and revoked more than access rights

• are exclusive subsets

• is the set cardinality function

The indicator is composed of the following series:

No Recert

Recert 0

Recert LowNormal

Recert High

This indicator is adequate for benchmarking given comparable recertification scopes and value.

The objective of this indicator is to measure the effectiveness of the LM Recertification process.

No Recert shows the ratio of line managers who failed to complete their recertification duty. This must be maintained as low as possible.

Recert 0 shows the ratio of line managers who completed their recertification duty but revoked 0 access rights. Two distinct causes may explain this result: 1) access rights were optimal and did not require any change or 2) the line manager ticked the boxes without due care. Further inquiry may be required to distinguish between the two.

Recert LowNormal shows the ratio of line managers who completed their recertification duty and revoked a few number of access rights . This is what is normally expectedthat is within expectations.

Recert Highshows the ratio of line managers who completed their recertification duty and revoked an important abnormally high number of access rights. A one time high may be caused by changes in the organization. But if the situation persists, this may reflect an inadequate setup where line managers must continuously adapt access rights. RBAC may not be implemented or not properly A root cause may be that RBAC is not implemented or improperly implemented.

• CISO (Stakeholder - IAM)

• IAM Management (Stakeholder)

• External Auditor (Stakehodler - IAM)

• Internal Control (Stakeholder - IAM)

• Line Manager

• CISO

• IT Risk Managers(Stakeholder - IAM)

• Top Management (Stakeholder)

This indicator may be specialized for different scopes. See Revocation Automation (Process - IAM) for typical scopes.

• In certain circumstances, the economical benefits of automation may be unjustifiable (e.g.: when processing low volumes of IAM artifacts on non-sensitive IT systems). Pursuing this indicator blindly could lead to economical waste.

• Poorly implemented automation may lead to new risks, e.g. silent automation errors leading to a false sense of security, automation mechanisms that are vulnerable to compromission or lead to denial of service.

• IT System inventory

• CMDB

• IAM software platformIAM System

Monthly

• Revocation Automation (Process - IAM)

• Revocation Automation Ratio (Indicator - IAM)