> 12 CFR 748 vs Basic Security Controls side by side, topic by topic: where they overlap, where they differ and which asks more, with incident deadlines, testing, third parties and fines.

# 12 CFR 748 vs Basic Security Controls

Where they overlap, where they differ and which asks more, topic by topic, with their deadlines and fines side by side.

[12 CFR 748](https://grc.plus/regulation/us-ncua-cyber-incident-notification/)Every federally insured credit union, including federally insured state-chartered and corporate credit unions.

[Basic Security Controls](https://grc.plus/regulation/basic-security-controls-government/)

## At a Glance

They differ on 5 of 5 topics. Each verdict names what it rests on; read the wording before relying on it.

- **12 CFR 748** Asks more on 0 topics Alone on 5 topics More detailed on 0 topics
- **Basic Security Controls** Asks more on 0 topics Alone on 0 topics More detailed on 0 topics

| Topic | 12 CFR 748 | Basic Security Controls | Verdict |
| --- | --- | --- | --- |
| Governance |  |  |  |
| Awareness and training | 12 CFR 748: 1 | Basic Security Controls: – | **Only 12 CFR 748**no specific requirement on the other side in the acts covered |
| Detection and response |  |  |  |
| Incident handling | 12 CFR 748: 3 | Basic Security Controls: – | **Only 12 CFR 748**no specific requirement on the other side in the acts covered |
| Incident classification | 12 CFR 748: 5 | Basic Security Controls: – | **Only 12 CFR 748**no specific requirement on the other side in the acts covered |
| Reporting to authorities | 12 CFR 748: 5 | Basic Security Controls: – | **Only 12 CFR 748**no specific requirement on the other side in the acts covered |
| Third parties and supply chain |  |  |  |
| Contract requirements | 12 CFR 748: 1 | Basic Security Controls: – | **Only 12 CFR 748**no specific requirement on the other side in the acts covered |

## What This Covers

The obligations below are summarised from the acts listed here, grouped by topic. Where a side shows nothing on a topic, the acts covered have no specific requirement on it; an act not yet included, national guidance or a supervisor's expectations may still say more. Use it to see where the regimes differ, not as a compliance checklist.

Included

- [12 CFR 748](https://grc.plus/regulation/us-ncua-cyber-incident-notification/) 12 CFR 748.1(c), added by the NCUA final rule Cyber Incident Notification Requirements for Federally Insured Credit Unions, 88 FR 12811 (1 March 2023) 15 requirements

Status

Reviewed against the official texts.

Included

- [Basic Security Controls](https://grc.plus/regulation/basic-security-controls-government/) GS_G2_Basic_Security_Controls, version 1.0 4 requirements

Status

Reviewed against the official texts.

## Key Numbers

### Incident reports go to

12 CFR 748: Appropriate NCUA-designated point of contact.

Basic Security Controls: Not in the acts covered

### Incident notification

12 CFR 748: As soon as possible, and received by the NCUA no later than 72 hours after the credit union reasonably believes it has experienced a reportable cyber incident. For a third-party incident under paragraph (c)(1)(i)(C), use the earlier of that reasonable belief and notification by the third party.

Basic Security Controls: Not in the acts covered

## Governance

### Awareness and training

**Only 12 CFR 748** no specific requirement on the other side in the acts covered

NIST CSF 2.0 PR.AT · ISO/IEC 27001:2022 A.6.3

- Train Employees on Incident Reporting Recommended
  NCUA implementation guidance recommends training all employees on cyber-incident reporting, their roles and the consequences of noncompliance, with resources and guidance to fulfil their responsibilities.
  [12 CFR 748, NCUA Letter 23-CU-07, Implementation Guidelines: Train Employees](https://grc.plus/regulation/us-ncua-cyber-incident-notification/#requirements)

Nothing in the acts covered.

## Detection and response

### Incident handling

**Only 12 CFR 748** no specific requirement on the other side in the acts covered

NIST CSF 2.0 RS.MA, RS.AN, RS.MI · ISO/IEC 27001:2022 A.5.24 to A.5.28

- Update the Incident Response Plan Recommended
  NCUA implementation guidance recommends reviewing and updating the response plan to include reporting timeframes, NCUA notification procedures, reportability criteria and escalation to management and the regulator.
  [12 CFR 748, NCUA Letter 23-CU-07, Implementation Guidelines: Update Response Plan](https://grc.plus/regulation/us-ncua-cyber-incident-notification/#requirements)
- Review and Exercise the Reporting Process Recommended
  NCUA implementation guidance recommends regular monitoring and review of the reporting process, periodic tests and exercises of response plans and procedures, and improvements based on lessons learned.
  [12 CFR 748, NCUA Letter 23-CU-07, Implementation Guidelines: Monitor and Review](https://grc.plus/regulation/us-ncua-cyber-incident-notification/#requirements)
- Document Incidents and Reporting Decisions Recommended
  NCUA implementation guidance recommends documenting all cyber incidents, including those that are not reportable, and retaining records under the credit union's retention policies. Document indicators of compromise, relevant network/traffic information, attack vector, exfiltrated-data information and forensic or other incident reports. Keep an audit trail supporting management's reporting decisions. This does not authorise sending excluded technical material in the initial notice.
  [12 CFR 748, NCUA Letter 23-CU-07, Implementation Guidelines: Document All Incidents](https://grc.plus/regulation/us-ncua-cyber-incident-notification/#requirements)

Nothing in the acts covered.

### Incident classification

**Only 12 CFR 748** no specific requirement on the other side in the acts covered

NIST CSF 2.0 RS.MA · ISO/IEC 27001:2022 A.5.25

- Include Substantial Third-Party and Supply-Chain Incidents
  A substantial cyber incident is reportable if it leads to disruption of the credit union's business operations or unauthorised access to sensitive data, facilitated through or caused by a compromise of a credit union service organisation, cloud service provider, other third-party data hosting provider or the supply chain. An unrelated incident at a supplier is not automatically reportable. The credit union must report qualifying incidents using the earlier reasonable-belief or third-party-notice clock.
  [12 CFR 748, 12 CFR 748.1(c)(1)(i)(C)](https://grc.plus/regulation/us-ncua-cyber-incident-notification/#requirements)
- Apply the Good-Faith Requested-Activity Exclusion Optional
  An event is excluded from the reportable-cyber-incident definition where an entity performs the cyber incident in good faith in response to a specific request by the system owner or operators, for example an authorised penetration test. Both good faith and the specific request are required.
  [12 CFR 748, 12 CFR 748.1(c)(1)(ii)](https://grc.plus/regulation/us-ncua-cyber-incident-notification/#requirements)
- Assess Substantial Loss of Confidentiality, Integrity or Availability
  Treat a substantial cyber incident as reportable where it leads to a substantial loss of confidentiality, integrity or availability of a network or member information system that results from unauthorised access to or exposure of sensitive data, disrupts vital member services, or seriously affects the safety and resiliency of operational systems and processes. Apply the incorporated definitions in Appendix A, I.B.2.e, and 12 CFR 749.1.
  [12 CFR 748, 12 CFR 748.1(c)(1)(i)(A)](https://grc.plus/regulation/us-ncua-cyber-incident-notification/#requirements)
- Assess Disruption From Cyberattacks and Exploited Vulnerabilities
  Treat a substantial cyber incident as reportable where it leads to disruption of business operations, vital member services or a member information system resulting from a cyberattack or exploitation of vulnerabilities. The overarching substantial-cyber-incident condition still applies.
  [12 CFR 748, 12 CFR 748.1(c)(1)(i)(B)](https://grc.plus/regulation/us-ncua-cyber-incident-notification/#requirements)
- Assess Whether the Incident Is Substantial Recommended
  NCUA guidance expects reasonable judgment when assessing whether an incident is substantial, taking account of factors including credit union size, the type and impact of the loss and its duration. The rule does not prescribe a single numeric substantiality threshold.
  [12 CFR 748, NCUA Letter 23-CU-07, Summary](https://grc.plus/regulation/us-ncua-cyber-incident-notification/#requirements)

Nothing in the acts covered.

### Reporting to authorities

**Only 12 CFR 748** no specific requirement on the other side in the acts covered

NIST CSF 2.0 RS.CO · ISO/IEC 27001:2022 A.5.5

- Ensure the NCUA Receives Notice Within 72 Hours
  As soon as possible, and received by the NCUA no later than 72 hours after the credit union reasonably believes it has experienced a reportable cyber incident. For a third-party incident under paragraph (c)(1)(i)(C), use the earlier of that reasonable belief and notification by the third party. Do not wait for a detailed incident assessment before giving the initial alert.
  [12 CFR 748, 12 CFR 748.1(c)](https://grc.plus/regulation/us-ncua-cyber-incident-notification/#requirements)
- Use an NCUA-Designated Reporting Channel
  Notify the appropriate NCUA-designated contact using email, telephone or a similar prescribed method. Current NCUA instructions allow the Cyber Incident Credit Union Reporting System webform, voicemail at 1.833.292.3728, or secure email to cybercu@ncua.gov through the NCUA Secure Email Message Center. Use the secure centre for email to ensure receipt.
  [12 CFR 748, 12 CFR 748.1(c); NCUA Letter 25-CU-02, How to Report and footnote 2](https://grc.plus/regulation/us-ncua-cyber-incident-notification/#requirements)
- Provide the Known Initial Facts Recommended
  NCUA guidance recommends providing the credit union name and charter number, reporter name and title, callback/contact details, when the credit union reasonably believed a reportable incident had occurred, and a general description of affected services, information and operations. Give what is known at initial reporting; a detailed incident assessment is not required within the 72-hour period.
  [12 CFR 748, NCUA Letter 23-CU-07, What to Report; Cyber Incident Reporting Guide, What to Report](https://grc.plus/regulation/us-ncua-cyber-incident-notification/#requirements)
- Keep Sensitive Technical Material Out of the Initial Notice Recommended
  NCUA reporting guidance directs credit unions not to include sensitive personally identifiable information, indicators of compromise, specific vulnerabilities or email attachments in the initial notification. This is agency reporting guidance, separately identified from the rule's statutory reporting trigger.
  [12 CFR 748, NCUA Letter 23-CU-07 and Cyber Incident Reporting Guide, What to Report](https://grc.plus/regulation/us-ncua-cyber-incident-notification/#requirements)
- Contact the NCUA Promptly When Reportability Is Uncertain Recommended
  NCUA guidance recommends contacting the agency as soon as possible if the credit union is unsure whether a cyber incident is reportable. This does not replace the reporting obligation when its legal trigger is met.
  [12 CFR 748, NCUA Letter 23-CU-07, Summary](https://grc.plus/regulation/us-ncua-cyber-incident-notification/#requirements)

Nothing in the acts covered.

## Third parties and supply chain

### Contract requirements

**Only 12 CFR 748** no specific requirement on the other side in the acts covered

NIST CSF 2.0 GV.SC · ISO/IEC 27001:2022 A.5.20

- Review Critical Provider Notification Terms Recommended
  NCUA implementation guidance recommends reviewing critical service-provider contracts for provisions requiring timely cyber-incident notification. The cyber notification rule itself does not impose a new requirement to amend those contracts.
  [12 CFR 748, NCUA Letter 23-CU-07, Implementation Guidelines: Review Contracts](https://grc.plus/regulation/us-ncua-cyber-incident-notification/#requirements)

Nothing in the acts covered.

Requirements are summarised in plain words; the official text prevails. Verdicts compare what the acts covered state, not how a supervisor applies them. Most topics are cross-referenced to NIST CSF 2.0 and ISO/IEC 27001:2022.

## More Comparisons

- [Compare 12 CFR 748](https://grc.plus/compare/12-cfr-748/)
- [Compare Basic Security Controls](https://grc.plus/compare/basic-security-controls/)

Source: https://grc.plus/compare/12-cfr-748-vs-basic-security-controls/
