People search Tenable data breach timeline because the brand sits on billions of accounts, credentials, and cloud workloads. BreachHistory indexes 1 Tenable-linked incident. This page maps every attested event through 2026 with internal links to canonical records.
Why Tenable breach history matters
Tenable operates in Technology (United States). Across indexed rows, recurring themes include third-party and supply-chain exposure. Understanding the chronological pattern helps security teams, customers, and regulators separate confirmed disclosures from forum marketing.
Full timeline through 2026
2025 — Salesloft/Drift OAuth supply chain; Salesforce CRM data accessed (2025-08-22)
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 tenable2025salesloft-drift and canonical BreachHistory entry.
Patterns and analysis
- Third-party and supply-chain exposure — appears across multiple Tenable 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 Tenable company page for new 2026+ disclosures.
Canonical BreachHistory hub
Explore every indexed row: breachhistory.com/tenable · Latest: tenable2025salesloft-drift.
Sources: BreachHistory catalog (1 row for Tenable), company and regulator disclosures cited in individual breach records.