Testing your incident response capability (IR.L2-3.6.3) is not a one-off checklist item — it's an evidence-driven process that shows you can detect, contain, eradicate, and recover from events affecting Controlled Unclassified Information (CUI) in line with NIST SP 800-171 Rev.2 / CMMC 2.0 Level 2 expectations; this post gives a practical, step-by-step approach, tools, and small-business scenarios to design repeatable tests and collect assessor-ready evidence.
Understanding IR.L2-3.6.3 and what assessors look for
IR.L2-3.6.3 requires organizations to test their incident response (IR) processes — not just document them. Key objectives: validate detection and escalation paths; exercise playbooks; verify communications, containment, and recovery procedures; and demonstrate continuous improvement through after-action activities. Evidence an assessor will expect includes: test plans and objectives, participant rosters, test logs and time-stamped artifacts (SIEM alerts, EDR telemetry, screenshots), after-action reports (AARs), prioritized remediation tickets, and updated IR plan/playbooks showing changes made in response to test findings.
Step-by-step testing process (practical implementation for Compliance Framework)
Define scope, objectives, and success criteria
Start by mapping the test to specific assets that process or store CUI (e.g., a file-share server, cloud storage bucket, or contractor workstation). Define measurable objectives (example: "Validate detection of credential phish yielding lateral movement within 30 minutes" or "Contain ransomware encryption to a single subnet within 60 minutes"). Set success criteria (MTTD under X minutes, containment within Y minutes, recovery to business-critical operations within Z hours). Document scope limits and any production-impact rules to inform stakeholders and third-party testers.
Prepare stakeholders, environment, and evidence collection
Notify executives and legal, obtain authorization, and appoint an incident commander and observers. Prepare technical controls to capture evidence: enable Sysmon/OSQuery on Windows endpoints, ensure EDR logging and packet capture (pcap) points are active, confirm SIEM correlation rules are logging relevant events, and capture baseline telemetry. For cloud workloads turn on CloudTrail, flow logs, and audit logging. Define chain-of-custody and evidence retention (e.g., retain logs for 180 days or per contract). For small businesses with limited tooling, use agent-based logging (Wazuh/OSQuery) and cloud-native logs (AWS CloudTrail/GuardDuty) to reduce cost and complexity.
Test types, execution details, and tools
Choose the right mix and run the exercise
Design a program that combines tabletop exercises, walk-throughs, functional tests (playbook walk-throughs with live actions), and annual full-scale or red-team style simulations. Tabletop: script a phishing that simulates CUI access and walk through escalation steps with stakeholders — capture decisions and timings. Functional test: execute a simulated malware outbreak in an isolated lab or use benign simulated behaviors via Atomic Red Team (e.g., simulated credential dumping) or Caldera to trigger EDR detections and SIEM alerts. For live network tests in production, use controlled blameless scenarios like account compromise (with a test account) or a simulated data exfiltration using a designated test bucket to validate DLP and egress controls. Tools to consider: Atomic Red Team, MITRE Caldera, Velociraptor, Wazuh, Elastic/Splunk, Microsoft Defender ATP / Sentinel, AWS GuardDuty + CloudTrail. Log and timestamp everything — timestamps are the primary evidence that MTTD/MTTR thresholds were met.
After-action analysis, remediation, and compliance evidence
Immediately after a test run a hotwash to capture observations while fresh, then produce an AAR that includes: timeline of events with timestamps (detection, escalation, containment, eradication, recovery), gaps identified, root causes, and prioritized remediation actions with owners and SLAs. Update IR playbooks, detection rules, and runbooks; document implemented changes. For compliance, keep the test plan, signed authorization, participant list, logs, AAR, remediation ticket list, and evidence demonstrating remediation closure. If an assessor queries your process, present a matrix mapping each test objective to artifacts and the control language of IR.L2-3.6.3 to demonstrate traceability.
Real-world small-business scenarios and examples
Scenario A — Phishing + Lateral Move: A small engineering contractor runs a tabletop where a phishing email results in credential capture of a non-admin user with access to specs stored in an S3 bucket. The test uses a mock phishing link pointing at a designated test server; detection is validated via SIEM alert for suspicious outbound connections and EDR alert on process creation. Measured outcome: detection in 45 minutes, escalation to IR team in 60 minutes, containment by disabling account and isolating host in 90 minutes. Evidence: email headers, SIEM alert log, EDR process tree, account-disable action in IAM audit logs, and AAR. Scenario B — Ransomware Simulation: In a sandbox environment, simulate file-encryption behavior using a permitted benign script that mimics file renames, trigger EDR ransomware heuristics, and verify backup restoration and offline backup integrity. Small businesses can run this annually and keep checklist evidence proving backups are restorable, meeting recovery objectives and demonstrating the ability to recover CUI-bearing systems.
Compliance tips, best practices, and risks of non-implementation
Best practices: test at least annually and after major changes (new cloud workloads, M&A, major patching); rotate test scenarios to cover insider threat, supply-chain compromise, cloud misconfiguration, and ransomware; maintain a metrics dashboard (MTTD, MTTR, percent of playbooks validated); and automate evidence capture where possible (SIEM dashboards, EDR exports, signed AARs). Keep tests scoped to avoid business disruption and obtain executive sign-off. The risk of not implementing IR.L2-3.6.3 is material: undetected breaches, extended downtime, loss of CUI, contract termination with DoD or primes, regulatory fines, and reputational damage. From a compliance standpoint, lack of test evidence is a frequent cause of failed assessments — documentation and timestamped artifacts are essential to pass a CMMC Level 2 assessment.
Summary: Treat IR.L2-3.6.3 as an ongoing program: define measurable objectives tied to CUI assets, run a mix of tabletop and technical exercises, instrument systems to capture forensic-quality evidence, produce timely AARs, and close remediation items promptly; for small businesses this can be achieved incrementally using cloud-native logging, open-source tooling, and a regimented test cadence to both reduce risk and produce the assessor-ready artifacts that demonstrate compliance with NIST SP 800-171 Rev.2 / CMMC 2.0 Level 2.
