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.2: Constituency

What does 3.3.2 require?

The constituency (for example a company's employees, paid subscribers, or users of a technology) is defined so as to draw a perimeter around those the team serves; the policy section explains how requests from outside the perimeter are handled. A team that does not disclose its constituency should explain why (a commercial team may state it serves confidential clients), and overlapping constituencies (an ISP team serving sites with their own teams) are clarified in the authority section.

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