Skip ahead to the main page
Partner Huddle
Pages

Tax firm security checklist: 7 checks for a systems review

Partner Huddle Editorial Team · Published · 13 min read

A tax firm security checklist during a systems review covers access, retention, recovery, encryption, testing, provider assessment, and guidance review. The NIST quick start guide provides direction for organizations seeking to improve cybersecurity risk management using the NIST Cybersecurity Framework, according to National Institute of Standards and Technology.

Key takeaways

  • Two-factor authentication blocks access: When an organization requires two-factor authentication, members and billing managers who do not use it cannot access the organization's resources until they enable it on their account, according to GitHub Docs.
  • Free plan retention is binary: Workspace Owners can use basic data retention settings that either keep all messages and files for one year or delete them after 90 days, according to Slack.
  • Channel recovery has a time limit: Deleted channels can be restored within 30 days, according to Microsoft Learn.
  • Record observed settings immediately: Note whether your team uses free or paid plans.
  • Verify authentication status now: Check if any team members are currently blocked from accessing shared repositories due to missing two-factor authentication setup.

Tax firm security checklist: seven checks to include

A tax firm security checklist should cover account access, Slack retention, Teams recovery, customer information encryption, security control testing, service provider assessment, and a review of security guidance. These seven items distinguish tool-specific settings from regulatory requirements cited in federal regulations. Verify which systems your team uses before applying these checks, as the following sections detail specific thresholds for GitHub, Slack, and Teams.

  1. Account access check: Verify that required two-factor authentication is enabled for all members. This setting distinguishes blocked member access from removed outside collaborators, a distinction detailed in the GitHub section later in this article.
  2. Slack retention check: Inspect the choice between ninety-day and one-year retention for your plan. Pinned or saved content remains subject to these retention settings, and deletions run daily, as noted in the Slack section.
  3. Teams recovery check: Record the thirty-day deleted-channel recovery window. Permanent deletion follows this period, a timeline documented in the Microsoft Learn section.
  4. Customer information encryption check: Protect by encryption all customer information held or transmitted by you both in transit over external networks and at rest, according to Legal Information Institute.
  5. Security control testing check: Regularly test or otherwise monitor the effectiveness of the safeguards' key controls, systems, and procedures, including those to detect actual and attempted attacks on, or intrusions into, information systems, according to Legal Information Institute.
  6. Service provider assessment check: Periodically assess your service providers based on the risk they present and the continued adequacy of their safeguards, according to Legal Information Institute.
  7. Security guidance check: Use the quick start guide, which intends to provide direction and guidance to organizations seeking to improve cybersecurity risk management using the NIST Cybersecurity Framework, according to National Institute of Standards and Technology. The Framework Core and Informative References are available as separate downloads in two formats: spreadsheet (Excel) , and alternate view (PDF), according to National Institute of Standards and Technology.

Before changing settings, identify the tools and plans in use

Start by listing every collaboration platform your team uses for client communication or internal coordination. For a broader look at client handoffs, see the Accounting Client Intake Checklist for a Clear Handoff. For each tool, record the current subscription tier.

If you use Slack, confirm whether you are on the free plan. On this plan, Workspace Owners can use basic data retention settings: either keep all messages and files for one year, or delete them after 90 days Slack. This distinction matters because the choice between these two options defines how long historical messages remain accessible before automatic deletion occurs. If your firm requires longer retention for compliance reasons, verify if your current plan supports it or if an upgrade is necessary to change the setting.

Do not assume that features visible in marketing materials are active on your account. Check the actual administration interface for each tool to see what is currently enabled. Record the specific retention period selected, the authentication methods required for access, and any recovery windows for deleted content. These observed settings form the baseline for your review.

When you encounter a tool where you cannot find a specific security control, note that absence explicitly. A missing feature is a finding just like a misconfigured one. Your inventory should reflect what is actually present in your environment, not what the vendor offers in its highest-tier package.

Complete this inventory before touching any settings. Changing a configuration without knowing the starting point makes it difficult to revert if the change causes unintended issues with message history or user access.

During review, examine GitHub access and Slack retention

