RFC 2350 - Expectations for Computer Security Incident Response (BCP 21)
Sections 3.6 and 3.7: Reporting forms and disclaimers – RFC 2350 - Expectations for Computer Security Incident Response (BCP 21)

RFC 2350 - Expectations for Computer Security Incident Response (BCP 21) 3.7: Disclaimers

What does 3.7 require?

Although the description is not a contract, liability could arise from its descriptions of services and purposes, so a disclaimer warning of limitations is recommended at the end of the template; a translation should carry a disclaimer and a pointer to the original stating which version prevails, and the disclaimer should be checked against local law, with a lawyer if in doubt.

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

Other controls in Sections 3.6 and 3.7: Reporting forms and disclaimers – 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