Identity Governance & Administration
sara.next
  1. sara.next
  2. Resources
  3. IAM system — identity and access management

Knowledge base · Introduction

IAM system — identity and access management

IAM, or Identity and Access Management, is a set of processes and tools that ensure the right people have the right access to the right resources — at the right time and with the ability to prove it.

  • Identity and Access Management
  • approx. 8 minutes

Definition

What IAM is

Identity and access management covers everything that happens between a person and an IT system: creating an account, confirming identity at sign-in, establishing what they are allowed to do, and closing the account when it is no longer needed. When they say "IAM system", organisations mean very different things — from a sign-in service to a complete platform for overseeing permissions.

It is therefore worth splitting IAM into layers. Each answers a different question and is usually provided by a different tool.

Layers

What identity and access management consists of

What identity and access management consists of
LayerQuestionTypical functions
Identity directoryWho is the user?Accounts, groups, employee attributes — e.g. Active Directory.
AuthenticationIs this really the person?Sign-in, single sign-on (SSO), multi-factor authentication (MFA).
Access controlCan they perform this operation now?Roles and permissions enforced in applications.
Oversight — IGAWhere did they get this access and should they still have it?Requests, approvals, access reviews, reports for audit.
Privileged access — PAMHow to protect administrator accounts?A password vault, session recording, just-in-time access.

sara.next provides the oversight layer (IGA). For sign-in it uses the organisation's identity provider.

Practice

The most common gap: there is sign-in, but no oversight

Most organisations start building IAM with authentication — and rightly so, because it is the first line of defence. They implement a directory, single sign-on and a second factor. After these investments there is often a belief that "identity is sorted".

Yet authentication answers only the question of whether the user is who they claim to be. It says nothing about whether they should have the access they have. An employee who has changed department three times and kept all their previous permissions signs in perfectly correctly — with a second factor — to systems they should have lost access to long ago.

Why it is the oversight layer that interests auditors

Controls — whether under SOX, NIS2 or an audit commissioned by a client — rarely ask about sign-in technology. They ask about the process: who approves access, how quickly it is revoked after an employee leaves, whether permissions are reviewed periodically. These are exactly the questions IGA answers.

That is why organisations that have already put sign-in in order usually choose an IGA system as the next step: it becomes the most reliable and up-to-date source of knowledge about identities and entitlements.

Plan

How to put IAM in order step by step

An order that works regardless of the size of the organisation.

  1. A single identity source

    A directory in which each employee has one account and up-to-date data.

  2. Shared sign-in

    Single sign-on and a second factor for key applications.

  3. Access records

    A single place with a list: who, to what, in what scope.

  4. Request process

    Every new access with approval from the responsible person.

  5. Reviews

    Periodic confirmation of entitlements and revocation of unnecessary ones.

  6. Privileged access

    Separate protection for administrative accounts.

Questions

Frequently asked questions about IAM systems

What is an IAM system?

An IAM (Identity and Access Management) system is a set of tools and processes for managing user identities and their access to resources: from creating accounts and sign-in to granting, reviewing and revoking permissions.

Are IAM and IGA the same thing?

No. IGA is part of IAM. IAM also covers authentication and access control at the moment of use, while IGA focuses on the process of granting permissions, verifying them periodically and providing evidence for audit.

Where should a company start implementing IAM?

By putting the identity source and sign-in in order, and then with access records and the request process. Access records and reviews can be launched without technical integration with all systems.

Is sara.next an IAM system?

sara.next is an IGA-class system, which means it provides the part of IAM responsible for requests, approvals, granting permissions, reviews and reporting. Sign-in takes place through the organisation's identity provider.

Put access in your organisation in order

Start with the element of IAM that provides evidence for audit: access records and reviews.