PIVTR-D

Program mapping: NIST CSF 2.0

Assessors working from the NIST Cybersecurity Framework (CSF) 2.0 check an incident response program against its functions and categories. PIVTR-D phases already produce the evidence they ask for. This page shows where each phase lands in CSF 2.0 and which record proves it.

The book maps its Dynamic Approach to Incident Response (DAIR) at function level for Protect, Detect, Respond and Recover, and at category level for Govern. The category crosswalk for the other functions is this site's addition from the CSF 2.0 text.

DAIR names to PIVTR-D names

DAIR activityPIVTR-D phase
PrepareP. Preparation
DetectI. Identification
Verify, TriageV+T. Verification and triage
Response Actions Loop: Scope, Contain, Eradicate, RecoverR. Response loop: Scope, Contain, Eradicate, Recover
DebriefD. Debrief
Decision Maker coordination (throughout)Decision makers at every phase; see who authorizes what

What compliance requires

Chapter 20, Table 60, p. 615.

RequirementWhat the assessor looks for
Documented capabilitiesDetection methods, response procedures, decision authority and external coordination, documented across all relevant CSF functions
Demonstrated effectivenessExercises, tabletops or real incidents showing documented procedures are followed and produce the intended outcomes
Metrics and measurementBaselines for detection time, response time, containment effectiveness and recovery duration, tracked as trends
Continuous improvementPost-incident reviews, procedure updates from lessons learned, root cause remediation

Function-level mapping

Chapter 20, Table 61 and Figure 200, pp. 616 to 617.

CSF functionDAIR activityPIVTR-DHow it satisfies the function
Govern (GV) / Identify (ID)Decision Maker coordination throughout all activitiesAll phasesAligns response with risk tolerance and supplies context on critical assets, acceptable impacts and strategy. Govern is mapped by category in the next table.
Protect (PR)PreparePResponse procedures, detection capability, forensic readiness and trained personnel limit incident impact.
Detect (DE)Detect, Verify, TriageI, V+TVerify confirms an event is an incident; Triage prioritizes it by organizational impact.
Respond (RS)Response Actions LoopREach iteration through Scope, Contain, Eradicate and Recover adds evidence of comprehensive response.
Recover (RC)Recover, DebriefR (Recover), DRecover restores systems; Debrief captures lessons learned and improvements.

Govern categories

Chapter 20, Table 62, pp. 618 to 619.

GV categoryAssessor expectationDAIR activitiesArtifacts generated
GV.OC Organizational ContextIncident response (IR) decisions reflect regulatory obligations, stakeholder expectations, risk appetite and business environmentPrepare: regulatory notification mapping, stakeholder identification, risk classification criteria. Verify and Triage: per-incident classification against pre-agreed thresholds.Risk classification framework, triage decision records with rationale, regulatory notification trigger log
GV.RM Risk Management StrategyResidual risk at closure assessed, accepted by an authorized individual, and fed into the enterprise risk registerLoop: exit risk acceptance decision. Debrief: lessons mapped to risk register entries. Recover: recovery metrics feeding program trend analysis.Signed loop exit risk acceptance, debrief report with risk register recommendations, metrics trend data sent to enterprise risk
GV.RR Roles, Responsibilities, and AuthoritiesAuthority matrix for declaration, command, business-impact decisions, loop exit and improvement ownership, with named rolesPrepare: team structure, a responsible, accountable, consulted and informed (RACI) chart, escalation thresholds and decision authority documented before incidentsAuthority matrix, escalation procedure, named role assignments per incident type or severity tier
GV.PO PolicyIR policy that separates policy (what should happen), procedure (how) and playbooks (how, per scenario type)Prepare: IR plan, playbooks, communication plan, contact lists, callout rosters, using that taxonomy consistentlyIR policy, procedures per DAIR phase, scenario playbooks, communication plan with last-reviewed timestamp
GV.SC Cybersecurity Supply Chain Risk ManagementSupplier IR obligations defined, contractual notification requirements mapped, supplier access revocation in proceduresPrepare: supplier obligation mapping, data processing agreement (DPA) review schedule, third-party access inventory. Scope and Contain: third-party access revocation. Debrief: supplier root cause and remediation tracking.Supplier obligations register, DPA and contract review records, third-party access revocation log, supplier remediation tracking

