Response activities are coordinated with internal and external stakeholders as required by laws, regulations, or policies
Scanned 9/3/2026
Install to Claude Code
npx -y skills add CyberStrikeus/CyberStrike --skill incident-response-reporting-and --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Incident Response Reporting And?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/cyberstrikeus-incident-response-reporting-and)More formats (shields.io, HTML) on the badges page.
---
name: "Incident Response Reporting and Communication (RS.CO)_incident-response-reporting-and-communication"
description: "Response activities are coordinated with internal and external stakeholders as required by laws, regulations, or policies"
category: "configuration"
version: "2.0"
author: "cyberstrike-official"
tags:
- nist
- csf
- v2.0
- incident response reporting and communication (rs-co)
- rs
- category
tech_stack:
- any
cwe_ids: []
chains_with: []
prerequisites: []
severity_boost: {}
---
# Incident Response Reporting and Communication (RS.CO) Incident Response Reporting and Communication
## High-Level Description
**Function:** RESPOND (RS)
**Framework:** NIST Cybersecurity Framework v2.0
Response activities are coordinated with internal and external stakeholders as required by laws, regulations, or policies
## What to Check
- [ ] Verify Incident Response Reporting and Communication (RS.CO) Incident Response Reporting and Communication outcome is achieved
- [ ] Review documentation and evidence for Incident Response Reporting and Communication (RS.CO)
- [ ] Assess organizational maturity for RESPOND function
## How to Test
### Step 1: Identify Current Profile
Determine the organization's current and target CSF profile tier for Incident Response Reporting and Communication (RS.CO).
### Step 2: Assess Outcome Achievement
```
# Review organizational policies and procedures
# Check for evidence that Incident Response Reporting and Communication (RS.CO) outcome is met
# Interview stakeholders responsible for RESPOND
```
### Step 3: Map to Technical Controls
Identify which SP 800-53 controls implement this CSF outcome and verify their operating effectiveness.
## Tools
| Tool | Purpose | Usage |
| --------------- | ----------------------------- | ---------------------------- |
| cloud-audit-mcp | Assess cloud security posture | `cloud_audit_*` tools |
| Manual Review | Policy and procedure review | Interviews and documentation |
## Remediation Guide
Achieve the Incident Response Reporting and Communication (RS.CO) Incident Response Reporting and Communication outcome:
Response activities are coordinated with internal and external stakeholders as required by laws, regulations, or policies
## Risk Assessment
| Finding | Severity | Impact |
| ------------------------------------------------------------------------------------------------------------------------ | -------- | -------------------- |
| Incident Response Reporting and Communication (RS.CO) Incident Response Reporting and Communication outcome not achieved | Medium | RESPOND Function Gap |
## CWE Categories
| CWE ID | Title |
| ------ | --------------------- |
| N/A | No direct CWE mapping |
## References
- [NIST CSF v2.0](https://www.nist.gov/cyberframework)
- [NIST CSF v2.0 Reference Tool](https://csrc.nist.gov/projects/cybersecurity-framework/filters#/csf/filters)
- [CSF 2.0 Quick Start Guides](https://www.nist.gov/cyberframework/getting-started)
## Checklist
- [ ] Current profile tier assessed
- [ ] Target profile tier defined
- [ ] Gap analysis completed
- [ ] SP 800-53 control mapping verified
- [ ] Implementation roadmap exists
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!