
Gramm-Leach-Bliley Act (GLBA) Explained: Privacy, Safeguards, and Compliance
If your business touches customer financial information, the Gramm-Leach-Bliley Act is not optional background reading. It is the federal law that tells financial institutions how to explain their privacy practices, limit sharing, and protect sensitive customer data. This guide explains what the Gramm-Leach-Bliley Act requires, who must comply, how the Financial Privacy Rule and the Safeguards Rule work, what changed in the 2023 Safeguards Rule updates, and what penalties apply when institutions fall short.
What Is the Gramm-Leach-Bliley Act?
The Gramm-Leach-Bliley Act, often shortened to GLBA and also known as the Financial Services Modernization Act of 1999, was signed into law on November 12, 1999. It modernized financial services by allowing banks, securities firms, and insurance companies to affiliate, while adding new consumer privacy protections in Title V. The central idea is simple: a company that collects personal financial information must be transparent about what it collects, how it shares it, and how it protects it.
GLBA protects what regulators call nonpublic personal information. That includes a person’s name, address, Social Security number, account numbers, payment history, credit history, and income, where that information is not publicly available. Most data gathered during a loan application, account opening, or insurance sale will qualify.
Who Must Comply With GLBA?
GLBA applies to financial institutions, a term broader than many people expect. It covers banks, credit unions, mortgage lenders, loan brokers, insurance companies, investment advisers, tax preparers, debt collectors, real estate appraisers, and retailers that issue their own credit cards. The test is functional: if a business is significantly engaged in providing financial products or services to consumers, it is likely covered.
That breadth surprises smaller firms. A car dealer that arranges financing, a college that participates in federal student aid, and a fintech company that processes payments can all be financial institutions for GLBA purposes. Service providers that receive customer information from a covered institution must also protect it under contract.
The Financial Privacy Rule
The Financial Privacy Rule, implemented by the Federal Trade Commission in 16 CFR Part 313 and by other regulators for the institutions they supervise, governs notices and sharing. A covered institution must give customers a clear privacy notice when the relationship begins and once a year after that, explaining the types of information collected, the categories of third parties with whom it may be shared, and the institution’s security practices.
The rule also gives consumers an opt-out right. Before sharing nonpublic personal information with a nonaffiliated third party, outside exceptions such as processing a transaction or complying with the law, the institution must give the consumer a reasonable chance to opt out. Notices must be clear and conspicuous, not buried in fine print.
The Safeguards Rule
While the Privacy Rule focuses on disclosure, the Safeguards Rule focuses on protection. It requires financial institutions to develop, implement, and maintain a comprehensive written information security program appropriate to the institution’s size, complexity, and the sensitivity of the customer information it holds. The program must identify reasonably foreseeable risks, design safeguards to control them, and regularly test and adjust those safeguards.
The rule is risk-based, not a fixed checklist of technologies. A small lender and a large bank will not have identical programs, but both must address access controls, encryption, employee training, vendor oversight, and incident response.
What Counts as a Safeguards Program?
A credible program starts with a designated qualified individual who oversees it, supported by senior leadership. It includes a written risk assessment, access controls that follow least privilege, multi-factor authentication for access to customer information, encryption of data in transit and at rest, secure development, and regular testing through vulnerability assessments or penetration testing. It also requires training, oversight of service providers, and a written incident response plan. For a broader view of how assurance programs are structured, see our guide to SOC 2 Type II, which covers a related but distinct framework for security controls.
Pretexting Protection
GLBA also includes a pretexting provision that makes it unlawful to obtain customer information from a financial institution under false pretenses. This targets social engineering: someone posing as a customer to trick a bank or its employees into disclosing account details. Institutions must train staff to verify identity, resist pressure tactics, and escalate suspicious requests.
Penalties and Enforcement
Enforcement comes from several regulators, including the FTC, the Consumer Financial Protection Bureau, and federal banking agencies, depending on the institution. Violations can lead to enforcement orders, civil penalties, and required remediation. The FTC has brought cases against companies that failed to maintain adequate safeguards, including cases where weak access controls or unencrypted data contributed to a breach.
Under the statute, criminal penalties can also apply for pretexting, with fines and imprisonment for knowing violations. Even without a headline fine, the cost of an enforcement action, mandatory audits, customer notification, and reputational damage can be substantial.
2023 Safeguards Rule Updates: What Changed
The FTC’s updated Safeguards Rule, with most strengthened requirements taking effect on June 9, 2023, made the rule far more prescriptive. Covered institutions must now designate a qualified individual, conduct a written risk assessment, and implement specific controls, including access controls, data inventory, encryption, secure application development, multi-factor authentication, and regular testing. The update also added requirements for employee training, vendor oversight, and periodic reporting to the board.
Another change arrived in 2024, when the FTC’s notification requirement took effect: institutions must notify the FTC as soon as possible, and no later than 30 days after discovery, when a security event involving at least 500 consumers is likely to result in unauthorized acquisition of unencrypted customer information.
Safeguards Rule Requirements Checklist
Use this checklist as a starting point for reviewing your own program. It reflects the FTC Safeguards Rule’s core elements, but it does not replace legal advice or a formal risk assessment.
| Requirement | What to do | Evidence to keep |
|---|---|---|
| Qualified individual | Designate one person or team to own the program | Appointment record and reporting lines |
| Written risk assessment | Identify risks to customer information and review it regularly | Dated assessment and risk register |
| Access controls | Apply least privilege and review access periodically | Access reviews and role definitions |
| Multi-factor authentication | Require it for access to customer information systems | Authentication configuration records |
| Encryption | Encrypt customer information in transit and at rest | Encryption standards and key management notes |
| Testing and monitoring | Test safeguards regularly and monitor for threats | Test reports and remediation tracking |
| Vendor oversight | Assess providers and require safeguards by contract | Vendor reviews and contract clauses |
| Training and incident response | Train staff and maintain a written response plan | Training logs and tested response plan |
GLBA and Cloud Security
Cloud adoption does not remove GLBA duties. A financial institution remains responsible for customer information even when it is stored or processed in the cloud, and it must oversee its cloud providers as service providers under the Safeguards Rule. That means reviewing provider security practices, controlling access, encrypting data, and planning for incident notification. Organizations handling regulated data in other sectors face similar discipline; for example, our explanation of what CJIS is shows how a different compliance framework also depends on access control, auditing, and incident handling.
Frequently Asked Questions
What is the Gramm-Leach-Bliley Act in simple terms?
It is a 1999 U.S. federal law requiring financial institutions to explain their privacy practices, give consumers a chance to opt out of certain sharing, and safeguard customer financial information.
Who does GLBA apply to?
It applies to financial institutions, including banks, lenders, insurers, investment firms, tax preparers, and other businesses significantly engaged in providing financial products or services to consumers.
What is the difference between the Privacy Rule and the Safeguards Rule?
The Privacy Rule governs privacy notices and opt-out rights for sharing information. The Safeguards Rule requires a written information security program to protect that information from unauthorized access and misuse.
What changed in the 2023 Safeguards Rule update?
The FTC added more specific requirements, including a qualified individual, a written risk assessment, multi-factor authentication, encryption, vendor oversight, training, and regular testing and board reporting.
What happens if a company violates GLBA?
Regulators can bring enforcement actions, impose civil penalties, and require remediation. Pretexting violations can also carry criminal penalties, and breaches can trigger notification and reputational costs.
Conclusion
The Gramm-Leach-Bliley Act remains a foundational privacy and security law for financial services. Its message has not changed since 1999, even as the technology has: tell customers honestly what you do with their information, give them control over certain sharing, and protect their data with a program that is written, tested, and actively overseen. Start with the checklist above, close the gaps your risk assessment reveals, and revisit the program at least annually.



[…] a deeper look at how another major privacy framework works, see our guide to the Gramm-Leach-Bliley Act (GLBA), which imposes similar safeguards duties on financial […]
[…] Secure the data. Apply the same reasonable safeguards you would to any sensitive data — encryption in transit and at rest, access controls and a breach plan. Financial services face similar safeguards requirements under the Gramm-Leach-Bliley Act (GLBA). […]