All incidents View linkage analytics →Get the evidence package — $79

Confirmed2 filings · 2 statesUnverified claimConfirmedEnforcedmoderate sensitivity

Merged incident · 2 filings

Gettysburg College — January 2019 breach

Clustered 2 filings across 2 jurisdictions · filed Apr 4, 2019. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

2 filings

States

Affected · reported

First → last filing

Apr 4, 2019

Merge confidence

100%

incident inc_dd46d9bda27a427f · merged by deterministic · confidence 100%

Part of the PrismRBS supply-chain incident (2019) — at least 5 organizations filed notifications naming this third party.

Confirmed breach. One breach, 2 legal records. Intrusion Jan 19, 2019–Jan 26, 2019, discovered Jan 27, 2019 — the first regulatory filing landed 67 days later. 13 individuals reported across the linked filings. This page is the deduped roll-up; each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay

67days

Discovered → first regulatory filing

Filing span

0days

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

Jan 19, 2019breach begins

Jan 27, 2019discovered

notification delay · 67 days

Apr 4, 2019first filing

—watching for filings

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

APR 4NH AGNH AG noticefirst filing · 2 NH residentsday 0
APR 4MA AGMA AG noticemost recent · 11 MA residentsauto-linkedday 0
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Jan 19, 2019 – Jan 26, 2019
Discovered: Jan 27, 2019· 8d undetected
Data types: Identity (basic) · Financial account
Attack vector: Third-Party / Supply Chain
Response: Engaged a leading cybersecurity firm to assist in their investigation · Implemented several additional security measures to help prevent this type of incident from reoccurring · Sending notifications to affected individuals

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Evidence ladder — rungs this incident occupies

Leak-site claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing2 members

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

SEC 8-K / victim statement

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.