WISP and FTC Safeguards Compliance for Accounting Firms

Share this post
Forward Systems logo depicting a stylized network connection and data flow, representing managed IT services

A staff member clicks a convincing tax-season email, and an attacker gains access to the employee’s account. Tax files become unavailable, client messages may be exposed, and deadline-sensitive work pauses while your firm investigates.

The effects can extend beyond the compromised account. Your firm may face delayed filings, lost revenue, damaged client trust, and a difficult recovery during its busiest period.

Tax and accounting professionals are treated as financial institutions under the Gramm-Leach-Bliley Act. They must create and maintain a Written Information Security Plan (WISP) to protect client information, as explained in the IRS Security Summit guidance.

Why Accounting Firms Need a Written Information Security Plan

A WISP is your firm-specific written program for protecting the security, confidentiality, and integrity of client information. It describes the administrative, technical, and physical safeguards your firm uses to manage information security.

Administrative safeguards include policies, assigned responsibilities, employee training, and vendor oversight. Technical safeguards include access controls, encryption, endpoint protection, backups, and monitoring. Physical safeguards address access to offices, paper records, devices, and other places where sensitive information is stored.

The right program depends on your services, clients, location, regulatory status, and data-handling practices. Covered financial institutions must maintain an information-security program that uses administrative, technical, and physical measures to protect customer information. Forward Systems’ financial and legal compliance guide gives broader context for firms handling regulated data.

Security gaps often develop without clear warning. Practical examples include:

  • Unclear ownership: Employees assume that an outside IT provider owns every compliance task, while no one inside the firm coordinates the WISP.
  • Undocumented data flows: The firm cannot trace how tax documents move between email, portals, cloud storage, local devices, and remote workers.
  • Excessive access: Employees retain access to applications or client records they no longer need.
  • Untested backups: Backup jobs appear successful, though the firm has not confirmed that critical files can be restored.
  • Unmanaged vendors: Software providers and contractors handle client information without documented security reviews or contractual safeguards.
  • Staff-targeted phishing: Attackers use fake client messages, document-sharing alerts, and password-reset requests to capture credentials.

A practical WISP links these risks to the safeguards your firm uses. It should help protect:

  • Client financial, identity, and tax information
  • Access to tax applications, secure portals, and document storage
  • Deadline-sensitive preparation, filing, reporting, and client-service work
  • Documentation requested during cyber-insurance reviews
  • Recovery from ransomware, account compromise, hardware failure, or another disruption

A WISP supports compliance readiness. It does not replace legal advice. Coordinate with legal, compliance, and insurance advisors when your obligations require their input.

What Your WISP Must Address Under the FTC Safeguards Rule

The security program must assign responsibility, identify risks to customer information, implement safeguards, and monitor or test those safeguards. It must also address service-provider selection, contractual protections, employee preparation, and system failures.

Keep your plan written and accessible to the people who use it. Review, test, and update it regularly. A document that no longer matches your technology, vendors, or working practices has limited operational value.

WISP RequirementWhat the Firm Must Document or OperateExamples of Supporting Controls
Responsible coordinatorThe named person responsible for coordinating the information-security program, including defined duties and reporting linesWISP ownership record, review calendar, escalation contacts
Risk assessmentThe client information held, its locations and movement, authorized users, foreseeable risks, and planned responsesData inventory, system inventory, access review, risk register
Safeguards testingAdministrative, technical, and physical safeguards, plus the methods used to monitor and test themMultifactor authentication, encryption, endpoint protection, recovery testing
Vendor/training/system-failure managementVendor requirements, employee training, failure detection, response procedures, and review recordsVendor agreements, training records, monitoring alerts, incident-response procedures

Assign a Responsible Security Coordinator

Name an employee to coordinate the information-security program. The coordinator should understand the WISP, track required reviews, bring gaps to leadership, and ensure the right people respond when an issue occurs.

