Financial Services · Security & Resilience
Financial Services: security and resilience
What to know now
Each number links to the point's source. Points checked unless the point shows another date.
- Under the OCC, Federal Reserve and FDIC rule of November 2021 (compliance from May 1, 2022), a banking organization must notify its primary federal regulator as soon as possible and no later than 36 hours after determining that a notification incident has occurred. A bank service provider must notify each affected banking organization customer as soon as possible when an incident has caused, or is reasonably likely to cause, a material service disruption or degradation for four or more hours.1
- Since September 1, 2023, a federally insured credit union must report a reportable cyber incident to the NCUA as soon as possible and within 72 hours of reasonably believing it has occurred. The first report does not need a detailed incident assessment.2
- The SEC's Regulation S-P amendments, published June 3, 2024, require broker-dealers, investment companies, registered investment advisers, funding portals and transfer agents to keep an incident response program and to notify affected individuals as soon as practicable, but not later than 30 days, after becoming aware of unauthorized access to or use of customer information. Larger entities had 18 months and smaller entities 24 months from publication to comply.3
- In a statement the OCC issued to banks on August 29, 2024, the FFIEC said it would sunset the Cybersecurity Assessment Tool and remove it from its website on August 31, 2025.4
- In a bulletin dated September 21, 2026, the OCC said it had updated the structure of its Cybersecurity Supervision Work Program to align with the updated NIST Cybersecurity Framework categories and subcategories. No procedures were added or changed. The OCC encourages, but does not require, a standardized approach to assessing cybersecurity preparedness.5
- FinCEN guidance of June 12, 2026 clarifies when financial institutions can share information about suspected fraud under the section 314(b) safe harbor. The Federal Reserve highlighted it in SR 26-3 on July 9, 2026. Participation is voluntary.6
License: CC BY 4.0. Underlying government texts are public domain or under their own terms. Attribute "Moraph Insights" with a link to the page.
Sources
- Office of the Comptroller of the Currency; Board of Governors of the Federal Reserve System; Federal Deposit Insurance Corporation. Computer-Security Incident Notification Requirements for Banking Organizations and Their Bank Service Providers (final rule). Checked .
- National Credit Union Administration. Cyber Incident Notification Requirements for Federally Insured Credit Unions (final rule). Checked .
- Securities and Exchange Commission. Regulation S-P: Privacy of Consumer Financial Information and Safeguarding Customer Information (final rule). Checked .
- Office of the Comptroller of the Currency. OCC Bulletin 2024-25, Cybersecurity: FFIEC Cybersecurity Assessment Tool Sunset Statement. Checked .
- Office of the Comptroller of the Currency. OCC Bulletin 2026-48, Cybersecurity: Cybersecurity Supervision Work Program. Checked .
- Board of Governors of the Federal Reserve System. SR 26-3, Guidance Clarifying Fraud-Related Information Sharing Under Section 314(b) of the USA PATRIOT Act. Checked .
How we source and check every fact: Editorial standards · Corrections
Last reviewed .
Spotted an error? Tell us and we will check it and correct the page where needed.
Looking Back
Week of August 31, 2026
Bank cyber gaps now arrive as observations the board never has to see
Two bank regulators narrowed formal findings to problems that threaten material financial harm, a year after a shared cyber checklist was retired. Many cyber weaknesses will now arrive as informal observations, so banks must decide for themselves what reaches the board.
Week of May 18, 2026
Searching by balance: how bribed bank insiders choose their targets
Bank insider cases prosecuted in 2026 show bribed employees selling three things: the search that finds wealthy customers, the screens that expose them, and the overrides that open doors. A bank can control all three without first catching the insider.
Week of April 6, 2026
When AI made flaws cheap to find, banks’ patch queues set the pace
An AI model that could find serious software flaws prompted a meeting with bank chief executives. A bank’s test was how fast it could install the fixes that would follow.
Week of March 2, 2026
Iran’s war tested banks’ decision rights more than their defenses
After the strikes on Iran, the cyber warnings named old tricks banks already knew how to stop. The harder test was judgment under pressure: what to fix first, who could override a change freeze, and what to ask of the providers banks depend on.
Week of June 16, 2025
Why Scattered Spider’s turn to insurers should have set a deadline for the rest of finance
A hacking group known for working through one industry at a time reached U.S. insurers in June 2025, and a warning became a deadline. Financial firms needed a pre-agreed surge mode: a clear trigger, tighter help-desk rules and containment planned around stolen identities.
Week of April 7, 2025
Supervisory correspondence: a bank’s most candid file, held in a system it cannot assess
The OCC’s email breach showed that a bank’s most candid account of its own weaknesses sits with a regulator it can neither audit nor replace. Banks still control what they write, how it travels and how they respond when the holder is breached.
Week of February 17, 2025
Bybit’s signers approved what their screens showed, which was not what they signed
The largest crypto theft on record beat a multi-person approval process without breaking it: attackers simply changed what the approvers saw on screen. Any bank approving payments through software carries the same risk at four points, from how the screen is built to recovery.
Week of October 14, 2024
NYDFS wrote no AI rule, and made AI risk part of what the CEO certifies
New York’s October 2024 letter on AI and cybersecurity added no new rules. Because the CEO and security chief already sign a yearly compliance certification, though, it turned four AI risks into evidence those executives must be able to show.
Week of February 12, 2024
Convincing faces, unauthenticated seats: the Hong Kong deepfake was a meeting-identity failure
A video call with a familiar, fake face persuaded one employee to send about US$25 million. The fraud beat a meeting, not a payment system. Banks need controls at the invitation, inside the meeting and at the handoff to money.
Week of November 6, 2023
Three seats at ICBC’s ransomware attack, and the plan each one needed
Ransomware hit ICBC’s U.S. broker-dealer in November 2023, and Treasury trades still had to settle that day. Every firm in the market could have been sitting in any of three seats, and each seat needed its own plan, written well before the crisis.
All 22 Looking Back articles in Financial Services and Security & Resilience
Explainers, checklists and data
Explainer · November 14, 2026
SEC Regulation SCI: entities, systems, event notices and the withdrawn 2023 expansion, explained
Regulation SCI sets technology resilience, change and incident-notice duties for exchanges, large ATSs, clearing agencies and other market infrastructure. A 2023 proposal to widen it to some broker-dealers was formally withdrawn in June 2025.
Explainer · November 14, 2026
The FTC Safeguards Rule (16 CFR part 314) and its 500-consumer breach notice, explained
Financial institutions under the FTC’s jurisdiction must keep a written information security program with specific elements, and since May 13, 2024 must tell the FTC within 30 days of discovering a notification event that involves at least 500 consumers.
Explainer · November 14, 2026
The FFIEC Cybersecurity Assessment Tool sunset and what replaced it, explained
The FFIEC set August 31, 2025 as the sunset date for its voluntary Cybersecurity Assessment Tool and named no single successor. The agencies pointed to the NIST Cybersecurity Framework 2.0, CISA’s Performance Goals and industry resources, Treasury added voluntary sector goals in August 2026, and credit unions keep NCUA’s updated ACET.
Data brief · November 14, 2026
U.S. bank failures since 2020: 19 closings, and three failures in 2023 carry 97% of the estimated loss
The FDIC lists 19 bank failures from 2020 to September 25, 2026, six of them in 2026. Of the $35.3 billion estimated loss to the Deposit Insurance Fund across the 17 with financial data, three 2023 failures account for 97.0%.
Checklist · November 14, 2026
Checklist: running a Regulation SCI program at an SCI entity
Fourteen steps under 17 CFR 242.1000 to 242.1007: defining SCI systems, writing the required policies, notifying the SEC and members of SCI events, filing quarterly change reports, completing the annual SCI review, testing continuity plans with members, and keeping the records.
Checklist · November 14, 2026
Checklist: the NCUA’s 72-hour cyber incident report and the part 748 security program
Thirteen steps for federally insured credit unions: the written security program and its guidelines, the three kinds of reportable cyber incident, when the 72 hours start, how to reach the NCUA, and the reports that run alongside it.
Checklist · November 14, 2026
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.
Explainer · November 14, 2026
CFTC system safeguards rules for exchanges, SEFs, clearing houses and swap data repositories, explained
Four CFTC rules set how derivatives exchanges, swap execution facilities, clearing organizations and swap data repositories test their systems and recover from disruption. Some entities have fixed minimum testing frequencies; others test on their own risk analysis.
Explainer · November 14, 2026
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.