Skip to content

Managed IT and Cybersecurity for Columbus Insurance Agencies

Your cyber insurance renewal has a date on it, and the questions on the application are about your systems rather than your book. Is multifactor authentication enforced on email and on the agency management system. Is endpoint detection deployed on every machine. Have the backups been restored from. Does a written incident response plan exist.

You sign those answers about an environment where a full financial profile for every household and business you write sits behind a handful of logins, a comparative rater, an e-signature tool and a carrier portal for every appointment you hold. That profile holds Social Security numbers, dates of birth, driver’s license numbers, bank details, and in benefits work, health information. Those same facts are the ground the state’s own rules cover. Ohio Revised Code Chapter 3965 has been in effect since March 20, 2019, and it is written to reach agents as well as carriers.

Our cyber insurance renewal is due. What does it ask us to prove?

You know the mechanics from the other side of the desk: an application is a set of statements about facts, made on a date. What changes when the application is about your own network is that most agencies have never had to produce the evidence behind an answer, only the answer.

Start with the line the questionnaires lead with. "Is multifactor authentication enforced for all users" is a different question from "is it available." Enforced means a policy that applies to every account, plus the list of accounts it does not apply to: a break-glass admin, a shared mailbox, a service account wired into the rater, a producer who got an exclusion in March that nobody removed. When nobody can produce that list, the list is the finding.

The rest work the same way:

  • Endpoint detection: a coverage report counting devices, not licenses, because the gap is usually the laptop that was rebuilt and never re-enrolled.
  • Backups: a restore with a date and the name of the person who ran it. A green checkmark says a file was copied, not that it can be brought back.
  • Training: completion records per person, including everyone hired since the last renewal.
  • Incident response: a written plan that existed before the week you needed it.

Ohio’s Chapter 3965 asks for training and a written incident response plan too, so one body of evidence tends to serve both. Our Virtual CISO and Compliance-as-a-Service work keeps that file current between renewals, and the same file answers a carrier’s security questionnaire and a commercial client’s.

Why would attackers go after an agency like ours?

Because you aggregate. One agency file carries what an attacker needs for identity theft, account takeover and follow-on fraud, and your book concentrates hundreds or thousands of those files in one system.

On June 16, 2025, John Hultquist, chief analyst at Google’s Threat Intelligence Group, warned that the crew tracked as Scattered Spider had turned to the US insurance sector. He said the industry should be on high alert “especially for social engineering schemes which target their help desks and call centers.”

In practice that looks like this:

  • A convincing caller talks someone into a password reset or a fresh MFA enrollment.
  • A lookalike domain arrives on a renewal thread.
  • A carrier portal password gets reused from a personal account.

The countermeasures are unglamorous, and they work:

  • Phishing-resistant multifactor authentication.
  • A verification script your staff follows before any credential change.
  • Conditional access on email and the agency management system.
  • Alerting that catches a sign-in from a place your team has never worked.

Our software belongs to someone else. What is still ours to secure?

Count what the agency runs on: the management system, a comparative rater, an e-signature tool, a document repository, cloud email, and a carrier portal for every appointment you hold. Almost none of it runs on hardware in your office, and you cannot patch any of it. Be exact about the parts you can control.

TTS Cyber works with any major agency management system that carries a current support contract from its software provider. A system its vendor no longer supports stops receiving security patches.

The way in is yours:

  • Administrator accounts kept separate from the daily login of the person who holds them.
  • No shared logins on a portal two people use.
  • A unique password from a password manager, with a named owner, on every platform that cannot enforce multifactor authentication.

The device is yours too: full-disk encryption on every laptop that leaves the office, patching that completes, endpoint protection and a screen lock. So is the office network, which our Managed IT and Network Operations Center work covers, down to the guest wireless.

Carrier portals are not in your directory, so disabling someone’s email on their last day does nothing to the eight portals they also held. Keep an inventory of every vendor touching client data, with an owner against each. Review each portal’s user list on a schedule. Treat offboarding as a per-system checklist, with a date and a name on each line.

One more piece stays yours: a copy of your own data. Back up cloud email and documents separately from the platform holding them. To see where the agency stands before the next questionnaire, our $349 Security Analysis at https://outreach.ttscyber.com/analysis is an independent assessment mapped to 38 compliance frameworks, with no other purchase required.

Does Ohio’s Chapter 3965 reach insurance agencies, or only carriers?

Agencies too. The chapter binds a “licensee,” which section 3965.01(M) defines as anyone licensed, authorized or registered, or required to be, under Ohio’s insurance laws. That pulls in captive and independent agencies alike, and it does not turn on headcount or revenue. This is not a carrier-only law.

Size enters only as an exemption from the written program in section 3965.02. A licensee is exempt from that section if it meets any one of three criteria:

  • Fewer than twenty employees.
  • Less than five million dollars in gross annual revenue.
  • Less than ten million dollars in assets at the end of its fiscal year.

The chapter does not define “employee” or say how to count part-time staff or contracted producers, which in this industry is often the question that matters.

There is a second route that has nothing to do with size. A licensee subject to and in compliance with the HIPAA privacy and security rules is deemed to meet the chapter, apart from notification. It has to file a written statement with the superintendent certifying that compliance, and keep supporting records for five years.

The size exemption does not reach the investigation and notification duties in sections 3965.03 and 3965.04, which apply whether or not a licensee is exempt from building the program. The HIPAA route covers everything except notification under section 3965.04.

What does Chapter 3965 require of us?

