HB 96 (ORC 9.64) Cybersecurity Compliance for Ohio Public Entities
Ohio Compliance
What HB 96 Requires
Adopt a Cybersecurity Program
Incident Reporting Requirements
Ransomware Decision Process
Public Records Exemption
Common Challenges
Where Ohio Entities
Get Stuck
• “We can’t prove training completion or role-based requirements.”
• “We don’t know what triggers the 7-day reporting clock.”
• “Our incident response plan doesn’t include the legislative path for ransomware decisions.”
• “We lack the in-house expertise to build a compliant program from scratch.”
Compliance Services
How Great Lakes Computer
Gets You Compliant

HB 96 Readiness Assessment
• Gap assessment mapped to NIST/CIS frameworks
• Draft adoption-ready program outline
• Prioritized action plan

Program Build + Audit Binder
• Written cybersecurity program with core policies
• Training plan with completion tracking
• Evidence binder for state audits

Operate & Monitor
• 24/7 SOC monitoring
• Vulnerability management & periodic testing
• Incident response support playbooks
Trusted Partner
Why Ohio Entities Partner with Great Lakes Computer
• 30+ years serving Ohio government and enterprise clients
• State of Ohio MMA contract holder – streamlined procurement
• Expertise in regulatory compliance (NIST, CIS, CJIS)
• Predictable budgeting vs. building an in-house security team
• Single point of accountability for your compliance program
Resources
HB 96 Compliance Resources
Downloadable Guides
A one-page checklist covering the key requirements for Ohio public entities.
What to do in the first 24 hours of a cybersecurity incident, including reporting timelines.
Frequently Asked Questions
What counts as a cybersecurity incident under HB 96?
Does HB 96 apply to small townships?
What do state auditors check for compliance?
Can we use NIST or CIS frameworks - or both?
What happens if we miss the compliance deadline?
Great Lakes Computer has helped Ohio public entities build audit-ready cybersecurity programs since 1990.