HubSpot App Marketplace is the directory where users find and install third-party apps that connect to HubSpot. It lists integrations that use account authorisation, OAuth, API keys, or private app tokens to sync data, automate workflows, or extend CRM functions, with access governed by the permissions granted during installation.
What the HubSpot App Marketplace actually is
The HubSpot App Marketplace is an integration directory, not a security boundary by itself. Its purpose is to help users discover third-party apps that extend CRM workflows, sync data and connect external services through permissions granted during installation.
That design makes the marketplace useful, but it also means the security posture of any installed app depends on the app, the consent flow and the permissions the user or admin approves. A marketplace listing can tell you what an integration claims to do, but it does not guarantee that the app is trustworthy, minimal in scope or appropriately governed.
Why permissions matter in marketplace apps
Marketplace apps commonly rely on OAuth, API keys or private app tokens, so the real control point is what access the integration receives and how long that access lasts. If an app is granted broad scopes or long-lived credentials, it may be able to read, write or synchronise more data than the business intended.
This is why installation review matters as much as vendor selection. The same app category can be low risk in one tenant and high risk in another, depending on whether the integration touches customer records, deal pipelines, tickets, exports or administrative functions. A careful review of scopes, data paths and publisher trust is the difference between a useful extension and an unnecessary standing trust relationship.
Common failure modes in app marketplaces
The most important failure modes are overpermissioned installs, stale integrations and unreviewed third-party code. Marketplace ecosystems are attractive to attackers because a successful compromise can piggyback on a legitimate app relationship instead of forcing a direct break-in.
That is why supply-chain style abuse is a real concern in app ecosystems. A malicious or compromised app can harvest tokens, exfiltrate data or create a hidden persistence path through a trusted platform connection. Even when the marketplace itself is legitimate, the risk often enters through the app lifecycle, publisher controls or the scope granted at install time. JetBrains Marketplace AI Plugin Campaign is a useful reminder of how marketplace trust can be abused when users install code without enough scrutiny.
How to evaluate and govern installed apps
HubSpot App Marketplace should be governed as part of third-party integration management. Organisations need a complete inventory of installed apps, clear ownership for each integration and a review path for requests that touch sensitive objects, export capabilities or admin-level data.
Good governance also means checking the permission model before installation, reviewing connected apps after major business changes and removing integrations that are no longer needed. In practice, that review should align with the HubSpot account model, not just the app catalog. HubSpot Security Guide covers the platform controls that shape that review, while SaaS-to-SaaS and OAuth App Governance Guide explains how to govern consent, scopes and revocation across connected apps.
What to do when an app is risky or no longer needed
When an app is high-risk, the right response is usually to narrow scope, replace long-lived access with tighter delegated access where possible, or remove the integration entirely. If the app is business-critical, the safer pattern is to reduce privileges, isolate data exposure and assign a named owner for ongoing review.
After removal or suspicion of misuse, review connected tokens, user grants and recent activity for signs of data access or automation abuse. If the app was using broad API access, the post-change work should include confirming that workflows still function with the least privilege needed and that stale authorisations have actually been revoked. Third-Party Integration Approval Checklist is a practical reference for deciding whether an app should be approved, constrained or rejected before it becomes a standing dependency.
Risk and Threat Considerations
Marketplace apps create a trust bridge between HubSpot and outside systems, so a compromised or overprivileged integration can become a fast path to data exposure, workflow abuse or token theft. The main danger is not the directory itself, but the fact that a legitimate install can carry broad access into a tenant that otherwise looks well controlled.
Failure mechanism: Attackers exploit excessive scopes, poor publisher vetting, stale installs or token reuse to gain durable access through an integration that appears legitimate.
Impact: The result can be CRM data exposure, manipulation of records or workflows, and persistent access that survives ordinary user-level password resets.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
OWASP API Security Top 10 and OWASP Non-Human Identity Top 10 address 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 rely on tokens and API credentials that require lifecycle control. |
| AC-20 — Use of External Information Systems | Third-party marketplace apps extend access outside the boundary of the core system. | |
| SA-9 — External System Services | Marketplace integrations are external services that need contractual and technical oversight. | |
| Recommendation — Manage app tokens with rotation, revocation and expiry to reduce standing access. Authorize external app connections only under defined terms and monitored use. Define security requirements for third-party integrations before approving them. | ||
| CIS Controls v8 | CIS-5 — Account Management | Installed apps add accounts, tokens and access paths that must be managed. |
| CIS-15 — Service Provider Management | Marketplace apps are third-party services that require supplier oversight. | |
| Recommendation — Inventory and remove unused integration access paths and credentials. Assess and monitor third-party app providers before and after approval. | ||
| OWASP API Security Top 10 | API2 — Broken Authentication | Many marketplace apps depend on OAuth, keys or tokens to authenticate to HubSpot APIs. |
| API5 — Broken Function Level Authorization | Overbroad app permissions can expose privileged HubSpot actions. | |
| Recommendation — Harden API authentication and revoke weak or stale app credentials. Verify that installed apps can invoke only the functions their role should allow. | ||
| OWASP Non-Human Identity Top 10 | NHI-02 — Secret Leakage | Marketplace integrations often use API keys and tokens that can be exposed or stolen. |
| NHI-05 — Overprivileged NHI | Third-party app tokens can be granted more access than the integration needs. | |
| Recommendation — Store and rotate integration secrets to reduce leakage and reuse risk. Constrain app scopes to the minimum access required for the use case. | ||
Practitioner Guidance
Governance implication: Treat every marketplace install as a third-party access decision, not a convenience purchase. The owner of the HubSpot tenant should know which apps are installed, why they exist, what data they can reach and when they will be reviewed again.
What to watch for: Any app that requests broad data access, uses long-lived tokens or is installed without a named business owner should trigger closer review before it is allowed to remain connected.
Related resources from NHI Mgmt Group
- What should IAM teams measure in a growing app marketplace?
- How should security teams respond when a cloned app appears in a marketplace?
- Who is accountable when a malicious app appears in a third-party marketplace?
- How should security teams plan an OAuth app launch when marketplace approval depends on review queues, paperwork, and install thresholds?
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 16, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org