Here’s the short version: the FTC Safeguards Rule requires a written information security program for non-bank financial firms, with a named Qualified Individual, MFA, encryption, and a 30-day notice to the FTC if unencrypted customer information of 500 or more consumers is taken. It is not a bank-only rule, and it is not a logo you buy.
This is the practical map for a tax office, a mortgage shop, a dealership that writes loans, or a finder that sits between buyers and sellers. It is not legal advice. The text that controls is 16 CFR Part 314. The FTC’s own small-entity guide is FTC Safeguards Rule: What Your Business Needs to Know. If you want the work run as a program instead of a binder, start with compliance and security audits.
Who the FTC Safeguards Rule actually covers
People hear “financial institution” and picture a bank. The Rule uses the Gramm-Leach-Bliley definition, which follows the activity. The FTC’s guide lists examples in section 314.2: 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 that are not required to register with the SEC, and finders. Finders were added in the 2021 amendments. They bring buyers and sellers together. They do not have to close the deal themselves.
A few boundaries keep this page honest.
- A medical practice follows HIPAA, not this Rule, unless it also does a covered financial activity. Start at the HIPAA checklist for the clinic side.
- A law firm is not covered because it has a trust account. Coverage is about financial activities, not about being a professional office. Ask counsel before you build a Safeguards program you do not owe, or skip one you do.
- Banks and credit unions with a federal banking regulator are outside the FTC’s piece of GLBA. This page is the FTC rule.
- Auto dealers are a frequent Valley case. The FTC wrote a separate automobile dealer FAQ because financing and leasing pull many dealerships in. Read that before you assume the service department is exempt.
The program has to fit the size of the business, the work, and how sensitive the information is. A two-person tax office and a multi-rooftop dealer do not produce the same binder. They do produce a written program.

Name a Qualified Individual, then write the risk down
Section 314.4 is the list. The FTC guide walks it as nine elements. The order below is the order we implement it, not the order of the regulation letters.
The Qualified Individual implements and supervises the program. Employee or service provider. No required title. If we are the service provider, a senior person at your firm still supervises. The buck does not move to Canoga Park.
The risk assessment is written. It says what customer information you have, where it sits, and the foreseeable ways it is disclosed, misused, altered, or destroyed. “We use Microsoft 365” is not an inventory. Returns in a portal, deal jackets on a shared drive, credit applications in email, and paper in a cabinet are four stores. Revisit the assessment when the business changes, not on a vague anniversary.
Access, encryption, MFA, and disposal
These are the safeguards inside element (c). They are also the ones an insurer and a client questionnaire ask about before they ask about penetration tests.
| Safeguard | What “done” looks like | What we refuse to call done |
|---|---|---|
| Access control | Only people with a current need can open customer files, and that list is reviewed | A shared login for the whole office |
| Inventory | You can name the systems that hold customer information | A guess during the incident |
| Encryption | Customer information is encrypted on systems and in transit, or the Qualified Individual has approved a written alternative | A laptop with BitLocker “on some of them” |
| Apps | Third-party apps that touch customer information were looked at | Whatever the front desk installed |
| MFA | Anyone reaching customer information uses two factor types, unless the Qualified Individual approved an equivalent in writing | SMS on the bookkeeper and nothing on the portal |
| Disposal | Customer information is destroyed no later than two years after you last used it to serve that customer, unless a law or a real business need says keep it | A closet of old returns “just in case” |
| Change | A new server, portal, or store does not skip the program | Security frozen at the 2023 install |
| Logging | You can see authorized access and you look for access that is not | A log nobody opens |
MFA here matches the Rule’s definition: at least two of knowledge (a password), possession (a token or phone), and inherence (a biometric). That is the same control we describe in multi-factor authentication and, for Microsoft 365, in Conditional Access. The Rule does not care which product. It cares that the second factor is real and that any exception is written by the Qualified Individual.
Encryption at rest on Windows laptops is the BitLocker problem. Encryption in transit is TLS on the portal and on email paths that carry customer files, not a sticker that says the website is secure. If encryption is not feasible, the alternative has to be approved by the Qualified Individual. “We could not get to it” is not an approval.
Test, train, and watch vendors
If you do not continuously monitor the systems that hold customer information, the Rule’s testing clause is specific: annual penetration testing, plus vulnerability assessments that include system-wide scans at least every six months, and a test when something material changes. Firms under the 5,000-consumer line should confirm whether 314.6 excuses that cadence before they buy a test to satisfy a sentence that does not apply. Firms over the line should not replace the test with a vulnerability scan they never read.
Training is part of the program. General awareness for everyone, and a tighter brief for the people who actually run it. Our security awareness page is the habit. A once-a-year video with no look at the tax portal is a calendar entry.
Service providers that receive customer information need a contract that states the safeguards, a way for you to monitor them, and a periodic look at whether they still fit. That is vendor risk with a regulatory reason, not a spreadsheet hobby. Your Microsoft tenant, your tax software, your dealer management system, and the scanner company all belong on the list if they can see customer information.
Incident plan and the annual report
The written incident response plan has to cover goals, internal steps, who decides, communications inside and outside the firm, how you repair the weakness, how you document the event, and a post-incident revision of the plan. That lines up with a normal incident response plan. Write the Safeguards version so it names customer information, not only “the server.”
The Qualified Individual reports in writing, at least annually, to the board or, if you have no board, to a senior officer responsible for the program. The report covers compliance, risk decisions, service providers, test results, security events and the response, and recommended changes. A small firm can do this in a few pages. The failure mode is never having the meeting.

