Data Protection & Privacy

GLBA Safeguards Rule

GLBA Safeguards Rule framework badge
Summarize with
ClaudeChatGPTPerplexityGoogle AI Mode
In this article
At a Glance
GLBA Safeguards Rule (16 CFR Part 314)
  • Classification
    Category
    Data Protection & Privacy
    Domain
    Financial Services Regulation
    Framework Family
    Global Privacy Regulations
  • Regulatory Context
    Type
    Regulation
    Legal Instrument
    Regulation
    Sector
    Financial Sector
    Industry
    Financial Services
  • Region / Publisher
    Region
    North America
    Region Detail
    United States
    Publisher
    Federal Trade Commission (rule); statute enacted by the United States Congress (15 U.S.C. 6801, Pub. L. 106-102)
  • Versioning
    Version
    16 CFR Part 314, as amended at 86 FR 70272 (2021) and 88 FR 77499 (2023)
    Effective Date
    June 9, 2023 (amended rule in full); section 314.4(j) notification from May 13, 2024
    Issue Date
    December 9, 2021 (amended rule); notification amendment November 13, 2023
  • Adoption
    Adoption Model
    Regulatory Compliance
    Implementation Complexity
    High
  • Official Reference
License Information

License included / downloadable: Yes

The Safeguards Rule is a U.S. federal regulation published free in the Code of Federal Regulations and on the FTC's site; the platform links to the official text.

Framework text is licensed by its publisher and is included only where stated above.

Official Resources
GLBA Safeguards Rule Overview
Describes the key requirements and implementation of the GLBA Safeguards Rule.
FTC Business Guidance on Security
Provides guidance on implementing security practices in line with FTC regulations.
FTC Guidance on Information Security Programs
Outlines how to create and maintain information security programs under the GLBA.
Key takeaways
  • The GLBA Safeguards Rule (16 CFR Part 314) requires non-bank financial institutions under FTC jurisdiction to run a written information security program.
  • The amended rule has applied in full since June 9, 2023, and the FTC notification duty in section 314.4(j) since May 13, 2024.
  • Covered businesses include mortgage lenders, payday lenders, finance companies, collection agencies, tax preparers, and non-federally insured credit unions.
  • Named controls include encryption, multi-factor authentication, disposal within two years, annual penetration testing, and six-monthly vulnerability assessments.
  • A covered institution designates a Qualified Individual and writes a risk assessment.

Overview

The GLBA Safeguards Rule (16 CFR Part 314, Standards for Safeguarding Customer Information) is the Federal Trade Commission regulation that requires every financial institution under FTC jurisdiction to develop, implement and maintain a written information security program with the elements listed in section 314.4. The amended rule has applied in full since June 9, 2023, and the FTC notification duty in section 314.4(j) since May 13, 2024.

The FTC issued the rule under sections 501(b) and 505(b)(2) of the Gramm-Leach-Bliley Act (15 U.S.C. 6801(b) and 6805(b)(2)), which Congress enacted on November 12, 1999. The original rule dates from May 23, 2002 (67 FR 36493); the FTC rewrote it on December 9, 2021 (86 FR 70272), delayed the applicability of the new elements from December 9, 2022 to June 9, 2023, and added the notification requirement on November 13, 2023 (88 FR 77499). Section 314.1(b) names the covered businesses: mortgage lenders, payday lenders, finance companies, mortgage brokers, account servicers, check cashers, wire transferors, collection agencies, credit counselors and other financial advisors, tax preparation firms, non-federally insured credit unions, investment advisors not required to register with the SEC and entities acting as finders. Banks, credit unions and SEC registrants follow their own regulators under 15 U.S.C. 6805.

A covered institution designates a Qualified Individual, writes a risk assessment, implements the eight safeguards in section 314.4(c), tests them, trains staff, oversees service providers, keeps a written incident response plan, reports to the board at least annually and notifies the FTC within 30 days when a notification event affects 500 or more consumers.

Why does it matter?

The Safeguards Rule is the federal security standard for non-bank financial businesses, and since 2021 it has named the controls instead of leaving them to judgment: encryption, multi-factor authentication, disposal within two years, annual penetration testing and six-monthly vulnerability assessments. Since May 13, 2024 the FTC also learns of larger breaches directly, through the section 314.4(j) notice that it publishes. A car dealer, mortgage broker or tax preparer that cannot show the written program, the Qualified Individual's annual report and the test results faces an FTC enforcement action under the rule and Section 5 of the FTC Act.

Key benefits include:

  • A named set of safeguards

Section 314.4(c)(1) to (8) lists access controls, an inventory of data and systems, encryption in transit and at rest, secure development, multi-factor authentication, disposal and retention, change management and activity logging.

  • One accountable person

Section 314.4(a) requires a Qualified Individual to oversee, implement and enforce the program, with a senior staff member overseeing any outside provider that fills the role.

  • Evidence examiners can read

A written risk assessment (314.4(b)), test results (314.4(d)), service provider assessments (314.4(f)) and a written incident response plan (314.4(h)) are all required documents.

  • Board visibility

