Skip to content
cisonews.net

Corrections

Corrections are made on the entry itself, noted there with a date, and listed here. Report an error through the contact page.

  • 2026-11-05 /incidents/caltrain-2026-11: Changed the detection date from November 21, 2025 to November 2024. The later date is when Turbo Data Systems says it learned the recipient's information was involved; the letter says the network disruption happened in November 2024.
  • 2026-11-04 /guides/ransomware-in-8-k-filings-how-companies-describe-encryption-data-theft: The guide called Jewett-Cameron's October 2025 filing the earliest of the four ransomware filings. It is the latest; the sentence now gives only its date.
  • 2026-10-28 /incidents/frontline-education-2026-10: Removed an unsupported specific date for when Frontline Education's notification letters went out. The filed document is a sample notice with a placeholder date field, not a stated date. (Made on the Kern County Superintendent of Schools entry, which was folded into the Frontline Education entry on November 8, 2026.)
  • 2026-11-04 /incidents/lexitas-2026-10: The entry said the notice gave no count of affected people. The notice states that approximately 14,361 individuals nationwide were affected; the count is now in the entry.
  • 2026-11-04 /incidents/troutman-pepper-locke-2026-10: The description listed "variable data" as information involved. That phrase is a merge field in the filed sample letter, not a type of data; the description now says the documents held personal data.