Your firm probably has a password policy. It may be a sticky note, a shared spreadsheet, or a verbal rule that the front desk login is “the same as always.” The FTC has already published what it expects instead, in plain language, and it takes about ten minutes to read. Put the two side by side, and the gaps show up quickly.
This post scores a small CPA firm against the FTC’s own password guidance and the Safeguards Rule duties behind it. The checklist groups the FTC’s examples into five practices: long, unique passwords; no shared logins; secure credential storage; brute-force lockout; and multi-factor authentication for sensitive accounts. Shared logins get their own section, because they fail the Rule itself.
The short answer
The FTC Safeguards Rule sets no password length, but it leaves no room for shared logins. Section 314.4 requires multi-factor authentication for anyone reaching a firm’s information systems, access controls the firm reviews, and a record of each authorized user’s activity. A login three staff use defeats the last two: nobody can tell which person opened a file, and one person’s access cannot end without a new password for the whole office. Length, lockout after failed attempts and credential storage come from the FTC’s 2017 Stick with Security guidance, which draws on its enforcement cases. Tax preparation firms are covered financial institutions, so a CPA firm that keeps a front-desk login, a tax software seat several preparers share, or passwords in a spreadsheet has a gap to close. Scoring each practice pass, partial or fail, with the evidence and a date, gives the Qualified Individual a record of where the firm stands.
The source is the FTC’s Stick with Security blog post on passwords and authentication. It expands one chapter of the FTC’s Start with Security guide, which draws its lessons from the agency’s data security enforcement cases.
The post covers the following points:
The FTC does not number these “the five rules.” That grouping is a working checklist built from its own examples, and it covers most of what the agency has said about passwords.
The Safeguards Rule is the binding part. The FTC’s compliance guide lists tax preparation firms among the financial institutions it covers. The IRS has reminded tax professionals that federal law requires a written information security plan and that FTC standards now require multi-factor authentication to protect client information.
Section 314.4 of the Rule sets out what that plan must include, and three items bear directly on sign-in habits.
There is a distinction to keep straight. MFA, access review, and logging come from the Rule itself. Password length, lockout, and storage are based on FTC guidance. Still, that guidance describes what the agency has treated as security failures in its cases, and the Rule asks for a program that fits your firm’s size and the sensitivity of the data. Tax returns are about as sensitive as client data gets, so a firm that ignores the FTC’s own examples will have a hard time calling its program reasonable.
Under the Safeguards Rule
What one shared login breaks
The FTC’s blog also warns against passwords that people share, and the Rule’s definition of an authorized user covers any employee, contractor, or agent allowed into your systems. Each of those people needs their own credential.
| PracticeMost often failed first | Where small firms slip | Passes when | Basis |
|---|---|---|---|
| One login per person | A scanner login, a tax software seat several preparers share, the shared inbox set up years ago | Everyone signs in as themselves | Safeguards Rule: access, logging |
| Credential storage | A spreadsheet or Word file of passwords on the server, the FTC’s own failure example | A password manager, one account per person | FTC guidance |
| MFA everywhere | Email, tax software, client portal, remote access, cloud storage | Two factors on each, or an equivalent your Qualified Individual approved in writing | Safeguards Rule: MFA |
| Lockout | Older on-premise software; cloud tools often lock by default | Repeated failed sign-ins lock the account | FTC guidance |
| Length and defaults | Short minimums; default passwords left on new software and hardware | Long passphrases; defaults changed on install | FTC guidance |
To score the firm, give each of the five a pass, partial, or fail, and write down what evidence you checked and when. Unless the firm holds customer information on fewer than 5,000 consumers, former clients included while their files are kept, the Rule expects a Qualified Individual to report in writing at least annually to a board or senior officer on the program's compliance, and a dated one-page scorecard fits directly into that report. A firm under the line is exempt from the report (§ 314.6) but still owes every item scored here. The remediation list is usually shorter than owners expect, and most items are a setting to change or a subscription to add.
For CPA firms
Score your firm’s logins with PK Tech
PK Tech has worked with CPA firms as a managed IT provider for more than 16 years, and holds AICPA SOC 2 Type II attestation from an independent audit. Bring a list of the accounts more than one person signs in to.
Schedule a compliance review →