Key takeaways
- 16 CFR 314.4(e)(1) requires security awareness training updated as necessary to reflect risks identified by the risk assessment.
- IRS Publication 5708 recommends a signed Employee/Contractor Acknowledgment of Understanding for all personnel, updated annually and kept on file.
- Publication 5708's sample policy says new employees are trained before they are given access to client data.
- The 5,000-consumer exemption in 16 CFR 314.6 does not cover the training requirement.
- As of November 2026, neither the Safeguards Rule nor Publication 5708 sets a retention period for training records, so the WISP should.
Why do WISP training records matter to a tax practice?
Training records are the most direct way to show that the people handling client data were taught how to protect it. Tax preparers are financial institutions under the FTC Safeguards Rule, and 16 CFR 314.4(e)(1) requires "security awareness training that is updated as necessary to reflect risks identified by the risk assessment." If your practice cannot produce evidence that training happened, the requirement is hard to show as met.
The question tends to come up at the worst moment. After a data theft, the IRS, the FTC, a state regulator, your cyber insurer or a client's attorney may ask what your staff knew and when they learned it. A dated, signed record answers that in minutes. A partner's recollection that "everyone did the training in January" does not.
The IRS has kept the topic in front of preparers. In IR-2026-92 (August 18, 2026), the IRS and the Security Summit reminded tax professionals that a written information security plan is required by federal law and listed employee management and training as one of the three areas a good WISP covers.
What does IRS Publication 5708 say about training records?
IRS Publication 5708 (Rev. 8-2024), the IRS guide to building a WISP, says it is a good idea to create an Employee/Contractor Acknowledgment of Understanding "for all personnel to keep a record of training." It recommends that the acknowledgments be "updated at annual training intervals and kept on file," and notes that signing and dating training "leaves a good documentation trail."
The publication's sample plan goes further. It assigns the Data Security Coordinator to verify that all employees have completed recurring Information Security Plan training, to conduct "an annual training session for all owners, managers, employees, and independent contractors," and states that all attendees "are required to certify their attendance." Its sample Information Security Training Policy says training happens at least annually and that "all new employees will be trained before PII access is granted."
Sample Attachment D gives the wording for the acknowledgment itself. The signer confirms they have been informed of the WISP, have undergone training conducted by the Data Security Coordinator, and understand that there will be periodic updates and training if policies change.
What are the FTC Safeguards Rule's security awareness training requirements?
The rule requires security awareness training that is updated as necessary to reflect the risks your risk assessment identifies, and it does not set a frequency, length, format or vendor. Our explainer on what security awareness training the Safeguards Rule requires covers the training content itself. This article focuses on the evidence.
Two related paragraphs shape what your records should show. Section 314.4(e)(3) and (e)(4) require security updates and training for the people who run the program, and verification that key security personnel "take steps to maintain current knowledge." Under 314.4(e)(2), those people can be employed by your firm, an affiliate or a service provider, so the records should cover your Qualified Individual and your outside IT provider's staff as well as your preparers.
Firm size does not remove the training duty. 16 CFR 314.6 exempts firms that maintain customer information on fewer than 5,000 consumers from the written risk assessment, the testing schedule in 314.4(d)(2), the written incident response plan and the annual board report. Paragraph (e) is not on that list.
What should a training record include?
A useful record answers five questions without anyone needing to explain it: who was trained, on what, when, by whom, and whether they acknowledged it. For each session or course, keep:
- The person's name, role and whether they are an employee, seasonal hire or contractor.
- The date completed and, for new hires, the date client data access was granted, so the record shows training came first.
- The version or date of the content delivered, so you can show it was updated when risks changed.
- The trainer or platform, and for self-paced courses, the completion report the platform generates.
- A signed and dated acknowledgment of the WISP, using the Publication 5708 Attachment D wording or your own equivalent.
- Results of phishing simulations or quizzes, if you run them, kept with the person's record.
Keep the content itself as well. A completion certificate shows that someone clicked through a module. The slide deck, the topics list and the date it was last revised show what they were taught, and that it reflected risks your risk assessment found. IRS Publication 4557 (Rev. 6-2024) says all employees in the office must be educated on the dangers of phishing scams, so that topic belongs in the content record every year.
How do you show training was "updated as necessary"?
Tie each content change to a reason you can point to. When your risk assessment, an incident, a new tool or an IRS alert changes your risk picture, update the training and write down what changed and why. A one-line change log with the date, the change and the trigger is enough.
For example, if your practice adopts an AI tool that staff use with client files, a dated note that says "added AI data handling rules to training after the tool was approved" links the content to the risk. The same goes for a new client portal, a change in e-signature process or a phishing pattern the IRS has warned about.
Section 314.4(g) requires firms to evaluate and adjust the program after testing, monitoring, material changes and risk assessment results. Training updates are one of the clearest pieces of evidence that the adjustment happened.
How do seasonal staff and contractors fit in?
Seasonal staff need the same record as permanent staff, and the timing matters more. Publication 5708's sample policy says new employees are trained before they get access to client data. During filing season, a start date and a first login can fall close together, which is where training gets skipped.
Build the acknowledgment into onboarding so access is not granted until the record exists. When the season ends, the training record stays on file even after the account is removed. Our 48-hour onboarding and offboarding checklist for seasonal tax staff covers the access side of that process.
Contractors and outside providers who touch client data belong in the records too. Publication 5708 lists independent contractors in the annual training session, and 314.4(e)(2) allows the information security personnel covered by (e)(3) and (e)(4) to be employed by an affiliate or service provider.
How long should you keep training records?
As of November 2026, neither the Safeguards Rule nor Publication 5708 sets a retention period for training records. Publication 5708 says to keep acknowledgments on file and refresh them annually. A workable approach is to keep them for as long as the person has access plus a set period afterward, and to state that period in the WISP's records retention section.
Whatever period you choose, write it down and apply it consistently. A record kept for some employees and missing for others raises more questions than a clear policy does.
Where should training evidence show up besides the HR file?
Training status belongs in the reports your firm already produces about its security program. Under 314.4(i), firms at or above the 5,000-consumer threshold must have the Qualified Individual report in writing at least annually to the board (or, if there is none, a senior officer) on the overall status of the program and compliance with the rule. Completion rates, overdue staff and content updates are a natural part of that report, as our guide to the Qualified Individual's annual report explains.
The WISP itself should name who runs training, how often, and where the records are kept. When you do the annual review that Publication 5708 recommends, check that the records match what the plan says. Our article on updating your WISP before the 2027 filing season lists the other sections to revisit.
For firms that want a structure for the program behind the records, NIST SP 800-50 Rev. 1 (September 2024) is voluntary guidance on building a cybersecurity and privacy learning program, with suggested metrics for measuring it.
What should a tax practice do about training records this quarter?
Start by checking every person with client data access against a dated training record, then close the gaps before the 2027 filing season opens.
- Pull a list of everyone with access to client data, including partners, seasonal hires and outside IT staff, and check each name against a dated training record.
- Collect signed WISP acknowledgments from anyone missing one, using the Publication 5708 Attachment D wording or your own version.
- Save the current training content with its revision date, and start a short change log tied to your risk assessment.
- Add a step to seasonal onboarding so access is granted only after training and the acknowledgment are on file.
- Write the retention period for training records into your WISP.
- Schedule the annual session before the 2027 filing season opens, and record attendance.
What should your counsel review before you set training record rules?
Do this review when you update the WISP for the 2027 filing season, or sooner if you change IT providers. Bring these decisions:
- The retention period for training records and signed acknowledgments, since neither 16 CFR 314.4 nor Publication 5708 sets one. Bring the WISP's records retention section and your current employee file policy.
- Which of your outside IT provider's staff count as information security personnel under 16 CFR 314.4(e)(2) through (e)(4), and what training evidence your agreement requires them to supply. Bring the provider agreement and any training reports they already send.
- Whether your firm maintains customer information on 5,000 or more consumers, which decides whether the written annual report in 314.4(i) applies under 16 CFR 314.6. Bring client counts by year and your archive inventory.
How s90 helps
If a data theft, an IRS inquiry or a cyber insurance claim forced you to show who was trained and when, could your practice produce the records in minutes? s90's IRS WISP and FTC Safeguards compliance services help tax and accounting practices run security awareness training, collect signed WISP acknowledgments and keep completion records in one place, mapped to the FTC Safeguards Rule and Publication 5708. When a regulator or insurer asks, we commit to producing evidence within 24 hours. If you would like a second look at your training records before filing season, we are happy to talk.




