MYCPE ONE

For many CPA and accounting firms, the website is less secure than the owners assume. Accounting firm website security often breaks down in the same places: outdated software and plugins, weak admin logins, contact forms that collect sensitive data, documents sent by email instead of a secure portal, spoofed firm email, and hosting with no reliable backups. Because firms that prepare tax returns or provide financial services to consumers are treated as financial institutions under the FTC Safeguards Rule, these gaps are not only an IT problem. They are a compliance and client-trust problem.

This guide covers the most common website risks, how they tie to your written information security plan (WISP), a practical checklist, and what to do if something goes wrong.

Key Takeaways

  • Many firm website breaches start with basics: outdated plugins, weak passwords, or no multi-factor authentication (MFA).
  • Never collect Social Security numbers or financial documents through a standard contact form or plain email.
  • Your website, host, and developer belong in your WISP and risk assessment, which IRS Publications 4557 and 5708 expect even when the FTC rule does not.
  • Email authentication (SPF, DKIM, and DMARC) helps stop criminals from impersonating your firm.
  • A tested backup and a written incident plan turn a crisis into a recoverable event.

Why Is Website Security a Bigger Issue for Accounting Firms?

Accounting firms hold exactly the data criminals want: Social Security numbers, bank details, income records, and tax returns. Your website is often the first point of contact for that data, through contact forms, portal logins, payment links, and the email domain your clients trust.

Regulation raises the stakes. The FTC Safeguards Rule (16 CFR Part 314) names tax preparation services as an example of a financial institution, so firms that prepare returns or provide tax planning for individuals are covered. It protects consumer data; business-client data falls mainly under Section 7216, state law, and contracts. Covered firms need a written information security program, MFA, encryption, vendor oversight, and staff training. Since May 13, 2024, they must also notify the FTC within 30 days of discovering a security event involving the unencrypted information of at least 500 consumers.

Firms holding information on fewer than 5,000 consumers are exempt (16 CFR 314.6) from four items: the written risk assessment, continuous monitoring or annual penetration testing, the written incident response plan, and the annual report to the owner. Everything else still applies. Our guide to the FTC Safeguards Rule for CPA firms covers the threshold in detail; confirm your status with counsel.

At PTIN renewal, Line 11 of Form W-12 asks paid preparers to acknowledge awareness of the legal WISP requirement. Taxpayer data disclosures fall separately under Section 7216, covered in our 7216 consent form guide.

Security also affects visibility. A hacked site can trigger browser warnings, inject spam pages, and lose search rankings, which undoes your SEO for accounting firms investment overnight.

What Are the Most Common Website Security Risks for Accounting Firms?

RiskWhat it looks likeWhy it matters
Outdated softwareOld CMS, plugins, or themesKnown flaws are exploited automatically
Weak admin accessShared logins, no MFAOne stolen password exposes the whole site
Missing or broken HTTPSBrowser shows "Not secure"Data in transit can be intercepted; trust drops
Unsafe contact formsForms asking for SSNs or uploadsSensitive data stored in inboxes and plugins
Email document exchangeReturns and W-2s sent as attachmentsEasy to misdirect, forward, or intercept
Email spoofingFake emails from your domainClients tricked into sharing data or paying fraudsters
Weak hosting and backupsShared hosting, no tested restoreLong outages and permanent data loss
Third-party scriptsChat widgets, trackers, form toolsA vendor flaw becomes your flaw
Domain and DNS hijackingExpired domain or stolen registrar loginAttackers redirect your site and email
No monitoring or planBreach found by a clientSlower response and missed obligations

1. Outdated CMS, plugins, and themes

Most firm websites run on a CMS such as WordPress plus a stack of plugins, and outdated plugins are a common entry point for automated attacks. Remove plugins you do not use, apply updates promptly, and assign someone to own the update schedule.

2. Weak admin logins and shared accounts

Shared "admin" accounts, reused passwords, and logins without MFA are common on small-firm sites. Give each person a named account with only the access they need, require MFA, and remove former staff and old agencies the day they leave.

3. Missing or misconfigured HTTPS

Every page, including forms and logins, should load over HTTPS with a valid certificate. Mixed content, expired certificates, and HTTP pages weaken security and make visitors doubt your firm.

4. Contact forms that collect sensitive data

