People search OneTrust data breach timeline because the brand sits on billions of accounts, credentials, and cloud workloads. BreachHistory indexes 1 OneTrust-linked incident (1 company-confirmed). This page maps every attested event through 2026 with internal links to canonical records.
Why OneTrust breach history matters
OneTrust operates in AI (United States). Across indexed rows, recurring themes include credential theft and social engineering, 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
2026 — Klue OAuth supply-chain breach; Salesforce business contact data exfiltrated
Verified breach. OneTrust confirmed on June 17, 2026 that it identified unauthorized activity in its Salesforce environment associated with the broader Klue supply-chain incident. The attack originated June 11–12, 2026 when threat actor Icarus used compromised legacy credentials to gain access to Klue's production environment and stole OAuth tokens connecting Klue to customer Salesforce instances. OneTrust's Salesforce CRM data—limited to business contact information and sales account data—was accessed and exfiltrated. OneTrust's i Exposed categories include Sales account data and business contact information from OneTrust's Salesforce CRM: names, email addresses, job titles, phone numbers, and business addresses of customer and prospe. No attested victim count is published for this row yet. See the onetrust-klue-salesforce 2026 record and canonical BreachHistory entry.
Patterns and analysis
- Credential theft and social engineering — appears across multiple OneTrust catalog entries; prioritize controls that address this class of failure.
- Third-party and supply-chain exposure — appears across multiple OneTrust 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: Bookmark the OneTrust company page for new 2026+ disclosures.
Canonical BreachHistory hub
Explore every indexed row: breachhistory.com/onetrust · Latest: onetrust-klue-salesforce2026.
Sources: BreachHistory catalog (1 row for OneTrust), company and regulator disclosures cited in individual breach records.