ORC 9.64 Compliance Support

Ohio political subdivision cybersecurity

GPI helps local governments meet the requirements of Ohio Revised Code 9.64.

ORC 9.64, “Political subdivision cybersecurity,” was enacted by House Bill 96 of the 136th General Assembly and took effect on September 30, 2025. GPI works with Ohio counties, townships, cities, and other political subdivisions to adopt a cybersecurity program, report incidents on time, and handle ransom decisions the law requires.

3 things ORC 9.64 requires

These duties come from the official statute text.

Adopt a cybersecurity program

The legislative authority must adopt a program that protects data and IT for availability, confidentiality, and integrity. It must follow generally accepted practices such as the NIST Cybersecurity Framework or CIS best practices.

Report incidents on a deadline

After each cybersecurity or ransomware incident, notify Homeland Security within 7 days of discovery, and the Auditor of State within 30 days. Official guidance names the Ohio Cyber Integration Center as the Homeland Security contact.

Approve ransom decisions formally

Do not pay or otherwise comply with a ransom demand unless the legislative authority approves it in a resolution or ordinance that states why that action is in the political subdivision’s best interest.

A program may include risk identification, threat detection, incident handling, recovery, and employee training scaled to each job. Annual training from the state, or from the Ohio Persistent Cyber Initiative at the Ohio Cyber Range Institute, satisfies the training requirement. Program materials and incident reports are not public records under ORC 149.43. Records that identify cybersecurity products or vendors are security records under ORC 149.433.

Incident reporting timeline

The clock starts when the political subdivision discovers a cybersecurity or ransomware incident. Notice is due as soon as possible, and no later than these deadlines.

0

Day 0 — Discover

The reporting timeline begins when the political subdivision discovers a cybersecurity or ransomware incident.

7

Day 7 — Notify OCIC

Notify the Homeland Security executive director, in the manner that director prescribes, no later than seven days after discovery. Official guidance names OCIC as the point of contact.

30

Day 30 — Notify the Auditor of State

Also notify the Auditor of State, in the manner the Auditor prescribes, no later than 30 days after the political subdivision discovers the incident.

Our services

GPI can help a political subdivision close gaps against ORC 9.64. We do not file official reports in an entity’s name, and we do not replace legal counsel or the legislative authority. This offering sits alongside GPI’s existing CMMC Level II Support practice.

Gap assessment

  • Compare current policies and controls to ORC 9.64
  • Align with NIST CSF or CIS best practices
  • Deliver a written gap analysis and roadmap

Program and policy development

  • Draft a program the legislative authority can adopt
  • Protect availability, confidentiality, and integrity
  • Tailor documents to the entity’s size and operations

Incident response and reporting playbooks

  • Define how to detect, contain, and recover
  • Meet the 7-day Homeland Security / OCIC notice
  • Meet the 30-day Auditor of State notice

Ransomware decision support

  • Set a formal legislative-approval process
  • Prepare draft resolution or ordinance language
  • The legislative authority remains the decision maker

Employee training

  • Set training requirements scaled to job duties
  • Point staff to qualifying state-provided training
  • Include Ohio Persistent Cyber Initiative options

Ongoing vCISO and monitoring

  • Maintain the adopted program over time
  • Run tabletop exercises and periodic check-ins
  • Review vendor and supply-chain risk

How it works

A four-step engagement, from scoping through adoption and ongoing readiness.

1

Consultation and scoping

Meet with administrators, IT or security leads, fiscal officers, and, as needed, the legislative authority to confirm coverage under ORC 9.64 and agree on scope.

2

Gap assessment

Compare existing practices to the statute and to a generally accepted framework such as NIST CSF or CIS Controls, then deliver findings and a practical roadmap.

3

Build and adopt

Draft or revise the program, policies, playbooks, training requirements, and ransom-approval materials for legal review and formal adoption.

4

Prepare and sustain

Rehearse reporting and response steps, connect staff to qualifying state or Ohio Cyber Range Institute training, and continue with vCISO support if requested.

Who we serve

ORC 9.64 applies to a “political subdivision,” which the statute defines as a county, township, municipal corporation, or other body corporate and politic responsible for governmental activities in a geographic area smaller than that of the state.

An official Auditor of State presentation describes the law as applying to all political subdivisions under that definition. GPI designed this support for those Ohio local governments and for the administrators, IT and security staff, fiscal officers, and legislative authorities who must implement the law.

