Crashcart Start your free trial

FTC Safeguards Rule and the WISP

FTC Safeguards Rule requirements for small businesses

The FTC Safeguards Rule requires tax preparers, mortgage brokers, financial advisers and other non-bank financial businesses to keep a written information security program that protects their customers' personal financial information. The program has to name one person in charge, rest on an assessment of risks, put specific safeguards in place such as encryption and multi-factor authentication, train staff, oversee vendors, and be kept current. A firm with information on fewer than 5,000 customers is excused from four of the written parts but not from the program itself. Since May 2024, a breach affecting 500 or more people has to be reported to the FTC within 30 days.

The rule's full name is the Standards for Safeguarding Customer Information, and it lives at 16 CFR Part 314. The Federal Trade Commission enforces it. Its own plain-language guide is FTC Safeguards Rule: What Your Business Needs to Know. This guide walks through each requirement for an office with a handful of people and no IT department.

Who has to follow the Safeguards Rule

The rule applies to "financial institutions" under the FTC's jurisdiction, and the term is much wider than banks. The FTC says what matters is the activity, not the name on the door. The rule's own list of examples in 16 CFR 314.2(h) includes:

  • accountants and other tax preparation services that are in the business of completing income tax returns
  • mortgage lenders and mortgage brokers
  • payday lenders, finance companies and account servicers
  • check cashers and wire transferors
  • collection agencies
  • credit counselors and other financial advisers
  • certain investment advisers
  • non-federally insured credit unions
  • car dealers that lease vehicles for more than 90 days as a usual part of their business
  • "finders" that bring buyers and sellers together for a financial transaction

Banks and federally insured credit unions answer to their own regulators instead. If your business is not on the list but handles customers' financial information as part of a financial service, read the FTC's guide or ask your attorney before deciding the rule does not reach you.

For tax firms, the IRS states it plainly: federal law enforced by the FTC requires professional tax preparers to create and keep a written data security plan. The IRS says so on its Protect Your Clients, Protect Yourself page and in its Security Summit news releases, and Form W-12, the PTIN application and renewal, asks every preparer to confirm they know it.

What counts as customer information

The rule protects "customer information": any record, on paper or electronic, containing nonpublic personal information about a customer that your firm or its affiliates handle, including records you keep through someone else (16 CFR 314.2(d)).

Two details decide what that means in practice:

  • A customer is an individual who gets a financial product or service from you mainly for personal, family or household purposes, in a continuing relationship. A family whose returns you prepare every year is a customer. A business client is not a consumer under the rule, though the people behind it often are.
  • Nonpublic personal information is personally identifiable financial information: Social Security numbers, income, account numbers, the contents of a return, and lists of clients built from that information.

For a tax office, that covers the tax software's data, scanned documents, prior-year returns on a shared drive, email attachments, the paper files in the back room and anything a vendor stores for you.

What the Safeguards Rule requires

The core duty is in 16 CFR 314.3: develop, put in place and maintain an information security program, written in one or more accessible documents, with safeguards that fit your size, how complex your business is and how sensitive the information is. This program is what most people call the WISP, the written information security plan.

16 CFR 314.4 lists what the program must contain. Here is each part and what it means for a small office.

A qualified individual

Name one person to oversee, put in place and enforce the program (314.4(a)). In a small firm this is usually the owner or a partner. The FTC says the person does not need a particular degree or title.

The qualified individual can work for an outside provider. If you choose that, your firm still carries responsibility for compliance, you must name a senior member of your own staff to direct and oversee that person, and you must require the provider to keep a program that meets the rule.

A written risk assessment

Base the program on a written assessment of the reasonably foreseeable risks to customer information, inside and outside the firm (314.4(b)). The written assessment needs criteria for rating risks, an evaluation of how well your current safeguards protect the confidentiality, integrity and availability of the information, and how each risk will be reduced or accepted. Repeat it periodically.

For a 6-person office, the risks are usually concrete: a stolen laptop, a phished email password, a former employee whose account still works, a backup nobody has tested, a vendor with remote access to every computer.