An IT provider can help operate safeguards, review technology, collect technical records, and support documentation. Your firm retains accountability for its security program and designated responsibilities. Identify the person inside the firm who has authority to coordinate decisions rather than listing “IT” as the owner.

Document the coordinator’s role clearly. Include backup contacts for absences, the person’s reporting path, and the situations that require leadership, legal counsel, insurance contacts, or technical specialists to become involved.

Identify Risks to Client Information

Start with a data inventory. Your firm needs to understand what it holds, where the information resides, and how employees use it before it can protect that information consistently.

Use practical questions to guide the assessment:

  • Information held: What tax records, financial statements, identity documents, payroll data, banking details, and authentication information does your firm receive?
  • Storage locations: Does the information reside in tax software, document-management systems, cloud storage, email, workstations, servers, removable media, or paper files?
  • Authorized access: Which employees, contractors, administrators, and vendors can reach each system?
  • Data movement: How does information travel through email, secure portals, cloud applications, endpoints, office networks, and remote-work connections?
  • Access or loss scenarios: Could phishing, stolen credentials, ransomware, device loss, accidental sharing, hardware failure, or a vendor incident expose or destroy the information?
  • Existing safeguards: Which controls reduce each risk, and who confirms that those controls continue to work?

Record findings in language that leadership and staff can understand. The assessment should connect each meaningful risk to an owner, safeguard, validation method, and remediation action.

Put Safeguards in Place and Test Them

IRS guidance organizes a sound WISP around employee management and training, information systems, and the detection and management of system failures. Choose safeguards that match your systems, information, workforce, working methods, and identified risks.

A defensible WISP typically addresses access controls, encryption, incident response, and scheduled reviews and updates. The appropriate combination may include:

  • Multifactor authentication: Require an additional verification method when users sign in to systems containing client information.
  • Encryption: Protect information while it is stored and while it moves between users, devices, applications, and providers.
  • Endpoint protection and firewalls: Monitor computers and servers for malicious activity while controlling unwanted network connections.
  • Backups and recovery: Maintain protected copies of important data and confirm that your firm can restore them.
  • Role-based access: Give each person access only to the applications and client information needed for that role.
  • Security awareness training: Teach employees to recognize phishing, suspicious login prompts, unsafe file sharing, and other relevant threats.
  • Incident response procedures: Define how your firm contains an event, preserves records, communicates internally, and brings in appropriate advisors.

Document how your firm tests each relevant safeguard. Testing may include reviewing user access, checking security alerts, confirming device protection, restoring selected backup data, and walking through an incident scenario. Record the date, scope, outcome, responsible person, and follow-up actions.

Manage Vendors, Training, and System Failures

Your WISP should address vendors that access, process, transmit, or store client information. Document how your firm evaluates providers, identifies expected safeguards, includes security requirements in contracts, and reviews material changes.

Training should match how your employees work. Staff members who manage administrator accounts, process client documents, approve financial activity, or support remote users may need different instruction from employees with limited system access.

Your procedures should also cover system failures. Define how your firm detects service interruptions, failed backup jobs, suspicious activity, unavailable cloud systems, and other events that could affect client information or operations.

Document who receives alerts and what happens next. Include escalation paths, communication responsibilities, recovery priorities, and records that must be preserved during an investigation.

How an All-Inclusive IT and Cybersecurity Stack Supports Compliance

An all-inclusive managed IT and cybersecurity stack supports the technical and operational work behind a WISP. Your firm still needs accountable leadership, written policies, employee training, vendor oversight, and regular review.

Forward Systems supports the daily systems accounting teams depend on, including document storage, secure portals, financial tools, and reporting tools. Its managed IT services for accounting firms connect those systems with access management, documentation standards, and secure configurations that support compliance reviews.

This approach can provide compliance IT services for accounting firms that handle client financial data. A technology platform alone does not satisfy every legal obligation.

