People search Tanium data breach timeline because the brand sits on billions of accounts, credentials, and cloud workloads. BreachHistory indexes 2 Tanium-linked incidents (1 company-confirmed). This page maps every attested event through 2026 with internal links to canonical records.
Why Tanium breach history matters
Tanium operates in Technology (United States). Across indexed rows, recurring themes include third-party and supply-chain exposure, unverified actor or scraping claims. Understanding the chronological pattern helps security teams, customers, and regulators separate confirmed disclosures from forum marketing.
Full timeline through 2026
2026 — Klue OAuth supply-chain breach; Salesforce CRM data exfiltrated
Verified breach. Downstream Klue supply-chain victim — June 2026. Tanium CISO Paul Black disclosed June 18 that Klue's OAuth-integrated Battlecards platform breach allowed unauthorized exfiltration of Tanium's Salesforce CRM data while Tanium products and cloud infrastructure were unaffected. Potentially compromised categories include opportunity names/values, sales-related messaging, and business contact fields (names, job titles, emails; in some cases phones, social media contacts, addresses). Tanium blocked Klue OAuth access, en Exposed categories include Sales account/opportunity data, sales messaging, business contacts (names, titles, emails; some phones, social handles, business addresses)—no Tanium products, cloud infrastructure. No attested victim count is published for this row yet. See the tanium-klue-salesforce 2026 record and canonical BreachHistory entry.
2025 — Salesloft/Drift OAuth supply chain; Salesforce CRM data accessed (2025-08-28)
Cataloged incident. In August–September 2025, multiple vendors publicly confirmed that threat activity—widely reported in connection with compromised OAuth tokens for the Salesloft Drift integration with Salesforce—enabled unauthorized queries/export-style access to limited Salesforce-held business contact and customer-support case material. Vendor statements routinely emphasized that core product clouds and unrelated infrastructure were not impacted; exact fields and scope differ by company. Exposed categories include Typically names, business emails, phones, employer metadata, and support-case subjects or correspondence snippets held in Salesforce—per each organization’s customer notice.. No attested victim count is published for this row yet. See the tanium2025salesloft-drift and canonical BreachHistory entry.
Patterns and analysis
- Third-party and supply-chain exposure — appears across multiple Tanium catalog entries; prioritize controls that address this class of failure.
- Unverified actor or scraping claims — appears across multiple Tanium catalog entries; prioritize controls that address this class of failure.
- Record-count hygiene — BreachHistory indexes actor-cited figures separately from company-confirmed totals; read each row's technicalWriteup before treating counts as fact.
- 2026 monitoring — New disclosures roll into this timeline as they are verified or labeled unverified per catalog policy.
What to do if you may be affected
- Step 1: Enable phishing-resistant MFA on every account tied to this brand.
- Step 2: Use unique passwords and a password manager—breach rows often involve credential reuse.
- Step 3: Monitor official company breach notices and regulator filings, not dark-web downloads.
- Step 4: Review OAuth app permissions and revoke unused third-party integrations.
- Step 5: Bookmark the Tanium company page for new 2026+ disclosures.
Canonical BreachHistory hub
Explore every indexed row: breachhistory.com/tanium · Latest: tanium-klue-salesforce2026.
Sources: BreachHistory catalog (2 rows for Tanium), company and regulator disclosures cited in individual breach records.