FTC Safeguards Rule and the WISP
FTC Safeguards Rule breach notification requirements
The FTC Safeguards breach notification requirement says a financial institution must notify the Federal Trade Commission no later than 30 days after it discovers a "notification event" involving the information of at least 500 consumers. A notification event is the acquisition of unencrypted customer information without the customer's authorization, and unauthorized access is presumed to be acquisition unless you have reliable evidence that nothing was taken. You file on the FTC's online form, and the requirement has applied since May 13, 2024. The notice goes to the FTC only; telling the affected people is a matter for your state's breach law.
The requirement is paragraph (j) of 16 CFR 314.4, part of the FTC's Standards for Safeguarding Customer Information. The full guide to the FTC Safeguards Rule covers the written plan and the safeguards around it. This post covers the notice alone.
Who has to notify the FTC
Every business the Safeguards Rule covers has to notify, whatever its size. That includes tax preparers, mortgage brokers and financial advisers. The rule's exception for firms with information on fewer than 5,000 consumers, in 16 CFR 314.6, excuses four paragraphs of 314.4, and (j) isn't one of them. The Safeguards Rule small business exemption post lists what that exception does cover.
The FTC's Federal Register notice adopting the requirement says an event involving 500 or more consumers' unencrypted information warrants notice "regardless of the size of the financial institution."
What triggers an FTC Safeguards breach notification
The definition is in 16 CFR 314.2(m):
Notification event means acquisition of unencrypted customer information without the authorization of the individual to which the information pertains.
Unencrypted. Encryption, under 314.2(f), means transforming data so there is "a low probability of assigning meaning" without the key, "consistent with current cryptographic standards and accompanied by appropriate safeguards for cryptographic key material." Encrypted information counts as unencrypted "if the encryption key was accessed by an unauthorized person." An encrypted spreadsheet emailed with its password in the same message is, for this purpose, unencrypted.
Acquisition. The rule doesn't make you prove someone read the files. Under 314.2(m), "unauthorized acquisition will be presumed to include unauthorized access to unencrypted customer information" unless you have reliable evidence that there wasn't, or couldn't reasonably have been, acquisition. If someone got into the mailbox, the rule assumes they took what they could reach.
No harm test. The proposed rule asked whether misuse was likely. The final rule dropped that, and the Federal Register notice says notification "is not conditioned on the assessment of likelihood of misuse." If unencrypted information was acquired and the count reaches 500, you notify.
For the most common case in a small office, see what to do when a work laptop is stolen.
Counting to 500
The threshold is "at least 500 consumers" (314.4(j)(1)), and a consumer under 314.2(b)(1) is someone who "obtains or has obtained" a financial product or service from you. Former clients whose records sat in the breached mailbox or folder count. Count every person whose information was involved, not only the ones you're sure were viewed; the FTC's form asks for the number "affected or potentially affected."
When the 30 days start
The notice is due "as soon as possible, and no later than 30 days after discovery of the event" (314.4(j)(1)). Discovery has its own definition in 314.4(j)(2):
A notification event shall be treated as discovered as of the first day on which such event is known to you. You shall be deemed to have knowledge of a notification event if such event is known to any person, other than the person committing the breach, who is your employee, officer, or other agent.
So the clock starts when anyone at the firm knows, not when the owner hears about it or finishes investigating. If a staff member spots the problem on a Friday evening, the 30 days start that Friday. The FTC turned down a request to count from the day a firm "determines" what happened.
You don't need every fact to file. The FTC's guide to the Safeguards Rule says to report what you know and send an updated report when you learn more.
What the notice has to include
Section 314.4(j)(1) lists six items:
- The firm's name and contact information.
- A description of the types of information involved.
- The date or date range of the event, "if the information is possible to determine."
- The number of consumers affected or potentially affected.
- A general description of the event.
- Whether a law enforcement official has given you a written determination that notifying the public would impede a criminal investigation or damage national security, and a way for the FTC to contact that official.
How to file on the FTC's form
The notice goes through the Safeguards Rule Security Event Reporting Form on ftc.gov. The rule says the notice "shall be made electronically," so there is no paper version.
On October 16, 2026 we opened the form and read every field in its page code, without submitting anything. It has 16 fields plus a CAPTCHA, and 9 of the fields are marked required:
| Section of the form | Fields | Required |
|---|---|---|
| Contact person at the affected firm | Name of the firm, an "update to an existing report" box, the contact's name, email and phone | All but the update box |
| Submitter, if a third party files | Company or firm name, name, email, phone | None |
| The event | Start date, end date, number of consumers affected or potentially affected, types of information, summary | All five |
| Other | Request Secure File Transfer Link, Law Enforcement Delay Requested | Neither |
Three things in the form differ from the rule's text:
- Both dates are required. The rule asks for dates only if they can be determined, but the form won't take a report without a start date and an end date. Enter your best estimate and say in the summary that it's an estimate.
- The law enforcement item is a single checkbox. The rule asks for "a means for the Federal Trade Commission to contact the law enforcement official," and the form has no field for it. Put the official's name, agency and phone number in the summary.
- There is no upload. Types of information and the summary are plain text boxes. A secure file transfer link is offered to a third party filing one report for several firms.
The form estimates 5 hours to read the instructions, gather the information and fill it in. Its OMB approval runs to December 31, 2026, so the form may change after that. An attorney or a service provider can file for you.
The law enforcement delay
The delay holds back publication, not your notice. The form says "Your report may be made public," and the FTC's 2023 notice says it "intends to enter notification event reports into a publicly available database."
If police or another agency gives you a written determination that public notice would impede a criminal investigation or damage national security, check the delay box. Under 314.4(j)(1)(vi), the official can ask for an initial delay of up to 30 days from the date you notified the FTC, extended by up to 60 more days if the official asks in writing. Anything longer needs FTC staff to decide disclosure would still do that harm. The Federal Register notice says "there is no reason to delay notice to the Commission itself."
Write the summary as if a client will read it, because one might.
When the requirement took effect
The FTC announced the amendment on October 27, 2023 and published it in the Federal Register on November 13, 2023 (88 FR 77499). 16 CFR 314.5 now reads, in full: "Section 314.4(j) is effective as of May 13, 2024."
The FTC notice doesn't reach your clients
The Safeguards Rule never requires you to notify the affected people. The FTC decided against it because "all States have some form of consumer notification requirement." So a breach can need two sets of notices, the FTC's under 314.4(j) and whatever state law requires, to the people affected and often to a state official. The FTC's notice says state laws vary in what has to be reported and to whom, and many use no minimum or a threshold of 250 or 500 people.
Where to look for your state's rules:
- Your state attorney general's website. Most states require notice to the attorney general, according to the IRS page below.
- The statute in each state where you have affected clients, not only your own. Ask your attorney which ones apply.
- The National Conference of State Legislatures' list of security breach notification laws, which gives the citation for every state. The page says it was updated January 17, 2022, so read the current statute before relying on it.
Tax preparers have more calls to make. The IRS's data theft page for tax professionals says to report client data theft to your local IRS Stakeholder Liaison, contact the tax agency of each state where you prepare returns, and check whether each state's attorney general needs notice. It gives idt-brt@ftc.gov for individualized guidance from the FTC.
Writing down the decision
An event can end with no FTC notice because the laptop was encrypted and the key was safe, or fewer than 500 people were involved, or there's reliable evidence nothing was taken. Write the conclusion down anyway, with the discovery date, the information involved, whether it was encrypted, the count and how you reached it, and who decided. Firms with 5,000 or more consumers need an incident response plan that covers "documentation and reporting regarding security events" (314.4(h)(6)), and a smaller firm will want the same page when an insurer asks a year later. The post on writing a WISP for tax preparers covers where the notification list goes in the plan.
Crashcart keeps that record in a breach log. Each entry holds what happened and when it was found, the kinds of data, how many people, whether the data was encrypted, your decision with its reason, and each notice with its date. When unencrypted data on 500 or more consumers is involved, the entry lists the FTC notice due 30 days from discovery, and the owner gets a reminder two weeks before it's due and another if it passes. Whether it's a notification event, and who gets told, stays with you and your attorney. The page for tax and accounting firms shows what Crashcart does for the rest of the rule.
Checklist for an FTC Safeguards notice
- Write down when anyone at the firm first knew. The 30 days start there.
- Find out whether the information was encrypted and whether the key was exposed.
- Count every consumer involved, current and former.
- At 500 or more, file the FTC's form within 30 days, with estimates where needed.
- With a written law enforcement delay, check the box and put the official's contact details in the summary.
- File an update when you learn more.
- Check the breach law in each state where you have affected clients.
- Tax preparers, call your IRS Stakeholder Liaison and the state tax agencies.
- Keep the record of what you decided and why, including a decision not to notify.
This is general information, not legal advice. For your situation, ask your attorney.
More in this topic
- FTC Safeguards Rule requirements for small businesses
- MFA requirements under the FTC Safeguards Rule
- The IRS Security Six for small tax offices
- How the Safeguards Rule small business exemption works
- Setting up and removing seasonal preparer accounts
- Who can be the Safeguards Rule qualified individual
- How to answer the WISP question on Form W-12
- How to write a WISP for a tax practice
Crashcart runs IT and security for small offices for $35 a computer a month. Start a 14-day free trial.