Knowledge base · Introduction
IGA, IAM, PAM — how they differ
The three abbreviations often appear side by side and are sometimes used interchangeably. Yet they describe three different jobs — and three different classes of tools.
- introduction
- approx. 6 minutes
In brief
Three questions, three classes of systems
| Class | Which question it answers | Typical functions |
|---|---|---|
| IAM — identity and access management | Is this really the person, and can they get in now? | Sign-in, single sign-on (SSO), multi-factor authentication. |
| IGA — identity governance | Who has access to what, who approved it and should they still have it? | Requests and approvals, access reviews, roles, reports for audit. |
| PAM — privileged access | How to protect administrator accounts and what was done with them? | A password vault, session recording, just-in-time access. |
IAM vs IGA
A slice, but a specialised one
IAM is the broadest term. IGA is part of it — focused not on the moment of sign-in itself, but on the process: where the access came from, who is responsible for it and how the organisation can prove it.
IGA systems are geared towards compliance. They let you build permissions at every level found in the organisation — position, function, department, country or region — and give a fuller picture of how the access granting process went. Once implemented, they usually become the most reliable and up-to-date database of identities and entitlements in the organisation.
Where sara.next fits in this division
sara.next is an IGA-class system. It does not replace the identity provider — it uses it for sign-in — and it is not a vault for administrator passwords. It deals with what lies in between: requests, approvals, executing changes, records and periodic reviews.
When
When IGA becomes a necessity
The more applications — especially cloud ones — the harder it is to guarantee the security of confidential data without a single place where access and permission levels are visible.
sara.next use casesSignals
- The organisation uses many SaaS applications and cloud systems
- Access to sensitive data is granted by e-mail or verbally
- Nobody can quickly say who has access to a given system
- A change of position does not lead to a change of permissions
- The organisation is subject to controls: SOX, NIS2, external audits
See sara.next on your own scenarios
During the presentation we will walk through an access request, approval, automatic execution of the change and a review — using examples from your organisation.