Incident to report to a regulator?Incident to report? Intake Line

Federal legislative rule / regulation · United States

12 CFR 53, 225, 304: Computer-Security Incident Notification Rule

The joint OCCOffice of the Comptroller of the Currency, Federal Reserve and FDICFederal Deposit Insurance Corporation requirements require the appropriate regulator to receive notification as soon as possible and within 36 hours after a banking organisation determines that a notification incident has occurred.

  • 36 hours to notify the regulator after determination
  • 4 hours disruption that triggers a service provider notice

Last updated 15 November 2026

What Is 12 CFR 53, 225, 304?

It promotes timely notification of computer-security incidents that may materially and adversely affect supervised banking organisations, so that the agencies get early warning of significant incidents.

Full title
Computer-Security Incident Notification Requirements for Banking Organizations and Their Bank Service Providers (12 CFR 53, 225, 304)
Official reference
Computer-Security Incident Notification Requirements for Banking Organizations and Their Bank Service Providers, final rule, 86 FR 66424 (23 November 2021); 12 CFR Part 53 (OCC); 12 CFR Part 225, Subpart N (Federal Reserve Board); 12 CFR Part 304, Subpart C (FDIC)
Type
Federal legislative rule / regulation
Issued by
Office of the Comptroller of the Currency, Board of Governors of the Federal Reserve System and Federal Deposit Insurance Corporation
In force
1 April 2022
Applies from
1 May 2022
Status
In force
Countries
United States

Get regulatory updates

One email a week when something changes in the countries you choose, 12 CFR 53, 225, 304 included.

Countries
United States

Pick one or more

One email a week, only when something changed. Each email has an unsubscribe link. Privacy notice

What 12 CFR 53, 225, 304 Requires

12 CFRCode of Federal Regulations 53.2(b)(4) and (7), 225.301(b)(4) and (7) and 304.22(b)(4) and (7)

Classify Notification Incidents

A notification incident is an occurrence causing actual harm to the confidentialityThe information-security property of keeping information from being disclosed to people, organisations or systems that are not authorised to receive it. Access restrictions and encryption help preserve confidentiality when information is stored, sent or processed. It concerns who can see information; it does not by itself ensure that the information is accurate or that a service remains available., integrity or availabilityThe information-security property that authorised people and systems can access and use information or services when needed, reliably and within an acceptable time. An outage or an attack that overwhelms a service can reduce availability even if no information is stolen or changed. In product security, this includes keeping essential functions accessible and usable. of an information system or its information that materially disrupts or degrades, or is reasonably likely to materially disrupt or degrade: banking operations or service delivery to a material portion of customers; business lines whose failure causes material loss of revenue, profit or franchise value; or operations whose failure threatens United States financial stability.

12 CFR 53.3, 225.302, 304.23

Ensure the Regulator Receives Notification Within 36 Hours

Ensure that the appropriate federal regulator receives notification as soon as possible and no later than 36 hours after the banking organisation determines that a notification incident has occurred. The clock starts at that determination, rather than at initial detection of every computer-security incident.

12 CFR 53.4(a), 225.303(a), 304.24(a)

Notify Affected Banking Customers Promptly

When the provider determines that a computer-security incident has materially disrupted or degraded, or is reasonably likely to materially disrupt or degrade, covered services for four or more hours, notify at least one designated contact at each affected banking organisation customer as soon as possible. Four hours is the service-disruption threshold, not a notification deadline or a period to wait before notifying.

Latest 12 CFR 53, 225, 304 Updates

12 CFR 53, 225, 304 Milestones Since 2021
  1. Compliance required
  2. Effective
  3. Final rule published86 FR 66424.

Can you notify within 36 hours?

Thirty minutes with a GRC+ consultant: we look at how you decide on notification incidents and what your service providers must tell you.

Loading the form…