FTC Safeguards and WISP.Central Valley CPA and tax firms
Firms that prepare tax returns must keep a written information security program under the FTC Safeguards Rule. The FTC treats tax preparers as financial institutions, and the written program applies at every size. The IRS reinforces the same requirement: Publication 4557 expects a Written Information Security Plan (WISP), and PTIN renewal asks you to attest that a data-security plan exists.
We write the plan and the policies behind it — for CPA, tax, and bookkeeping firms across the Central Valley, built for how the firm actually operates, not from a template with the firm name inserted. Every engagement starts with a first look, at no charge.
The work is reviewed and signed by Brian Olson, CMMC Registered Practitioner.
When it comes up
The firm has no WISP, or has a template that describes controls it doesn’t have.
PTIN renewal is coming and the attestation needs to be true.
A cyber-insurance application asks about the written program, and the answers need evidence behind them.
The firm has grown, changed systems, or added staff, and the old plan describes a firm that no longer exists.
A client or bank asks how client files are protected.
What you receive
The Written Information Security Plan
Describing your firm’s actual environment: the systems that hold client data, the controls in place, who has access, and how it is granted and removed.
The policies behind it
Access control, encryption, incident response, vendor oversight, and training, written to match the firm’s size and systems.
A named Qualified Individual structure
One person accountable for the program, positioned to actually oversee it, whether that’s a partner, a staff member, or a designated provider.
A risk assessment
What client data you hold, where it lives, and what could happen to it, in writing.
An annual review cycle
The program reviewed at least annually and whenever the firm changes, so the plan stays true.
What a good WISP is not
A downloaded template with the firm name inserted does not satisfy the requirement. It describes controls the firm may not have, and it reads badly under scrutiny — because it describes a security program that doesn’t exist. The WISP we write names your systems, your vendors, your access paths, and your incident steps. If an examiner, an insurer, or a client asks to see it, it describes the firm sitting in front of them.
Straight answers.
What people ask about FTC Safeguards and WISP.
Does the Rule apply to a solo preparer?
Yes. The Rule covers tax preparers of all sizes, and the written program applies to every one. A firm that holds information on fewer than 5,000 consumers is excused from four elements: the written risk assessment, continuous monitoring or yearly penetration testing, the written incident response plan and the yearly report to the owners (16 CFR 314.6). Those elements are still good practice, and the IRS expects a written plan either way.
Our IT provider says we’re covered. Are we?
Maybe — if the provider is your designated Qualified Individual, the program is documented, and the firm can show the risk assessment, training records, and annual review. Ask to see the WISP with your firm’s name, systems, and controls in it. If nobody can produce it, you don’t have it.
Do you work through our CPA firm or IT provider?
Yes. We work directly with firms and through the partners they already use — including CPA firms that want the fieldwork done under their own client relationship. See our partners page.
What does it cost?
It depends on the firm’s size and starting point, so we don’t list prices. The scope is in writing before any work starts. The first look costs nothing.
Start with a first look.
A short review of where your firm stands against the Safeguards Rule and Publication 4557, and a short report signed by a person. No charge, no obligation. A person gets back to you within one business day.