Some risks are visible from outside the office. On October 14, 2026 we checked the public DNS records of 316 small tax and accounting firms in Alabama, Tennessee and Georgia, firms with 3 to 12 preparers and their own website. Of the 262 whose domain receives email, 122 had no DMARC record and 73 more had one set only to monitor. DMARC is the setting that tells receiving mail servers to reject email that pretends to come from your domain. Without it enforced, anyone can send a client an email that appears to come from the firm, which is how fake refund notices and document requests reach clients during tax season. It belongs in the risk assessment. Publishing the record takes minutes; moving it from monitoring to rejecting fake mail takes a few weeks of checking that the firm's own email still gets through.

The safeguards

314.4(c) names eight safeguards. In plain terms:

  1. Access controls. Each person can reach only the customer information their job needs, and access is reviewed periodically.
  2. An inventory. Know what data, people, devices, systems and facilities you have and how much each matters to the business.
  3. Encryption. Encrypt customer information on external networks and at rest, such as a laptop's disk. If that is not feasible, the qualified individual must review and approve other effective controls.
  4. Secure development. Use secure practices for any software you build in-house, and procedures for evaluating software you get from others.
  5. Multi-factor authentication for anyone accessing an information system, meaning a password plus a code from a phone, a security key or a fingerprint. The qualified individual can approve an equivalent or stronger control in writing.
  6. Disposal. Dispose of customer information no later than two years after it was last used for that customer, unless it is needed for business operations, the law requires you to keep it, or targeted disposal is not reasonably feasible. Review your retention policy periodically.
  7. Change management. Have procedures for changes to your systems, so an update or a new program does not quietly open a hole.
  8. Monitoring and logging. Monitor and log what authorized users do, and detect unauthorized access to, use of or tampering with customer information.

Testing and monitoring

Regularly test or monitor whether the safeguards work, including the ones meant to detect attacks (314.4(d)). For your information systems, that means either continuous monitoring, or a penetration test every year plus a vulnerability assessment at least every six months and after any material change to your business or systems.

An annual penetration test is a real expense for a small office, so continuous monitoring is often the practical route. Whichever you choose, write down which one and how it is done.

Staff training

Give staff security awareness training that reflects the risks your assessment found, use qualified people to run the program, and keep the people responsible for security current on threats (314.4(e)). For a small office, that means short, recurring training with a record of who completed it and when.

Service providers

Choose vendors that can protect your customers' information, require it in your contracts, and check on them periodically based on the risk they pose (314.4(f)). Your tax software company, cloud storage, document portal, email provider, shredding company and IT provider all count.

Keeping the program current

Adjust the program when your testing finds something, when your operations or business arrangements change, or when a new risk assessment calls for it (314.4(g)). A new office, a new partner, a new remote worker or a new vendor are all reasons to revisit it.

A written incident response plan

Write down how you will respond to and recover from a security event that materially affects customer information (314.4(h)). The plan must cover its goals, your internal response steps, who has which roles and decision-making authority, internal and external communication, how weaknesses get fixed, how events are documented and reported, and how the plan gets updated after an event.

A yearly report

At least once a year, the qualified individual reports in writing to your board, or if you have none, to a senior officer responsible for the program (314.4(i)). The report covers the program's overall status and compliance, and material matters such as risk decisions, service provider arrangements, test results, security events and recommended changes. In a firm where the owner is the qualified individual, this is the owner's own dated review of the year.

What changes for firms with fewer than 5,000 customers

A firm that keeps customer information on fewer than 5,000 consumers is excused from four parts of 314.4 (16 CFR 314.6):

Part excused What it means
314.4(b)(1) The formal written risk assessment with its criteria. You still base the program on an assessment of risks.
314.4(d)(2) The choice between continuous monitoring and annual penetration testing with twice-yearly vulnerability assessments. You still test or monitor your safeguards.
314.4(h) The written incident response plan.
314.4(i) The yearly written report to the board or a senior officer.

Everything else still applies: the written program, the qualified individual, the eight safeguards including encryption and multi-factor authentication, training, vendor oversight, keeping it current, and the FTC breach notice below. Count consumers, not households or returns, and write the number down with the date. Keeping the excused documents anyway costs little, and they are what an insurer or a client's security review usually asks to see.

