| name | IR-2_incident-response-training |
| description | Provide incident response training to system users consistent with assigned roles and responsibilities: Within [organization-defined] of assuming an i |
| category | configuration |
| version | 5.2.0 |
| author | cyberstrike-official |
| tags | ["nist","sp800-53","rev5","ir-2","ir"] |
| tech_stack | ["any"] |
| cwe_ids | [] |
| chains_with | ["AT-2","AT-3","AT-4","CP-3","IR-3","IR-4","IR-8","IR-9"] |
| prerequisites | [] |
| severity_boost | {"AT-2":"Chain with AT-2 for comprehensive security coverage","AT-3":"Chain with AT-3 for comprehensive security coverage","AT-4":"Chain with AT-4 for comprehensive security coverage"} |
IR-2 Incident Response Training
High-Level Description
Family: Incident Response (IR)
Framework: NIST SP 800-53 Rev 5
Incident response training is associated with the assigned roles and responsibilities of organizational personnel to ensure that the appropriate content and level of detail are included in such training. For example, users may only need to know who to call or how to recognize an incident; system administrators may require additional training on how to handle incidents; and incident responders may receive more specific training on forensics, data collection techniques, reporting, system recovery, and system restoration. Incident response training includes user training in identifying and reporting suspicious activities from external and internal sources. Incident response training for users may be provided as part of AT-2 or AT-3 . Events that may precipitate an update to incident response training content include, but are not limited to, incident response plan testing or response to an actual incident (lessons learned), assessment or audit findings, or changes in applicable laws, executive orders, directives, regulations, policies, standards, and guidelines.
What to Check
How to Test
Step 1: Review Documentation
Examine the System Security Plan (SSP) and related artifacts for IR-2 implementation details. Verify the organization has documented how this control is satisfied.
Step 2: Validate Implementation
# For cloud environments, use cloud-audit-mcp tools
# For on-premises, review system configurations directly
# Example: Check if account management policies exist
grep -r "account.management\|access.control" /etc/security/ 2>/dev/null
Step 3: Test Operating Effectiveness
Verify the control is actively functioning, not just documented. Check logs, configurations, and operational evidence.
Tools
| Tool | Purpose | Usage |
|---|
| Manual Review | Documentation and interview-based | N/A |
Remediation Guide
Control Statement