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.2: Relationships with other CSIRTs: decide and explain what is shared

What does 2.2 require?

Because most incidents involve parties outside the constituency, a team will interact with other CSIRTs and sites (advice, dissemination of problems, joint resolution); the constituency should understand the nature and extent of that collaboration since sensitive information about constituents may be disclosed. The team must decide what agreements it can have with other teams to share yet safeguard information, whether a relationship may be disclosed and to whom, and distinguish peering agreements from simple requests for help.

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