The statute itself does not set staggered program-adoption deadlines. Official Auditor of State guidance presented with CyberOhio stated these compliance dates for adopting a program: counties and cities by January 1, 2026, and all other political subdivisions by July 1, 2026. Incident reporting and ransom-approval duties were described as effective on September 30, 2025. Those program-adoption dates have already passed. Entities that have not yet adopted a program, or that need to strengthen one, can still use this process.

Frequently asked questions

Who must comply with ORC 9.64?
The statute applies to political subdivisions: counties, townships, municipal corporations, and other bodies corporate and politic responsible for governmental activities in a geographic area smaller than that of the state. Whether a particular local entity falls under the “other body corporate and politic” clause should be confirmed with the entity’s legal counsel.
What counts as a cybersecurity incident or a ransomware incident?
The statute defines a cybersecurity incident as any of the following: a substantial loss of confidentiality, integrity, or availability of a covered entity’s information system or network; a serious impact on the safety and resiliency of a covered entity’s operational systems and processes; a disruption of a covered entity’s ability to engage in business or industrial operations, or deliver goods or services; or unauthorized access to an entity’s information system or network, or nonpublic information in it, facilitated through or caused by a compromise of a cloud service provider, managed service provider, or other third-party data hosting provider, or by a supply chain compromise.

The term does not include mere threats of disruption as extortion; events perpetrated in good faith in response to a request by the system owner or operator; or lawfully authorized activity of a United States, state, local, tribal, or territorial government entity. The statute uses the phrase “covered entity” in this definition even though the rest of the section addresses political subdivisions.

A ransomware incident is a malicious cybersecurity incident in which a person or entity introduces software that gains unauthorized access to, or encrypts, modifies, or otherwise renders unavailable, a political subdivision’s information technology systems or data, and then demands a ransom to prevent publication of the data, restore access to the data, or otherwise remediate the impact of the software.

Official OCIC reporting guidance states that if there is doubt about whether an event is reportable, the entity should report it and OCIC will help determine whether a formal report is warranted.

Where and how quickly must incidents be reported?
Notice is due as soon as possible after discovery: no later than seven days to the executive director of the Division of Homeland Security, and no later than 30 days to the Auditor of State. Official guidance identifies OCIC as Homeland Security’s point of contact. As published by OCIC and in an official Auditor of State presentation, current contact points include:

– OCIC: email OCIC@dps.ohio.gov, phone 614-387-1089, or https://homelandsecurity.ohio.gov/ohio-cyber-integration-center
– Auditor of State: email Cyber@ohioauditor.gov, using the cybersecurity reporting form at https://ohioauditor.gov/fraud/docs/CybersecurityReportingForm.pdf, or phone 866-FRAUD-OH

On November 16, 2026, the Auditor of State website was not returning those pages from the environment used to research this draft. Confirm the form and email address on the Auditor’s site or by calling the office before you rely on them in an incident.

Can a political subdivision pay a ransom?
Only if the legislative authority formally approves the payment or other compliance in a resolution or ordinance that specifically states why that action is in the best interest of the political subdivision. The statute does not create a blanket prohibition, and it does not create a right to pay. It requires that formal, documented legislative approval first.
Must the program follow NIST or CIS exactly?
No. The program must be consistent with generally accepted best practices for cybersecurity. The statute names the NIST Cybersecurity Framework and CIS cybersecurity best practices as examples, not as the only permitted approaches. The six program elements listed in the statute are permissive (“may include, but are not limited to”).
Are program documents and incident reports public records?
Records, documents, or reports related to the cybersecurity program and framework, and reports of a cybersecurity or ransomware incident under the statute, are not public records under ORC 149.43. Records that identify cybersecurity-related software, hardware, goods, and services being considered, procured, or used—including vendor name, product name, project name, or project description—are security records under ORC 149.433. Counsel should still review any public-records request, because other records may be treated differently.
Does GPI replace legal counsel or official reporting?
No. GPI can prepare materials and help staff execute a playbook, but the political subdivision remains responsible for adopting the program, making required notices, and deciding any ransom response. Legal questions should go to the entity’s legal counsel.

Schedule a consultation

If your political subdivision needs to adopt, update, or operationalize an ORC 9.64 cybersecurity program, GPI can walk through your current posture and outline a practical path forward.

This page is for informational purposes only. It is not legal advice and is not an official government publication. The summary of Ohio Revised Code 9.64 is based on official sources reviewed on November 16, 2026, and may not reflect later amendments or new agency guidance. Political subdivisions should consult their legal counsel and confirm current reporting instructions with the Ohio Department of Public Safety / OCIC and the Auditor of State before acting.