RFC 2350 - Expectations for Computer Security Incident Response (BCP 21)
Sections 3.1 and 3.2: Document and contact information – RFC 2350 - Expectations for Computer Security Incident Response (BCP 21)

RFC 2350 - Expectations for Computer Security Incident Response (BCP 21) 3.2: Contact information

What does 3.2 require?

Full details of how to reach the team: its name, mailing address, time zone (for coordinating incidents across time zones), telephone, facsimile, other telecommunication (for example secure voice), e-mail address, public keys and encryption information enabling users to decide whether and how to communicate encrypted, team members (teams may choose not to name them), operating hours and holiday schedule including whether a 24-hour hotline exists, and additional or customer contact information; separate contacts per service and procedures for special access (such as mailing-list requests) may be added.

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

Other controls in Sections 3.1 and 3.2: Document and contact information – 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