PIVTR-D
SSector

Financial services: banks, fintech and payments

First moves
  1. Confirm which rows apply to each entity; record in T1 who decided each clock started.Legal advisor
  2. Put the notification incident question to the named decider at the first triage brief.Incident Commander
  3. Record the decision, the decider and each trigger time in T1; open T17, one per regime.Planning
  4. Tell the acquirer at once of suspected card data compromise.Liaison
  5. Brief the Bank Secrecy Act (BSA) officer if transactions may be affected; keep suspicious activity report (SAR) work out of incident records.Legal advisor
  6. Isolate the card environment at the network; leave compromised hosts running for the PCI Forensic Investigator (PFI).Operations

Then work the page: Reporting obligations, Terms, Roles, What changes in each phase, Records, Who you work with.

This page is for responders at banks, credit unions, broker-dealers, investment advisers, insurers, fintechs, payment processors, card-accepting merchants and money transmitters, and at the service providers that run their systems. One firm often sits in several groups. Take a public bank holding company with a broker-dealer and a New York branch. One incident there goes to the banking agencies, the Securities and Exchange Commission (SEC) and the New York Department of Financial Services (NYDFS).

The clocks are short and start at different events. A bank has 36 hours after it determines a notification incident occurred; the National Credit Union Administration (NCUA) and NYDFS allow 72 hours. Visa allows three calendar days, and a public company has four business days after it determines materiality.

A SAR runs on a 30-day clock and stays confidential. Examiners review the response afterward.

This page adds to the phase playbooks for scope, contain, eradicate and recover. Incident Command seats for this sector are on Command by incident type.

This sector page is an addition to the book. Primary sources checked: 12 CFR Part 53, 12 CFR 225 Subpart N, 12 CFR 304 Subpart C, 12 CFR Part 748, 12 CFR 364 Appendix B, Regulation S-P, 17 CFR 242.1002, SEC Release 33-11216, 16 CFR 314.4, 23 NYCRR 500.17, NAIC Model Law 668, 31 CFR 1020.320, Visa What To Do If Compromised. Federal and New York rule text checked October 2026. The NAIC model law, card brand and PCI items were last checked as dated in the sources below.

Reporting obligations

Counsel confirms which rows apply; a firm in several groups owes every row that fits. Record in T1 who decided that each clock started, and when. The notification deadlines table lists state breach laws, the EU Digital Operational Resilience Act (DORA) for firms with EU operations, and other regimes.

