RFC 2350 - Expectations for Computer Security Incident Response (BCP 21)
RFC 2350 (BCP 21, 1998, updated by RFC 7942) describes the expectations of the Internet community regarding Computer Security Incident Response Teams (CSIRTs). It defines what a CSIRT should communicate about itself: mission, constituency, authority, policies, services, reporting procedures, and operating procedures. The RFC established the standard template for CSIRT descriptions still used today by incident response teams worldwide. Complemented by RFC 7970 (IODEF - Incident Object Description Exchange Format), RFC 8134 (Management Incident Lightweight Exchange), and RFC 9424 (Indicators of Compromise).
Framework summaries on this platform are AI-assisted interpretations for educational and compliance planning purposes. They do not reproduce or replace the official standards. Refer to the authoritative source for the definitive text. Framework names and trademarks belong to their respective organisations.
Framework Domains (23)
Authority
| Code | Title |
|---|---|
| RFC2350-06 | Authority |
Charter
| Code | Title |
|---|---|
| RFC2350-03 | Charter and Mission Statement |
Classification
| Code | Title |
|---|---|
| RFC2350-15 | Incident Classification Scheme |
Constituency
| Code | Title |
|---|---|
| RFC2350-04 | Constituency Definition |
Contact Details
| Code | Title |
|---|---|
| RFC2350-02 | Contact Information |
Cooperation
| Code | Title |
|---|---|
| RFC2350-09 | Cooperation, Interaction, and Disclosure of Information |
Disclosure Policy
| Code | Title |
|---|---|
| RFC2350-07 | Policies and Information Disclosure |
Document Management
| Code | Title |
|---|---|
| RFC2350-01 | Document Information and Version Control |
Incident Lifecycle
| Code | Title |
|---|---|
| RFC2350-16 | Lifecycle of Incident Handling |
Legal Disclaimers
| Code | Title |
|---|---|
| RFC2350-14 | Disclaimers and Liability |
Maintenance
| Code | Title |
|---|---|
| RFC2350-18 | Periodic Review and Update of the Profile |
Proactive Services
| Code | Title |
|---|---|
| RFC2350-12 | Service Catalogue - Proactive Services |
Publication
| Code | Title |
|---|---|
| RFC2350-17 | Public Availability of the Profile Document |
Reactive Services
| Code | Title |
|---|---|
| RFC2350-11 | Service Catalogue - Reactive Services |
Reporting Intake
| Code | Title |
|---|---|
| RFC2350-13 | Incident Reporting Forms and Channels |
Section 1 - Document Information
| Code | Title |
|---|---|
| RFC2350-1.1 | Date of Last Update |
| RFC2350-1.2 | Distribution List for Notifications |
| RFC2350-1.3 | Document Locations |
Section 2 - Contact Information
| Code | Title |
|---|---|
| RFC2350-2.1 | Team Identification |
| RFC2350-2.2 | Communication Channels |
| RFC2350-2.3 | Public Keys and Encryption |
| RFC2350-2.4 | Points of Customer Contact |
Section 3 - Charter
| Code | Title |
|---|---|
| RFC2350-3.1 | Mission Statement |
| RFC2350-3.2 | Constituency |
| RFC2350-3.3 | Sponsorship and Affiliation |
| RFC2350-3.4 | Authority |
Section 4 - Policies
| Code | Title |
|---|---|
| RFC2350-4.1 | Types of Incidents and Level of Support |
| RFC2350-4.2 | Cooperation and Disclosure |
| RFC2350-4.3 | Communication and Authentication |
Section 5 - Services
| Code | Title |
|---|---|
| RFC2350-5.1 | Incident Triage |
| RFC2350-5.2 | Incident Coordination |
| RFC2350-5.3 | Incident Resolution |
| RFC2350-5.4 | Proactive Activities |
Secure Communication
| Code | Title |
|---|---|
| RFC2350-10 | Communication and Authentication |
Service Scope
| Code | Title |
|---|---|
| RFC2350-08 | Types of Incidents and Level of Support |
Sponsorship
| Code | Title |
|---|---|
| RFC2350-05 | Sponsorship and Affiliation |
Your Compliance Coverage
If you comply with RFC 2350 - Expectations for Computer Security Incident Response (BCP 21), you already cover:
ISO/IEC 27400:2022
22%
8 controls mapped
Compare →FTC GLBA Safeguards Rule (16 CFR Part 314)
19%
7 controls mapped
Compare →NIST SP 800-171A Rev 3 - Assessing CUI Security Requirements
19%
7 controls mapped
Compare →+ 270 more: RBI Cybersecurity Framework for Banks (19%), NIST SP 800-124 Revision 2 - Guidelines for Managing the Security of Mobile Devices (19%)
See all 273 mapped frameworks ↓Maps to 273 other frameworks
Frequently Asked Questions
What is RFC 2350 - Expectations for Computer Security Incident Response (BCP 21)?
RFC 2350 - Expectations for Computer Security Incident Response (BCP 21) is a compliance framework from International (IETF) with 23 domains and 36 controls. RFC 2350 (BCP 21, 1998, updated by RFC 7942) describes the expectations of the Internet community regarding Computer Security Incident Response Teams (CSIRTs). It defines what a CSIRT should communicate about itself: mission, constituency, authority, policies, services, reporting procedures, and operating procedures. The RFC established the standard template for CSIRT descriptions still used today by incident response teams worldwide. Complemented by RFC 7970 (IODEF - Incident Object Description Exchange Format), RFC 8134 (Management Incident Lightweight Exchange), and RFC 9424 (Indicators of Compromise). It is used by organisations to establish and maintain compliance with industry standards and regulatory requirements.
How many controls does RFC 2350 - Expectations for Computer Security Incident Response (BCP 21) have?
RFC 2350 - Expectations for Computer Security Incident Response (BCP 21) has 36 controls organised across 23 domains. The largest domains are Section 2 - Contact Information (4 controls), Section 3 - Charter (4 controls), Section 5 - Services (4 controls). Each control defines specific requirements that organisations must implement to achieve compliance.
What frameworks does RFC 2350 - Expectations for Computer Security Incident Response (BCP 21) map to?
RFC 2350 - Expectations for Computer Security Incident Response (BCP 21) maps to 273 other compliance frameworks. The top mapping partners are ISO/IEC 27400:2022 (22% coverage), FTC GLBA Safeguards Rule (16 CFR Part 314) (19% coverage), NIST SP 800-171A Rev 3 - Assessing CUI Security Requirements (19% coverage). Use our comparison tool to explore control-level mappings between frameworks.
How do I get started with RFC 2350 - Expectations for Computer Security Incident Response (BCP 21) compliance?
Start your RFC 2350 - Expectations for Computer Security Incident Response (BCP 21) compliance journey by running a self-assessment on our platform to identify your current compliance posture. Our AI advisory can answer specific questions about RFC 2350 - Expectations for Computer Security Incident Response (BCP 21) requirements, and cross-framework mapping helps you leverage existing controls from other frameworks you may already comply with. Create a free account to access all 36 controls and track your progress.
Start Your Compliance Journey
Create a free account to run self-assessments, get AI advisory, and track your compliance progress across 700 frameworks.
Get Started Free →Free forever — no credit card required