The 500-consumer notice to the FTC
The 2023 amendment, in effect since May 13, 2024, added notification. The FTC’s notification post states the trigger: unauthorized acquisition of unencrypted customer information of at least 500 consumers. Notify as soon as possible and no later than 30 days after discovery.
Three details get missed.
If the key was taken, encryption does not save the notice
If the encryption key was accessed, the information is treated as unencrypted. Encryption only helps the notice analysis if the key stayed protected.
Access is presumed to be acquisition
Unauthorized access to unencrypted customer information is presumed to be acquisition unless you have reliable evidence that it was not, and could not reasonably have been, taken.
The FTC form can become public
The report goes on the FTC’s form. The guide says the report can be made public, and that you can check a law-enforcement delay box if police have asked you not to publicize it yet. If you do not yet know the consumer count, you report what you know and update later. The rule text and the amendment history sit on the FTC’s Safeguards Rule page.
State breach notices, and IRS notifications for tax professionals, are additional. The FTC clock does not pause them. Cyber insurance applications ask about this program before a loss. The notice duty is why the incident plan cannot be a paragraph that says “call IT.”
Tax preparers and the WISP
The IRS tells tax professionals to protect client data with a written information security plan. Publication 4557 is the booklet they point at, and the overview page is Protect Your Clients; Protect Yourself. A tax preparation firm is also one of the FTC’s named examples of a financial institution.
Do not write two plans that disagree. One program can serve both readers if it names the Qualified Individual, the stores of client data (tax software, Microsoft 365, paper, portals), MFA, encryption, vendors, disposal, and the incident steps. A plan that says “we will implement MFA” while the tenant still has Security Defaults half-configured has not been implemented.
Disposal matters in a tax office. The Rule’s default is to get rid of customer information within two years of the last use to serve that customer, unless you need it for a business or legal reason. Tax records often have a legal reason. Write the reason down. “We might need it” for a return you no longer support is how a closet becomes a breach.
What we will and will not sign
We will inventory the systems, turn on MFA and encryption, write the access list, test a restore, and help the Qualified Individual produce the annual note. We will not sign a letter that says your firm is “Safeguards certified.” There is no such certificate in the Rule. We will not be the Qualified Individual of record unless the contract says so and a senior person at the firm is named to supervise. We will not pretend a penetration test replaces a missing inventory.
Contact Secure Techies with the activity you actually perform: tax, lending, deals, collections, or something else. We will tell you if this Rule is the wrong frame, and if it is the right one we will start with the written inventory rather than a policy template.
