Identity and Access Management

Access should follow the person's current role

Joining, changing roles and leaving each call for a clear decision about accounts and permissions

The issue

The issue

01

The issue

Access granted informally or left unchanged after a role change becomes difficult to explain

02

Operational effect

Without an owner for each request, users wait and access reviews become harder

What is reviewed?

What is reviewed?

What is reviewed?

Map accounts, roles and requests across the systems included in the agreed scope

Service boundary

The business owner of a resource should approve decisions about job-related permissions

Management approach

Management approach

ABRITManagement approach
  • Management approachRecord why access was created, changed or removed and who approved it
  • Follow-upPersonnel changes need to reach the access process instead of relying on individual memory

Expected outcome

Expected outcome

01

Expected outcome

The organization can see who requested a resource and how the decision was made

02

Before you decide

Define the systems in scope and each role's authority with the organization

Assess

Define

  1. 01

    Assess

    Map accounts and roles

  2. 02

    Define

    Define access requests and approvals

  3. 03

    Review

    Review access on role changes and departure

Discuss your needs

Discuss your current IT environment

Share the environment and responsibilities you need covered so a suitable scope can be assessed

Discuss your needs