The Qualified Individual reports in writing to the board or governing body at least annually under section 314.4(i), covering program status, risk decisions, test results and security events.

  • A fixed breach clock

A notification event involving at least 500 consumers must be reported to the FTC as soon as possible and no later than 30 days after discovery (314.4(j)).

How does it work?

Section 314.3 sets the frame: a comprehensive information security program, written in one or more readily accessible parts, with administrative, technical and physical safeguards appropriate to the institution's size and complexity, the nature and scope of its activities and the sensitivity of the customer information. Its objectives follow the statute: to ensure the security and confidentiality of customer information, to protect against anticipated threats or hazards to its security or integrity, and to protect against unauthorized access to or use of it that could result in substantial harm or inconvenience to any customer.

Section 314.4 lists the elements. The Qualified Individual (a) runs the program. The written risk assessment (b) identifies reasonably foreseeable internal and external risks and the criteria for rating them. The safeguards (c) are the eight controls, including encryption of customer information in transit over external networks and at rest, multi-factor authentication for anyone accessing an information system and secure disposal no later than two years after the last use unless retention is needed. Testing (d) means continuous monitoring or annual penetration testing plus vulnerability assessments at least every six months. Training (e), service providers (f), program adjustment (g), the incident response plan (h) and the annual board report (i) complete the list.

Section 314.4(j), effective May 13, 2024, requires electronic notice to the FTC on its form for any notification event involving at least 500 consumers: the institution's name and contact details, the types of information involved, the date or date range, the number of consumers affected and a general description, plus whether a law enforcement official has determined in writing that public notice would impede an investigation. The FTC publishes these notices. Section 314.6 exempts institutions holding information on fewer than 5,000 consumers from the written risk assessment, the continuous monitoring or penetration testing requirement in 314.4(d)(2), the incident response plan and the annual board report.

Key Elements

  • Qualified Individual (314.4(a))

One person, who may be an employee, an affiliate's employee or a service provider's employee, oversees the program; the institution stays responsible and designates a senior staff member to oversee an outside provider.

  • Written risk assessment (314.4(b))

Identifies reasonably foreseeable risks to customer information, assesses existing safeguards, sets criteria for rating risks and for confidentiality, integrity and availability, and is reassessed periodically.

  • Eight safeguards (314.4(c))

Access controls, data and system inventory, encryption, secure development practices, multi-factor authentication, disposal and retention, change management, and monitoring and logging of user activity.

  • Testing, training and service providers (314.4(d) to (f))

Continuous monitoring or annual penetration tests and six-monthly vulnerability assessments; security awareness training; contractual safeguards and periodic assessment of service providers.

  • Incident response plan and board report (314.4(h) and (i))

A written plan covering goals, processes, roles, communications, remediation, documentation and post-event revision; a written report to the board at least annually.

  • Notification events (314.2 and 314.4(j))

Unauthorized acquisition of unencrypted customer information, presumed from unauthorized access unless reliable evidence shows otherwise; FTC notice within 30 days when 500 or more consumers are involved.

What does it cover?

The rule applies to the handling of customer information by every financial institution over which the FTC has jurisdiction under section 505 of the Gramm-Leach-Bliley Act (15 U.S.C. 6805(a)(7)), that is, businesses significantly engaged in activities that are financial in nature under section 4(k) of the Bank Holding Company Act and not supervised by a federal banking agency, the NCUA, the SEC or a state insurance authority. Section 314.1(b) gives the examples, from mortgage lenders and payday lenders to tax preparation firms and finders. It covers all customer information in the institution's possession, including information about other institutions' customers, in any form.

What are its objectives?

The Safeguards Rule exists to carry out the objectives Congress set in 15 U.S.C. 6801(b).

Ensure the security and confidentiality of customer records and information.

Protect against any anticipated threats or hazards to the security or integrity of such records.

Protect against unauthorized access to or use of such records or information that could result in substantial harm or inconvenience to any customer.

Make one accountable person, a written program and periodic testing the proof of those outcomes.

Give the FTC prompt notice of larger breaches through section 314.4(j).

Framework in Context

The Safeguards Rule is the FTC's half of the GLBA security regime; banks, savings associations and credit unions follow the Interagency Guidelines Establishing Information Security Standards and the FFIEC IT Handbook, and SEC registrants follow Regulation S-P, which the SEC amended in 2024 with its own incident response and notification duties. The 2021 rewrite drew its structure from the New York Department of Financial Services' 23 NYCRR 500, and its eight safeguards line up with the NIST Cybersecurity Framework and ISO/IEC 27001 controls, which is why a single control set serves the rule, a SOC 2 report and state privacy laws. The FTC's companion Privacy Rule (16 CFR Part 313) and the FTC Act's Section 5 supply the enforcement backdrop.

Common Framework Mappings

Organizations map the Safeguards Rule's elements to the frameworks below so that the same safeguards, tests and evidence serve the FTC, auditors and other regulators.

Mapped frameworks include:

CIS Controls v8.1

EU DORA

FFIEC CAT

ISO 27001:2022

ISO 27701

NIST CSF 2.0

NIST 800-53 Rev.5

