Woodland Unified School District — November 2019 breach
One linked filing — more sources may join as they report · filed Nov 4, 2020. View entity profile → Other incidents for this victim →
incident inc_f5ddf49791e04cc3 · merged by deterministic
Litigation Timing
Discovered → first regulatory filing
Not recorded for this incident
Discovery variance · Leak precedence · Materiality delta · SEC filing delay · Filing span — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Incident timeline
Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.
Member cascade — every filing about this breach
- NOV 4CA AGCA AG noticeonly filing · no count statedday 0
- Watching for additional filings — new sources merge into this incident automatically.
Roll-up facts — reconciled across members
- Breach window
- Nov 4, 2019 CA AG
- Discovered
- Apr 27, 2020· 175d undetected CA AG
- Data types
- Identity (basic) · Credentials CA AG
- Attack vector
- Third-Party / Supply Chain CA AG
- Response
- Launched an investigation into the nature and scope of the event · Undertook a comprehensive review of our Aeries SIS to confirm the type of information it contained and to whom it related · Working with Aeries to confirm actions they are taking and measures they are putting in place to prevent the reoccurrence CA AG
Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.
Evidence ladder — rungs this incident occupies
No leak-site claim on record for this incident.
No press coverage linked yet.
Unlocks: discovery date, data types, affected count, compliance clock.
No SEC filing or victim statement yet.
About this clustering
DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.