Home · Guides
FTC Safeguards Rule checklist for tax professionals
The written information security plan that Form W-12 asks you to acknowledge is grounded in the FTC Safeguards Rule, 16 CFR part 314. This page is a plain-language checklist of § 314.4, notes the narrow exception in § 314.6 for offices with fewer than 5,000 consumers, and points back to the official text. It is not legal advice and is not an FTC or IRS publication.
Who this applies to
The Gramm-Leach-Bliley Act and the Safeguards Rule cover “financial institutions.” The FTC and the IRS treat tax return preparers as in that category when they provide tax-preparation services to consumers. IRS Publication 5708 explains this at the outset and tells firms to implement and maintain a WISP. Size does not take you out of the rule; it only changes which elements of § 314.4 you must formalize, as described below.
Checklist: 16 CFR 314.4
Use this against your current plan. “Done” means the control is in place and written down, not that you intend to get to it next year.
- (a) Qualified Individual. You have designated a person responsible for overseeing, implementing, and enforcing the information security program. They may be an employee, an affiliate, or a service provider. If you use a provider or affiliate, you still retain responsibility, you designate a senior person to oversee them, and their program must protect you under this part.
- (b) Risk assessment. The program is based on a risk assessment of reasonably foreseeable internal and external risks to the security, confidentiality, and integrity of customer information. Paragraph (b)(1) requires that assessment to be written and to include criteria for evaluating risks, for assessing your systems and information, and for how you will mitigate or accept risks. You also revisit the assessment periodically (b)(2). See the exception below if you have fewer than 5,000 consumers.
- (c) Safeguards, encryption, MFA. You design and implement safeguards to control the risks you identified. Among other items, § 314.4(c) requires encryption of customer information in transit over external networks and at rest (or effective compensating controls approved in writing by the Qualified Individual if encryption is infeasible), and multi-factor authentication for anyone accessing an information system, unless the Qualified Individual has approved in writing reasonably equivalent or more secure access controls. Access, disposal, change management, and monitoring of activity are part of this design.
- (d) Regular testing and monitoring, and (d)(2) annual testing. You test and monitor the effectiveness of your safeguards. Paragraph (d)(2) is the more formal annual requirement (continuous monitoring, or a combination of annual penetration testing and vulnerability assessments at least every six months, as the rule specifies). (d)(2) is one of the items excused for firms under the 5,000-consumer exception.
- (e) Training and qualified personnel. You provide security awareness training and utilize qualified information security personnel (yours, an affiliate’s, or a provider’s) sufficient to manage the risks and oversee the program. You keep the training current.
- (f) Service-provider oversight. You take reasonable steps to select providers that can maintain appropriate safeguards, require those safeguards by contract, and periodically assess providers based on the risk they present.
- (g) Continuous improvement of the program in light of testing results, personnel changes, and other circumstances that you reasonably believe may have a material impact.
- (h) Written incident-response plan designed to promptly respond to and recover from a security event that materially affects customer information, covering the goals, roles, communications, remediation, documentation, and post-event revision the rule lists. Exempted for firms under 5,000 consumers, but still a good idea, and the IRS separately recommends a data-theft response plan in Publication 5709.
- (i) Annual written report by the Qualified Individual to your board or equivalent, or, if you have no board, to a senior officer responsible for the program, covering the status of the program and material matters (risks, vendors, testing, events, recommendations). Also exempted under § 314.6 for firms under 5,000 consumers.
- (j) FTC notice of notification events involving 500 or more consumers. If a notification event involves the information of at least 500 consumers, you must notify the FTC as soon as possible and no later than 30 days after discovery, on the form at ftc.gov, with the content § 314.4(j) lists. This element is not in the § 314.6 exception. State breach-notification laws may impose separate, shorter deadlines; this checklist does not replace them.
The under-5,000-consumers exception, stated precisely
16 CFR 314.6 is one sentence: “Section 314.4(b)(1), (d)(2), (h), and (i) do not apply to financial institutions that maintain customer information concerning fewer than five thousand consumers.”
It does not exempt you from having a written information security program, a Qualified Individual, safeguards including MFA and encryption, training, vendor oversight, or the 500-consumer FTC notice. If you rely on the exception, write down your consumer count method and revisit it when you grow.
Want the crosswalk in the document itself? A PreparerGuard WISP includes a mapping to 16 CFR 314.4(a)–(j) and calls out which items § 314.6 may excuse, based on the consumer-count range you enter. You still have to implement the controls and review the draft. This is not a certification of compliance.
Check my email domain Build my WISP Read the WISP / W-12 line 11 guide
- 16 CFR 314.4, Elements — eCFR
- 16 CFR 314.6, Exceptions — eCFR
- FTC, Standards for Safeguarding Customer Information (Safeguards Rule), 16 CFR Part 314 — eCFR
- IRS Publication 5708 — irs.gov/pub/irs-pdf/p5708.pdf
- IRS Publication 5709 — irs.gov/pub/irs-pdf/p5709.pdf
Related: MFA requirement (16 CFR 314.4(c)(5)) · WISP template and Form W-12 line 11 · Free DMARC / spoofing check · Publication 4557 checklist · Data-breach reporting steps