DisclosureLens
HackingCustomer Data InvolvedIdentity (basic)Government IDMediumContained

Cygilant

bd_fdb32a853223f1ee · schema v1 · pii pii-v1

Severity

Medium

Discovered

Aug 25, 2020

Filed

Mar 17, 2021

To disclose

29 weeks

Affected · nationwide

4112 in this filing

Linked

2 filings

Confidence

50%
Full breach record for Cygilant →2 incidents on file

Cygilant, Inc. reported an external system breach (hacking) that occurred and was discovered on August 25, 2020. The breach affected 2 Maine residents, compromising their names and Social Security numbers. The company notified the affected individuals on March 17, 2021, and offered 24 months of credit monitoring and identity restoration services through Experian.

Maine clockDiscovered Aug 25, 2020 → Filed with AG Mar 17, 2021204d ✗ ME AG >90d29 weeks discovery → filing
⚠ occurrence dateThe stored discovery date equals the breach OCCURRENCE date. Detection is normally later, so this OVERSTATES the delay — a 'late' verdict here may not be real.

Incident timeline

discovery → filing · 29 weeks / 204 days

Aug 25, 2020

Begins

Aug 25, 2020

Discovered

Mar 17, 2021

Filed

This filing is one of 2 about the same incident.View merged incident

Linked disclosures

Why this link?

Regulatory filings (1) · sorted by filing gap

Filing propagation · 2 filings · 2 states

View merged incident ↗
Maine State AGMar 17 · first · this page
New Hampshire State AG+5d

Pattern: first filing Mar 17 (ME), last Mar 22 (NH) — a 5-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?

Evidence ladder

Leak-site claim

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filingThis record

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

Unlocks: materiality, stated response, full audit trail. Ceiling removed.