The WISP and the IRS templates

The IRS also publishes a short list of basics, the Security Six, and the rule's own multi-factor authentication requirement reaches further than most firms expect.

The written program is the WISP. The IRS and its Security Summit partners publish free help for tax professionals:

  • Publication 5708, Creating a Written Information Security Plan for Your Tax and Accounting Practice, is a template that walks through objectives, the responsible people, the risk assessment, an inventory, safeguards and attachments. The current revision is dated August 2024.
  • Publication 5709 is a short guide to why a WISP matters and how to scale it.
  • Publication 4557, Safeguarding Taxpayer Data, covers the security practices the plan describes.

A template is a starting point. The plan has to describe your office as it is: your computers, your software, your vendors, who has access to what. A WISP copied from a template and never touched again describes a firm that does not exist, and it goes stale the first time someone buys a laptop or changes vendors.

Reporting a breach to the FTC

FTC Safeguards Rule breach notification requirements goes through the notice field by field. In short:

Since May 2024, the rule has required notice to the FTC after a "notification event" involving the information of at least 500 consumers (16 CFR 314.4(j)).

  • What counts. A notification event is the acquisition of unencrypted customer information without the customer's authorization. Information counts as unencrypted if the encryption key was also taken. Unauthorized access is presumed to mean acquisition unless you have reliable evidence that the information was not acquired.
  • When. As soon as possible and no later than 30 days after discovery. Discovery is the first day the event is known to anyone at your firm other than the person who caused it.
  • How. Through the electronic form on the FTC's website. The notice gives your firm's name and contact information, the types of information involved, the date or date range if known, the number of consumers affected, a general description of the event, and whether a law enforcement agency has asked you to delay public notice.

The FTC notice does not replace your state's breach notification law, which may require notice to the affected people and to state officials on its own deadlines. Tax preparers should also report data theft to the IRS through their IRS Stakeholder Liaison, as Publication 5293 describes.

Encryption matters here twice: an encrypted laptop that is stolen, with the key safe, is usually not a notification event at all.

When the requirements took effect

The FTC updated the rule in 2021. After an extension, most of the new requirements, including the qualified individual, the written risk assessment, encryption, multi-factor authentication, the incident response plan and vendor oversight, took effect on June 9, 2023. The FTC added the breach notice requirement in October 2023, effective 180 days after it was published, in May 2024.

A starting checklist for a small firm

  1. Decide whether the rule applies to you and whether you hold information on fewer than 5,000 consumers. Write both down.
  2. Name your qualified individual, and a backup for when they are away.
  3. List your computers, phones, software, cloud services, paper files and vendors that hold customer information.
  4. Assess the risks to that information, in writing if you are over 5,000 consumers.
  5. Check the safeguards on every device: disk encryption, multi-factor authentication on email and tax software, updates, antivirus, screen locks, and who has admin rights.
  6. Remove accounts for people who have left and limit each person to what their job needs.
  7. Decide how you test or monitor your safeguards, and write it down.
  8. Train your staff, and keep a record of who completed it.
  9. Collect your vendors' security commitments and put them in your contracts.
  10. Write the WISP from all of the above, using Publication 5708 as a guide, and have the qualified individual sign it.
  11. Write the incident response plan, including the FTC notice and your state's breach law.
  12. Set a date to review everything at least once a year.

Where Crashcart fits

Crashcart runs the IT for small offices, and for firms under the Safeguards Rule it drafts the WISP, risk assessment, incident response plan and yearly review from what is on your computers and your answers at setup. Each morning it checks the safeguards on every computer, such as encryption, updates and admin rights, fixes routine problems, and records every check and fix by date and rule section. When your systems stop matching the plan, it tells you. The decisions stay with your firm: you name the qualified individual, fill in what only you know, and sign. The page for tax and accounting firms shows what it does for each part of the rule.

This is general information, not legal advice. For your situation, ask your attorney.

More in this topic

Crashcart runs IT and security for small offices for $35 a computer a month. Start a 14-day free trial.