ObligationWho reports to whomClockStarts whenWhat the report contains
Notification incident: 12 CFR 53.3 (Office of the Comptroller of the Currency, OCC), 225.302 (Federal Reserve), 304.23 (Federal Deposit Insurance Corporation, FDIC)Bank or bank holding company to its primary federal regulator: OCC supervisory office or BankNet; incident@frb.gov or the Board's telephone line, and the Reserve Bank central point of contact; FDIC supervisory office36 hours, sooner if possibleThe bank determines a notification incident occurredNo form. Email or telephone with the facts known
Bank service provider notice: 12 CFR 53.4, 225.303, 304.24Provider to each affected bank's designated contact, or its CEO and CIOAs soon as possibleThe provider determines a computer-security incident has materially disrupted or degraded covered services, or is reasonably likely to, for four or more hoursThe disruption. Maintenance, testing and updates announced in advance are excluded
NCUA, 12 CFR 748.1(c), effective September 1, 2023Federally insured credit union to NCUA: webform, voicemail line or cybercu@ncua.gov72 hours, sooner if possibleReasonable belief that a reportable cyber incident occurred, or notice of one from a credit union service organization (CUSO) or other third partyContact, charter number, when identified, services affected, whether sensitive data was compromised. No personally identifiable information (PII) or indicators of compromise in the first report
Gramm-Leach-Bliley Act (GLBA) response program: Interagency Guidance, 12 CFR 364 Appendix B, Supplement A, and parallel OCC, Federal Reserve and NCUA appendicesBank or credit union to its primary federal regulator, and to affected customersAs soon as possible, for eachRegulator: awareness of unauthorized access to sensitive customer information. Customers: misuse has occurred or is reasonably possibleCustomer notice: what happened, the information involved, what the institution did, a telephone number, and advice on vigilance, fraud alerts and credit reports
Regulation S-P, 17 CFR 248.30 (2024 amendments)Broker-dealer, funding portal, fund, SEC-registered adviser or transfer agent to affected individuals30 days, sooner if practicableBecoming aware that unauthorized access to sensitive customer information occurred or is reasonably likelyThe incident, the data and what individuals can do. No notice if an investigation finds substantial harm or inconvenience unlikely. Delay only on the Attorney General's written notice to the SEC
Regulation S-P, service providersService provider to the covered institution, under contract72 hours, sooner if possibleAwareness of a breach giving unauthorized access to a customer information system the provider maintainsWhat the contract requires
Regulation SCI, 17 CFR 242.1002(b)SCI entity (exchanges, clearing agencies, the Financial Industry Regulatory Authority (FINRA), certain alternative trading systems) to the SECImmediately; Form SCI within 24 hours; interim report at 30 days if unresolved; final report 5 business days after resolution and closure of the investigationResponsible SCI personnel have a reasonable basis to conclude an SCI event occurredThe event and systems affected, then participants, market impact and corrective steps. Regular updates. Events with no or de minimis impact go in a log and a quarterly summary
Form 8-K, Item 1.05Public company (registrant) to the SEC4 business daysThe company determines the incident is material, which it must do without unreasonable delay after discoveryMaterial aspects of nature, scope and timing, and material or reasonably likely material impact. Amend when new facts arrive. The Attorney General can delay filing for national security or public safety
Safeguards Rule, 16 CFR 314.4(j), effective May 13, 2024Financial institution under Federal Trade Commission (FTC) jurisdiction (mortgage brokers, finance companies, check cashers, wire transferors, tax preparers and others) to the FTC online form30 days, sooner if possibleDiscovery of unauthorized acquisition of unencrypted customer information of 500 or more consumers. Data counts as unencrypted if the key was accessed. Unauthorized access to unencrypted data is presumed to be acquisition without reliable evidence otherwiseContact, information types, dates, consumer count, a description, and any law enforcement delay (up to 30 days, then up to 60 more)
23 NYCRR 500.17(a)NYDFS covered entity (licensed or chartered under the Banking, Insurance or Financial Services Law) to the Superintendent through the DFS Portal72 hours, sooner if possibleDetermining that a cybersecurity incident occurred at the entity, an affiliate or a third-party service providerEntity, contact, dates, location, description and impact. Updates on material changes
23 NYCRR 500.17(c)NYDFS covered entity to the Superintendent24 hours, then 30 daysMaking an extortion paymentNotice of payment; then why it was necessary, alternatives and diligence considered, and sanctions diligence
State law based on National Association of Insurance Commissioners (NAIC) Model Law 668, Section 6Insurance licensee to its home state commissioner, and to any state with 250 or more affected residents where notice to a government body is required or material harm is likely72 hours, sooner if possibleDetermining that a cybersecurity event occurred, including at a service providerDates, how it happened, information and consumers involved, notices made, control lapses and remediation. Consumer notice follows state breach law
Visa What To Do If Compromised, version 10.0, June 25, 2026Any entity handling Visa cardholder data to Visa, and immediately to its acquirer or issuer. Visa clients answer for their merchants and agents3 calendar days; incident report 3 calendar days laterEvidence raising a reasonable suspicion of, or confirming, a compromise eventEnvironment, scope, card data at risk, exposure, containment and dated steps. If Visa requires a PFI: contract within 5 business days, preliminary report 5 business days later, final report 10 business days after the investigation
Mastercard account data compromise rules, Security Rules and Procedures, Chapter 10Mastercard customer (acquirer or issuer) to Mastercard24 hoursBecoming aware of an account data compromise (ADC) event or potential ADC event. The customer's contracts must make its agents notify Mastercard on the same clockKnown facts within 24 hours, then updates. Affected account numbers within 72 hours. If Mastercard requires a PFI: engage one within 72 hours, name it to Mastercard within 2 business days, preliminary report within 5 business days of the investigation's start, final report within 10 business days of its end (section 10.3.1)
State money transmission laws and license conditionsMoney transmitter to each state that licensed itNo uniform clockSet by each stateSet by each state
Suspicious activity report: 31 CFR 1020.320 (banks), 1022.320 (money services businesses), 1023.320 (broker-dealers)Institution to the Financial Crimes Enforcement Network (FinCEN). Violations needing immediate attention, such as ongoing money laundering, go to law enforcement by telephone at once30 calendar days; banks and broker-dealers get 30 more to identify a suspect, 60 at mostInitial detection of facts. FIN-2016-A005: a cyber-event meant to conduct or affect transactions of $5,000 or more ($2,000 for money services businesses)The activity and cyber indicators: IP addresses with times, device identifiers, wallet addresses, hashes, domains. Ransomware: key term CYBER-FIN-2021-A004

