Jointli Book a scoping callScoping call

NCUA vendor and cyber rules for credit unions

If you run or oversee a federally insured credit union, the NCUA expects your board to own the security program, your team to check every vendor before and after you sign, and someone to report a serious cyber incident to the NCUA within 72 hours. That includes incidents that start at a vendor. This page sets out what the rules say and where to start.

Why it matters now

Picture a Thursday afternoon. Your online banking provider calls to say an attacker got into a system that holds member data. It isn't your system, and your staff did nothing wrong. Under the NCUA's rule, a compromise at a credit union service organization, a cloud provider or another data host can still be a reportable cyber incident for you. The NCUA has to hear from you within 72 hours of the vendor's call.

Then the board asks the questions it should: what did we check before we signed with them, what does the contract say, and when did we last look at their audit? Those answers come from work done months earlier.

What the rules say

The security program (12 CFR Part 748, Appendix A). The NCUA's Guidelines for Safeguarding Member Information say each credit union should:

Involve the board. The board, or a committee of it, approves the written information security policy and program and oversees it, including who is responsible for running it.

Assess risk. Identify reasonably foreseeable threats to member information, assess how likely and how damaging each one is, and check whether current policies, procedures and systems are enough to control them.

Oversee service providers. Use due diligence when choosing them, require them by contract to protect member information, and, where your risk assessment calls for it, monitor them, including by reviewing their audits, test results or similar evaluations.

Report to the board at least once a year. The report covers the program's status, the risk assessment, risk decisions, service provider arrangements, testing results, breaches and how management responded, and recommended changes.

Cyber incident reporting (12 CFR 748.1(c)). A federally insured credit union must notify the NCUA of a reportable cyber incident as soon as possible and no later than 72 hours after it reasonably believes one has happened. When the incident comes through a third party, such as a credit union service organization, a cloud service provider or a data host, the 72 hours can run from when the third party tells you.

Third-party relationships (NCUA Letter to Credit Unions 07-CU-13). The NCUA's guidance on evaluating third-party relationships says the planning, due diligence and controls should fit your risk profile and the kind of relationship. At a minimum, due diligence should weigh how critical the service is, the vendor's expertise, staffing changes, economic and regulatory changes, and how you'll manage the risk.

Where to start this quarter

List every vendor that touches member information or keeps services running. Core processor, online banking, card processing, cloud storage, and the credit union service organizations you use.

Sort them by how much a failure would hurt members. Our free vendor risk assessment questionnaire shows how, and gives you 40 questions to send.

Read the contracts. Do they require the vendor to protect member information? Do they say how fast the vendor tells you about an incident, fast enough for you to report to the NCUA within 72 hours?

Collect the proof. For your most critical vendors, get their latest audit or independent report and file what you reviewed.

Put it in the board report. Service provider arrangements are one of the topics the yearly report should cover.

A credit union board listening to a presenter with a printed report

How Jointli helps

A cybersecurity risk assessment follows the same steps the NCUA's guidelines describe: what threats your member information faces, how likely and how damaging each one is, and whether your controls are enough. That includes your vendors. You get a written risk register with an owner for every risk and fixes sized to your budget, in a form your board can approve and your examiner can follow. For a quicker first look, a Framework Gap Analysis shows in two weeks which controls you have and which are missing.

The owners run the work live with your team, and the fee is fixed before we start.

Ask us about a risk assessment →

Questions credit unions ask

It can. The rule counts a compromise at a credit union service organization, a cloud service provider or another data host as a possible reportable incident, and the 72 hours can run from when the vendor notifies you.

The guidelines say at least once a year, in a report that includes the risk assessment and service provider arrangements.

The guidance says the depth of due diligence should match your risk profile and the relationship. Critical vendors deserve the full review, and low-risk ones can get a lighter check.

The guidelines name audits, summaries of test results, or other equivalent evaluations. One example is a recent independent report, such as a SOC 2 Type 2.

This page summarizes NCUA rules and guidance. It is not legal advice. Check your obligations with your examiner or counsel.