Incident Response Policy template (free, plain-language starter)

Free incident response policy template for small companies: full text, the controls it supports and the decisions to make. Not legal advice or a certification.

Template · Updated · by the Controlkeep team

In short

How to report, triage, contain, communicate and learn from security incidents and data breaches. This free starter covers 3 controls and leaves 7 decisions for you; it is original text, not a standard’s wording, and adopting it is not a certification.

How to report, triage, contain, communicate and learn from security incidents and data breaches. Customers and auditors ask for it in customers asking how fast you will tell them about a breach; write it before you need it.

Starter policies are original templates written by Controlkeep. They are a starting point, not legal advice, and adopting them is not a certification or an audit opinion. Adapt every rule to how your company really works, and have a qualified adviser review policies with legal effect (privacy, employment, contracts).

Controls it supports

RefControlStarter framework
TC-OPS-03Incidents are handled to a planSOC 2-style common criteria starter
IS-ORG-06Incident managementISO 27001-style Annex A starter
TC-OPS-01Systems are monitoredSOC 2-style common criteria starter

Decisions to make before approving

  • [1 hour]
  • [out-of-hours phone or channel]
  • [role]
  • [2 hours]
  • [check your contracts]
  • [10 working days]
  • [3 years]

The policy text

Purpose

To make sure security incidents at [Company] are noticed, reported and handled quickly and consistently, that people affected are informed when they need to be, and that we learn from each incident.

Scope

This policy applies to everyone who works for or with [Company] and to all company and customer information and systems, including those run for us by suppliers.

What is an incident

Any event that threatens the confidentiality, integrity or availability of company or customer information, for example: a lost or stolen device, a compromised account, malware, data sent to the wrong person, a suspicious payment request, an outage caused by an attack, or a supplier telling us they were breached.

Reporting

  1. Anyone who suspects an incident reports it to [Security Contact] immediately, and in any case within [1 hour] of noticing it, even if unsure.
  2. Do not try to investigate on your own, delete evidence, or contact the attacker.
  3. Out-of-hours reports go to [out-of-hours phone or channel].

Roles

  • Incident lead: [Policy Owner] or a deputy they name. Leads the response, decides severity, and keeps the record.
  • Technical responders: the people who own the affected systems.
  • Communications: [role] handles messages to customers, staff and, where required, regulators.
  • Leadership: informed of every high-severity incident and decides on external notifications with legal advice.

Severity

  • High: confirmed access to customer or personal data, ransomware, or a major outage. Leadership informed within [2 hours].
  • Medium: contained compromise of a single account or device, no evidence of data access.
  • Low: attempted attack with no impact (for example a reported phishing email).

Response steps

  1. Record: open an incident record with time, reporter, what is known and who is involved.
  2. Contain: limit damage, for example by disabling accounts, rotating keys, isolating devices or blocking senders.
  3. Investigate: establish what happened, what data and systems were affected, and when it started. Keep logs and evidence.
  4. Recover: restore systems from known-good states and confirm they work.
  5. Notify: decide with legal advice whether customers, partners or regulators must be told, and meet any legal deadlines (some privacy laws require notifying the regulator within 72 hours of becoming aware of a personal data breach). Customer contracts may set shorter deadlines: [check your contracts].
  6. Learn: within [10 working days] of closing a medium or high incident, hold a blameless review, record root cause and actions, and track the actions to completion.

Records

Every incident, including low-severity ones, is recorded with its timeline, decisions and actions. Records are kept for at least [3 years].

Testing

The response process is rehearsed at least once a year, for example with a short tabletop exercise.

Exceptions

Exceptions to this policy must be requested in writing, approved by [Policy Owner], recorded with a reason and an end date, and reviewed when they expire.

Enforcement

Breaking this policy may lead to loss of access and to disciplinary action in line with employment contracts and local law. Contractors may have their engagement ended.

Review

[Policy Owner] owns this policy and reviews it at least every [Review Period], and after any major incident or change in how [Company] works. Questions go to [Security Contact].

Adopt it

  1. Copy the policy below, or create it from the starter library in Controlkeep, where [Company], [Policy Owner], [Security Contact] and [Review Period] are filled from a form.
  2. Decide the 7 remaining bracketed items so the rules match how you actually work.
  3. Approve it, ask staff to acknowledge it, and link it to the controls it supports so auditors can follow the trail.

Related: collecting audit evidence, policies help, Business Continuity and Backup Policy, Change Management Policy.

Questions and answers

What notification deadline should we write?

Use the shortest one in your contracts and the laws that apply to you; the bracketed deadline in the starter is a decision you must make.

Does adopting this incident response policy make us SOC 2 or ISO 27001 compliant?

No. Policies are one part of a programme; an auditor tests whether you follow them over time. Controlkeep helps you keep the evidence, but it is not a certification or an audit opinion.

Try Controlkeep free

A working control register: owners, evidence, policies and reviews in one place, with exports your auditor can read. The Free plan needs no card; you can export or delete your data any time.