Back to Resources
Template

A Sample Backup Policy You Can Actually Use

A backup policy is a one-to-two-page document stating what you back up, how often, how long you keep it, who is responsible, and how you verify it works.

Copy this template, formatted, to paste straight into Word or Google Docs.

A backup policy is a one-to-two-page document stating what you back up, how often, how long you keep it, who is responsible, and how you verify it works. Below is a complete sample you can copy and adapt, written for a small company and structured to satisfy ISO 27001's backup control (A.8.13) without enterprise jargon.

What a backup policy must cover

The policy is usually the first document an auditor or a customer's security questionnaire asks for. It doesn't need to be long; it needs to answer five questions without ambiguity: scope (what is backed up), frequency (how often), retention (how long copies are kept), responsibility (who owns it), and verification (how you know it works). Most templates online fail by being either a gated teaser or forty pages of enterprise boilerplate. This one fits on two pages. Replace the [bracketed] parts and delete what doesn't apply.

The sample policy

Backup Policy: [Company Name]

Version: [1.0] · Owner: [role, e.g. IT Manager] · Approved by: [role, e.g. Managing Director] · Last reviewed: [date]

1. Purpose

This policy ensures that [Company Name]'s business data can be recovered after hardware failure, human error, malicious action (including ransomware), or disaster, with an acceptable and known loss of data and time.

2. Scope

This policy covers the systems listed in the Backup Register (Appendix A), which includes at minimum: [core business database(s), file shares, email, accounting system, HR/payroll system]. Any newly deployed system holding business data must be added to the Backup Register within [5 business days] of go-live. Systems explicitly excluded, and the reason, are also recorded in Appendix A.

3. Backup schedule and retention

Systems in scope are backed up at least [daily]. Retention follows a grandfather-father-son scheme: [daily copies kept 14 days; weekly copies kept 8 weeks; monthly copies kept 12 months], unless a legal or contractual requirement demands longer for a specific system (recorded in Appendix A).

4. Storage and protection of backup copies

At least [two] copies of each backup are maintained, of which at least one is stored offsite or in cloud storage, physically separate from the primary systems. At least one copy is protected against modification and deletion (immutable storage / object lock) where the storage platform supports it. Backups containing personal or confidential data are encrypted at rest. Access to backup storage and backup software is restricted to [named roles] and uses credentials distinct from day-to-day administrative accounts.

5. Verification and restore testing

Backup completion alone is not treated as evidence of recoverability. Backups are verified on an ongoing basis for existence, freshness and integrity, and alerts for failed or missing backups are reviewed by [role] each business day. A restore test of at least one in-scope system is performed at least [quarterly], the result and duration recorded. Each in-scope system must have a successful restore test at least [annually].

6. Responsibilities

The [IT Manager] owns the operation of this policy: schedules, monitoring, verification, restore tests, and the Backup Register. The [Managing Director] approves this policy, reviews the monthly backup report, and approves exceptions.

7. Exceptions

Any deviation from this policy (a system not backed up, retention shorter than stated, a missed restore test) is recorded with a reason, an owner and a target date, and reported in the monthly backup report.

8. Review

This policy is reviewed at least annually, and after any significant incident or infrastructure change.

Appendix A: Backup Register

For each system: name; data it holds; backup method and destination; frequency; retention; encrypted (y/n); immutable copy (y/n); last restore test date and result.

Clause-by-clause: how an auditor reads it

The header block (version, owner, approver, review date) is checked before anything else. A policy with no owner or no review date signals a document written once and forgotten.

Scope (§2): the auditor will pick a system from your network diagram and ask where it appears in Appendix A. The "new systems within 5 days" line answers the most common coverage failure: the server added after the policy was written.

Schedule & retention (§3): what's checked here is not the numbers but whether reality matches them. Claiming daily backups you run weekly is worse than honestly stating weekly.

Storage (§4): this is the ransomware clause. Offsite + immutable is what separates "we have backups" from "an attacker with admin credentials still can't destroy our backups."

Verification (§5): the sentence "backup completion alone is not treated as evidence" is the one auditors most like to see, because it shows you understand the difference between a job log and proof. Expect to be asked for the restore-test records this clause promises.

Exceptions (§7): a policy with a working exceptions process is more credible than a policy that claims perfection. Auditors trust documents that admit gaps and date them.

Policy vs. practice

An auditor's finding is rarely "the policy is bad." It is "the policy says X and you could not show us X." The moment you adopt this document, §5 starts generating homework: daily alert reviews, quarterly restore tests, records of both. That is the part worth automating: continuous verification, restore tests on a schedule, and evidence collected as a by-product. This is exactly what Backup Governor does. For what the evidence should look like, see How to Prove Your Backups Actually Work.

Disclaimer: this template is a starting point, not legal or audit advice. Adapt it to your actual practice (a policy that overstates what you do will hurt you in an audit more than a modest one) and have it reviewed against any regulatory requirements specific to your industry.

Free for one node

Make §5 run itself

Backup Governor gives you the daily verification, scheduled restore tests and evidence records this policy commits you to, free for one node.

Get started free
No credit card requiredCancel anytime

Want to see these best practices in action?

Start for free and experience proper backup monitoring firsthand.

No credit card required
Cancel anytime