Category crosswalk for the other functions

This table is an addition to the book, built from the NIST CSF 2.0 category list. NIST SP 800-61r3 organizes its recommendations by these same CSF 2.0 functions, categories and subcategories. Category names checked October 2026 against SP 800-61r3.

PIVTR-D phaseCSF 2.0 categories
P. PreparationGV.PO, GV.RR, GV.SC; ID.AM Asset Management; ID.RA Risk Assessment; PR.AT Awareness and Training; PR.PS Platform Security (log generation); ID.IM Improvement (IR plans maintained)
I. IdentificationDE.CM Continuous Monitoring; DE.AE Adverse Event Analysis
V+T. Verification and triageDE.AE (incident declaration); RS.MA Incident Management (triage, validation, categorization, prioritization, escalation); GV.OC
R. ScopeRS.AN Incident Analysis; RS.MA
R. ContainRS.MI Incident Mitigation; RS.CO Incident Response Reporting and Communication; GV.SC
R. EradicateRS.MI
R. RecoverRS.MA (criteria for starting recovery); RC.RP Incident Recovery Plan Execution; RC.CO Incident Recovery Communication
Loop exitGV.RM
D. DebriefID.IM; GV.RM; GV.SC

Evidence each phase produces

Chapter 20, Tables 63 and 64, pp. 620 to 621. Template column is this site's mapping.

PhaseArtifacts (book)CSF function (book)Site template
PIR plans, playbooks, contact lists, training records, CSF cross-references in proceduresPRPlan and playbook set
I, V+TAlert logs, dashboards, threat intel reports, triage decisions, false positive records, declaration documentationDET1 Incident record, T2 Triage brief
RScoping analysis, containment decisions, eradication records, recovery verification, accumulated across iterationsRST3, T4 Loop iteration log, T5, T7, T8
Loop exitSigned loop exit risk acceptance (Table 62)GVT6 Residual risk acceptance
DLessons learned, root cause analysis, recommendations, implementation trackingRCT9 After-action review, T10 Executive debrief, T14 Improvement register, T15 Incident report
ThroughoutStakeholder consultation records, guidance, business impact assessments, decision rationaleGV / IDDecision fields in T1 to T3

Effectiveness evidence, from Table 64:

  • DE: incidents found by monitoring and alerting, with trends in mean time to detect.
  • RS: containment that limited scope, and loop passes that caught what a single pass would miss.
  • RC: validated restoration and completed improvements.

Using the mapping in an audit

Chapter 20, pp. 617 to 623.

  • File incident records by CSF function and category, the structure auditors use.
  • Put the CSF cross-reference in the IR plan and in each playbook header.
  • Set tracker statuses in phase vocabulary (Detection Complete, Verification Pending, Containment Active, Eradication in Progress, Recovery Underway) and allow the loop phases to repeat.
  • Add tracker fields for decision makers consulted, guidance given and its effect on the response. These fields are the GV evidence.
  • Link every evidence artifact to its incident record and retain it under the incident retention policy.
  • Tag status updates with the CSF function and PIVTR-D phase, for example "RS, Scope".
  • Log what new information triggered each loop iteration and what remediation followed, in T4.
  • Keep incident reports, timelines and lessons learned in standard formats ready for request. Train responders to explain each phase in CSF terms.
Watch out
  • Auditors read repeated loop passes as process failure unless each pass records its trigger and outcome (pp. 617 to 618).
  • A record of actions without decision rationale fails the artifact requirement (p. 620).
  • The book files Verify and Triage under Detect and Debrief under Recover. CSF 2.0 places triage in RS.MA and improvement in ID.IM, so cite both when an assessor works from the subcategory list.
  • Loop exit with no signed residual risk acceptance leaves GV.RM without evidence. Record it in T6.
Adapts material from Dynamic Incident Response: A Framework for Security Teams by Joshua Wright, © 2026 The Escal Institute of Advanced Technologies, Inc. d/b/a SANS Institute, licensed under CC BY 4.0. Figures reproduced under that license. Changes were made. Not published by, endorsed by, or affiliated with the SANS Institute.