DOUBLE RULESECURITY
Learn

Security requirements, translated for accounting-firm leadership.

What the rules mean, where firms fall short, and what to do next.

Coming next: plain guidance on AI use, note-takers, and client data.

WISP

A WISP is the written record of the program.

The IRS states that tax professionals are required by law to maintain a WISP. A template alone does not create the controls it describes.

A useful WISP matches your real:

  • Systems
  • Personnel
  • Vendors
  • Access controls
  • Data flows
  • Response procedures
Safeguards Rule

Why the Safeguards Rule matters to tax practices

The FTC Safeguards Rule applies to covered financial institutions under the Gramm-Leach-Bliley Act. IRS guidance states that federal regulations require professional tax preparers to create and enact security plans protecting client data.

Depending on applicability, the program may include:

  • A qualified individual responsible for the program
  • A written risk assessment
  • Administrative, technical, and physical safeguards
  • Access controls
  • Encryption
  • Multi-factor authentication (unless a qualified individual has approved reasonably equivalent or more secure access controls in writing)
  • Secure disposal
  • Monitoring or testing
  • Employee training
  • Service-provider oversight
  • An incident response plan
  • Periodic reporting to the governing body

Some elements, including a written incident response plan and annual leadership reporting, may not apply under the Rule's fewer-than-5,000-consumers exception.

The real question is whether the firm can show a program exists, matches its environment, and is maintained.

IT support

IT support is not automatically a security program.

A capable IT provider runs devices, accounts, backups, and support. That alone does not create:

  • A written risk assessment
  • Program governance and a vendor register
  • Partner reporting and a maintained WISP
  • Incident planning and remediation priorities

We make sure the security program exists around your IT.

Incidents

When the firm suspects an incident

A suspected compromise raises many questions at once:

  • Is it real, and what is affected?
  • Is client information involved?
  • Who preserves evidence?
  • Which providers must respond?
  • Do the carrier, counsel, clients, or regulators need notice?
  • How does the firm keep operating safely?

An incident response plan settles contacts, authority, and first steps before the pressure hits. Exact legal and notification duties depend on the incident, the data, jurisdictions, contracts, and professional advice.

FAQ

Common questions, answered plainly.

Can we just use a template?

Only if it reflects your real systems, vendors, and workflows. Foundation builds documentation around what you actually run.

Does Double Rule "make us compliant"?

We help turn requirements into an operating program. We do not promise audit outcomes or compliance certifications.

Do you include an incident response plan?

Yes, as a document. Foundation builds it, and Managed keeps related procedures current.

Are you our IR retainer or forensics team?

Not by default. IR as a service, retainers, and forensics are scoped separately, and we do not replace counsel or carriers.

Are you a 24/7 SOC?

No. Managed includes a named security contact for program coordination, not a monitoring center.

We already have an MSP. Why do we need you?

Your IT keeps systems running. We add the security program around it and work alongside them.

Will you take over our Microsoft 365 or device management?

In Managed we operate the security controls, such as MFA, access policies, and endpoint security. General admin, helpdesk, and devices stay with your IT.

What's the path in?

Free Security Snapshot, then Accounting Security Foundation (typically 2 to 6 weeks), then Build Your Security Baseline where gaps need closing, then Managed Accounting Security, a monthly program under an annual engagement.

What does it cost?

Fees are set before work begins. We do not publish a price list.

How do you handle filing season?

Major changes wait until after peak where practical. Urgent risks still get fixed.

Partner questions

Questions every partner should be able to answer

  1. Who owns the security program?
  2. Where is client data stored, and which vendors can reach it?
  3. Is MFA enforced everywhere?
  4. How fast is access removed when someone leaves?
  5. Can the firm recover from a destructive incident?
  6. What are the three biggest open risks?
  7. What happens during a suspected breach?
  8. What proof would you give an insurer, regulator, or client?

Nobody expects partners to know every detail. The exposure is having no one assigned to find out.

Start with a Free Security Snapshot

Avery reviews what's public about your firm and follows up with plain next steps.

Get a Free Security Snapshot
See What Attackers Can See