Join our Newsletter — 33% off our NHI Course
Home› Guides› CIS Control 17 Incident Response Management Guide: Safeguards,…
Guide Regulations & Frameworks

CIS Control 17 Incident Response Management Guide: Safeguards, Implementation Groups and Evidence

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 26 October 2026 13 min read
On this page

Many organisations have an incident response plan on file but fail CIS Control 17 because the plan is more than a year old, names roles without people, and has never been exercised. CIS Control 17 (Incident Response Management) in CIS Controls v8.1 asks for a programme to develop and maintain an incident response capability: policies, plans, procedures, defined roles, training and communications. This guide covers the nine Safeguards by Implementation Group, what the CIS Controls Assessment Specification checks for each, an order of work, the evidence to keep and the mapping to NIST, ISO and NIST SP 800-61 Rev. 3. It is for security managers, incident response leads and GRC teams preparing for a CIS assessment. How to actually run incident response (playbooks, CSIRT roles, containment, reporting deadlines) is covered in the Incident Response Guide; this page stays with the Safeguards and their evidence.

Key takeaways

  • IG1 is about people, contacts and reporting. Safeguards 17.1 (incident handling manager and backup), 17.2 (contact list) and 17.3 (workforce reporting process) apply to every organisation.
  • The twelve-month clock fails most Safeguards. The assessment specification gives a failing score to 17.1 to 17.7 and 17.9 if the documentation, or for 17.7 the last exercise, is more than twelve months old.
  • Roles must map to named individuals. For 17.5 the specification counts roles mapped and not mapped to an individual, so a role list without names, deputies and contact details is a gap.
  • Exercises and reviews are Recover Safeguards. 17.7 (annual exercises) and 17.8 (post-incident reviews with lessons learned and follow-up actions) are what turn a plan into a capability.
  • Identity is both a responder and a target. Responders need break-glass access that survives an identity provider outage, and eradication is incomplete until exposed human and non-human credentials are rotated.

What it is and who it applies to

CIS describes the purpose of Control 17 as establishing a programme to develop and maintain an incident response capability to prepare, detect and quickly respond to an attack. It is an organisational Control: the Safeguards apply to the enterprise as a whole, not to an asset class.

  • IG1: 17.1, 17.2 and 17.3, plus 17.9 (incident thresholds), which the assessment specification lists for all three groups. Confirm the 17.9 assignment against the v8.1 spreadsheet before formal reporting. A small organisation can meet IG1 with a two-page document naming its incident lead and backup, a contact sheet and a reporting route for staff.
  • IG2: adds 17.4 (incident response process), 17.5 (roles), 17.6 (communication mechanisms), 17.7 (exercises) and 17.8 (post-incident reviews).
  • IG3: no additional Safeguards; the difference is depth, such as more frequent and technical exercises and integration with Control 8 logging and Control 13 monitoring.

CIS Controls v8.1 (June 2024) clarified wording and realigned security functions with NIST CSF 2.0 without changing Implementation Group assignments. The Safeguard titles below follow the CIS Controls Assessment Specification, written for v8.

Structure and key requirements

SafeguardTitleIGWhat it requiresReview cadence
17.1Designate Personnel to Manage Incident HandlingIG1, IG2, IG3One key person and at least one backup to coordinate and document response and recovery; if a third party is used, an internal person oversees itAnnually or on significant change
17.2Establish and Maintain Contact Information for Reporting Security IncidentsIG1, IG2, IG3Contacts for internal staff, vendors, law enforcement, cyber insurer, government agencies, ISAC partners and other stakeholdersVerify annually
17.3Establish and Maintain an Enterprise Process for Reporting IncidentsIG1, IG2, IG3Reporting timeframe, who to report to, mechanism and minimum information; available to the whole workforceAnnually or on significant change
17.4Establish and Maintain an Incident Response ProcessIG2, IG3Roles and responsibilities, compliance requirements and a communication planAnnually or on significant change
17.5Assign Key Roles and ResponsibilitiesIG2, IG3Legal, IT, information security, facilities, public relations, human resources, incident responders and analysts, as applicableAnnually or on significant change
17.6Define Mechanisms for Communicating During Incident ResponseIG2, IG3Primary and secondary mechanisms (phone, email, letters), recognising that some, such as email, may be affectedAnnually or on significant change
17.7Conduct Routine Incident Response ExercisesIG2, IG3Exercises and scenarios for key personnel that test communication channels, decision making and workflowsAt least annually
17.8Conduct Post-Incident ReviewsIG2, IG3Reviews that identify lessons learned and follow-up actions to prevent recurrenceAfter incidents
17.9Establish and Maintain Security Incident ThresholdsIG1, IG2, IG3 (per assessment specification)Thresholds that at minimum distinguish an event from an incident, for example abnormal activity, vulnerability, weakness, data breach, privacy incidentAnnually or on significant change

