Book a Revenue Review

Who or What Has Access to Your Salesforce? The Hidden Risk in Integrations

Red and black illustration of a secure cloud connected to API integrations, servers, automation and AI agents

Salesforce rarely operates alone. It connects to marketing platforms, finance systems, quoting tools, integration platforms, customer support applications, data warehouses and increasingly AI-powered workflows. Each connection helps the business move faster. Each also creates another access path that somebody needs to understand, own and govern.

The difficult question is not simply whether a connected application is approved. It is whether your organisation still knows what that application can access, whose identity it uses, what privileges it has, and what would happen if its credentials or tokens were compromised.

The problem: Salesforce access extends well beyond employees

Most companies devote considerable attention to interactive users: SSO, MFA, joiners and leavers, profiles and permission sets. Yet machine-to-machine connections can be less visible. A middleware platform may authenticate through a dedicated integration user. A sales enablement tool may retain OAuth access. A service account may have been granted broad permissions years ago to resolve a deployment issue. An AI workflow may be introduced without a complete understanding of the CRM data it can retrieve or change.

None of these connections is inherently a security failure. The risk develops when access outlives its purpose, ownership becomes unclear, controls are inconsistent or permissions exceed the business requirement.

Five questions Salesforce leaders should be asking

1. Which applications and automated identities can access Salesforce?

Start with an inventory of connected apps, external client apps, API clients and integrations using dedicated or shared identities. Include applications that are rarely used but remain authorised. Consider indirect connections routed through integration platforms as well as direct API access.

2. Whose identity is each integration using?

An integration is not only an application registration. Its effective access also depends on the Salesforce user context and associated permission sets. Shared administrator identities, poorly documented service users and integrations tied to individual employees complicate accountability and offboarding.

3. What data and actions are possible?

OAuth scopes are important, but they are not the whole story. Review the effective object permissions, field-level permissions and other privileges of the identities involved. A connection with broad API capability paired with a highly privileged Salesforce user can create an unnecessarily large blast radius.

4. Who owns the connection and how is it controlled?

Every material integration should have a business owner and technical owner, a documented purpose, an appropriate authentication flow, token-handling controls, a defined change process and a safe method for revocation. Where applicable, examine token lifetime, IP restrictions, trusted network conditions and monitoring. Do not tighten settings blindly: revoking a token or changing a service account can interrupt critical business operations.

5. What changes when AI agents enter the picture?

AI agents and automated workflows introduce new patterns of delegated access and action. Their permissions, execution identities and data flows should be understood just like any other integration. The essential questions remain familiar: what can connect, what can it see, what can it change, and who is accountable?

Why this matters now

Salesforce continues to evolve its guidance on connected applications, external client apps and OAuth security. The direction is clear: modern authentication flows, carefully selected scopes and better governance of third-party access. A practical review should include both established connections and any integrations that will need changes as authentication requirements evolve.

For example, Salesforce has documented the move towards External Client Apps for new integrations, stronger PKCE expectations for relevant OAuth flows, and scheduled retirement of certain legacy OAuth flows. These changes make an accurate integration inventory useful for security and operational continuity.

The solution: make access visible, assign ownership and reduce unnecessary privilege

A sensible approach begins with discovery, not mass revocation. First establish which applications, integration users and service accounts can connect to Salesforce. Then map the associated identities, OAuth scopes, effective permissions, business purposes and owners. Compare that access with what each integration genuinely needs. Finally, prioritise improvements based on exposure, business criticality and the risk of disrupting essential processes.

Some findings may be straightforward: an obsolete connection can be investigated for retirement, an integration owner assigned or a permission set reviewed. Other findings require deeper technical assessment, coordinated changes or additional monitoring. The objective is to improve control without breaking the automations that support the business.

Start with a Salesforce Integration Exposure Assessment

Ravienta offers a focused, scoped assessment to help organisations understand their Salesforce connected-access landscape. Depending on agreed access and available evidence, the review considers connected applications, API integrations, non-human identities, OAuth policies, permissions, ownership and monitoring. The output is a clear summary of observations and a prioritised set of recommended next steps.

This is an advisory assessment and does not replace penetration testing, a formal security audit or independent assurance. Scope, access and commercial terms are agreed before work begins.

Request Your Salesforce Assessment

Further reading

Salesforce: Manage OAuth Access Policies ยท Salesforce: Connected Apps and External Client Apps security review guidance

One response to “Who or What Has Access to Your Salesforce? The Hidden Risk in Integrations”

  1. […] For the wider context on integration identities, OAuth scope and AI-enabled workflows, read our related article: Who or What Has Access to Your Salesforce? The Hidden Risk in Integrations. […]

Leave a Reply

Your email address will not be published. Required fields are marked *