Knowledge base · Introduction
IGA system — what it is and how it works
IGA, or Identity Governance and Administration, is a class of systems that answer three questions: who has access to what, who allowed it and should they still have it.
- Identity Governance and Administration
- approx. 9 minutes
Definition
What IGA means
An IGA system is software for managing user identities and their permissions across many applications at once. It combines two things that stand side by side in the name. Administration: accepting access requests, approving them and executing changes in systems. And governance: periodically checking whether granted permissions are still justified, and providing evidence for audit.
In practice an IGA system is the central record of access in an organisation. It does not replace business applications or their own permission mechanisms. It sits above them and is responsible for the process: from the moment someone needs access to the moment they stop needing it.
Where the need came from
As long as an organisation had a few systems, permissions could be managed by hand. Today the average company uses dozens, and often more than a hundred, applications, each with its own accounts and roles. On top of that came regulations — SOX, GDPR, NIS2 — requiring the organisation to be able to show who has access to data and on what basis. A spreadsheet and a mailbox are no longer enough.
Features
What an IGA system consists of
Regardless of the vendor, systems of this class provide a similar set of functions.
Access requests
A structured request: application, role, scope, justification.
02Approval workflow
The decision is made by the person responsible for the area.
03Granting permissions (provisioning)
Manually based on a work order or automatically through an integration.
04Access reviews
Periodic recertification of entitlements by line managers or owners.
05Roles and policies
The permission model, limits, rules the system does not allow to be broken.
06Reports and audit trail
The history of every access entry and ready-made reports for controls.
How it works
The access lifecycle in an IGA system
IGA vs IAM
How an IGA system differs from an IAM system
The terms IAM and IGA are sometimes used interchangeably, but they describe different scopes. IAM (Identity and Access Management) covers all identity-related matters: the user directory, sign-in, single sign-on, multi-factor authentication and access control at the moment of use. IGA is a slice of IAM — specialised in the process of granting permissions and overseeing them.
The difference is easiest to see with an example. When an employee opens the finance system, the IAM solution checks whether it really is them and lets them in according to their permissions. The IGA system answers an earlier question: why does this employee have the accountant role at all, who approved it, in what scope and when was it last confirmed.
In a mature organisation both elements work together. The identity provider handles sign-in, and the IGA system — which also signs in through it — manages what everyone can do in applications.
When
How to tell that an organisation needs IGA
| Symptom | What it means |
|---|---|
| Nobody can quickly say who has access to a given system | No central record of access. |
| Access is granted on request by e-mail or verbally | Decisions do not leave the trace that an audit requires. |
| After a change of position an employee keeps their old permissions | Permissions accumulate, and so do risk and the number of licences. |
| Accounts of former employees are sometimes active | No process for revoking access. |
| Reviewing permissions is a once-a-year exercise in a spreadsheet | The control is neither repeatable nor reliable. |
| The organisation is subject to SOX, NIS2 or client audits | Evidence of access control is required regularly. |
Deployment
How to implement an IGA system so that it starts working
IGA implementations have a reputation for being long and expensive. Usually this results from one mistake: trying to cover all applications and automate everything from day one. A phased approach works much better.
- Records: import current access to the most important applications and establish who is responsible for each.
- Process: launch requests with approval, so that every new access leaves a trace.
- Oversight: carry out the first access review — it is usually what reveals the biggest clean-up to be done.
- Automation: integrate the systems with the most changes and leave the rest in the manual model.
The order matters. Records and reviews provide value without any technical integration, and at the same time they clean up the data that is later worth automating. Where to start also depends on the size of the organisation — the first stage looks different in a company of two hundred people and in a capital group.
Questions
Frequently asked questions about IGA systems
What is an IGA system?
An IGA (Identity Governance and Administration) system is software for managing identities and access: it handles access requests, approvals, granting and revoking permissions, periodic access reviews and reports for audit.
How does IGA differ from IAM?
IAM covers the whole of identity and access management, including sign-in and authentication. IGA is the part of IAM focused on the process of granting permissions and overseeing them: who has access, who approved it and whether it is still needed.
Is an IGA system only for large companies?
No. Access records and periodic reviews are useful even in an organisation with a dozen or so systems. Size determines how it is implemented, not whether the solution makes sense.
Does IGA require integration with all applications?
No. An application can be covered by the process without technical integration: access is imported from a file, and changes are made by an administrator based on an approved work order. Automation is added where it pays off.
What is an access review?
An access review, also called entitlement recertification, is the periodic confirmation by line managers or application owners that users should still have their access. Unconfirmed access is revoked.
How does IGA help meet NIS2 requirements?
NIS2 requires, among other things, risk management and access control. An IGA system provides a process for granting permissions with approval, regular reviews and evidence that can be presented during an inspection.
See an IGA system in action
We will show a request, approval, review and audit report using your applications as an example.