RFC 2350 - Expectations for Computer Security Incident Response (BCP 21)
Section 2: Scope (publishing, relationships, secure communications) – RFC 2350 - Expectations for Computer Security Incident Response (BCP 21)

RFC 2350 - Expectations for Computer Security Incident Response (BCP 21) 2.1: Publish the CSIRT's policies and procedures to its constituency

What does 2.1 require?

Every constituent should know the team's services and how to interact with it long before needing them, including the limits of what the team will do; whatever the type of team, publishing its policies and procedures to its constituency is mandatory, in a form suited to that constituency (internal operations need not be public). Publication on the team's own information server is recommended, and because a description can be retrieved from anywhere, the team should protect it with a digital signature so users can check it is authentic and untampered.

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

Other controls in Section 2: Scope (publishing, relationships, secure communications) – 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