Back to Resources
GLBA Safeguards Rule Checklist: visual preview
Checklist

GLBA Safeguards Rule Checklist

Financial Institution Data Security Compliance

Overview

The FTC enforces the Gramm-Leach-Bliley Act (GLBA) Safeguards Rule. The original version was short and vague: have an information security program, develop it, implement it, maintain it. The amendments that took effect in 2023 spelled out what the program must contain, down to who runs it (a Qualified Individual) and what that person tells the board each year in writing. MFA, encryption, a written risk assessment and regular testing are now explicit. A later amendment made certain security incidents reportable to the FTC itself.

Banks mostly answer to their own regulators, so the rule really bites on mortgage brokers, auto dealers, tax preparers and the like. Many of them have no security staff at all, which is exactly why the FTC wrote the requirements down.

Who Must Comply

  • The FTC reads "financial institution" broadly. If you are on this list, the rule applies:
  • Mortgage lenders and brokers
  • Payday lenders, finance companies
  • Account servicers, check cashers
  • Financial or investment advisors; tax preparation firms, including seasonal storefront preparers
  • Insurance companies, and travel agencies acting in a financial capacity
  • Real estate settlement services
  • Car dealerships that arrange financing
  • Colleges and universities in federal student loan programs
  • Retailers with their own store credit card

Key Requirements Under the 2023 Updates

RequirementDescription
Qualified IndividualA named person who oversees and runs the information security program
Written Risk AssessmentPeriodic, written assessment of foreseeable threats and of how well current safeguards hold up
Access ControlsAccess to customer information limited to people who need it, and reviewed periodically
Data InventoryA list of the systems, devices and data stores that hold or process customer data
EncryptionCustomer information encrypted in transit and at rest
MFAMulti-factor authentication for anyone accessing customer information
Disposal ProceduresCustomer information no longer needed is securely disposed of within two years
Change ManagementThe program is re-evaluated and adjusted when operations or systems change
MonitoringContinuous monitoring, or annual penetration testing plus semi-annual vulnerability assessments
Incident ResponseA written incident response plan, kept current
Board ReportingThe Qualified Individual reports in writing to the board at least annually

Building Your Information Security Program

Name your Qualified Individual first. No particular certification is required, but the person needs the knowledge to run the program and the authority to make people fix things. It can be an employee, someone at an affiliate or a service provider, and the institution stays responsible either way.

Then write the GLBA risk assessment. List the foreseeable internal and external threats (a stolen laptop, a phished loan officer, a vendor with standing VPN access, a former employee whose login still works), rate how sensitive each category of customer information is, and judge whether today's safeguards are enough. Be specific. Everything else in the program, from which systems get MFA first to what goes in the board report, should trace back to this document, and examiners or FTC staff will read it before anything else.

Implementation Priorities

  • Finish the data inventory, so you know which customer information you hold and where; include the shared drive full of scanned loan applications
  • Turn on MFA for every system that touches customer information, starting with email and remote access
  • Encrypt customer data at rest and in transit
  • Write access control rules on least privilege and run the first review
  • Choose continuous monitoring, or book the penetration test and vulnerability scans
  • Write the incident response plan with named roles, a call tree and the notification steps, including notice to the FTC where required
  • Set up service provider oversight, with security requirements written into contracts
  • Train staff at onboarding and annually, and keep the attendance records
  • Schedule the annual written report to the board and keep a copy

Enforcement and Consequences

The FTC enforces the Safeguards Rule through investigations, consent orders and public enforcement actions, and state attorneys general can act as well. FTC consent orders commonly run for 20 years and impose ongoing compliance monitoring and assessments, which is a long time to have a regulator reading your security reports. A breach of customer financial data also triggers state breach notification laws, invites class action litigation, and costs trust that a financial services firm does not easily win back.

Frequently asked questions

© 2026 Hunto AI. All rights reserved.