# The banking agencies’ 36-hour computer-security incident notification rule, explained

Since May 1, 2022, banking organizations must tell their primary federal regulator within 36 hours of determining that a notification incident has occurred, and bank service providers must alert bank customers about incidents that disrupt covered services for four or more hours.

Explainer · Financial Services · Security & Resilience. Published November 14, 2026. Last reviewed November 14, 2026.

## At a glance

- Joint final rule of the OCC, the Federal Reserve Board and the FDIC, published November 23, 2021 (86 FR 66424). Effective April 1, 2022; compliance required from May 1, 2022.
- Codified at 12 CFR part 53 (OCC), 12 CFR part 225 subpart N (Federal Reserve) and 12 CFR part 304 subpart C (FDIC).
- A banking organization notifies its primary federal regulator as soon as possible and no later than 36 hours after it determines that a notification incident has occurred.
- A bank service provider notifies each affected banking organization customer as soon as possible after it determines that an incident has materially disrupted or degraded, or is reasonably likely to, covered services for four or more hours.
- No form or template. Notice goes by email, telephone or another similar method the agency prescribes.

## Who is covered

The OCC, the Federal Reserve Board and the FDIC issued the rule together, and each agency put the same requirements in its own regulations [1]. Which version applies depends on who supervises the institution:

- **OCC, 12 CFR part 53:** national banks, federal savings associations, and federal branches and agencies of foreign banks.
- **Federal Reserve, 12 CFR part 225 subpart N:** U.S. bank holding companies and savings and loan holding companies, state member banks, the U.S. operations of foreign banking organizations, and Edge and agreement corporations.
- **FDIC, 12 CFR part 304 subpart C:** insured state nonmember banks, insured state-licensed branches of foreign banks, and insured state savings associations [1].

Each version also applies to the bank service providers of those institutions. A bank service provider is a bank service company or other person that performs covered services, meaning services subject to the Bank Service Company Act. Designated financial market utilities are excluded both as banking organizations and as bank service providers [1].

## Two definitions decide whether the clock starts

A **computer-security incident** is an occurrence that results in actual harm to the confidentiality, integrity or availability of an information system or the information it processes, stores or transmits. Not every such incident has to be reported. The duty to notify the regulator applies to a **notification incident**: a computer-security incident that has materially disrupted or degraded, or is reasonably likely to materially disrupt or degrade, a banking organization’s

- ability to carry out banking operations, activities or processes, or to deliver banking products and services to a material portion of its customer base, in the ordinary course of business;
- business lines, including associated operations, services, functions and support, whose failure would result in a material loss of revenue, profit or franchise value; or
- operations, including associated services, functions and support, whose failure or discontinuance would pose a threat to the financial stability of the United States [1].

The 36 hours run from the moment the banking organization determines that a notification incident has occurred, not from when the incident began [1] [2]. In our view, that makes the determination itself a step worth defining in advance: who makes it, on what information, and how it is recorded. That is a practice point, not a requirement of the rule.

### The agencies’ examples

The preamble gives a non-exhaustive list of incidents that generally count as notification incidents [1]:

- a large-scale distributed denial of service attack that disrupts customer account access for an extended period, for example more than four hours;
- a bank service provider used for the core banking platform suffering widespread outages with no determinable recovery time;
- a failed system upgrade or change that causes widespread outages for customers and employees;
- an unrecoverable system failure that triggers the business continuity or disaster recovery plan;
- a hacking incident that disables banking operations for an extended period;
- malware that poses an imminent threat to core business lines or critical operations, or that forces the bank to disconnect affected systems from the internet;
- a ransom malware attack that encrypts a core banking system or backup data.

Several of these are not attacks at all. A failed upgrade or an unrecoverable system failure can qualify, because the definition turns on harm to availability and the effect on operations. The preamble says the rule requires banks to consider, case by case, whether a significant incident is a notification incident, and the agencies encourage a bank in doubt to contact its regulator [1].