The Regulation S-P compliance dates, December 3, 2025 for larger entities and June 3, 2026 for smaller ones, have passed. On May 21, 2024 the SEC's Division of Corporation Finance said incidents not determined material can be disclosed under Item 8.01. A later materiality determination starts four business days for Item 1.05.

Regulation S-K Item 106 adds annual 10-K disclosure of cyber risk management, strategy and board oversight. Industry groups petitioned on May 22, 2025 to rescind Item 1.05, which remained in force when this page was checked in October 2026.

NCUA proposed on December 11, 2025 to remove Appendix B to Part 748 and reissue it as a Letter to Credit Unions, with no change to what credit unions must do. Comments closed February 9, 2026. Appendix B was still in the eCFR on October 22, 2026, and NCUA's Deregulation Project page listed the proposal with no final rule when checked on November 10, 2026.

NAIC's state implementation report counts 28 jurisdictions that adopted the model as of March 9, 2026, and state versions differ. New York insurers and money transmitters report under Part 500, whose last phase-in took effect November 1, 2025: multi-factor authentication (MFA) for all access to information systems (500.12) and the asset inventory (500.13(a)).

The Payment Card Industry Data Security Standard (PCI DSS) v4.0.1 sets no clock. Requirement 12.10.1 requires a plan that covers notifying payment brands and acquirers, the legal reporting analysis and the brands' procedures; 12.10.3 requires responders available 24/7.

The Conference of State Bank Supervisors (CSBS) counted 31 states in September 2026 that enacted the Money Transmission Modernization Act in full or in part. Its Section 7.04 event reports cover bankruptcy, receivership, license actions and felony charges, and list no cyber event. The FTC Safeguards Rule reaches wire transferors.

A SAR is confidential. No one at the institution may disclose a SAR or information revealing that one exists, except to FinCEN, law enforcement, examining regulators, and within the corporate structure for BSA purposes. The underlying facts, transactions and documents may go to the insurer, forensic firm and law enforcement as other law allows, with no mention of the SAR.

The September 21, 2021 advisory of Treasury's Office of Foreign Assets Control (OFAC) governs ransom payment decisions; see the ransomware scenario.

Two cases show a provider's incident becoming the firm's. On February 2, 2023 the Commodity Futures Trading Commission (CFTC) said a cyber incident at ION Cleared Derivatives would delay registrants' required reports. It told firms to file best estimates, and later postponed its Commitments of Traders report.

On December 1, 2023 NCUA said about 60 credit unions had outages from ransomware at the provider Ongoing Operations. NCUA counted 1,072 credit union cyber incident reports in the rule's first year, 742 involving a third-party vendor.