When required two-factor authentication is enabled for an organization, members and billing managers who do not use 2FA will not be able to access the organization's resources until they enable 2FA on their account, according to GitHub Docs. Outside collaborators face a different consequence: those who do not use 2FA are removed from the organization and lose access to its repositories, according to GitHub Docs. The documented reinstatement condition allows you to reinstate their access privileges and settings if they enable 2FA for their personal account within three months of their removal from your organization, according to GitHub Docs. Record whether any outside collaborators currently lack 2FA, as this setting triggers automatic removal rather than just blocking access. For common staff access errors, see firm authentication mistakes.

For Slack workspaces, verify how retention settings interact with daily deletion cycles. Deletions run once a day, so data may be deleted shortly after making a change to your retention settings, according to Slack. Retention settings apply to all messages, files, canvases, and lists, including those that are pinned or saved, according to Slack. Note which channels contain client data and align the chosen retention period with your firm’s recordkeeping needs.

Setting or RuleSpecific BehaviorSource Publisher
Member access restrictionMembers and billing managers without 2FA cannot access organization resources until 2FA is enabledGitHub Docs
Outside collaborator removalOutside collaborators without 2FA are removed from the organization and lose repository accessGitHub Docs
Collaborator reinstatement windowAccess can be reinstated if 2FA is enabled within three months of removalGitHub Docs
Daily deletion timing Deletions run once a day, so data may be deleted shortly after changing retention settingsSlack
Pinned content coverage Retention settings apply to all messages, files, canvases, and lists, including pinned or saved itemsSlack

During review, examine Teams recovery and security controls

In Limits and specifications for Microsoft Teams, a deleted channel can be restored within 30 days according to Microsoft Learn. After this period, the channel and its content are permanently deleted and the channel no longer counts toward the team's limit according to Microsoft Learn. Note that these product limits describe tool behavior; they do not replace legal or professional recordkeeping duties.

Separate the cited regulatory requirements for encryption, control testing, and periodic service-provider assessment from optional collaboration settings. The following table maps each control area to its specific requirement or limit as documented in the named sources:

Control AreaRequirement or LimitSource Publisher
Customer information encryption (3) Protect by encryption all customer information held or transmitted by you both in transit over external networks and at restLegal Information Institute
Security control testing (1) Regularly test or otherwise monitor the effectiveness of the safeguards' key controls, systems, and procedures, including those to detect actual and attempted attacks on, or intrusions into, information systems Legal Information Institute
Service provider assessment (3) Periodically assessing your service providers based on the risk they present and the continued adequacy of their safeguardsLegal Information Institute
Channel recovery windowDeleted channels can be restored within 30 daysMicrosoft Learn
Permanent channel deletion After 30 days, a deleted channel and its content are permanently deleted and the channel no longer counts toward the team's limitMicrosoft Learn

These requirements come from 16 CFR § 314.4 - Elements, according to Legal Information Institute. Do not infer regulatory applicability from these excerpts alone; verify whether your firm falls under these provisions with legal counsel.

When examining Teams settings, distinguish between the tool's automatic deletion schedule and your firm's retention obligations. The thirty-day window is a product specification, not a compliance standard. If your firm requires longer retention for client data stored in Teams channels, the built-in 30-day limit may conflict with those needs. Document any gaps between the tool's behavior and your policy requirements. For example, if you must retain channel content for audit purposes beyond 30 days, export it before deleting the channel, because a deleted channel and its content are permanently deleted 30 days after deletion, according to Microsoft Learn. This does not mean the data is lost if you have exported or archived it elsewhere, but the native Teams channel itself will no longer exist.

When you finish this section of the review, record the observed Teams recovery settings and any unresolved questions about how encryption, testing, and provider assessment apply to your specific firm structure.

Illustrative example: a 45-day retention policy

Suppose a firm's policy keeps client channel content for 45 days after a channel is deleted. The tool in this example restores a deleted channel only within 30 days, and after that the channel and its content are permanently deleted. The native channel therefore cannot meet the 45-day policy. The firm exports the content within the first 30 days after deletion and keeps the export with its review notes.

Publisher reference table for the seven checks

The following table maps each of the seven checklist items to its supporting publisher and specific fact. Use this consolidated view to verify that every check in your systems review is grounded in a documented source or regulatory excerpt.