How to read the requirements

  • 17.2 contacts are external as well as internal: include the cyber insurer's breach hotline and panel requirements, your incident response retainer, the national CERT or NCSC reporting route, the relevant data protection authority, sector regulators and any ISAC. Many insurance policies set conditions on which responders you appoint, so check before an incident. See the Cyber Insurance Guide.
  • 17.3 must be visible to everyone: the specification fails the metric if the reporting process is not available to the whole workforce. An intranet page, phishing report button and a phone number on the security awareness material meet it.
  • 17.4 "compliance requirements": list the notification clocks that apply to you, such as GDPR Article 33's 72 hours to the supervisory authority. Do not rebuild the list here: see the Cyber Incident Reporting Requirements Map.
  • 17.9 is the declaration rule: it defines when an event becomes an incident and therefore when the plan starts. Pair it with a severity matrix. See the Incident Severity Classification Matrix Template.

Identity and NHI requirements

Incidents increasingly start with a stolen credential or token, and responders depend on identity systems that may themselves be compromised. Build these into the Control 17 documents.

  • Responder access (17.1, 17.5, 17.6): the incident lead and backups need emergency access that does not depend on the production identity provider, and an out-of-band channel if email and chat are suspected compromised. Document and test break-glass accounts in exercises. See the Break-Glass Account Guide.
  • Identity owners as named roles (17.5): include the identity provider administrator, the secrets or PAM owner and the cloud platform owner, because containment often means disabling accounts, revoking sessions and rotating keys.
  • Thresholds for non-human identities (17.9): state that a leaked API key, token or service account secret, or anomalous use of one, is an incident even when no data loss is confirmed. ATT&CK T1078 Valid Accounts and T1078.004 Cloud Accounts are common initial access routes that will not trigger malware-based thresholds.
  • Complete rotation in eradication (17.8): post-incident reviews should verify that every exposed credential was rotated. In the Cloudflare Thanksgiving breach, a service token and three service account credentials left unrotated after the Okta support system breach, because they were wrongly believed unused, gave a nation-state actor access in November 2023. See the Identity Incident Response Playbook.

Implementation steps

  1. Name the incident manager and backup (17.1): record names, deputies and out-of-hours contacts; if an MSSP or retainer handles response, name the internal person who oversees it. Get executive approval.
  2. Build and verify the contact list (17.2): internal, supplier, insurer, retainer, law enforcement, regulator and ISAC contacts, held both online and in a copy available offline. Set an annual verification task.
  3. Publish the reporting process (17.3) and thresholds (17.9): what to report, how fast, through which route and with what minimum information; define event versus incident and severity levels.
  4. Write the incident response process (17.4) with roles (17.5) and communication mechanisms (17.6): map every role to a person and a deputy, include legal, HR, communications and facilities, set a primary and secondary channel for each audience, and record regulatory notification duties. Start from the Incident Response Plan Template.
  5. Exercise (17.7): run at least one exercise a year covering communication channels, decisions and workflow, starting with a facilitated tabletop and moving to technical simulations. Free scenario sets include CISA Tabletop Exercise Packages and the NCSC's Exercise in a Box. See the Tabletop Exercise Guide.
  6. Review incidents and exercises (17.8): hold a blameless review after every significant incident and exercise, record lessons learned, assign follow-up actions with owners and dates, and track them to closure. See the Post-Incident Review and Root Cause Analysis Template.
  7. Set the annual review: one review date for all Control 17 documents, with triggers for earlier review (reorganisation, new regulator, new outsourcing, major incident).

Choosing an exercise format for 17.7

FormatWhat it testsBest forEvidence produced
Discussion tabletopDecision making, roles, escalation and notification dutiesExecutives and first annual exercise; IG1 and IG2 organisationsAttendance, scenario, after-action report with actions
Communication drillContact list accuracy (17.2) and secondary channels (17.6)Quarterly checks between full exercisesCall-tree results, failed contacts corrected
Technical simulationDetection, containment steps, credential revocation and restoreSecurity operations and platform teams; IG3 depthTimings against targets, gaps in tooling or access
Full functional exerciseEnd-to-end workflow across IT, legal, communications and suppliersLarge or regulated organisationsFormal report, regulator-ready evidence, action plan

Rotate scenarios so that over two to three years the exercises cover ransomware, business email compromise, cloud or SaaS account takeover, a supplier incident and a leaked non-human credential. See the Tabletop Exercise Scenario Pack.

Small versus large organisations

  • Small (IG1): a short plan, a contact sheet and a single reporting route are enough. Use an insurer or retainer for specialist response, but keep 17.1's internal oversight role.
  • Large (IG2/IG3): the hard parts are coordination and currency. Integrate Control 17 with business continuity, crisis management and supplier contracts, run separate executive and technical exercises, and keep role assignments synchronised with HR changes. See the Incident Response Maturity Model.

