Control statement
Test the effectiveness of the incident response capability for the system [Organization-defined: frequency] using the following tests: [Organization-defined: tests].
Discussion
Organizations test incident response capabilities to determine their effectiveness and identify potential weaknesses or deficiencies. Incident response testing includes the use of checklists, walk-through or tabletop exercises, and simulations (parallel or full interrupt). Incident response testing can include a determination of the effects on organizational operations and assets and individuals due to incident response. The use of qualitative and quantitative data aids in determining the effectiveness of incident response processes.
Organization-defined parameters
These values must be resolved through the organization’s tailoring and governance process. Bracketed parameter references in the control text identify where a decision is required.
From control text to operational evidence
Use Incident Response Testing as a testable risk decision. Translate the official statement into accountable people, repeatable processes, configured technology, and evidence that demonstrates the outcome over time. In this family, pay particular attention to prepared detection, coordinated response, analysis, reporting, and lessons learned.
Implementation workflow
- Define the control boundary, responsible owner, inherited portions, and systems or processes in scope.
- Resolve each organization-defined parameter before declaring the control implemented.
- Document how the implementation satisfies every clause of the official control statement.
- Collect evidence as a normal byproduct of operation rather than only before an assessment.
- Review exceptions, changes, and monitoring results on a risk-based cadence.
Evidence examples
- incident response plans and playbooks
- case records and timelines
- exercise and tabletop results
- lessons-learned and corrective-action tracking
Common failure patterns
- plans that do not match current architecture
- unclear authority for containment decisions
- evidence lost during response
- lessons learned recorded but not implemented
Questions practitioners should ask
- What risk decision is this control intended to support in this system?
- Which parts are implemented locally, inherited, shared, or not applicable—and what evidence supports that decision?
- Do the documented narrative, deployed configuration, operating process, and collected evidence agree?
- What event or threshold requires the implementation to be reviewed or changed?
Assessment objectives and methods
Show the assessment objective
the effectiveness of the incident response capability for the system is tested [Organization-defined: frequency] using [Organization-defined: tests].
Examine
- Incident response policy
- contingency planning policy
- procedures addressing incident response testing
- procedures addressing contingency plan testing
- incident response testing material
- incident response test results
- incident response test plan
- incident response plan
- contingency plan
- system security plan
- privacy plan
- other relevant documents or records
Interview
- Organizational personnel with incident response testing responsibilities
- organizational personnel with information security and privacy responsibilities
Related controls
These relationships come from the official OSCAL catalog. They indicate useful dependencies or context, not automatic inheritance or equivalence.
Related NIST SP 800-171 requirements
These Rev. 3 requirements cite this base control or one of its enhancements as a source. The relationship does not by itself determine contractual applicability or complete implementation.
Control enhancements
Enhancements add specificity, strength, or scope to the base control. Baseline badges show explicit selections in the official SP 800-53B OSCAL profiles.
IR-3(1) — Automated Testing
Test the incident response capability using [Organization-defined: automated mechanisms].
Official discussion
Organizations use automated mechanisms to more thoroughly and effectively test incident response capabilities. This can be accomplished by providing more complete coverage of incident response issues, selecting realistic test scenarios and environments, and stressing the response capability.
Organization-defined parameters (1)
Assessment objectives and methods
the incident response capability is tested using [Organization-defined: automated mechanisms].
Examine
- Incident response policy
- contingency planning policy
- procedures addressing incident response testing
- procedures addressing contingency plan testing
- incident response testing documentation
- incident response test results
- incident response test plan
- incident response plan
- contingency plan
- system security plan
- automated mechanisms supporting incident response tests
- other relevant documents or records
Interview
- Organizational personnel with incident response testing responsibilities
- organizational personnel with information security responsibilities
Test
- Automated mechanisms that more thoroughly and effectively test the incident response capability
IR-3(2) — Coordination with Related Plans
Coordinate incident response testing with organizational elements responsible for related plans.
Official discussion
Organizational plans related to incident response testing include business continuity plans, disaster recovery plans, continuity of operations plans, contingency plans, crisis communications plans, critical infrastructure plans, and occupant emergency plans.
Assessment objectives and methods
incident response testing is coordinated with organizational elements responsible for related plans.
Examine
- Incident response policy
- contingency planning policy
- procedures addressing incident response testing
- incident response testing documentation
- incident response plan
- business continuity plans
- contingency plans
- disaster recovery plans
- continuity of operations plans
- crisis communications plans
- critical infrastructure plans
- occupant emergency plans
- system security plan
- privacy plan
- other relevant documents or records
Interview
- Organizational personnel with incident response testing responsibilities
- organizational personnel with responsibilities for testing organizational plans related to incident response testing
- organizational personnel with information security and privacy responsibilities
IR-3(3) — Continuous Improvement
Use qualitative and quantitative data from testing to:
- (a)Determine the effectiveness of incident response processes;
- (b)Continuously improve incident response processes; and
- (c)Provide incident response measures and metrics that are accurate, consistent, and in a reproducible format.
Official discussion
To help incident response activities function as intended, organizations may use metrics and evaluation criteria to assess incident response programs as part of an effort to continually improve response performance. These efforts facilitate improvement in incident response efficacy and lessen the impact of incidents.
Assessment objectives and methods
- IR-03(03)(a)
- IR-03(03)(a)[01]qualitative data from testing are used to determine the effectiveness of incident response processes;
- IR-03(03)(a)[02]quantitative data from testing are used to determine the effectiveness of incident response processes;
- IR-03(03)(b)
- IR-03(03)(b)[01]qualitative data from testing are used to continuously improve incident response processes;
- IR-03(03)(b)[02]quantitative data from testing are used to continuously improve incident response processes;
- IR-03(03)(c)
- IR-03(03)(c)[01]qualitative data from testing are used to provide incident response measures and metrics that are accurate;
- IR-03(03)(c)[02]quantitative data from testing are used to provide incident response measures and metrics that are accurate;
- IR-03(03)(c)[03]qualitative data from testing are used to provide incident response measures and metrics that are consistent;
- IR-03(03)(c)[04]quantitative data from testing are used to provide incident response measures and metrics that are consistent;
- IR-03(03)(c)[05]qualitative data from testing are used to provide incident response measures and metrics in a reproducible format;
- IR-03(03)(c)[06]quantitative data from testing are used to provide incident response measures and metrics in a reproducible format.
Examine
- Incident response policy
- contingency planning policy
- procedures addressing incident response testing
- incident response testing documentation
- incident response plan
- business continuity plans
- contingency plans
- disaster recovery plans
- continuity of operations plans
- crisis communications plans
- critical infrastructure plans
- occupant emergency plans
- system security plan
- privacy plan
- other relevant documents or records
Interview
- Organizational personnel with incident response testing responsibilities
- organizational personnel with responsibilities for testing organizational plans related to incident response testing
- organizational personnel with information security and privacy responsibilities
Authoritative sources
Bare Metal Cyber is an independent educational publisher and is not affiliated with or endorsed by NIST. Official control requirements and interpretations remain with NIST and the responsible authorizing organization.