{
 "page": "https://insights.moraph.com/compare/state-insurance-data-security-laws",
 "csv": "https://insights.moraph.com/compare/state-insurance-data-security-laws.csv",
 "publisher": "Moraph",
 "license": "https://creativecommons.org/licenses/by/4.0/",
 "license_note": "License: CC BY 4.0. Underlying government texts are public domain or under their own terms.",
 "attribution": "Moraph Insights, https://insights.moraph.com/compare/state-insurance-data-security-laws",
 "slug": "state-insurance-data-security-laws",
 "title": "Insurance data security laws in nine selected states: notice to the regulator and small-licensee exemptions",
 "sector": "Financial Services",
 "lens": "Regulation & Compliance",
 "in_short": "This table covers nine selected states whose insurance data security statutes we opened; it is not a complete list, and other states may have similar laws. Of the nine, South Carolina gives licensees 72 hours to notify the regulator after determining a cybersecurity event occurred; Ohio, New Hampshire, Delaware, Connecticut, Virginia, Iowa and North Dakota allow three business days, and Minnesota five business days. Employee-count exemptions from the information security program range from fewer than ten employees (South Carolina, Connecticut) to fewer than 25 (Minnesota); Ohio and Iowa add revenue and asset tests, North Dakota uses revenue and assets only, and Virginia sets no size exemption.",
 "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.",
 "published": "2026-11-14",
 "last_reviewed": "2026-11-14",
 "columns": [
  {
   "id": "state",
   "label": "State"
  },
  {
   "id": "citation",
   "label": "Citation"
  },
  {
   "id": "effective",
   "label": "Effective date"
  },
  {
   "id": "notice",
   "label": "Notice to the insurance regulator"
  },
  {
   "id": "exemption",
   "label": "Small-licensee exemption"
  }
 ],
 "rows": [
  {
   "id": "south-carolina",
   "cells": {
    "state": {
     "text": "South Carolina",
     "source": "s1",
     "checked": "2026-11-14"
    },
    "citation": {
     "text": "S.C. Code Title 38, Chapter 99 (South Carolina Insurance Data Security Act), 2018 Act No. 171",
     "source": "s1",
     "checked": "2026-11-14"
    },
    "effective": {
     "text": "January 1, 2019 (2018 Act No. 171, section 3)",
     "source": "s1",
     "checked": "2026-11-14"
    },
    "notice": {
     "text": "To 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)).",
     "source": "s1",
     "checked": "2026-11-14"
    },
    "exemption": {
     "text": "Fewer than ten employees, including independent contractors: exempt from the information security program section, 38-99-20 (38-99-70(A)(1)).",
     "source": "s1",
     "checked": "2026-11-14"
    }
   }
  },
  {
   "id": "ohio",
   "cells": {
    "state": {
     "text": "Ohio",
     "source": "s2",
     "checked": "2026-11-14"
    },
    "citation": {
     "text": "Ohio Rev. Code Chapter 3965 (Cybersecurity Requirements for Insurance Companies), Senate Bill 273, 132nd General Assembly",
     "source": "s2",
     "checked": "2026-11-14"
    },
    "effective": {
     "text": "March 20, 2019 (as shown for each section on the Ohio Laws site)",
     "source": "s2",
     "checked": "2026-11-14"
    },
    "notice": {
     "text": "To 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)).",
     "source": "s2",
     "checked": "2026-11-14"
    },
    "exemption": {
     "text": "Fewer 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)).",
     "source": "s2",
     "checked": "2026-11-14"
    }
   }
  },
  {
   "id": "new-hampshire",
   "cells": {
    "state": {
     "text": "New Hampshire",
     "source": "s3",
     "checked": "2026-11-14"
    },
    "citation": {
     "text": "N.H. RSA Chapter 420-P (Insurance Data Security Law), 2019, 309:1",
     "source": "s3",
     "checked": "2026-11-14"
    },
    "effective": {
     "text": "January 1, 2020 (Source note: 2019, 309:1, eff. Jan. 1, 2020)",
     "source": "s3",
     "checked": "2026-11-14"
    },
    "notice": {
     "text": "To 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).",
     "source": "s3",
     "checked": "2026-11-14"
    },
    "exemption": {
     "text": "Fewer than 20 employees, including independent contractors: exempt from the information security program section, RSA 420-P:4 (RSA 420-P:9).",
     "source": "s3",
     "checked": "2026-11-14"
    }
   }
  },
  {
   "id": "delaware",
   "cells": {
    "state": {
     "text": "Delaware",
     "source": "s4",
     "checked": "2026-11-14"
    },
    "citation": {
     "text": "18 Del. C. Chapter 86 (Insurance Data Security Act), 82 Del. Laws, c. 176",
     "source": "s4",
     "checked": "2026-11-14"
    },
    "effective": {
     "text": "Takes effect upon enactment; the act shows Approved July 31, 2019. Licensees had 1 year to implement section 8604 and 2 years for 8604(f).",
     "source": "s5",
     "checked": "2026-11-14"
    },
    "notice": {
     "text": "To 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)).",
     "source": "s4",
     "checked": "2026-11-14"
    },
    "exemption": {
     "text": "Fewer than 15 employees: exempt from the information security program section, 8604 (8609(a)(1)).",
     "source": "s4",
     "checked": "2026-11-14"
    }
   }
  },
  {
   "id": "connecticut",
   "cells": {
    "state": {
     "text": "Connecticut",
     "source": "s6",
     "checked": "2026-11-14"
    },
    "citation": {
     "text": "Conn. Gen. Stat. 38a-38 (Insurance Data Security Law), P.A. 19-117",
     "source": "s6",
     "checked": "2026-11-14"
    },
    "effective": {
     "text": "October 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.",
     "source": "s6",
     "checked": "2026-11-14"
    },
    "notice": {
     "text": "To 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)).",
     "source": "s6",
     "checked": "2026-11-14"
    },
    "exemption": {
     "text": "Fewer 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)).",
     "source": "s6",
     "checked": "2026-11-14"
    }
   }
  },
  {
   "id": "virginia",
   "cells": {
    "state": {
     "text": "Virginia",
     "source": "s7",
     "checked": "2026-11-14"
    },
    "citation": {
     "text": "Va. Code 38.2-621 to 38.2-629, 2020, c. 264",
     "source": "s7",
     "checked": "2026-11-14"
    },
    "notice": {
     "text": "To 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)).",
     "source": "s7",
     "checked": "2026-11-14"
    },
    "exemption": {
     "text": "No 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.",
     "source": "s7",
     "checked": "2026-11-14"
    }
   }
  },
  {
   "id": "minnesota",
   "cells": {
    "state": {
     "text": "Minnesota",
     "source": "s8",
     "checked": "2026-11-14"
    },
    "citation": {
     "text": "Minn. Stat. 60A.985 to 60A.9857, 1Sp2021 c 4 art 3",
     "source": "s8",
     "checked": "2026-11-14"
    },
    "effective": {
     "text": "August 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).",
     "source": "s9",
     "checked": "2026-11-14"
    },
    "notice": {
     "text": "To 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).",
     "source": "s8",
     "checked": "2026-11-14"
    },
    "exemption": {
     "text": "Fewer than 25 employees: exempt from sections 60A.9851 (information security program) and 60A.9852 (investigation) (60A.9856, subd. 1).",
     "source": "s10",
     "checked": "2026-11-14"
    }
   }
  },
  {
   "id": "iowa",
   "cells": {
    "state": {
     "text": "Iowa",
     "source": "s11",
     "checked": "2026-11-14"
    },
    "citation": {
     "text": "Iowa Code Chapter 507F (Insurance Data Security Act), 2021 Acts, ch 79",
     "source": "s11",
     "checked": "2026-11-14"
    },
    "effective": {
     "text": "January 1, 2022 (2021 Acts, ch 79, section 17); the act was approved April 30, 2021.",
     "source": "s13",
     "checked": "2026-11-14"
    },
    "notice": {
     "text": "To 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)).",
     "source": "s11",
     "checked": "2026-11-14"
    },
    "exemption": {
     "text": "Fewer 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.",
     "source": "s11",
     "checked": "2026-11-14"
    }
   }
  },
  {
   "id": "north-dakota",
   "cells": {
    "state": {
     "text": "North Dakota",
     "source": "s12",
     "checked": "2026-11-14"
    },
    "citation": {
     "text": "N.D. Cent. Code Chapter 26.1-02.2 (Insurance Data Security)",
     "source": "s12",
     "checked": "2026-11-14"
    },
    "notice": {
     "text": "To 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)).",
     "source": "s12",
     "checked": "2026-11-14"
    },
    "exemption": {
     "text": "Less 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.",
     "source": "s12",
     "checked": "2026-11-14"
    }
   }
  }
 ],
 "sources": [
  {
   "id": "s1",
   "title": "S.C. Code Title 38, Chapter 99, Insurance Data Security",
   "publisher": "South Carolina Legislature",
   "url": "https://www.scstatehouse.gov/code/t38c099.php",
   "checked": "2026-11-14"
  },
  {
   "id": "s2",
   "title": "Ohio Revised Code Chapter 3965, Cybersecurity Requirements for Insurance Companies",
   "publisher": "Ohio Legislative Service Commission",
   "url": "https://codes.ohio.gov/ohio-revised-code/chapter-3965",
   "checked": "2026-11-14"
  },
  {
   "id": "s3",
   "title": "N.H. RSA Chapter 420-P, Insurance Data Security Law",
   "publisher": "New Hampshire General Court",
   "url": "https://gc.nh.gov/rsa/html/XXXVII/420-P/420-P-mrg.htm",
   "checked": "2026-11-14"
  },
  {
   "id": "s4",
   "title": "18 Del. C. Chapter 86, Insurance Data Security Act",
   "publisher": "Delaware General Assembly",
   "url": "https://delcode.delaware.gov/title18/c086/index.html",
   "checked": "2026-11-14"
  },
  {
   "id": "s5",
   "title": "82 Del. Laws, c. 176 (Insurance Data Security Act session law)",
   "publisher": "Delaware General Assembly",
   "url": "https://delcode.delaware.gov/sessionlaws/ga150/chp176.shtml",
   "checked": "2026-11-14"
  },
  {
   "id": "s6",
   "title": "Conn. Gen. Stat. Chapter 697, section 38a-38, Insurance Data Security Law",
   "publisher": "Connecticut General Assembly",
   "url": "https://www.cga.ct.gov/current/pub/chap_697.htm",
   "checked": "2026-11-14"
  },
  {
   "id": "s7",
   "title": "Code of Virginia, Title 38.2, Chapter 6, Article 2, Insurance Data Security Act (38.2-621 to 38.2-629)",
   "publisher": "Virginia General Assembly, Division of Legislative Automated Systems",
   "url": "https://law.lis.virginia.gov/vacodefull/title38.2/chapter6/article2/",
   "checked": "2026-11-14"
  },
  {
   "id": "s8",
   "title": "Minn. Stat. 60A.9853, Notification of a cybersecurity event",
   "publisher": "Minnesota Office of the Revisor of Statutes",
   "url": "https://www.revisor.mn.gov/statutes/cite/60A.9853",
   "checked": "2026-11-14"
  },
  {
   "id": "s9",
   "title": "Laws of Minnesota 2021, First Special Session, chapter 4, article 3 (sections 60A.985 to 60A.9857)",
   "publisher": "Minnesota Office of the Revisor of Statutes",
   "url": "https://www.revisor.mn.gov/laws/2021/1/Session+Law/Chapter/4/",
   "checked": "2026-11-14"
  },
  {
   "id": "s10",
   "title": "Minn. Stat. 60A.9856, Exceptions",
   "publisher": "Minnesota Office of the Revisor of Statutes",
   "url": "https://www.revisor.mn.gov/statutes/cite/60A.9856",
   "checked": "2026-11-14"
  },
  {
   "id": "s11",
   "title": "Iowa Code 2026, Chapter 507F, Insurance Data Security",
   "publisher": "Iowa Legislature",
   "url": "https://www.legis.iowa.gov/docs/code/507F.pdf",
   "checked": "2026-11-14"
  },
  {
   "id": "s12",
   "title": "N.D. Cent. Code Chapter 26.1-02.2, Insurance Data Security",
   "publisher": "North Dakota Legislative Branch",
   "url": "https://ndlegis.gov/cencode/t26-1c02-2.pdf",
   "checked": "2026-11-14"
  },
  {
   "id": "s13",
   "title": "2021 Iowa Acts, chapter 79 (House File 719), Insurance Data Security",
   "publisher": "Iowa Legislature",
   "url": "https://www.legis.iowa.gov/docs/acts/2021/CH0079.pdf",
   "checked": "2026-11-14"
  }
 ],
 "notes": [],
 "omitted": [
  {
   "where": "all/state",
   "reason": "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."
  },
  {
   "where": "virginia/effective",
   "reason": "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."
  },
  {
   "where": "north-dakota/effective",
   "reason": "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."
  }
 ]
}
