Establishing secure connection…Loading editor…Preparing document…

Incident Response Support Plan

This template is fully customizable. Edit the text, fill out the fields, and send it for signature. Give it a try!

INCIDENT RESPONSE SUPPORT PLAN

RECITALS

This Incident Response Support Plan (the "Plan") is entered into by and between Service Provider: and Client Name: .

WHEREAS, Service Provider maintains staffed incident response capabilities, technical expertise, and processes to investigate, contain, remediate, and report information security incidents; and

WHEREAS, Client desires to retain Service Provider to provide incident response support services under the terms and conditions set forth in this Plan; and

WHEREAS, the parties agree to define scope, service levels, fees, confidentiality obligations and procedures for engagement of incident response services as set forth below.

OBJECTIVE

The objective of this Plan is to establish the services, response levels, responsibilities and contractual terms by which Service Provider will provide incident response support to Client in the event of a suspected or confirmed security incident.

SCOPE OF WORK

INCIDENT CLASSIFICATION & RESPONSE LEVELS

Incidents will be classified by severity. Service Provider's initial prioritization and recommended actions will be consistent with industry practice and the particulars provided by Client.

Critical — widescale service outage, active data exfiltration or confirmed major breach.
High — localized outage, confirmed intrusion with limited scope.
Medium — suspected intrusion, anomalous activity requiring containment.
Low — investigative or advisory support only.

SERVICES AND DELIVERABLES

Services to be provided may include remote incident triage, containment guidance, forensic data collection coordination, malware analysis, eradication guidance, recovery support, and preparation of an incident report.

SERVICE LEVELS

Initial response time is the elapsed time from Client notification to initial analyst contact or assignment of incident to an on-call responder.

24/7 emergency support:

CLIENT RESPONSIBILITIES

PAYMENT TERMS

Client will pay Service Provider for the services and deliverables in accordance with the following fees and schedule.

TERM AND TERMINATION

This Plan commences on Effective Date and continues until terminated in accordance with this section.

Effective Date:

Term End Date:

Either party may terminate this Plan for material breach if the breaching party fails to cure within the stated notice period following written notice. Termination does not relieve Client of payment obligations for services performed prior to termination.

CONFIDENTIALITY

Each party will keep confidential all non-public information disclosed by the other party in connection with this Plan that is designated as confidential or that reasonably should be understood to be confidential given the nature of the information and the circumstances of disclosure ("Confidential Information"). Confidential Information excludes information that is (a) publicly known other than by breach of this Plan; (b) rightfully received from a third party without restriction; or (c) independently developed without access to the disclosing party's Confidential Information.

Service Provider may disclose Confidential Information to subcontractors and personnel strictly on a need-to-know basis, provided Service Provider remains responsible for such persons' compliance with confidentiality obligations. Confidential Information containing personal data or business-critical information shall be handled and returned or securely destroyed upon Client's request following the conclusion of incident response activities, to the extent permitted by law and forensic obligations.

LIMITATION OF LIABILITY & INDEMNIFICATION

Except for willful misconduct or gross negligence, neither party will be liable for incidental, consequential, indirect or punitive damages. Service Provider's aggregate liability arising from or relating to this Plan will not exceed the total fees paid by Client to Service Provider under this Plan in the twelve months preceding the claim.

Client will indemnify, defend and hold harmless Service Provider and its personnel from third-party claims arising from Client's use of services, Client's negligence, or Client's failure to follow Service Provider's reasonable containment and remediation instructions.

GOVERNING LAW

This Plan will be governed by and construed in accordance with the laws of , without regard to conflict of law principles.

ENTIRE AGREEMENT

This Plan, together with any executed statement of work, fee schedule or appendix expressly incorporated herein, constitutes the entire agreement between the parties with respect to its subject matter and supersedes all prior agreements, proposals and communications, whether written or oral.

CONTACTS FOR INCIDENT NOTIFICATION

MISCELLANEOUS

Any amendments to this Plan must be in writing and signed by authorized representatives of both parties. If any provision is found unenforceable, the remainder of the Plan will remain in effect.

Service Provider:

By:

Date:

Client:

By:

Date:

Enter text✕

What the Incident Response Support Plan Is

An Incident Response Support Plan is a documented, role-based playbook that defines detection, escalation, containment, forensic handling, communication and recovery steps for cyber and data incidents. It centralizes responsible parties, contact information, authorization thresholds, evidence preservation rules and post-incident review procedures to reduce response time and support regulatory reporting.

Why a Formal Plan Matters for Response

A formal Incident Response Support Plan clarifies responsibilities, accelerates decision making, preserves evidence and helps meet regulatory notification obligations under ESIGN/UETA, HIPAA and state breach laws, reducing operational disruption and legal exposure when incidents occur.

Why a Formal Plan Matters for Response

Primary Teams and Roles That Use This Plan

Core stakeholders who prepare and rely on the plan span security, IT, legal and executive functions.

  • Security Operations — Incident handlers, SOC analysts, and forensics engineers who execute technical containment and evidence preservation.
  • Legal and Compliance — Counsel and privacy officers who assess reportability, regulatory obligations, and notification timing.
  • IT / Infrastructure — System owners and administrators who apply containment, recovery, and change controls.

Essential Components of a Professional Incident Response Support Plan

A complete plan combines governance, technical playbooks, communication templates, evidence handling rules and continuous improvement steps so teams can respond consistently across incident types and regulatory contexts.

Governance

Escalation matrix and approval authorities for operational decisions, legal notifications, and executive briefings; lists alternate signatories and decision thresholds.

Detection & Triage

Clear criteria for event classification, initial triage steps, required logs and immediate containment actions tailored to common attack vectors.

Containment & Eradication

