17.5
IG2 IG3

Assign Key Roles and Responsibilities

Asset Type: N/A
Security Function: Respond

Description

Assign key roles and responsibilities for incident response, including staff from legal, IT, information security, facilities, public relations, human resources, incident responders, and analysts, as applicable. Review annually, or when significant enterprise changes occur that could impact this Safeguard.

Implementation Checklist

1
Define response procedures and playbooks
2
Assign response roles and responsibilities
3
Establish response timeframes and SLAs
4
Test response procedures through tabletop or simulation
5
Document lessons learned and update procedures
6
Develop incident response plan and playbooks
7
Define roles, escalation paths, and communication channels
8
Conduct tabletop exercise to validate plan
9
Establish post-incident review process

Threats & Vulnerabilities (CIS RAM)

Threat Scenarios

Critical Response Function Unfilled During Incident

Integrity

During a breach, no one is assigned to handle legal obligations such as breach notification or evidence preservation, resulting in regulatory violations and potential spoliation of evidence.

Conflicting Decisions from Multiple Uncoordinated Teams

Availability

IT, security, legal, and public relations teams make contradictory decisions during an incident because no predefined role assignments clarify who is responsible for which response functions.

Vulnerabilities (When Safeguard Absent)

No Predefined Role Assignments for Incident Response

Without assigned roles spanning legal, IT, security, facilities, PR, and HR, critical response functions are either duplicated or completely unaddressed during incidents.

Cross-Functional Coordination Gaps

Absence of defined roles means non-technical functions like legal, HR, and public relations are not integrated into the incident response, causing delays in notifications, employee actions, and public communications.

Evidence Requirements

Type Evidence Item Collection Frequency
Document Response procedure/playbook documentation Reviewed bi-annually
Record Response action logs showing procedure execution Per incident
Document Incident response plan and playbooks Reviewed bi-annually
Record Incident reports and post-incident review documentation Per incident
Document Governing policy document (current, approved, communicated) Reviewed annually

Related Policy Templates