HackingGovernmentGovernmentStolen CredentialsCustomer Data InvolvedPIIIdentity (basic)LowContained

Steele County, North Dakota

bd_7f8dc7a6d3e94547 · schema v1 · pii pii-v1

Severity

Low

Discovered

Feb 21, 2020

Filed

Feb 21, 2020

To disclose

≤1 day

Affected

6state residents only

Linked

3 filings

Confidence

66%

Full breach record for Steele County, North Dakota →

Steele County notified individuals that an unauthorized party accessed an employee email account between Sept 17 and Oct 10, 2019. The county discovered the incident on Feb 21, 2020, after forensic review revealed personal information was stored in the account. No evidence of misuse was found. Kroll was engaged to provide one year of free identity monitoring.

J jump to incidentP pin to compareR raw source

Incident timeline

undetected · 157 days

discovery → filing · ≤1 day / 0 days

Sep 17, 2019

Begins

Feb 21, 2020

Discovered

Feb 21, 2020

Filed

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

Linked disclosures

Why this link?

Regulatory filings (2) · sorted by filing gap

Indiana State AGbd_e0dd41ac5d09f3082020-03-19 · +27dVerified
Massachusetts State AGbd_15d53e875c28ea3d2020-03-20 · +28dVerified

Name: Steele County, North Dakota
norm: steele county north dakota

Name: Steele County, North Dakota
norm: steele county north dakota
Industry: Governmentllm

Discovered: Feb 21, 2020
Breach occurred: Sep 17, 2019 – Oct 10, 2019
Undetected for: 157 daysoccurrence → discovery
Materiality determined: —
Notification sent: —
Affected individuals: 6state-resident count only
Data types: PIIIdentity (basic)
Attack vector: Unauthorized Access
MITRE ATT&CK: T1078 Valid Accounts
Threat actor: External
Initial access: valid_credentials

During the incident: Secured the account
Commenced a prompt and thorough investigation
Working very closely with external cybersecurity professionals
Engaged Kroll to provide identity monitoring
Changes made: Continually evaluate and modify 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: ≤1 day(0 days from discovery to filing)
Compliance flags: — (clock not assessable for this source)

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 3 filings · 3 states

View merged incident ↗

Montana State AGFeb 21 · first · this page

Indiana State AG+27d

Massachusetts State AG+28d

Pattern: first filing Feb 21 (MT), last Mar 20 (MA) — a 28-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/Breach-NotificationDetails-142.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Feb 21, 2020
Raw hash: ff55f122b966192ec7f2f0c6e8d8a7b74de2184c0b08f78c5df1e4b08c46ace1

Linked disclosures

Regulatory filings (2) · sorted by filing gap

Reporting entitySteele County, North Dakota

Victim entitySteele County, North Dakota

Incidentdiscovered Feb 21, 2020

Stated responseSecured the account

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancedojmt.gov