# Checklist: getting a bank ready to make the 36-hour computer-security incident notice

Eleven steps for banks, holding companies and their bank service providers under the joint OCC, Federal Reserve and FDIC rule: deciding what counts, starting the clock, reaching the regulator, and making providers tell you when covered services go down.

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

## Three rules with one text

The OCC (12 CFR part 53), the Federal Reserve (12 CFR part 225, subpart N) and the FDIC (12 CFR part 304, subpart C) adopted the same requirements in a joint final rule published on November 23, 2021, effective April 1, 2022, with compliance from May 1, 2022 [1] [2] [3] [4]. Each part covers the organizations its agency supervises: national banks, federal savings associations and federal branches and agencies of foreign banks for the OCC; bank and savings and loan holding companies, state member banks, the U.S. operations of foreign banking organizations and Edge and agreement corporations for the Federal Reserve; insured state nonmember banks, insured state-licensed branches of foreign banks and insured state savings associations for the FDIC. Each also binds bank service providers.

## Using the steps

Each step names the work, who usually owns it and the section behind it. Citations use the OCC’s section numbers; the matching Federal Reserve and FDIC sections are 225.300 to 225.303 and 304.21 to 304.24. Where a step draws on the agencies’ explanation in the preamble to the rule, or is our suggestion, it says so. This page explains the rule; it is not legal advice.

## The checklist

1. **List each legal entity in the group and the part it falls under, so a holding company and its bank subsidiary each know which regulator they notify.** (Regulatory compliance with legal) The scope paragraphs, section 53.1(c), section 225.300(c) and section 304.21(c), each name the organizations covered [1] [2] [3]. A holding company under the Federal Reserve’s subpart and a bank under the OCC’s or FDIC’s part have separate duties to their own regulator.
2. **Write the two definitions into the incident procedure: a computer-security incident causes actual harm; a notification incident is one that materially disrupts or degrades, or is reasonably likely to, the organization’s operations in the ways the rule lists.** (CISO with operational risk) Section 53.2(b)(4) and (7). The three tests are the ability to carry out banking operations, activities or processes, or deliver banking products and services, to a material portion of the customer base; business lines whose failure would cause a material loss of revenue, profit or franchise value; and operations whose failure would threaten U.S. financial stability [1].
3. **Name in advance the business lines and operations that meet the second and third tests, so triage does not start from a blank page.** (Operational risk with business line heads) Our suggestion for applying section 53.2(b)(7)(ii) and (iii) quickly [1]. The preamble says organizations must consider case by case whether a significant incident is a notification incident [4].
4. **Put the agencies’ seven examples of notification incidents into the triage playbook.** (Incident response lead) The preamble gives them as a non-exhaustive list of incidents generally considered notification incidents: large-scale distributed denial of service attacks that disrupt customer account access for an extended period (for example, more than 4 hours); a core banking provider outage with undeterminable recovery time; a failed upgrade or change causing widespread outages; an unrecoverable failure that activates business continuity or disaster recovery plans; a hacking incident disabling operations for an extended period; malware posing an imminent threat to core business lines or critical operations, or requiring the systems that support them to be disconnected from the internet; and ransomware that encrypts a core banking system or backup data [4].
5. **Name who determines that a notification incident has occurred, and log the time of that decision.** (CIO or CISO, with the incident committee) Section 53.3 requires the agency to receive notice as soon as possible and no later than 36 hours after the organization determines that a notification incident has occurred [1]. The preamble confirms the clock starts at that determination and accepts that an organization needs a reasonable amount of time to reach it [4]. A logged decision time is our suggestion so the deadline can be shown.
6. **Record the regulator’s point of contact and at least two ways to reach it, one of which does not depend on the organization’s own email.** (Regulatory relations) Section 53.3 allows notice by email, telephone or other similar methods the agency prescribes, to the supervisory office or a designated point of contact [1]. The preamble notes commenters’ concern that an incident could affect normal communication channels [4]; keeping an alternative channel is our suggestion.
7. **Prepare a short notice script that says a notification incident has occurred and what is known so far.** (Regulatory compliance) The preamble describes the notice as an early alert: no specific information is required beyond the fact that a notification incident has occurred, there is no form or template, and the notice and related information fall under the agencies’ confidentiality rules [4].
8. **Tell decision makers that when in doubt they should call the regulator.** (CISO and Chief Risk Officer) The preamble encourages an organization in doubt to contact its regulator, and says the agencies generally do not expect to take supervisory action when a notice is filed on a mistaken determination [4].
9. **List the bank service providers that perform covered services, and give each one a bank-designated point of contact.** (Third-party risk management) Covered services are those subject to the Bank Service Company Act, under section 53.2(b)(5). Section 53.4(a)(1) and (2) has providers notify the point of contact the bank gave them, or, if none was given, the CEO and CIO or two people of comparable responsibility [1]. Recording the contact in writing with each provider is our suggestion.
10. **Check that provider contracts and onboarding reflect the provider’s duty to notify as soon as possible when an incident has disrupted or degraded, or is reasonably likely to disrupt or degrade, covered services for four or more hours.** (Procurement and legal) Section 53.4(a) sets the duty; section 53.4(b) excludes scheduled maintenance, testing or software updates communicated in advance [1]. The preamble records commenters’ view that existing contracts would need amending [4]; reviewing them is our suggestion.
11. **If the organization itself provides covered services to other banks, set up its own process to notify each affected bank customer.** (Incident response lead at the provider) Section 53.4 applies to bank service companies and any other person that performs covered services, and the scope paragraphs of all three parts extend to bank service providers [1] [2] [3].

## Sources

1. Electronic Code of Federal Regulations. 12 CFR part 53, Computer-Security Incident Notification (OCC; current text, checked November 14, 2026). <https://www.ecfr.gov/current/title-12/part-53> Checked November 14, 2026.
2. Electronic Code of Federal Regulations. 12 CFR part 225, subpart N, Computer-Security Incident Notification (Federal Reserve; current text, checked November 14, 2026). <https://www.ecfr.gov/current/title-12/part-225/subpart-N> Checked November 14, 2026.
3. Electronic Code of Federal Regulations. 12 CFR part 304, subpart C, Computer-Security Incident Notification (FDIC; current text, checked November 14, 2026). <https://www.ecfr.gov/current/title-12/part-304/subpart-C> Checked November 14, 2026.
4. OCC, Federal Reserve and FDIC, Federal Register (via GovInfo). Computer-Security Incident Notification Requirements for Banking Organizations and Their Bank Service Providers (final rule, 86 FR 66424, November 23, 2021). <https://www.govinfo.gov/content/pkg/FR-2021-11-23/html/2021-25510.htm> Checked November 14, 2026.

Published: November 14, 2026
Canonical URL: <https://insights.moraph.com/checklist-bank-36-hour-computer-security-incident-notice>
Publisher: Moraph Insights
