How familiar is your team with IRS Publication 4557 and the FTC Safeguards Rule?
We're familiar with the basics — IRS Publication 4557 (Safeguarding Taxpayer Data) requires every tax preparer to have a Written Information Security Plan (WISP) and to implement certain technical safeguards. The FTC Safeguards Rule under Gramm-Leach-Bliley applies to tax preparers and CPAs because they handle non-public personal information. We're not your compliance advisor or IRS Pub 4557 specialist. What we are is the IT and security team that works alongside your firm's compliance advisor — we own the technical safeguards (encryption, MFA, access controls, audit logging, off-site backup, endpoint protection, anti-phishing email defenses) those professionals need to be in place; they own the WISP documentation and the regulatory interpretation.
What tax software have you supported on the IT side?
UltraTax CS, Thomson Reuters (GoSystem Tax RS, Onvio), Lacerte, CCH ProSystem fx, Drake Tax, ProSeries, TaxSlayer Pro, QuickBooks Enterprise, QuickBooks Online Accountant, Xero, Sage, and a handful of others. We don't replace your tax-software vendor's implementation team — we work alongside them on the IT plumbing: bandwidth sizing for cloud tax software during peak filing season, firewall rules, MFA enrollment, single sign-on, certificate management, off-site backup integration, endpoint security on the workstations that touch return data, and the documentation your compliance advisor needs to demonstrate the technical safeguards your WISP describes.
How do you protect against tax-season ransomware and downtime?
Tax season is the worst possible time for a ransomware incident — filing deadlines don't move, clients are anxious, and your firm's revenue concentration in 60-90 days means downtime is enormously costly. Our defenses are layered: encrypted off-site backups with documented restore testing (so you actually know your data comes back when you need it), endpoint detection and response on every workstation and server, email advanced threat protection, MFA on every account, network segmentation between client-data systems and general business systems, and a documented incident-response runbook so the first four hours of an event are decisive rather than chaotic.
How do you handle client tax data in our portal and backups?
Portals: TLS in transit, encryption at rest, MFA on every login, audit logging on every document access. Backups: encrypted in transit and at rest, stored off-site with documented retention that meets your record-keeping obligations. Email: TLS in transit, advanced threat protection on inbound (tax preparers are heavily targeted by phishing — fake IRS notices, fake client urgency, fake bank notifications), encrypted-email enforcement for outbound messages containing sensitive PII. Every configuration is documented so it shows up on your WISP and your annual compliance review.
What's your role if we have a confirmed or suspected breach of client tax data?
We're the technical first-responders. On suspected breach: contain the scope (isolate affected systems, preserve forensic evidence, change credentials), identify what client data was accessed and by whom, document the timeline, and provide the technical record your firm's compliance advisor and outside breach counsel need. We don't make the IRS, FTC, or state notification call — that's your compliance advisor and breach counsel — but we make sure they have what they need to make those calls correctly within the IRS Pub 4557 and state-law notification windows.
Do you provide accounting-firm-specific phishing simulations?
Yes. Generic phishing-simulation content (fake Microsoft password resets, fake DocuSign requests) catches some attacks but misses the tax-pro-specific ones: fake IRS notices, fake client urgency right before a filing deadline, fake bank transfer-request emails from a client, fake e-file rejection notices. We build phishing simulations around the scenarios your firm actually sees, document training records (so they're available for your annual compliance review), and report measurable improvement in your team's detection rate over time.
What about firms that also handle medical-billing or financial-services clients (HIPAA and GLBA overlay)?
Many of our accounting clients have layered compliance obligations. A firm doing medical-billing work picks up HIPAA Business Associate obligations on any matter involving PHI. A firm preparing returns for a community bank picks up GLBA-adjacent expectations from the bank's vendor management program. A firm doing audit work for federal contractors may inherit DFARS-flavored expectations. We build the security program around the strictest applicable framework, then map it down to satisfy the others — so you're not stacking three contradictory compliance programs.
How are you different from an accounting-IT consultancy?
Most accounting-IT consultancies deliver a written assessment and an invoice, then leave you to find an MSP to actually implement and operate the controls. We're the operator — we do the IT and security work day-to-day, alongside whatever accounting-IT consultancy or compliance advisor your firm uses for IRS Pub 4557 and FTC Safeguards interpretation. Plus we're locally based in Arkansas with same-day on-site response across 10 counties, not a national consultancy billing $300+/hour out of a different time zone.