The evaluation of likely effectiveness covers how easily the solution can be bypassed by users or malware; its complexity (hash-based versus signature-based) and the false positives and negatives that follow; implementation and ongoing operating costs; the effect on host performance, which should not be noticeable; the impact on the mission when authorised software is blocked or malware is let through; how usable it is for users and administrators, including the information shown when something is blocked; and the long-term maintenance demand, balanced against incidents prevented.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.