Check NumberPublisherSupporting Fact or Resource
1 Account access checkGitHub Docs Blocked member access and removed outside collaborators when required two-factor authentication is enabled
2 Slack retention checkSlack Choice between ninety-day and one-year retention; pinned content remains subject to settings; deletions run daily
3 Teams recovery checkMicrosoft Learn Thirty-day deleted-channel recovery window followed by permanent deletion
4 Customer information encryption checkLegal Information Institute (3) Protect by encryption all customer information held or transmitted by you both in transit over external networks and at rest according to Legal Information Institute
5 Security control testing checkLegal Information Institute (1) Regularly test or otherwise monitor the effectiveness of the safeguards' key controls, systems, and procedures according to Legal Information Institute
6 Service provider assessment check Legal Information Institute(3) Periodically assessing your service providers based on the risk they present and the continued adequacy of their safeguards according to Legal Information Institute
7 Security guidance check National Institute of Standards and Technology The quick start guide intends to provide direction and guidance to those organizations – in any sector or community – seeking to improve cybersecurity risk management using the NIST Cybersecurity Framework according to National Institute of Standards and Technology

After review, fill in the systems checklist

Record observed settings and unresolved questions for each system your team currently uses. Record whether your firm regularly tests or otherwise monitors the effectiveness of the safeguards' key controls, systems, and procedures, including those to detect actual and attempted attacks on, or intrusions into, information systems, as described in the elements section of 16 CFR § 314.4 according to Legal Information Institute. Log any gaps between current practices and these documented requirements without inferring regulatory applicability from these excerpts alone. Use the quick start guide as a review resource, which intends to provide direction and guidance to those organizations seeking to improve cybersecurity risk management using the NIST Cybersecurity Framework according to National Institute of Standards and Technology. Do not treat completing this checklist as establishing compliance with the requirements in 16 CFR § 314.4 or constituting a complete WISP.

PublisherCheck ItemDocumented Detail
SlackRetention choiceKeep all messages and files for one year, or delete them after 90 days
SlackDeletion timing Deletions run once a day
Legal Information InstituteControl testingRegularly test or otherwise monitor the effectiveness of the safeguards' key controls
National Institute of Standards and TechnologyReview resource Quick start guide provides direction and guidance for improving cybersecurity risk management

Today, open the admin settings for each tool you use and record the setting for each of the seven checks.

Related guides: Early withdrawal 10% tax: 4 rules to check · Federal tax classification for a new LLC: 8 items.

FAQ: applying the checklist to your firm's tools

What belongs on a tax firm security checklist?

The checklist covers account access, Slack retention, Teams recovery, encryption, control testing, provider assessment, and security guidance. These seven checks distinguish tool settings from regulatory requirements. Record observed settings for each system during your review.

Does the Slack retention choice apply to our free workspace?

Yes, Workspace Owners on free plans can use basic data retention settings. They can choose to keep all messages and files for one year or delete them after 90 days, according to Slack. Select the option that matches your recordkeeping needs before deletion cycles run.

How does required GitHub authentication affect outside collaborators?

When two-factor authentication is required, members and billing managers without 2FA cannot access organization resources until they enable it, according to GitHub Docs. Outside collaborators who do not use 2FA are removed and lose repository access. Reinstatement is possible only if the collaborator enables 2FA on their personal account within three months of removal.

When does a deleted Teams channel become permanently deleted?

A deleted channel has a thirty-day recovery window before permanent deletion occurs. After 30 days, the channel and its content are permanently deleted and the channel no longer counts toward the team's limit, according to Microsoft Learn. Verify whether any client work resides in channels scheduled for deletion.

Which IRS publications provide identity theft and data theft guidance?

Publication 5199, Tax Preparer Guide to Identity Theft, provides identity theft guidance for tax professionals, according to Internal Revenue Service. Publication 5293, Data Theft Resource Guide for Tax Professionals, offers a roundup of IRS.gov information on data theft, according to Internal Revenue Service. Use these documents as review resources rather than compliance evidence. For related identity protection steps, see IP PIN before e-filing.

Sources