0
Skip to content

California DFPI Urges Rapid 48-Hour Cyber Incident Reporting

California’s DFPI is pushing for early notification of cyberattacks within 48 hours — prioritizing rapid awareness over complete forensic reports. Here’s what triggers a reportable event and how to update your response protocols.

09/14/2026 12:00 P.M.

As cyber threats grow more frequent and sophisticated and continue to target the financial sector, regulatory oversight is shifting toward rapid detection.

California’s Department of Financial Protection and Innovation (DFPI) has established reporting guidelines and a Cybersecurity Incident Report portal to encourage regulated entities to report cyber events as early as possible.

For debt collectors, banks, credit unions, and other DFPI-regulated entities operating in California, understanding these reporting expectations is vital for risk management and compliance.

The DFPI’s reporting mechanism prioritizes rapid notification, according to a recent announcement about the notification procedures. The regulator encourages entities that experience a reportable cyber incident — or have reason to believe one occurred — to submit an incident report within 48 hours, or as soon as possible, provided the event has a nexus to California operations.

The DFPI does not require a detailed, fully completed forensic assessment at the initial filing. The priority is early awareness so that containment steps can be taken to safeguard data, critical infrastructure, and consumer trust.

It defines a reportable incident across several categories of substantial operational disruption, unauthorized exposure, or compromise.

Key trigger scenarios include:

  • Ransomware & System Compromise: Attacks impacting critical systems or resulting in the destruction or alteration of client, member, or financial data.
  • Unauthorized Access & Exfiltration: Intrusions that grant network access, system misconfigurations that expose sensitive data, or exfiltration of sensitive client/employee PII off-network.
  • DDoS & Disruption: Distributed Denial of Service attacks or major phishing incidents causing significant business downtime.
  • Third-Party/Vendor Breaches: Notifications from critical vendors or software providers that client/member data has been compromised.
  • Social Engineering & Insider Threats: Phishing or social engineering leading to fraudulent fund transfers, internal actor compromises, or the physical loss/theft of unencrypted devices.

Concurrent Reporting for Federally Regulated Entities

If your organization is already subject to federal incident reporting rules, the DFPI expects you to promptly submit a copy/report to the state portal as well. Dual reporting ensures state regulators remain aligned with federal counterparts during major systemic threats.

Steps to Prepare Your Incident Response Plan

  • Update Incident Response Playbooks: Ensure your IT and compliance protocols explicitly list the DFPI as a required regulatory notification, alongside federal agencies and legal counsel.
  • Train Vendor Oversight Teams: Vendor breaches count as reportable events. Ensure your third-party risk management processes include fast-turnaround escalation rules when a vendor discloses a security event.
  • Know How to File: Access the official portal via the DFPI’s website (dfpi.ca.gov/regulated-industries/report-a-cybersecurity-incident/).

For questions or follow-up communications on submitted reports, companies can reach out directly to Ask.DFPI@dfpi.ca.gov.

Remember, subscribe to ACA Daily and Member Alerts under your My ACA Assistant profile when logged in to acainternational.org.

If you have executive leadership updates or other member news to share with ACA, contact our communications department at comm@acainternational.org. View our publications page for more information and our news submission guidelines here.

One moment please...

Share Profile

This site utilizes cookies as included in our Privacy Policy and User Agreement.