Evidence and assessment

The assessment specification takes its inputs from incident response documentation and the incident response process, and checks existence, required components and age.

SafeguardEvidence an assessor expectsMeasure in the specification
17.1Plan or appointment record naming manager and backup; third-party oversight namedExists; fails if over 12 months since review
17.2Contact list with verification dateExists; fails over 12 months
17.3Reporting procedure and proof it is published to all staffExists; components; fails over 12 months; metric fails if not available to all
17.4Approved incident response process covering roles, compliance and communicationExists; components; fails over 12 months
17.5RACI or role table with named individuals and deputiesRoles mapped and not mapped to an individual; fails over 12 months
17.6Communication plan with primary and secondary mechanismsCount of mechanisms; fails over 12 months
17.7Exercise plans, attendance, after-action reportsFails if more than 12 months since the last exercise
17.8Post-incident review reports, action trackerProcess includes reviews; lessons learned and follow-up actions present
17.9Threshold and severity definitionsExists; fails over 12 months

Metrics that show it is working

  • Documentation currency: months since review of each Control 17 document (target 12 or fewer, matching the specification).
  • Role coverage: percentage of incident roles with a named, current individual and deputy.
  • Exercise coverage: priority scenarios exercised in the last 12 months, including at least one identity or credential compromise scenario.
  • Action closure: percentage of post-incident and post-exercise actions closed by their due date.
  • Time to declare: median time from first alert to incident declaration under the 17.9 thresholds.

Mapping to other frameworks

SafeguardsNIST CSF 2.0NIST SP 800-53 Rev 5ISO/IEC 27001:2022 Annex A
17.1, 17.5GV.RR-02IR-7, IR-8A.5.24 Information security incident management planning and preparation
17.2, 17.6RS.CO-02, RS.CO-03IR-6, IR-8A.5.5 Contact with authorities, A.5.6 Contact with special interest groups
17.3RS.MA-02IR-6A.6.8 Information security event reporting
17.4ID.IM-04, RS.MA-01IR-1, IR-4, IR-8A.5.24, A.5.26 Response to information security incidents
17.7ID.IM-02IR-2, IR-3A.5.24
17.8ID.IM-03, RC.RP-01IR-4A.5.27 Learning from information security incidents
17.9DE.AE-08, RS.MA-03, RS.MA-04IR-4, IR-5A.5.25 Assessment and decision on information security events

NIST SP 800-61 Rev. 3 (April 2025), which superseded Rev. 2 of 2012, is now a CSF 2.0 Community Profile, so CSF Govern, Identify, Detect, Respond and Recover outcomes are the natural crosswalk for Control 17. The NIST SP 800-61 Incident Response Guide covers it in depth. Use the official CIS v8.1 mappings for formal crosswalks.

Common pitfalls

  • A stale plan: documents not reviewed in 12 months fail outright, however good they are. One annual review date for all Control 17 documents avoids drift.
  • Roles without people: "Head of IT" with no named deputy fails 17.5 counts and fails in a real incident at 2 a.m.
  • Single-channel communication: plans that rely on corporate email and chat leave responders blind when those platforms are compromised; 17.6 requires a secondary mechanism.
  • Exempting "unused" credentials during eradication: the Cloudflare intrusion succeeded through four credentials skipped for that reason. Post-incident reviews should check rotation completeness.
  • Unprepared decisions: shutdown, ransom and disclosure choices made without pre-agreed criteria are slow and costly. In the Colonial Pipeline ransomware attack, the proactive pipeline shutdown contained the attack but halted fuel supply for nearly a week. Name who decides and on what criteria in 17.4, and rehearse it in 17.7.
  • Reviews without follow-through: lessons are written down but actions have no owner or date, so 17.8 evidence exists while nothing changes. Track action closure.

Practitioner checklist

  • Confirm the target Implementation Group and check the 17.9 assignment in the v8.1 spreadsheet.
  • Name the incident manager and backup, and an internal overseer for any third-party responder.
  • Verify internal and external contacts annually, including insurer, retainer, regulators and ISAC, and keep an offline copy.
  • Publish the workforce reporting process where every employee can find it.
  • Define event versus incident thresholds that include leaked or misused non-human credentials.
  • Map every incident role to a named person and deputy, including identity, secrets and cloud owners.
  • Document primary and out-of-band communication mechanisms and test them.
  • Run at least one exercise a year and produce an after-action report.
  • Hold post-incident reviews with owned, dated actions and check credential rotation completeness.
  • Review all Control 17 documents at least every 12 months.

Standards and references

Related NHI Mgmt Group resources: Incident Response Guide · CIS Controls Guide · Incident Response Plan Template · CIS Control 16 Application Software Security Guide · CIS Control 18 Penetration Testing Guide

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 26 October 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.