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.1: Document information: last update, notification of changes, location

What does 3.1 require?

Because team details change and outdated descriptions do more harm than good, the completed template must show when it was last changed and should say how to learn of updates: the date of last update; a distribution list used to notify changes, with update messages digitally signed; and the location of the current version on the team's online services, accompanied by a digital signature.

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