HackingTechnologyGovernmentInformationSQL InjectionTargetedData ExfiltratedPIIFinancial accountIdentity (basic)LowContained

Iowa’s County Conservation System

bd_6a30dfabda9ef79e · schema v1 · pii pii-v1

Severity

Low

Discovered

Apr 4, 2020

Filed

May 4, 2020

To disclose

4 weeks

Affected

1state residents only

Linked

3 filings

Confidence

66%

Iowa’s County Conservation System (ICCS) experienced a data breach involving the mycountyparks.com website. Malicious code was placed on the site between Jan 31 and Apr 8, 2020, intercepting payment card info and PII. ICCS discovered the incident on Apr 4, 2020, removed the code, and offered one year of credit monitoring via TransUnion.

J jump to incidentP pin to compareR raw source

Incident timeline

undetected · 64 days

discovery → filing · 4 weeks / 30 days

Jan 31, 2020

Begins

Apr 4, 2020

Discovered

May 4, 2020

Filed

vs. sector median

14 wks faster

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

New Hampshire State AGbd_b3eeb443587dd58d2020-05-04Verified
Indiana State AGbd_e3bc56eeb92bb4da2020-05-04Verified

Name: CRUX INFORMATICS, INC.
norm: crux informatics

Name: Iowa’s County Conservation System
norm: iowa’s county conservation system
Industry: TechnologyllmGovernmentllm

Discovered: Apr 4, 2020
Breach occurred: Jan 31, 2020 – Apr 8, 2020
Undetected for: 64 daysoccurrence → discovery
Materiality determined: —
Notification sent: —
Affected individuals: 1state-resident count only
Data types: PIIFinancial accountIdentity (basic)
Attack vector: Misconfiguration
MITRE ATT&CK: T1190 Exploit Public-Facing ApplicationT1056 Input CaptureT1074 Data Staged
Threat actor: ExternalFinancial
Initial access: exploit_public_facing

During the incident: Removal of the malicious code
Arranged for credit monitoring service provided by TransUnion Interactive
Changes made: Strengthening cybersecurity posture
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 4 weeks(30 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 ↗

New Hampshire State AGMay 4 · first

Indiana State AGMay 4 · first

Montana State AGMay 4 · first · this page

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-83.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: May 4, 2020
Raw hash: bab9bbe2b78772db91c03fe1cd6cabebeff08993b4211261d28311941a27c06a

Linked disclosures

Regulatory filings (2) · sorted by filing gap

Reporting entityCRUX INFORMATICS, INC.

Victim entityIowa’s County Conservation System

Incidentdiscovered Apr 4, 2020

Stated responseRemoval of the malicious code

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancedojmt.gov