Tracker · re-checked monthly
State privacy laws, and the security each one requires.
The nineteen comprehensive state privacy laws listed here are in force, and four more arrive by 2028. Nearly all require reasonable data security, written processor contracts and, for risky processing, documented assessments. Each row below was checked against the statute or the state's own guidance, last on November 19, 2026.
Last verified November 19, 2026
Laws in force
| State | Law | In force | Who is covered | Security duty | Assessments | Enforcement |
|---|---|---|---|---|---|---|
| California | CCPA as amended (Civ. Code §1798.100 et seq.) and CPPA regulations | In force; risk-assessment rules from Jan 1, 2026; cybersecurity audit certifications due Apr 1 of 2028, 2029 or 2030 by revenue | Revenue over $26,625,000 (2025 adjustment), or 100,000+ consumers or households, or 50%+ of revenue from selling or sharing data | Reasonable security appropriate to the information (§1798.100(e), §1798.81.5) | Risk assessments; cybersecurity audits for higher-risk businesses | CPPA and Attorney General |
| Virginia | VCDPA (Va. Code §59.1-575 et seq.) | Jan 1, 2023 | 100,000 consumers, or 25,000 plus over 50% of revenue from data sales | Reasonable administrative, technical and physical practices (§59.1-578(A)(3)) | Yes (§59.1-580) | AG; 30-day cure |
| Colorado | Colorado Privacy Act (C.R.S. §6-1-1301 et seq.) | Jul 1, 2023 | 100,000 consumers, or 25,000 plus revenue or discounts from data sales | Reasonable measures to secure data (§6-1-1308(5)); processors must apply risk-appropriate security (§6-1-1305(4)) | Yes (§6-1-1309) | AG and district attorneys; cure period ended Jan 1, 2025 |
| Connecticut | CTDPA (Conn. Gen. Stat. §42-515 et seq.) | Jul 1, 2023; amendments Jul 1, 2026 | From Jul 1, 2026: 35,000 consumers, or any sensitive data, or any sale of data | Reasonable data security safeguards (§42-520) | Yes; profiling impact assessments for processing from Aug 1, 2026 | AG; cure period ended Jan 1, 2025 |
| Utah | UCPA (Utah Code §13-61-101 et seq.) | Dec 31, 2023 | $25M+ revenue and 100,000 consumers, or 25,000 plus over 50% of revenue from data sales | Reasonable administrative, technical and physical practices (§13-61-302(2)) | No | Division of Consumer Protection and AG; 30-day cure |
| Texas | TDPSA (Bus. & Com. Code ch. 541) | Jul 1, 2024 | No count threshold; SBA small businesses exempt except for selling sensitive data without consent | Reasonable data security practices (Texas AG summary) | Yes | AG only; 30-day cure (§541.154) |
| Oregon | OCPA (ORS 646A.570–646A.589) | Jul 1, 2024 (nonprofits Jul 1, 2025) | 100,000 consumers, or 25,000 plus 25%+ of revenue from data sales | Safeguards as required by ORS 646A.622 (ORS 646A.578(1)(c)) | Yes (ORS 646A.586) | AG; cure period ended Jan 1, 2026 |
| Montana | MCDPA (MCA §30-14-2801 et seq.) | Oct 1, 2024 | 25,000 consumers, or 15,000 plus over 25% of revenue from data sales | Reasonable administrative, technical and physical practices (§30-14-2812(1)(b)) | Yes (§30-14-2814) | AG; no cure provision in the current text |
| Iowa | ICDPA (Iowa Code ch. 715D) | Jan 1, 2025 | 100,000 consumers, or 25,000 plus over 50% of revenue from data sales | Reasonable administrative, technical and physical practices (§715D.4(1)) | No | AG; 90-day cure |
| Delaware | DPDPA (6 Del. C. ch. 12D) | Jan 1, 2025; lower thresholds from Jan 1, 2027 | 35,000 consumers, or 10,000 plus over 20% of revenue from data sales (10,000 or 5,000 from 2027) | Reasonable administrative, technical and physical practices (§12D-106(a)(3)) | Yes, at 100,000+ consumers (50,000 from 2027) | Department of Justice; mandatory cure ended Dec 31, 2025 |
| New Hampshire | RSA 507-H | Jan 1, 2025 | 35,000 consumers, or 10,000 plus over 25% of revenue from data sales | Practices appropriate to the volume and nature of the data (507-H:6, I(c)) | Yes (507-H:8) | AG; mandatory cure ended Dec 31, 2025 |
| New Jersey | N.J.S.A. 56:8-166.4 et seq. | Jan 15, 2025 | 100,000 consumers, or 25,000 plus revenue or discounts from data sales | Reasonable security practices (56:8-166.12(a)(3)); processor contracts must include security measures | Yes | AG; cure period ended Jul 1, 2026 |
| Nebraska | Neb. Rev. Stat. 87-1101 to 87-1130 | Jan 1, 2025 | Businesses that are not federally defined small businesses and that process or sell personal data | Reasonable practices (87-1112(1)(b)) | Yes | AG; 30-day cure |
| Tennessee | Tennessee Information Protection Act (Tenn. Code Ann. 47-18-3201 et seq.) | Jul 1, 2025 | Over $25M revenue and 175,000 consumers, or 25,000 plus 50%+ of revenue from data sales | Data security practices required (47-18-3204) | Yes | AG; 60-day cure; a privacy program conforming to the NIST privacy framework is a defense |
| Minnesota | MCDPA (Minn. Stat. 325M.10–325M.21) | Jul 31, 2025 | 100,000 consumers, or 25,000 plus over 25% of revenue from data sales; small businesses largely exempt | Reasonable security plus a data inventory (325M.16, subd. 2) | Yes (325M.18) | AG; cure period ended Jan 31, 2026 |
| Maryland | MODPA (Com. Law §14-4601 to §14-4614) | Oct 1, 2025 (not applied to processing before Apr 1, 2026) | 35,000 consumers, or 10,000 plus over 20% of revenue from data sales | Reasonable security (§14-4607(b)(1)(ii)); processor contracts must include security | Yes, including for algorithms (§14-4610) | Consumer Protection Division; optional cure through Apr 1, 2027 |
| Indiana | Indiana Consumer Data Protection Act (IC 24-15) | Jan 1, 2026 | 100,000 residents, or 25,000 plus over 50% of revenue from data sales | See IC 24-15 | See IC 24-15 | AG |
| Kentucky | KRS 367.3611–367.3629 | Jan 1, 2026 | 100,000 consumers, or 25,000 plus over 50% of revenue from data sales | Reasonable practices (367.3617(1)(c)) | Yes, for processing from Jun 1, 2026 | AG; 30-day cure |
| Rhode Island | R.I. Gen. Laws ch. 6-48.1 | Jan 1, 2026 | 35,000 customers, or 10,000 plus over 20% of revenue from data sales | Reasonable safeguards for data processed under 6-48.1-7(s) | Yes | AG; no cure period |
Enacted, not yet in force
| State | Law | Effective | Who is covered | Security duty | Assessments | Enforcement |
|---|---|---|---|---|---|---|
| Louisiana | Act 502 of 2026 (R.S. 51:1780.1–1780.5) | Jan 1, 2027 | Over $25M revenue, 75,000+ consumers, households or devices, or 50%+ of revenue from data sales | R.S. 51:1780.4(A)(1)(b) | Yes | AG; 30-day cure through July 2027 |
| Oklahoma | SB 546 (2026) | Jan 1, 2027 | Over 100,000 consumers, or 25,000 plus a majority of revenue from data sales | Required | — | AG |
| Alabama | HB 351 (2026) | May 1, 2027 | Over 25,000 consumers, or over 25% of revenue from data sales | §7(a)(2) | No | AG; 45-day cure; up to $15,000 per violation |
| Vermont | Act 145 of 2026 (9 V.S.A. §2415a–2415k) | Jan 1, 2028 | 35,000 consumers, or 3,000 for sensitive data or data sales | §2415e(a)(3) | Yes (§2415g) | AG; 60-day cure through Jun 30, 2029 |
Thresholds are counts of state residents whose data is processed in a year, as each law defines them. Most laws exempt some entities, such as HIPAA- or GLBA-regulated organizations and nonprofits; check the statute.
Where ISO/IEC 27001 fits
- One program, many states. The security duties are written in similar terms: reasonable administrative, technical and physical practices scaled to the data. One risk-based information security management system answers all of them, instead of a policy per state.
- Evidence, not just policy. An ISO/IEC 27001 certificate shows an independent auditor has checked that the controls operate. That is useful when an Attorney General, a customer or an insurer asks what "reasonable" meant in practice.
- Processors under control. Supplier security, confidentiality terms and flow-down to subcontractors map to Annex A controls 5.19 to 5.22, with each processor contract checked.
- Assessments with a home. Privacy assessments and the ISMS risk assessment can share one method and one register; ISO/IEC 27701 extends the system to privacy.
Estimate the audit with our ISO 27001 audit days calculator, budget with the ISO 27001 cost guide, and check the standard's status on Is ISO 27001 being revised?
Free tools and downloads
- ISO 27001 audit days calculatorA realistic range of ISO 27001 audit days for each audit in the cycle, built site by site.
- ISO 27001 internal audit toolkit52 ISMS checks for clauses 4 to 10 and Annex A sampling for all 93 controls, linked to your SoA.
- Is ISO 27001 being revised?The 2022 edition, its 2024 climate amendment and when ISO's next review is due.
Common questions
Does any state privacy law require ISO 27001 certification?
No. None of the laws on this page requires ISO/IEC 27001. Most require reasonable administrative, technical and physical data security practices, scaled to the volume and sensitivity of the data. An ISO/IEC 27001 information security management system is a well-documented way to show those practices exist, are risk-based and are checked by an independent auditor.
How many states have comprehensive privacy laws?
Nineteen state laws are in force on this page as of November 19, 2026, and four more take effect between January 2027 and January 2028 (Louisiana, Oklahoma, Alabama and Vermont). Many other states have breach-notification and sector laws that are not listed here.
What do processor contracts have to say?
Almost every law requires a contract between the controller and each processor, with a duty of confidentiality for everyone handling the data and help with security and breach obligations. Colorado, New Jersey, Minnesota and Maryland go further on security in the processor relationship. In an ISMS that is supplier security (Annex A 5.19 to 5.22), with the contract terms checked per supplier.
What is a data protection assessment, and does ISO 27001 cover it?
Most of these laws require a documented assessment before high-risk processing such as targeted advertising, selling data, profiling or sensitive data. It weighs benefits against risks to consumers. An ISO/IEC 27001 risk assessment covers security risk to the organization; a privacy assessment needs the consumer-harm view as well. ISO/IEC 27701, the privacy extension, bridges the two.
Sources
- California Privacy Protection Agency — CCPA regulations, risk assessments and cybersecurity audits.
- Code of Virginia, ch. 53 — VCDPA.
- Colorado Attorney General, Colorado Privacy Act — statute and rules.
- Connecticut Attorney General, CTDPA — obligations and 2026 amendments.
- Utah Code ch. 13-61 — UCPA.
- Texas Attorney General, TDPSA — applicability, duties and enforcement.
- Oregon DOJ, privacy — OCPA.
- Montana Code, Title 30, ch. 14, part 28 — MCDPA.
- Iowa Code ch. 715D — ICDPA.
- Delaware Code, Title 6, ch. 12D — DPDPA and its 2027 changes.
- New Hampshire RSA 507-H — statute.
- New Jersey Division of Consumer Affairs, data privacy FAQ — and P.L.2023, c.266.
- Nebraska LB 1074 — Data Privacy Act.
- Tennessee Attorney General — Tennessee Information Protection Act.
- Minnesota Statutes ch. 325M — MCDPA.
- Maryland Chapter 454 (HB 567), 2024 — MODPA.
- Indiana Attorney General — Consumer Data Protection Act summary.
- Kentucky Revised Statutes — KRS 367.3611 to 367.3629.
- Rhode Island General Laws ch. 6-48.1 — statute.
- Louisiana Act 502 (2026) — enacted text.
- Oklahoma House — SB 546.
- Alabama HB 351 (2026), enrolled — text.
- Vermont Act 145 (2026) — as enacted.
Changelog
- 2026-11-19 — Published. Nineteen laws in force and four enacted for 2027–2028, each checked against statute text, the Attorney General or the state privacy agency on November 19, 2026.
Information, not legal advice. Confirm how a law applies to you with counsel.