MalwareEducationEducationRansomwareData EncryptedPIIIdentity (basic)LowContained

Lakeland Community College

bd_a30c64b910a2b485 · schema v1 · pii pii-v1

Severity

Low

Discovered

Jan 13, 2020

Filed

Apr 13, 2020

To disclose

13 weeks

Affected

5state residents only

Linked

5 filings

Confidence

66%

Full breach record for Lakeland Community College →2 incidents on file

Lakeland Community College detected a ransomware infection on January 13, 2020, which encrypted files on network drives. The college contained the threat, restored data, and engaged forensic investigators. On March 6, 2020, it was determined that personal information was impacted. No evidence of misuse was found. Kroll was engaged to provide one year of complimentary identity monitoring services.

J jump to incidentP pin to compareR raw source

Leak gap clock⏱ Leak >30d13 weeks discovery → filing

⚠ occurrence dateThe stored discovery date equals the breach OCCURRENCE date. Detection is normally later, so this OVERSTATES the delay — a 'late' verdict here may not be real.

Incident timeline

discovery → filing · 13 weeks / 91 days

Jan 13, 2020

Begins

Jan 13, 2020

Discovered

Apr 13, 2020

Filed

vs. sector median

+4 wks slower

This filing is one of 5 about the same incident.View merged incident

A leak claim by maze about this victim predates this filing by 76 days.View originating leak claim

Linked disclosures

Why this link?

Ransomware claims (1)

Leak Sitemazebd_f4bf78d9f9cc6bba2020-01-28 · +76dVerified by operator

Regulatory filings (3) · sorted by filing gap

New Hampshire State AGbd_e6bb4b050f2798f42020-04-16 · +3dVerified by operator
Massachusetts State AGbd_06cf510da11d6dcb2020-04-21 · +8dVerified by operator
Indiana State AGbd_703b0e8e397d43e52020-04-03 · +10dVerified by operator

Name: Lakeland Community College
norm: lakeland community college
Domain: lakelandcc.edu

Name: Lakeland Community College
norm: lakeland community college
Domain: lakelandcc.edu
Industry: Educationllm

Discovered: Jan 13, 2020
Breach occurred: Jan 13, 2020
Undetected for: 0 daysoccurrence → discovery
Materiality determined: —
Notification sent: —
Affected individuals: 5state-resident count only
Data types: PIIIdentity (basic)
Attack vector: Ransomware
MITRE ATT&CK: T1486 Data Encrypted for Impact
Threat actor: ExternalFinancial

During the incident: Contained the threat by disabling all unauthorized access to our network
Restored all encrypted data
Commenced a prompt and thorough investigation
Working very closely with external cybersecurity professionals
Secured the services of Kroll to provide identity monitoring services
Changes made: Continually evaluate and modify our practices and internal controls to enhance the security and privacy of your information
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 13 weeks(91 days from discovery to filing)
Compliance flags: Leak >30d
Discovery-date grounding: occurrence dateThe stored discovery date equals the breach OCCURRENCE date. Detection is normally later, so this OVERSTATES the delay — a 'late' verdict here may not be real.

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 4 filings · 4 states

View merged incident ↗

Indiana State AGApr 3 · first

Montana State AG+10d · this page

New Hampshire State AG+13d

Massachusetts State AG+18d

Pattern: first filing Apr 3 (IN), last Apr 21 (MA) — a 18-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?

Evidence ladder

Leak-site claim

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filingThis record

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

SEC 8-K / victim statement

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Source URL: https://dojmt.gov/wp-content/uploads/OCP/General-Notice-64.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Apr 13, 2020
Raw hash: 88099aba10b43cc6e923d77f2ac74dc743889c4fffa0b784dbfd79116f5727fe

Linked disclosures

Ransomware claims (1)

Regulatory filings (3) · sorted by filing gap

Reporting entityLakeland Community College

Victim entityLakeland Community College

Incidentdiscovered Jan 13, 2020

Stated responseContained the threat by disabling all unauthorized access to our network

ComplianceLeak >30d

Extraction provenanceno artifact recorded

Source provenancedojmt.gov