GLBA Requirements: Privacy, Safeguards and Pretexting Rules
Published · Last updated · 8 min read

The Gramm-Leach-Bliley Act (GLBA) requires financial institutions, a group that includes banks, credit unions, lenders, tax preparers, many accounting firms and other non-bank firms, to explain how they share customers' personal financial information, let customers opt out of some sharing, and protect that information with a written security program. Its three main parts are the Privacy Rule, the Safeguards Rule and the pretexting provisions.
Key takeaways
- GLBA has three parts: the Privacy Rule (notices and opt-outs), the Safeguards Rule (a written information security program) and pretexting protections.
- Which agency enforces GLBA depends on the firm: the FTC for most non-bank financial institutions, banking regulators for banks and credit unions, and the SEC for registered investment advisers and broker-dealers.
- For FTC-regulated firms, the Safeguards Rule at 16 CFR Part 314 sets specific controls and, since May 13, 2024, a 30-day FTC notice for events involving 500 or more consumers.
- An annual privacy notice is not required if you share only under the rule's exceptions and your practices have not changed.
- Firms with customer information on fewer than 5,000 consumers are exempt from a few Safeguards Rule requirements, but not from having a written program.
What is the Gramm-Leach-Bliley Act?
The Gramm-Leach-Bliley Act is a 1999 federal law that modernized the financial industry and, in Title V, created privacy and security duties for "financial institutions," meaning businesses significantly engaged in financial activities. The privacy and security sections apply far beyond banks.
GLBA protects "nonpublic personal information," broadly the personally identifiable financial information a firm collects to provide a financial product or service, such as account numbers, income, tax return data and Social Security numbers. That is why a CPA firm preparing individual tax returns, a mortgage broker or a wealth manager can all fall under it.
Who has to comply with GLBA?
If your business provides financial products or services to individuals, assume GLBA applies until you confirm otherwise. Common examples include:
- Banks, savings associations and credit unions.
- Mortgage lenders and brokers, auto lenders and finance companies.
- Tax preparers and accounting firms that prepare individual returns or provide financial advice.
- Investment advisers, broker-dealers and insurance companies, each under its own regulator.
- Collection agencies, payday lenders and other non-bank lenders.
Who enforces the rules matters. The FTC covers most non-bank financial institutions, including tax preparers and many accounting firms. Banks and credit unions follow interagency guidelines from their federal regulators, coordinated through the FFIEC. Registered investment advisers and broker-dealers follow the SEC's Regulation S-P. Insurance companies are largely regulated by the states.
What does the GLBA Privacy Rule require?
The Privacy Rule, implemented for most institutions by the CFPB's Regulation P at 12 CFR Part 1016, is about transparency and choice:
- Privacy notices. Give customers a clear notice describing what information you collect, whom you share it with and how you protect it, when the customer relationship begins.
- Opt-out rights. If you share nonpublic personal information with nonaffiliated third parties outside the rule's exceptions, customers must be told and given a reasonable way to opt out.
- Limits on reuse. Information received from another financial institution can only be reused or redisclosed within limits.
Annual notices are no longer required in every case. Under the exception in 12 CFR 1016.5(e), you do not have to send an annual privacy notice if you share only under the rule's exceptions (for example, with service providers or as required by law) and your sharing policies have not changed since your last notice.
What does the GLBA Safeguards Rule require?
The Safeguards Rule requires a written information security program with administrative, technical and physical safeguards that fit your size and the sensitivity of the data. For FTC-regulated firms the rule is 16 CFR Part 314, which was amended in 2021, with most of the new requirements in force since June 9, 2023. Key elements include:
- A Qualified Individual who oversees the program.
- A written risk assessment.
- Access controls, encryption of customer information in transit and at rest, and multi-factor authentication for anyone accessing information systems.
- Continuous monitoring, or annual penetration testing plus vulnerability assessments at least every six months.
- Security awareness training, service provider oversight, a written incident response plan and an annual written report to the board or senior officer.
Since May 13, 2024, the rule also requires notifying the FTC as soon as possible, and no later than 30 days after discovery, when a notification event involves the information of at least 500 consumers. Our FTC Safeguards Rule guide covers each element in detail, and our FTC Safeguards compliance support page explains how NorthStar helps.
What are GLBA's pretexting provisions?
Subtitle B of GLBA Title V makes it illegal to obtain, or try to obtain, a customer's financial information from a financial institution by false pretenses, such as impersonating the customer on the phone or using forged documents. It also prohibits asking someone else to do so.
For a firm, the practical duty is to make pretexting hard. Verify callers and email requests before changing account details, releasing documents or moving money, and train staff to recognize social engineering. Phone and email impersonation remains one of the most common ways attackers reach client data, so these checks belong in your written program and your security awareness training.
Are small financial firms exempt from any GLBA requirements?
Partly. Under 16 CFR 314.6, financial institutions that maintain customer information on fewer than 5,000 consumers do not have to meet four Safeguards Rule provisions: the written risk assessment, continuous monitoring or periodic penetration testing and vulnerability assessments, the written incident response plan, and the annual written report to the board.
That exemption is narrower than many firms assume. Small firms still need a written information security program, a Qualified Individual, access controls, encryption, MFA, training and service provider oversight. Most small firms also find that a basic risk assessment and an incident plan are the cheapest way to show the program is reasonable, even when they are not strictly required.
How do firms put GLBA into practice?
- Confirm your regulator and rules. FTC, banking regulator, SEC or state insurance department.
- Map customer data. Know where nonpublic personal information lives: tax software, document management, email, file shares, backups and paper.
- Review your privacy notice and sharing. Confirm the notice matches what you actually do and whether an annual notice is required.
- Write or update the security program. Name the Qualified Individual, complete a risk assessment, and document controls.
- Close the technical gaps. MFA, encryption, logging, patching, backups and access reviews.
- Oversee vendors. Choose service providers that can protect customer data, put requirements in contracts, and review them periodically.
- Plan for incidents. Include the 30-day FTC notice for events involving 500 or more consumers, alongside state breach laws. Our breach response guide for financial institutions covers the sequence.
What GLBA mistakes do regulators and auditors find most often?
- A program that exists only as a template. A downloaded policy that names no Qualified Individual and does not match your systems will not hold up after an incident.
- Customer data outside the program. Tax files in personal email, client folders on laptops without encryption, and old backups no one tracks.
- MFA with gaps. MFA on email but not on the tax or portfolio software, remote access or administrator accounts.
- No vendor oversight. No record of why a software or IT provider was chosen or how it protects customer data.
- No annual report. Firms above the 5,000-consumer threshold must give the board or a senior officer a written report on the program at least annually.
How can NorthStar help with GLBA requirements?
NorthStar works with accounting firms, advisers, lenders and other financial firms on the technical side of GLBA: risk assessments, MFA and encryption, monitoring, vendor reviews, incident planning and the evidence your Qualified Individual needs for the annual report. Learn more about our financial services IT and cybersecurity. We help firms meet and document their requirements; responsibility for compliance stays with the firm.
Start with our free security check, read how managed IT supports accounting firms, or browse more financial services resources.
What else do financial firms ask about GLBA?
Does GLBA apply to CPA firms?
Often, yes. Firms that prepare individual tax returns or provide other financial services to individuals are generally financial institutions under the FTC's GLBA rules, which brings in both the Privacy Rule and the Safeguards Rule.
Is GLBA the same as the FTC Safeguards Rule?
No. The Safeguards Rule is one part of GLBA. GLBA also includes the Privacy Rule, which covers notices and opt-outs, and the pretexting provisions.
Do we have to send a privacy notice every year?
Not always. Under 12 CFR 1016.5(e), no annual notice is required if you share information only under the rule's exceptions and your policies have not changed since your last notice.
What happens after a breach under GLBA?
For FTC-regulated firms, a notification event involving at least 500 consumers must be reported to the FTC no later than 30 days after discovery. State breach notification laws and other regulators may add their own requirements.
Sources
- 16 CFR Part 314, Standards for Safeguarding Customer Information
- 12 CFR Part 1016, Regulation P (Privacy of Consumer Financial Information)
- CFPB: Regulation P overview
- 16 CFR Part 313, FTC Privacy Rule
Industry Resources
Financial Services IT & Cybersecurity
NorthStar helps financial firms build and document GLBA and FTC Safeguards programs, from risk assessments to MFA, encryption and incident planning.
Learn More →About the author

Ken Satkunam, CISM
President & Founder, NorthStar Technology Group
Ken has spent over 25 years in IT leadership, serving in roles from technical support to CIO for organizations as large as 23,000 employees. He founded NorthStar Technology Group in 2000 to help regulated organizations build secure, compliant, and operationally resilient technology environments. Ken holds the Certified Information Security Manager (CISM) credential from ISACA and is the co-author of the Amazon best-seller "Cyber Attack Prevention." He has been quoted in industry publications including eWeek and DM News, and NorthStar has been recognized on the Inc. 5000 list in both 2024 and 2025.