A contact form should ask for a name, email, phone number, and a short message. It should never ask for Social Security numbers, bank details, or tax documents. Submissions often sit unencrypted in inboxes and plugin databases.

5. Sending documents by email instead of a secure portal

Email is a poor channel for tax returns and financial statements. A secure, encrypted client portal linked from your website gives clients a safer way to exchange files. See our CPE e-book on choosing a client portal for your accounting firm and the course on addressing email security concerns in your accounting firm.

6. Email spoofing and phishing that use your domain

Without email authentication, criminals can send messages that appear to come from your domain, asking clients to "update bank details" or "upload documents here." Set up SPF, DKIM, and a DMARC policy for your domain. These records also improve deliverability, since Google's email sender guidelines now require all three from bulk senders, which matters for any email marketing for accountants program.

These records are set in your domain's DNS through your registrar or email provider, not in the website. Roll DMARC out in stages, from monitoring (p=none) to quarantine to reject, so a strict policy does not block your own legitimate mail.

7. Cheap hosting and untested backups

Low-cost shared hosting may lack firewalls, malware scanning, and isolation from other sites. Choose hosting with a web application firewall, daily backups stored separately, and a restore process you have actually tested. Security is one part of the real cost of a cheap accounting website for CPA firms.

8. Third-party scripts and vendors

Chat widgets, scheduling tools, analytics tags, and form builders all run code on your site. Keep an inventory, remove what you no longer use, and include these vendors in your oversight process.

9. Domain and DNS hijacking

If your domain expires or someone takes over your registrar account, attackers can redirect your website and email. Turn on auto-renewal, enable MFA and registrar lock, and keep the domain in the firm's name, not a former employee's or agency's account.

10. No monitoring or incident plan

Many firms learn of a website problem from a client. Uptime monitoring, malware scanning, and login alerts catch issues early; a written plan tells your team what to do next.

How Does Website Security Connect to the FTC Safeguards Rule and Your WISP?

If your website collects, transmits, or links to client information, it is part of the information system your WISP must protect. In practice, that means:

  • Include the website in your risk assessment, covering forms, portals, hosting, and admin access.
  • Apply MFA to any account that can reach client information, including website and portal admin logins.
  • Encrypt data in transit with HTTPS and use encrypted portals for documents.
  • Oversee service providers such as your web host, developer, and portal vendor, and ask how they protect data.
  • Cover website incidents in your incident response plan, including who decides whether a notification event occurred.

For firms under 5,000 consumers, the written risk assessment and incident response plan are best practice rather than FTC mandates, though IRS Publications 4557 and 5708 expect both.

Ask any vendor that touches client data for evidence of independent security controls, such as SOC 2 Type 2 reports or ISO 27001 certification. A vendor's SOC 2 report covers its own controls. It does not make your firm compliant, since you still own your WISP and vendor oversight. See how we approach data security at MYCPE ONE and why we pursued SOC 2 Type 2 certification.

Website Security Checklist for Accounting Firms

  • Update the CMS, plugins, and themes; remove anything unused.
  • Give every user a named account with MFA and least-privilege access.
  • Confirm HTTPS on every page with a valid, auto-renewing certificate.
  • Strip sensitive fields from contact forms and route documents to a secure portal.
  • Publish SPF, DKIM, and DMARC records, moving DMARC from monitoring to reject in stages.
  • Use hosting with a web application firewall and malware scanning.
  • Run daily off-site backups and test a restore at least twice a year.
  • Inventory and review third-party scripts and plugins each quarter.
  • Lock the domain at the registrar, enable auto-renewal, and secure the account with MFA.
  • Set up uptime, malware, and login monitoring with alerts to a named owner.
  • Add the website, host, and developer to your WISP and vendor list.
  • Write and rehearse a one-page website incident plan.

Repeat it before filing season with our tax season website checklist for CPA firms.

Who Should Manage Your Firm's Website Security?

ApproachWorks whenWatch out for
Do it yourselfVery small site with a technical partnerUpdates and monitoring slip during tax season
General IT providerThey already manage your network and devicesWebsite and CMS security may fall outside their scope
Specialist website partnerYou want the site built and maintained for accounting firmsConfirm security tasks are in writing
Managed cybersecurity serviceYou need monitoring and response across systemsMake sure the website is included


