| name | IR-4_incident-handling |
| description | Implement an incident handling capability for incidents that is consistent with the incident response plan and includes preparation, detection and ... |
| category | configuration |
| version | 5.2.0 |
| author | cyberstrike-official |
| tags | ["nist","sp800-53","rev5","ir-4","ir"] |
| tech_stack | ["any"] |
| cwe_ids | [] |
| chains_with | ["AC-19","AU-6","AU-7","CM-6","CP-2","CP-3","CP-4","IR-2","IR-3","IR-5"] |
| prerequisites | [] |
| severity_boost | {"AC-19":"Chain with AC-19 for comprehensive security coverage","AU-6":"Chain with AU-6 for comprehensive security coverage","AU-7":"Chain with AU-7 for comprehensive security coverage"} |
IR-4 Incident Handling
High-Level Description
Family: Incident Response (IR)
Framework: NIST SP 800-53 Rev 5
Organizations recognize that incident response capabilities are dependent on the capabilities of organizational systems and the mission and business processes being supported by those systems. Organizations consider incident response as part of the definition, design, and development of mission and business processes and systems. Incident-related information can be obtained from a variety of sources, including audit monitoring, physical access monitoring, and network monitoring; user or administrator reports; and reported supply chain events. An effective incident handling capability includes coordination among many organizational entities (e.g., mission or business owners, system owners, authorizing officials, human resources offices, physical security offices, personnel security offices, legal departments, risk executive [function], operations personnel, procurement offices). Suspected security incidents include the receipt of suspicious email communications that can contain malicious code. Suspected supply chain incidents include the insertion of counterfeit hardware or malicious code into organizational systems or system components. For federal agencies, an incident that involves personally identifiable information is considered a breach. A breach results in unauthorized disclosure, the loss of control, unauthorized acquisition, compromise, or a similar occurrence where a person other than an authorized user accesses or potentially accesses personally identifiable information or an authorized user accesses or potentially accesses such information for other than authorized purposes.
What to Check
How to Test
Step 1: Review Documentation
Examine the System Security Plan (SSP) and related artifacts for IR-4 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.
