Meet the GLBA Safeguards Rule with evidence you can show the FTC
The GLBA Safeguards Rule (16 CFR Part 314) is the Federal Trade Commission regulation that requires non-bank financial institutions to develop, implement and maintain a written information security programme protecting customer information.
- Issued by
- Federal Trade Commission (FTC)
- Legal basis
- Gramm-Leach-Bliley Act of 1999
- Major amendments
- Most 2021 amendments in force since 9 June 2023; FTC notification requirement since 13 May 2024
- Applies to
- Non-bank financial institutions under FTC jurisdiction
Is the GLBA Safeguards Rule right for your organisation?
4 sets out the required elements, including a Qualified Individual, written risk assessments, access controls, encryption, multi-factor authentication, testing, incident response and annual reporting to the board. Since 13 May 2024 it also requires notice to the FTC of certain security events.
Any financial institution within the FTC's jurisdiction under the Gramm-Leach-Bliley Act must comply, which covers non-bank businesses such as mortgage lenders and brokers, auto dealers that arrange financing, payday lenders, tax preparers, collection agencies and many fintech companies. Institutions holding customer information on fewer than 5,000 consumers are exempt from some elements, but not from the core programme, encryption, MFA or FTC notification. Service providers to these firms are often asked to show equivalent safeguards by contract.
How OneClickComply helps with the GLBA Safeguards Rule
OneClickComply supports the Safeguards Rule today. The 314.4 elements map to controls that share evidence with ISO 27001 and SOC 2, so automated evidence collection, AutoComplete policies and continuous monitoring cover MFA, encryption, access reviews and logging. Our in-house audit team can help you prepare the written risk assessment, incident response plan and annual board report.
Requirements covered
Six sections, with the information security programme elements set out in section 314.4 paragraphs (a) to (j) and small-institution exceptions in section 314.6.
Manual GLBA Safeguards Rule compliance vs OneClickComply
Doing it manually
- Working out which 314.4 elements apply and what counts as reasonable evidence
- Writing the risk assessment, security programme and incident response plan from blank templates
- Chasing screenshots to prove MFA, encryption and access reviews are in place
- Tracking service providers, contracts and periodic assessments in spreadsheets
- Pulling together the annual written report to the board at the last minute
With OneClickComply
- Each 314.4 element is mapped to clear controls, with guidance from our auditors
- Policies are generated from your real environment and ready for review
- Evidence for MFA, encryption and access is collected automatically and kept current
- Vendor records, contracts and reviews live in one register with reminders
- Board reporting draws on live control status, risks and incidents
Everything you need for the GLBA Safeguards Rule
Safeguards Rule controls mapped to ISO 27001 and SOC 2 so evidence counts once across all
Automated evidence for MFA, encryption and access controls from cloud and identity tools
AutoComplete policies for the written security programme and incident response plan
Continuous monitoring and change logging with alerts when safeguards drift
Vendor risk management to select, contract and periodically assess service providers
Penetration testing and expert guidance from our in-house audit team
Three steps to GLBA Safeguards Rule compliance
Connect and scan
Connect your cloud, identity and SaaS tools. OneClickComply checks them against the GLBA Safeguards Rule and shows which controls pass and which fail.
Fix and generate
OneClickFix fixes supported misconfigurations automatically, and AutoComplete drafts GLBA Safeguards Rule policies from your real environment.
Monitor and evidence
Continuous monitoring flags drift as it happens, and our in-house audit team is on hand when you need expert guidance.
See how far your current setup is from the GLBA Safeguards Rule.
FTC Safeguards Rule (GLBA, 16 CFR Part 314) requirements
All six sections of 16 CFR Part 314, with the section 314.4 programme elements broken out by paragraph and sub-points merged into their parent requirement.
| Reference | Requirement |
|---|---|
| 314.1 | Purpose and scope |
| 314.2 | Definitions |
| 314.3(a) | Information security program |
| 314.3(b) | Objectives of the information security program |
| 314.4(a) | Designate a Qualified Individual |
| 314.4(b)(1) | Written risk assessment |
| 314.4(b)(2) | Periodic additional risk assessments |
| 314.4(c)(1) | Access controls |
| 314.4(c)(2) | Inventory of data, personnel, devices, systems and facilities |
| 314.4(c)(3) | Encryption of customer information in transit and at rest |
| 314.4(c)(4) | Secure development and assessment of applications |
| 314.4(c)(5) | Multi-factor authentication |
| 314.4(c)(6)(i) | Secure disposal of customer information |
| 314.4(c)(6)(ii) | Periodic review of data retention policy |
| 314.4(c)(7) | Change management procedures |
| 314.4(c)(8) | Monitoring and logging of authorised user activity |
| 314.4(d)(1) | Regular testing or monitoring of safeguards |
| 314.4(d)(2) | Continuous monitoring or penetration testing and vulnerability assessments |
| 314.4(e)(1) | Security awareness training |
| 314.4(e)(2) | Qualified information security personnel |
Always check the official text of the GLBA Safeguards Rule for the exact wording.
GLBA Safeguards Rule questions, answered
Can't find what you need? Our in-house auditors can talk you through the GLBA Safeguards Rule on a 30-minute call.
What is the FTC Safeguards Rule?
The FTC Safeguards Rule is a federal regulation at 16 CFR Part 314, issued under the Gramm-Leach-Bliley Act, that requires non-bank financial institutions to keep a written information security programme protecting customer information. The programme must include administrative, technical and physical safeguards appropriate to the size and complexity of the business, the nature of its activities and the sensitivity of the customer information it holds.
Who must comply with the GLBA Safeguards Rule?
Financial institutions under the FTC's jurisdiction must comply. These are mainly non-bank businesses significantly engaged in financial activities, such as mortgage lenders and brokers, auto dealers offering financing, payday lenders, tax preparers, collection agencies, non-bank lenders and many fintech firms. Banks and credit unions are generally covered by their own banking regulators' safeguards guidelines instead of the FTC rule.
What are the main requirements of the Safeguards Rule?
Section 314.4 requires a Qualified Individual to oversee the programme, a written risk assessment, safeguards including access controls, a data and systems inventory, encryption, secure development, multi-factor authentication, secure disposal, change management and activity logging. Firms must also test safeguards, train staff, oversee service providers, keep a written incident response plan, report to the board at least annually and notify the FTC of qualifying security events.
When must a business notify the FTC of a data breach?
Since 13 May 2024, a covered financial institution must notify the FTC as soon as possible, and no later than 30 days after discovery, of a notification event involving the information of at least 500 consumers. A notification event is the acquisition of unencrypted customer information without the authorisation of the individual it relates to. Notice is submitted electronically using the FTC's online form.
Are small businesses exempt from the Safeguards Rule?
Only partly. Institutions that maintain customer information on fewer than 5,000 consumers are exempt from the written risk assessment, penetration testing and vulnerability scanning, written incident response plan and annual board report requirements. They must still run an information security programme with a Qualified Individual, access controls, encryption, multi-factor authentication, staff training, service provider oversight and FTC breach notification.
How does the Safeguards Rule relate to ISO 27001 and SOC 2?
The Safeguards Rule is a legal requirement, while ISO 27001 and SOC 2 are voluntary frameworks, but they overlap heavily. Risk assessment, access control, encryption, MFA, logging, change management, vendor oversight and incident response appear in all three. An organisation with a mature ISO 27001 or SOC 2 programme will already meet much of section 314.4, though rule-specific items such as FTC notification and board reporting still need attention.
Is there a GLBA Safeguards Rule certification?
No. There is no official certification or audit scheme for the Safeguards Rule. Each institution is responsible for maintaining its own programme and evidence, and the FTC enforces compliance through investigations and enforcement actions. Many firms use an independent assessment, penetration test or an ISO 27001 or SOC 2 report to demonstrate their safeguards to partners and examiners.
Does OneClickComply support the GLBA Safeguards Rule?
Yes. The Safeguards Rule is supported in OneClickComply today. Its requirements share controls and evidence with frameworks such as ISO 27001 and SOC 2, and our in-house audit team can guide you through the risk assessment, incident response plan and board reporting. OneClickComply does not certify compliance or guarantee the outcome of an FTC review.
Related frameworks
- NYDFS Cybersecurity Regulation (23 NYCRR Part 500)Regulation · United States
- FCA Cyber Risk Management Rule (12 CFR Part 609)Regulation · United States
- SEC Cybersecurity Disclosure RuleRegulation · United States
- NAIC Insurance Data Security Model Law (MDL-668)Law · United States
- Sarbanes-Oxley ActLaw · United States
- Digital Operational Resilience Act (DORA)Regulation · EU
- BAIT (BaFin Supervisory Requirements for IT)Regulation · Germany
- BMA Insurance Sector Operational Cyber Risk Management Code of ConductRegulation · Bermuda
What powers GLBA Safeguards Rule compliance
Start working towards the GLBA Safeguards Rule
Automate controls, gather evidence continuously and stay audit-ready, all on one platform.