# Checklist: meeting the OCC’s information security guidelines in 12 CFR part 30, appendix B

Thirteen steps for national banks and federal savings associations: the written program the board approves, the risk assessment and the eight measures to consider, service provider oversight, the annual board report, and the response program for unauthorized access to customer information.

Checklist · Financial Services · Regulation & Compliance. Published November 14, 2026. Last reviewed November 14, 2026.

## Guidelines with an enforcement path

Appendix B to 12 CFR part 30 holds the Interagency Guidelines Establishing Information Security Standards, issued under section 39 of the Federal Deposit Insurance Act and sections 501 and 505(b) of the Gramm-Leach-Bliley Act [1]. They apply to customer information maintained by or for national banks, federal savings associations, federal branches and agencies of foreign banks, and their subsidiaries other than brokers, dealers, insurers, investment companies and investment advisers. The Federal Reserve and the FDIC publish the same guidelines in their own rules (12 CFR part 208, appendix D-2 and part 225, appendix F; 12 CFR part 364, appendix B), as the footnotes to Supplement A list [1]. Under section 30.3 the OCC may determine that a bank has failed to meet the guidelines and request a compliance plan, which section 30.4 says is due within 30 days of receiving the request unless the OCC notifies the bank in writing that the plan is to be filed within a different period [1].

## Using the steps

Each step names the work, who usually owns it and the paragraph of appendix B, or of its Supplement A on response programs, behind it. The owner under each step is a typical role, not one the guidelines name, unless the step says the guidelines name it. Where a step is our suggestion, it says so. The separate notice under 12 CFR part 53, which the OCC must receive no later than 36 hours after the bank determines that a notification incident has occurred, is a different requirement with its own definitions [2]. This page explains the guidelines; 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 which entities and subsidiaries the program covers, and write down the guidelines’ definitions of customer information, customer information systems and service provider.** (Regulatory compliance with legal) Paragraph I.A sets the scope and paragraph I.C.2 the definitions, including customer information systems as any methods used to access, collect, store, use, transmit, protect or dispose of customer information [1]. Supplement A notes that those systems include ones maintained by service providers [1].
2. **Keep one written information security program with administrative, technical and physical safeguards, coordinated across business lines, that meets the four objectives.** (Chief Information Security Officer) Paragraph II.A requires a comprehensive written program appropriate to the bank’s size, complexity and activities, and allows parts of the bank to use different policies as long as all elements are coordinated. Paragraph II.B sets the objectives: security and confidentiality, protection against anticipated threats, protection against unauthorized access that could cause substantial harm or inconvenience to a customer, and proper disposal [1].
3. **Have the board or a board committee approve the written program and assign specific responsibility for carrying it out.** (Board of directors or a board committee) The guidelines name this owner. Paragraph III.A requires the board or an appropriate committee to approve the program and oversee its development, implementation and maintenance, including assigning specific responsibility and reviewing management reports [1]. For a foreign bank’s branch or agency, I.C.2.a treats the managing official in charge as the board.
4. **Run and document a risk assessment that identifies foreseeable internal and external threats, assesses their likelihood and potential damage, and assesses whether current policies, procedures, systems and other arrangements are sufficient to control the risks.** (Information security risk management) Paragraph III.B.1 to 3 [1].
5. **Go through the eight security measures the guidelines list, decide for each whether it is appropriate, adopt those that are, and record the reasoning.** (Chief Information Security Officer) Paragraph III.C.1 requires the bank to consider access controls, physical access restrictions, encryption, change procedures, dual control and background checks, intrusion monitoring, response programs, and protection against environmental hazards and technological failures, and to adopt those it concludes are appropriate [1]. Recording the reasoning for each is our suggestion.
6. **Train staff to carry out the program.** (Security awareness lead with human resources) Paragraph III.C.2 [1].
7. **Test key controls, systems and procedures regularly, at a frequency the risk assessment sets, with the tests conducted or reviewed by independent third parties or by staff independent of those who develop or maintain the program.** (Internal audit or an independent testing team) Paragraph III.C.3 [1].
8. **Put disposal measures for customer information and consumer information into the program.** (Records management) Paragraph III.C.4 requires appropriate disposal measures, and paragraph II.B.4 makes proper disposal an objective. Consumer information, under I.C.2.b, is information from or derived from a consumer report [1].
9. **For each service provider with access to customer or consumer information, record the due diligence, require security measures by contract, and monitor it where the risk assessment calls for it, reviewing its audits or test results.** (Third-party risk management) Paragraph III.D.1 to 3 requires appropriate due diligence in selecting providers, contract terms and, where the risk assessment indicates, monitoring that should include reviewing audits, summaries of test results or equivalent evaluations [1]. Recording the due diligence is our suggestion. Supplement A adds that the contract should require the provider to act on incidents of unauthorized access to the bank’s customer information, including notifying the bank as soon as possible [1].
10. **Review and adjust the program when technology, threats, the sensitivity of customer information or business arrangements change, including mergers, joint ventures and new outsourcing.** (Chief Information Security Officer) Paragraph III.E [1].
11. **Report to the board or a board committee at least annually on the program’s overall status and compliance with the guidelines, covering the topics the guidelines list.** (Chief Information Security Officer) Paragraph III.F requires at least annual reporting and says the report should discuss material matters such as risk assessment, risk management and control decisions, service provider arrangements, test results, security breaches or violations and management’s responses, and recommended changes [1].
12. **Write a response program for unauthorized access to customer information that covers assessing scope, notifying the primary federal regulator as soon as possible for incidents involving sensitive customer information, notifying law enforcement as well as filing a timely SAR when a federal criminal violation needs immediate attention, containing the incident while preserving evidence, and notifying customers when warranted.** (Incident response lead) Supplement A, paragraph II.A.1.a to e, lists these as the minimum procedures; II.A.2 says the bank stays responsible for notifying its customers and regulator when the incident is at a service provider, though it may contract with the provider to notify on its behalf [1]. The notice under section 53.3, due to the OCC no later than 36 hours after the bank determines that a notification incident has occurred, can apply to the same event on its own terms [2].
13. **Set the test and content for customer notice: investigate promptly, notify affected customers as soon as possible when misuse has occurred or is reasonably possible, and include the elements the guidance lists.** (Incident response lead with customer communications) Supplement A, paragraph III.A, sets the standard and allows delay at a law enforcement agency’s written request; III.A.1 defines sensitive customer information; III.B lists the content, including a general description of the incident, a telephone number for help and a reminder to stay vigilant over the next twelve to twenty-four months; III.C covers delivery [1].

## Sources

1. Electronic Code of Federal Regulations. 12 CFR part 30, Safety and Soundness Standards, including appendix B and Supplement A (current text, checked November 14, 2026). <https://www.ecfr.gov/current/title-12/part-30> Checked November 14, 2026.
2. Electronic Code of Federal Regulations. 12 CFR part 53, Computer-Security Incident Notification (current text, checked November 14, 2026). <https://www.ecfr.gov/current/title-12/part-53> Checked November 14, 2026.

Published: November 14, 2026
Canonical URL: <https://insights.moraph.com/checklist-occ-information-security-guidelines-part-30-appendix-b>
Publisher: Moraph Insights
