People search InterSystems data breach timeline because regulated data and trust are existential—one incident triggers class actions and regulator exams. BreachHistory indexes 1 InterSystems-linked incident, with headline counts up to 3K+ in catalog rows. This page maps every attested event through 2026 with internal links to canonical records.
Why InterSystems breach history matters
InterSystems operates in Healthcare (United States). Across indexed rows, recurring themes include mixed intrusion and disclosure events. Understanding the chronological pattern helps security teams, customers, and regulators separate confirmed disclosures from forum marketing.
Full timeline through 2026
2019 — sensitive patient files transferred outside governed process
Cataloged incident. Australian public inquiries (later summarized in 2023 ABC and trade coverage) found that during the Northern Territory’s Acacia digital health program, identifiable patient files—including high-risk clinical material for more than 3,000 people—were transferred to InterSystems, overseas-based product/support teams, without the governance framework NT Health later deemed necessary. InterSystems publicly indicated that after August 2019 awareness it quarantined and destroyed copies across environments. The episode is Exposed categories include Identifiable patient clinical records described as highly sensitive in oversight reporting. BreachHistory cites approximately 3K+ affected records in this row. See the intersystems-nt-health2019 and canonical BreachHistory entry.
Patterns and analysis
- Mixed intrusion and disclosure events — appears across multiple InterSystems catalog entries; prioritize controls that address this class of failure.
- Record-count hygiene — BreachHistory indexes actor-cited figures separately from company-confirmed totals; read each row's technicalWriteup before treating counts as fact.
- 2026 monitoring — New disclosures roll into this timeline as they are verified or labeled unverified per catalog policy.
What to do if you may be affected
- Step 1: Enable phishing-resistant MFA on every account tied to this brand.
- Step 2: Use unique passwords and a password manager—breach rows often involve credential reuse.
- Step 3: Monitor official company breach notices and regulator filings, not dark-web downloads.
- Step 4: Watch for medical-ID theft and billing fraud after health-data incidents.
- Step 5: Bookmark the InterSystems company page for new 2026+ disclosures.
Canonical BreachHistory hub
Explore every indexed row: breachhistory.com/intersystems · Latest: intersystems-nt-health2019.
Sources: BreachHistory catalog (1 row for InterSystems), company and regulator disclosures cited in individual breach records.