EQUIFAX INC.
bd_958fcf9ef068490f · schema v1 · pii pii-v1
Full breach record for EQUIFAX INC. →12 incidents on fileEquifax, Inc. filed a supplemental notice with the Washington Attorney General regarding a cybersecurity incident. The breach, caused by the exploitation of a web application vulnerability, occurred from May 16 to July 31, 2017, and was discovered on July 29, 2017. The incident impacted approximately 145.5 million U.S. consumers, including 3,243,664 Washington residents. Data exposed included names, SSNs, birth dates, addresses, driver's license numbers, and credit card numbers. Equifax engaged Mandiant for forensic investigation and offered free credit monitoring.
J jump to incidentP pin to compareR raw source
Incident timeline
May 16, 2017
Begins
Jul 29, 2017
Discovered
Sep 7, 2017
Filed
vs. sector median
3 wks faster
Linked disclosures
Why this link?Regulatory filings (6) · sorted by filing gap
- California State AGbd_278155640602f8682017-09-07Verified
- New Hampshire State AGbd_c7a263041aff38052017-09-07Candidate
- Oregon State AGbd_d60b910cf11a2f9c2017-09-07Verified
- Massachusetts State AGbd_e7e140ebd326c5762017-09-07Verified
Show 2 more filings ↓Show fewer ↑up to 35d gap
- South Carolina State AGbd_20e4e8963ad56aa02017-09-12 · +5dVerified
- New Hampshire State AGbd_bf00e329b87159ef2017-10-12 · +35dVerified
Filing propagation · 7 filings · 6 states
View merged incident ↗Pattern: first filing Sep 7 (CA), last Oct 12 (NH) — a 35-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.