Written Information Security Program (WISP) — Full Template
NOTE: This is a fill‑in template. Each section starts with quick instructions and the evidence auditors/insurers expect. Replace bracketed placeholders [like this] and attach evidence where noted.
This template helps you establish a practical, auditable security program aligned to IRS Publication 4557 and the FTC Safeguards Rule. Customize sections to your firm, assign owners, and keep evidence for audits and insurance.
Signature Page
- Approved by: [Executive/Partner]
- Effective Date:
- Version:
- Next Review:
How to complete: Enter who approved the WISP, the effective date, and target next review date (at least annually).
Evidence to attach: Signed approval (PDF or e‑signature export).
1) Document Control
- Owner: [Title/Name]
- Distribution / Location (authoritative copy):
- Change Log:
- v1.0 (yyyy-mm-dd) — Initial release
- v1.1 (yyyy-mm-dd) — Updated access review cadence
How to complete: Assign a single owner. Keep the authoritative copy path (Drive/SharePoint) here. Update the change log for every modification.
Evidence to attach: Version history exports or change control tickets.
2) Purpose & Scope
Describe purpose, business units, locations, and in-scope systems. Include client data types (PII, taxpayer data, financial records) and any out-of-scope exclusions.
How to complete: List physical locations, subsidiaries, and all systems handling sensitive data. Note any exclusions and why.
Evidence to attach: Org chart, system inventory export, data map diagram.
3) Definitions
MFA, EDR, SOC, PHI/PII, Least Privilege, Break‑glass, RTO/RPO.
How to complete: Keep concise, business-friendly definitions. Link to internal glossary if you have one.
4) Roles & Responsibilities
- Security Program Lead (CISO/Delegate)
- IT Operations Lead
- Data Owner(s)
- Incident Response Lead
- Privacy/Compliance Lead
- Vendor Manager
- Evidence & Audit Coordinator Include deputies and escalation paths.
How to complete: Name primary and backup owners; include after-hours escalation path.
Evidence to attach: Contact roster and on‑call schedule (export).
5) Legal & Regulatory Mapping
- IRS Publication 4557: Safeguarding Taxpayer Data (access control, backups, incident response, training, vendor oversight)
- FTC Safeguards Rule: Risk assessment, access, encryption, monitoring, training, testing, and service provider management
- State privacy & breach laws: Notification timelines and requirements
How to complete: Check which laws apply to your firm and summarize the mapping of your controls to each requirement.
Evidence to attach: Control matrix (spreadsheet) mapping requirements to policies/procedures.
6) Data Inventory & Classification
- Systems: Email, File Storage, Practice/Tax Apps, Finance, IdP/SSO, Ticketing
- Data Classes: Confidential, Internal, Public
- Handling Rules:
- Confidential: Encryption at rest and in transit, limited access, logging, no personal accounts
- Internal: Business use only, minimum necessary
- Public: Approved for public distribution
- Data Flow: Describe where data is stored, transmitted, and processed (with diagrams if possible)
How to complete: List all systems with sensitive data and classify them. Add a simple data flow diagram linking sources → systems → destinations.
Evidence to attach: System inventory export, data flow diagram, classification register.
7) Access Control & Identity
- Unique accounts; least privilege; role-based access
- MFA for remote, email, and admin access
- Joiners/Movers/Leavers (JML) with SLAs
- Privileged access management (break‑glass accounts logged and reviewed)
- Quarterly access reviews with evidence retained
How to complete: Document the JML workflow and SLA (e.g., leavers disabled within 24 hours). Define how access reviews are performed and by whom.
Evidence to attach: IdP/MFA policy, last two access review sign‑offs, sample audit logs, JML tickets.
8) Cryptography & Key Management
- TLS for data in transit; strong encryption at rest (disk/database/SaaS where supported)
- Approved cryptographic standards and key rotation intervals
How to complete: List where encryption is enforced and how keys are rotated and stored.
Evidence to attach: Vendor documentation/screenshots proving encryption and key settings.
9) Endpoint & Device Security
- Managed devices, disk encryption, screen lock, patching SLAs
- Prohibited: personal email/file sharing for client data
- Mobile device controls (PIN/biometric, remote wipe)
How to complete: Describe EDR/AV tooling, patch cadence, and how you enforce disk encryption and screen locks.
Evidence to attach: EDR console screenshots, patch compliance report, MDM policy export.
10) Network Security
- Secure Wi‑Fi (WPA2+), guest isolation, admin network segmentation
- VPN or ZTNA for remote access; restrict admin interfaces
How to complete: Summarize segmentation, remote access, and how admin interfaces are restricted.
Evidence to attach: Network diagram, firewall/VPN config screenshots.
11) Secure Configuration & Patch Management
- Baseline configurations (CIS/benchmarks where feasible)
- Patch cadence (critical within 7 days; high within 14 days) with exceptions logged
How to complete: Define baselines and timeframes. Note exception handling and approvals.
Evidence to attach: Patch dashboard exports, exception register.
12) Monitoring, Logging & 24/7 Protection
- Centralized log collection for OS, IdP, and critical SaaS
- Alert triage with 24/7 coverage and defined escalation
- Retention: 90–365 days based on risk/requirements
How to complete: List log sources, retention period, and who provides 24/7 coverage.
Evidence to attach: SIEM/SOC service description, sample alerts, retention settings.
13) Backups & Recovery
- Scope, frequency, retention, offsite/immutable copies where possible
- Quarterly restore tests; evidence includes duration, success, and RTO/RPO attainment
- Recovery runbooks for critical applications
How to complete: Describe what’s backed up, where, and how often. Include restore testing cadence and targets.
Evidence to attach: Last two restore test reports (use the template below) and runbooks.
14) Incident Response
- Severity levels and declaration criteria
- Phases: Identification, Containment, Eradication, Recovery, Lessons Learned
- Evidence: timelines, artifacts, containment notes
- Communications: internal, client, regulators; breach notification per state law
How to complete: Define who declares an incident, how severities are assigned, and who is paged.
Evidence to attach: IR plan, table‑top exercise notes, communications templates.
15) Vendor & Cloud Security
- Risk assessment prior to onboarding; minimum controls (MFA, encryption, incident notice)
- Contracts/BAAs (as applicable); annual review of critical vendors
How to complete: Describe vendor due diligence and ongoing reviews.
Evidence to attach: Completed vendor questionnaires, BAAs/contracts, review checklist.
16) Secure Development & Change Management (if applicable)
- Code review, secrets management, SBOM (where relevant), change approval records
How to complete: Summarize dev lifecycle, gating controls, and approvals.
Evidence to attach: Pull request samples, change tickets, SBOM (if applicable).
17) Training & Awareness
- Onboarding and annual security training
- Phishing simulations cadence and metrics
- Policy acknowledgments tracked
How to complete: Set cadence and responsibility; track completion and metrics.
Evidence to attach: LMS exports, phishing campaign results, signed acknowledgments.
18) Risk Assessment & Treatment
- Annual risk assessment method and schedule
- Top risks with owners, treatment plans, acceptance or compensating controls
How to complete: Choose a method (e.g., NIST-style likelihood/impact). Keep a prioritized risk register.
Evidence to attach: Completed risk assessment, risk register (use the template below).
19) Physical Security
- Office access controls, visitor logging, media storage
- Device protection for remote/hybrid users
How to complete: Outline how you control office access and protect devices when offsite.
Evidence to attach: Access logs, visitor policy, photos of signage/locked storage.
20) Data Retention & Destruction
- Retention schedule for client and firm data
- Sanitization/destruction methods (logical and physical)
How to complete: Define retention by data type; list destruction methods and triggers.
Evidence to attach: Retention schedule, destruction logs or certificates.
21) Governance, Metrics & Review
- KPIs (patch SLAs, phishing rate, access review completion, backup test success)
- Management review and annual WISP update triggers (incidents/major changes)
How to complete: Pick 3–6 KPIs and set review cadence (monthly/quarterly). Note who signs off on reviews.
Evidence to attach: KPI dashboard screenshots, management review meeting notes.
Appendices
A) Contact Lists
- Security Lead, IT Ops, Legal/Privacy, External IR, Insurer, Key Vendors
How to complete: Use the fill‑in table below and keep it updated quarterly.
B) Risk Register Template
| Risk | Owner | Likelihood | Impact | Treatment | Target Date | Status | |------|-------|------------|--------|-----------|-------------|--------| | | | Low/Med/High | Low/Med/High | Mitigate/Accept/Transfer | yyyy-mm-dd | Open/In Progress/Closed |
Instruction: Start with top 5–10 risks. Update status monthly. Link remediation tickets.
C) Incident Playbooks
- Malware/Ransomware, Account Compromise, SaaS Outage, Data Loss
Instruction: Create step‑by‑step playbooks using the outline below. Test via tabletop annually.
D) Backup Test Report Template
- System, Date, Success/Fail, Restore Time, Notes/Issues, Next Actions
Instruction: Record at least quarterly. Track restore duration vs. RTO target.
E) Access Review Checklist
- Scope, Owners, Findings, Remediation Actions, Sign‑off
Instruction: Perform quarterly for critical systems; attach sign‑offs.
Appendix Templates (Fill-in)
Risk Register Template
Log your top risks, owners, and treatment plans.
| Risk | Owner | Likelihood | Impact | Treatment | Target Date | Status |
|---|---|---|---|---|---|---|
| ________________________ | ________________ | Low / Med / High | Low / Med / High | Mitigate / Accept / Transfer | ____ / ____ / ______ | Open / In Progress / Closed |
| ________________________ | ________________ | Low / Med / High | Low / Med / High | Mitigate / Accept / Transfer | ____ / ____ / ______ | Open / In Progress / Closed |
| ________________________ | ________________ | Low / Med / High | Low / Med / High | Mitigate / Accept / Transfer | ____ / ____ / ______ | Open / In Progress / Closed |
| ________________________ | ________________ | Low / Med / High | Low / Med / High | Mitigate / Accept / Transfer | ____ / ____ / ______ | Open / In Progress / Closed |
| ________________________ | ________________ | Low / Med / High | Low / Med / High | Mitigate / Accept / Transfer | ____ / ____ / ______ | Open / In Progress / Closed |
| ________________________ | ________________ | Low / Med / High | Low / Med / High | Mitigate / Accept / Transfer | ____ / ____ / ______ | Open / In Progress / Closed |
Backup Test Report Template
Document periodic restore tests and results.
| System | Date | Success/Fail | Restore Time | Notes/Issues | Next Actions |
|---|---|---|---|---|---|
| ________________________ | ____ / ____ / ______ | Success / Fail | ________ minutes | _______________________________________ | _______________________________________ |
| ________________________ | ____ / ____ / ______ | Success / Fail | ________ minutes | _______________________________________ | _______________________________________ |
| ________________________ | ____ / ____ / ______ | Success / Fail | ________ minutes | _______________________________________ | _______________________________________ |
| ________________________ | ____ / ____ / ______ | Success / Fail | ________ minutes | _______________________________________ | _______________________________________ |
| ________________________ | ____ / ____ / ______ | Success / Fail | ________ minutes | _______________________________________ | _______________________________________ |
Access Review Checklist
Track periodic access reviews and sign‑off.
| System / App | Owner | Period | Findings | Remediation Actions | Sign‑off |
|---|---|---|---|---|---|
| ________________________ | ________________ | Q1 / Q2 / Q3 / Q4 | _______________________________________ | _______________________________________ | Name / Date |
| ________________________ | ________________ | Q1 / Q2 / Q3 / Q4 | _______________________________________ | _______________________________________ | Name / Date |
| ________________________ | ________________ | Q1 / Q2 / Q3 / Q4 | _______________________________________ | _______________________________________ | Name / Date |
| ________________________ | ________________ | Q1 / Q2 / Q3 / Q4 | _______________________________________ | _______________________________________ | Name / Date |
| ________________________ | ________________ | Q1 / Q2 / Q3 / Q4 | _______________________________________ | _______________________________________ | Name / Date |
| ________________________ | ________________ | Q1 / Q2 / Q3 / Q4 | _______________________________________ | _______________________________________ | Name / Date |
Contact List Template
Key internal and external contacts for incidents.
| Role | Name | Phone | Notes | |
|---|---|---|---|---|
| Security Lead | ________________ | ________________ | ________________ | ________________ |
| IT Operations | ________________ | ________________ | ________________ | ________________ |
| Legal/Privacy | ________________ | ________________ | ________________ | ________________ |
| External IR | ________________ | ________________ | ________________ | ________________ |
| Insurance | ________________ | ________________ | ________________ | ________________ |
| Key Vendor | ________________ | ________________ | ________________ | ________________ |
Incident Playbooks (Outline)
Use these prompts to author step‑by‑step playbooks.
- Ransomware: detection cue, isolation steps, backup restore, insurer/LE notification, comms template.
- Account Compromise: revoke sessions, reset credentials, review audit logs, notify affected clients.
- SaaS Outage: continuity steps, manual workarounds, RTO/RPO alignment, vendor escalation.
- Data Loss/Leak: identify scope, containment, legal review, state breach notice checklist.

