Prioritized activities can be shielded by lowering the chance they are disrupted or by handing them to a third party while the organization keeps the responsibility, and where workable alternatives exist the way an activity is carried out can be changed. Guidance: in choosing how to shield prioritized activities, weigh how much vulnerability the activity can bear and what follows if it stops, what the measures cost against the benefit expected, how urgent the activity is (urgency leaves less time to fix problems), and whether the measures are practical and suitable overall.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.