Sources: interagency rule effective April 1, 2022 (SR 22-4; OCC Bulletin 2022-8); NCUA final rule and reporting guide; SEC Regulation S-P guide, disclosure guide, Gerding statement and petition 4-856; FTC; NYDFS instructions; NAIC State Implementation Report, as of March 9, 2026 (checked October 2026); Visa What To Do If Compromised, version 10.0 (checked October 2026); Mastercard Security Rules and Procedures, Merchant Edition (August 4, 2026), section 10.3.1 (checked November 2026); PCI DSS v4.0.1 (June 2024), requirements 12.10.1 and 12.10.3, read in the PCI Security Standards Council PDF as copied by Middlebury College (checked November 2026); CSBS MTMA page, September 3, 2026 (checked October 2026); FinCEN FIN-2016-A005 and FIN-2021-A004; OFAC advisory; CFTC statement and release 8662-23; The Record; NCUA October 24, 2024 briefing; NCUA, proposed removal of Appendix B to Part 748, 90 FR 57397, December 11, 2025, eCFR Appendix B to Part 748, current to October 22, 2026, and NCUA's Deregulation Project page (checked November 2026); 23 NYCRR 500.22 (transitional periods); 17 CFR 248.30; 31 CFR 1023.320.

Terms

TermMeaningPIVTR-D equivalent
Primary federal regulatorOCC for national banks and federal savings associations; Federal Reserve for state member banks and bank holding companies; FDIC for state nonmember banks and state savings associations; NCUA for federally insured credit unionsnone
Computer-security incidentAn occurrence causing actual harm to the confidentiality, integrity or availability of a system or its informationIncident
Notification incidentA computer-security incident that materially disrupts or degrades, or is reasonably likely to, banking operations, a major business line, or operations whose failure threatens US financial stabilityA clock start recorded in T1
Bank service providerA company performing services subject to the Bank Service Company Act, such as a core processorVendor; see the supply chain scenario
MRA / MRIAMatters requiring attention, and requiring immediate attention: examination findings the institution must fixT14 Improvement register entries
FFIECFederal Financial Institutions Examination Council, which sets uniform examination standards for the banking agenciesnone
CATFFIEC Cybersecurity Assessment Tool, sunset August 31, 2025none
CRI ProfileThe Cyber Risk Institute's industry profile, one of the CAT replacements the FFIEC named with NIST CSF 2.0 and CISA's performance goalsPreparation
SARSuspicious activity report to FinCEN, confidential by lawnone
BSA/AMLBank Secrecy Act and anti-money laundering programnone
FinCENTreasury bureau that administers the BSA and receives SARsnone
OFACTreasury's sanctions office. Civil penalties for paying a sanctioned person apply on strict liabilitynone
GLBAGramm-Leach-Bliley Act, the source of the financial privacy and safeguards rulesnone
NPINonpublic personal information: personally identifiable financial information about a consumerRestricted data scenario
Customer informationAny record of NPI about a customer, kept by or for the institution. Sensitive customer information adds identifiers that permit account access or identity theftRestricted data
Reg S-PSEC privacy and safeguards rule, amended in 2024 to require an incident response program and customer noticenone
Reg SCISEC rule for market infrastructure systems. An SCI event is a systems disruption, compliance issue or intrusionIncident
8-K Item 1.05The Form 8-K item for a cybersecurity incident the registrant determines is materialnone
MaterialityA substantial likelihood that a reasonable investor would consider the incident importantnone; the T1 risk level is a separate rating
NYDFS CISO certificationFiled by April 15 each year and signed by the highest-ranking executive and the CISO: compliance, or acknowledged noncompliance with a remediation plannone
PCI DSSPayment Card Industry Data Security Standard, now v4.0.1none
PFIPCI Forensic Investigator, approved and listed by the PCI Security Standards CouncilOutside forensic firm
QSAQualified Security Assessor, which assesses PCI DSS compliancenone
ADCAccount data compromise, Mastercard's term. Visa says compromise eventRestricted data
AcquirerThe bank that contracts with a merchant to accept cardsnone
IssuerThe bank that issues cards; it monitors and reissues after a compromisenone
BINBank identification number: the leading card digits that identify the issuernone
NachaACH network rulemaker. Large non-bank originators and processors must make stored account numbers unreadablenone
Swift CSPSwift Customer Security Programme: controls framework with annual attestationnone
Sheltered HarborSubsidiary of the Financial Services Information Sharing and Analysis Center (FS-ISAC) whose standard vaults customer account data nightly offline, with a plan to restore customer access to fundsRestore source in Recover
Core processorVendor running the bank's system of record for deposits and loansCritical system in the containment triggers
BaaSBanking as a service: a bank's accounts or payments offered through a fintech's productnone
Sponsor bankThe chartered bank behind a BaaS program or a fintech's network accessnone

