Skip to main content
Practitioner template

WISP Template (Written Information Security Program)

A written information security program template that follows the elements of the FTC Safeguards Rule, with a free editable Word file and plain guidance for MSPs and the firms they support.

By Reviewed 20 November 2026For MSPs supporting accountants, tax preparers, auto dealers and lenders, vCISOs acting as Qualified Individual, Owners of small US financial services firms

What a WISP is

A written information security program (WISP) is the document a business uses to show how it protects customer information: who is responsible, which risks it has identified, which safeguards it runs, how it tests them and what it does when something goes wrong. Some firms call it a written information security plan. The two names describe the same document.

In the United States the term is most closely tied to the FTC Safeguards Rule, published at 16 CFR Part 314. The Rule applies to financial institutions within the FTC’s jurisdiction, a group that can include tax preparers, accountants, mortgage brokers, auto dealers that arrange finance and other non-bank firms. Whether a particular business is covered is a legal question. This page is not legal advice; confirm scope with counsel before relying on it.

If you only want the file, download the WISP template in Word. It opens in Microsoft Word, Google Docs and LibreOffice. The guidance below explains what each section needs.

Who needs one and who is partly exempt

Section 314.4 of the Rule lists the elements an information security program must include. Section 314.6 then makes an exception: four of those elements do not apply to financial institutions that maintain customer information concerning fewer than 5,000 consumers. The four are:

  • the written risk assessment requirement in 314.4(b)(1)
  • the penetration testing and vulnerability assessment requirement in 314.4(d)(2)
  • the written incident response plan in 314.4(h)
  • the Qualified Individual’s annual written report to the board in 314.4(i)

Everything else still applies to smaller firms, including the Qualified Individual, the safeguards, training and service provider oversight. The template keeps every section and asks you to mark the exempt ones as “not required”, so the document still shows that the question was considered. Even where an element is not mandatory, a short written risk assessment and incident plan are usually worth having.

For tax preparers the IRS is explicit: Publication 5708 states that under the GLBA and the Safeguards Rule, tax and accounting professionals are considered financial institutions regardless of size. IRS Publication 5708 (Rev. 8-2024) is a free guide with sample content aimed at smaller tax and accounting practices. It is a useful companion to this template if your client prepares returns.

What the template contains

The Word file follows the Rule’s elements in order, so a reviewer can match each section to its citation.

  1. Qualified Individual
  2. Written risk assessment
  3. Safeguards
  4. Testing and monitoring
  5. People and training
  6. Service provider oversight
  7. Program evaluation and changes
  8. Incident response plan
  9. Annual report to the board
  10. FTC notification of security events

Each section has bracketed prompts, a reference to the paragraph of 314.4 it answers and, where useful, a table to fill in.

Section by section

1. Qualified Individual

The Rule requires one person to oversee, implement and enforce the program. That person can be an employee, someone at an affiliate or someone at a service provider. If you, as an MSP or vCISO, take the role, the Rule says the client still keeps responsibility for compliance, must name a senior member of its own staff to direct and oversee you, and must require you to maintain an information security program that protects the client. Write all three points into the WISP and into your contract.

2. Written risk assessment

The program must be based on a risk assessment. Unless the 5,000-consumer exception applies, the assessment must be written and must include criteria for evaluating and categorising risks, criteria for assessing confidentiality, integrity and availability of systems and customer information, and a description of how each risk will be mitigated or accepted. The Rule also requires periodic reassessment. Record the date of the last assessment and when the next one is due. A risk register is a practical way to keep the results.

3. Safeguards

Paragraph 314.4(c) names specific safeguards. The template turns them into a table with three columns: the safeguard, how you meet it and where the evidence lives. The list covers access controls that authenticate users and limit access to what each role needs; an inventory of data, personnel, devices, systems and facilities; encryption of customer information in transit over external networks and at rest, or compensating controls approved by the Qualified Individual; secure development and evaluation of applications; multi-factor authentication for anyone accessing any information system, unless the Qualified Individual approves an equivalent control in writing; secure disposal no later than two years after the information was last used, subject to the Rule’s exceptions, plus periodic review of retention; change management; and monitoring and logging of authorised users.

