People search RSA Security data breach timeline because the brand sits on billions of accounts, credentials, and cloud workloads. BreachHistory indexes 2 RSA Security-linked incidents, with headline counts up to 40M+ in catalog rows. This page maps every attested event through 2026 with internal links to canonical records.
Why RSA Security breach history matters
RSA Security operates in Technology. Across indexed rows, recurring themes include credential theft and social engineering, zero-day exploitation and malware. Understanding the chronological pattern helps security teams, customers, and regulators separate confirmed disclosures from forum marketing.
Full timeline through 2026
2011 — 40,000,000 tokens
Cataloged incident. Mar 2011. Sophisticated APT breached RSA via spearphishing (malicious Excel/Flash). Stole SecurID seed values; attackers could forge tokens. 40M token users affected. Stolen data used in May attack on Lockheed Martin. EMC (RSA parent) spent $66M in Q2. RSA replaced virtually all tokens. Exposed categories include SecurID seed values; token security undermined. BreachHistory cites approximately 40M+ affected records in this row. See the rsa-security2011 and canonical BreachHistory entry.
2011 — spearphishing zero-day attack
Cataloged incident. RSA suffered a sophisticated spearphishing attack using a malicious Excel file with a zero-day Flash vulnerability. Attackers gained access to information related to RSA's SecurID two-factor authentication tokens. The breach led to subsequent attacks on Lockheed Martin and other defense contractors. Exposed categories include SecurID token seed data; information enabling token prediction. No attested victim count is published for this row yet. See the rsa2011 and canonical BreachHistory entry.
Patterns and analysis
- Credential theft and social engineering — appears across multiple RSA Security catalog entries; prioritize controls that address this class of failure.
- Zero-day exploitation and malware — appears across multiple RSA Security 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 RSA Security company page for new 2026+ disclosures.
Canonical BreachHistory hub
Explore every indexed row: breachhistory.com/rsa · Latest: rsa-security2011.
Sources: BreachHistory catalog (2 rows for RSA Security), company and regulator disclosures cited in individual breach records.