Insurance data security laws in nine selected states: notice to the regulator and small-licensee exemptions
| State | Citation | Effective date | Notice to the insurance regulator | Small-licensee exemption |
|---|---|---|---|---|
| South Carolina1 | CitationS.C. Code Title 38, Chapter 99 (South Carolina Insurance Data Security Act), 2018 Act No. 1711 | Effective dateJanuary 1, 2019 (2018 Act No. 171, section 3)1 | Notice to the insurance regulatorTo the director no later than 72 hours after determining a cybersecurity event occurred, when South Carolina is the insurer's domicile or the producer's home state, or the event involves 250 or more South Carolina consumers and meets the statute's other criteria (38-99-40(A)).1 | Small-licensee exemptionFewer than ten employees, including independent contractors: exempt from the information security program section, 38-99-20 (38-99-70(A)(1)).1 |
| Ohio2 | CitationOhio Rev. Code Chapter 3965 (Cybersecurity Requirements for Insurance Companies), Senate Bill 273, 132nd General Assembly2 | Effective dateMarch 20, 2019 (as shown for each section on the Ohio Laws site)2 | Notice to the insurance regulatorTo the superintendent as promptly as possible, no later than three business days after determining a cybersecurity event involving nonpublic information occurred, when the statute's criteria are met (3965.04(A)).2 | Small-licensee exemptionFewer than 20 employees, less than $5 million in gross annual revenue, or less than $10 million in assets at fiscal year end: exempt from the information security program section, 3965.02 (3965.07(A)).2 |
| New Hampshire3 | CitationN.H. RSA Chapter 420-P (Insurance Data Security Law), 2019, 309:13 | Effective dateJanuary 1, 2020 (Source note: 2019, 309:1, eff. Jan. 1, 2020)3 | Notice to the insurance regulatorTo the commissioner within 3 business days of determining a cybersecurity event occurred, when either of the statute's criteria is met (RSA 420-P:6, I).3 | Small-licensee exemptionFewer than 20 employees, including independent contractors: exempt from the information security program section, RSA 420-P:4 (RSA 420-P:9).3 |
| Delaware4 | Citation18 Del. C. Chapter 86 (Insurance Data Security Act), 82 Del. Laws, c. 1764 | Effective dateTakes effect upon enactment; the act shows Approved July 31, 2019. Licensees had 1 year to implement section 8604 and 2 years for 8604(f).5 | Notice to the insurance regulatorTo the Commissioner as promptly as possible, no later than 3 business days from determining a cybersecurity event occurred, when either of the statute's criteria is met (8606(a)).4 | Small-licensee exemptionFewer than 15 employees: exempt from the information security program section, 8604 (8609(a)(1)).4 |
| Connecticut6 | CitationConn. Gen. Stat. 38a-38 (Insurance Data Security Law), P.A. 19-1176 | Effective dateOctober 1, 2020: P.A. 19-196 changed the effective date of P.A. 19-117 from October 1, 2019, to October 1, 2020 (history note). Information security program required by October 1, 2021.6 | Notice to the insurance regulatorTo the Insurance Commissioner as promptly as possible, no later than three business days after first determining a cybersecurity event occurred, when the statute's criteria are met (38a-38(e)(1)).6 | Small-licensee exemptionFewer than ten employees, including independent contractors with access to nonpublic information, from October 1, 2022 (fewer than twenty from October 1, 2021, to September 30, 2022): exempt from the information security program subsection (38a-38(c)(10)).6 |
| Virginia7 | CitationVa. Code 38.2-621 to 38.2-629, 2020, c. 2647 | Effective dateNot confirmed (see Method) | Notice to the insurance regulatorTo the Commissioner as promptly as possible, no later than three business days after determining a cybersecurity event actually occurred, for a domestic insurer or home-state producer meeting thresholds the Commission sets, or when 250 or more Virginia consumers are involved or another law requires notice to a government body (38.2-625(A)).7 | Small-licensee exemptionNo employee-count or size exemption in 38.2-629. Its exceptions cover licensees meeting HIPAA security requirements that certify compliance, licensees covered by another licensee's program, and affiliates of depository institutions under the Interagency Guidelines.7 |
| Minnesota8 | CitationMinn. Stat. 60A.985 to 60A.9857, 1Sp2021 c 4 art 38 | Effective dateAugust 1, 2021; licensees had one year to implement most of the information security program and two years for third-party service provider oversight (1Sp2021 c 4 art 3).9 | Notice to the insurance regulatorTo the commissioner of commerce or of health, without unreasonable delay and no later than five business days from determining a cybersecurity event occurred, when the statute's criteria are met (60A.9853, subd. 1).8 | Small-licensee exemptionFewer than 25 employees: exempt from sections 60A.9851 (information security program) and 60A.9852 (investigation) (60A.9856, subd. 1).10 |
| Iowa11 | CitationIowa Code Chapter 507F (Insurance Data Security Act), 2021 Acts, ch 7911 | Effective dateJanuary 1, 2022 (2021 Acts, ch 79, section 17); the act was approved April 30, 2021.13 | Notice to the insurance regulatorTo the commissioner no later than three business days from the licensee's confirmation of a cybersecurity event, when the statute's conditions apply (507F.7(1)).11 | Small-licensee exemptionFewer than twenty individuals on its workforce (employees and independent contractors), less than $5 million in gross annual revenue, or less than $10 million in year-end total assets: the information security program section, 507F.4, does not apply.11 |
| North Dakota12 | CitationN.D. Cent. Code Chapter 26.1-02.2 (Insurance Data Security)12 | Effective dateNot confirmed (see Method) | Notice to the insurance regulatorTo the commissioner as promptly as possible, no later than three business days from determining a cybersecurity event occurred, when the statute's criteria are met (26.1-02.2-05(1)).12 | Small-licensee exemptionLess than $5 million in gross revenue or less than $10 million in year-end assets: exempt from subsections 2 through 10 of the information security program section, 26.1-02.2-03 (26.1-02.2-08(1)(a)). No employee-count threshold.12 |
License: CC BY 4.0. Underlying government texts are public domain or under their own terms. Attribute "Moraph Insights" with a link to the page.
Method
We opened each selected state's statute on its legislature's or code publisher's official site and copied the citation, effective date, deadline for notifying the insurance regulator and any small-licensee exemption. Effective dates come from the statute's own history or source notes, or from the session law where we opened it; where neither states a date, the cell is left out (see Omitted). The NAIC's model law and adoption pages could not be opened, so the table covers only the states whose statutes we opened and makes no claim about which follow the NAIC model or how many states have such a law. Notice cells summarize the triggering criteria; the statutes add conditions on consumer counts and other notices. Every cell was checked on 2026-11-14. This table explains the statutes; it is not legal advice.
Omitted
What was left out, and why.
- Every row · State: The NAIC's Insurance Data Security Model Law (#668) pages on content.naic.org returned HTTP 403 to automated requests on 2026-11-14, so which states the NAIC counts as adopting the model, and the full set of states with such a law, could not be confirmed. The table is a selection of states, not a complete list, and does not label any row as based on the model.
- Virginia · Effective date: The Code of Virginia page shows only the session law (2020, c. 264). The session law (Acts of Assembly 2020, chapter 264, opened on 2026-11-14) shows Approved March 10, 2020 and contains no effective-date clause, so no source opened states the effective date.
- North Dakota · Effective date: The North Dakota Century Code chapter states no effective date; its implementation-dates section, 26.1-02.2-11, shows as repealed by S.L. 2025, ch. 280, section 5.
Sources
- South Carolina Legislature. S.C. Code Title 38, Chapter 99, Insurance Data Security. Checked .
- Ohio Legislative Service Commission. Ohio Revised Code Chapter 3965, Cybersecurity Requirements for Insurance Companies. Checked .
- New Hampshire General Court. N.H. RSA Chapter 420-P, Insurance Data Security Law. Checked .
- Delaware General Assembly. 18 Del. C. Chapter 86, Insurance Data Security Act. Checked .
- Delaware General Assembly. 82 Del. Laws, c. 176 (Insurance Data Security Act session law). Checked .
- Connecticut General Assembly. Conn. Gen. Stat. Chapter 697, section 38a-38, Insurance Data Security Law. Checked .
- Virginia General Assembly, Division of Legislative Automated Systems. Code of Virginia, Title 38.2, Chapter 6, Article 2, Insurance Data Security Act (38.2-621 to 38.2-629). Checked .
- Minnesota Office of the Revisor of Statutes. Minn. Stat. 60A.9853, Notification of a cybersecurity event. Checked .
- Minnesota Office of the Revisor of Statutes. Laws of Minnesota 2021, First Special Session, chapter 4, article 3 (sections 60A.985 to 60A.9857). Checked .
- Minnesota Office of the Revisor of Statutes. Minn. Stat. 60A.9856, Exceptions. Checked .
- Iowa Legislature. Iowa Code 2026, Chapter 507F, Insurance Data Security. Checked .
- North Dakota Legislative Branch. N.D. Cent. Code Chapter 26.1-02.2, Insurance Data Security. Checked .
- Iowa Legislature. 2021 Iowa Acts, chapter 79 (House File 719), Insurance Data Security. Checked .
How we source and check every fact: Editorial standards · Corrections
Last reviewed .
Spotted an error? Tell us and we will check it and correct the table where needed.