Many firms combine a specialist website for CPA and accounting firms, with security updates and SSL included, with broader managed IT services for cybersecurity. Comparing providers? This comparison of CPA website development services lists the security features to check, and our roundup of top website providers for accountants gives a wider view.

How Can Your Team Reduce Human Risk?

People still click links, reuse passwords, and approve requests under deadline pressure, so short, regular training is one of the best controls you can add.

Pair training with simple rules: verify any request to change bank details by phone, never share portal links by text, and report suspicious emails to one named person.

How Can You Tell If Your Firm's Website Has Been Compromised?

Investigate any of these warning signs quickly:

  • Browser or search results warn visitors that the site may be unsafe.
  • Unknown pages, links, or spam keywords appear in search results for your domain.
  • New admin users or plugins appear that nobody on your team added.
  • Contact form submissions stop arriving, or clients report odd redirects.
  • Clients receive emails from your domain that your team did not send.
  • Your host reports unusual traffic, file changes, or suspended service.

Google Search Console's security issues report and your host's malware scans catch many problems early.

What Should You Do If Your Firm's Website Is Hacked?

  • Contain it. Take the site offline or into maintenance mode and disable compromised accounts.
  • Call your host and developer to identify how the attacker got in.
  • Change every credential tied to the site, hosting, domain, and email, and enforce MFA.
  • Restore from a clean backup and patch the weakness before going live again.
  • Assess data exposure. Check forms, inboxes, and portals for client information that may have been accessed.
  • Meet your obligations. If taxpayer data was stolen, contact your IRS Stakeholder Liaison right away, then work through the IRS data theft contacts in Publication 4557, such as state tax agencies and law enforcement. Notify your cyber insurer promptly, since policies often require early notice. Confirm with counsel whether FTC or state breach notification applies.
  • Document and review what happened, then update your WISP and checklist.

Common Website Security Mistakes Accounting Firms Make

  • Assuming a small firm is not a target.
  • Leaving a former agency or employee as the website owner.
  • Treating the website as marketing only and leaving it out of the WISP.
  • Collecting sensitive data through forms because it is convenient.
  • Having backups that have never been restored.
Build a CPA Website That Attracts More Clients - Schedule a Free Call.

Conclusion: Treat Your Website Like Part of the Vault

Your website is the front door to client trust. Keep the software current, lock down access, keep sensitive data out of forms and email, authenticate your domain, and include the site in your WISP. Small, consistent steps protect your clients, your compliance, and your firm's reputation.

This article is general guidance, not legal or cybersecurity advice. Consult qualified legal and security professionals about your firm's situation.

Frequently Asked Questions

It applies to firms that prepare tax returns or provide other financial services to consumers. If your website collects, transmits, or links to client information, include it in your WISP. Firms under 5,000 consumers skip some written requirements, but MFA, encryption, and vendor oversight still apply.

No. Use an encrypted client portal for documents and keep contact forms limited to basic contact details.

DMARC is an email authentication policy that, together with SPF and DKIM, helps stop criminals from sending email that appears to come from your domain. Every firm that uses its own domain for email should set it up.

Apply security updates to the CMS, plugins, and themes promptly, and review the full site at least quarterly.

Under the Safeguards Rule, notify the FTC as soon as possible and no later than 30 days after discovering a security event involving unencrypted information of at least 500 consumers. Confirm specifics with legal counsel.

HTTPS protects data in transit, but it does not stop outdated plugins, weak passwords, or malware. It is one layer, not a complete solution.

Yes. Small firms hold the same sensitive data as large ones and are often targeted because their defenses are weaker. The 5,000-consumer exemption reduces paperwork, not the need for MFA and encryption.

Ben Kumar

Ben Kumar

Ben Kumar is a passionate digital marketer with over nine years of experience in helping businesses grow through smart strategy and data-driven marketing. At MYCPE ONE, he brings together creativity, technology, and teamwork to build meaningful digital experiences. Ben is passionate about innovation and how AI and automation are reshaping marketing. He enjoys exploring digital trends and performance strategies that make marketing smarter and more impactful. He believes marketing goes beyond metrics, it’s about building connections, solving real challenges, and helping professionals succeed in today’s fast-moving digital space.

Must Read Blogs