Written Information Security Plan
Built around how the firm really works: what client data you hold, who touches it, and what protects it. Updated as the firm changes.

Based in Winter Haven · Serving Polk County & the I-4 corridor
I am Kevin Woolf, the owner. The IRS and the FTC require tax preparers to keep a written information security plan. I write yours around how your firm actually works and run the controls behind it.
Winter Haven chain of lakes, Central Florida
The problems
Your firm holds other people's financial records and works against deadlines that do not move. These are the problems I hear about most.
Returns are queued, clients are calling, and a deadline is on the calendar. I keep those mornings rare, and I put upgrades in the quiet months.
A plan that describes safeguards the firm does not run is a written record of the gap. I keep the document and the reality pointed at each other.
Social Security numbers, bank details, a complete picture of someone's finances. Most attempts arrive as ordinary-looking email, and the defenses are habits your team can keep during season.
A client questionnaire or an insurance renewal asks what safeguards you have. You send a file instead of writing one under pressure.
What I do
One local person for the written plan, the controls behind it, the day-to-day support, and the planning. No juggling vendors.
Built around how the firm really works: what client data you hold, who touches it, and what protects it. Updated as the firm changes.
Endpoint protection, multi-factor authentication, and email filtering, tuned so nobody is slowed down in the middle of season.
Backups of the client records your firm cannot lose, tested so they actually restore.
I watch your computers, network, and updates, and I am the person you call. The owner, not a ticket queue.
A Microsoft 365 move, a server replacement, or years of IT drift cleaned up, scheduled around your calendar.
Budgets, roadmaps, and vendor decisions planned in the off season, not the middle of one.

When the document and the reality drift apart, the document is the part that hurts you.
Great blue heron, Lake Howard, Winter Haven
The WISP
If your firm prepares tax returns for pay, the IRS and the FTC require a written information security plan. The FTC Safeguards Rule reaches tax preparers and many accounting practices, and law firms get asked for the same thing by clients and carriers.
The IRS template is a fine place to start reading. It is not your plan, because a plan has to describe your firm: the data you hold, the people who touch it, and the controls actually running.
That is the work. I write the plan around how your firm operates, put real controls behind every line, and keep both current. When the document and the reality drift apart, the document is the part that hurts you.
I will not tell you I can make your firm compliant; nobody outside your office can. I keep the plan honest, the safeguards real, and hand you documentation a client, an insurer, or a reviewer can read as written.
If you hold a PTIN, this plan is what Line 11 of Form W-12 asks you to attest to at renewal. Lacerte, Drake, ProSeries, UltraTax, QuickBooks: I support the machines and accounts they run on, and I do not resell any of them.
What you end up holding
Why Woolf IT
No call center, no ticket roulette. The person who wrote your plan is the person who answers when something is wrong.
I live and work here. You are hiring a neighbor, not a national franchise.
Monitoring runs around the clock, and upgrades land in the quiet months, well away from a deadline.
Questions
The questions partners and office managers ask me most. If yours is not here, just ask.
If your firm prepares tax returns for pay, yes: the IRS and the FTC both require it. IRS Publication 4557, "Safeguarding Taxpayer Data", is the plain-language source.
It is a useful start. The catch is that a plan describing safeguards you do not actually run is a written record of the gap. Fill it in if you like, then let me make every line of it true.
No, and be careful with anyone who says otherwise. Compliance includes how your team works every day. I build the plan around your firm, run the controls behind it, and give you documentation that shows the safeguards are real.
No. We start with what would hurt most if it failed, usually backups, multi-factor authentication, and email security, and save the bigger changes for after the deadline.
I support the computers, network, and Microsoft 365 accounts they run on. When the software itself misbehaves, I work with that vendor on your behalf.
They were always yours. Accounts, domain, and data stay in your name, so you leave with everything, and I help with the handoff.
A free 30-minute conversation about your firm and whatever you already have written down. You get a plain-English picture of where you stand and what the WISP would take, with no obligation.

The first step
We start with your written information security plan: what it has to say, what has to be true behind it, and where your firm stands today. No obligation.
Sunset on the dock, Winter Haven