SOC 2

SMARTSUITE

How SmartSuite Supports the GLBA Safeguards Rule

SmartSuite provides the system for managing controls, evidence, mappings, assessments, and reporting.

Use Compliance Management to hold the section 314.4 elements as requirements, each linked to the policy, control and evidence that satisfies it, with the Qualified Individual as owner, the testing cadence the rule fixes and the 30-day notification clock built into the incident workflow.

Section 314.4 Requirement Library

Load elements (a) to (j) and the eight safeguards in (c) as requirements with owners, implementation status and linked evidence.

Written Risk Assessment

Run the 314.4(b) assessment as a record with rating criteria, identified risks, existing safeguards and the periodic reassessment schedule.

Testing Calendar

Schedule annual penetration tests and six-monthly vulnerability assessments, or log continuous monitoring, and attach results to the controls tested (314.4(d)).

Service Provider Oversight

Track each provider's contractual safeguards, risk rating and periodic assessment under 314.4(f) in Third Party Risk Management.

Incident Response and FTC Notification

Run the 314.4(h) plan with discovery date, consumer count, the 30-day deadline for the 314.4(j) notice, law enforcement delay requests and the submitted form.

Annual Board Report

Assemble the Qualified Individual's written report to the board from the same records: program status, risk decisions, provider arrangements, test results and security events.

Related frameworks

CIS Controls v8.1

CIS Controls v8.1 is a prioritized set of 18 Controls and 153 Safeguards, in three Implementation Groups, with a new Govern function.

EU DORA

DORA (Regulation (EU) 2022/2554) requires EU financial entities to manage ICT risk, report major incidents, test resilience and control ICT third-party risk, applying from January 17, 2025.

CRI Profile

The CRI Profile is a voluntary cyber risk framework for financial institutions, built on NIST CSF 2.0, with 318 diagnostic statements, four impact tiers and about 40 regulatory mappings.

ISO 27001:2022

ISO/IEC 27001:2022 specifies requirements for an information security management system: Clauses 4 to 10, risk treatment, the Statement of Applicability and 93 Annex A controls.

ISO 27701

ISO/IEC 27701:2025 specifies requirements for a stand-alone privacy information management system (PIMS) for PII controllers and processors, replacing the 2019 edition.

NIST CSF 2.0

NIST CSF 2.0 (CSWP 29, February 26, 2024) is the voluntary cybersecurity framework with six Functions including Govern, 22 Categories, 106 Subcategories, Profiles and Tiers.

NIST 800-53 Rev.5

NIST SP 800-53 Rev. 5 is the NIST catalog of security and privacy controls in 20 families, mandatory for federal systems under OMB A-130 and FISMA; Release 5.2.0 issued August 27, 2025.

SOC 2

SOC 2 is the AICPA examination, under AT-C 105 and 205, of a service organization's controls against the 2017 Trust Services Criteria, issued as a type 1 or type 2 attestation report.

FAQ

Frequently Asked Questions For GLBA Safeguards Rule (Gramm-Leach-Bliley Act, 16 CFR Part 314)

Financial institutions under FTC jurisdiction, meaning businesses significantly engaged in financial activities that no other GLBA regulator supervises (15 U.S.C. 6805(a)(7)). Section 314.1(b) lists examples: mortgage lenders and brokers, payday lenders, finance companies, account servicers, check cashers, wire transferors, collection agencies, credit counselors and other financial advisors, tax preparation firms, non-federally insured credit unions, investment advisors not required to register with the SEC and finders. Banks and credit unions follow their own regulators.

Access controls that limit users to the information they need; an inventory of data, personnel, devices, systems and facilities; encryption of customer information in transit over external networks and at rest; secure development practices; multi-factor authentication for anyone accessing information systems; secure disposal no later than two years after last use unless retention is required; change management procedures; and monitoring and logging of authorized users' activity to detect unauthorized access.

Section 314.4(d) requires regular testing or monitoring of key controls. An institution may run continuous monitoring; otherwise it must conduct annual penetration testing and vulnerability assessments at least every six months, and again after material changes to operations or business arrangements. Institutions holding information on fewer than 5,000 consumers are exempt from the 314.4(d)(2) cadence under section 314.6.

Since May 13, 2024, section 314.4(j) requires notice to the FTC as soon as possible and no later than 30 days after discovery of a notification event involving at least 500 consumers. A notification event is unauthorized acquisition of unencrypted customer information, and unauthorized access is presumed to be acquisition unless reliable evidence shows otherwise. The notice is filed on the FTC's online form and published, unless a law enforcement official requests a delay of up to 30 days, extendable by 60.

The December 9, 2021 final rule (86 FR 70272) added the Qualified Individual, the written risk assessment, the eight named safeguards, the testing cadence, training, service provider assessment, the written incident response plan and the annual board report, and added finders to the definition of financial institution. It took effect January 10, 2022, and the FTC delayed the applicability of the new elements from December 9, 2022 to June 9, 2023.

Put this framework to work in SmartSuite

Manage controls, risks, evidence, and audits in one platform designed for modern governance, risk, and compliance.