Technical containment procedures, isolation checklists, temporary mitigations, and steps to remove malware or unauthorized access with rollback considerations.

Forensics & Evidence

Chain-of-custody procedures, secure evidence storage, forensic imaging guidance and designated custodians responsible for preserving artifacts.

Notifications

Templates and timelines for internal stakeholders, regulators, affected individuals and vendors; criteria for public statements and law enforcement engagement.

Post‑Incident Review

Root cause analysis process, remediation tracking, updates to controls and training schedules to prevent future recurrence.

Security and Compliance Facts to Include

Encryption: TLS 1.2/1.3 in transit; AES-256 at rest
Audit Trail: Timestamped logs with signer attribution
HIPAA Support: BAA available where required
Regulatory Standards: SOC 2 Type II and ISO 27001
21 CFR Part 11: Compliant options exist
Accessibility: WCAG 2.0 Level AA

Key Risks if the Plan Is Incorrect or Incomplete

Regulatory Fines: HIPAA or state penalties possible
Missed Notifications: Late notice increases liability
Evidence Loss: Forensic gaps harm prosecutions
Operational Downtime: Uncoordinated response extends outages
Contract Breach: Vendor/partner obligations may trigger
Reputational Harm: Customer trust and market impact

How to Complete an Incident Response Support Plan

Follow a reproducible sequence: collect contacts, define authority, set detection thresholds, create playbooks, test and finalize approval channels.

  • 01
    Gather Contacts: List names, roles, phone and secure emails.
  • 02
    Define Roles: Assign responsibilities for each incident stage.
  • 03
    Write Playbooks: Create stepwise technical and communication procedures.
  • 04
    Approve & Test: Obtain signatory approval and run tabletop exercises.

Configuring the Plan for Online Completion

Set up conditional fields, authentication and retention settings so signatures are captured with an auditable trail and the document is reproducible for regulators.

Field Configuration
Template Create reusable template with locked sections
Conditional Fields Show playbook sections based on incident type
Authentication Enable email, SMS or advanced signer verification
Retention Set automatic retention and export settings

Technical Delivery and Integration Options

Consider integrations and file formats that preserve metadata, audit trails and evidence integrity when sharing the plan.

  • Integrations: Salesforce, NetSuite, Microsoft 365, Google Workspace
  • File Formats: PDF/A, DOCX, and exported audit logs
  • Storage: Cloud storage with versioning and access controls

Where to Send and Store the Completed Plan

Decide primary repositories and distribution lists so the approved plan is accessible to responders while remaining protected from unauthorized changes.

  • Internal Repository: Store master copy in a secured document management system.
  • Incident Platform: Attach active version to SIEM or ticketing system.
  • Legal Archive: Keep signed copy in compliance archive for audits.
  • Keyholder Distribution: Provide signed plan to designated incident contacts.

Typical Response Timelines and Expectations

Timelines vary by incident severity and applicable law; assign clear target windows for detection, triage, containment, notifications and post-incident reporting.

Initial Triage Window:

Identify and classify incident within 24 hours of detection.

Containment Target:

Enact containment measures within 72 hours for high-severity events.

Regulator Notification:

Follow HIPAA and state breach rules; many require notice within 30–60 days.

Affected Parties:

Notify affected individuals per applicable law and contractual obligations.

Post‑Incident Report:

Deliver root cause analysis and remediation plan within 30–90 days.

Common Mistakes to Avoid When Preparing the Plan

  • Omitting updated contact details and alternate contacts, which stalls escalation and leads to missed deadlines or ineffective containment.
  • Using vague escalation criteria instead of measurable thresholds, causing delayed or inconsistent activation of response teams.
  • Failing to preserve forensic evidence immediately, which can make legal or regulatory responses and investigations infeasible.
  • Treating the plan as static without regular testing, resulting in untested assumptions and unclear handoffs during real incidents.

Supporting Documents to Attach to the Plan

Attach operational documents that responders and legal teams will need immediately to reduce confusion and speed remediation.

Network Diagram

Detailed, current network and asset maps showing critical systems, data flows and segmentation so responders can identify affected components quickly and plan containment.

Contact Roster

Complete list of internal and external contacts, including executives, legal counsel, vendors, forensics providers and law enforcement points of contact with escalation instructions.

Runbooks

Step-by-step technical procedures for containment, remediation and recovery for common incident types to reduce dependency on tribal knowledge during crises.

Notification Templates

Prewritten internal, regulator and customer notice templates with variable fields to speed communication while ensuring consistent legal language.

How to Update and Approve Revisions

Maintain a controlled revision process with versioning, approvals and test validation to ensure changes are auditable and effective.

01

Review Cadence:

Schedule quarterly or after major incidents.
02

Change Request:

Log proposed edits and rationale.
03

Approval Workflow:

Require legal and security sign-off.
04

Testing:

Run tabletop exercises after changes.
05

Distribution:

Publish updated version to stakeholders.
06

Archive:

Retain prior versions for audits.

eSignature Pricing and Feature Snapshot for Plan Execution

Compare baseline vendor pricing and common features for executing and storing signed Incident Response Support Plans; signNow appears first as the platform column in this comparison.

signNow DocuSign Adobe Sign PandaDoc HelloSign
Starting Price $8/user/mo $15/user/mo $14/user/mo $19/user/mo $15/user/mo
Free Trial 7-day free trial Varies Varies Varies Varies
Bulk Send Yes Yes Yes Yes Varies
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes Yes Yes No No

Frequently Asked Questions About the Incident Response Support Plan

Answers to common questions about e-signature validity, notarization, signatures authority and retention for Incident Response Support Plans.


Need help? Contact support

be ready to get more
Join over 28 million airSlate SignNow users