Compliance program
FTC Safeguards Rule Your WISP, kept current
The Federal Trade Commission (FTC) Safeguards Rule requires non-bank financial firms, including tax preparers, to protect the security, confidentiality and integrity of customer information. Tax professionals remain prime targets for identity thieves, federal tax officials warn. We build and maintain your security program and Written Information Security Plan (WISP).
- Who it is for
- Accounting firms, tax preparers and other non-bank financial firms
- How it runs
- A setup project, then reviews every quarter or every year
- What you get
- Your WISP, a written risk assessment and an evidence package
What the FTC Safeguards Rule is
The FTC Safeguards Rule sets standards for protecting customer information under the Gramm-Leach-Bliley Act. Every business it covers must keep a written information security program "appropriate to your size and complexity." The text is in the Code of Federal Regulations (CFR) at 16 CFR Part 314.
The last amendments, effective May 13, 2024, added the duty to notify the FTC of certain breaches. As of November 13, 2026, the online CFR shows no later change.
Who the FTC Safeguards Rule applies to
Among the financial institutions it covers, the rule names "an accountant or other tax preparation service that is in the business of completing income tax returns." The Internal Revenue Service (IRS) says tax and accounting professionals count as financial institutions "regardless of size."
It also names mortgage brokers, real estate appraisers and settlement services, investment advisory companies, check cashers and auto dealers that lease vehicles for more than 90 days. See real estate and mortgage rules.
In the rule, a consumer is a person who uses a financial service for personal, family or household purposes. Customer information includes paper records.
FTC Safeguards Rule requirements, part by part
Sections 314.4(a) to (i), in plain words.
- A Qualified IndividualOne person who oversees, runs and enforces the program (314.4(a)).
- A written risk assessmentCriteria for rating risks and deciding which to reduce or accept, repeated periodically (314.4(b)).
- Access and inventoryStaff reach only the customer information they need, and you track your data, people, devices and systems (314.4(c)(1), (2)).
- EncryptionAll customer information encrypted, stored or sent over outside networks, or alternatives your Qualified Individual approves if that is not feasible (314.4(c)(3)).
- Multi-factor authentication (MFA)Two or more kinds of proof, such as a password and a token, for anyone signing in, unless your Qualified Individual approves an equivalent control in writing (314.4(c)(5)).
- Apps, changes and activity logsSecure app development, checks on outside apps, change procedures, and logs of what users do with customer information (314.4(c)(4), (7), (8)).
- Disposal and retentionDisposal of customer information within two years of last use, with set exceptions, and periodic review of your retention policy (314.4(c)(6)).
- Testing or monitoringRegular checks of key controls, plus effective continuous monitoring or a yearly penetration test and vulnerability assessments at least every six months and after material changes (314.4(d)).
- Training and staffSecurity awareness training kept current, and qualified security staff, yours or a provider's (314.4(e)).
- Service provider oversightCapable providers, safeguards in their contracts and periodic reviews by risk (314.4(f)).
- Program updatesAdjustments after tests, business changes and new risk assessments (314.4(g)).
- An incident response planA written plan, in seven set areas, for responding to and recovering from security events (314.4(h)).
- A yearly written reportFrom your Qualified Individual to your board, or a senior officer if you have none (314.4(i)).
Under 5,000 consumers: exempt from four parts only
If your firm keeps customer information on fewer than 5,000 consumers, section 314.6 lifts the four requirements below. Everything else still applies, including the Qualified Individual, periodic risk assessments, encryption, MFA, regular checks of key controls, training, provider oversight and the FTC notice.
On MFA, the IRS is direct: "This is required for all companies regardless of size."
- A risk assessment written with set criteria (314.4(b)(1))
- Effective continuous monitoring, or the yearly penetration test and six-monthly vulnerability assessments (314.4(d)(2))
- The written incident response plan (314.4(h))
- The yearly written report (314.4(i))
Your written information security plan (WISP)
For a tax or accounting practice, the WISP is the written form of its Safeguards Rule program. The IRS says "A requirement of the Safeguards Rule is implementing and maintaining a WISP."
On August 18, 2026, the IRS and its Security Summit partners repeated that federal law requires tax and accounting professionals to keep one (IR-2026-92). A good WISP, the release says, focuses on employee management and training, information systems, and detecting and managing system failures.
The IRS template, Publication 5708, outlines seven parts: objectives and scope, a qualified individual, a risk assessment, a hardware inventory, written safety measures, an implementation clause and attachments. It recommends signed staff acknowledgments at yearly training and a copy kept offsite or in the cloud. It also calls the WISP "an evergreen document that is regularly reviewed, tested, and updated."
Safeguards Rule breach notice to the FTC
The rule calls it a notification event when unencrypted customer information is acquired without authorization (16 CFR 314.2(m)). If one involves 500 or more consumers, you must notify the FTC on its electronic form as soon as possible and no later than 30 days after discovery (314.4(j)).
Encrypted data counts as unencrypted if the key was accessed by an unauthorized person, and unauthorized access is presumed to be acquisition unless you have reliable evidence otherwise. The 30 days start when anyone working for your firm, other than the person behind the breach, knows of it.
The IRS recommends reporting data theft to your IRS Stakeholder Liaison and sharing information with state tax agencies.
Our separate Incident Response Support service helps contain an incident and preserve evidence, while the decision to notify stays with you and your attorney. State notice laws are part of our Data Breach Readiness Program.
IT services for accounting firms, built on the rule
The first four include the IRS "Security Six": anti-virus, a firewall, two-factor authentication, backups, drive encryption and virtual private networks (VPNs).
- Security-First Endpoint ManagementAnti-virus, drive encryption, threat detection and updates on every computer.
- Firewall and Network Security ManagementYour firewall, VPN and network rules managed so only the right traffic gets in.
- Microsoft 365 Security ManagementTwo-factor sign-in, protected email and a locked-down Microsoft 365.
- Backup and Ransomware RecoveryImmutable backups with scheduled restore tests.
- Cyber Risk AssessmentThe program's risk assessment, at the start and every year.
- Vulnerability ManagementScans monthly or quarterly, with fixes tracked until they are closed.
- Penetration Testing and Security ValidationApproved break-in tests, run as a project with our testing partner, then a retest once the gaps are fixed.
- Security Awareness and Phishing ReadinessYearly training and quarterly practice phishing emails.
- Incident Response ReadinessA written response plan and practice drills.
- Third Party Risk ManagementOutside companies you rely on, ranked by risk and reviewed.
How the Safeguards Rule program runs
- 01 AssessWe check your firm against each part of the rule and write the risk assessment.
- 02 BuildWe write the WISP and policies with you and close the gaps or guide the fixes.
- 03 MaintainWe review the program and WISP every quarter or every year so both stay current.
- 04 ReportYou get gap reports, a roadmap and an evidence package to support the yearly report.
What we handle, What your firm stays responsible for
CyberBlip
- Map your controls to the rule and list the gaps
- Write and update the WISP and policies
- Close the gaps or guide your staff through them
- Run scans and coordinate penetration tests
- Organize proof of each safeguard
- Report progress to your Qualified Individual
You
- Choose your Qualified Individual and an owner inside the firm
- Approve the WISP, policies and scope
- Make the risk decisions, including risks you accept
- Authorize scans, and approve penetration tests in writing
- Decide with your advisers whether your monitoring counts as "effective continuous monitoring"
- Oversee your service providers, including any IT provider with access to customer information
- Decide on any FTC or client notice with your attorney
Questions tax firms ask about the Safeguards Rule
Does the rule apply if our accounting firm does not prepare tax returns?
It depends on what your firm does. The accountant example in the rule is about tax work: an accountant "in the business of completing income tax returns." A business "not significantly engaged" in financial activities falls outside the rule, and whether yours is covered is a question for your attorney.
Do I need a WISP to renew my PTIN?
Form W-12, the IRS application and renewal form for a Preparer Tax Identification Number (PTIN), asks you to confirm you know paid preparers must create and maintain a written information security plan. Line 11 needs a yes or no answer, not a copy of the plan.
Can we just fill in the IRS WISP template?
Not by itself: the IRS says the template is not "a substitute for developing your own plan." Publication 5708 was written mainly for smaller practices, and it says a sole practitioner can use a shorter, simpler plan. We build your plan around how your firm works.
Can someone from an outside company be our Qualified Individual?
Yes. The rule says the Qualified Individual "may be employed by you, an affiliate, or a service provider," but your firm keeps responsibility, names a senior person to oversee that individual and requires the provider to keep a security program that protects you. Our vCISO (virtual chief information security officer) service can support your Qualified Individual.
What happens if a tax firm ignores the Safeguards Rule?
The IRS says failing to create and enact a security plan "may result in an FTC investigation." Its e-file provider handbook adds that security failures may bring FTC sanctions, and that failures causing unauthorized disclosure may bring penalties under Internal Revenue Code sections 7216 and 6713.
Sources
Show all 9 sourcesHide sources
- Security Summit closes summer series with data security reminder for tax pros (IR-2026-111) IRS, 2026-09-16
- 16 CFR Part 314, Standards for Safeguarding Customer Information (FTC Safeguards Rule) eCFR, 2026-11-13
- Version history of 16 CFR Part 314 eCFR, 2026-11-13
- IR-2026-92, IRS, Security Summit remind tax pros they need a Written Information Security Plan IRS, 2026-08-18
- Publication 5708, Creating a Written Information Security Plan for your Tax and Accounting Practice IRS, 2024-08
- Publication 4557, Safeguarding Taxpayer Data IRS, 2024-06
- Form W-12, IRS Paid Preparer Tax Identification Number (PTIN) Application and Renewal IRS, 2026-10
- Tax Security 2.0: The Taxes-Security-Together Checklist IRS, 2026-10-09
- Publication 1345, Handbook for Authorized IRS e-file Providers of Individual Income Tax Returns IRS, 2026-10
Next step
Find out where you stand
Tell us how we can best support you.
Icons: Tabler Icons, MIT License. License text: /licenses/tabler-icons.txt