Handling Entitlement Revocations for Non-Integrated Applications

When Identity Panel identifies an entitlement that should be revoked but the associated application is not directly connected (or "integrated"), the platform can still support effective governance through integration with an IT Service Management (ITSM) system like Ivanti. This ensures manual processes remain traceable, auditable, and automated where possible.

Automated Ticket Generation via Ivanti Integration

If an entitlement is marked for revocation and belongs to a non-integrated application, Identity Panel can generate an ITSM ticket in Ivanti. This ticket is automatically assigned to the correct IT or support team responsible for the application, prompting them to manually remove the access. This workflow helps maintain compliance even when direct integration isn’t feasible or necessary.

To enable this capability, your Identity Panel environment must be integrated with Ivanti. This can be accomplished using:

• A PowerShell-based fixture

• A dedicated provider integration, built and configured within Identity Panel or HyperSync Panel

Common Data Flows for Non-Integrated Systems

Non-integrated applications typically rely on indirect data exchange methods:

• Inbound (entitlement source): Identity Panel collects entitlement data via periodic spreadsheet uploads, ensuring visibility into who has access.

• Outbound (remediation actions): Identity Panel creates service tickets in Ivanti when access should be removed, triggering manual revocation by IT staff.

This structure enables organizations to bring non-connected systems into the access governance framework without requiring custom APIs or deep integration.