Meet NAIC MDL-668 data security duties with less manual effort
NAIC MDL-668, the Insurance Data Security Model Law, is a model act adopted by the National Association of Insurance Commissioners in 2017 that sets data security standards for insurance licensees. It becomes binding when a state enacts it, and requires a written, risk-based information security programme, oversight of third-party service providers, investigation of cybersecurity events and notification to the insurance commissioner.
Is NAIC MDL-668 right for your organisation?
Insurers, producers and other licensees of a state insurance department must comply when their state has enacted a version of the model law. Licensees with fewer than ten employees are exempt from the information security programme requirements of Section 4, but not from investigation and notification duties. Domiciled insurers must also certify compliance to their commissioner each year by 15 February.
It is a legal or regulatory requirement for organisations in scope.
- Issued by
- National Association of Insurance Commissioners (NAIC)
- Adopted
- 4th quarter 2017, with a technical edit in 2025
- Legal effect
- Binding only where a state has enacted it into law
- Enforced by
- State insurance commissioners
- Notification deadline
- No later than 72 hours after determining a cybersecurity event has occurred (model text)
- Annual certification
- Domiciled insurers certify Section 4 compliance by 15 February each year
- Small business exception
- Licensees with fewer than ten employees are exempt from Section 4
- Type
- Law (mandatory)
- Region
- US
- In OneClickComply
- Supported today
OneClickComply makes it simple
OneClickComply has mapped MDL-668 in its control library, and support is available on request rather than live today. The same controls cover the Section 4 programme elements, such as risk assessment, access controls, encryption, monitoring and third-party oversight, with automated evidence collection from your connected tools. Our audit team can advise on how your state's enacted version differs from the model.
Requirements covered
13 sections, with the information security programme in Section 4 (subsections A to I), cybersecurity event investigation in Section 5 and notification duties in Section 6.
Manual NAIC MDL-668 vs. OneClickComply
- Tracking how each state's enacted version differs from the model text
- Gathering evidence for every Section 4 safeguard from separate tools by hand
- Chasing third-party service providers for security assurances in spreadsheets
- Rebuilding records each year to support the 15 February certification
- Struggling to assemble notification details within 72 hours of an event
- Ask an Auditor for guidance on state variations of the model law
- Evidence collected automatically from connected tools and admin consoles
- Vendor risk management keeps third-party oversight records in one place
- Continuously maintained evidence ready to support the annual certification
- A documented incident response plan and logged evidence to support prompt notification
Everything you need for NAIC MDL-668
Control library mapping for MDL-668, available on request
Risk assessment and risk register aligned to Section 4.C
Automated evidence for access, encryption, logging and monitoring safeguards
Vendor risk management for third-party service provider oversight
Incident response plan and policies generated with AutoComplete
Continuous monitoring to support the annual certification statement
Three steps to NAIC MDL-668 compliance
Connect & scan
Connect your cloud, identity and SaaS tools. OneClickComply checks them against NAIC MDL-668 and shows you exactly where you stand.
Fix & generate
OneClickFix remediates technical gaps in one click, and AutoComplete generates NAIC MDL-668-aligned policies from your real environment.
Monitor & evidence
Continuous monitoring keeps you compliant, and our in-house audit team is on hand when you need expert guidance.
NAIC Insurance Data Security Model Law (MDL-668) requirements
All 13 sections of the model law, with the obligation-bearing Sections 4, 5 and 6 broken down into their lettered subsections.
| Reference | Requirement |
|---|---|
| Section 1 | Title |
| Section 2 | Purpose and Intent |
| Section 3 | Definitions |
| Section 4.A | Implementation of an Information Security Program |
| Section 4.B | Objectives of Information Security Program |
| Section 4.C | Risk Assessment |
| Section 4.D | Risk Management |
| Section 4.E | Oversight by Board of Directors |
| Section 4.F | Oversight of Third-Party Service Provider Arrangements |
| Section 4.G | Program Adjustments |
| Section 4.H | Incident Response Plan |
| Section 4.I | Annual Certification to Commissioner of Domiciliary State |
| Section 5.A | Prompt investigation of a cybersecurity event |
| Section 5.B | Investigation steps: nature, scope and containment |
| Section 5.C | Events in systems maintained by third-party service providers |
| Section 5.D | Retention of cybersecurity event records for five years |
| Section 6.A | Notification to the Commissioner |
| Section 6.B | Information to provide to the Commissioner |
| Section 6.C | Notification to Consumers |
| Section 6.D | Notice Regarding Cybersecurity Events of Third-Party Service Providers |
Always check the official NAIC MDL-668 text for the exact wording.
NAIC MDL-668 FAQs
What is the NAIC Insurance Data Security Model Law?
The NAIC Insurance Data Security Model Law, Model #668, is a model act adopted by the National Association of Insurance Commissioners in late 2017. It sets standards for protecting insurance data, requiring licensees to run a risk-based information security programme, oversee third-party service providers, investigate cybersecurity events and notify the insurance commissioner. It only has legal force in states that enact it.
Who must comply with NAIC MDL-668?
Licensees of a state insurance department in a state that has enacted the model law must comply. This includes insurers, producers and other persons licensed, authorised or registered under the state's insurance laws. Licensees with fewer than ten employees, including independent contractors, are exempt from Section 4, and HIPAA-covered licensees with a compliant programme are treated as meeting Section 4.
What does Section 4 of the model law require?
Section 4 requires a comprehensive written information security programme based on a risk assessment and scaled to the licensee's size, complexity and the sensitivity of the information it holds. It covers risk assessment, risk management safeguards such as access controls and encryption, board oversight, third-party service provider oversight, programme adjustments, an incident response plan and annual certification by domiciled insurers.
How quickly must a cybersecurity event be reported?
Under the model text, a licensee must notify the commissioner as promptly as possible and no later than 72 hours after determining that a cybersecurity event has occurred, where the state is its home state or domicile, or 250 or more state residents are affected and certain harm or reporting conditions apply. Enacted state versions can differ, so check your state's statute.
What are the penalties for non-compliance?
The model law leaves penalties to each state: a licensee that violates the Act may be penalised under the state's general insurance penalty statute. The commissioner can also examine and investigate licensees and take action where a violation is suspected. Penalty amounts therefore vary by state, so check the enacted law in each state where you are licensed.
How does MDL-668 relate to ISO 27001 and NIST frameworks?
MDL-668 does not require a specific framework or certification, but its risk-based programme overlaps heavily with ISO 27001 and NIST-based security programmes. Risk assessment, access control, encryption, logging, vendor oversight and incident response all appear in both. A mapped control set lets evidence gathered for ISO 27001 or SOC 2 support MDL-668 obligations too.
What is the annual certification under MDL-668?
Each insurer domiciled in an enacting state must submit a written statement to its commissioner by 15 February each year, certifying compliance with Section 4. Insurers must keep supporting records for five years and document any areas needing material improvement along with the remedial work planned or underway, available for the commissioner to inspect.
Does OneClickComply support NAIC MDL-668?
OneClickComply has mapped NAIC MDL-668 in its control library, and support is available on request rather than live in the product today. Because controls are mapped across frameworks, evidence you collect for ISO 27001, SOC 2 or other standards can count towards MDL-668. OneClickComply does not issue certifications, and your annual certification remains your own statement.
Related standards
All standards- California Consumer Privacy Act (CCPA)Law · US
- Nevada Consumer Health Data and Data Security Law (NRS 603A)Law · US
- Oregon Consumer Information Protection Act (ORS 646A.600 to 646A.628)Law · US
- Texas Data Privacy and Security ActLaw · US
- Tennessee Information Protection ActLaw · US
- Oregon Consumer Privacy ActLaw · US
- Virginia Consumer Data Protection ActLaw · US
- Vermont Data Broker Law (Act 171 of 2018)Law · US
Get NAIC MDL-668 ready, not stressed
Automate controls, gather evidence continuously and stay audit-ready, all on one platform.