The evidence column is where most WISPs fall short. A sentence saying “we use MFA” is weaker than a link to the conditional access policy and last month’s sign-in report.

4. Testing and monitoring

Key controls must be tested or monitored regularly. For information systems, the Rule asks for continuous monitoring or, failing that, annual penetration testing and vulnerability assessments at least every six months and after material changes. Record which approach you use, the dates of the last tests and who owns any open findings.

5. People and training

The program must cover security awareness training updated for the risks you have identified, qualified security personnel (in-house, affiliate or provider), ongoing updates and training for those personnel, and some way of verifying that key staff keep up with threats. Name the training programme and its frequency rather than describing it in general terms.

6. Service provider oversight

Select providers that can protect the information, require safeguards by contract and assess each provider periodically based on the risk it presents. The template includes a table for each provider, the customer information it can reach, whether the contract has a safeguards clause and when it was last assessed. For many small firms this is the section with the most gaps: payroll, document storage, tax software and the MSP itself all belong here.

7. Program evaluation and changes

The program must be adjusted after test results, material business changes, new risk assessments or anything else that could materially affect it. Keep a short change log with the date, the change, the reason and who approved it.

8. Incident response plan

Unless the exception applies, the Rule requires a written plan covering seven areas: its goals; internal response processes; roles, responsibilities and decision authority; internal and external communications; remediation of weaknesses found; documentation and reporting; and review of the plan after an event. The template lists all seven so none is missed. Link to your full plan rather than pasting it in.

9. Annual report to the board

The Qualified Individual must report in writing, regularly and at least annually, to the board or an equivalent governing body. If there is none, the report goes to a senior officer responsible for the program. It covers the overall status of the program and compliance with the Rule, and material matters such as risk decisions, service provider arrangements, test results and security events. Our board report template can be adapted for this.

10. FTC notification of security events

Since 13 May 2024, paragraph 314.4(j) requires a covered institution to notify the FTC when a notification event involves the information of at least 500 consumers. Notice is made electronically on the FTC’s website as soon as possible and no later than 30 days after discovery. The Rule defines a notification event as acquisition of unencrypted customer information without the authorisation of the individual it relates to. Record who makes the decision to notify and where the required details are kept.

Download the Word template

The WISP template has an approval block, the ten sections above with their 314.4 references, tables for safeguards and service providers, and a prompt to record how many consumers’ information you hold so the 314.6 exception is applied deliberately. Replace every bracketed prompt and delete guidance you do not need.

Free editable Word file. Opens in Microsoft Word, Google Docs and LibreOffice.

Common mistakes

  • Copying a generic template unchanged. A WISP should describe the firm’s real systems, providers and people, or it will not hold up when someone asks for evidence.
  • No evidence. Each safeguard should point to something that proves it runs.
  • No owner for the Qualified Individual role. If the MSP fills it, say so in the WISP and the contract, and name the client’s senior overseer.
  • Writing it once. The Rule expects periodic reassessment and adjustment. Put the next review date on the cover.

How this relates to NIST and CISA guidance

The Safeguards Rule does not require a particular framework. Many practitioners map their safeguards to NIST Cybersecurity Framework 2.0 so the same evidence can support other client requirements later. CISA Cyber Essentials is a plain-language starting point for small business leaders who need to understand their part.

Where GetCybr fits

A Word document is a sound way to start. If you maintain WISPs for several clients, GetCybr can keep each client’s program, risk assessment, safeguards evidence and review dates in one place, so the annual report and reassessment are not rebuilt from scratch each year. Decisions about risk and compliance stay with the client and their advisers.

Run the workflow across every client

GetCybr gives MSPs one workspace for assessments, evidence, roadmaps and client reporting.

Become a partner