Coordinate incident response testing with organizational elements responsible for related plans.
Scanned 9/3/2026
Install to Claude Code
npx -y skills add CyberStrikeus/CyberStrike --skill IR-3(2)_coordination-with-related-plans --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of IR 3(2) Coordination With Related Plans?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/cyberstrikeus-ir-3-2-coordination-with-related-plans)More formats (shields.io, HTML) on the badges page.
---
name: "IR-3(2)_coordination-with-related-plans"
description: "Coordinate incident response testing with organizational elements responsible for related plans."
category: "configuration"
version: "5.2.0"
author: "cyberstrike-official"
tags:
- nist
- sp800-53
- rev5
- ir-3-2
- ir
- enhancement
tech_stack:
- any
cwe_ids: []
chains_with: []
prerequisites:
- IR-3
severity_boost: {}
---
# IR-3(2) Coordination with Related Plans
> **Enhancement of:** IR-3
## High-Level Description
**Family:** Incident Response (IR)
**Framework:** NIST SP 800-53 Rev 5
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.
## What to Check
- [ ] Verify IR-3(2) Coordination with Related Plans is documented in SSP
- [ ] Confirm control is operating effectively
- [ ] Review evidence of continuous monitoring for IR-3(2)
- [ ] Verify enhancement builds upon base control IR-3
## How to Test
### Step 1: Review Documentation
Examine the System Security Plan (SSP) and related artifacts for IR-3(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
Coordinate incident response testing with organizational elements responsible for related plans.
### Implementation Guidance
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.
## Risk Assessment
| Finding | Severity | Impact |
| ------------------------------------------------------- | -------- | ---------------------------- |
| IR-3(2) Coordination with Related Plans not implemented | Medium | Incident Response |
| IR-3(2) partially implemented | Low | Incomplete Incident Response |
## CWE Categories
| CWE ID | Title |
| ------ | --------------------- |
| N/A | No direct CWE mapping |
## References
- [NIST SP 800-53 Rev 5 - IR-3(2)](https://csrc.nist.gov/projects/cprt/catalog#/cprt/framework/version/SP_800_53_5_1_1/home?element=ir-3.2)
- [NIST SP 800-53A Rev 5 (Assessment Procedures)](https://csrc.nist.gov/pubs/sp/800/53/a/r5/final)
- [NIST SP 800-53 Rev 5 Full Catalog](https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final)
## Checklist
- [ ] Control documented in SSP
- [ ] Implementation evidence collected
- [ ] Operating effectiveness validated
- [ ] Continuous monitoring in place
- [ ] Related controls (none) reviewed
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!