Topic starter
12/06/2026 12:34 am
TL;DR: App request handling and access approval should be treated as a governance problem, not just an ITSM tooling choice, according to Zluri. Zluri compares Zendesk, ServiceNow, and Jira on ticketing, knowledge management, automation, integration, and pricing, then argues that for IAM and NHI programmes, the key issue is whether request workflows can enforce identity, role, and compliance checks consistently.
Editorial analysis by NHI Mgmt Group, based on content published by Zluri: “Zendesk Vs ServiceNow Vs Jira: Which ITSM Platform To Choose?”.
By the numbers:
- Zendesk's suite plan starts at $49 per agent per month and suite pro starts at $99 per agent per month.
- Zluri says its own platform is free for up to three agents, with a premium subscription available from $20 per agent per month.
Key questions
Q: How should security teams govern app requests in ITSM workflows?
A: They should treat app requests as access decisions, not service tickets.
Q: Why do self-service app catalogues create governance risk if they are not tightly controlled?
A: Because the catalogue becomes an implicit policy boundary.
Q: What are the signs that ITSM access governance is failing?
A: Look for missing approval histories, inconsistent changelogs, weak searchability, manual reconstruction of request decisions, and reporting that cannot tie requests to actual provisioning outcomes.
Practitioner guidance
- Define request approval criteria before platform selection Document the identity, role, risk, and compliance checks that every app request must satisfy, then test whether the workflow can enforce them consistently across all request types.
- Separate routing automation from access authorisation Use automation to move tickets, not to imply approval.
- Curate the app catalogue as a policy object Limit what appears in self-service based on business need, risk tier, and entitlement scope so the portal reflects governance intent rather than every available SaaS app.
Bottom line: App request portals become governance controls when they enforce role, risk, and compliance checks rather than only handling tickets.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 4 days ago by NHI Mgmt Group
12/06/2026 9:53 am
App request workflows are now an identity governance surface, not a service desk detail. When access requests can trigger entitlement creation, the workflow is effectively deciding who may enter the software estate. That makes ticketing logic part of IAM and, where machine accounts or app integrations are involved, part of NHI governance as well. The practitioner conclusion is straightforward: if the workflow cannot express policy, it cannot be trusted to enforce it.
A few things that frame the scale:
- 28% of secrets incidents now originate outside code repositories, in Slack, Jira, and Confluence, and are 13% more likely to be categorised as critical than code-based leaks, according to the State of Secrets Sprawl 2026.
A question worth separating out:
Q: What should teams do when app requests also create non-human access?
A: Apply the same identity checks, approval discipline, and entitlement scoping that you would use for privileged access. If a request can create integrations, service accounts, or other non-human access, it should be governed as part of the broader identity lifecycle, not treated as a separate ITSM convenience.
👉 Read our full editorial: ITSM platform choice exposes access governance gaps in app requests
This post was modified 4 days ago by NHI Mgmt Group