# 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 · Financial Services · Security & Resilience. Published November 14, 2026. Last reviewed November 14, 2026.

## One part, two duties

Part 748 of the NCUA’s rules asks every federally insured credit union for two things that meet in an incident. Section 748.0 requires a written security program, and appendix A sets out the guidelines for safeguarding member information that sit behind it [1]. Section 748.1 requires reports, and since September 1, 2023 that includes a cyber incident report: the NCUA must receive notice as soon as possible and no later than 72 hours after the credit union reasonably believes it has experienced a reportable cyber incident [1] [2]. The NCUA adopted the report in a final rule published on March 1, 2023 [2], and its August 2023 letter to credit unions, 23-CU-07, explains what and how to report, with examples of incidents that are and are not reportable [3].

## Using the steps

The first four steps cover the security program; the rest cover the cyber incident report and the reports beside it. Each step cites the section of part 748, the NCUA’s letter or the preamble to the 2023 rule, using the eCFR text current to November 12, 2026 [1]. Where a step is our suggestion, it says so. The owner under each step is a typical role, not one the rule names, unless the step says the rule names it. State-chartered credit unions should also check what their state supervisor expects. This page explains the rule; it is not legal advice.

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

## The checklist

1. **Confirm the credit union has a written security program, approved by the board or a board committee, that covers the five aims in section 748.0(b).** (Board, with the information security officer) Section 748.0(a) and (b) require the written program and list its aims, from protecting offices against robbery and embezzlement to protecting member records and responding to unauthorized access to member information. Appendix A, paragraph III.A, says the board or an appropriate committee should approve the written information security policy and program and oversee it [1].
2. **Run and record a risk assessment of member information and member information systems.** (Information security officer) Appendix A, paragraph III.B, asks the credit union to identify reasonably foreseeable internal and external threats, assess their likelihood and potential damage given the sensitivity of member information, and assess whether current policies, procedures and systems control the risks [1].
3. **Decide, item by item, which of the eight security measures in appendix A apply, adopt those that do, then train staff and have the key controls tested regularly, with the tests run or reviewed by people independent of those who develop or maintain the program.** (CISO, with internal audit) Appendix A, paragraph III.C.1, says the credit union must consider whether each listed measure is appropriate, from access controls and encryption to monitoring and response programs, and adopt those it concludes are. Paragraphs III.C.2 and III.C.3 cover staff training and regular testing of key controls, with tests conducted or reviewed by independent third parties or by staff independent of those who develop or maintain the program [1]. Writing down why a measure was not adopted is our suggestion.
4. **Set the service provider rules: due diligence before selection, contract terms that require appropriate safeguards and prompt notice of unauthorized access, and monitoring where the risk assessment calls for it.** (Third-party risk management) Appendix A, paragraph III.D, covers due diligence, contracts and monitoring of service providers. Appendix B says a credit union’s contract with its service provider should require the provider to notify the credit union as soon as possible of an incident of unauthorized access to member information [1].
5. **Write the definition of a reportable cyber incident into the incident procedure, with its three outcomes and the exclusion for testing the credit union asked for.** (Incident response lead) Section 748.1(c)(1)(i) lists the three outcomes: a substantial loss of confidentiality, integrity or availability of a network or member information system; a disruption of business operations, vital member services or a member information system from a cyberattack or exploited vulnerability; and a disruption or unauthorized access to sensitive data through a compromised credit union service organization, cloud provider, other third-party data host or supply chain. Section 748.1(c)(1)(ii) excludes incidents performed in good faith at the system owner’s request [1]. The NCUA’s letter gives a contracted penetration test as an example of that exclusion [3].
6. **Add the NCUA’s examples of incidents that are and are not reportable to the triage guide, and tell staff to contact the NCUA when unsure.** (Incident response lead) The letter says blocked phishing attempts, failed attempts to gain access, unsuccessful malware attacks and routine maintenance outages are not reportable, while a DDoS attack that disrupts member account access with substantial outages is. It says whether an incident is substantial depends on factors including the credit union’s size, the type and impact of the loss and its duration, and that a credit union unsure whether an incident is reportable should contact the NCUA as soon as possible [3]. Putting the examples in a triage guide is our suggestion.
7. **Name who decides that the credit union reasonably believes a reportable cyber incident has occurred, and log the time of that decision and the time any third-party notice arrives.** (CISO, with the CEO) Section 748.1(c) runs the 72 hours from the reasonable belief or, for a third-party compromise, from being notified by the third party, whichever is sooner [1]. The letter confirms the clock starts when the reasonable belief forms [3]. Naming the decision maker and logging both times are our suggestions, so the deadline can be shown.
8. **Brief business and IT staff that a loss of access to member accounts can mean a provider has been compromised, even before the provider says so.** (Third-party risk management, with operations) The preamble says a credit union may reasonably not know of a third party’s breach without notice from it, but if it loses access to its member accounts it reasonably should be aware that its core service provider has been compromised. It adds that the rule does not require existing contracts to be amended [2]. The letter’s implementation guidelines still recommend reviewing contracts with critical service providers for timely notification terms [3]. The staff briefing is our suggestion.
9. **Put both reporting channels in the playbook: the NCUA’s cyber line, 1.833.CYBERCU (1.833.292.3728), where a voicemail can be left, and secure email to cybercu@ncua.gov through the NCUA Secure Email Message Center.** (Regulatory compliance) Section 748.1(c) allows notice by email, telephone or other similar methods the NCUA prescribes, to the NCUA-designated point of contact [1]. The letter names these two channels and says the secure message center must be used for the email to be received [3].
10. **Prepare a short first-notice template with the details the NCUA asks for, and leave out what it asks not to receive.** (Regulatory compliance) The letter asks credit unions to be ready to give as much of the following as is known: the credit union’s name and charter number, the reporter’s name, title, telephone and email, when the reasonable belief formed, and a basic description of what was affected. It asks credit unions not to send sensitive personally identifiable information, indicators of compromise, specific vulnerabilities or email attachments in the initial notice [3]. The preamble describes the notice as an early alert, not a lengthy assessment [2].
11. **Keep the other reports on their own tracks: notice to the regional director and, where warranted, to members under appendix B; a suspicious activity report where section 748.1(d) applies; and a catastrophic act report within five business days under section 748.1(b).** (BSA officer and regulatory compliance) Appendix B describes a response program that notifies the NCUA regional director, and the state supervisor for a state-chartered credit union, as soon as possible after unauthorized access to sensitive member information, and notifies members when misuse has occurred or is reasonably possible [1]. The letter says incidents that do not trigger the cyber report can still fall under appendix B [3]. Sections 748.1(b) and (d) set the catastrophic act and suspicious activity reports [1].
12. **Record every cyber incident, reportable or not, and run exercises on the reporting process.** (Incident response lead) The letter’s implementation guidelines ask credit unions to document all cyber incidents, including indicators of compromise, network traffic, the attack vector, exfiltrated data and forensic reports, and to test and exercise the incident response plan and reporting procedures and train staff [3].
13. **Each year, report to the board on the security program and certify compliance with part 748 in the Credit Union Profile.** (President or managing official (named in the rule), with the information security officer) Section 748.1(a) requires the president or managing official to certify compliance with part 748 annually through the NCUA’s online system. Appendix A, paragraph III.F, says the credit union should report to its board or a board committee at least annually on the program, including risk assessment, service provider arrangements, testing results and security breaches [1].

## Sources

1. Electronic Code of Federal Regulations. 12 CFR part 748, Security Program, Suspicious Transactions, Catastrophic Acts, Cyber Incidents, and Bank Secrecy Act Compliance (eCFR current to November 12, 2026; checked November 14, 2026). <https://www.ecfr.gov/current/title-12/part-748> Checked November 14, 2026.
2. National Credit Union Administration, Federal Register (via GovInfo). Cyber Incident Notification Requirements for Federally Insured Credit Unions (final rule, 88 FR 12811, March 1, 2023). <https://www.govinfo.gov/content/pkg/FR-2023-03-01/html/2023-03682.htm> Checked November 14, 2026.
3. National Credit Union Administration. Letter to Credit Unions 23-CU-07, Cyber Incident Notification Requirements (August 2023; checked November 14, 2026). <https://ncua.gov/regulation-supervision/letters-credit-unions-other-guidance/cyber-incident-notification-requirements> Checked November 14, 2026.

Published: November 14, 2026
Canonical URL: <https://insights.moraph.com/checklist-ncua-72-hour-cyber-incident-report-part-748>
Publisher: Moraph Insights
