Zendesk Marketplace is an app and integration directory for extending a Zendesk instance with third-party tools and add-ons. Administrators use it to install connectors, automations and data-sharing integrations, which can expand the system's permissions, data flows and administrative surface.
What the Zendesk Marketplace is for
Zendesk Marketplace is the discovery and installation layer for extending a Zendesk tenant with third-party apps, connectors and automation. Its value is operational, not cosmetic: it gives administrators a controlled place to add integrations that change how data moves, which permissions are granted, and which external services can act inside the support platform.
That extension model is useful because modern service desks rarely operate in isolation. A marketplace can improve routing, enrichment, reporting and workflow automation, but every installed app becomes part of the trust boundary around tickets, customer data and administrator actions.
How marketplace apps change the attack surface
The security significance of a marketplace is that each app can introduce new authentication paths, API access, data sharing rules and background automation. A benign integration may only read ticket metadata, while a broader connector can request write access, impersonation-style actions or access to adjacent systems through API tokens and delegated permissions.
This means risk does not come only from the core SaaS platform. It also comes from the behaviour of each installed integration, the quality of its publisher, the scope it requests and whether the organisation understands what data leaves the tenant. In practice, the marketplace becomes a supply-chain entry point for configuration drift, overbroad permissions and unexpected data exposure.
Exposure, trust and governance questions
Because the marketplace expands the administrative surface, organisations should treat app review as a trust decision, not a convenience purchase. The key questions are who published the app, what data it can reach, which APIs it consumes, where it stores information, and whether it needs persistent access after setup.
That scrutiny matters even when the integration looks routine. A ticketing add-on can touch customer records, internal notes, attachments, automations and identity-linked workflows. If the vendor is compromised or the app is overprivileged, the marketplace path can become a route for data theft, ticket tampering or lateral movement into connected systems.
Operational controls for safe use
Administrators should review installed apps as part of change control, not as one-time setup activity. Least privilege, environment segregation, approval workflows, vendor review and periodic revalidation are all important because marketplace apps often outlive the original business need that justified them.
It is also sensible to inventory every integration, document the data it handles and remove anything unused or unowned. Where an app needs broad access to support operations, the organisation should understand whether that access is truly required and whether a narrower integration pattern would achieve the same outcome.
Risk and Threat Considerations
Marketplace integrations can become a security problem when they are installed quickly but governed loosely. The main exposure is not the directory itself, but the cumulative effect of third-party apps that expand permissions, store tokens, and create persistent paths into ticket data and adjacent systems.
Failure mechanism: A malicious, compromised or overprivileged app can misuse granted access, exfiltrate ticket content, alter workflows, or keep working after the original business owner has forgotten it exists.
Impact: Organisations can face customer-data exposure, integrity loss in support records, unauthorized actions through connected tools, and a harder incident response problem because the attack path is hidden inside an approved integration.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
OWASP Non-Human Identity Top 10 addresses the attack and risk surface, while NIST SP 800-53 Rev 5 and CIS Controls v8 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | IA-5 — Authenticator Management | Marketplace apps often rely on API tokens and secrets that need lifecycle control. |
| AC-6 — Least Privilege | Marketplace apps expand permissions and should only receive the access they need. | |
| Recommendation — Manage integration tokens as authenticators and rotate or revoke them when app access changes. Constrain each app to the minimum permissions required for its function. | ||
| CIS Controls v8 | CIS-5 — Account Management | Installed integrations create additional accounts, access paths and ownership obligations. |
| Recommendation — Inventory and periodically review every marketplace integration and its access rights. | ||
| OWASP Non-Human Identity Top 10 | NHI-03 — Vulnerable Third-Party NHI | Third-party marketplace apps can introduce unsafe external identity and trust dependencies. |
| NHI-05 — Overprivileged NHI | Marketplace apps commonly request broad access that can exceed their operational need. | |
| Recommendation — Assess publisher trust and third-party integration risk before enabling marketplace apps. Reduce each integration to the narrowest permissions the use case allows. | ||
Practitioner Guidance
Governance implication: Treat marketplace usage as part of access governance for the service desk, not as a procurement afterthought. Ownership should include who approved the app, which business need it serves, and when it should be reviewed or removed.
What to watch for: Pay close attention to apps that request broad scopes, touch sensitive ticket fields, authenticate to multiple systems, or remain installed without an active owner. Those are the integrations most likely to create stale access and hidden dependency risk.
Related resources from NHI Mgmt Group
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on November 3, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org