Compliance NeedAll-Inclusive IT and Cybersecurity CapabilityOperational Result for the Firm
Governance/documentationPolicy review, system validation, security documentation, and scheduled reviewsCurrent technical information can support WISP updates and leadership decisions
Identity and endpoint protectionAccess management, secure device configurations, endpoint protection, and security assessmentsUsers receive appropriate access while managed devices follow defined security settings
Cloud-data protectionSecure configurations, access controls, encryption, and monitored backupsThe firm can apply consistent protection to supported cloud data and user access
Backups and recoveryProtected backups, recovery planning, and restore testingThe firm can evaluate whether critical information can be restored after a disruption
MonitoringDevice, network, alert, and backup-status monitoringTechnical problems and suspicious events can enter a documented response process
Compliance validationReviews of controls, documentation, access practices, and known questionnaire concernsThe firm receives documented findings and can prioritize remediation work

Governance and Documentation

Technology records give your WISP operational substance. Your policy may require controlled access and protected backups. System documentation shows which controls are configured and how the firm reviews them.

Forward Systems’ compliance services include policy reviews and updates, system and security validation, documentation support, and ongoing monitoring. These activities can help you compare written requirements with current system settings and operating practices.

Set a consistent documentation standard with your IT partner. Records should identify the system, control owner, review date, result, exception, and required follow-up. Keep security documents available to authorized decision-makers without placing sensitive technical details in broadly shared folders.

Identity, Endpoint, and Data Protection

Access management limits people to the systems and client information required for their work. Apply that principle to employees, contractors, temporary staff, vendors, service accounts, and administrators.

Review access when someone joins the firm, changes roles, begins a temporary assignment, or leaves. Pay particular attention to privileged accounts because they can change security settings, create users, or access broad collections of data.

Forward Systems states that its information-security measures include encryption, access controls, and regular security assessments in its privacy policy. Endpoint controls can support this work by applying security configurations, monitoring device health, and identifying computers that no longer meet your standard.

Cloud protection also requires deliberate configuration. Forward Systems says its cloud services use secure configurations, access controls, encryption, and monitored backups to protect cloud data and support recoverability.

Backup, Recovery, and Incident Readiness

A backup is a protected copy of information. Recovery readiness means your firm can restore critical data, recover required systems, and resume work after ransomware, hardware failure, accidental deletion, or another disruption.

Forward Systems provides accounting firms with layered cybersecurity, reliable backups, and systems intended to support the protection of financial records and client information. These capabilities contribute to business continuity, which keeps essential work available during disruption, and disaster recovery, which restores systems and data afterward.

Review backup scope before relying on status dashboards. Confirm which systems, cloud applications, folders, databases, and configuration records are protected. Test restoration and document whether the recovered information is usable.

Your firm should be able to review the following evidence with its IT partner:

  • The current WISP and related policies
  • The latest risk assessment and remediation list
  • User, administrator, and service-account access records
  • Employee security-training records
  • Relevant vendor reviews and contractual documentation
  • Backup scope, status, retention settings, and exceptions
  • Recovery and security test results
  • Incident-response contacts and escalation paths
  • Policy review and approval dates

A single tool may not create every record. Assign responsibility for collecting, protecting, reviewing, and retaining the evidence your firm needs.

Ongoing Monitoring and Compliance Validation

Monitoring helps your team detect failed backups, device problems, suspicious sign-ins, malware alerts, and configuration issues. Define which alerts require immediate action, which enter routine remediation, and who tracks each issue through closure.

A compliance readiness review examines whether your operating environment matches your written program. Forward Systems reviews the IT environment, security controls, documentation, access practices, backup readiness, and known concerns from audits or questionnaires.

Validation should produce specific findings rather than broad assurance statements. Useful findings identify the affected system, observed condition, expected standard, responsible owner, and next action.

Build and Maintain Your WISP Compliance Program

