integration architecture

When your vendor holds your OAuth tokens, their incident is your incident.

Competitive-intelligence platforms need access to your CRM and your call recordings to be useful. Almost all of them take that access by holding your OAuth tokens inside their own multi-tenant infrastructure. That is an architectural choice, and it has a consequence — one the public record has now made concrete.

the shape of the risk

A CI platform is, structurally, a token vault.

To surface a competitor mention from a call or push a battlecard into an opportunity, the platform needs live credentials to your systems. In a multi-tenant SaaS model those credentials are pooled: hundreds of customers' Salesforce and call-recording tokens, held by one company, reachable through one integration tier. That concentration is efficient to operate and it is also, unavoidably, a single high-value target.

This is not a criticism of any one vendor's engineering. It is a property of the deployment model. Any platform built that way carries it, and the mitigation available within that model is to defend the vault well — not to stop being one.

the public record

What was reported, and when.

Below is a dated summary drawn from Klue's own published disclosure and from contemporaneous security reporting. It is presented without commentary, and quotes Klue directly where their wording is the clearest statement of fact. Sources are linked in full at the end of this page.

June 11, 2026
Salesforce disabled the Klue Battlecards app integration on its AppExchange.
Reported by The Hacker News
June 12, 2026
Klue identified unauthorized activity affecting part of its integration infrastructure.
“On June 12, we identified unauthorized activity affecting a portion of Klue's integration infrastructure.”
Klue, “An Update on the Recent Klue Security Incident”
June 2026
Klue stated the entry point was a compromised legacy credential, and that the attacker obtained OAuth tokens connecting Klue to third-party platforms, including Salesforce.
“The attacker used that access to obtain OAuth tokens used to connect Klue with certain third-party platforms, including Salesforce, and subsequently accessed data within a number of connected customer environments.”
Klue disclosure
June 2026
Klue reported containment steps: revoking affected credentials and tokens, removing unauthorized code, disabling potentially impacted integrations, opening an investigation, and notifying law enforcement. CrowdStrike was engaged for investigation support.
Klue disclosure
June 2026
Klue stated there was no evidence that customer content stored within the Klue platform itself was impacted.
“there is no evidence that customer content stored within the Klue platform was impacted.”
Klue disclosure
July 27, 2026
Klue published “Integrations Restored: Salesforce and Gong Reconnected.”
Klue newsroom
July 31, 2026
Klue published “What a Security Incident Taught Us About Securing a Modern SaaS Platform.”
Klue newsroom

We have deliberately not named the other organisations identified in public reporting as affected. They are not party to this comparison, and listing them here would serve no purpose for a reader evaluating platform architecture.

the alternative

Self-hosted PrismCI never takes custody in the first place.

The strongest guarantee a vendor can give you about your credentials is not holding them. That is the whole argument, and it is architectural rather than procedural — it does not depend on us executing a control correctly.

Your integration credentials stay in your instance

Salesforce, Gong, Slack and every other connector is configured inside your own PrismCI deployment. The credentials are written to your database, on your infrastructure. There is no PrismCI-operated service that holds a copy, because there is no PrismCI-operated service in the path at all.

No shared blast radius

Single-tenant means the failure domain is one customer wide — yours. A compromise of another company's PrismCI deployment has no route to yours. There is no common integration tier for the two to share.

Column-level encryption, with the key you hold

Sensitive fields are encrypted with AES-256 (SIV and GCM) before they touch disk. The Key-Encryption-Key lives in a volume you control and is read only at startup. We do not have it, and cannot ask for it.

You revoke on your own timeline

If you ever need to cut an integration, you rotate the credential in your own admin console and it is done. You are not waiting on a vendor's remediation schedule, or on a third-party marketplace to re-enable an app.

The practical test. Ask any CI vendor a single question: if your infrastructure is compromised tomorrow, what of mine is in it? For a multi-tenant platform the honest answer includes your live integration tokens. For self-hosted PrismCI the honest answer is nothing — because the connection to your Salesforce runs from your own instance, under your own credentials, inside your own perimeter.

what we don't claim

The limits of the argument, stated by us.

A trust page that only flatters the vendor who wrote it is not worth reading. Three things we think you should weigh against everything above.

PrismCI also offers a managed hosted option. If you choose it, we run the infrastructure and the properties on this page describe your deployment differently — self-hosted is where the architecture above holds end to end. We would rather say that plainly than let a diagram imply otherwise.
No architecture removes security risk. Self-hosting moves responsibility for patching, key custody and backups to you; we ship the tooling for all three and document it, but the accountability genuinely changes hands.
Every platform in this category, ours included, will face security incidents. The question a buyer should ask is not whether a vendor has had one, but how much of your data a vendor is positioned to lose on your behalf when they do.

sources

This page describes publicly reported events and links to primary sources so you can read them yourself. Klue's own disclosure is listed first, deliberately. If any statement here becomes inaccurate or is superseded by a later disclosure, we will correct it — write to us.

own your intelligence

Run competitive intelligence inside your own perimeter.

Single-tenant, self-hosted, column-encrypted, with your integration credentials never leaving your infrastructure.