The Assignment
Back in 2018, the Ohio Secretary of State issued Directive 2018-15, directing counties to conduct security assessments of their election infrastructure. Clark State Community College was designated to lead the assessment for Clark County, and they brought us in to handle the technical evaluation.
Election systems are high-value targets: voter registration databases, ballot handling systems, tabulation equipment. A breach compromises data and undermines public confidence in the democratic process. The assignment was straightforward: evaluate the county's election infrastructure against established security frameworks and identify gaps.
The four-phase assessment framework used for Clark County's election infrastructure evaluation
The Framework
We used the CIS Controls as the foundation, the same framework used across critical infrastructure sectors. It's an 88-item checklist that covers everything from basic inventory management (knowing what systems you have) to advanced measures like intrusion detection and incident response planning.
For Clark County, our work covered the majority of these controls. Working alongside Clark State faculty (Professor Dan Heighton, Professor Greg Teets, William Blake, and Brian Sammons), we systematically evaluated each component of the county's election infrastructure.
What We Did
The assessment had several phases:
Documentation Review: We started with what was already documented: network diagrams, security policies, access control procedures, system configurations. This gave us the baseline.
Onsite Technical Evaluation: Then we went onsite. Multiple visits to observe systems in operation, interview personnel about day-to-day security practices, and verify that documented procedures matched reality. We looked at voter registration systems, pollbook preparation, vote tabulation equipment, and result reporting infrastructure.
Technical Testing: We evaluated network segmentation (were election systems properly isolated?), access controls (who had admin privileges and why?), logging and monitoring capabilities, backup procedures, and physical security measures.
Gap Analysis: For each CIS Control, we documented current state versus recommended state. Where were the vulnerabilities? What were the highest-priority fixes?

What We Found
The specific findings remain confidential. That's standard for security assessments. But in general terms, what we typically see in these environments:
- Legacy Systems: Equipment and software that worked fine when installed but hadn't kept pace with evolving threats
- Network Architecture Gaps: Insufficient segmentation between election systems and general county networks
- Access Control Issues: Too many people with administrative privileges, weak password policies
- Monitoring Blind Spots: Limited logging and no centralized monitoring to detect suspicious activity
- Incomplete Incident Response Plans: No clear procedures for what to do if something went wrong
Gaps like these build up when systems are deployed over time without a comprehensive security framework. Our job was to identify the gaps and recommend practical fixes that the county could implement.
How election security threats have evolved: 2018 baseline vs. 2026 reality
What's Changed Since 2018
Eight years later, the fundamentals haven't changed. You still need proper network segmentation, access controls, monitoring, and incident response. But the threats have changed:
- Ransomware is Everywhere: In 2018, ransomware was a concern. In 2026, it's assumed. Critical infrastructure organizations, including counties, are prime targets.
- Supply Chain Attacks: Compromising vendors and service providers has become a preferred attack vector.
- AI-Powered Threats: Social engineering and phishing have gotten sophisticated enough that even trained staff can be fooled.
- Regulatory Requirements Have Tightened: What was recommended in 2018 is often required in 2026, especially for critical infrastructure.
The method we used in Clark County (a CIS Controls-based assessment, gap analysis and prioritized remediation) is the same one we use today for cybersecurity risk assessments in every sector. The framework applies the same way to election systems, healthcare patient records, legal case files, or financial transactions.
What This Experience Means for Your Organization
Election infrastructure security and business security aren't that different. Both require:
- Understanding what systems you have and how they connect
- Knowing who has access to what and why
- Monitoring for suspicious activity
- Having a plan for when something goes wrong
- Keeping pace with evolving threats
The same CIS Controls framework we used in 2018 for Clark County is what we implement today for Ohio businesses. If your security was set up three years ago and hasn't been reassessed since, you're likely in the same position Clark County was in 2018: a solid foundation, but gaps have emerged as threats evolved.
That's fixable. But it requires a systematic assessment to identify where the gaps are, followed by prioritized remediation that fits your budget and operational reality.
Want to Know Where Your Gaps Are?
We conduct the same style of technical assessment we did for Clark County, adapted for your industry and risk profile. We use established frameworks (CIS Controls, NIST, industry-specific standards), evaluate your current state, identify gaps, and recommend prioritized fixes.
We tell you what we find, recommend what makes sense to fix, and let you decide how to proceed. Some clients handle remediation internally. Others want us to implement the fixes.
See what the risk assessment covers and how it is quoted.
Ready to Identify Your Security Gaps?
We assess Ohio businesses using the same framework we used for Clark County's election infrastructure. Let's figure out where your vulnerabilities are and what makes sense to fix first.
Quoted as project work. You see the scope in writing before work starts.
A 15-minute call, then written security findings with action items. No cost and no obligation.
Managed clients: we acknowledge every support request by phone, email or our portal by the end of the next business day.
Prefer to write it out? Send us the details.