RFC 2350 - Expectations for Computer Security Incident Response (BCP 21)
Section 3.3: Charter – RFC 2350 - Expectations for Computer Security Incident Response (BCP 21)

RFC 2350 - Expectations for Computer Security Incident Response (BCP 21) 3.3.1: Mission statement

What does 3.3.1 require?

The mission statement focuses on the team's core activities; to count as a CSIRT the team must support the reporting of incidents and support its constituency by dealing with incidents (Appendix A: provide a secure channel for reports, assist constituents in handling incidents, disseminate incident-related information), and its goals and purposes need clear, unambiguous definition.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

Other controls in Section 3.3: Charter – RFC 2350 - Expectations for Computer Security Incident Response (BCP 21)

Query this from an agent

The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.

MCP endpointAll RFC 2350 - Expectations for Computer Security Incident Response (BCP 21) controls