5 min read

Fix guide: No Documented Incident Response Plan

The FTC Safeguards Rule and IRS guidance require a written incident response plan. When a breach or suspected breach occurs, you must know whom to contact (IRS DataTheft@irs.gov, clients, law enforcement) and what steps to take. A WISP cannot claim compliance without a documented plan.

Why this needs attention

The FTC Safeguards Rule and IRS guidance require a written incident response plan. When a breach or suspected breach occurs, you must know whom to contact (IRS DataTheft@irs.gov, clients, law enforcement) and what steps to take. A WISP cannot claim compliance without a documented plan.

How this can affect taxpayers

Without a plan, delays in notification and remediation can worsen the harm. Clients may not learn their data was compromised in time to take protective action. You may face additional penalties for failing to have and follow an incident response plan.

Step by step

  1. 1

    Step 1

    Document a simple incident response plan that includes: (1) How to detect and contain a breach, (2) Who to contact, IRS DataTheft@irs.gov, clients, and law enforcement, (3) Steps to preserve evidence, (4) How to notify affected clients and regulators per state law.

  2. 2

    Step 2

    Store the plan in an accessible location and share it with key staff.

  3. 3

    Step 3

    Review the plan annually.

  4. 4

    Step 4

    Or adopt the Incident Response Plan in your EasyWISP: choose 'EasyWISP will be my new incident response plan' in the questionnaire.

Ready to do this in your own account?

Everything in this guide happens inside EasyWISP. The trial is free and takes about an hour to set up.

Start your free trial
Start Free Trial