Do tax preparers need a penetration test?
Yes, in practice. The FTC Safeguards Rule names tax preparers as a financial institution, and one way to satisfy its security-testing requirement is annual penetration testing plus vulnerability assessments every six months. Your client files are among the most sensitive records any small business holds, which is exactly why the rule reaches you.
A single return carries a taxpayer's Social Security number, every dependent's SSN, wages, bank account and routing numbers for the refund, and often a spouse's details too. One exposed client folder is a complete identity kit for a whole household.
Grapefruit runs the test the rule points to: a real attack on your portal and systems, every finding proven, at a fixed price, with the report in about 10 days.
What does the FTC Safeguards Rule require?
The Safeguards Rule, at 16 CFR 314.4(d), lets you choose. You can continuously monitor your systems, or do both annual penetration testing and vulnerability assessments at least every six months, and again after any material change. The testing path gives a tax practice a clean, dated record it can hand over if asked.
At 16 CFR 314.2 the rule defines a penetration test as a method where testers try to defeat your security from outside or inside your systems. Grapefruit does that with authenticated testing, using test accounts you supply, so the attack reflects what a logged-in client or staff member could actually reach.
- Annual penetration testing: one full Grapefruit test a year covers this half.
- Vulnerability assessments every six months: a Grapefruit maintenance plan re-tests weekly or monthly, well inside the line.
- After material changes: a plan re-tests on its next run after you add a portal feature or a new software integration.
- In force since June 9, 2023, so this is a current expectation.
Are you a covered financial institution?
Very likely. The rule and FTC guidance describe financial institutions broadly and name tax preparers directly, alongside firms like check cashers and credit counselors. If you prepare returns for a fee and store client data on a portal or in software, you are in scope. The definition sits at 16 CFR 314.2.
There is a narrow exemption. Under 16 CFR 314.6, a firm that maintains customer information on fewer than 5,000 consumers is exempt from the testing requirement. A busy seasonal practice usually clears 5,000 individuals once you count returning clients, spouses and dependents across prior years.
The IRS also expects paid preparers to keep a written information security plan, often called a WISP, which points to the same Safeguards Rule safeguards. Keep your focus on the Safeguards Rule itself, and the testing it describes answers both.
What does a tax preparer breach look like?
The classic one hides in the client portal. A taxpayer logs in to download this year's return, and the file loads from a web address that ends in a document number. Change that number and a different client's full return opens, Social Security numbers, dependents and bank details included, because the portal never confirmed the file belonged to the person requesting it.
That is a broken access check, and at tax scale it can leak hundreds of households from one logged-in account. The same flaw class shows up in refund-status lookups and in document uploads that accept a client ID an attacker can change.
- Returns that load across accounts through a guessable document or client ID.
- Refund-status pages that reveal another taxpayer's bank or routing details.
- Upload or messaging features reachable without the right login.
- Prior-year archives left on a test server with live SSNs inside.
What does Grapefruit test for a tax practice?
Everything a return touches, in one test. The client portal, the APIs behind it, and any AI assistant you use for intake or client questions are attacked together, because real attacks chain across them. Findings are ranked critical, high, medium or low in an online portal you can share.
Every finding arrives with the exact request and response that proves it. Your developer pastes the request, runs it, watches another client's return appear, then applies the fix and runs it again to watch the attack fail. That before and after is the evidence an examiner or an insurer wants to see.
- Authenticated testing with test accounts you supply, covering both client and staff views.
- Access-control testing across returns, documents and refund records.
- API testing mapped to the OWASP API Security Top 10 2023.
- A downloadable report listing the tested hostnames, the run date and proof for every finding.
| Rule element | What it means for a tax practice | How Grapefruit covers it |
|---|---|---|
| Annual penetration test, 16 CFR 314.4(d) | A real attack on the systems holding returns, once a year | One full penetration test at a fixed quote |
| Vulnerability assessments every six months | Repeat checks between annual tests | A maintenance plan that re-tests weekly or monthly |
| After material changes | Re-test when you add a feature or integration | The next scheduled run covers the change |
| Evidence of testing | Dated proof you can produce on request | Dated reports with captured request and response for each finding |
How does one test a year plus a plan cover the rule?
The Safeguards Rule's two halves line up with Grapefruit's two offers. One full penetration test a year satisfies the annual testing requirement. A Grapefruit maintenance plan re-tests your verified domains every week or month, which sits inside the six-month vulnerability-assessment line and dates each run for your records.
So one full test a year plus a maintenance plan covers both halves of the rule. See pricing to configure a full test, or to start a plan before next filing season.
How do you start?
Add your hostname, publish one DNS TXT record and sign the testing authorization online. It takes a few minutes. Testing without authorization is a federal crime under the Computer Fraud and Abuse Act, 18 U.S.C. 1030, which is why Grapefruit takes a signed authorization and a defined scope before any test.
Results land in your portal within hours of kickoff. Choose a full penetration test at a fixed quote, or a maintenance plan for weekly or monthly re-tests. This is a summary of public rules, not legal advice.
Questions
- Is penetration testing required for tax preparers?
- The FTC Safeguards Rule names tax preparers as financial institutions and, at 16 CFR 314.4(d), lets you meet its testing requirement with annual penetration testing plus vulnerability assessments every six months. Grapefruit runs that test at a fixed price with the report in about 10 days, and a plan keeps the six-month checks dated.
- Does the IRS require a pentest too?
- The IRS expects paid preparers to keep a written information security plan that follows the FTC Safeguards Rule safeguards, so the two point at the same testing. The surest footing is to meet the Safeguards Rule directly: an annual penetration test plus six-month vulnerability assessments. A Grapefruit test and plan deliver exactly that.
- Is my small tax office exempt?
- Maybe. Under 16 CFR 314.6, a firm maintaining customer information on fewer than 5,000 consumers is exempt from the testing requirement. Count returning clients, spouses and dependents across prior years before you rely on it, because a seasonal practice often passes 5,000 individuals faster than expected.
- What client data is at risk in a tax practice?
- A return holds the taxpayer's Social Security number, every dependent's SSN, wages, and the bank account and routing numbers for the refund. One exposed folder is a full identity kit for a household. Grapefruit tests whether any of it can be reached across accounts or through your portal's APIs.
- Do I need a certified tester?
- No. The Safeguards Rule asks for a competent tester, not a certified or licensed one, and there is no federal penetration-testing license. What an examiner wants is a real test with evidence behind each finding, which is what a Grapefruit report provides, with the request and response that proves every issue.
- Can you test during tax season without disrupting us?
- Yes. Testing uses the hostnames and test accounts you supply, and you choose the window. A maintenance plan can re-test on a weekly or monthly schedule so coverage continues through the busy months without a separate engagement each time. Results land in your portal within hours of kickoff.