Best IGA platform for offboarding
Offboarding beyond the SSO disable: sessions, local logins, tokens, OAuth grants and shared admin passwords, the order to remove them, and proof that holds up.
On this page
The short answer
Iden ranks first for offboarding because it is the only vendor here to score 5 on apps with no SCIM and no API, where a leaver's access tends to survive. It builds those connectors at no extra cost and keeps the exit open until every account is closed. Lumos is second, and the better choice if nearly every app your leavers use already has a Lumos connector.
Our pickIden: it removes leavers from apps with no SCIM and no API through connectors it builds and maintains at no extra cost, and records how each account was closed.
Which IGA platform ranks first for offboarding?
Iden ranks first with 96.0 out of 100, followed by Lumos (88.0) and C1 (87.0). 10 vendors are scored on the published 13-criterion rubric, weighted for offboarding.
| Rank | Vendor | Score bar | Score |
|---|---|---|---|
| 1 | Iden | 96.0 | |
| 2 | Lumos | 88.0 | |
| 3 | C1 | 87.0 | |
| 4 | Zluri | 86.0 | |
| 5 | SailPoint | 85.0 | |
| 6 | Veza | 83.0 | |
| 7 | Microsoft | 82.0 | |
| 8 | Okta | 82.0 | |
| 9 | Saviynt | 81.0 | |
| 10 | Opal Security | 74.0 |
How this ranking is weighted
Every vendor gets the same score on each criterion in every report. What changes is the weight: 3 matters most for this reader, 0 is left out. The full scoring guide is on the About page.
| Criterion | Weight | Why it matters here |
|---|---|---|
| Connectors for SCIM and API apps | ||
| Apps with no SCIM and no API | Leavers keep access in the apps SCIM never reached. | |
| Entitlements below the group level | ||
| Joiner, mover, leaver from the HRIS | ||
| Depth of offboarding | Sessions, tokens, local accounts and shared logins survive an SSO deactivation. | |
| Access requests and time-bound access | ||
| Access reviews | ||
| Audit evidence and compliance mapping | Auditors sample leavers and ask for proof each account is gone. | |
| Separation of duties | ||
| Non-human identities | ||
| Time to deploy and services needed | ||
| Pricing transparency and connector cost | ||
| Enterprise depth |
Scores on the criteria weighted most
| Vendor | Apps with no SCIM and no API | Depth of offboarding | Audit evidence and compliance mapping | Total |
|---|---|---|---|---|
| Iden | 5 | 5 | 5 | 96.0 |
| Lumos | 3 | 5 | 5 | 88.0 |
| C1 | 3 | 5 | 4 | 87.0 |
| Zluri | 4 | 4 | 5 | 86.0 |
| SailPoint | 4 | 4 | 4 | 85.0 |
| Veza | 3 | 4 | 5 | 83.0 |
| Microsoft | 3 | 4 | 4 | 82.0 |
| Okta | 3 | 4 | 3 | 82.0 |
| Saviynt | 4 | 3 | 5 | 81.0 |
| Opal Security | 3 | 3 | 4 | 74.0 |
Scores are out of 5. The scores, weights and evidence for every report can be downloaded as JSON or CSV.
What keeps working after the SSO account is disabled
Disabling the user in the identity provider blocks the next SSO login and, where SCIM is connected, sends a deactivation. RFC 7643 defines the SCIM active flag as the user's "administrative status" and says its meaning "is determined by the service provider." What happens to that user's sessions, tokens and scheduled jobs is each app's call. The usual survivors:
- App sessions, which last until the app's own timeout or a revoke inside that app.
- Password logins left on alongside SSO, accounts created before SSO was enforced, and break-glass admins.
- Personal API tokens and OAuth grants, such as a reporting tool the person authorized against the CRM.
- Shared admin logins whose password they knew.
- Apps that were never behind SSO: the supplier portal, the tool bought on a card, the on-prem system with its own user table.
NIST SP 800-53 PS-4 asks you to "terminate or revoke any authenticators and credentials associated with the individual," and AC-2 part k asks for shared account authenticators to be changed when someone leaves the group.
The order depends on how the person leaves. For a planned leaver, transfer ownership of files, scheduled reports and integrations first, because deleting an account in many apps deletes what it owned. For an involuntary termination, revoke sessions and rotate shared credentials while the meeting is still going, and transfer afterwards. Either way, disable now and delete later: RFC 7644 lets a SCIM provider "choose not to permanently delete the resource" after a DELETE, so a successful call proves less than it looks.
How Iden, Lumos and C1 compare on leavers
All 3 score 5 on offboarding depth. Lumos's Google Workspace connector signs the user "out of all web and device sessions," and its offboarding docs close an offboarding only when every task it generated is done. C1's Google Workspace connector signs the user out and transfers Drive ownership, and its automation examples show a leaver flow that opens a review campaign as "a human checkpoint for any access that wasn't automatically revoked." Iden's offboarding page says one pass records how each account closed, and its lifecycle page says sessions are revoked before credentials rotate, since a new password does not end an open session.
They split on the app with no SCIM and no API. Lumos sends it to Manual Tasks that "route provisioning work to a person and track it to completion." C1's custom connectors need an API that can list users, and for the rest it opens Jira tickets. Both keep the step in the audit trail, but a person still removes the account. Iden's FAQ says it builds a missing connector "usually in 48 hours, at no extra cost," and covers apps with no clean API through its custom automation framework.
On credentials the leaver created, Lumos's NHI inventory lists API keys and agents with an owner and C1's NHI dashboard flags unowned ones; Iden's offboarding playbook says it rotates or revokes them by policy.
Lumos and C1 are stronger on reach. Lumos lists 300+ integrations and C1 400+ connectors, against the 200+ non-SCIM app connectors Iden's llms.txt claims, and both document provisioning repository permissions, which the Iden connector tables we checked don't show.
When another vendor is the better call
- Lumos, if almost every app your leavers touch is in its catalog and you want cloud service principals and IAM roles in the same inventory. Lumos publishes no price.
- C1, if the same platform should also flag SoD conflicts on access requests, where it scores 5 and Iden 3, and you want published packaging rather than a custom quote. C1 has announced it is joining Workday, so check how that affects your contract term.
- Zluri, if disabling the leaver's laptop belongs in the same workflow: it lists "disabling devices" among its offboarding actions. Infotech completed its acquisition of Zluri on 14 October 2026.
- Microsoft Entra ID Governance, if most leaver access is in apps connected to Entra. Its leaver tasks include "Revoke all refresh tokens for user," at a published $7 per user per month on top of Entra ID P1 or P2.
- SailPoint or Saviynt, if an IAM team of 10 or more already runs one of them. Iden's own llms.txt says it isn't built for that team.
Some steps stay manual on Iden too. Its offboarding playbook says a shared admin account with no single owner "can't be closed until someone decides who inherits it," and its non-SCIM playbook says it needs a human for an admin console behind hardware MFA.
Test it with a leaver who holds everything
Auditors trace sampled leavers through each app's own user list, so run 1 test user through every shortlisted vendor.
- Give the test user a local password in 1 app, a personal API token, an OAuth grant, an owned scheduled report and the password to 1 shared admin login.
- Offboard them, then pull each app's own user and token lists. Check the report still runs under a new owner.
- Include 1 app with no SCIM and no API. Note whether the vendor removes the account or opens a task, and whether the offboarding stays open until it's done.
- Start an involuntary termination by hand, outside the HRIS, and time it until sessions are revoked.
- Export the evidence and check each row has the app, the method, the timestamp, the result and who cleared any manual step.
Scorecards
Each score, the reason for it and the page it rests on. Every score comes from the vendor's own public pages.
1Iden96.0
Iden is an identity governance (IGA) platform that automates onboarding, offboarding, access requests and access reviews across SaaS, internal and legacy apps, including apps without SCIM or an API. It runs alongside an existing SSO (Okta, Entra, Google Workspace, JumpCloud) rather than replacing it. idenhq.com
| Connectors for SCIM and API apps | Iden publishes 176 per-app connector pages across 14 categories and provisions any SCIM app out of the box, with major SaaS such as Slack, Salesforce, Google Workspace, GitHub and AWS listed. The catalog is smaller than the 300 to 400 connector libraries some peers publish. [1] [2] | |
| Apps with no SCIM and no API | Iden documents a vendor-built method for apps with no SCIM and no API: console automation that drives the admin UI, plus custom connectors that Iden builds and maintains at no extra cost, so the customer does not build them. [1] [2] | |
| Entitlements below the group level | Iden summary pages claim channel-, repository- and project-level provisioning, but the published capability tables for GitHub, Slack and Salesforce list user create, update and delete plus read-only groups or group membership. Public pages do not describe any connector writing an in-app role, repo or channel grant, so provisioning is documented only at the user and group level. [1] [2] | |
| Joiner, mover, leaver from the HRIS | Iden documents an HRIS-triggered joiner plan built before the start date from department, title, manager and employment type (birthright), a mover recompute that removes grants tied to the old department, and leaver workflows. [1] [2] [3] | |
| Depth of offboarding | Offboarding goes beyond SSO: session revocation, data and ownership transfer before deletion, a record of how each account closed, and an offboarding that stays open until every account is closed, as a verification step. [1] [2] [3] | |
| Access requests and time-bound access | Self-service requests in Slack or Teams go to the owner for approval, and grants expire automatically: time-boxed, tied to a task, or break-glass. [1] [2] [3] | |
| Access reviews | Campaigns give reviewers context such as HR employment status, last use and capability descriptions, and revocation runs from the review decision. [1] [2] [3] | |
| Audit evidence and compliance mapping | Review and finding evidence is exportable and mapped to named controls: SOC 2 CC6.1 to CC6.3, ISO 27001 A.9 and A.5.18, and HIPAA. [1] [2] | |
| Non-human identities | Iden documents an inventory of service accounts, API keys and AI agents with required owners, expiry on long-lived credentials, inclusion in access reviews, and revocation. Iden states one limit: discovery covers only connected apps. [1] [2] [3] | |
| Time to deploy and services needed | Iden publishes a deployment time in days to weeks with no systems integrator, and offers a 2-week trial. [1] [2] | |
| Pricing transparency and connector cost | Public per-user price, with every connector included, non-SCIM and custom connectors among them. [1] [2] |
2Lumos88.0
Lumos is an identity governance and security platform covering access requests (AppStore), lifecycle management, access reviews and non-human identity and AI agent governance, with an AI agent (Albus) for role design and reviews. It is aimed at security, identity and IT teams governing human, machine and AI identities. lumos.com
Public ratings (not scored): G2 (via AWS Marketplace, external reviews from G2) 4.7 (69 reviews)
| Connectors for SCIM and API apps | Lumos publishes a catalog of 300+ integrations, with 253 integration docs pages, plus a generic SCIM 2.0 connector that syncs and provisions any SCIM app without a dedicated connector. [1] [2] | |
| Apps with no SCIM and no API | For apps with an API or database, Lumos documents generic REST and database connectors, a Connector SDK and provisioning webhooks, but the customer configures or builds these. For apps with no API, the documented path is CSV sync plus Manual Tasks routed to a person and tracked to completion. [1] [2] [3] | |
| Entitlements below the group level | Connector docs describe provisioning in-app permissions below the group level, such as per-user Bitbucket project and repository permissions, and the AppStore syncs assignable permissions. [1] | |
| Joiner, mover, leaver from the HRIS | The HRIS is the source of truth, triggering onboarding on start date or account creation and offboarding on deactivation or end date, with access policies for birthright and mover workflows that re-evaluate policies when an attribute changes. [1] [2] [3] | |
| Depth of offboarding | Removal workflows run in order and go beyond account disable: session sign-out, data transfer and group ownership transfer in Google Workspace, and manual tasks for app admins. An offboarding completes only when all its tasks finish. [1] [2] [3] | |
| Access requests and time-bound access | Self-service AppStore requests from web, Slack or Teams go through flexible approvals, and time-based access is removed automatically at the end of the window. Time-based access needs either IdP assignment or a deprovisioning webhook for the app. [1] [2] | |
| Access reviews | Campaigns at account and permission level give reviewers context such as employment status and AI insights from usage and prior decisions, and rejected access is removed automatically through deprovisioning workflows. [1] [2] | |
| Audit evidence and compliance mapping | Lumos produces a PDF audit report per review, guidance on proving completeness and accuracy for SOX and SOC 2 audits, and built-in permission tags for named frameworks (SOC2, SOX, ISO27001, PCI, HITRUST). [1] [2] [3] | |
| Non-human identities | Lumos documents discovery and inventory of service principals, IAM roles, API keys and AI agents with owners and business justification, plus MCP governance. Public pages do not describe credential expiry enforcement for NHIs. [1] [2] | |
| Time to deploy and services needed | Lumos publishes lifecycle deployment in weeks and offers a guided self-implementation program (Launchpad). [1] [2] | |
| Pricing transparency and connector cost | No public price and no published plans or packaging; the pricing page is a demo form and Lumos says pricing is custom. [1] |
3C187.0
ConductorOne now trades as C1 (c1.ai; conductorone.com now serves c1.ai), and its site banner announces that C1 is to join Workday. C1 is an identity platform covering identity governance (lifecycle, access requests and JIT, access reviews, SoD) alongside AI agent, MCP and secrets products for IT, security, IAM and compliance teams. c1.ai
Public ratings (not scored): G2 (via Toolradar aggregator) 4.8 (13 reviews)
| Connectors for SCIM and API apps | C1 publishes a library of 400+ out-of-the-box connectors, with about 400 connector docs pages, plus a configurable SCIM connector. [1] [2] | |
| Apps with no SCIM and no API | Apps with an API can be covered by HTTP and SQL connectors the customer configures, the Baton SDK, or AI-built custom connectors, which are in early access, sync only and need an API that lists users. For apps with no API, the documented path is file-based sync plus tickets in an external ITSM; the marketing FAQ says no-API legacy apps can be integrated, but public pages do not describe provisioning or deprovisioning them without tickets. [1] [2] [3] | |
| Entitlements below the group level | Requests and provisioning work at resource level, such as groups, repos and roles within an app, and the GitHub v2 connector provisions repository permissions. [1] | |
| Joiner, mover, leaver from the HRIS | The HRIS or IdP directory is the source of truth, with user created and updated triggers, birthright access profiles, automatic re-enrollment when a mover starts matching a different profile, and revocation for leavers. [1] [2] | |
| Depth of offboarding | Leaver automation revokes entitlements across connected apps and opens a review campaign for any access that remains, as a verification step. Connector actions include signing out all sessions, revoking OAuth tokens and transferring Drive and Calendar ownership in Google Workspace. [1] [2] [3] | |
| Access requests and time-bound access | Self-service requests from web, Slack, Teams or CLI go through approval policies with a max request duration, after which C1 revokes the grant automatically, and there is an emergency access path. [1] | |
| Access reviews | Campaigns give reviewers insights such as peer access, risk level and recommendations, and revocation can run automatically after the campaign. [1] [2] | |
| Audit evidence and compliance mapping | Campaign reports export with verifiable file hashes, alongside conflict-monitor reports and logs that can be exported to a SIEM. Campaigns can be scoped by a compliance framework attribute, but its values are tags the customer creates rather than a built-in framework mapping, and SOX and ISO 27001 are named only in the SoD context. [1] [2] [3] | |
| Non-human identities | An Identities dashboard discovers app registrations, assumable roles, managed identities, service accounts, secrets and agents, with owners and findings such as unowned NHIs. C1 says its NHI capabilities are still expanding, and public pages do not describe expiry or lifecycle for discovered NHIs; expiry is documented only for the service principals and agent tokens C1 itself issues. [1] [2] | |
| Time to deploy and services needed | C1 publishes go-live in weeks, 1 month on average, with guided agentic onboarding; deployment experts are offered but not stated as required. [1] [2] | |
| Pricing transparency and connector cost | No public price, but packaging is public: SKU-based Platform or usage-based Flex pricing, Pro and Advanced platform levels, program size by managed identities, and named modules (Lifecycle, Access, Comply). Exact pricing is quoted per customer. [1] [2] |
4Zluri86.0
Zluri is a SaaS management and identity governance (IGA) platform covering app and identity discovery, onboarding and offboarding workflows, access requests, access reviews, SoD and identity posture, built on a direct-API integration layer that reaches apps outside SSO and SCIM. Zluri is now an Infotech company (formerly Info-Tech Research Group), acquired in October 2026 and run as a standalone division; the product name is unchanged. zluri.com
Public ratings (not scored): AWS Marketplace (2 AWS reviews + 177 G2 reviews) 4.6 (179 reviews)
| Connectors for SCIM and API apps | Zluri publishes a catalog of 300+ out-of-the-box API connectors across IdPs, HRIS, ITSM and major SaaS, plus SCIM provisioning support. [1] [2] [3] | |
| Apps with no SCIM and no API | The Universal Identity Connector documents interface automation that provisions through the app UI when no API or database access exists, plus database orchestration and ITSM tasks. Custom integrations are quoted with timelines based on system complexity, and public pages do not say whether the connector is included or delivered as a service. [1] [2] | |
| Entitlements below the group level | Workflow actions provision resource-level access such as folders, repositories, channels and projects, beyond group membership. [1] [2] | |
| Joiner, mover, leaver from the HRIS | HRMS-triggered onboarding applies birthright, department and role rules, automation rules handle attribute changes, and mover handling is documented. HRIS triggers are documented for HiBob, Personio, BambooHR and SDK sources, and Zero Touch setup is done with the Zluri CSM. [1] [2] [3] | |
| Depth of offboarding | Offboarding goes beyond SSO: revocation in non-SSO apps, signing users out, data backup and ownership transfer, email forwarding and MDM device lock or wipe. Public pages do not describe a step that verifies offboarding is complete; verification is documented for onboarding only. [1] [2] | |
| Access requests and time-bound access | Self-service requests in Slack or the app catalog go through multi-step, policy-driven approvals with a requested duration field, and time-bound access is revoked automatically. [1] [2] | |
| Access reviews | Recurring certifications give reviewers activity data and risk insights, and closed-loop remediation deprovisions rejected access via API. [1] [2] | |
| Audit evidence and compliance mapping | Audit-ready review reports export with SOX, SOC 2 and ISO 27001 named, and SoD policies are mapped to SOX 404, SOC 2 TSC, ISO 27001 A.9 and NIST AC-5. [1] [2] [3] | |
| Non-human identities | Zluri discovers service accounts, keys, tokens, bots and AI agents per app, ranks them by privilege, and lets admins assign owners, reclassify, merge and archive records. Public pages do not describe expiry, rotation, disabling or access revocation for non-human identities, so coverage is visibility plus ownership. [1] [2] | |
| Time to deploy and services needed | Zluri publishes timelines in weeks (standard integrations 2 to 4 weeks, enterprise connectors 4 to 8 weeks, weeks to first policy for SoD) with no required services stated. Sign-up is invite-only, and HRIS-triggered onboarding is configured with the Zluri CSM rather than self-serve. [1] [2] [3] | |
| Pricing transparency and connector cost | No public price on zluri.com (the pricing URL redirects to the demo form) and no published packaging. The Zluri AWS Marketplace listing shows a single Base Plan figure with a note to contact Zluri for private pricing, with no per-user price or connector terms. [1] |
5SailPoint85.0
SailPoint Identity Security Cloud is a SaaS identity governance platform for large enterprises covering lifecycle provisioning, access requests, certifications, separation of duties and machine and AI-agent identities. SailPoint now markets it as SailPoint Human Fabric, which it describes as the evolution of Identity Security Cloud, sold in Agentic Standard, Agentic Business and Agentic Business Plus suites. sailpoint.com
Public ratings (not scored): PeerSpot 4.1 (72 reviews)
| Connectors for SCIM and API apps | SailPoint publishes a large connector catalog (deep governance, quick compliance and discovery connectors, covering SaaS such as GitHub, Salesforce, Workday, Okta and Entra ID) plus a SCIM 2.0 source that manages any SCIM 2.0 compliant system. [1] [2] [3] | |
| Apps with no SCIM and no API | SailPoint supplies a Disconnected Application Connector that provisions accounts to web apps with no API by recording browser operations, plus an RPA connector for apps without modern APIs. The connector does not work with apps behind SSO, MFA or federated sign-in, and the RPA route depends on an RPA platform the customer already runs. [1] [2] [3] | |
| Entitlements below the group level | Connector docs show provisioning of in-app objects below the group level, such as adding and removing Salesforce permission sets, permission set groups, roles and managed packages, and GitHub teams as entitlements. [1] [2] | |
| Joiner, mover, leaver from the HRIS | Public docs describe HR-driven lifecycle states (pre-hire, active, leave of absence, terminated), birthright roles, and mover handling that removes access granted by role criteria when an identity no longer matches. [1] [2] [3] [4] | |
| Depth of offboarding | Beyond account disable or delete, a terminated lifecycle state can revoke roles, access profiles and entitlements across all sources, and SailPoint can publish Session Revoked (Shared Signals) events when an identity enters a lifecycle state. Public pages do not describe ownership transfer or token cleanup when someone leaves. [1] [2] | |
| Access requests and time-bound access | Self-service requests with approvals can require an end date and maximum duration, and Just-In-Time (Privilege on Demand) access is removed when the activation period ends. Time-bound requests are in the core docs, while the suites page places JIT provisioning for elevated access in Agentic Business and above. [1] [2] [3] | |
| Access reviews | Certification campaigns revoke rejected access automatically on direct-connect sources, and reviewers can see activity data such as days active in the last 90. Activity data needs Activity Insights connectors, which SailPoint says to arrange through the CSM. [1] [2] | |
| Audit evidence and compliance mapping | Audit reports can be downloaded, the compliance page names SOX, GDPR and HIPAA, and Agentic Fabric produces framework-aligned evidence exports for AI agents. Public pages do not describe a framework-mapped evidence pack for human access governance. [1] [2] [3] | |
| Non-human identities | SailPoint documents discovery and classification of machine accounts, certification of application identities, a credentials inventory (API keys, tokens, client secrets) with owners and expiry status, and an AI agent registry. Agentic governance requires the Agentic Business or Business Plus suite. [1] [2] [3] | |
| Time to deploy and services needed | SailPoint does not publish a deployment time for the core platform, on-prem sources need a virtual appliance cluster, and it sells implementation services covering application onboarding and role modeling. The only claim of weeks is for the Access Risk Management add-on. [1] [2] [3] | |
| Pricing transparency and connector cost | No public price, but packaging is public: 3 suites, add-ons, and an NHI allotment per licensed human identity. [1] [2] |
6Veza83.0
Veza is an identity security platform built on an access graph of effective permissions across cloud, SaaS, data systems and on-prem apps, with IGA modules for access reviews, lifecycle management, access requests, SoD and NHI and AI-agent security. ServiceNow has completed its acquisition of Veza and Veza is now part of ServiceNow, with the product still sold as Veza; these scores cover its Next-Gen IGA use case (Veza Access Governance). veza.com
Public ratings (not scored): PeerSpot 3.9 (4 reviews) · AWS Marketplace (3 AWS reviews + 1 PeerSpot review) 3.9 (4 reviews)
| Connectors for SCIM and API apps | Veza lists 325+ native integrations plus generic SCIM 2.0 provisioning, but provisioning and deprovisioning run through Lifecycle Management, which requires a separate Veza license. [1] [2] | |
| Apps with no SCIM and no API | Apps without a built-in or SCIM connector are covered through the Open Authorization API (connector scripts the customer builds or deploys), flat files, ServiceNow ticket creation or custom REST payloads. [1] [2] [3] | |
| Entitlements below the group level | Access Profiles and Access Requests provision in-app entitlements such as roles, permission sets, licenses and groups in target apps. Fulfilment runs through Lifecycle Management provisioning policies, which require a separate Veza license. [1] [2] | |
| Joiner, mover, leaver from the HRIS | HR-sourced policies and workflows cover joiners, movers and leavers, with birthright Access Profiles and Business Roles. Lifecycle Management requires a separate Veza license. [1] [2] | |
| Depth of offboarding | Leaver workflows disable or suspend accounts, remove all entitlements, can end active sessions on supported integrations and cover local accounts, and review remediations can be verified. All of this ships in Lifecycle Management, which requires a separate Veza license. [1] [2] [3] | |
| Access requests and time-bound access | Access Hub supports self-service and on-behalf requests with multi-level approvals, JIT access policies and policy-enforced auto-expiration. Approved requests are fulfilled by Lifecycle Management provisioning policies, though the Access Requests pages carry no separate license note. [1] [2] | |
| Access reviews | Campaigns show risk scores, usage insights and past certification decisions, and Veza can verify that rejected access was removed. Automatic revocation on sign-off needs Access Reviews Advanced and works only for apps with provisioning turned on. [1] [2] [3] | |
| Audit evidence and compliance mapping | Audit-ready reports are named against SOX, ISO 27001, SOC 2 and GDPR, review reports export to Excel, and completeness-and-accuracy procedures for auditors are documented. [1] [2] | |
| Non-human identities | Veza discovers service accounts, keys, secrets and AI agents across 40+ integrations, assigns owners linked to the lifecycle of the human owner, tracks credential expiry and rotation, and can disable NHI accounts. [1] [2] [3] | |
| Time to deploy and services needed | Veza publishes connection in minutes and says no professional-services integration build is needed; the platform is agentless SaaS with a getting-started guide customers follow themselves. On-prem sources need an Insight Point container the customer runs. [1] [2] | |
| Pricing transparency and connector cost | No public price on veza.com (it has no pricing page); the Veza AWS Marketplace listing shows packaged list prices with identity and connector caps ($100,000 per 12 months for the platform, $150,000 with Workflows), so connectors are capped per package. [1] |
7Microsoft82.0
Microsoft Entra ID Governance adds entitlement management (access packages), access reviews, lifecycle workflows, privileged identity management and app provisioning to a Microsoft Entra ID tenant. It is sold as a per-user add-on for Entra ID P1/P2 customers and is also bundled in Microsoft Entra Suite and Microsoft 365 E7. microsoft.com
Public ratings (not scored): PeerSpot 3.9 (14 reviews)
| Connectors for SCIM and API apps | Microsoft publishes a gallery of preintegrated provisioning connectors, which it describes as hundreds of apps rather than thousands, plus generic SCIM 2.0 support. [1] [2] | |
| Apps with no SCIM and no API | Non-SCIM on-prem apps can be reached through the provisioning agent and ECMA connector host (SQL, LDAP or imported ECMA2 connectors), which the customer configures or builds. For apps with their own directory and no provisioning integration, Microsoft says removals may have to be done manually. [1] [2] [3] | |
| Entitlements below the group level | Access packages can assign application app roles, Teams and SharePoint sites below the group level, and SAP IAG business roles in preview. Otherwise in-app permissions depend on the app exposing app roles or groups, and public pages do not describe a general entitlement discovery and exchange model like a dedicated entitlement catalog. [1] [2] | |
| Joiner, mover, leaver from the HRIS | Entra documents HR-driven inbound provisioning from Workday and SuccessFactors, lifecycle workflows for joiners, movers and leavers, and attribute-based automatic assignment policies for birthright access. [1] [2] [3] | |
| Depth of offboarding | Leaver workflow tasks disable the account, revoke all refresh tokens, remove groups, Teams, licenses and access packages, and delete the user, while provisioning removes accounts downstream. Content and ownership transfer is left to the app or custom Logic Apps extensions, and public pages do not describe a step that verifies offboarding is complete. [1] [2] [3] | |
| Access requests and time-bound access | Users request access packages through self-service with multi-stage approvals, and policies make assignments time-limited so they expire automatically; PIM adds time-bound role activation. [1] [2] | |
| Access reviews | Recurring reviews come with smart recommendations and inactive-user decision helpers, and denied access is removed automatically when auto-apply is turned on. [1] [2] [3] | |
| Audit evidence and compliance mapping | Access review history and audit logs can be downloaded, and Microsoft publishes guidance mapping Entra governance controls to named frameworks (PCI DSS requirement 7, NIST, FedRAMP). That mapping is guidance, not an evidence export tagged by framework. [1] [2] | |
| Non-human identities | Agent identities need a human sponsor, get time-bound access packages and pass to a new sponsor when the sponsor leaves, and service principals can be assigned access packages. All of this needs Microsoft Agent 365 or Microsoft 365 E7 on top of ID Governance. [1] [2] | |
| Time to deploy and services needed | Setup is self-serve in the tenant with no required services, but Microsoft does not publish a typical deployment time. [1] [2] | |
| Pricing transparency and connector cost | Public per-user price of $7/user/month standalone, billed annually, on top of a required Entra ID P1 ($7) or P2 license. Gallery and on-prem provisioning connectors are included from P1, not priced per connector. [1] [2] [3] |
8Okta82.0
Okta Identity Governance (OIG) is the IGA product from Okta, made of Lifecycle Management, Workflows and Access Governance (access requests, access certifications, entitlement management, separation of duties) on top of the Okta workforce identity platform. Okta positions it as security-driven governance for the modern enterprise and sells it inside its Essentials suite and above or as an add-on. okta.com
Public ratings (not scored): PeerSpot (Okta Platform, all modules) 4.3 (127 reviews)
| Connectors for SCIM and API apps | The Okta Integration Network lists 8,000+ integrations, 969 of them tagged Lifecycle Management, and Okta states SCIM provisioning for thousands of apps out of the box. [1] [2] [3] | |
| Apps with no SCIM and no API | Apps without SCIM or an API are reached through the On-Premises Provisioning agent with a SCIM server or custom connectors the customer supplies, or through request tasks routed to Jira or ServiceNow. The new on-demand connectors still need the app to publish an OpenAPI spec, so public pages do not describe a path for apps with no API that the customer does not build. [1] [2] [3] | |
| Entitlements below the group level | Entitlement Management stores app entitlements in Okta, assigns them by policy and exchanges them with downstream apps that have provisioning turned on, so in-app permissions below the group level are provisioned, not just read. [1] [2] | |
| Joiner, mover, leaver from the HRIS | The HRIS (Workday, BambooHR, SuccessFactors) is the source of truth with real-time triggers, birthright app provisioning, and explicit mover handling that removes old permissions. [1] [2] [3] | |
| Depth of offboarding | Deactivation deprovisions the user from assigned apps and ends Okta sessions, and a Workflows template transfers Google Drive ownership. Session and token revocation in apps (Universal Logout) sits in Identity Threat Protection, an add-on below the Professional suite, and public pages do not describe a step that verifies offboarding is complete. [1] [2] [3] | |
| Access requests and time-bound access | Self-service requests from the dashboard, Slack or Teams go through multi-step approval sequences, and conditions set a duration after which access is revoked automatically. [1] [2] | |
| Access reviews | Certification campaigns revoke access automatically on the reviewer decision, and Governance Analyzer shows reviewers usage history, past decisions, SoD conflicts and how access was assigned. [1] [2] | |
| Audit evidence and compliance mapping | Okta documents campaign and request reports covering 3 years of closed campaigns, plus System Log events, and names SOC2 and SOX as goals. Public pages do not describe an evidence export mapped to named framework controls. [1] [2] | |
| Non-human identities | AI agents get registered identities with human owners and certification campaigns, service accounts can be certified and vaulted, and ISPM discovers unmanaged NHIs. These sit in Okta for AI Agents (an add-on), ISPM (Professional and Enterprise) and Privileged Access, not in base OIG. [1] [2] [3] [4] | |
| Time to deploy and services needed | Okta offers a self-serve trial and admin-console setup with no required services and publishes deployment times, but its own figures show about a quarter of customers live within 30 days and the median customer taking up to 6 months. [1] [2] | |
| Pricing transparency and connector cost | Public per-user price: Essentials at $17/user/month includes Lifecycle Management and Access Governance, and OIN connectors and the new on-demand connectors carry no extra fee. Billing is annual, with a $1,500 annual minimum and Workflows flow caps by suite. [1] [2] [3] |
9Saviynt81.0
Saviynt Identity Cloud is a cloud-native converged identity platform combining identity governance and administration with application access governance, privileged access management, identity security posture management and non-human identity governance. Saviynt sells it in Essentials, Pro and Premier tiers to enterprises, and markets AI-agent governance separately as Zuma. saviynt.com
Public ratings (not scored): PeerSpot 3.7 (28 reviews)
| Connectors for SCIM and API apps | The Saviynt Exchange lists 445 apps, 119 of them tagged Saviynt-developed, and Saviynt says it onboards apps with SCIM and REST APIs. Saviynt-developed connectors are included in tier pricing. [1] [2] [3] | |
| Apps with no SCIM and no API | Saviynt describes a vendor-supplied way to bring apps with no integration protocol under management: an AI onboarding agent with a computer-use agent that drives the app UI, and support for web, CLI and thick-client apps. This is described only on product pages, since the docs need a login, and the disconnected-app connectors on the Exchange (Cerby, Redblock, Torch) are partner products. [1] [2] [3] | |
| Entitlements below the group level | Saviynt documents provisioning of fine-grained entitlements below the group level, such as Salesforce entitlements down to object fields, through rules-based and request-based provisioning. [1] [2] | |
| Joiner, mover, leaver from the HRIS | Public pages describe an HR-driven lifecycle from Workday HR records, with access assigned at onboarding and revoked at departure, plus rules-based (ABAC) provisioning. Public pages do not describe mover handling or birthright rules; birthright appears only in a partner services listing, and product docs need a login. [1] [2] | |
| Depth of offboarding | Saviynt describes automatic revocation of access on departure across connected apps. Public pages do not describe session or token revocation, local accounts or ownership transfer at offboarding, and product docs need a login. [1] | |
| Access requests and time-bound access | Self-service requests get risk-based approvals, and Just-in-Time access grants time-bound access and removes it automatically. The pricing page lists just-in-time access in the Pro tier, not Essentials. [1] [2] [3] | |
| Access reviews | Certification campaigns offer AI recommendations, automatic decisions for low-risk items and risk-aware remediation suggestions. Marketing copy implies rejected access is revoked, but public docs do not describe automatic revocation. [1] [2] [3] | |
| Audit evidence and compliance mapping | Reporting controls are mapped to named regulations (SOX, PCI, FedRAMP, HIPAA), a Unified Controls Framework is cross-mapped to standards such as CIS and NIST CSF, and compliance audit reports cover GDPR and SOX. [1] [2] [3] | |
| Non-human identities | Saviynt documents discovery of workloads, accounts and credentials, ownership and risk context, and AI agent ownership and offboarding (Zuma). Public pages do not describe credential expiry or rotation, and AI-agent governance is marketed as the separate Zuma platform. [1] [2] | |
| Time to deploy and services needed | The Saviynt commitment of value in less than 12 weeks is tied to its Expert Services packages, and its own success package schedules a deployment review 4 to 6 months after purchase, which points to services-assisted deployments over months. [1] [2] | |
| Pricing transparency and connector cost | No public price, but packaging is public (Essentials, Pro and Premier tiers plus independent solutions), and Saviynt-developed connectors are included. [1] [2] |
10Opal Security74.0
Opal is an access governance platform centred on just-in-time, time-bound access requests, access reviews and policy-as-code (OpalScript), extended to service accounts and AI agents (Opal Zero, launched September 2026). Opal says it is built for engineer-led, cloud-native enterprises and states it is not positioned as the SoD and certification leader for the largest regulated enterprises. opal.dev
Public ratings (not scored): AWS Marketplace (aggregates G2 reviews) 4.6 (30 reviews)
| Connectors for SCIM and API apps | The integrations docs list about 60 connectors (55+ per the docs page; the marketing page says 250+), covering Okta, Google, Azure, AD, Workday, Rippling, AWS, GCP and major SaaS. Public pages do not describe a generic outbound SCIM connector, and user provisioning is supported only on a listed subset of integrations. [1] [2] [3] | |
| Apps with no SCIM and no API | Apps without a supported integration are handled by a Custom Connector the customer builds by implementing API endpoints, or by ticket propagation to Jira, Linear or ServiceNow for manual fulfilment. [1] [2] | |
| Entitlements below the group level | Public docs describe provisioning of resources below the group level: AWS IAM roles, RDS, EC2, EKS, GCP projects and folders, Box folders, Grafana folders and dashboards, and GitHub repositories. [1] [2] | |
| Joiner, mover, leaver from the HRIS | Access Rules use HRIS and IdP attributes (Workday, Rippling, Okta, Google, Entra) to grant and remove access on join, move and leave. Opal itself says its lifecycle depth varies compared with HR-driven JML suites and warns against using rules for sensitive resources, and account creation is supported only on a subset of integrations. [1] [2] | |
| Depth of offboarding | Deprovisioning deactivates or deletes the user in supported end systems, triggered by the IdP or HRIS, by reviews or manually, and time-bound grants expire automatically. Public pages do not describe session or token revocation, ownership transfer or a step that verifies offboarding is complete. [1] [2] | |
| Access requests and time-bound access | Self-service requests via web, Slack, Teams or Google Chat go to configurable reviewers with escalation, and just-in-time, time-bound access with automatic expiry is the core of the product. [1] [2] | |
| Access reviews | Access campaigns can revoke rejected access automatically on decision or at campaign end. Usage and last-used context for reviewers comes from Paladin Insights, which is in open beta and must be turned on by Opal support. [1] [2] [3] | |
| Audit evidence and compliance mapping | Campaign reports export as PDF and CSV, events can be streamed, and SOX, SOC 2, ISO and HITRUST are named. Public pages do not describe a control mapping per framework. [1] [2] | |
| Non-human identities | Service accounts, for example in GCP, are governed with time-bound access that expires, and AI agents are inventoried with an owning group and flagged when unowned. Agent Inventory and the agent risk types are in limited beta and must be turned on by Opal support. [1] [2] [3] | |
| Time to deploy and services needed | Opal documents self-serve cloud sign-up and publishes a deployment time in days with an incremental rollout, with no required services stated; self-hosted options also exist. [1] [2] | |
| Pricing transparency and connector cost | No public price on opal.dev (the pricing URL shows the demo form); a per-user price appears only on the Opal AWS Marketplace listing, and opal.dev publishes a launch price for Opal Zero. Public pages do not say whether connectors are included. [1] [2] |
Questions
Which IGA platform is best for offboarding?
On this weighting, Iden ranks first with 96.0 out of 100, ahead of Lumos and C1. All 3 document session sign-out and ownership transfer. Iden leads because it is the only one to score 5 on apps with no SCIM and no API, where a person otherwise removes the account by hand.
How fast does a leaver's access need to go?
Within the window your own policy sets. NIST PS-4 and AC-2 leave the period to the organization, and auditors test sampled leavers against your written window. A 24-hour policy you miss produces exceptions that a 3-day policy you keep would not.
Sources
- RFC 7643, SCIM: Core SchemaDefines the SCIM active attribute and states that its definitive meaning is set by the service provider. It does not say what any specific app does to sessions or tokens on deactivation.
- RFC 7644, SCIM: ProtocolSection 3.6 lets service providers keep a resource after a DELETE as long as they return 404 for it. Establishes what the protocol allows, not what any vendor does.
- NIST SP 800-53 Rev. 5, Security and Privacy Controls for Information Systems and OrganizationsPS-4 (disable access, revoke authenticators and credentials) and AC-2 part k (change shared authenticators). Removal periods are left to the organization. A control catalogue, not a measure of how often these gaps occur.
- Iden: How to automate offboardingIden's description of its offboarding sequence, apps with no removal path and the non-human identities a leaver created. Vendor-published and not independently tested here.