Roles

Sector roleWhat they do in an incidentPIVTR-D or Incident Command seat
CISOLeads the response, briefs examiners, signs the NYDFS certificationCISO
General counselDecides which rows apply, advises on materiality, approves every noticeLegal advisor
Chief compliance officerFiles regulator notices and answers examinersLiaison
BSA officerDecides SAR filing and keeps SAR material confidentialLiaison for FinCEN, beside the Legal advisor
Chief risk officerRates business and customer impact for notification and materiality decisionsExecutive group
Treasury and payments operationsPauses, reroutes or recalls wires, ACH and settlement; runs manual paymentsOperations, payments branch, with Finance/Admin
Fraud operationsWatches accounts and cards for misuse, blocks and reissues cardsIntelligence/Investigations
Investor relationsKeeps the 8-K and market statements consistentPublic Information Officer
Vendor managementKeeps service provider contracts, notice terms and contactsLiaison
Board risk committeeOversees cyber risk and receives briefings; the disclosure committee decides materialityExecutive group

What changes in each phase

Preparation

#ItemOwner
1Keep a register of the rows that apply to each legal entity, with channel and decision ownerLegal advisor
2Test regulator channels, including DFS Portal accounts with MFALiaison
3Give every bank service provider a designated contactLiaison
4Require 72-hour breach notice in broker-dealer and adviser vendor contractsLegal advisor
5Write the criteria and name the deciders for notification incident, NYDFS incident and disclosure committee escalationCISO
6Put the BSA officer on the call treeLegal advisor
7Set the rule that SAR material stays out of incident recordsLegal advisor
8Name brand and acquirer notice and a PFI shortlist in the PCI incident response planCISO
9Test the vaulted account data restore and manual payment proceduresOperations

Identification and verification

#ItemOwner
1Put the notification incident question to the named decider at the first triage brief, and at each brief after until it is decidedIncident Commander
2Record the decision, the time and the decider in T1Planning
3Record the time of each trigger: NCUA belief, NYDFS determination, card compromise suspicion, materiality determinationPlanning
4Tell the acquirer at once of suspected card data compromiseLiaison
5Send the facts to the disclosure committee without delayLegal advisor
6Brief the BSA officer when transactions may be affectedLegal advisor
7If a provider outage is involved, ask the provider in writing for the expected durationLiaison
8Search accounts and cards for misuseIntelligence/Investigations

Response loop

#ItemOwner
1File each notice with unknowns marked and counsel's approval, one T17 per regimeLiaison
2Send updates as each rule requires: NYDFS material changes, Reg SCI updates, amended 8-KLiaison
3Isolate the card environment at the network, leave compromised hosts running, and allow no administrator loginsOperations
4If a web skimmer is found, copy it with its logs, then remove itOperations
5Sign a PFI contract within 5 business days of Visa's noticeLegal advisor
6Because the PFI report goes to the brands and acquirer, decide whether counsel runs a separate privileged investigationLegal advisor
7Before any ransom payment, complete OFAC screening and the SAR decisionLegal advisor
8After any extortion payment, file the NYDFS notice within 24 hours and the explanation within 30 daysLegal advisor
9Pause, reroute or recall payments as the executive group decidesFinance/Admin
10Send compromised card numbers to the brands through the acquirerLiaison
11If the core is untrusted, restore customer access from vaulted dataOperations
12Send customer notices from T16, within 30 days for Regulation S-PLegal advisor
13File the FTC Safeguards Rule notice within 30 days of discoveryLegal advisor

Debrief

