What an information security policy is for
An information security policy is the short, approved statement of how an organisation expects its information and systems to be protected, who is responsible and what happens when the rules are broken. It is the document everything else hangs from: standards, procedures, contracts, audits and training all point back to it.
It is not a technical manual. Settings such as password length or patch windows change more often than the policy should, so they belong in standards and procedures that the policy refers to. Our guide to policies, standards and procedures explains the split.
If you only want the file, download the information security policy template in Word. It opens in Microsoft Word, Google Docs and LibreOffice. The guidance below explains each section and how to adapt it.
One policy or many?
NIST SP 800-12 Rev. 1 distinguishes three kinds of security policy: a program policy that sets direction for the whole organisation, issue-specific policies that address particular areas such as email or remote working, and system-specific policies for individual systems. Larger organisations often keep these separate.
For a small or mid-sized business, one organisation-wide policy with short sections for the most important issues is usually easier to approve, read and keep current. That is the approach this template takes. If a client later needs a separate acceptable use, remote working or AI use policy, lift the relevant section out and expand it.
NIST Cybersecurity Framework 2.0 places policy under its Govern function (GV.PO): policy for managing cybersecurity risk is established, communicated and enforced, and is reviewed and updated as requirements change. The template’s approval block, owner table and review section are there to make those points visible.
What the template contains
- Purpose and scope
- Roles and responsibilities
- Acceptable use
- Access control and authentication
- Data classification and handling
- Device, patching and malware protection
- Backup and recovery
- Suppliers and third parties
- Incident reporting and response
- Security awareness
- Exceptions, enforcement and review
Every section uses bracketed prompts. Replace them with the organisation’s real choices, and delete any statement the organisation does not intend to follow. A policy that promises controls nobody runs is worse than a shorter one that is true.
Section by section
1. Purpose and scope
State what the policy protects and who and what it covers: employees, contractors, company and personal devices used for work, cloud services and data held by suppliers on the organisation’s behalf. Ambiguous scope is the most common reason a policy cannot be enforced.
2. Roles and responsibilities
Name a person or role for each responsibility. The template includes a table for senior management, the information security lead (which may be an MSP or vCISO), system and data owners, and all personnel. If the security lead is a service provider, record who inside the client organisation oversees them.
3. Acceptable use
Set out what personnel must not do with organisation systems and information: sharing credentials, installing unapproved software, sending data to personal accounts, bypassing controls. Add organisation-specific rules, for example whether staff may paste client data into public AI tools.
4. Access control and authentication
Access should follow least privilege, be approved by the owner and be removed when no longer needed. State where multi-factor authentication is required, how privileged access is separated and reviewed, and how quickly joiner, mover and leaver changes are processed.
5. Data classification and handling
A simple four-level scheme (public, internal, confidential, restricted) is enough for most SMBs. The template gives a table to fill in with examples and handling rules for each level. Keep the examples specific to the business so staff can classify without asking.
6. Device, patching and malware protection
Require managed, encrypted and supported devices, define the window for applying security updates by severity and confirm malware protection is enabled. The NCSC Small Business Guide and CISA Cyber Essentials both treat these basics as a starting point for smaller organisations.
7. Backup and recovery
Say what is backed up, how often and where at least one copy is kept out of reach of the production credentials. Then require restore tests and record the results. An untested backup is an assumption, not a control.
8. Suppliers and third parties
Assess suppliers that handle organisation information before onboarding and review them in proportion to the risk they present. Contracts should cover security, confidentiality, incident notification and return or deletion of data at the end of the service.
9. Incident reporting and response
Tell people exactly how to report a suspected incident: a named contact, phone number and email. Point to the incident response plan for everything that happens next, including any legal or contractual notification steps.
10. Security awareness
Training at induction and at least annually, covering this policy, phishing and social engineering, data handling and incident reporting. Record completion so you can show it later.
11. Exceptions, enforcement and review
Exceptions should be written, approved, time-limited and recorded in a risk register. State the consequence of breaching the policy and commit to a review at least annually and after significant incidents or business changes.
Download the Word template
The Word template includes a version and approval block, the eleven sections above with bracketed prompts, tables for roles and data classification, and an acknowledgement block for staff to sign. Delete any guidance you do not need before you issue it.
Free editable Word file. Opens in Microsoft Word, Google Docs and LibreOffice.
Adapting it for a client
- Match the organisation’s size. A ten-person firm does not need the same document as a regulated lender. Cut sections rather than leaving promises nobody will keep.
- Use the client’s language. Name their systems, suppliers and roles so the policy reads as theirs.
- Link, do not paste. Put technical settings in standards and procedures and reference them.
- Get it approved. A policy signed by the owner or board carries more weight with staff than an unsigned draft.
- Plan the review. Put the next review date on the cover and in the calendar.
If the client is a US financial institution
Firms covered by the FTC Safeguards Rule, a group that can include tax preparers, accountants and lenders, also need a written information security program built around the Rule’s specific elements. Use this policy for organisation-wide expectations and the WISP template for the program the Rule describes.
Where GetCybr fits
A Word document is a sound way to start. If you maintain policies for several clients, GetCybr can keep each client’s policies, owners, linked controls and review dates in one place, so annual reviews and evidence requests do not start from scratch. The organisation remains responsible for approving and following its own policy.