← Breach analysis by the Dual Vulnerabilities framework

Coffee County IT intrusion (Unattributed, 2024)

2024 · United States · O - Public administration and defence · Intrusion into county IT infrastructure (suspected ransomware), precautionary severing from state election systems

Analysed 2026-11-06 by Hermes

Open this case in the tool →

What happened

Intrusion into county IT infrastructure (suspected ransomware), precautionary severing from state election systems

Dual vulnerability type

Expertise to Execution

Evidence coverage: 2/6 stages, weight 13/60

Decisive stage: detection (clearest evidence) · Alternative: Strategy to Leadership

Why this classification

(1) Coffee County runs the local leg of Georgia's election infrastructure and, per its own disclosure, operates cyber systems/activity logs, network logs and monitoring systems together with a contracted IT provider; the expectation that these detect unauthorized access to county IT is a technical/operational one. (2) In practice the county did not notice the intrusion: DHS/CISA alerted it on 15 April 2024, an incident was declared only after that, examination found unauthorized-access artifacts and activity by an unknown malicious actor, and no exfiltration was found. Georgia severed the county's access to GARViS, ePulse and the election night reporting system on 16 April; the county first acknowledged the incident publicly on 26 April, after press reporting, while records requests were deflected with a maintenance explanation. Investigators believed ransomware was involved; the entry vector, dwell time and full scope were never disclosed and the entry vector is not load-bearing. (3) The classification rests on the detection stage: the expectation to detect the intrusion through existing monitoring sat with technical/operational practice (material origin), and the monitoring did not surface the activity or alert the county (execution break) - expertise about detection existed but was not realised in operations, an Expertise to Execution gap. A secondary, weaker-documented pattern is visible in the response and disclosure timeline (the state acted before the county acknowledged; the first public account was late and the outage to records requesters was explained inaccurately), a Strategy to Leadership reading, but its doctrinal origin is only inferred and it is carried as a contributing stage. (4) RM34 (Expertise to Execution lens): the county's available monitoring and log tooling was present but evidently not configured or maintained to surface the unauthorized access - detection and the first notification came from DHS/CISA on 15 April, and the county learned of the intrusion only through that external alert, leaving dwell time unknown (causal role: Obscuring). RM04 (Expertise to Execution lens): the county's election operations ran over a single county-network connection, backed by one contracted IT provider, to all state election systems, so one compromise of that network forced severing from GARViS, ePulse and the election night reporting system, with access recovered only through isolated backup laptops and cellular connections - a dependency a small rural county's specialists could not engineer away (causal role: Amplifying).

Evidence by stage

Risk markers

Sources

Notes

Case-file description matches the stated victim (Coffee County, Georgia); no data-quality mismatch. Entry vector, dwell time and actor identity were never disclosed; the ransomware assessment rests on unnamed investigators quoted by CNN (read via the WRAL syndication because cnn.com refused direct extraction) and was never confirmed, and the Georgia Secretary of State notice is unpublished, known only through CyberScoop's obtained copy, with the state's 16 April action quoted via a press spokesman. The widely reported January 2021 breach of the same county's election office (pro-Trump operatives copying state election software) is a different-kind incident; the case file carries no related_rows and no source shows a comparable weakness left unfixed, so no recurring-weakness marker was coded. RM39 was considered for the late, partly inaccurate public account but dropped: its Expertise to Execution lens requires forensic scoping constraints as the mechanism, and the delayed acknowledgement is instead described in the rationale as a response-stage condition. No action requiring consent was needed or taken.