## What the bank’s notice contains

The agencies describe the notice as an early alert. No specific information is required other than that a notification incident has occurred, and the rule prescribes no form or template. The agencies expect banks to share general information about what is known at the time, and the notices are subject to the agencies’ confidentiality rules [1]. Under the OCC’s version, notice goes to the appropriate OCC supervisory office or an OCC-designated point of contact by email, telephone or another similar method the OCC prescribes [2] [3]. The agencies left room for other methods, noting that an incident could affect a communication channel [1].

## The service provider’s duty

A bank service provider must notify at least one bank-designated point of contact at each affected banking organization customer as soon as possible when it determines that it has had a computer-security incident that has materially disrupted or degraded, or is reasonably likely to materially disrupt or degrade, covered services provided to that bank for four or more hours [2].

- The bank-designated point of contact is an email address, phone number or other contact the bank has given the provider.
- If the bank has not given one, the provider must notify the bank’s chief executive officer and chief information officer, or two people with comparable responsibilities, by any reasonable means.
- Scheduled maintenance, testing or software updates that were communicated to the bank in advance do not trigger the duty [2].

The rule text requires the provider to notify its bank customers; it does not require the provider to notify the regulators [2]. The provider’s notice is one way a bank learns of an incident that may be a notification incident for the bank itself, and the agencies’ examples include a core platform provider with widespread outages [1]. In our view, that gives banks a reason to keep their designated contacts current with every provider that performs covered services.

## How it differs from customer breach notice

This rule is about telling a supervisor that operations are disrupted. It is separate from rules that require notice to affected individuals. Regulation S-P, for example, applies to broker-dealers, investment companies, SEC-registered investment advisers and registered transfer agents, and requires notice to individuals within 30 days and a 72-hour breach notice from service providers [4]. A banking group with such an affiliate may need both processes, and the triggers differ: one is material disruption of banking operations, the other is unauthorized access to customer information.

## Dates

The rule was published on November 23, 2021, took effect on April 1, 2022 and has required compliance since May 1, 2022 [1]. In the eCFR version dated November 12, 2026 (checked November 14, 2026), the OCC’s notification and service provider sections still read as adopted [2]. The OCC’s bulletin notes that the rule applies to community banks [3].

This explainer describes the rule; it is not legal advice, and institutions should confirm with counsel how it applies to them. The steps a bank takes to be ready are in the companion [36-hour incident notice checklist](https://insights.moraph.com/checklist-bank-36-hour-computer-security-incident-notice).

Moraph’s teams help organizations with work like this. [See our solutions](https://www.moraph.com/solutions).

## Sources

1. OCC, Federal Reserve Board and FDIC, Federal Register (via GovInfo). Computer-Security Incident Notification Requirements for Banking Organizations and Their Bank Service Providers (final rule, 86 FR 66424). <https://www.govinfo.gov/content/pkg/FR-2021-11-23/html/2021-25510.htm> Checked November 14, 2026.
2. Electronic Code of Federal Regulations. 12 CFR part 53, Computer-Security Incident Notification. <https://www.ecfr.gov/current/title-12/chapter-I/part-53> Checked November 14, 2026.
3. Office of the Comptroller of the Currency. OCC Bulletin 2021-55, Computer-Security Incident Notification: Final Rule. <https://www.occ.gov/news-issuances/bulletins/2021/bulletin-2021-55.html> Checked November 14, 2026.
4. Securities and Exchange Commission, Federal Register (via GovInfo). Regulation S-P: Privacy of Consumer Financial Information and Safeguarding Customer Information (final rule, 89 FR 47688). <https://www.govinfo.gov/content/pkg/FR-2024-06-03/html/2024-11116.htm> Checked November 14, 2026.

Published: November 14, 2026
Canonical URL: <https://insights.moraph.com/bank-computer-security-incident-notification-rule-explained>
Publisher: Moraph Insights
