Where SOUP failure or unexpected results is a potential cause, the manufacturer evaluates at least the anomaly list the SOUP supplier publishes for the version used, to determine whether any known anomaly could lead to a sequence of events resulting in a hazardous situation. Applies to classes B and C.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.