Build the program in a controlled sequence so that policies match your actual data, systems, risks, and safeguards.

  1. Identify your coordinator: Name the employee responsible for coordinating the program. Document authority, duties, backup contacts, and reporting lines.
  2. Inventory client information and systems: List the information your firm handles, its storage locations, the applications that process it, and the people or vendors with access.
  3. Complete a risk assessment: Evaluate unauthorized access, information loss, system failure, phishing, ransomware, remote work, device theft, and vendor-related risks.
  4. Document the WISP and related policies: Write the firm’s responsibilities, safeguards, review process, incident procedures, vendor requirements, and employee expectations.
  5. Implement and validate safeguards: Configure appropriate access controls, encryption, endpoint protection, monitoring, secure settings, and other selected controls. Confirm that the settings work as intended.
  6. Train staff and review vendors: Teach employees how to recognize and report threats. Review providers that handle or can access client information.
  7. Test backups and incident-response procedures: Restore critical information and conduct a response exercise. Record failures, delays, missing contacts, and remediation work.
  8. Review and update the program: Update the WISP after material changes to systems, vendors, insurance requirements, client requirements, risks, or data-handling practices.

Forward Systems recommends reviewing your compliance posture at least annually and when material changes occur. Its compliance readiness review can examine technical controls and documentation often requested in cyber-insurance questionnaires, including access controls, endpoint protection, backups, monitoring, and security policies.

Speak to an Expert: Request qualified support when:

  • You cannot identify every location where client information is stored.
  • Your firm lacks a current written plan.
  • You are uncertain who has administrator access.
  • Your team has never tested data recovery.
  • An employee reports suspicious account activity.
  • You receive a cyber-insurance or client-security questionnaire that you cannot answer confidently.

Coordinate technical remediation with your legal, compliance, and insurance advisors where appropriate. An IT review can identify system conditions and documentation gaps. Those advisors address obligations within their respective roles.

Security Incident Reporting and the 500-Consumer Threshold

Covered financial institutions must notify the FTC of certain security events involving information from at least 500 consumers. Notification must occur as soon as possible and no later than 30 days after discovery, using the FTC’s online notification process.

Your WISP should define who assesses an event, who coordinates response decisions, how the firm preserves evidence, and which internal and external contacts become involved. Legal counsel and other appropriate advisors should determine how reporting rules apply to a specific event.

Act immediately when your firm discovers suspicious access or a possible data-security event:

  • Contain access: Disable or restrict affected accounts, sessions, devices, or connections without destroying relevant evidence.
  • Preserve records: Retain logs, messages, alerts, system records, and other information needed to investigate what happened.
  • Engage responsible contacts: Notify the designated security coordinator, technical response team, leadership, and appropriate advisors.
  • Assess affected information: Identify the systems, client records, accounts, and time periods that may be involved.
  • Follow the response plan: Use the documented process for investigation, communication, recovery, insurance coordination, and regulatory review.

Avoid deleting messages, wiping devices, or making undocumented changes during the initial response. These actions can remove evidence needed to understand the incident.

Strengthen Your Accounting Firm’s WISP Readiness

Review your current WISP, validate technical controls, document gaps, and create a prioritized remediation plan. Address the highest-risk access, backup, endpoint, cloud, and incident-response issues first.

Forward Systems provides IT compliance services for organizations handling financial data and sensitive client records. We support Atlanta-area accounting firms as a security-focused managed IT partner. We help protect critical data, support employees, maintain client access, and improve business continuity and disaster recovery readiness.

Technology cannot guarantee FTC compliance, prevent every breach, or establish legal sufficiency. It can give your firm clearer controls, stronger operating practices, and better evidence for reviews.

Contact Forward Systems to schedule a compliance readiness consultation and identify practical next steps for your WISP, security controls, documentation, and recovery planning.

Share this post

Other Related Blogs

What can we do better?

We love to hear from our clients, please let us know if there are any areas that you think we could improve upon.