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.3: Establish secure communications and authenticate keys in advance

What does 2.3 require?

Once parties share information they need channels giving confidentiality, integrity and authenticity; response teams must support and use a method to secure communications with constituents and other teams at a level acceptable to the constituency. Preparation in advance is essential: public keys must be authenticated before use (web of trust or certification hierarchy), secret keys exchanged beforehand over a secure channel, and any specific verification requirement (such as calling a number to check a key) stated from the start in the template.

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