Remote work security checklist for accountants

Device, account, network, file-handling and incident controls for accountants working remotely with client data, drawn from IRS Pub. 4557 and the FTC rule.

US rule; elsewhere, check your own regulator · Updated November 20, 2026

How to use this checklist

US rule where a source is cited; check your own regulator for local data protection rules. Go through it when you set up a remote workspace, after any change of device or network, and at least once a year. Where the firm sets controls, the firm's controls come first and this list fills gaps.

The IRS says data security is a necessity for every tax professional, and that data thefts at tax professionals' offices are on the rise (Publication 4557). The same publication states that federal law gives the FTC authority to set safeguard regulations for entities including professional tax return preparers. Whether the FTC rule applies to you directly or reaches you through a firm's agreement depends on your role. This page is general information, not legal advice, and does not state that any set of controls is sufficient for any particular firm.

1. Devices

  • Anti-virus and anti-spyware are installed on every device used for client work.
  • A firewall is on. Common desktop operating systems include one that can be enabled.
  • Software updates automatically.
  • Drive encryption is on for laptops, desktops, tablets and phones. The IRS describes drive encryption as protecting information if a device is lost, stolen or improperly discarded.
  • The device locks after a short idle period and needs a password or biometric to unlock.
  • No one else uses the device for client work.
  • I have a list of devices that can reach client data.
  • I install software only from official sources, not from pop-up advertisements or offers of "free" security software (Publication 4557).

2. Accounts and passwords

  • Every account used for client work has a unique password.
  • Passwords are at least eight characters; the IRS suggests considering at least sixteen for an administrator account, and using phrases and mixed character types.
  • I use a password manager protected by a strong password.
  • Default and temporary passwords are changed, including on printers and routers.
  • I do not use my email address as a username where I can avoid it.
  • I never share passwords. Each person with access has their own.
  • Multi-factor authentication is on for tax software, email, storage and every firm system. The FTC Safeguards Rule lists multi-factor authentication for access to any information system among the required safeguards unless an equivalent is approved in writing (16 CFR 314.4(c)(5)).

3. Network

  • My router's default administrator password is changed.
  • I use WPA3 encryption on my wireless network and not WEP, which the IRS says is not secure (Publication 4557).
  • My network name does not identify me or my practice.
  • I do not use public wi-fi, at a café or an airport, to reach business email or sensitive documents (Publication 4557).
  • Where I connect to a firm network, I use the firm's multi-factor authentication and a secure VPN. The IRS says these should be minimum standards for remote access.
  • Where I can, I use a wired connection for devices that process or display client information. The IRS suggests avoiding wireless for those devices if possible.

4. Files and data

  • I work in the firm's approved workspace and do not download client files unless the firm says I may.
  • No client data sits in personal email, personal cloud storage or messaging apps.
  • Where files must travel, they are encrypted. The IRS says to encrypt sensitive files and emails, especially those with personally identifiable information.
  • Any approved local copies are backed up in encrypted form to a location not connected to my network full time. The IRS describes this as the best protection against ransomware.
  • I do not plug drives holding client data into public computers.
  • I limit access to client data to people who need it.
  • I know the firm's rules on retention and disposal. The FTC rule lists secure disposal among the required safeguards (16 CFR 314.4(c)(6)).
  • Old drives, printers and phones are wiped or destroyed before they leave my hands.

5. Tax return information

  • I know whether the files I handle contain tax return information.
  • I have not sent a Social Security number or other tax return information to anyone outside the approved route.
  • I have asked the firm about consent requirements before any disclosure. The regulation requires consent to be knowing and voluntary, in writing, signed and dated, and not obtained retroactively; for Form 1040 series filers, consent for a US-based preparer to disclose an SSN to a preparer outside the United States generally cannot be obtained without an adequate data protection safeguard (26 CFR 301.7216-3(a), (b)(1) and (b)(4)).

6. Phishing and social engineering

  • I can recognise phishing, especially messages that pretend to come from the IRS, tax software providers or cloud storage providers.
  • I do not open links or attachments in a suspicious email (Publication 4557).
  • A request to send files, change payment details or reset access gets a second check through a route I already know.
  • I know who to tell at the firm if I get a suspicious message.

7. Physical and working environment

  • My screen cannot be seen by others when I work.
  • I take calls about clients where others cannot overhear.
  • I keep a clean desk: no printouts or notes with client data left out. The IRS lists a clean desk policy among its basic steps.
  • I shred or securely dispose of any paper that holds client data.

8. If something goes wrong

  • I know who at the firm to tell first, how to reach them, and that I should tell them at once.
  • I know the steps I will take on a lost device: report, lock, remote wipe if enabled, change passwords.
  • I have written down the firm's incident contact where I can find it without access to my own accounts.
  • I know that the FTC rule requires covered financial institutions to notify the FTC of a notification event involving at least 500 consumers as soon as possible and no later than 30 days after discovery (16 CFR 314.4(j); effective May 13, 2024 under 16 CFR 314.5), and to keep a written incident response plan (314.4(h)) unless they hold customer information on fewer than five thousand consumers (16 CFR 314.6). Whether that duty falls on me or on the firm depends on the facts; I tell the firm immediately.

9. Written plan and review

  • I have a short written list of my controls and where they are set.
  • I review it at least once a year and after any change of device, network or firm system.
  • I keep it for my own records and share it with the firm if asked.

For a firm-level plan, the IRS directs tax professionals to Publication 5708 on creating a written information security plan (Publication 4557). The FTC rule also lists risk assessment, testing and monitoring, training, and oversight of service providers (16 CFR 314.4(b), (d), (e) and (f)). A freelancer's plan is lighter than a firm's, but it should say the same things in smaller form.

FAQ

Is this checklist enough to comply with the law?

No checklist can say that. It lists controls the IRS and the FTC rule point to. What applies to you depends on your role and the firm's agreement.

Do I need all of this if the firm gives me a managed workspace?

Many items still apply: your device, your password, your network, your environment. Items about files and backups depend on what the firm allows you to hold.

What if my country has its own data protection rules?

Check your own regulator. This page covers US sources only and does not summarise local law.

Sources

Last verified November 20, 2026. Sources checked by the editorial team; not yet reviewed by a named professional. General information, not legal, tax or accounting advice.

Related pages

Join the CORAA CPA network waitlist

CORAA prepares audit files for US CPA firms. Network members are independent contractors who clear what the software flags, with evidence and a note, paid per file under a contractor agreement.

  • Files are offered to you; you accept or decline
  • No exclusivity: you can work for others
  • The firm reviews and signs; CORAA never does

* required