CIS Control 17: Incident Response Management
Decide now who does what when something goes wrong, so a security incident is handled quickly and calmly instead of improvised. The faster you contain a breach, the less it costs.
What it means
Establish a program to develop and maintain an incident response capability: policies, plans, procedures, defined roles, training and communications to prepare for, detect and quickly respond to an attack.
Why it matters
Breaches contained in under 200 days cost about 25% less (IBM Cost of a Data Breach Report 2026). A plan and practiced roles are what make fast containment possible.
Key safeguards
Designate personnel to manage incident handling (IG1)
Establish and maintain contact information for reporting security incidents (IG1)
Establish and maintain an enterprise process for reporting incidents (IG1)
Establish and maintain an incident response process, with assigned roles and responsibilities (IG2)
Define mechanisms for communicating during incident response (IG2)
Conduct routine incident response exercises and post-incident reviews (IG2)
Establish and maintain security incident thresholds (IG3)
How Prominic helps
Recovery from offsite and air-gapped backups, and desktops rebuilt from one clean central image
Prominic engineers who help you recover when it matters
Our compliance tracking grows into formal incident response planning when you need it
Incident response plans and exercises: details to confirm
Where it fits
Knowing who handles incidents and how they are reported is IG1; a full response process and exercises come in IG2.
See also: Control 11: Data Recovery, and Control 8: Audit Log Management.
