Colgate University — April 2019 breach
Clustered 2 filings across 2 jurisdictions · filed May 30, 2019. View entity profile → Other incidents for this victim →
incident inc_da7671dcf819483f · merged by deterministic · confidence 100%
Litigation Timing
Discovered → first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — 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
- MAY 30MA AGMA AG noticefirst filing · 9 MA residentsauto-linkedday 0
- MAY 30NH AGNH AG noticemost recent · 1 NH residentsday 0
- Watching for additional filings — new sources merge into this incident automatically.
Roll-up facts — reconciled across members
- Breach window
- Apr 13, 2019 – Apr 26, 2019 NH AG
- Discovered
- May 3, 2019· 20d undetected NH AG
- Data types
- Financial account · Identity (basic) MA AG + NH AG
- Attack vector
- Third-Party / Supply Chain NH AG
- Response
- PrismRBS hired an outside expert IT forensics firm to respond to and investigate the incident · The University has also notified its credit card payment processor of the incident · PrismRBS has also informed us that it has enhanced the security of its systems, including implementing additional threat monitoring and detection tools, and enabling two-factor authentication on its internal email system NH 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.
Merge provenance
- Method
- deterministic
- Confidence
- 1.00 · above the 0.85 auto-merge floor
- Audit
- Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).
Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.
Filing velocity
Spread
0 days
vs. multi-state median
20.0× faster
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.