# CIS Controls v8 17.1 — Designate Personnel to Manage Incident Handling - Source: https://support.icompaas.com/compliance/cis-controls-v8/17-1-designate-personnel-to-manage-incident-handling - Section: [Compliance](https://support.icompaas.com/compliance) › [CIS Critical Security Controls v8](https://support.icompaas.com/compliance/cis-controls-v8) › Control 17 — Incident Response Management - Last updated: 2026-06-05 - Publisher: iCompaas, Inc. (https://www.icompaas.com) **CIS Controls v8**·Control `17.1`·critical·Component: **Respond** ## What this control requires > Designate a primary person and a backup to manage the enterprise's incident handling process. They coordinate and document incident response and recovery, whether handled internally, by third-party vendors, or a mix. If using a third party, assign an internal contact to oversee their work. Review roles annually or after major enterprise changes. > > — CIS Controls v8, Control 17.1 ### In plain English Designate a primary person and a backup to manage the enterprise's incident handling process. In practice, this means you can prove you document response-level controls on a defined cadence. ## Why it matters The CIS Controls are an industry-vetted, prioritised defence: skipping a safeguard widens the attack surface that the safeguards above and below it assume is closed. Audit frameworks (FedRAMP, PCI DSS, HIPAA) all cite CIS as evidence of due care. This control is rated **critical** in the source catalogue. Treat gaps here as production incidents in the risk register, not housekeeping. ## What an auditor looks for A CIS-aligned reviewer wants to see (a) which Implementation Group you are targeting, (b) a documented owner for the safeguard, and (c) a tooling or process artefact (config, scan output, ticket) that proves the safeguard runs on the cadence the control demands. Within **Respond**, the assessor will trace your implementation back to the catalogue reference (Control 17.1) and look for objective evidence on the latest two assessment cycles. ## How to implement #### Incident Response **Runbook.** Maintain a runbook keyed by incident type with named roles (IC, comms, scribe), an out-of-band comms channel, and a 72-hour timeline for external notification. **Tabletop.** Run a quarterly tabletop exercise (ransomware, insider, supply-chain) and feed gaps back into the runbook. ### Operational checklist - **Document.** Document the trigger, the owner and the cadence. - **Manage.** Document the trigger, the owner and the cadence. - **Designate.** Document the trigger, the owner and the cadence. - **Assign.** Document the trigger, the owner and the cadence. - **Scope:** response, third party vendors, enterprise. ## Evidence to collect - **Vendor Risk Management.** `vendor_risk_management` evidence - **Policy Document.** A signed and version-controlled policy / standard / procedure document. Third-party risk management evidence (assessments, contracts, due diligence) shows supplier oversight. Signed policy or standard documents the safeguard. Focus: Designate Personnel to Manage Incident Handling. ## Common pitfalls - Runbooks that name a role but no person, or list a paging channel that no longer exists. ## How it maps to other frameworks Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit. - [**SOC 2 (2017 TSC) P6.5** — Third-Party Breach Notification Commitments](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/p6-5-third-party-breach-notification-commitments) - [**ISO/IEC 27701:2025 A.3.10** — Supplier agreements](https://support.icompaas.com/compliance/iso-27701-2025/a-3-10-supplier-agreements) ## Related controls in CIS Controls v8 - [**Control 17.4** — Establish and Maintain an Incident Response Process](https://support.icompaas.com/compliance/cis-controls-v8/17-4-establish-and-maintain-an-incident-response-process) - [**Control 17.2** — Establish and Maintain Contact Information for Reporting Security Incidents](https://support.icompaas.com/compliance/cis-controls-v8/17-2-establish-and-maintain-contact-information-for-reporting-security-incidents) - [**Control 11.5** — Test Data Recovery](https://support.icompaas.com/compliance/cis-controls-v8/11-5-test-data-recovery) - [**Control 15.1** — Establish and Maintain an Inventory of Service Providers](https://support.icompaas.com/compliance/cis-controls-v8/15-1-establish-and-maintain-an-inventory-of-service-providers) - [**Control 5.3** — Disable Dormant Accounts](https://support.icompaas.com/compliance/cis-controls-v8/5-3-disable-dormant-accounts) - [**Control 11.2** — Perform Automated Backups](https://support.icompaas.com/compliance/cis-controls-v8/11-2-perform-automated-backups) ## References - [Center for Internet Security — CIS Controls v8](https://www.cisecurity.org/controls/v8) - Catalogue identifier: `Control 17.1` Topics: governance riskincident responsevendor riskvendor managementbackup recoverysupply chain security ## Related compliance guidance - [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Configuration checks like this one are the technical half of a SOC 2 / ISO 27001 programme — the guide shows where they fit, what else an auditor expects, and how to evidence them. - [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): ISO 27001 Annex A.8 (technological controls) is where cloud hardening evidence lands; the guide shows how to run the ISMS around it.