#ItemOwner
1Enter examiner findings and MRAs in T14CISO
2Weigh the incident in the next NYDFS April 15 filingCISO
3Check the Item 106 text against what the incident showedLegal advisor
4File an amended SAR when new facts emergeLegal advisor
5Map PFI findings to PCI DSS gaps for the QSACISO
6Fix provider notice and evidence terms in contractsLiaison

Records

RecordWhat changes
T1 Incident recordAdd legal entities, regulators and each trigger time. Record that the BSA officer was briefed, and leave out whether a SAR was filed
T2 Triage briefTime left on each clock, card data involvement, provider outage hours
T13 Law enforcement and insurer contactFBI and Secret Service contacts, with nothing that reveals a SAR
T16 Notice to affected individuals or customersOne version per rule: banking guidance, Regulation S-P, each state
T17 Regulator notification worksheetOne per regulator and card brand. Attach the DFS email receipt, which DFS sends only once
T19 Vendor evidence and preservation requestTo the core processor or payment processor, citing the contract's notice clause
Filed 8-K, Form SCI, FTC, NYDFS, Visa and PFI reportsSupplement T15 Incident report. Keep each as filed
SAR and supporting documentsKept by the BSA officer, apart from incident records, five years from filing

Who you work with

BodyWhat they do for youHow to reach them
Primary federal regulator, NCUAReceive notices, follow the response, review it at examinationSupervisory office; channels in the reporting table
SEC, NYDFS, state regulatorsReceive filings and notices; CSBS coordinates state supervisionEDGAR; DFS Portal; each licensing agency
FinCEN, OFACSAR filing; sanctions guidance on paymentsBSA E-Filing; contacts in FIN-2021-A004 and the OFAC advisory
FS-ISACMember intelligence sharing and crisis coordinationMembership
Financial Services Sector Coordinating Council (FSSCC)Industry council, founded 2002, coordinating sector resilience with Treasury, DHS and regulatorsThrough member associations
Treasury Office of Cybersecurity and Critical Infrastructure Protection (OCCIP)Coordinates Treasury's sector resilience work and shares threat informationThrough FS-ISAC, or your regulator as a member of the Financial and Banking Information Infrastructure Committee (FBIIC)
FBI, US Secret ServiceCriminal investigation. Secret Service Cyber Fraud Task Forces cover BEC, ransomware and stolen financial dataField offices; ic3.gov
CISATechnical help and voluntary reportingcisa.gov/report
Acquirer and card brandsCarry card notices, require PFI workThrough the acquiring bank
Sheltered HarborVaulting standard and certification for restoring customer accountsshelteredharbor.org

Sources: FFIEC CAT sunset statement; Nacha; Swift CSP; PCI SSC on PFIs; FS-ISAC on Sheltered Harbor; FSSCC; Treasury OIG OIG-25-007 on OCCIP; Secret Service Cyber Fraud Task Forces.

Watch out
  • A SAR mentioned in T1, a ticket, a status update or a note to the insurer can reveal that it exists. Keep SAR work with the BSA officer.
  • Clocks start at a determination (banking agencies, NYDFS, SEC), a reasonable belief (NCUA), a reasonable suspicion (Visa), discovery (FTC) or awareness (Regulation S-P). Record each event and who decided it.
  • A provider's four-hour notice starts no bank clock; the bank decides whether the outage is its own notification incident. A credit union's 72 hours can start when a CUSO or other third party notifies it of a compromise that disrupts its operations or exposes member information.
  • Visa's procedures say to leave compromised systems running, with no logins or password changes. Automatic endpoint detection and response (EDR) remediation and fast rebuilds break that. Isolate at the network and preserve for the PFI.
  • A ransom payment starts NYDFS's 24-hour notice and needs OFAC screening and a SAR decision. Settle all three before anyone pays.
Adapts material from Dynamic Incident Response: A Framework for Security Teams by Joshua Wright, © 2026 The Escal Institute of Advanced Technologies, Inc. d/b/a SANS Institute, licensed under CC BY 4.0. Figures reproduced under that license. Changes were made. Not published by, endorsed by, or affiliated with the SANS Institute.