POLISCOPE
Back to bills

The civic record

Read. Follow. Verify.
Did Not Advance

Connecticut requires financial institutions to adopt data security safeguards and report security breaches

Original title: AN ACT ESTABLISHING VARIOUS DATA SECURITY REQUIREMENTS APPLICABLE TO CERTAIN FINANCIAL INSTITUTIONS.

Last action · March 24, 2026: File Number 133Sponsors: Travis Simms and 3 others

Introduced
Committee
Floor Vote
Passed
Law

Track this bill to get notified when it advances a stage. One tap to stop, anytime.

What This Bill Proposed

Banks, credit unions, and other financial licensees must adopt written data security safeguard programs and report security breaches to the Department of Banking within three business days, starting October 1, 2026.

Why it matters

Financial institutions face mandatory compliance standards and strict three-day reporting deadlines for cyber incidents that compromise customer data or disrupt operations.

Who It Would Have Affected

Groups the bill's text would have affected, as described in the record. Being affected is not a position for or against it.

Directly affected

Banks and Credit Unions

Banks and credit unions must adopt written data security safeguard programs and submit mandatory incident notifications to the Department of Banking within three business days.

Directly affected

Department of Banking

The department receives and processes data security incident notifications submitted by financial institutions and licensees.

Directly affected

Financial Consumers

Consumers receive enhanced data security safeguards for their personal and financial information, with provisions favoring greater customer protection in case of legal conflicts.

Key Facts

  • Covered financial institutions must adopt a written program setting forth standards for developing, implementing, and maintaining reasonable data security safeguards.
  • Institutions required to adopt security programs include banks, Connecticut credit unions, federal credit unions, out-of-state banks and trust companies with branches in the state, and title 36a and 36b licensees.
  • Licensees, Connecticut banks, and Connecticut credit unions must notify the Department of Banking not later than three business days after knowing or having reason to know of a qualifying data security incident.
  • A qualifying data security incident includes any incident that materially impacts operations, causes significant customer service disruption, or involves unauthorized access to personal information.
Show all 6 facts
  • Where state data security requirements conflict with existing financial records disclosure laws under sections 36a-41 to 36a-44, the provisions affording greater customer protection control.
  • Covered entities must comply with Subtitle A of Title V of the Gramm-Leach-Bliley Financial Modernization Act of 1999 and associated regulations including 12 CFR Part 364 Appendix B, 12 CFR Part 748 Appendix A, and 16 CFR Part 314.

Frequently Asked Questions

Which financial entities must comply with the new data security program rules?
Banks, Connecticut credit unions, federal credit unions, out-of-state banks and trust companies with a local branch or office, title 36a licensees, and persons under the jurisdiction of the commissioner under title 36b.
How quickly must a financial institution report a data security incident to the state?
Licensees, Connecticut banks, and Connecticut credit unions must notify the Department of Banking within three business days after knowing or having reason to know of an incident.
What triggers the mandatory breach notification to the Department of Banking?
Any that may materially impact safe and sound operations, cause significant customer service disruption, or involve unauthorized access to an individual's personal information.

What else do you want to know?

News Coverage

No news coverage found yet. Articles are indexed twice daily.

Where This Stands

This bill did not become law - Died at adjournment · on the House floor.

Procedural history

9 actions
  1. Mar 24, 2026Connecticut General Assembly
    File Number 133
  2. Mar 24, 2026House
    House Calendar Number 113
  3. Mar 24, 2026House
    Favorable Report, Tabled for the Calendar, House
  4. Mar 24, 2026Connecticut General Assembly
    Reported Out of Legislative Commissioners' Office
  5. Mar 18, 2026Connecticut General Assembly
    Referred to Office of Legislative Research and Office of Fiscal Analysis 03/23/26 5:00 PM
  6. Mar 10, 2026Connecticut General Assembly
    Filed with Legislative Commissioners' Office
Show 3 earlier actions
  1. Mar 10, 2026Connecticut General Assembly
    Joint Favorable Substitute
  2. Feb 19, 2026Connecticut General Assembly
    Public Hearing 02/24
  3. Feb 18, 2026Connecticut General AssemblyCommittee
    Referred to Joint Committee on Banking

Version history

Only one version on file - nothing to compare yet. As later stages (committee substitute, engrossed, enrolled) are captured, the redline appears here.

View official text →

Lobbying Activity

No state lobbying filings in our records match this bill. Federal lobbying reports (LDA) cover Congress, so they are not listed on state bills.

Full breakdown

Who this bill affects and the strongest case for and against it, written only from the bill’s own text.

Sponsors

Discoveries

1 pattern noticed across the record

Patterns POLISCOPE noticed across the record. These are observations to investigate, not conclusions.

policy shift95% confidence

Establishment of State-Level Breach Notification Window

The legislation establishes a strict three-day reporting window for financial institutions to notify the Department of Banking of qualifying data security incidents.

Connected Entities

Department of Banking, Banking Committee, Banking Commissioner
OrganizationDepartment of Banking“Receives breach notifications from financial institutions”Map →
OrganizationBanking Committee“Committee reporting substitute bill”Map →
PersonBanking Commissioner“Prescribes form and manner for data security incident notifications”Map →

Sources

Analysis Score

0–100
  • Significance20
    Lowered because this bill did not pass (its text scored 65)
  • Controversy10
    Intensity of disagreement among stakeholders
  • Entertainment5
    Compellingness for a non-policy-wonk reader
  • Buzz25
    Current news / social attention level

Publisher tools

Share or embed this record

POLISCOPE publisher tools

Share or embed this record