Unless an exemption applies, the core duty is a comprehensive written information security program, based on your own risk assessment and sized to the agency and the sensitivity of what it holds. The risk assessment decides which of the listed measures are appropriate, and then you put them in place:

  • Access controls that let in only authorized individuals.
  • Encryption or other appropriate protection of nonpublic information while it travels over an external network and while it is stored on a laptop or other portable device or media.
  • Restricted physical access.
  • Effective controls, which may include multifactor authentication.
  • Regular testing and monitoring to detect actual and attempted attacks.
  • Audit trails.
  • Secure disposal of nonpublic information in any format.

The chapter also requires cybersecurity awareness training updated for the risks your assessment found, and a written incident response plan.

Read the encryption line twice. It names laptops and portable media on their own terms, so if your producers carry client files on the road, expect that hardware to be inside the program.

Something happened. Who do we notify, and how fast?

First, investigate promptly. Section 3965.03 requires you to determine whether an event occurred, assess its scope, identify the nonpublic information involved, and restore security. An outside vendor designated to act for you can do that work, but it cannot go undone. If the event happened in a system a service provider maintains, you either take those steps or confirm and document that the provider did. Keep records of every cybersecurity event for at least five years.

Notice to the superintendent is due as promptly as possible and no later than three business days after you determine an event occurred, when either of two tests in section 3965.04(A) is met. One runs on Ohio being your home state as an independent insurance agent, the other on nonpublic information of 250 or more Ohio consumers. Each pairs that scope condition with a harm condition, and both halves have to be true.

That filing is not the end of it. Where superintendent notice is owed, section 3965.04(C) also requires you to comply with Ohio’s breach law, section 1349.19, as it applies, and to send the superintendent a copy of the notice you sent consumers. Consumer notice is due in the most expedient time possible and no later than forty-five days after discovery of the breach or notice of it, subject to the legitimate needs of law enforcement. More than one thousand Ohio residents in one occurrence adds notice to the nationwide consumer reporting agencies.

The two clocks start on different days: three business days from determination, forty-five days from discovery. The small-agency exemption waives neither. Section 1349.19 does not apply to a HIPAA covered entity, but an agency writing benefits is usually a business associate, not a covered entity. The superintendent is told to weigh an agency’s size, but none of this is achievable without logging, retained backups and written procedure in place before the bad week.

Start here

Find out where you actually stand

The Security Analysis is a fixed-scope review of your environment, run independently and mapped to 38 compliance frameworks. It replaces an assumption about your posture with a finding.

Questions we get asked

Which agency management systems does TTS Cyber support?

All the major ones, on one condition: the system has to carry a current support contract from its software provider. That takes in the platforms agencies in this market usually run, Applied Epic, AMS360, EZLynx and HawkSoft among them. The condition is practical rather than commercial. A system its vendor no longer supports stops receiving security patches. So the agency ends up relying on controls built around the software instead of fixes inside it, which is a different position to defend at renewal.

Does having fewer than 20 employees exempt an agency from Chapter 3965?

It can exempt a licensee from the written program, but not from the rest of the chapter. Section 3965.07(A) exempts a licensee from section 3965.02 if it meets any one of three criteria. The three are fewer than twenty employees, less than five million dollars in gross annual revenue, or less than ten million dollars in assets at the end of its fiscal year. The chapter does not define “employee” or say how to count part-time staff or contracted producers. The investigation and notification duties in sections 3965.03 and 3965.04 apply either way. TTS Cyber is not a law firm; this is not legal advice.

Does a carrier’s security program cover a captive agency for Chapter 3965?

Only partly. Section 3965.07(C) exempts an agent or other designee of another licensee from the program requirement only to the extent the other licensee’s program covers it. The exemption is measured part by part, not granted as a status. The prompt investigation, the five-year event records, the three-business-day notice to the superintendent and the consumer notice that follows still sit with the agency. TTS Cyber is not a law firm; this is not legal advice.

Does the February 15 Chapter 3965 certification apply to agencies?

No. The February 15 annual certification in section 3965.02(I) is written for insurers domiciled in Ohio, so it is a carrier obligation. An agency is still a licensee, so the security program, investigation and notification duties reach it. A separate written statement applies only if the agency uses the HIPAA route in section 3965.07(B). TTS Cyber is not a law firm; this is not legal advice.

How long does a licensee have to build the program after it outgrows an exemption?

One hundred eighty days from the date it stops qualifying, under section 3965.07(D). That is enough to do it properly and not much more. Start with the risk assessment, because every control is scaled to it. Then put multifactor authentication on email and the agency management system, and encryption on every laptop and portable drive that leaves the office. End shared logins, add an offboarding checklist that removes carrier portal access, and restore from your backups at least once. TTS Cyber is not a law firm; this is not legal advice.

Is there anything to gain from compliance beyond staying out of trouble with the department?

Yes, and Ohio put it in the statute. Section 3965.08 gives a licensee that satisfies the chapter an affirmative defense to certain tort claims brought under Ohio law or in Ohio courts. These are claims alleging that a failure to implement reasonable information security controls resulted in a data breach of nonpublic information. That defense runs on evidence: a dated risk assessment, a written program, training records and incident logs. TTS Cyber is not a law firm; this is not legal advice.

Primary sources

Read the rules yourself

These are the official texts for the main rules this page covers. The page also draws on other sources named in the text above, which are not linked here. Where a section is named above, it is worth reading in the instrument rather than taking a summary for it, including this one.

TTS Cyber is an IT and cybersecurity company, not a law firm, and nothing on this page is legal advice. This page summarises published rules and cites them so they can be read directly; where this page and the source differ, the source governs. Whether a particular rule reaches a particular business, and what it requires of that business, are legal questions for that business's own attorney.

Page last updated .

Let’s Get in Touch!

Security Analysis

Find out where you actually stand.

Most businesses do not discover a gap until something goes wrong. This is a fixed-scope analysis of your environment, run independently, so you get an answer rather than an opinion.

What the analysis covers