Notifications
Clear all
Topic starter
12/06/2026 9:00 pm
TL;DR: PagerDuty’s App Store groups 400-plus integrations that help teams detect, triage, and resolve incidents faster, but the article also shows how tightly incident response now depends on SaaS visibility, lifecycle control, and access governance according to Zluri. The governance problem is not integration count, but whether identity, renewals, and deprovisioning keep pace with the sprawl those integrations create.
NHIMG editorial — based on content published by Zluri: IT Teams Top 10 Apps in PagerDuty App Store
By the numbers:
- The PagerDuty App Store offers over 400 apps and integrations that IT teams can use to extend incident management capabilities.
- Zluri says organisations purchased 1,000 Google Workspace licenses but needed usage clarity before the next renewal.
- Zluri notes that contract alerts arrive 30 days, 15 days, and one day before renewal dates.
Questions worth separating out
Q: How should security teams govern SaaS integrations used for incident response?
A: Security teams should treat incident-response integrations as governed access paths, not simple connectors.
Q: Why do SaaS apps create identity risk even when they improve operations?
A: SaaS apps create identity risk because every new connection adds users, tokens, permissions, and renewal obligations.
Q: What breaks when app discovery is disconnected from access governance?
A: When discovery is disconnected from access governance, teams may know an app exists without knowing who owns it, who uses it, or whether its access is still justified.
Practitioner guidance
- Map incident-platform integrations to identity owners Inventory every PagerDuty-connected app, assign a business and technical owner, and review the permissions each integration can exercise during alerting, ticketing, and remediation workflows.
- Link SaaS discovery to access reviews Use discovery and usage analytics to identify inactive applications, then feed those findings into access review and deprovisioning workflows before the next renewal cycle.
- Tighten renewal governance around dormant apps Require renewal approvals to include application activity, security ownership, and entitlement status so auto-renewals do not preserve unused or risky software.
What's in the full article
Zluri's full article covers the operational detail this post intentionally leaves for the source:
- The full ranking and descriptions of all 10 PagerDuty apps, including the collaboration and ITSM tools Zluri highlights.
- Product-specific examples of how each app supports incident management workflows in practice.
- Detailed feature lists for SaaS discovery, license management, and renewal alerts that this analysis only summarises.
- The source article's broader walkthrough of Zluri's platform capabilities and integration context.
👉 Read Zluri's analysis of the top 10 PagerDuty app integrations →
PagerDuty app integrations and the SaaS identity governance gap?
Explore further
12/06/2026 10:47 pm
Integration depth has become an identity-governance problem, not just an operations problem. The article frames PagerDuty’s App Store as a way to accelerate incident response, but every additional integration also expands the access graph that IAM and IGA teams must understand. The more systems an incident platform can touch, the more important entitlement review, connector ownership, and change control become. Practitioners should treat integration sprawl as a governance input, not a technical convenience.
A few things that frame the scale:
- 79% of organisations have experienced secrets leaks, with 77% of these incidents resulting in tangible damage, according to Ultimate Guide to NHIs.
- 96% of organisations store secrets outside of secrets managers in vulnerable locations including code, config files, and CI/CD tools.
A question worth separating out:
Q: Who should approve SaaS renewal decisions in identity programmes?
A: Renewal decisions should involve the application owner, the identity or IAM team, and the security function when the app carries sensitive access. That makes renewals a control point rather than a procurement formality. If an application still has active identities but no clear ownership, renewal should trigger a governance review before approval.
👉 Read our full editorial: PagerDuty app integrations expose the SaaS identity gap
